Difference between revisions of "Final Text Process"
Jump to navigation
Jump to search
Chrisdcarr (talk | contribs) |
Chrisdcarr (talk | contribs) |
||
| Line 9: | Line 9: | ||
* Announce intention to review for Final Text (announce in mid-Feb) | * Announce intention to review for Final Text (announce in mid-Feb) | ||
| + | |||
| + | * Gather feedback from implementers via a formal questionnaire to Connectathon participants | ||
* Run down the checklist for each profile | * Run down the checklist for each profile | ||
| Line 17: | Line 19: | ||
** Are there IHE-provided software testing tools to address all aspects of the profile? | ** 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? | ** Have the standards underlying the profile been implemented? In similar use cases? In healthcare? In general IT? | ||
| − | ** | + | ** 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 exceptions (failure of the above is cause for discussion) | * Debate exceptions (failure of the above is cause for discussion) | ||
| Line 25: | Line 27: | ||
* Communicate results to TC | * Communicate results to TC | ||
| − | + | Technical Committee | |
* Prepare Final Text Supplement | * Prepare Final Text Supplement | ||
* Publish Final Text on ihe.net | * Publish Final Text on ihe.net | ||
Revision as of 11:10, 4 April 2007
<Note: All Process pages are very much Strawman documents>
At some point, a Trial Implementation supplement will be ready for consideration as a Final Text candidate.
- Put Final Text Decision on the planning committee agenda (April-May)
- scheduling pre-requisite: after Public Comment resolution meeting (March)
- input pre-requisite: Deal with CPs against the profile.
- input pre-requisite: after Connectathons (NA=Jan, EU=Apr)
- Announce intention to review for Final Text (announce in mid-Feb)
- Gather feedback from implementers via a formal questionnaire to Connectathon participants
- Run down the checklist for each profile
- 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?
- 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 exceptions (failure of the above is cause for discussion)
- Hold and record formal vote
- Communicate results to TC
Technical Committee
- Prepare Final Text Supplement
- Publish Final Text on ihe.net
- Announce publication
<Discuss whether you can put an Integration Statement up for a TI Profile? Would need to review and either remove IS or change implementation based on Final Text>