Custom HL7 v2 integration development
HL7 version 2 is the messaging standard that systems within hospitals and laboratories have used for years to exchange data: patient admissions and transfers, orders and results. According to Nictiz, it is the most widely used HL7 standard in secondary and tertiary care. If your own system needs to receive or send those messages, or you want to translate them into something newer, you need an integration. Appfront builds that integration.
What is an HL7 v2 integration?
An HL7 v2 integration lets your system take part in the message traffic within a hospital or lab. HL7 Netherlands calls v2 messages the workhorse of HL7: they support the most common transactions between systems in healthcare organisations, such as patient registration and admission, placing orders, receiving results, prescriptions, scheduling and financial processing. In the Netherlands they are mainly used in hospitals, for the administrative domain and order communication. According to Nictiz, this mostly concerns exchange within a single organisation, and to a lesser extent between organisations.
A v2 message consists of segments: reusable groups of data, such as patient attributes, visit details, insurance details, orders and results. Which segments appear in a message, and in what order, is defined in the specification for that message. The messages have the familiar pipe-delimited structure, although XML is also possible. Examples from the standard are ADT_A01 for an admission or visit and ADT_A02 for a transfer in patient administration, ORM_O01 and OML_O21 for orders, ORU_R01 for results and SIU_S12 for appointments. Versions of HL7 v2 are backward compatible, and HL7 Netherlands maintains implementation guides with agreements on Dutch specifics such as the BSN (citizen service number).
We build custom because every hospital interprets the standard slightly differently: which fields are filled in, which codes they contain, which messages actually arrive. The integration reads each message, checks it against the agreements you have with the sender, processes it in your system and sends an acknowledgement back. A message that is invalid is not lost but ends up in a queue where you can see what went wrong. We agree the transport per connection, for example via MLLP, HL7's minimal lower layer protocol, or as a file. If you also want to make the data available as FHIR, we use the HL7 implementation guide that maps v2 messages, segments and data types to FHIR R4.
Receiving
Messages read and validated.
Confirmed
Every message acknowledged.
Nothing gets lost
Errors held in a queue.
How we build your HL7 v2 integration
We start with the message traffic as it is now: which systems send which messages, which fields they use and where things go wrong. Using sample messages from your own environment, we define for each message type which segments and fields the integration reads and writes, and what happens when a message deviates. We first build one message flow, for example the ADT messages, and test it with real, anonymised samples in a test environment. Orders, results or appointments follow after that. If a sending system changes version, we update the integration.
Systems, messages, bottlenecks.
Segments, fields, deviations.
Tested with your own samples.
Monitoring, and maintenance for new versions.
What an HL7 v2 integration actually does
The components below appear in almost every HL7 v2 integration. Which ones you need depends on the message flows and the systems at the other end.
Receiving
Messages read and validated.
Sending
Orders and results sent.
Confirmations
Every message acknowledged.
Queue
Rejected messages made visible.
Translation
From v2 to FHIR R4.
Log
Every message traceable.
Who we build an HL7 v2 integration for
The integration is intended for organisations that need to connect a system to the message traffic of a hospital or lab, or that want to convert v2 messages to a newer standard.
Hospitals
Departmental systems connected.
Laboratories
Orders in, results out.
Diagnostic centres
Requests and reports.
Software builders
Your package on the HIS.
Technology and integrations
This page is about message traffic using HL7 version 2, mainly within hospitals and labs. If the data then needs to connect to the national healthcare information building blocks, see the zibs integration. If your hospital works with HiX, also read about the ChipSoft integration, and for referrals from GPs to the hospital, the ZorgDomein integration. If message traffic needs to run through an intermediate layer, there is building middleware. You can read about our approach on building software.
Why choose Appfront for your HL7 v2 integration?
A result that doesn't arrive because one field was filled differently, an admission that is retyped by hand, or an integration that stalls after an update to the hospital system: all of these hit the work on the ward immediately. That is what we build around: agreements per message that you can review, acknowledgements for every message and a queue from which nothing disappears.
Assessed
Every message checked.
Visible
Deviations reported immediately.
Kept up to date
New versions handled.
Security and privacy in an HL7 v2 integration
HL7 v2 messages contain data about patients, admissions, orders and results, and that is health data. The integration only processes the segments and fields your system needs, keeps messages no longer than is necessary for checking and recovery, and records every message with time, sender and outcome.
The integration runs in a European data centre or in your own environment, with encrypted connections and storage. Because v2 messages are not encrypted by themselves, transport runs over a secure connection or an isolated network. We agree with you in advance who may view the queue and resubmit messages.
Frequently asked questions about an HL7 v2 integration
Questions that application managers, integration specialists and suppliers of hospital and lab software ask before they get started.
A messaging standard from HL7 for exchanging data between systems in healthcare institutions, such as patient admissions, orders, results, appointments and financial processing. The messages consist of segments in the so-called pipe structure.
According to Nictiz, mainly in secondary and tertiary care, and then within the institution itself, to a lesser extent between institutions. HL7 Netherlands cites the hospital environment, in particular the administrative domain and order communication.
They are message groups from the standard. ADT messages belong to patient administration, such as ADT_A01 for an admission or visit. ORM_O01 is a general order message, OML_O21 a laboratory order and ORU_R01 is used for reporting results.
HL7 v2 works with messages that are sent between systems. FHIR works with resources via a REST interface on web standards, with profiles for the Dutch situation. According to Nictiz, FHIR combines features of v2, v3 and CDA. Both can exist side by side.
Yes. HL7 publishes an implementation guide that maps HL7 v2 messages, segments, data types and vocabulary to FHIR R4. An integration can keep receiving messages and also offer the data as FHIR.
We agree this per connection with the system on the other side. Options include MLLP, HL7's Minimal Lower Layer Protocol, and file transfer, always over a secure connection.
For organisations with their own or departmental software that needs to connect to the message traffic of a hospital or lab, and for vendors who want to include that in their package. If your package already has an interface that matches your hospital's messages exactly, a custom integration is usually not needed.
Your system on HL7 v2 message traffic?
Tell us which messages your system needs to receive or send, and with which system. We'll show you how an integration handles that reliably.