HL7 stands for Health Level Seven. It is published by the organisation HL7 International. When people in a hospital talk about “HL7”, they usually mean HL7 version 2, the most widespread messaging standard between the HIS (hospital information system) and subsystems.
How HL7 v2 works
HL7 v2 exchanges messages that describe an event: a patient is admitted, an examination is requested, a finding is available. Each message consists of segments, that is, lines with a fixed meaning whose fields are separated by vertical bars.
| Segment | Content |
|---|---|
| MSH | Message header: sender, recipient, message type |
| PID | Patient data |
| PV1 | Case and stay data |
| ORC, OBR | Order |
| OBX | Individual result, e.g. a reading |
Typical message types are ADT for admission and master data, ORM or OML for orders and ORU for results. Because the standard leaves room for interpretation, each interface is agreed between the parties in a specification.
HL7 v2, v3 and FHIR
Alongside v2, there is HL7 v3 with the document format CDA, which has caught on less in everyday hospital use. The most recent standard from the same organisation is FHIR. In practice, v2 and FHIR often run side by side.
HL7 in the Datico® Life Hub
The HIS Connector supports HL7 v2 and v3. It receives orders from the HIS and returns readings and findings. How this works in a project is described in the guide HIS interface.
Frequently asked questions
What is the difference between HL7 and FHIR?
HL7 v2 sends messages about events, usually through a communication server. FHIR describes data as individual resources that are retrieved via web interfaces. Both come from HL7 International.
What is a communication server?
A system in the hospital that distributes HL7 messages between the HIS and subsystems and translates them where necessary.