visit the hl7 website The Demo site for our new HL7 Version 2+ (plus) Standard

18.4.148 RDE - Pharmacy/Treatment Encoded Order Message (Event O11) (4A.3.6)

This message communicates the pharmacy or treatment application's encoding of the pharmacy/treatment order ,OMP, message. It may be sent as an unsolicited message to report on either a single order or multiple pharmacy/treatment orders for a patient.

The RDE/RRE message pair can also be used to communicate a refill authorization request; however, a specific trigger event has been assigned. See section 4A.3.13 "RDE - Pharmacy/Treatment Refill Authorization Request Message (Event O25)." As a site-specific variant, the original order segments (RXO, RXRs, associated RXCs, and any NTEs) may be sent optionally (for comparison).

The event O11 represents an encoding of an order. To communicate explicit dispense requests, which are different event types, the RDE^O11/RRE^O12 message pair is also used, but the event O49 is preferred. See section 4A.3.23 "RDE - Pharmacy/Treatment Dispense Request Message (Event O49)." As a site-specific variant, the original order segments (RXO, RXRs, associated RXCs, and any NTEs) may be sent optionally (for comparison).

Segment Cardinality Implement Status
RDE^O11^RDE_O11
MSH

Message Header

[1..1] SHALL
ARV

Access Restriction

 
UAC

User Authentication Credential Segment

[0..1]  
NTE

Notes and Comments

 
PATIENT [0..1]  
PID

Patient Identification

[1..1] SHALL
PD1

Patient Additional Demographic

[0..1]  
PRT

Participation Information

 
NTE

Notes and Comments

 
ARV

Access Restriction

  B
PATIENT_VISIT [0..1]  
PV1

Patient Visit

[1..1] SHALL
PV2

Patient Visit - Additional Information

[0..1]  
PRT

Participation Information

 
ARV

Access Restriction

  B
INSURANCE  
IN1

Insurance

[1..1] SHALL
IN2

Insurance Additional Information

[0..1]  
IN3

Insurance Additional Information, Certification

[0..1]  
GT1

Guarantor

[0..1]  
AL1

Patient Allergy Information

 
ORDER [1..*] SHALL
ORC

Common Order

[1..1] SHALL
PRT

Participation Information

 
TIMING  
TQ1

Timing/Quantity

[1..1] SHALL
TQ2

Timing/Quantity Relationship

 
ORDER_DETAIL [0..1]  
RXO

Pharmacy/Treatment Order

[1..1] SHALL
PRT

Participation Information

 
NTE

Notes and Comments

 
RXR

Pharmacy/Treatment Route

[1..*] SHALL
COMPONENT  
RXC

Pharmacy/Treatment Component Order

[1..1] SHALL
NTE

Notes and Comments

 
RXE

Pharmacy/Treatment Encoded Order

[1..1] SHALL
PRT

Participation Information

 
NTE

Notes and Comments

 
TIMING_ENCODED [1..*] SHALL
TQ1

Timing/Quantity

[1..1] SHALL
TQ2

Timing/Quantity Relationship

 
PHARMACY_TREATMENT_INFUSION_ORDER  
RXV

Pharmacy/Treatment Infusion

[1..1] SHALL
PRT

Participation Information

 
NTE

Notes and Comments

 
TIMING_ENCODED [1..*] SHALL
TQ1

Timing/Quantity

[1..1] SHALL
TQ2

Timing/Quantity Relationship

 
RXR

Pharmacy/Treatment Route

[1..*] SHALL
RXC

Pharmacy/Treatment Component Order

 
CDO

Cumulative Dosage

 
OBSERVATION  
OBX

Observation/Result

[1..1] SHALL
PRT

Participation Information

 
NTE

Notes and Comments

 
FT1

Financial Transaction

 
BLG

Billing

[0..1]  
CTI

Clinical Trial Identification

 

 

RDE_O11

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank - RRE^O26^RRE_O26
Blank Blank - RRE^O12^RRE_O12 orOSU^O52^OSU_O52
NE NE - -
NE NE - -
NE AL, SU, ER - RRE^O26^RRE_O26
NE AL, SU, ER - RRE^O12^RRE_O12 orOSU^O52^OSU_O52
AL, SU, ER AL, SU, ER ACK^O25^ACK RRE^O26^RRE_O26
AL, SU, ER AL, SU, ER ACK^O11^ACK RRE^O12^RRE_O12 orOSU^O52^OSU_O52
We need some ER7 examples...
We need some XML examples...
Note: The RXCs which follow the RXO may not be fully encoded, but those that follow the RXE must be fully encoded.
The NTE segment(s) following the PD1 segment are intended to communicate notes and comments relative to the patient.
The NTE segment(s) following the RXO segment are intended to communicate notes and comments relative to the pharmacy/treatment order.
The NTE segment(s) following the RXE segment are intended to communicate notes and comments relative to the encoded order.
The NTE segment(s) following the RXV segment are intended to communicate notes and comments relative to the encoded order.
The NTE segment(s) following the RXC segment are intended to communicate notes and comments relative to the component(s).
The NTE segment following the OBX segment is intended to communicate notes and comments relative to the results.