Is MessageFoundry an HL7 integration engine?

Yes — and more. MessageFoundry has deep HL7 v2 support: parsing, tiered validation, routing, and transformation over MLLP. It is also a broader healthcare integration engine that connects FHIR, X12/EDI, and DICOM across many transports — so one engine handles HL7 and everything around it.

What does MessageFoundry support besides HL7 v2?

FHIR (REST), X12/EDI, and DICOM, plus JSON and XML payloads — over MLLP, TCP, HTTP/REST, SOAP, files, SFTP/FTP, and databases. It connects a wide range of healthcare protocols and message types from a single, self-hosted engine.

Is MessageFoundry an HL7 interface engine or a healthcare integration engine?

Both terms fit. MessageFoundry handles classic HL7 v2 interfaces and the broader integration work — FHIR, X12, DICOM — in one open-source, self-hosted, Python-native engine, so you don't need a separate tool per standard.

HL7 — and well beyond

More than just an HL7 integration engine

Yes, MessageFoundry is a capable HL7 integration engine — with deep HL7 v2 parsing, validation, routing, and transformation. But it's a full healthcare integration engine: the same engine connects FHIR, X12/EDI, and DICOM across a wide range of transports — open-source, self-hosted, and written in Python.

See all the formats Get started →

A capable HL7 v2 engine

If you came looking for an HL7 interface engine, you're in the right place. MessageFoundry does the classic HL7 v2 work and does it well:

Receive and send over MLLP (with MLLP-over-TLS), TCP, and files.
Tiered validation — tolerant peek, strict structural, and cross-field business checks.
Route, filter, and transform in plain Python, addressed by HL7 path (MSH-9.1, OBR-25, …).

HL7 over MLLP in Python →

…and a broad healthcare integration engine

The same engine, the same Python config, reaches well past HL7 v2:

FHIR — deliver resources and Bundles to a FHIR server over REST (R4B/R5/STU3).
X12/EDI and DICOM imaging alongside HL7 — no separate tool per standard.
Many transports — HTTP/REST, SOAP, SFTP/FTP, and databases, plus JSON and XML payloads.

HL7 v2 to FHIR in Python →

One engine, every interface. The reason "HL7 integration engine" undersells it: healthcare integration rarely stops at HL7 v2. MessageFoundry connects a wide range of protocols and message types from a single open-source, self-hosted, Python-native engine — so HL7 and everything around it run side by side, version-controlled like any codebase. See how that compares to legacy engines →

Explore the features Full feature list View on GitHub ↗