HL7 RDR_RDR (Pharmacy/Treatment Dispense Information) | Integration Soup HL7 Reference Guide

HL7 RDR_RDR Pharmacy/Treatment Dispense Information

The old-style query response for what pharmacy dispensed.

HL7 message structure RDR_RDR 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
RDR_RDR.DEFINITION	Definition group	Yes	Yes
QRD	Original-Style Query Definition	Yes	No
QRF	Original style query filter	No	No
RDR_RDR.PATIENT	Patient group	No	No
PID	Patient Identification	Yes	No
NTE	Notes and Comments	No	Yes
RDR_RDR.ORDER	Order group	Yes	Yes
ORC	Common Order	Yes	No
RDR_RDR.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
RDR_RDR.DISPENSE	Dispense group	Yes	Yes
RXD	Pharmacy/Treatment Dispense	Yes	No
RXR	Pharmacy/Treatment Route	Yes	Yes
RXC	Pharmacy/Treatment Component Order	No	Yes
DSC	Continuation Pointer	No	No

RDR_RDR returns pharmacy or treatment dispense information in response to an original-style query. It is the pull-style answer for data that is otherwise reported through dispense workflows such as RDS_O13.

Use it when a receiver asks for medication dispense history, fill details, or dispense records for a patient or order.

A small RDR RDR example

MSH|^~\&|PHARMACY|CITYHOSP|EHR|CITYHOSP|20260723131000||RDR^RDR^RDR_RDR|RDR00001|P|2.5.1 MSA|AA|QRYRDR001 QRD|20260723130900|R|I|QRYRDR001|||1^RD|123456^^^CITYHOSP^MR|RXD^Dispense history^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 RXD|1|AMOX500^Amoxicillin 500 mg capsule^L|20260723083000|14|CAP^Capsule^L|CAP^Capsule^L|RX990201|0 RXR|PO^Oral^HL70162

What workflow it represents

A requesting system asks for dispense information, and the pharmacy/treatment application returns matching dispense records. Receivers often use this for reconciliation, medication history display, or checking whether a medication was actually supplied.

This response should not be treated as an order. It is a statement about what was dispensed.

How to read the structure

The envelope uses MSH, required MSA, optional ERR, and optional SFT.

Each DEFINITION group starts with QRD and optional QRF. Patient identity is optional in the structure but practically important when responses cross patient contexts.

Each ORDER group begins with ORC. Optional encoded order context uses RXE, RXR, and RXC. Repeating DISPENSE groups carry required RXD, route in RXR, and optional component detail in RXC.

Implementation traps

Dispensed is not administered. RXD tells you the pharmacy or treatment application supplied something; it does not prove the patient received it.

Preserve prescription number, dispense date/time, amount, units, and refills. Those fields are often what reconciliation workflows actually need.

As with the other old-style query responses, continuation is not optional in practice if the responder can return more rows than fit in one message.

Reference notes

HL7 v2.5.1 query listings identify RDR_RDR as pharmacy/treatment dispense information. The response structure returns QRD/QRF query context plus ORC-led orders with RXD dispense groups.