Skip to content
LambogeniusDocs

HL7 Edge Gateway

Introduction

What the gateway does and when to use it.

Runs onWindows · Linux · macOS · DockerFree developer license for test traffic. Production traffic needs a paid license.

Any HL7 interface to any endpoint

Most HL7 v2 systems, MEDITECH included, exchange messages over MLLP: a TCP connection, each message wrapped in start and end block characters, and an acknowledgement (ACK) back for every message. The systems around them increasingly speak HTTPS or a message broker: REST APIs, SOAP web services, Azure Service Bus, cloud platforms such as Salesforce. The HL7 Edge Gateway sits between them. Each route takes messages from a source and delivers them to a destination, in any combination, and the sender always gets an HL7 ACK.

MEDITECH ──── MLLP/MLLPS ──▶ :7890      ─┐                      ┌─▶ https://lab.example.org/oru      (REST)
MEDITECH ──── MLLP/MLLPS ──▶ :7891      ─┤                      ├─▶ https://results.example.org/svc  (SOAP)
Order portal ─ HTTPS/REST ─▶ :8443/hl7  ─┤   HL7 Edge Gateway   ├─▶ meditech.hospital.local:6661     (MLLPS)
Partner ───── HTTPS/SOAP ──▶ :8443/svc  ─┘                      └─▶ Salesforce Apex REST             (OAuth2)
FeatureWhat you get
Sources and destinationsMLLP and MLLPS, HTTP or HTTPS with REST or SOAP, Azure Service Bus queues and topics, and HL7 files on SFTP servers, on either side of a route. Send into MEDITECH as easily as out of it. See Routes.
X12 EDI and CAQH COREClaims, remittances, eligibility and enrollment, checked and answered with 999 and TA1, and real-time and batch exchange with payers' CORE servers. See X12 EDI.
HL7 v2 to FHIRADT, results, orders and immunizations as FHIR R4 transaction Bundles, sent to Azure Health Data Services, Google Cloud, HAPI or any FHIR server. See HL7 v2 to FHIR.
Two delivery modesPass-through (ACK with the destination's answer) or store-and-forward (ACK once the message is stored, then deliver in order with retries), chosen per route.
SecurityOAuth2 / OpenID Connect tokens or API keys for callers, IP allowlists, mutual TLS, and OAuth2 or Salesforce logins to destinations. See Security.
High availabilitySeveral gateways share replicated queues in NATS JetStream, with at most one message per route in flight across the cluster, so order holds.
Admin consoleLive route state, queues and dead letters, pause and retry, cluster nodes, and license status.
Duplicate suppressionA resend with the same MSH-10 within the dedup window is acknowledged but not delivered twice.

The gateway is a single binary for Windows, Linux and macOS, and a Linux container image. It needs no runtime, and TLS doesn't depend on OpenSSL. Download it from lambogenius.com with a free account.

Sending into Azure Logic Apps?

The gateway posts to any HTTPS endpoint, including a workflow's HTTP trigger. If you want the payload as JSON with the MSH fields already parsed, or need to send MLLP from a workflow, look at the HL7 MLLP Connector for Azure Logic Apps instead.