Final Text Process: Difference between revisions
Jump to navigation
Jump to search
AGREED by DCC |
No edit summary |
||
| Line 1: | Line 1: | ||
==Proposal== | |||
The Technical Committee, at some point, decides that a Trial Implementation supplement is ready for consideration as a Final Text candidate. | The Technical Committee, at some point, 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 | ** Consider doing this around the time of Public Comment for other Profiles | ||
* Run down the checklist for each profile | * Run down the following checklist for each profile | ||
** Are all significant CPs against the profile "closed"? | ** Are all significant CPs against the profile "closed"? | ||
** Have all significant comments been CP'd or rejected? | ** Have all significant comments been CP'd or rejected? | ||
| Line 8: | Line 10: | ||
*** Gather feedback from implementers via a [ftp://ftp.ihe.net/Connectathon/IHE%20Vendor%20Questionnaire%20V0.4.doc formal questionnaire to Connectathon participants] | *** Gather feedback from implementers via a [ftp://ftp.ihe.net/Connectathon/IHE%20Vendor%20Questionnaire%20V0.4.doc formal questionnaire to Connectathon participants] | ||
** Has the Connectathon Project Manager been queried and significant issues addressed? | ** 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 | * Put Final Text Decision on the planning committee agenda | ||
** Consider doing this a couple months before new TF version will be released | ** Consider doing this a couple months before new TF version will be released so it can be incorporated. | ||
* Run down the checklist for each | * 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 through a Connectathon in at least two regions? | ||
** Has the profile been successfully tested with all actors at least at one Connectathon? | ** Has the profile been successfully tested with all actors at least at one Connectathon? | ||
| Line 23: | Line 28: | ||
** Have all issues that may have been raised about the profile been resolved? | ** Have all issues that may have been raised about the profile been resolved? | ||
** Have all CPs against the profile been addressed? | ** Have all CPs against the profile been addressed? | ||
* Debate exceptions (failure of the above is cause for discussion) | * Debate checklist exceptions (failure of any of the above is cause for discussion) | ||
* Record checklist findings and debate conclusions | |||
* 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 Tech Framework: | |||
* Prepare Final Text Supplement | * Prepare Final Text Supplement | ||
==Publication== | |||
The Secretariat publishes the updated Technical Framework | |||
* Publish Final Text on ihe.net | * Publish Final Text on ihe.net | ||
* Announce publication | * Announce publication on ...? | ||
Revision as of 15:06, 27 July 2007
Proposal
The Technical Committee, at some point, 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"?
- Have all significant comments been CP'd or rejected?
- Have all significant issues at Connectathon been dealt with?
- Gather feedback from implementers via a formal questionnaire to Connectathon participants
- 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.
- 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?
- Have all CPs against the profile been addressed?
- Debate checklist exceptions (failure of any of the above is cause for discussion)
- Record checklist findings and debate conclusions
- Hold and record formal vote
- Communicate results to TC
Incorporation
The Technical Committee completes the Final Text and/or folds it into the Tech Framework:
- Prepare Final Text Supplement
Publication
The Secretariat publishes the updated Technical Framework
- Publish Final Text on ihe.net
- Announce publication on ...?