Final Text Process
Revision as of 10:57, 4 April 2007 by Chrisdcarr (talk | contribs)
<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)
- 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?
- Have at least one of each actor been released in the market (but Vendors may not want to publish integration statement if it’s not FT)?
- ?? Have any complaints been raised against the profile ??
- Are there any outstanding CPs against the profile?
- Debate exceptions (failure of the above is cause for discussion)
- Hold and record formal vote
- Communicate results to TC
Tech Cmte.
- 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>