This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Vocabulary"
Jump to navigation
Jump to search
Frankoemig (talk | contribs) m |
Frankoemig (talk | contribs) m (codesystem versioning project added) |
||
| Line 48: | Line 48: | ||
*[[HL7 proposed content change requests for SNOMED-CT to IHTSDO]] | *[[HL7 proposed content change requests for SNOMED-CT to IHTSDO]] | ||
*[[Evaluation of IHTSDO Workbench Information Model to the HL7 Vocabulary MIF Format]] | *[[Evaluation of IHTSDO Workbench Information Model to the HL7 Vocabulary MIF Format]] | ||
| − | * | + | *[http://www.hl7.org/documentcenter/ballots/2009may/downloads/V3_CTS_R2_DSTU_2009OCT.pdf Common Terminology Services - Release 2] (DSTU) |
*[[Common Terminology Services - Release 2 (Normative)]] | *[[Common Terminology Services - Release 2 (Normative)]] | ||
*[[HL7 proposed guidance on use of displayName(V3 CD) and Text (V2.x CNE,CWE)]] | *[[HL7 proposed guidance on use of displayName(V3 CD) and Text (V2.x CNE,CWE)]] | ||
| − | * | + | *[http://wiki.hl7.org/index.php?title=Binding_Syntax Binding Syntax for Implementation Guides] (joint with [[Conformance_and_Guidance_for_Implementation/Testing|CGIT]]) |
*[[HL7 proposed policy for submission of non-US english vocabulary]] | *[[HL7 proposed policy for submission of non-US english vocabulary]] | ||
*[[Terminfo_2|Terminfo 2]] | *[[Terminfo_2|Terminfo 2]] | ||
*[[HL7 Terminology Authority]] | *[[HL7 Terminology Authority]] | ||
| + | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=874 V2 code table versioning and alignment to V3 vocabulary model] (joint with [[Conformance_and_Guidance_for_Implementation/Testing|CGIT]]) | ||
== Vocabulary Tooling == | == Vocabulary Tooling == | ||
Revision as of 08:38, 5 June 2012
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
HL7 Vocabulary TC Infrastructure and Assets
Documents
- Compositional Expressions in HL7 Value Sets
- HL7 Oid Symposium (INM and VOCAB)
- Vocabulary/Terminfo Compositional Expression Working Group
- 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
- Policy on OIDs for SNOMED CT Extensions
- ISO TR 12310 Best Practices for Terminology Conformance Draft
Vocabulary
- HL7 Vocabulary Technical Correction Reporting
- Value Set binding
- CWE, CNE
- 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
- [Vocabulary Maintenance Language And Tool]
- Concept Domain Naming Conventions
- Post-coordination Value Set Examples
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
- Common Terminology Services - Release 2 (DSTU)
- Common Terminology Services - Release 2 (Normative)
- HL7 proposed guidance on use of displayName(V3 CD) and Text (V2.x CNE,CWE)
- Binding Syntax for Implementation Guides (joint with CGIT)
- HL7 proposed policy for submission of non-US english vocabulary
- Terminfo 2
- HL7 Terminology Authority
- V2 code table versioning and alignment to V3 vocabulary model (joint with CGIT)
