Supports donor management workflows. Key segments include MSH, PID, OBX, PV1. Blood bank and donor management systems exchange this to track donor eligibility, registration, and donation procedures.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'DEO^O45^DEO_O45|MSG001|P|2.9\r' \
'PID|1||MRN-10045||SMITH^JOHN||19850315|M'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birthHow to construct, send, receive, and extract fields from real-world DEO^O45 messages.
Demonstrates receiving and extracting key fields from a donor eligibility order transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'DEO^O45^DEO_O45|MSG001|P|2.9\r' \
'PID|1||MRN-10045||SMITH^JOHN||19850315|M'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birthStep-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||DEO^O45^DEO_O45|MSG00001|P|2.9'
msg = HL7Message.parse(raw)
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birthBeyond the mandatory MSH header, the required segments are: PID, OBX, PV1, OBR, OBX. 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 DEO^O45 message, in order. Groups are shown with their child segments.
| # | Segment | Usage | Repeats | Description | Group |
|---|---|---|---|---|---|
| 1 | MSH | Required | No | Message header | - |
| 2 | ARV | Optional | Yes | Access restriction | - |
| 3 | SFT | Optional | Yes | Software segment | - |
| 4 | UAC | Optional | No | User authentication credential | - |
| 5 | PID | Required | No | Patient identification | Donor |
| 6 | PRT | Optional | Yes | Participation information | Donor |
| 7 | OBX | Required | No | Observation result | Donor |
| 8 | PRT | Optional | Yes | Participation information | Donor |
| 9 | ARV | Optional | Yes | Access restriction | Donor |
| 10 | NTE | Optional | Yes | Notes and comments | Donor |
| 11 | PV1 | Required | No | Patient visit | Donor |
| 12 | PRT | Optional | Yes | Participation information | Donor |
| 13 | NTE | Optional | Yes | Notes and comments | Donor |
| 14 | OBR | Required | No | Observation request | DONATION_ORDER |
| 15 | PRT | Optional | Yes | Participation information | DONATION_ORDER |
| 16 | NTE | Optional | Yes | Notes and comments | DONATION_ORDER |
| 17 | OBX | Required | No | Observation result | DONATION_ORDER |
| 18 | PRT | Optional | Yes | Participation information | DONATION_ORDER |
| 19 | NTE | Optional | Yes | Notes and comments | DONATION_ORDER |
Get started with Zato and connect your systems in minutes.