HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

RRG: Pharmacy/treatment give acknowledgment message

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

Recognising RRG messages

RRG announces itself in MSH-9 like this:

MSH-9RRG^O16^RRG_O16
  1. MSH-9.1RRGmessage code: what kind of message this is
  2. MSH-9.2O16trigger event: what happened in the real world: pharmacy/treatment give acknowledgment message
  3. MSH-9.3RRG_O16message 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

RRG takes 1 structure.

RRG_O16: Pharmacy/Treatment Give Acknowledgment Message

Sent when one thing happens: O16: Pharmacy/Treatment Give Acknowledgment 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..*
GIVEin ORDERa group of 4 segments, repeated togetherO0..1
RXGin GIVER1..1
TIMING_GIVEin GIVEa group of 2 segments, repeated togetherR1..*
TQ1in TIMING_GIVER1..1
TQ2in TIMING_GIVEO0..*
RXRin GIVER1..*
RXCin GIVEO0..*

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, GIVE, TIMING_GIVE.

Trigger events

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

EventNameStructure
O16Pharmacy/Treatment Give Acknowledgment MessageRRG_O16