HL7 Terminology (THO)
3.0.0 - Publication
This page is part of the HL7 Terminology (v3.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/v2-0175 |
Version: | 2.0.0 |
Name: | Hl7VSMasterFileIdentifierCode |
Title: | hl7VS-masterFileIdentifierCode |
Status: | Active as of 12/1/19 |
Definition: | Concepts which are represented by codes identifying HL7Versions 2.x Master Files. |
Publisher: | HL7, Inc |
Copyright: | Copyright HL7. Licensed under creative commons public domain |
OID: | 2.16.840.1.113883.21.103 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/v2-0175
This value set contains 26 concepts
Expansion based on masterFileIdentifierCodes v2.5.0 (CodeSystem)
All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v2-0175
Code | Display | Definition |
OM1 | Observation text master file segments (e.g., Lab) | Observation text master file segments (e.g., Lab) (see Chapter 87, Appendix B): |
OM2 | Observation text master file segments (e.g., Lab) | Observation text master file segments (e.g., Lab) (see Chapter 87, Appendix B): |
OM3 | Observation text master file segments (e.g., Lab) | Observation text master file segments (e.g., Lab) (see Chapter 87, Appendix B): |
OM4 | Observation text master file segments (e.g., Lab) | Observation text master file segments (e.g., Lab) (see Chapter 87, Appendix B): |
OM5 | Observation text master file segments (e.g., Lab) | Observation text master file segments (e.g., Lab) (see Chapter 87, Appendix B): |
OM6 | Observation text master file segments (e.g., Lab) | Observation text master file segments (e.g., Lab) (see Chapter 87, Appendix B): |
CM0 | Clinical study master | Clinical study master |
CM1 | Clinical study phase master | Clinical study phase master |
CM2 | Clinical study Data Schedule Master | Clinical study Data Schedule Master |
OM1-OM6 | Observation text master file segments (e.g., Lab) | Observation text master file segments (e.g., Lab) (see Chapter 87, Appendix B): |
CDM | Charge description master file | Charge description master file |
CMA | Clinical study with phases and scheduled master file | Clinical study with phases and scheduled master file |
CMB | Clinical study without phases but with scheduled master file | Clinical study without phases but with scheduled master file |
LOC | Location master file | Location master file |
OMA | Numerical observation master file | Numerical observation master file |
OMB | Categorical observation master file | Categorical observation master file |
OMC | Observation batteries master file | Observation batteries master file |
OMD | Calculated observations master file | Calculated observations master file |
OMM | Mixed type observation master file | Mixed type observation master file |
PRA | Practitioner master file | Practitioner master file |
STF | Staff master file | Staff master file |
CLN | Clinic master file | Clinic master file |
OME | Other Observation/Service Item master file | Other Observation/Service Item master file |
INV | Inventory master file | Inventory master file |
MLCP | Medicare Limited Coverage Process | Medicare Limited Coverage Process |
MACP | Medicare Approved Coverage Process | Medicare Approved Coverage Process |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |
History
Date | Action | Author | Custodian | Comment |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |