Message type

Laboratory order for additional work up response

Responds to a laboratory order for additional work-up. The MSA segment reports the processing status. Laboratory systems exchange this.

38segments

15required

4groups

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RCV^O59^RCV_O59|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXE|1^BID|54321^Metformin^NDC|500|mg|TAB'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
order_control = msg.orc.order_control
order_number = msg.orc.placer_order_number
drug = msg.rxe.give_code
dose = msg.rxe.give_amount_minimum

Python examples

Build and parse RCV^O59 messages in Python

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

Parse an incoming RCV^O59 message

Demonstrates receiving and extracting key fields from a laboratory order for additional work up response transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RCV^O59^RCV_O59|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXE|1^BID|54321^Metformin^NDC|500|mg|TAB'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
order_control = msg.orc.order_control
order_number = msg.orc.placer_order_number
drug = msg.rxe.give_code
dose = msg.rxe.give_amount_minimum

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||RCV^O59^RCV_O59|MSG00001|P|2.9'
msg = HL7Message.parse(raw)

order_control = msg.orc.order_control
order_number = msg.orc.placer_order_number

Beyond the mandatory MSH header, the required segments are: PID, PV1, ORC, TQ1, RXO, NTE, RXR, RXC. 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

RCV^O59 segment composition

Segments that make up the RCV^O59 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	`NTE`	Optional	Yes	Notes and comments	-
6	`PID`	Required	No	Patient identification	PATIENT
7	`PD1`	Optional	No	Patient additional demographic	PATIENT
8	`PRT`	Optional	Yes	Participation information	PATIENT
9	`NTE`	Optional	Yes	Notes and comments	PATIENT
10	`AL1`	Optional	Yes	Patient allergy information	PATIENT
11	`PV1`	Required	No	Patient visit	PATIENT
12	`PV2`	Optional	No	Patient visit - additional info	PATIENT
13	`PRT`	Optional	Yes	Participation information	PATIENT
14	`ORC`	Required	No	Common order	ORDER
15	`TQ1`	Required	No	Timing / quantity	ORDER
16	`TQ2`	Optional	Yes	Timing / quantity relationship	ORDER
17	`RXO`	Required	No	Pharmacy / treatment order	ORDER
18	`NTE`	Required	Yes	Notes and comments	ORDER_DETAIL_SUPPLEMENT
19	`RXR`	Required	Yes	Pharmacy / treatment route	ORDER_DETAIL_SUPPLEMENT
20	`RXC`	Required	No	Pharmacy / treatment component order	ORDER_DETAIL_SUPPLEMENT
21	`NTE`	Optional	Yes	Notes and comments	ORDER_DETAIL_SUPPLEMENT
22	`PRT`	Optional	Yes	Participation information	ORDER
23	`RXE`	Required	No	Pharmacy / treatment encoded order	ORDER
24	`PRT`	Optional	Yes	Participation information	ORDER
25	`NTE`	Optional	Yes	Notes and comments	ORDER
26	`TQ1`	Required	No	Timing / quantity	TIMING_ENCODED
27	`TQ2`	Optional	Yes	Timing / quantity relationship	TIMING_ENCODED
28	`RXR`	Required	Yes	Pharmacy / treatment route	ORDER
29	`RXC`	Optional	Yes	Pharmacy / treatment component order	ORDER
30	`RXD`	Required	No	Pharmacy / treatment dispense	ORDER
31	`PRT`	Optional	Yes	Participation information	ORDER
32	`NTE`	Optional	Yes	Notes and comments	ORDER
33	`RXR`	Required	Yes	Pharmacy / treatment route	ORDER
34	`RXC`	Optional	Yes	Pharmacy / treatment component order	ORDER
35	`OBX`	Required	No	Observation result	ORDER
36	`PRT`	Optional	Yes	Participation information	ORDER
37	`NTE`	Optional	Yes	Notes and comments	ORDER
38	`FT1`	Optional	Yes	Financial transaction	ORDER

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python