Difference between revisions of "RAD TF Maintenance 2019-2020"
Jump to navigation
Jump to search
| Line 79: | Line 79: | ||
| − | List of " | + | List of "non-trivial" CPs: |
| − | |||
| − | |||
List of outstanding items not yet submitted as CPs: | List of outstanding items not yet submitted as CPs: | ||
| − | List of | + | List of "priority" CPs: |
| − | |||
:* Repeat TOP TEN CPs process | :* Repeat TOP TEN CPs process | ||
::* note that the list of CPs is increasing, not decreasing | ::* note that the list of CPs is increasing, not decreasing | ||
| Line 94: | Line 91: | ||
::* Consider which might help a profile go to FT | ::* 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 | ::* Consider organizing batches of CPs around themes (Profile or topic) so we can get relevant domain experts on that call and keep them engaged | ||
| − | |||
| − | |||
| − | :* Profile Pages on Wiki | + | List of other maintenance tasks (proposed priority): |
| − | : | + | :* Split technical framework Vol 1-3 into multiple smaller documents |
| + | :** Some thought about how to do this: | ||
| + | :*** 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 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. | ||
| + | :* 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: | Update existing page: | ||
| − | *SWF to SWF.b (Andrei) | + | * SWF to SWF.b (Andrei) |
* Update IRWF to IRWF.b (Kinson) | * Update IRWF to IRWF.b (Kinson) | ||
Revision as of 15:35, 12 September 2019
(Personally, I'd like to prioritize time to get a bunch of TI Profiles to FT (and maybe retire a couple) - KOD)
Target Dates:
- Publish CP Ballot in early-Jan 2018? (for CPs needed for IHE-Europe Connectathon in April 2018) (is this enough time?)
- Allow adequate time at the Nov F2F Meeting to prep for this
- Publish CP Ballot at end-of-April 2018
- Incorporate FT CPs into updated TF released July 2018
- Publish CP Ballot in early-Jan 2018? (for CPs needed for IHE-Europe Connectathon in April 2018) (is this enough time?)
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.
Number of outstanding CPs:
List of "non-trivial" CPs:
List of outstanding items not yet submitted as CPs:
List of "priority" CPs:
- 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
List of other maintenance tasks (proposed priority):
- Split technical framework Vol 1-3 into multiple smaller documents
- Some thought about how to do this:
- 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 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:
- 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
- Split technical framework Vol 1-3 into multiple smaller documents
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):
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 | 36% | 45% | 62% | 29% | 19% |
Discussion
- What do we want to do in the normal time allotted.