Message type

Unsolicited point-of-care observation

Delivers unsolicited point-of-care observation results. Structured similarly to ORU^R01 but focused on bedside device data. The OBX segments carry vital signs, glucose readings, or other point-of-care measurements.

29segments

9required

5groups

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ORU^R30^ORU_R30|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.units

Python examples

Build and parse ORU^R30 messages in Python

How to construct, send, receive, and extract fields from real-world ORU^R30 messages.

Parse an incoming ORU^R30 message

Demonstrates receiving and extracting key fields from a unsolicited point-of-care observation transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'ORU^R30^ORU_R30|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.units

Tutorials

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

MLLP

Receive and parse HL7 v2 messages

Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.

Start tutorial Build

Build and send HL7 v2 messages

Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.

Start tutorial

FAQ

Frequently asked questions

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^R30^ORU_R30|MSG00001|P|2.9\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rPD1|||Family Health Clinic^^12345\rPRT|1||AT^Attending||1234^CHEN^DAVID^L^^^MD\rOH1|1|EMPLOYED^Employed^HL70761|20200101\rOH2|1|SOFTWARE^Software developer^SOC||20200101\rOH3|1|SOFTWARE^Software developer^SOC\rORC|NW|ORD-2001||||||20260401120000|||1234^CHEN^DAVID^L^^^MD\rOBR|1|ORD-2001||CBC^Complete blood count^LN|||20260401120000'
msg = HL7Message.parse(raw)

order_id = msg.obr.placer_order_number
test = msg.obr.universal_service_identifier

Beyond the mandatory MSH header, the required segments are: PID, OBX, PV1, ORC, OBR, TQ1, OBX, DEV. 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.

Reference

ORU^R30 segment composition

Segments that make up the ORU^R30 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	-
6	`PD1`	Optional	No	Patient additional demographic	-
7	`PRT`	Optional	Yes	Participation information	-
8	`OH1`	Optional	Yes	Employment status	-
9	`OH2`	Optional	Yes	Past or present job	-
10	`OH3`	Optional	No	Usual work	-
11	`OH4`	Optional	Yes	Combat zone work	-
12	`ARV`	Optional	Yes	Access restriction	-
13	`OBX`	Required	No	Observation result	PATIENT_OBSERVATION
14	`PRT`	Optional	Yes	Participation information	PATIENT_OBSERVATION
15	`PV1`	Required	No	Patient visit	VISIT
16	`PV2`	Optional	No	Patient visit - additional info	VISIT
17	`PRT`	Optional	Yes	Participation information	VISIT
18	`ORC`	Required	No	Common order	-
19	`PRT`	Optional	Yes	Participation information	-
20	`OBR`	Required	No	Observation request	-
21	`NTE`	Optional	Yes	Notes and comments	-
22	`PRT`	Optional	Yes	Participation information	-
23	`TQ1`	Required	No	Timing / quantity	TIMING_QTY
24	`TQ2`	Optional	Yes	Timing / quantity relationship	TIMING_QTY
25	`OBX`	Required	No	Observation result	OBSERVATION
26	`PRT`	Optional	Yes	Participation information	OBSERVATION
27	`NTE`	Optional	Yes	Notes and comments	OBSERVATION
28	`DEV`	Required	No	Device	DEVICE
29	`OBX`	Optional	Yes	Observation result	DEVICE

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python