Difference between revisions of "Vocabulary and RIM Harmonization Process"
| Line 6: | Line 6: | ||
*The representatives would reach consensus before approving a proposal | *The representatives would reach consensus before approving a proposal | ||
*An updated, documented, "approved" RIM would be available at each HL7 Working Group Meeting to allow progress on the RIM-based standards being developed in HL7 | *An updated, documented, "approved" RIM would be available at each HL7 Working Group Meeting to allow progress on the RIM-based standards being developed in HL7 | ||
| + | |||
| + | The first Harmonization Meeting was held July 8 & 9, 1997 in Indianapolis, Indiana. Since then there has been at least one "interim" Harmonization Meeting between each pair of Working Group Meetings. By 1999, when Vocabulary content became part of the core definition of the RIM classes, the scope was extended to include Vocabulary, and this dual responsibility has remained ever since. | ||
=Prior Content and History= | =Prior Content and History= | ||
Revision as of 14:49, 7 June 2010
Background and Objectives
When HL7 first considered developing a single Reference Information Model (RIM) for use in all of the HL7 technical committees (as they were then known), it adopted a process of "RIM Harmonization" to assure that:
- There was a formal process for review and adoption of change proposals
- The process would include representation from all interested groups within HL7
- (and from external Standards Development Organizations (SDOs) that wished to collaborate)
- The representatives would reach consensus before approving a proposal
- An updated, documented, "approved" RIM would be available at each HL7 Working Group Meeting to allow progress on the RIM-based standards being developed in HL7
The first Harmonization Meeting was held July 8 & 9, 1997 in Indianapolis, Indiana. Since then there has been at least one "interim" Harmonization Meeting between each pair of Working Group Meetings. By 1999, when Vocabulary content became part of the core definition of the RIM classes, the scope was extended to include Vocabulary, and this dual responsibility has remained ever since.
Prior Content and History
This Page was initiated by Russ Hamm May 17, 2010
I moved two prior Harmonization-related sub-items (that had been listed under MnM on the "Main page") here, because as this page is completed, this is where those links belong. GWBeeler
- Harmonization Wiki Template
- This template came into being in 2006, but has never been formally used as a harmonization source path. I (GWBeeler) suggest this be dropped for the following reason(s):
- The current proposal management process is highly dependent upon being able to extract 'specific data fields from the Word document, and the Wiki template has no facilities that lend themselves to reliable automated parsing.
- We should focus current improvements on the updating of the Word "template"
- This template came into being in 2006, but has never been formally used as a harmonization source path. I (GWBeeler) suggest this be dropped for the following reason(s):
- Vocabulary Harmonization Tool
- The Vocabulary Maintenance Language remains a main-stay of vocabulary harmonization processing, but the specific tool linked from here has no active users, and therefore, I (GWBeeler) suggest this link be dropped.
