HL7 RDE_O11 (Pharmacy/Treatment Encoded Order) | Integration Soup HL7 Reference Guide

HL7 RDE_O11 Pharmacy/Treatment Encoded Order

The pharmacy has encoded the order into something it can dispense or administer.

HL7 message structure RDE_O11 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
NTE	Notes and Comments	No	Yes
RDE_O11.PATIENT	Patient group	No	No
PID	Patient Identification	Yes	No
PD1	Patient Additional Demographic	No	No
NTE	Notes and Comments	No	Yes
RDE_O11.PATIENT_VISIT	Patient Visit group	No	No
PV1	Patient Visit	Yes	No
PV2	Patient Visit - Additional Information	No	No
RDE_O11.INSURANCE	Insurance group	No	Yes
IN1	Insurance	Yes	No
IN2	Insurance Additional Information	No	No
IN3	Insurance Additional Information, Certification	No	No
GT1	Guarantor	No	No
AL1	Patient Allergy Information	No	Yes
RDE_O11.ORDER	Order group	Yes	Yes
ORC	Common Order	Yes	No
RDE_O11.TIMING	Timing group	No	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
RDE_O11.ORDER_DETAIL	Order Detail group	No	No
RXO	Pharmacy/Treatment Order	Yes	No
NTE	Notes and Comments	No	Yes
RXR	Pharmacy/Treatment Route	Yes	Yes
RDE_O11.COMPONENT	Component group	No	Yes
RXC	Pharmacy/Treatment Component Order	Yes	No
NTE	Notes and Comments	No	Yes
RXE	Pharmacy/Treatment Encoded Order	Yes	No
NTE	Notes and Comments	No	Yes
RDE_O11.TIMING_ENCODED	Timing Encoded group	Yes	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
RXR	Pharmacy/Treatment Route	Yes	Yes
RXC	Pharmacy/Treatment Component Order	No	Yes
RDE_O11.OBSERVATION	Observation group	No	Yes
OBX	Observation/Result	Yes	No
NTE	Notes and Comments	No	Yes
FT1	Financial Transaction	No	Yes
BLG	Billing	No	No
CTI	Clinical Trial Identification	No	Yes

RDE_O11 is the encoded pharmacy or treatment order message. It is used when the pharmacy/treatment application has taken the ordered medication or treatment and turned it into a pharmacy-ready order with encoded medication detail, timing, route, components, and often billing or observation context.

Think of RDE as the message where the order stops being a general request and becomes a pharmacy-specific instruction. It may be sent from an ordering system to pharmacy, from pharmacy to a medication administration system, or from pharmacy middleware to downstream clinical systems that need the perfected order.

A small RDE example

MSH|^~\&|PHARM|CITYHOSP|MAR|CITYHOSP|20260715113000||RDE^O11^RDE_O11|RDE00001|P|2.5.1 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F PV1|1|I|WARD2^205^1^CITYHOSP ORC|NW|MED448811^EHR|RX998877^PHARM||||^^^20260715120000|||12345^Careful^Clara RXO|AMOX500^Amoxicillin 500 mg capsule^L|1|CAP^capsule^UCUM|TID^Three times daily^HL70335 RXE|^^^20260715120000|AMOX500^Amoxicillin 500 mg capsule^L|1|CAP^capsule^UCUM|30|CAP^capsule^UCUM|||||||||||||||||RX998877^PHARM TQ1|1|||TID^Three times daily^HL70335||20260715120000 RXR|PO^Oral^HL70162 OBX|1|CE|ALLERGYCHECK^Pharmacy allergy check^L||NEG^No issue found^L||||||F

What systems do with it

The sender is commonly a pharmacy system or pharmacy integration component. The receiver may be an electronic medication administration record, a dispensing cabinet system, an EHR, or an integration engine that routes medication orders. The receiver uses ORC to identify and control the order, RXE as the encoded pharmacy order, and RXR for route instructions.

The optional RXO group can carry a copy of the originally requested order. That is useful when the receiver needs to compare what the prescriber requested with what pharmacy encoded. Do not confuse the two. RXO is the requested order; RXE is the pharmacy's encoded version.

How to read the structure

The patient group carries PID, optional visit, insurance, guarantor, and allergy information. The required order group starts with ORC, may include timing and original order detail, then requires RXE, encoded timing, route, optional components in RXC, observations in OBX, financial transactions, billing, and clinical trial identifiers.

Timing appears in more than one place because medication orders often distinguish requested timing from encoded administration or dispensing timing. If those disagree, define which timing drives the receiver's schedule.

Implementation traps

The big trap is losing the medication identifiers that make the order actionable. Local drug code, formulary code, NDC or national code, strength, dose form, route, units, and quantity need to survive mapping. A pretty display name is not enough for safe downstream processing.

Also watch compound and component medications. RXC repeats are how many profiles represent components or additives. Flattening a compound into one free-text drug name can make the order unreadable to dispensing and administration systems.

Reference notes

The HL7 v2+ RDE_O11 page describes this message as communicating a pharmacy/treatment application's encoding of a pharmacy/treatment order. Vendor overviews such as iNTERFACEWARE's RDE guide also frame it as the order flow between ordering and filling applications.