TermInfo Project
This group has been ArchivedStatus
This Work Group has been archived.
Charter
Work Products and Contributions to HL7 Processes
WP1: Specification of a general approach to resolving issues related to the interface between HL7 information models and terminologies or code systems.
- The purpose of this activity is to enable HL7 Version 3 standards to achieve their stated goal of semantic interoperability between systems using one or more widely adopted terminologies.
- The initial focus will be on terminologies recommended for clinical use by NHCVS or by large scale service providers, such as the national government or central authority of an HL7 International Affiliate realm.
- This activity will:
- Identify specific guides required for use of particular terminologies (or combinations of terminologies). The first of these has already been identified as described below in WP2.
- Track common issues arising from guidance on individual terminologies and seek to harmonize guidance in relation to similar or related issues.
- Make coherent the class codes and the codes in the back-bone classes so they are coherent
- Move content out of domain into the realm (Historically confused domain and value sets)
WP2: A guide on use of SNOMED Clinical Terms (SNOMED CT) concepts in the HL7 Version 3 communication standards.
- The purpose of this guide is to ensure that HL7 Version 3 standards achieve their stated goal of semantic interoperability when used to communicate clinical information that is represented using concepts from SNOMED CT.
- The guide will take account of:
- The SNOMED CT concept model including those elements concerned with the representation of context.
- The structure and semantics of the HL7 Reference Information Model (RIM).
- Gaps in or between these models will be identified and referred to the relevant or-ganization or work group.
- The guide will identify options for use of SNOMED CT concepts, in both pre and post-coordinated forms in different attributes of HL7 RIM classes.
- The primary focus will be on classes used in the HL7 Clinical Statement pattern.
- The advantages and disadvantages of each option will be identified and recommendations will be made on which option (or options) should be used to provide for the greatest level of semantic interoperability.
- In cases where alternative options are recommended advice will be included on mapping between them.
- The guide will be developed by a consensus process involving all interested parties. In particular the work will involve:
- The HL7 Project of Clinical Statement patterns.
- March through choice-boxes, as foci of activity
- The SNOMED International - Concept Model Working Group.
- Vendors and providers actively implementing HL7 Version 3 with SNOMED CT.
- The guide will be submitted for ballot as an HL7 informative document with the objective that it be published as part of the HL7 Version 3 standard to assist consistent implementation.
- Moves seamlessly into projects and publishing
- Examples of problems solved using the methods (see UK products)
Formal Relationships With Other HL7 Groups
The Vocabulary Technical Committee sponsors this project. Relations are established to
- Patient Care, Orders and Observations and Structured Documents in relation to their joint Clinical Statement pattern project; Other indirect relations though common interest in Clinical Statements should be established with
Formal Relationship With Groups Outside of HL7
SNOMED International (note: College of American Pathologists is an ANSI accredited SDO). The general work plan for the special project will be as follows:
- Create the set of possible models for given exemplary cases involving the HL7 RIM and SNOMED CT in the spreadsheet as demonstrated by Bob Dolin
- Stan Huff will create some examples of how the same information can be shown in XML RIM instances
- Each model will be rated as correct or incorrect
- The rationale for why a given model is incorrect will be given
- Models that are isomorphic (have the same information content and that can be converted from one to the other) will be identified
- The translations will be documented
- Optional: One model will be designated as preferred for data exchange and as the basis for authoring decision logic
- A rationale will be given about why a particular model was preferred
- The examples and other associated information will be organized into a document that will be balloted