HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

RRA: Pharmacy/treatment administration acknowledgment message

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

Recognising RRA messages

RRA announces itself in MSH-9 like this:

MSH-9RRA^O18^RRA_O18
  1. MSH-9.1RRAmessage code: what kind of message this is
  2. MSH-9.2O18trigger event: what happened in the real world
  3. MSH-9.3RRA_O18message 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

RRA takes 1 structure.

RRA_O18

Sent when one thing happens: O18: O18.

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..*
ADMINISTRATIONin ORDERa group of 2 segments, repeated togetherO0..1
RXAin ADMINISTRATIONR1..*
RXRin ADMINISTRATIONR1..1

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 5 such groups: RESPONSE, PATIENT, ORDER, TIMING, ADMINISTRATION.

Trigger events

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

EventNameStructure
O18O18RRA_O18