HL7 Messaging Standards and Clinical Data Exchange

HL7 messaging standards are the family of specifications from HL7 International that define how clinical and administrative events are packaged and exchanged between health information systems. HL7 version 2, the most widely deployed, sends event-driven messages such as patient admissions, laboratory orders, and results between systems; HL7 version 3 and the Clinical Document Architecture add a formal information model and structured clinical documents.

Definition

HL7 messaging standards are application-layer specifications that define the structure, content, and trigger events of messages and documents exchanged between healthcare information systems, so that clinical and administrative data can be communicated between independently developed applications.

Scope

This entry covers HL7 version 2 trigger-event messaging, the HL7 version 3 Reference Information Model, and the Clinical Document Architecture for structured documents. It treats these as data-exchange standards and a methodological topic in informatics; it does not give implementation or procurement guidance and does not address FHIR, which is covered in a separate entry.

Core questions

• How does an HL7 v2 message represent a clinical event such as an admission or a lab result?
• What did HL7 v3 and the Reference Information Model try to add over v2?
• What is the Clinical Document Architecture and how does it differ from messaging?
• Why is HL7 v2 still dominant despite its known limitations?

Key concepts

• Trigger events and message types
• Segments, fields, and delimiters (pipe-and-hat encoding)
• ADT (admission, discharge, transfer) and ORU (observation result) messages
• Reference Information Model (RIM) in HL7 v3
• Clinical Document Architecture (CDA)
• Document persistence, attestation, and human readability
• Backward compatibility and optionality

Mechanisms

In HL7 version 2 a real-world trigger event (for example a patient admission or a finalised laboratory result) generates a message built from ordered segments, each segment carrying fields separated by delimiter characters. A receiving system parses the segments to update its own records. HL7 version 3 replaced this with a model-driven approach in which messages are derived from the Reference Information Model, an object model of acts, entities, roles, and participations, expressed in XML. The Clinical Document Architecture, built on the version 3 model, specifies a persistent, attestable clinical document with both a machine-readable structured body and a human-readable rendering, so that the same document can be processed and displayed reliably.

Clinical relevance

HL7 messaging underlies routine flows such as registration, order entry, and result reporting between hospital systems, and CDA documents are used for discharge summaries and referral letters. This entry explains how these exchanges are structured; it is reference material about the standards and is not guidance for configuring interfaces or for clinical decision-making.

Evidence & guidelines

HL7 version 2, version 3, and the Clinical Document Architecture are normative standards maintained by HL7 International through a balloting process. Dolin et al. (2006) is the authoritative description of CDA Release 2, and Benson and Grieve's textbook provides a consolidated account of the HL7 v2 and v3 standards and their relationship to terminology.

History

HL7 was founded in 1987 to standardise interfaces between hospital information systems, and HL7 version 2 evolved incrementally through the 1990s and 2000s into the de facto standard for clinical messaging. HL7 version 3, begun in the late 1990s, introduced the Reference Information Model and a more rigorous but heavier methodology; the Clinical Document Architecture, released in stages from 2000, became its most widely adopted product, with Release 2 published in 2005-2006.

Debates

Did the HL7 v3 / RIM approach deliver on its promise?

HL7 v3 aimed for semantic rigour through the Reference Information Model but was criticised as complex and hard to implement; v2 remained dominant, and CDA became the most successful v3-based product, prompting the later, lighter-weight FHIR effort.

Key figures

• Robert Dolin
• Liora Alschuler
• Amnon Shabo
• W. Edward Hammond
• Tim Benson

Seminal works

• dolin-2006
• benson-grieve-2021

Frequently asked questions

What is an ADT message in HL7 v2?

ADT stands for admission, discharge, and transfer; an ADT message communicates patient-movement and registration events between systems, and it is one of the most common HL7 v2 message types in routine hospital operations.

Is the Clinical Document Architecture the same as a messaging standard?

No. CDA specifies a persistent, attestable clinical document that can be exchanged and displayed, rather than an event-driven message; it is built on the HL7 v3 information model and complements, rather than replaces, v2 messaging.