HL7 RGR_RGR (Pharmacy/Treatment Dose Information) | Integration Soup HL7 Reference Guide

HL7 RGR_RGR Pharmacy/Treatment Dose Information

The old-style query response for give or dose details.

HL7 message structure RGR_RGR groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
MSA	Message Acknowledgment	Yes	No
ERR	Error	No	Yes
SFT	Software Segment	No	Yes
RGR_RGR.DEFINITION	Definition group	Yes	Yes
QRD	Original-Style Query Definition	Yes	No
QRF	Original style query filter	No	No
RGR_RGR.PATIENT	Patient group	No	No
PID	Patient Identification	Yes	No
NTE	Notes and Comments	No	Yes
RGR_RGR.ORDER	Order group	Yes	Yes
ORC	Common Order	Yes	No
RGR_RGR.ENCODING	Encoding group	No	No
RXE	Pharmacy/Treatment Encoded Order	Yes	No
RXR	Pharmacy/Treatment Route	Yes	Yes
RXC	Pharmacy/Treatment Component Order	No	Yes
RXG	Pharmacy/Treatment Give	Yes	Yes
RXR	Pharmacy/Treatment Route	Yes	Yes
RXC	Pharmacy/Treatment Component Order	No	Yes
DSC	Continuation Pointer	No	No

RGR_RGR returns pharmacy or treatment dose information in response to an original-style query. It is closest to the "give" side of pharmacy messaging, similar in content to RGV_O15, but used as a response to a query rather than an unsolicited event.

Use it when the requester needs scheduled or recorded give-level dose detail: what should be given, how much, by what route, and with which components.

A small RGR RGR example

MSH|^~\&|PHARMACY|CITYHOSP|EHR|CITYHOSP|20260723133000||RGR^RGR^RGR_RGR|RGR00001|P|2.5.1 MSA|AA|QRYRGR001 QRD|20260723132900|R|I|QRYRGR001|||1^RD|123456^^^CITYHOSP^MR|RXG^Dose query^L|PHARMACY|T PID|1||123456^^^CITYHOSP^MR||Rivera^Maya^^^^^L||19750519|F ORC|RE|ORD448811^EHR|RX990201^PHARMACY|GRP448811|CM RXE||AMOX500^Amoxicillin 500 mg capsule^L|500||mg^milligram^UCUM|CAP^Capsule^L RXR|PO^Oral^HL70162 RXG|1||BID^Twice daily^HL70335|AMOX500^Amoxicillin 500 mg capsule^L|500||mg^milligram^UCUM|CAP^Capsule^L RXR|PO^Oral^HL70162

What workflow it represents

The requester asks for dose or give information, and the pharmacy/treatment system returns one or more give rows for the matching order. That can support dose schedule display, reconciliation, or downstream clinical decision support.

The response is only as safe as the profile around it. Dose, route, timing, and units need to survive intact.

How to read the structure

The response envelope is MSH, required MSA, optional ERR, and optional SFT.

Each DEFINITION group uses QRD and optional QRF, then optional patient context and repeating order detail.

The ORDER group starts with ORC. Optional encoded order context uses RXE, RXR, and RXC. Repeating required RXG rows carry the give or dose details, followed by route in RXR and optional components in RXC.

Implementation traps

Give amount, units, and route should be treated as a bundle. A dose value without units, or a route without the correct coding system, is not safe enough for clinical use.

Do not assume RXG timing means the same thing as the original order timing. Pharmacy/treatment systems often have the authority to encode the practical give schedule.

If the response contains both RXE and RXG, be clear which values are order context and which values are the actual give rows being returned.

Reference notes

HL7 v2.5.1 query listings identify RGR_RGR as pharmacy/treatment dose information. The structure returns query context plus ORC-led orders with RXG dose rows, route detail, and optional components.