HL7 ORP_O10 (Pharmacy/Treatment Order Acknowledgment) | Integration Soup HL7 Reference Guide

HL7 ORP_O10 Pharmacy/Treatment Order Acknowledgment

The pharmacy answers an OMP order with status, identifiers, and sometimes corrected detail.

HL7 message structure ORP_O10 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
NTE	Notes and Comments	No	Yes
ORP_O10.RESPONSE	Response group	No	No
ORP_O10.PATIENT	Patient group	No	No
PID	Patient Identification	Yes	No
NTE	Notes and Comments	No	Yes
ORP_O10.ORDER	Order group	Yes	Yes
ORC	Common Order	Yes	No
ORP_O10.TIMING	Timing group	No	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
ORP_O10.ORDER_DETAIL	Order Detail group	No	No
RXO	Pharmacy/Treatment Order	Yes	No
NTE	Notes and Comments	No	Yes
RXR	Pharmacy/Treatment Route	Yes	Yes
ORP_O10.COMPONENT	Component group	No	Yes
RXC	Pharmacy/Treatment Component Order	Yes	No
NTE	Notes and Comments	No	Yes

ORP_O10 is the application response to an OMP_O09 pharmacy/treatment order. It lets the pharmacy or treatment system acknowledge the order message and return order-level outcome, identifiers, or detail needed by the placer.

The message starts like other application responses with MSH, MSA, and optional ERR. The order response then uses ORC, optional timing, and optional medication detail in RXO, RXR, and RXC.

A small ORP pharmacy acknowledgment example

MSH|^~\&|PHARM|CITYHOSP|EHR|CITYHOSP|20260718110003||ORP^O10^ORP_O10|ORP100001|P|2.5.1 MSA|AA|OMP090001 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L ORC|OK|RX550001^EHR|PHARM880001^PHARM||||||20260718110003 TQ1|1|1^dose|QID^Four times daily^HL70335|||20260718120000 RXO|AMOX500^Amoxicillin 500 mg capsule^L|500|mg|PO^Oral^HL70162 RXR|PO^Oral^HL70162

What systems do with it

The pharmacy sends ORP_O10 after it evaluates an OMP order. The placer can use it to show accepted/rejected status, store the pharmacy order number, display warnings, or send the user back to fix an order that the pharmacy cannot process.

For rejected orders, ERR should say what actually failed: medication code, route, dose, formulary status, allergy rule, duplicate therapy, timing, or another local business rule.

How to read the structure

MSA is message acknowledgment. ORC is order outcome. RXO/RXR/RXC are optional response detail, but they are useful when the pharmacy returns the normalized medication order it accepted or the detail it wants the placer to reconcile.

Do not file ORP as a dispense, administration, or medication history event. It acknowledges the order. Other pharmacy message families handle dispense, administration, and treatment history workflows.

Implementation traps

Ignoring ORP turns pharmacy into a black box. The placer may show an order as active while the pharmacy rejected it or accepted it under a different identifier.

Also be clear about what OK, UA, CR, and similar ORC control values mean in your local medication workflow. Pharmacy status language can drift between ordering, dispensing, and administration systems.

Reference notes

HL7 describes ORP_O10 as the pharmacy/treatment order acknowledgment message and shows the ORC/RXO/RXR/RXC response detail groups. See HL7 Europe ORP_O10.