^O11
RDE^O11 — Pharmacy/Treatment Encoded Order
RDE^O11 is sent by the pharmacy system when a pharmacist has reviewed, encoded, and verified a medication order for dispensing. It represents the pharmacist's interpretation of the original prescriber order, including the specific drug product, dose, and dispensing instructions.
When Is This Sent?
When the pharmacist encodes and verifies an order for dispensing. This is the pharmacy's outbound signal that the order has been clinically reviewed and is ready for the dispenser.
Real-World Usage
RDE^O11 is used in interfaces between pharmacy order management systems (like Pyxis, Omnicell, or CareFusion) and downstream dispensing or administration systems. The RXE segment carries the pharmacist-encoded drug details including the specific commercial product (NDC code), quantity, and sig. Downstream systems use this to drive automated dispensing cabinet (ADC) restocking and medication administration records.
Message Structure
Segment names link to their field-level reference pages.
| # | Segment | Purpose in this message | Req | Repeat |
|---|---|---|---|---|
| 1 | MSH | Message header with RDE^O11 in MSH.9 | R | — |
| 2 | PID | Patient demographics | R | — |
| 3 | ORC | Order common segment — ORC.1=RE (observations to follow) or NW/XO for new/change | R | — |
| 4 | RXE | Pharmacy encoded order: drug code (NDC/formulary), dose, frequency, route, quantity to dispense | R | — |
| 5 | RXR | Route of administration details | R | — |
| 6 | PV1 | Patient visit context (ward, bed location for delivery) | O | — |
| 7 | NTE | Pharmacist notes and administration instructions | O | Yes |
| 8 | RXC | Pharmacy component order (for compounded medications) | O | Yes |
Example Message
Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.
1MSH||^~\&|PHARMACY|HOSPITAL_A|ADC_SYSTEM|HOSPITAL_A|20260310150000||RDE^O11^RDE_O11|RDE00001|P|2.5.1 2PID||1||123456^^^HOSP_A^MR||Smith^John^M^^Mr.||19850315|M 3PV1||1|I|4A^201^1^^^HOSP_A||||1234^Ahmed^Dr.^Khalid 4ORC||RE|ORD20260310005^EPIC|RX20260310001^PHARMACY||SC||||20260310150000 5RXE|||0069-3060-68^Amoxicillin 500mg Cap^NDC|500|mg|C38288^Oral^NCIT|500|MG|CAP||Q8H&Every 8 hours&HL70136||||||20260310150000 6RXR||C38288^Oral^NCIT|PO
Troubleshooting Scenarios
ADC not restocking medication after RDE^O11
Cause
RXE.2 (give code/drug identifier) format does not match the ADC's formulary. The ADC expects NDC codes but the pharmacy system sends local formulary codes.
Fix
Obtain the ADC's formulary code format requirements. Build a drug code crosswalk from the pharmacy system's internal codes to NDC or the ADC's expected format. Map the codes in the interface engine's RXE.2 transformation.
Dose or frequency not displaying correctly in ADC or MAR
Cause
RXE.5 (give frequency) is using a local code that the receiving system doesn't recognize, or RXE.3/RXE.4 (give amount/units) format doesn't match expected component structure.
Fix
Review RXE segment components for dose (RXE.3-4) and frequency (RXE.5). Map local frequency codes (Q8H, BID, TID) to the receiving system's frequency table. Verify dose and units are in separate components as expected.
Common Confusions
RDE^O11 (Encoded order) vs RDS^O13 (Dispense). RDE^O11 is the pharmacist's verified order — it authorizes dispensing but doesn't confirm it happened. RDS^O13 confirms the medication was actually dispensed. Both are needed in a complete pharmacy-to-ADC-to-MAR workflow. Also: RDE^O11 vs ORM^O01 for pharmacy — ORM^O01 is the prescriber's order to the pharmacy; RDE^O11 is the pharmacy's encoded response going downstream to the dispenser.
Related Message Types
Segment Reference
Paste this message into our viewer
Interactive HL7 parser. Decodes every field, validates structure, highlights errors. Free, no signup.
Open HL7 Message Viewer →Need mapping templates?
The HL7 Integration Toolkit includes field mapping worksheets and interface spec templates for every major HL7 message type including RDE^O11.
View HL7 Integration Toolkit →