Carries unsolicited observation results from a producing system to one or more recipients. The OBR segment defines the observation request and OBX segments carry individual result values. Laboratory, radiology, and point-of-care systems send this to deliver findings to ordering providers and clinical repositories.
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'ORU^R01^ORU_R01|MSG001|P|2.9\r' \
'OBR|1||ORD001\r' \
'OBX|1|NM|2345-7^Glucose^LN||95|mg/dL|70-100'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
order_id = msg.obr.placer_order_number
test = msg.obr.universal_service_identifier
value = msg.obx.observation_value
units = msg.obx.unitsHow to construct, send, receive, and extract fields from real-world ORU^R01 messages.
Demonstrates receiving and extracting key fields from a unsolicited observation result transaction
# Zato
from zato.hl7v2 import HL7Message
# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
'ORU^R01^ORU_R01|MSG001|P|2.9\r' \
'OBR|1||ORD001\r' \
'OBX|1|NM|2345-7^Glucose^LN||95|mg/dL|70-100'
# .. parsed into a Python object ..
msg = HL7Message.parse(raw)
# .. whose fields we can now access.
order_id = msg.obr.placer_order_number
test = msg.obr.universal_service_identifier
value = msg.obx.observation_value
units = msg.obx.unitsStep-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||ORU^R01^ORU_R01|MSG00001|P|2.9\rDSC|CONT-001'
msg = HL7Message.parse(raw)
order_id = msg.obr.placer_order_number
test = msg.obr.universal_service_identifierBeyond the mandatory MSH header, the required segments are: PID, NK1, OBX, PV1, IN1, ORC, OBX, TXA. 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 ORU^R01 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 | PATIENT_RESULT |
| 6 | PD1 | Optional | No | Patient additional demographic | PATIENT_RESULT |
| 7 | PRT | Optional | Yes | Participation information | PATIENT_RESULT |
| 8 | OH1 | Optional | Yes | Employment status | PATIENT_RESULT |
| 9 | OH2 | Optional | Yes | Past or present job | PATIENT_RESULT |
| 10 | OH3 | Optional | No | Usual work | PATIENT_RESULT |
| 11 | OH4 | Optional | Yes | Combat zone work | PATIENT_RESULT |
| 12 | NTE | Optional | Yes | Notes and comments | PATIENT_RESULT |
| 13 | NK1 | Required | No | Next of kin / associated parties | NEXT_OF_KIN |
| 14 | OH2 | Optional | Yes | Past or present job | NEXT_OF_KIN |
| 15 | OH3 | Optional | No | Usual work | NEXT_OF_KIN |
| 16 | ARV | Optional | Yes | Access restriction | PATIENT_RESULT |
| 17 | OBX | Required | No | Observation result | PATIENT_OBSERVATION |
| 18 | PRT | Optional | Yes | Participation information | PATIENT_OBSERVATION |
| 19 | PV1 | Required | No | Patient visit | VISIT |
| 20 | PV2 | Optional | No | Patient visit - additional info | VISIT |
| 21 | PRT | Optional | Yes | Participation information | VISIT |
| 22 | IN1 | Required | No | Insurance | INSURANCE |
| 23 | IN2 | Optional | No | Insurance additional info | INSURANCE |
| 24 | IN3 | Optional | No | Insurance additional info - certification | INSURANCE |
| 25 | ORC | Required | No | Common order | COMMON_ORDER |
| 26 | PRT | Optional | Yes | Participation information | COMMON_ORDER |
| 27 | OBX | Required | No | Observation result | COMMON_ORDER |
| 28 | PRT | Optional | Yes | Participation information | COMMON_ORDER |
| 29 | TXA | Required | No | Transcription document header | COMMON_ORDER |
| 30 | OBR | Required | No | Observation request | PATIENT_RESULT |
| 31 | NTE | Optional | Yes | Notes and comments | PATIENT_RESULT |
| 32 | PRT | Required | No | Participation information | OBSERVATION_PARTICIPATION |
| 33 | DEV | Optional | Yes | Device | OBSERVATION_PARTICIPATION |
| 34 | TQ1 | Required | No | Timing / quantity | TIMING_QTY |
| 35 | TQ2 | Optional | Yes | Timing / quantity relationship | TIMING_QTY |
| 36 | CTD | Optional | No | Contact data | PATIENT_RESULT |
| 37 | OBX | Required | No | Observation result | OBSERVATION |
| 38 | PRT | Optional | Yes | Participation information | OBSERVATION |
| 39 | NTE | Optional | Yes | Notes and comments | OBSERVATION |
| 40 | FT1 | Optional | Yes | Financial transaction | PATIENT_RESULT |
| 41 | CTI | Optional | Yes | Clinical trial identification | PATIENT_RESULT |
| 42 | SPM | Required | No | Specimen | SPECIMEN |
| 43 | OBX | Required | No | Observation result | SPECIMEN |
| 44 | PRT | Optional | Yes | Participation information | SPECIMEN |
| 45 | DEV | Required | No | Device | PATIENT_RESULT |
| 46 | OBX | Optional | Yes | Observation result | PATIENT_RESULT |
| 47 | DSC | Optional | No | Continuation pointer | - |
Get started with Zato and connect your systems in minutes.