HL7 Registration of Terminology Systems (Proposal)

Background Principles have been developed over the last 2 years Processes for implementing those principles must now be developed Need a fair process that does not subject HL7 to liability regarding antitrust, or other types of liability

Proposal Terminology Systems will self-register Registration of a terminology system will require Registration Documentation to describe how the system is to be used in HL7 Registration process will not discriminate, and thus will not incur liability

Registration Documentation An itemized description of how the Terminology System meets the “Principles for HL7-compliant terminologies” A initial list of domain constraints for HL7 v 2.X and v 3.X in tabular form suitable for upload into a commercial database as described in the Terminology Chapter of the Message Development Framework

Registration Step 1 A Terminology System Sponsor (acceptable to the Terminology Development Organization being sponsored) will identify themselves to the HL7 Terminology TC and will commit to the creation and timely update of the HL7 terminology registration documentation.

Registration Step 2 Complete the Registration Documentation Make the documentation available to HL7 for posting on the HL7 web site

Registration Step 3 Respond to questions: Any HL7 member may ask clarifying question regarding the principles and the domain constraints. These questions alone or the questions and their subsequent answers will become a permanent part of the documents. Questions deemed irrelevant by a majority of the Technical Committee Co-Chairs may be excluded from or edited before inclusion into the Registration Documentation.

Registration Step 4 Completed registration documents are submitted during a regular HL7 meeting. At the next HL7 meeting, allowing for clarifying questions and incorporation of the answers of those questions into the registration documentation, the terminology system shall be considered registered.

Obligations upon registration Advertisements that a system is HL7 registered must include a prominent disclaimer stating that “HL7 registration does not imply endorsement by the HL7 organization, nor does it imply that a system is necessarily appropriate for use in HL7 messages.” Keep the document up to date on a quarterly basis, and move toward comprehensive specification of domain values.

Finalize Guidelines for HL7 Compliant Terminology

Change the name: From: Principles for Approving HL7-Compliant Terminologies To: Principles for HL7-Compliant Terminologies

The hard one: Motion to keep 4 as is: 3 for, rest against. Motion Fails Motion to remove 4 from document and not replace: 13 for, 15 against. Motion fails. Motion: Appropriateness of cost will be a consideration. 2 for, 26 against. Motion Fails. Agreed to come back to this later in the day..

Original text: The Terminology must be free from excessive license fees, yet HL7-sanctioned interoperability efforts must not jeopardize the business model of the terminology provider (see “Principles for HL7- Sanctioned Terminology Integration Efforts)

Proposal Terminology license fees should be proportional to the value they provide to the enterprise and the end user, yet should not be out of proportion with the development and support costs of the terminology itself.