Supports blood product processing workflows. Key segments include MSH, MSA, PID, ORC. Blood bank and transfusion management systems exchange this to track product status from order through disposition.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'BRT^O32^BRT_O32|MSG001|P|2.9\r' \
'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
'BPO|1|O+^O Positive^ABO|3|ML|300'
# .. 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_birth
product = msg.bpo.bp_universal_service_identifier
quantity = msg.bpo.bp_quantityHow to construct, send, receive, and extract fields from real-world BRT^O32 messages.
Demonstrates receiving and extracting key fields from a blood product transfusion / disposition acknowledgment transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'BRT^O32^BRT_O32|MSG001|P|2.9\r' \
'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
'BPO|1|O+^O Positive^ABO|3|ML|300'
# .. 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_birth
product = msg.bpo.bp_universal_service_identifier
quantity = msg.bpo.bp_quantityStep-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||BRT^O32^BRT_O32|MSG00001|P|2.9\rMSA|AA|MSG00001\rERR|||0|I|'
msg = HL7Message.parse(raw)
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birthBeyond the mandatory MSH header, the required segments are: MSA, PID, ORC, TQ1. 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 BRT^O32 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 | MSA | Required | No | Message acknowledgment | - |
| 4 | ARV | Optional | Yes | Access restriction | - |
| 5 | ERR | Optional | Yes | Error | - |
| 6 | SFT | Optional | Yes | Software segment | - |
| 7 | UAC | Optional | No | User authentication credential | - |
| 8 | NTE | Optional | Yes | Notes and comments | - |
| 9 | PID | Required | No | Patient identification | RESPONSE |
| 10 | PRT | Optional | Yes | Participation information | RESPONSE |
| 11 | ARV | Optional | Yes | Access restriction | RESPONSE |
| 12 | ORC | Required | No | Common order | RESPONSE |
| 13 | PRT | Optional | Yes | Participation information | RESPONSE |
| 14 | TQ1 | Required | No | Timing / quantity | TIMING |
| 15 | TQ2 | Optional | Yes | Timing / quantity relationship | TIMING |
| 16 | BPO | Optional | No | Blood product order | RESPONSE |
| 17 | BTX | Optional | Yes | Blood product transfusion / disposition | RESPONSE |
Get started with Zato and connect your systems in minutes.