RAD TF Maintenance 2019-2020
Jump to navigation
Jump to search
Target Dates:
- Publish 3+ CP Ballots (one shortly after each face-to-face meeting in November, January, April)
- Candidate CPs and assignees should be identified early and have enough time to work on the CPs so that the committee can review during the F2F meeting
- Incorporate FT CPs into updated TF released July 2020
- Publish 3+ CP Ballots (one shortly after each face-to-face meeting in November, January, April)
Prioritize TI profiles:
- There are current a large number of Radiology profiles remain in TI for a long time. Sometimes new profiles reference transactions in these TI profiles, making understanding these new profiles challenging, involving reviewing multiple documents and find the relevant sections. To address this problem, we need to review them to determine if the profile should be promoted to Final Text or deprecated.
- Review Questionnaire Template for decision making (EP: 1)
- Assign selected TI profiles to someone to lead the evaluation (EP: 1)
- Schedule a TC meeting to assign the top x TI profile review candidates so that we can review the questionnaire at the kickoff meeting.
Number of outstanding CPs: 81 (Assigned by end of 2018-19 cycle), 81 (Assigned by end of 2017-18 cycle), 75 (2016-17), 68, 59
List of "non-trivial" CPs:
List of outstanding items not yet submitted as CPs:
List of "priority" CPs:
- Completed the 4 remaining SWF.b CPs that were identified in 2018-19 cycle but have not yet completed
- CP-RAD-356 (Charles)
- CP-RAD-378 (Charles)
- CP-RAD-379 (Kinson)
- CP-RAD-382 (Kinson)
- Repeat TOP TEN CPs process
- note that the list of CPs is increasing, not decreasing
- CP author distribution
- Consider which might help a profile go to FT
- Consider organizing batches of CPs around themes (Profile or topic) so we can get relevant domain experts on that call and keep them engaged
- Completed the 4 remaining SWF.b CPs that were identified in 2018-19 cycle but have not yet completed
List of other maintenance tasks (proposed priority):
- Split technical framework Vol 1-3 into multiple smaller documents (come up with a low risk mechanical method, and volume editors and Mary will work through the details)
- Some thought about how to do this: (Kinson)
- Speaking of breaking up the TF, my thought is that can we do something slightly different from ITI? That means can we create the break up Vol1-3. For example, Vol 2 to 2a, 2b, 2.. and Vol 3 to 3a, 3b, 3… (e.g. by number of transactions that we want to keep in one document), but we DO NOT change the section references to reference 2a or 3b, but stay with referencing just Vol 2 and 3 as today. I think the readers will know that when referencing Vol 3, it is inside one of 3a, 3b, 3… Then in the document title page, it can include also the transaction number range. Therefore someone trying to find TF Vol 3: 3.74 will immediately know which TF Vol 3x should read. No hunting necessary. Also we don’t change any of the references, which is the scary part because we need to make sure there is no dangling references or old references to nowhere. With this plan, then we can easily break up the TF Vol 2 and 3 now into smaller documents. If we agree with the plan, I am in fact leaning towards do it now than pushing to another cycle.
- In Vol 3, we should put all of the ‘content module’ sections into one document. This is RAD TF-3: 6. None of this content is Final Text yet (eg RAD TF-3: 6.1 in XDR-I).
- For the Vol 2 and Vol 3 documents that contain transactions, the cover page could contain the starting and ending transaction number.
- We will have to consider what to do about appendices. Maybe all Vol 2 appendices in one Vol 2 document, and all Vol 3 appendices into one Vol 3 document.
- Some thought about how to do this: (Kinson)
- Split technical framework Vol 1-3 into multiple smaller documents (come up with a low risk mechanical method, and volume editors and Mary will work through the details)
- How to more effectively use the regular scheduled CP tcons? (Wim)
- Observation: some CPs can be effective done in tcons and leave the f2f time for more important work.
- Write up a proposal for how many regular CP tcons.
- How to more effectively use the regular scheduled CP tcons? (Wim)
- Update the existing technical framework to use the new template?
- Need to identify what needs to be done: (Kevin)
- Content of each profile chapter
- New profile inside a chapter will use new template, old ones remain old template. => Should not be a problem
- Need to fix the "intro chapters"
- Update the existing technical framework to use the new template?
- Enhance outreach-ability to make the profile wiki more easier to consumer by people not already familiar with IHE
Profile Pages on Wiki
- From the face-to-face meeting in January 2019, we agreed the following catch up:
Update existing page:
- SWF to SWF.b (Andrei)
- Update IRWF to IRWF.b (Kinson)
Populate empty or missing page:
- EBIW (Kevin)
- RD (Antje)
- KIN (Antje)
- MRRT (Kinson)
7. Risks
- Effort underestimated for other activities, less effort spend on maintenance
- Lack of appropriate knowledge, there is a lack of expertise in HL7v2 area
9. Tech Cmte Evaluation
Effort Evaluation (as a % of Tech Cmte Bandwidth): 35%
Total Maintenance load
For reference from recent cycles:
| Cycle | 2018-19 | 2017-18 | 2016-17 | 2015-16 | 2014-15 | 2013-14 | 2012-13 | |
| Maint Allocated | 30% | 40% | 15% | 35% | 30% | 30% | 15% | |
| Maint Used | 38% | 31% + 28% (WIA) | 17% + 26% (WIA) | 45% | 62% | 29% | 19% | |
| Outstanding CPs | 87 | 81 | 75 | 68 | 59 | 47 |
Discussion
- What do we want to do in the normal time allotted.