HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

RGR: Pharmacy/treatment dose information

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

Recognising RGR messages

RGR announces itself in MSH-9 like this:

MSH-9RGR^RGR^RGR_RGR
  1. MSH-9.1RGRmessage code: what kind of message this is
  2. MSH-9.2RGRtrigger event: what happened in the real world
  3. MSH-9.3RGR_RGRmessage 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

RGR takes 1 structure.

RGR_RGR

Sent when one thing happens: RGR: RGR.

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

SegmentNameOPTCardinality
MSHR1..1
MSAR1..1
ERRO0..*
SFTO0..*
DEFINITIONa group of 4 segments, repeated togetherR1..*
QRDR1..1
QRFO0..1
PATIENTa group of 2 segments, repeated togetherO0..1
PIDin PATIENTR1..1
NTEin PATIENTO0..*
ORDERa group of 5 segments, repeated togetherR1..*
ORCR1..1
ENCODINGa group of 3 segments, repeated togetherO0..1
RXEin ENCODINGR1..1
RXRin ENCODINGR1..*
RXCin ENCODINGO0..*
RXGR1..*
RXRR1..*
RXCO0..*
DSCO0..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 4 such groups: DEFINITION, PATIENT, ORDER, ENCODING.

Trigger events

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

EventNameStructure
RGRRGRRGR_RGR