Object Identifiers (OIDs) for coding and identification schemes are available free of charge to organisational members and above of HL7 UK. Non members may purchase OIDs for a one-off fee of £150 plus VAT. To apply for an OID, download the OID Request Form and follow the instructions.
Introduction to OIDS
HL7 uses OIDs (Object Identifiers) to identify coding schemes and identification schemes.
OIDS are strings of numbers separated by dots. Each number indicates a branch from in a tree of identifiers. The first set of branches is allocated by ISO and further levels nationally and by other organisations. Therefore OIDs can be allocated by any organisation with a unique OID root from which to allocate branches. Provided each organisation respects the need for uniqueness in its allocation of branches the resulting OID will uniquely identify an object.
The object identified by an OID could be anything. For example, HL7 allocates OIDs for message components as well as coding and identification schemes. However, for the purposes of this page we are primarily concerned with the use of OIDs for identifying two types of object:
- A coding scheme or terminology (e.g. OCS Specialty Codes, Read Codes, SNOMED CT)
- The OID goes in the codeSystem attribute of an instance of an HL7 coded datatype (CD, CE, CV) in which the code attribute is a code from the specified scheme.
- In some cases, the OID may be included as a fixed attribute in the message specification rather than with each instance.
- An external scheme of identifiers (e.g. NHS Numbers, GP Numbers, Referral Numbers)
- The OID goes in the root attribute of the instance identifier datatype (II) with the actual identifier in the extension attribute.
- In the case of instance identifier that do not refer to an external coding scheme the root may represent the entire identifier and may either be an OID or a UUID/GUID and there is no need for an extension attribute.
For a full list of the types of objects HL7 UK allocates OIDs for please consult the HL7 UK OID management policy.
A single message can use OIDs from various sources and a single scheme can be identified by more than one OID (e.g. by an OID from more than one organisation). Once issued an OID is never withdrawn and always identifies the same scheme or object.
To assist UK projects using HL7 messages that require OIDs for coding and identification schemes HL7 UK has registered OIDs for some coding and identification schemes in widespread use in the NHS.
OIDs and FHIR
OIDs are mandatory for use with HL7 Version 3, and with some IHE profiles. HL7 FHIR can still use OIDs, but it is now preferred to use more meaningful URI based identifiers. HL7 UK maintains a registry of identifier systems used with FHIR here.
OID roots for HL7 and HL7 UK
|The HL7 Branch OID is||2.16.840.1.113883|
|External Identification schemes registered with HL7||2.16.840.1.113883.4|
|Internal Coding schemes registered with HL7||2.16.840.1.113883.5|
|External Coding schemes registered with HL7||2.16.840.1.113883.6|
|The HL7 UK Branch OID is||2.16.840.1.113883.2.1|
|External Identification schemes registered with HL7 UK||2.16.840.1.1138126.96.36.199|
|External Coding schemes registered with HL7 UK||2.16.840.1.1138188.8.131.52|
HL7 UK-registered OIDs
Allocation of an OID does not imply any statement of quality about the scheme registered. The OID merely identifies the scheme. Inclusion of an OID in these lists does not imply a right to access the associated coding scheme data which in many case is associated with copyright or privacy restrictions.
- View the latest HL7 UK Registered OIDs in HTML format
- Download HL7 UK allocated OIDs in XML and .zip format
- Download the HL7 UK OID request form
Please note that OID Registration is FREE for HL7 UK members. There is a charge of £150 + VAT for non-members.
HL7 International registered OIDs relevant to the UK
Below is a selection of OIDs known to be of immediate use in the UK NHS. For a full list please go to the HL7 International OID registry. You will then be able to query the register and download PDF or XML representations as necessary.