HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

RRE: Pharmacy/treatment encoded order acknowledgment message

This page lists the structures and trigger events RRE defines, taken from the standard. The written commentary that theADT page carries has not been written for RRE.

Recognising RRE messages

RRE announces itself in MSH-9 like this:

MSH-9RRE^O12^RRE_O12
  1. MSH-9.1RREmessage code: what kind of message this is
  2. MSH-9.2O12trigger event: what happened in the real world: pharmacy/treatment encoded order acknowledgment
  3. MSH-9.3RRE_O12message structure: which segments to expect, and in what order

How to use these specifications explains MSH-9 in full, with a worked example.

Message structures

RRE takes 1 structure.

RRE_O12: Pharmacy/Treatment Encoded Order Acknowledgment

2 different trigger events send this structure:

The segments below are the same for all 2. HL7 varies the meaning, not the shape: there is no separate RRE_O26 layout. What changes is MSH-9, which tells the receiver which of the 2 happened and therefore what to do with the message.

You must always send: MSH, MSA. Everything else is optional, or required only inside a group you chose to send.

SegmentNameOPTCardinality
MSHR1..1
MSAR1..1
ERRO0..*
SFTO0..*
NTEO0..*
RESPONSEa group of 2 segments, repeated togetherO0..1
PATIENTin RESPONSEa group of 2 segments, repeated togetherO0..1
PIDin PATIENTR1..1
NTEin PATIENTO0..*
ORDERin RESPONSEa group of 3 segments, repeated togetherR1..*
ORCin ORDERR1..1
TIMINGin ORDERa group of 2 segments, repeated togetherO0..*
TQ1in TIMINGR1..1
TQ2in TIMINGO0..*
ENCODINGin ORDERa group of 4 segments, repeated togetherO0..1
RXEin ENCODINGR1..1
TIMING_ENCODEDin ENCODINGa group of 2 segments, repeated togetherR1..*
TQ1in TIMING_ENCODEDR1..1
TQ2in TIMING_ENCODEDO0..*
RXRin ENCODINGR1..*
RXCin ENCODINGO0..*

R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 6 such groups: RESPONSE, PATIENT, ORDER, TIMING, ENCODING, TIMING_ENCODED.

Trigger events

The trigger event is the real-world thing that made the message get sent. RRE defines 2.

EventNameStructure
O12Pharmacy/Treatment Encoded Order AcknowledgmentRRE_O12
O26O26RRE_O12