Healthcare interface engine

Move ADT feeds, orders and other clinical messages between medical, business and IT systems.

Get started

Route your first HL7 feed end to end - destinations picked in the Dashboard, with no code, or a routing service of your own, in under five minutes.

HL7 v2 tutorial

Move clinical messages

Receive ADT, orders and results HL7 v2 messages arrive over MLLP or REST and reach your services as typed Python objects. Route by sender and message type Channels select on sending application, facility, message type and trigger event, with catch-all channels. Send and get acknowledged Send HL7 v2 over MLLP with TLS, acknowledgment timeouts and retry advice on every result. Acknowledgments AA, AE and AR in one lookup - what each code means and what the ERR segment contains. Handle non-compliant senders Every repair the platform applies to malformed messages, when it fires and how to see that it fired. Go-live runbook Take an interface live - parallel run, message-count reconciliation and a tested rollback path.

AI and MCP

AI in clinical interfaces Agents calling your services and your services calling models, in one governed layer. Expose services as MCP Let AI applications use existing Zato services under the access controls you define. Calling LLMs from services Invoke a model from a clinical service in one line of Python.

Work with HL7 v2 in Python

HL7 v2 in Python Everything for HL7 v2 messages in Python code - parsing, typed access, validation and serialization. Parsing and serialization Parse any HL7 v2 message with one call - and turn it back into ER7, dicts or JSON. Field access Read and write any field by name, wire position or path string such as PID.5.1. Validation Check required fields and datatypes, with every problem reported at once.

FHIR

FHIR connections Connect to FHIR servers as a client and work with clinical data through self.fhir in services. Resources Read, create and update typed FHIR R4 resources such as Patient and Observation. Searches and bundles Search FHIR servers with pagination and post transaction bundles in one call. Security and SMART on FHIR Basic Auth, OAuth, SMART on FHIR Backend Services and mutual TLS, per connection.

Convert HL7 v2 to FHIR

One-call conversion msg.to_fhir() turns ADT, ORU, ORM and other messages into FHIR R4 transaction bundles. Per-segment mappings What each segment becomes - PID to Patient, PV1 to Encounter, OBX to Observation, and more. Code mappings and warnings Customize code maps and identifier systems - conversion warnings surface, nothing is dropped silently. Z-segments Custom Z-segments are preserved as FHIR resources instead of disappearing in conversion. Sending bundles Post converted bundles to FHIR servers through outgoing connections.

EDIFACT

EDIFACT overview Parse EDIFACT interchanges into typed Python objects and serialize them back byte for byte. Dialects Dutch healthcare profiles - MEDLAB lab results, MEDVRI doctor-to-doctor and more - as complete examples. Transports EDIFACT rides on file drops, mailboxes, email and REST - arrival is a file event, not an MLLP ACK.

Operate and troubleshoot

The audit log in clinical interfaces Every message with its acknowledgment, searchable by patient identifier - the first place to look. Troubleshooting by symptom Feed is silent, sender gets AE, message accepted but nothing happened - causes and fixes per symptom. Audit log reference Everything the audit log records, its storage, retention and configuration, source by source. Views and search HL7 rendered as a tree beside the raw wire form, with a flow diagram of everything one message touched. Resubmit failed messages Replay failures without double-sending - transient errors retry, content errors need a fix first. Downtime and recovery What happens while an interface is off and how deduplication protects reprocessing on catch-up. Alerting Know when an interface goes down or falls silent, and what to do with the alert.

Mandates by land

IHE, TEFCA and eHealth Exchange XDS.b and XCA document exchange with XUA SAML assertions, underlying the US health networks. CDC immunization registries VXU submissions and QBP queries over the CDC-specified SOAP transport. NHS Spine HL7 v3 over ebXML, MESH and NHS FHIR APIs for integrations in England. Norwegian Helsenett Per-recipient signing and encryption for messages on the Norwegian health network. Dutch healthcare EDIFACT The Dutch healthcare profiles - MEDLAB lab results and MEDVRI doctor-to-doctor messages. CMS-0057-F prior authorization The US payer FHIR APIs for prior authorization, with their compliance dates. EHDS The European Health Data Space obligations for integration teams, staged and dated. gematik ISiK The FHIR modules German hospitals are required to expose, module by module. NHS FHIR NHS FHIR APIs in the UK and how to connect to them from Python.