Schedule a demo
Message type

Pharmacy / treatment refill authorization request

Requests a refill authorization for an existing pharmacy or treatment order. The ORC and RXE segments carry the refill request details.

41segments
13required
3groups
v2.9HL7 version
rde-o49.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RDE^O49^RDE_O49|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

Build and parse RDE^O49 messages in Python

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

1

Parse an incoming RDE^O49 message

Demonstrates receiving and extracting key fields from a pharmacy / treatment refill authorization request transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RDE^O49^RDE_O49|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

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||RDE^O49^RDE_O49|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, IN1, ORC, TQ1, RXO, 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.

RDE^O49 segment composition

Segments that make up the RDE^O49 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
7PD1OptionalNoPatient additional demographicPATIENT
8PRTOptionalYesParticipation informationPATIENT
9NTEOptionalYesNotes and commentsPATIENT
10PV1RequiredNoPatient visitPATIENT
11PV2OptionalNoPatient visit - additional infoPATIENT
12PRTOptionalYesParticipation informationPATIENT
13IN1RequiredNoInsurancePATIENT
14IN2OptionalNoInsurance additional infoPATIENT
15IN3OptionalNoInsurance additional info - certificationPATIENT
16GT1OptionalNoGuarantorPATIENT
17AL1OptionalYesPatient allergy informationPATIENT
18ORCRequiredNoCommon orderORDER
19PRTOptionalYesParticipation informationORDER
20TQ1RequiredNoTiming / quantityORDER
21TQ2OptionalYesTiming / quantity relationshipORDER
22RXORequiredNoPharmacy / treatment orderORDER
23PRTOptionalYesParticipation informationORDER
24NTEOptionalYesNotes and commentsORDER
25RXRRequiredYesPharmacy / treatment routeORDER
26RXCRequiredNoPharmacy / treatment component orderCOMPONENT
27NTEOptionalYesNotes and commentsCOMPONENT
28PRTOptionalYesParticipation informationORDER
29RXERequiredNoPharmacy / treatment encoded orderORDER
30PRTOptionalYesParticipation informationORDER
31NTEOptionalYesNotes and commentsORDER
32TQ1RequiredNoTiming / quantityORDER
33TQ2OptionalYesTiming / quantity relationshipORDER
34RXRRequiredYesPharmacy / treatment routeORDER
35RXCOptionalYesPharmacy / treatment component orderORDER
36OBXRequiredNoObservation resultORDER
37PRTOptionalYesParticipation informationORDER
38NTEOptionalYesNotes and commentsORDER
39FT1OptionalYesFinancial transactionORDER
40BLGOptionalNoBillingORDER
41CTIOptionalYesClinical trial identificationORDER

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python