HL7 v2 (HL7 Version 2)

standard organization technical interoperabilityhealthcarefhir
Source: HL7 System: http://terminology.hl7.org/CodeSystem/v2-tables Code: HL7 v2 Reviewed: 14/12/2025 License: CC-BY-4.0

HL7 v2 (HL7 Version 2)

One-sentence definition: HL7 v2 is the healthcare messaging standard that has connected hospital systems since the late 1980s, using pipe-delimited text messages to exchange patient admissions, lab results, orders, and clinical data in near-real-time between EHRs, labs, and ancillary systems.

Full Definition

HL7 v2 was designed to solve a specific hospital problem: how to automatically notify other systems when something happens to a patient. When a patient is admitted (ADT message), when a lab result is ready (ORU message), when a physician places an order (ORM message) — v2 defines structured text messages for each of these events, transmitted over TCP/IP connections using the MLLP transport protocol.

The format is a flat, pipe-delimited text structure: each message consists of segments (lines of text beginning with a 3-letter code like MSH, PID, OBX), each segment contains fields separated by |, and each field may contain sub-components separated by ^. While this looks primitive compared to modern XML or JSON, it is extremely well-understood, widely implemented, and still the primary integration mechanism in most hospital environments worldwide.

HL7 v2 first appeared in 1987 and has evolved through versions 2.1 through 2.9, with 2.3, 2.4, and 2.5.1 being the most widely deployed. The standard is deliberately loose — it provides a common structure but allows many fields to be optional or locally defined, which means v2 implementations are never truly plug-and-play and almost always require custom mapping at each integration site.

Context and Usage

Where This Term Appears

  • Hospital interface engines: Systems like Rhapsody, Mirth Connect, and Ensemble are built to parse and route HL7 v2 messages between hospital systems
  • Lab integrations: Laboratory Information Systems (LIS) send ORU messages to EHRs for every resulted lab test
  • ADT feeds: Admissions, discharge, and transfer events flow as ADT messages from registration systems to downstream consumers
  • FHIR migration discussions: “Moving from v2 to FHIR” describes replacing or augmenting v2 interfaces with FHIR APIs

Common Usage Examples

In conversation: “The lab results come in as ORU^R01 messages over MLLP — we parse the OBX segments and map the LOINC codes to our internal codes before storing.”

In documentation: “The ADT feed provides real-time patient movement events as HL7 v2.5.1 messages via the HL7 listener on port 2575.”

Relationship to Other Terms

  • HL7 — the standards body that created and maintains HL7 v2
  • FHIR — HL7’s modern successor standard; many organisations run both in parallel

Common Misconceptions

Misconception: HL7 v2 Is Being Replaced by FHIR Everywhere

  • Incorrect belief: FHIR is replacing HL7 v2, so existing v2 interfaces will soon be retired.
  • Reality: HL7 v2 remains the dominant real-time messaging standard in hospital internal integrations. FHIR is being adopted for patient access APIs, payer-provider exchange, and new-build integrations, but the vast majority of lab, ADT, and order interfaces in production today are HL7 v2 and will remain so for many years.
  • Why it matters: Teams building integrations with hospitals need to plan for v2 interfaces alongside FHIR APIs — they are complementary, not competitive, in most organizations’ integration strategies.

Misconception: HL7 v2 and FHIR Are Incompatible

  • Incorrect belief: Because v2 and FHIR use different formats and paradigms, data cannot flow between them.
  • Reality: Many integration platforms support bidirectional translation between v2 messages and FHIR resources. FHIR’s concept mapping guidance and HL7’s v2-to-FHIR mapping project provide systematic translation rules for common message types.
  • Why it matters: Hybrid architectures — where v2 handles internal hospital messaging and FHIR handles external API access — are the norm, not the exception.

Why HL7 v2 Matters

Understanding HL7 v2 is unavoidable for anyone working with US hospital data. Lab results, medication orders, patient demographics, and clinical documents that originate in EHRs arrive downstream via v2 interfaces. FHIR-based systems that need to ingest real hospital data must be able to consume or translate from v2 feeds, at least until those interfaces are replaced.

Cross-References

  • HL7 — the standards body that created and maintains HL7 v2
  • FHIR — HL7’s modern successor standard; many organisations run both in parallel

Last reviewed: December 14, 2025 Definition authority: HL7 International Content status: Canonical reference