Schedule a demo
Message type

Pharmacy / treatment dispense

Reports the dispensing of a pharmacy or treatment order. The ORC carries order control and RXD reports the dispensed medication, quantity, and dispensing details.

42segments
16required
4groups
v2.9HL7 version
rds-o13.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RDS^O13^RDS_O13|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXD|1|54321^Metformin^NDC|20260701|60|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.rxd.dispense_give_code
quantity = msg.rxd.actual_dispense_amount

Build and parse RDS^O13 messages in Python

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

1

Parse an incoming RDS^O13 message

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

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RDS^O13^RDS_O13|MSG001|P|2.9\r' \
      'ORC|NW|ORD001||GRP001|||1^BID\r' \
      'RXD|1|54321^Metformin^NDC|20260701|60|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.rxd.dispense_give_code
quantity = msg.rxd.actual_dispense_amount

Learn by building

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

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||RDS^O13^RDS_O13|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.

RDS^O13 segment composition

Segments that make up the RDS^O13 message, in order. Groups are shown with their child segments.

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5NTEOptionalYesNotes and comments-
6PIDRequiredNoPatient identificationPATIENT
7PD1RequiredNoPatient additional demographicPATIENT
8PRTOptionalYesParticipation informationPATIENT
9ARVOptionalYesAccess restrictionPATIENT
10NTEOptionalYesNotes and commentsPATIENT
11AL1OptionalYesPatient allergy informationPATIENT
12PV1RequiredNoPatient visitPATIENT
13PV2OptionalNoPatient visit - additional infoPATIENT
14PRTOptionalYesParticipation informationPATIENT
15ARVOptionalYesAccess restrictionPATIENT
16ORCRequiredNoCommon orderORDER
17PRTOptionalYesParticipation informationORDER
18TQ1RequiredNoTiming / quantityORDER
19TQ2OptionalYesTiming / quantity relationshipORDER
20RXORequiredNoPharmacy / treatment orderORDER
21PRTOptionalYesParticipation informationORDER
22NTERequiredYesNotes and commentsORDER_DETAIL_SUPPLEMENT
23RXRRequiredYesPharmacy / treatment routeORDER_DETAIL_SUPPLEMENT
24RXCRequiredNoPharmacy / treatment component orderORDER_DETAIL_SUPPLEMENT
25NTEOptionalYesNotes and commentsORDER_DETAIL_SUPPLEMENT
26RXERequiredNoPharmacy / treatment encoded orderORDER
27PRTOptionalYesParticipation informationORDER
28NTEOptionalYesNotes and commentsORDER
29TQ1RequiredNoTiming / quantityTIMING_ENCODED
30TQ2OptionalYesTiming / quantity relationshipTIMING_ENCODED
31RXRRequiredYesPharmacy / treatment routeORDER
32RXCOptionalYesPharmacy / treatment component orderORDER
33RXDRequiredNoPharmacy / treatment dispenseORDER
34PRTOptionalYesParticipation informationORDER
35NTEOptionalYesNotes and commentsORDER
36RXRRequiredYesPharmacy / treatment routeORDER
37RXCOptionalYesPharmacy / treatment component orderORDER
38CDOOptionalYesClinical study data objectORDER
39OBXRequiredNoObservation resultORDER
40PRTOptionalYesParticipation informationORDER
41NTEOptionalYesNotes and commentsORDER
42FT1OptionalYesFinancial transactionORDER

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python