HL7 ROR_ROR (Pharmacy Prescription Order Query Response) | Integration Soup HL7 Reference Guide

HL7 ROR_ROR Pharmacy Prescription Order Query Response

The old-style query response for the requested pharmacy order.

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

ROR_ROR returns pharmacy prescription order information in response to an original-style query. It answers the question, "what was ordered?" using the requested-order view in RXO.

That makes it different from RER_RER, which returns pharmacy's encoded order view, and different again from RDR_RDR or RAR_RAR, which return dispense or administration facts.

A small ROR ROR example

MSH|^~\&|PHARMACY|CITYHOSP|EHR|CITYHOSP|20260723134000||ROR^ROR^ROR_ROR|ROR00001|P|2.5.1 MSA|AA|QRYROR001 QRD|20260723133900|R|I|QRYROR001|||1^RD|123456^^^CITYHOSP^MR|RXO^Prescription order query^L|PHARMACY|T PID|1||123456^^^CITYHOSP^MR||Rivera^Maya^^^^^L||19750519|F ORC|RE|ORD448811^EHR|RX990201^PHARMACY|GRP448811|CM RXO|AMOX500^Amoxicillin 500 mg capsule^L|500||mg^milligram^UCUM|CAP^Capsule^L|TAKE WITH FOOD^Take with food^L RXR|PO^Oral^HL70162 RXC|A^Additive^HL70166|CLAV125^Clavulanate 125 mg^L|125|mg^milligram^UCUM

What workflow it represents

The requester wants prescription order detail. The responding system returns order identity, patient context when needed, requested medication or treatment detail, routes, and optional component rows.

Use this response for order display or reconciliation. Do not treat it as a new order transaction unless the interface profile explicitly says so.

How to read the structure

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

Each DEFINITION group contains QRD, optional QRF, optional patient context, and one or more ORDER groups.

Each ORDER group starts with ORC, then required RXO for the requested pharmacy/treatment order, repeating RXR for route choices, and optional RXC for components or additives.

Implementation traps

ROR_ROR returns the requested-order view. If the pharmacy substituted, encoded, dispensed, or administered something different, that belongs in the related encoded, dispense, dose, or administration response.

Preserve order identifiers from ORC. They are the only sane way to join the returned order to dispense, give, and administration information later.

RXO often looks simple until compounds appear. If RXC rows are present, keep the component detail with the parent order rather than flattening it into a display string.

Reference notes

HL7 v2.5.1 query listings identify ROR_ROR as the pharmacy prescription order query response. The structure returns QRD/QRF query context with ORC, RXO, RXR, and RXC order detail.