This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Vocabulary"
Jump to navigation
Jump to search
| Line 67: | Line 67: | ||
*[[Evaluation of IHTSDO Workbench Information Model to the HL7 Vocabulary MIF Format]] | *[[Evaluation of IHTSDO Workbench Information Model to the HL7 Vocabulary MIF Format]] | ||
*[[Value Set Definition Standard Project]] | *[[Value Set Definition Standard Project]] | ||
| + | *[[Value Set Expansion Standard Project]] | ||
*[[Vocabulary Quality Assurance Project]] | *[[Vocabulary Quality Assurance Project]] | ||
*[http://www.hl7.org/documentcenter/ballots/2009may/downloads/V3_CTS_R2_DSTU_2009OCT.pdf Common Terminology Services - Release 2] (DSTU) | *[http://www.hl7.org/documentcenter/ballots/2009may/downloads/V3_CTS_R2_DSTU_2009OCT.pdf Common Terminology Services - Release 2] (DSTU) | ||
Revision as of 22:30, 19 January 2017
The Vocab TC identifies, organizes and maintains coded vocabulary terms used in HL7 messages, to enable the exchange of clinical data and information so that sending and receiving systems have a shared, well defined, and unambiguous knowledge of the meaning of the data transferred.
Contents
Vocabulary WG Agendas
HL7 Vocabulary TC Infrastructure and Assets
Documents
- Compositional Expressions in HL7 Value Sets
- HL7 Oid Symposium (INM and VOCAB)
- Vocabulary/TermInfo Compositional Expression
- NLM Contract
- 16 Points Document
- Vocabulary TC Decisions Document
- Domain and Value Set Definitions and Binding - "rescued" from valuesets.org
- Vocabulary Portion of Core Principles
- ISO TR 12310 Best Practices for Terminology Conformance Draft
- Planning for Core Principles R3
Policy statements
- Policy on case sensitivity of codes
- Policy on OIDs for SNOMED CT Extensions
- Policy for Intensional Value Set Definitions based on LOINC
- HL7 proposed guidance on use of displayName(V3 CD) and Text (V2.x CNE,CWE)
- CWE, CNE
Vocabulary
- HL7 Vocabulary Technical Correction Reporting
- Value Set binding
- Revise existing Foundation Vocabulary Introduction
- Revise existing Background V3 Guide Vocabulary Section
- Revise existing Vocabulary section in HDF
- Discussion of Act.text vs. Act.code.originalText
- Marital Status Code Definitions
- Code Conformance Discussion
- Technical_Correction_of_Value_Sets_-_February_2009
- Concept Domain Naming Conventions
- Post-coordination Value Set Examples
- Special Vocabulary Considerations for Harmonization Processes
- Value Set MIF 2.2 Definition
Vocabulary Tooling
Specifications
HL7 Common Terminology Services (CTS).
IHTSDO / HL7 Collaboration
Projects
- HL7 proposed content change requests for SNOMED-CT to IHTSDO
- Evaluation of IHTSDO Workbench Information Model to the HL7 Vocabulary MIF Format
- Value Set Definition Standard Project
- Value Set Expansion Standard Project
- Vocabulary Quality Assurance Project
- Common Terminology Services - Release 2 (DSTU)
- Common Terminology Services - Release 2 (Normative)
- Binding Syntax for Implementation Guides (joint with CGIT)
- HL7 proposed policy for submission of non-US english vocabulary
- TermInfo Project
- Hot Topics being discussed:
- How to represent negation.
- Considering Changes in ASSERTION
- Discuss use of nesting in Problem Concern and Allergy Concern Acts
- Post-coordination
- Reporting Negative Assertions, ie No Growth, No Problems, No Results
- Use of ASSERTION pattern
- Use of NULL flavors
- Terminology binding
- Hot Topics being discussed:
- HL7 Terminology Authority
- v2 code table project
- HL7 Vocabulary Facilitator Roles, Responsibilities and Tasks
- HL7 Vocabulary Glossary
- LOINC Clinical Document Ontology (joint with Structured Documents)
