HL7 v2 and other healthcare message formats
MessageFoundry parses, validates, routes, and transforms HL7 v2 messages. The same healthcare interface engine also connects FHIR, X12/EDI, and DICOM. It is open source, self-hosted, and written in Python.
MessageFoundry as an HL7 interface engine
Exchange HL7 v2 messages between clinical systems such as labs, radiology, pharmacy, and billing. Configure connections and write routing and transform logic in Python.
An open-source HL7 interface engine
MessageFoundry is AGPL-licensed, with no per-interface license fees. Run it on your servers or in your private cloud. The project started in May 2026 and is in Early Access. Read about self-hosting →
HL7 v2 support
HL7 v2 capabilities include:
- 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, …).
Other healthcare message formats
Use the same engine and Python configuration for these formats and transports:
- 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.
Keep HL7 and other healthcare interfaces in the same version-controlled Python configuration. Compare the supported protocols and tools →
Related guides
Frequently asked questions
Is MessageFoundry an HL7 interface engine?
Yes. It parses, validates, routes, and transforms HL7 v2 messages over MLLP. The same engine also connects FHIR, X12/EDI, and DICOM.
What does MessageFoundry support besides HL7 v2?
It supports FHIR, X12/EDI, DICOM, and JSON and XML payloads. Transports include MLLP, TCP, HTTP/REST, SOAP, files, SFTP/FTP, and databases.
Is MessageFoundry an HL7 interface engine or a healthcare interface engine?
Both terms fit. MessageFoundry handles HL7 v2 and other healthcare formats, including FHIR, X12, and DICOM. You configure them in the same self-hosted Python engine.
What is an HL7 interface engine?
An HL7 interface engine receives, routes, transforms, and validates messages between clinical systems. For example, it can send admission or lab-result messages to a lab or billing system.