LambogeniusStep 1
Get started
What the gateway does, how to license it, and your first message.
Step 2
Configure
Routes, sources and destinations, filters and transforms, FHIR, X12 and CAQH CORE, delivery modes and acknowledgements, security, and TLS.
RoutesMap MLLP ports to HTTPS URLs, and what each request looks like.Several sources and destinationsOne route for several senders and several systems: a queue per destination, and filters on any field.FiltersThe filter syntax in full: MSH fields, segment field paths with indexes, values and wildcards, AND, OR and NOT, segment groups, and how to check a filter.TransformsGive each destination its own version of a message: rules that change fields and segments, code tables, and Liquid templates that make JSON, XML, text or another HL7 message.HL7 v2 to FHIRTurn ADT, results, orders and immunizations into FHIR R4 transaction Bundles, and send them to any FHIR server.X12 EDIClaims, remittances, eligibility and enrollment (HIPAA 5010) through the same routes, checked and acknowledged with TA1 and 999.CAQH COREReal-time eligibility, batch claims and batch results (835, 277CA, 999) with payers' and clearinghouses' CAQH CORE servers, C4.0.0 and 2.2.0.HTTP, SOAP and MLLP outReceive HL7 over HTTPS with REST or SOAP, call SOAP services, and send into MEDITECH over MLLP.Azure Service BusSend HL7 to Service Bus queues and topics, and receive it from queues and subscriptions.SFTP filesRead HL7 files from an SFTP folder, and write messages to one as single files or HL7 batches.Delivery modes and ACKsPass-through and store-and-forward, and which ACK the sender gets in each case.Security and HIPAAConsole users, roles and single sign-on, the audit trail, encryption at rest, how they map to the HIPAA Security Rule, and who may call the gateway and how it signs in to destinations.TLSMLLPS and HTTPS on both sides: client certificates, private CAs, and secrets from environment variables.
Step 3
Operate
Run it as a service, in a cluster or in the cloud, and keep an eye on it.
High availabilityRun several gateways on NATS JetStream, active/passive behind one address.DeploymentRun it as a service on Windows, Linux or macOS, or in Docker, Kubernetes, Azure or AWS.Admin consoleWatch routes and queues, pause and retry, manage dead letters, and install licenses.TroubleshootingCommon problems and how to fix them.Release notesWhat's in each version, and which platforms it runs on.
Step 4
Examples
Complete sample solutions you can run, step by step: from one route to a cluster in each cloud.
All examplesComplete, runnable sample solutions, from one MLLP route to a three-zone cluster in the cloud.MEDITECH → REST APIMLLP in, HTTPS REST out: store-and-forward through an API outage, dead letters, and pass-through.Partners → MEDITECHHTTPS REST with an API key per partner and SOAP with basic auth, into MEDITECH over MLLP.Azure Service BusMEDITECH to a Service Bus topic and from a queue, with outages on both sides, on the local emulator.Entra ID and SalesforceOnly callers with an Entra ID access token and app role get in; results go to Salesforce with the JWT bearer flow.HA cluster in DockerThree NATS JetStream nodes, two gateways and HAProxy: crashes with nothing lost, duplicated or reordered.On-premises HAThree Linux VMs with systemd, NATS over mutual TLS, and a keepalived virtual IP for MEDITECH.Azure (AKS)HL7 Edge Gateway and NATS JetStream on AKS across three zones, behind an internal Azure Load Balancer.AWS (EKS)HL7 Edge Gateway and NATS JetStream on EKS across three AZs, behind an internal NLB with /ready health checks.Google Cloud (GKE)HL7 Edge Gateway and NATS JetStream on a regional GKE cluster, behind an internal passthrough load balancer.HL7 files over SFTPA reference lab's result files into MEDITECH in order, and MEDITECH's orders out as HL7 batch files, over SFTP.One ADT feed, three systemsMEDITECH and a partner clinic into one route, out to a filtered lab API, a downstream HIS and an SFTP archive.Results to the EHR, alerts by orderA pass-through route: the lab system waits for the EHR's own ACK, and what the EHR accepted is copied to a pager and infection control by segment-group filters.One ADT feed, three shapesOne route, three destinations, each with a transform: HL7 with the lab system's own codes, JSON for a patient portal, and de-identified HL7 for research.MEDITECH to FHIRMEDITECH's ADT, orders, results and immunizations into a FHIR R4 server, one transaction per message, with MEDITECH's own codes added in one small file.Claims, remittances and eligibilityX12: claims from billing checked and acknowledged, sent to the clearinghouse in the clinic's own envelope; remittances to a revenue API as JSON; real-time eligibility with a payer's CAQH CORE server; an encrypted store, console sign-in and the audit trail.