Supports health care services invoicing workflows. Key segments include MSH. Payer and provider systems exchange this for claims processing, authorization, and payment reconciliation.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'EHC^E15^EHC_E15|MSG001|P|2.9\r' \
'IVC|INV001|20260701|1500.00|USD\r' \
'SFT|ACME^Software|v4.1|EHR System|BIN001'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
invoice_number = msg.ivc.provider_invoice_number
invoice_amount = msg.ivc.invoice_amount
vendor = msg.sft.software_vendor_organization
version = msg.sft.software_certified_version_or_release_numberHow to construct, send, receive, and extract fields from real-world EHC^E15 messages.
Demonstrates receiving and extracting key fields from a payment / remittance advice transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'EHC^E15^EHC_E15|MSG001|P|2.9\r' \
'IVC|INV001|20260701|1500.00|USD\r' \
'SFT|ACME^Software|v4.1|EHR System|BIN001'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
invoice_number = msg.ivc.provider_invoice_number
invoice_amount = msg.ivc.invoice_amount
vendor = msg.sft.software_vendor_organization
version = msg.sft.software_certified_version_or_release_numberStep-by-step guides for working with HL7 v2 in Zato.
Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.
from zato.hl7v2 import HL7Message
raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||EHC^E15^EHC_E15|MSG00001|P|2.9'
msg = HL7Message.parse(raw)
invoice_number = msg.ivc.provider_invoice_number
invoice_amount = msg.ivc.invoice_amountBeyond the mandatory MSH header, the required segments are: IPR, IVC, PSS, PSG, PSL, ADJ. Optional segments provide additional detail when available.
Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.
Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.
Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.
Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.
Segments that make up the EHC^E15 message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | SFT | Optional | Yes | Software segment | - |
| 3 | UAC | Optional | Yes | User authentication credential | - |
| 4 | IPR | Required | No | Invoice processing results | PAYMENT_REMITTANCE_DETAIL_INFO |
| 5 | IVC | Required | No | Invoice segment | PAYMENT_REMITTANCE_DETAIL_INFO |
| 6 | PSS | Required | No | Product / service section | PAYMENT_REMITTANCE_DETAIL_INFO |
| 7 | PSG | Required | No | Product / service group | PRODUCT_SERVICE_GROUP |
| 8 | PSL | Required | No | Product / service line item | PRODUCT_SERVICE_GROUP |
| 9 | ADJ | Optional | Yes | Adjustment | PRODUCT_SERVICE_GROUP |
| 10 | ADJ | Required | No | Adjustment | ADJUSTMENT_PAYEE |
| 11 | PRT | Optional | No | Participation information | ADJUSTMENT_PAYEE |
| 12 | ROL | Optional | No | Role | ADJUSTMENT_PAYEE |
Get started with Zato and connect your systems in minutes.