Difference between revisions of "Final Text Process"
Jump to navigation
Jump to search
(minor rewording and added link to subscribe to technical publication emails.) |
|||
| (24 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Taking a supplement from Trial Implementation to Final Text should go through 4 stages: Proposal, Consensus, Incorporation and Publication. | |
| − | |||
| − | + | ==Proposal== | |
| − | + | The Technical Committee, after a minimum of one annual cycle of Connectathon testing, decides that a Trial Implementation supplement is ready for consideration as a Final Text candidate. | |
| − | |||
| − | |||
| − | * Announce intention to review for Final Text ( | + | * Announce intention to review for Final Text |
| + | ** Consider doing this around the time of Public Comment for other Profiles | ||
| + | * Run down the following checklist for each profile | ||
| + | ** Are all significant CPs against the profile "closed"? | ||
| + | ** Are all significant CPs against the underlying standards "closed"? | ||
| + | ** Have all significant comments been CP'd or rejected? | ||
| + | ** Have all open issues listed in the Supplement been closed? | ||
| + | ** Have all significant issues at Connectathon been dealt with? | ||
| + | ** Gather feedback from implementers. Your domain secretary has access to the contact information for vendors that have tested your profile at previous Connectathons and can help coordinate reaching out. | ||
| + | ** Has the Connectathon Project Manager been queried and significant issues addressed? | ||
| + | * Debate checklist exceptions (failure of any of the above is cause for discussion) | ||
| + | * Record checklist findings and debate conclusion | ||
| − | + | ==Consensus== | |
| − | + | The Planning Committee votes on the Tech Cmte proposal to Final Text the supplement. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | * Debate exceptions (failure of the above is cause for discussion) | + | * Put Final Text Decision on the planning committee agenda |
| + | ** Consider doing this a couple months before new TF version will be released so it can be incorporated. | ||
| + | ** It's helpful to assign an advocate for the supplement at this time to check/prepare the evidence for the upcoming checklist rather than go hunting for it during the meeting | ||
| + | * Run down the following checklist for each proposed supplement | ||
| + | ** Has the profile been through a Connectathon in at least two regions? | ||
| + | ** Has the profile been successfully tested with all actors at least at one Connectathon? | ||
| + | ** Have different implementations of each actor in the profile been tested? | ||
| + | ** Have all the options been tested successfully at at least one Connectathon? | ||
| + | ** Are there IHE-provided software testing tools to address all aspects of the profile? | ||
| + | ** Have the standards underlying the profile been implemented? In similar use cases? In healthcare? In general IT? | ||
| + | ** (Do you have concrete reason to believe that this works robustly in the Real World) / (Are any products available for purchase that implement the profile?) | ||
| + | ** Have all issues that may have been raised about the profile been resolved? | ||
| + | ** Has there been sufficient interest in the profile to generate a one-page [[Profiles|overview of the profile]] | ||
| + | * Debate checklist exceptions (failure of any of the above is cause for discussion) | ||
| + | * Record checklist findings and conclusions of the debate in your meeting minutes | ||
* Hold and record formal vote | * Hold and record formal vote | ||
* Communicate results to TC | * Communicate results to TC | ||
| − | + | ==Incorporation== | |
| + | The Technical Committee completes the Final Text and/or folds it into the Technical Framework: | ||
| + | |||
* Prepare Final Text Supplement | * Prepare Final Text Supplement | ||
| − | |||
| − | |||
| − | + | ==Publication== | |
| + | The IHE Documentation Specialist publishes the updated Technical Framework on the [http://ihe.net/Technical_Frameworks/ ihe.net website]. An announcement is made to the IHE Technical Frameworks distribution list (a subset of the IHE Newsletter distribution list). To subscribe to IHE Technical Frameworks emails see [https://www.ihe.net/monthly-newsletters/technical-publications/ here]. | ||
| + | |||
| + | ==See Also== | ||
| + | * [[Final Text Evaluations]] of Profiles | ||
Latest revision as of 10:17, 12 February 2020
Taking a supplement from Trial Implementation to Final Text should go through 4 stages: Proposal, Consensus, Incorporation and Publication.
Proposal
The Technical Committee, after a minimum of one annual cycle of Connectathon testing, decides that a Trial Implementation supplement is ready for consideration as a Final Text candidate.
- Announce intention to review for Final Text
- Consider doing this around the time of Public Comment for other Profiles
- Run down the following checklist for each profile
- Are all significant CPs against the profile "closed"?
- Are all significant CPs against the underlying standards "closed"?
- Have all significant comments been CP'd or rejected?
- Have all open issues listed in the Supplement been closed?
- Have all significant issues at Connectathon been dealt with?
- Gather feedback from implementers. Your domain secretary has access to the contact information for vendors that have tested your profile at previous Connectathons and can help coordinate reaching out.
- Has the Connectathon Project Manager been queried and significant issues addressed?
- Debate checklist exceptions (failure of any of the above is cause for discussion)
- Record checklist findings and debate conclusion
Consensus
The Planning Committee votes on the Tech Cmte proposal to Final Text the supplement.
- Put Final Text Decision on the planning committee agenda
- Consider doing this a couple months before new TF version will be released so it can be incorporated.
- It's helpful to assign an advocate for the supplement at this time to check/prepare the evidence for the upcoming checklist rather than go hunting for it during the meeting
- Run down the following checklist for each proposed supplement
- Has the profile been through a Connectathon in at least two regions?
- Has the profile been successfully tested with all actors at least at one Connectathon?
- Have different implementations of each actor in the profile been tested?
- Have all the options been tested successfully at at least one Connectathon?
- Are there IHE-provided software testing tools to address all aspects of the profile?
- Have the standards underlying the profile been implemented? In similar use cases? In healthcare? In general IT?
- (Do you have concrete reason to believe that this works robustly in the Real World) / (Are any products available for purchase that implement the profile?)
- Have all issues that may have been raised about the profile been resolved?
- Has there been sufficient interest in the profile to generate a one-page overview of the profile
- Debate checklist exceptions (failure of any of the above is cause for discussion)
- Record checklist findings and conclusions of the debate in your meeting minutes
- Hold and record formal vote
- Communicate results to TC
Incorporation
The Technical Committee completes the Final Text and/or folds it into the Technical Framework:
- Prepare Final Text Supplement
Publication
The IHE Documentation Specialist publishes the updated Technical Framework on the ihe.net website. An announcement is made to the IHE Technical Frameworks distribution list (a subset of the IHE Newsletter distribution list). To subscribe to IHE Technical Frameworks emails see here.
See Also
- Final Text Evaluations of Profiles