Final Text Process

<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 tested with all actors at least at one Connectathon.
  • have the standards underlying the profile been previously implemented in a system/product in our domain (expand on the issue of testing the standard and testing the profile)
  • has each actor in the profile been implemented independently at least twice
  • 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>