Final Text Process

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 (e.g. in mid-Feb)
• Run down the 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?

The Planning Committee votes on the proposal from the Tech Cmte to Final Text

• Put Final Text Decision on the planning committee agenda (April-May)
  • input pre-requisite: Deal with CPs against the profile.
  • input pre-requisite: after Connectathons (NA=Jan, EU=Apr)

• 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>