Message type

Pharmacy / treatment administration

Reports the administration of a pharmacy or treatment order with timing details. The ORC carries order control and RXA reports the administered medication, route, and administration time.

40segments

16required

5groups

v2.9HL7 version

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RAS^O17^RAS_O17|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXA|0|1|20260701||08^HepB^CVX|1|mL|IM'

# .. 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
substance = msg.rxa.administered_code
amount = msg.rxa.administered_amount

Python examples

Build and parse RAS^O17 messages in Python

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

Parse an incoming RAS^O17 message

Demonstrates receiving and extracting key fields from a pharmacy / treatment administration transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RAS^O17^RAS_O17|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXA|0|1|20260701||08^HepB^CVX|1|mL|IM'

# .. 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
substance = msg.rxa.administered_code
amount = msg.rxa.administered_amount

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||RAS^O17^RAS_O17|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, PD1, PV1, ORC, TQ1, RXO, NTE, RXR. 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

RAS^O17 segment composition

Segments that make up the RAS^O17 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`	Required	No	Patient additional demographic	PATIENT
8	`PRT`	Optional	Yes	Participation information	PATIENT
9	`NTE`	Optional	Yes	Notes and comments	PATIENT
10	`ARV`	Optional	Yes	Access restriction	PATIENT
11	`AL1`	Optional	Yes	Patient allergy information	PATIENT
12	`PV1`	Required	No	Patient visit	PATIENT
13	`PV2`	Optional	No	Patient visit - additional info	PATIENT
14	`PRT`	Optional	Yes	Participation information	PATIENT
15	`ARV`	Optional	Yes	Access restriction	PATIENT
16	`ORC`	Required	No	Common order	ORDER
17	`PRT`	Optional	Yes	Participation information	ORDER
18	`TQ1`	Required	No	Timing / quantity	ORDER
19	`TQ2`	Optional	Yes	Timing / quantity relationship	ORDER
20	`RXO`	Required	No	Pharmacy / treatment order	ORDER
21	`PRT`	Optional	Yes	Participation information	ORDER
22	`NTE`	Required	Yes	Notes and comments	ORDER_DETAIL_SUPPLEMENT
23	`RXR`	Required	Yes	Pharmacy / treatment route	ORDER_DETAIL_SUPPLEMENT
24	`RXC`	Required	No	Pharmacy / treatment component order	ORDER_DETAIL_SUPPLEMENT
25	`NTE`	Optional	Yes	Notes and comments	ORDER_DETAIL_SUPPLEMENT
26	`RXE`	Required	No	Pharmacy / treatment encoded order	ORDER
27	`PRT`	Optional	Yes	Participation information	ORDER
28	`NTE`	Optional	Yes	Notes and comments	ORDER
29	`TQ1`	Required	No	Timing / quantity	TIMING_ENCODED
30	`TQ2`	Optional	Yes	Timing / quantity relationship	TIMING_ENCODED
31	`RXR`	Required	Yes	Pharmacy / treatment route	ORDER
32	`RXC`	Optional	Yes	Pharmacy / treatment component order	ORDER
33	`CDO`	Optional	Yes	Clinical study data object	ORDER
34	`RXA`	Required	Yes	Pharmacy / treatment administration	ORDER
35	`PRT`	Optional	Yes	Participation information	ORDER
36	`RXR`	Required	No	Pharmacy / treatment route	ORDER
37	`OBX`	Required	No	Observation result	OBSERVATION
38	`PRT`	Optional	Yes	Participation information	OBSERVATION
39	`NTE`	Optional	Yes	Notes and comments	OBSERVATION
40	`CTI`	Optional	Yes	Clinical trial identification	ORDER

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python