HL7 v2.x Integration
HL7 v2.x is the most widely deployed messaging standard in hospital environments. It connects departmental systems — LIS, RIS, PACS, pharmacy, HIS, EMR, EHR — and drives the real-time workflows that clinical operations depend on: patient admissions and discharges, order placement, result notifications, medication dispensing. Despite being decades old, it remains the integration backbone of most hospitals. We design, implement, test, and audit HL7 v2 interfaces so they work correctly and hold up over time.
Where HL7 v2 integrations fail
HL7 v2 gives implementers significant freedom in how they use the standard. That flexibility is also the source of most integration problems.
Systems that use HL7 v2 differently
HL7 v2 allows many optional fields, local extensions, and implementation-specific conventions. Two systems can each implement HL7 v2 correctly according to their own interpretation and still be unable to exchange data without a custom adapter. Without a shared interface specification, every connection is a one-off project.
Integrations nobody understands
Many HL7 v2 integrations in production were built by people who have since left the organization. The message flows are undocumented, the mapping rules live only in the integration engine configuration, and nobody is confident about what triggers a message or how errors are handled. Any change to either connected system becomes a risk.
Silent failures in production
HL7 v2 interfaces can appear to work while silently dropping or misrouting messages. Missing acknowledgements, unhandled error conditions, and message queue backlogs often go undetected until a clinician notices that a lab result never arrived or a patient was not properly admitted in a downstream system.
How we help
We work with hospitals and software vendors at any stage of an HL7 v2 project — from designing new integrations to auditing and fixing existing ones.
Requirements Analysis
We establish what workflows need to be integrated, which systems are involved on each side, what events trigger messages, what data must be carried in each message, and what the expected behavior is for errors and edge cases. This analysis produces a clear integration scope that all parties can agree on before any design or development begins.
Integration Design
We design the HL7 v2 interface specification: which message types and trigger events to use (ADT, ORM, ORU, RDE, MDM, and others), the acknowledgement model, the transport protocol (MLLP, file, API), and the sequencing and error handling rules. The interface specification is the contract between sending and receiving systems — documented precisely enough that both sides can implement to it independently.
Data Mapping
We map the internal data models of each system to the HL7 v2 message fields: which source field populates which segment and component, how coded values are translated between local code tables and HL7 tables, how identifiers are managed across systems, and how missing or optional data is handled. Mapping rules are documented formally so they can be implemented, reviewed, and updated as system models evolve.
Implementation
We implement HL7 v2 interfaces using integration engines and middleware platforms commonly deployed in hospital environments. Implementation includes message construction and parsing, routing logic, acknowledgement handling, error queues, and logging. We deliver documented, version-controlled channel configurations that your operations team can manage.
Testing and QA
We design and execute test plans that cover the full message lifecycle: valid messages, malformed messages, edge cases, duplicate events, and error recovery. We use protocol-level tools to inspect what is actually sent and received on the wire — not just what the integration engine reports — and validate that acknowledgements, error flags, and data values match the specification.
Integration Audit
For existing HL7 v2 integrations, we audit what is running in production: capture and analyze live message traffic, reconstruct the interface specification from the actual implementation, identify deviations from HL7 v2 standards, undocumented behaviors, and failure modes that are not being handled. We deliver an audit report with prioritized findings and recommendations for each issue.
Do you have any questions?
Let us know how we can help you.