MajwareMAJWARE
Free templateEditable7 systems6 interfaces

HL7 Interface Engine Integration Diagram

Most hospitals connect their clinical systems through an interface engine rather than point-to-point. This diagram shows the classic hub-and-spoke pattern: the EHR feeds ADT and orders into the engine, which routes, filters and transforms them for the RIS, LIS, PACS, billing system and EMPI, and carries results back.

Open & edit in Diagram Builder →Download SVG

Free, no sign-up. The builder runs in your browser; nothing is uploaded.

HL7 Interface Engine Integration Diagram: EHR / HIS, EMPI, RIS, Interface Engine, LIS, Billing, PACS
HL7 Interface Engine Integration Diagram — 7 systems and 6 labelled interfaces. Free to use in your own documentation.

What this diagram shows

Each spoke is labelled with the HL7 v2 message types it carries. Replace the systems with your own and add your channel names to the connection labels, and you have an interface inventory diagram for change control and onboarding.

Components

EHR / HIS

Source of patient registration (ADT) and clinical orders; consumer of results.

Interface engine

Receives every message over MLLP, acknowledges it, then routes, filters, maps and transforms it for each destination. Rhapsody, Cloverleaf, Mirth Connect and InterSystems HealthShare all follow this pattern.

RIS

Receives radiology orders and returns reports.

LIS

Receives lab orders (OML or ORM) and returns results (ORU).

PACS

Needs ADT updates and orders so image headers match the registered patient.

Billing

Receives charges from ancillary systems as DFT^P03.

EMPI

Maintains the enterprise patient identifier and publishes merges (A40) so every system can link duplicate records.

How the data flows

  1. Registration

    The EHR sends ADT^A04 or A01 when a patient is registered or admitted, and A08 for updates. The engine fans these out to every system that keeps a patient table.

  2. Orders

    Orders arrive as ORM^O01 (radiology) or OML^O21 (lab). The engine routes on order type and translates codes to each system’s catalogue.

  3. Results

    The RIS and LIS return ORU^R01. The engine routes them to the EHR and any other subscribers.

  4. Charges

    Ancillary systems post charges as DFT^P03, which the engine delivers to billing.

  5. Identity

    The EMPI receives ADT, detects duplicates and issues A40 merges that the engine distributes downstream.

  6. Acknowledgement

    Every hop is acknowledged with an ACK carrying MSA-1 = AA, AE or AR. The engine queues and retries until it receives one.

Interfaces in this diagram

Every connection in the diagram, ready to copy into an interface register or test plan.

#FromToProtocolDetail
1EHR / HIS (ADT · Orders)↔Interface Engine (Route · Transform)HL7ADT · ORM
2Interface Engine (Route · Transform)↔RIS (Radiology)HL7ORM · ORU
3Interface Engine (Route · Transform)↔LIS (Laboratory)HL7OML · ORU
4Interface Engine (Route · Transform)→PACS (Imaging)HL7ADT · ORM
5Interface Engine (Route · Transform)→Billing (Charges)HL7DFT^P03
6Interface Engine (Route · Transform)↔EMPI (Patient Identity)HL7ADT · A40

Design considerations

  • Keep transformations in the engine, not in the endpoints, so one change does not need two vendors.
  • Name channels consistently (for example source_destination_message) and put those names on the diagram.
  • Alert on queue depth and on time since the last message per channel — a silent interface is worse than a failing one.
  • Decide how merges (A40) and updates (A08) propagate before go-live; they cause most downstream mismatches.
  • Keep raw inbound and outbound messages for replay and audit, with a retention period that matches your policy.

Related reference

Frequently asked questions

What does an HL7 interface engine do?

It receives HL7 messages from source systems, acknowledges them, and then routes, filters, transforms and delivers them to one or more destinations, with queuing, retry, logging and monitoring. It replaces many point-to-point interfaces with one managed hub.

What is hub-and-spoke integration?

Every system connects once to a central engine (the hub) instead of to every other system. With n systems you manage n connections instead of up to n×(n−1)/2, and a new system needs only one new interface.

Which HL7 messages flow through a hospital interface engine?

Mainly ADT (A01, A04, A08, A40 and others) for patients, ORM, OML or OMI for orders, ORU for results, SIU for scheduling, MDM for documents and DFT for charges — each acknowledged with an ACK.

What port does HL7 use?

IANA registers port 2575 for HL7, but in practice HL7 v2 runs over MLLP on TCP with a port assigned per interface by the site. Record the host and port of every connection on your diagram.

Make it match your site

Rename systems, add your AE titles and message types, then export PNG, SVG or PDF — or send a colleague a share link.

Open in Diagram Builder →

More architecture templates

All 12 templates →
FHIR Integration Architecture Diagram — preview
Integration

FHIR Integration

SMART on FHIR apps and partners behind an API gateway, OAuth 2.0, and a FHIR server fed from HL7 v2.

9 systems · 6 interfaces

PACS Architecture Diagram — preview
Imaging

PACS Architecture

Modalities, RIS worklist, PACS image manager, diagnostic and web viewers, and long-term VNA archive.

7 systems · 7 interfaces

Radiology Workflow Diagram (RIS–PACS) — preview
Imaging

Radiology Workflow

End-to-end order-to-report workflow: CPOE order, worklist, acquisition, PACS, reading and reporting.

6 systems · 7 interfaces