Table 0301: Universal ID Type
HL7-defined table of codes specifying the type of UID (Universal Identifier). Open Issue: Table 0301 has a mix of class and instance identifiers for namespaces, which is improper. The values for instances. such as CLIA, CLIP, CAP, and NPI. These were added for pragmatic issues related to older datatypes that were universally bound tand should not be here but are needed for implementation pragmatics. These should be annotated in Comment or Usage Notes that these are not universal ID types really.
- Type
- HL7-defined
- Codes
- 19
- Introduced
- HL7 v2.3
- Used in
- HD.3, EI.4
- FHIR code system
http://terminology.hl7.org/CodeSystem/v2-0301- THO code system
http://terminology.hl7.org/CodeSystem/v2-0301- OID
2.16.840.1.113883.18.186
HL7-defined: The standard fixes the values. PipeHat flags codes outside this list as warnings.
Codes
| Code | Meaning | Definition | FHIR code | Status |
|---|---|---|---|---|
CAP | College of American Pathologist Accreditation Number | Allows for the ability to designate organization identifier as a "CAP" assigned number (for labs) | — | N |
CLIA | Clinical Laboratory Improvement Amendments | Clinical Laboratory Improvement Amendments. Allows for the ability to designate organization identifier as a "CLIA" assigned number (for labs) | CLIA | |
CLIP | Clinical laboratory Improvement Program | Clinical laboratory Improvement Program. Allows for the ability to designate organization identifier as a "CLIP" assigned number (for labs). Used by US Department of Defense. | CLIP | |
DNS | Domain Name System | An Internet host name, in accordance with RFC 1035; or an IP address. Either in ASCII or as integers, with periods between components ("dotted" notation). | DNS | |
EUI64 | IEEE 64-bit Extended Unique Identifier | IEEE 64-bit Extended Unique Identifier is comprised of a 24-bit company identifier and a 40-bit instance identifier. The value shall be formatted as 16 ASCII HEX digits, for example, “AABBCC1122334455”. The 24-bit company identifier, formally known as Organizationally Unique Identifier (OUI-24), is guaranteed to be globally unique. The 40-bit extensions are assigned by manufacturers. This identifier is often used in equipment interfaces (e.g., “MAC” address format for IPv4 & IPv6). [See http://standards.ieee.org/regauth/oui/tutorials/EUI64.html for a detailed explanation of the format.] | EUI64 | |
GUID | globally unique identifier | Same as UUID. | GUID | |
HCD | CEN Healthcare Coding Identifier | The CEN Healthcare Coding Scheme Designator | HCD | |
HL7 | HL7 registration schemes | HL7 | ||
ISO | ISO Object Identifier | An International Standards Organization Object Identifier (OID), in accordance with ISO/IEC 8824. Formatted as decimal digits separated by periods; recommended limit of 64 characters | ISO | |
L | Local | These are reserved for locally defined coding schemes. | — | |
L,M,N | Local | These are reserved for locally defined coding schemes. | L,M,N | deprecated |
M | Local | These are reserved for locally defined coding schemes. | — | |
N | Local | These are reserved for locally defined coding schemes. | — | |
NPI | US National Provider Identifier | Allows for the ability to designate organization identifier as a "NPI" assigned number (lab, any medical provider, can be a person or an organization) | — | N |
Random | Random | Usually a base64 encoded string of random bits.<p>Note: Random IDs are typically used for instance identifiers, rather than an identifier of an Assigning Authority that issues instance identifiers | Random | |
URI | Uniform Resource Identifier | URI | ||
UUID | Universal Unique Identifier | The DCE Universal Unique Identifier, in accordance with RFC 4122. Recommended format is 32 hexadecimal digits separated by hyphens, in the digit grouping 8-4-4-4-12 | UUID | |
x400 | X.400 MHS identifier | An X.400 MHS identifier. Recommended format is in accordance with RFC 1649 | x400 | |
x500 | X500 directory Name | An X.500 directory name | x500 |
FHIR codes from the HL7 v2-to-FHIR concept map UniversalIDType (unconditional mappings only).
Where it's used
| Element | Name | FHIR (v2-to-FHIR mapping) |
|---|---|---|
HD.3 | Universal ID Type | — |
EI.4 | Universal ID Type | — |
Elements with a dot (such as CX.5) are data type components, used wherever that data type appears.
Source: HL7 Terminology (THO) 7.4.0 and the HL7 v2-to-FHIR Implementation Guide 1.0.0, published by HL7 International under CC0. Check your trading partner's specification for the values they actually send.