×

To enhance security, Multi-Factor Authentication (MFA) is mandatory for all HL7 users. More information

Section 1e: Version 3 (V3)
Section 3: Implementation Guides

HL7 Implementation Guidance for Unique Object Identifiers (OIDs), Release 1

DESCRIPTION

The Object Identifier Definition (OID) informational guide has been retired and will not be maintained moving forward. The content of this informative guide can still be accessed for OID information.

The purpose of the HL7 Implementation Guidance for Unique Object Identifiers (OIDs), Release 1 document is to describe how to manage the various values needed to provide global uniqueness for identifiers used for patients, documents, providers and other entities when appearing in clinical documents or messages. 

ALTERNATIVE NAMES

HL7 Implementation Guidance for Unique Object Identifiers (OIDs), Release 1 may also go by the following names or acronyms:

OID,OIDs

TARGETS

  • Healthcare Institutions (hospitals, long term care, home care, mental health)
  • EHR system vendors and implementers
  • Dictation / transcription systems vendors and implementers
  • Local, regional, and national health information exchange networks

BENEFITS

  • Provides understanding how to obtain and manage values used to label the different identifiers in the Clinical Document or within the V3 message
  • Assist organizations to develop an OID maintenance strategy where none already exists

IMPLEMENTATIONS/CASE STUDIES

DEVELOPMENT BACKGROUND

This guide is not intended to replace existing organizational strategies already in use for OID maintenance. This document approaches the assignment of OIDs to a V3 document or message by first describing how healthcare organizations can acquire an OID that they may use as a root OID.  Secondly it describes how that OID can then be used to generate new OIDs which can be used to label the different identifiers used within clinical documents or messages produced by that organization.  Although this document primarily focuses on examples drawn from CDA documents, the same approach would also apply to V3 messages.

 

This document is intended to help organizations develop processes to manage OIDs.  When organizational structures change, the processes used to manage these OIDs may also need to change.  This document does not describe a transition path between different processes.  Organizations should consider possible transition paths when selecting a strategy for managing OIDs.

RELATED DOCUMENTS

HL7 Implementation Guidance for Unique Object Identifiers (OIDs), Release 1

(Download) (316 KB)

ADDITIONAL DETAILS

OIDs are used in HL7 documents and messages to add global uniqueness to identifiers used within the document.  OIDs are also used to identify the vocabulary terminology systems used in documents and messages.  The term OID is short for Object Identifier, and is specified in clause 28 of the ISO/IEC 8824:1990(E) standard describing the ASN-1 notation. 

BALLOT TYPE

  • Informative

STATUS DATE

2024-12-12

RESPONSIBLE WORK GROUP

Payer/Provider Information Exchange

PRODUCT TYPE

  • Methodology Specifications

STAKEHOLDER

  • Healthcare Institutions

FAMILY

  • V3

CURRENT STATE

  • Retired

REALM

  • Universal