What HL7 Is and Why It Exists

The problem HL7 solves

A modern hospital does not run on a single system. Admitting, laboratory, pharmacy, radiology, billing, and the electronic health record are frequently separate applications, often from different vendors, purchased years apart. Each must nonetheless act on the same events: when a patient is admitted, the lab needs to know who they are; when a result is finalized, the chart must show it.

Without a shared convention, every pair of systems would need a bespoke, hand-built connection, and the number of connections grows roughly with the square of the number of systems. Health Level Seven (HL7) exists to break that pattern by defining a common language for clinical and administrative data so that any conforming system can exchange information with any other ¹.

The “Level Seven” in the name refers to the seventh — application — layer of the OSI networking model. HL7 standardizes what the messages mean, not how bytes move across the wire.

What HL7 actually standardizes

HL7 is not one thing but a family of standards maintained by Health Level Seven International, a not-for-profit standards development organization ¹. The family includes:

• HL7 v2 — a lightweight, text-based messaging standard, in production use since the late 1980s and still the most widely deployed interface standard in hospitals worldwide.
• HL7 v3 / CDA — an XML-based model, most visible today as the Clinical Document Architecture used for documents like discharge summaries.
• FHIR — a modern, web-API-based standard built on REST and JSON, now the focus of most new interoperability work.

This course begins with v2 deliberately: it remains the substrate of real-world integration, and its concepts — segments, fields, trigger events — recur, renamed, in everything that followed ².

Interoperability is a spectrum, not a switch

It is tempting to treat “interoperable” as a yes/no property. In practice it is layered. Two systems can exchange a message (technical interoperability) yet disagree on what a code means (semantic interoperability). National programs such as those coordinated in the United States by the Office of the National Coordinator for Health IT push the industry up this ladder over time, which is why standards keep evolving rather than settling ³.

Keep this distinction in mind throughout: moving a message successfully is necessary but not sufficient. The next lesson opens up a real v2 message so you can see exactly what is — and is not — being communicated.