ORP: Pharmacy/treatment order acknowledgment message
This page lists the structures and trigger events ORP defines, taken from the standard. The written commentary that theADT page carries has not been written for ORP.
Recognising ORP messages
ORP announces itself in MSH-9 like this:
ORP^O10^ORP_O10- MSH-9.1
ORPmessage code: what kind of message this is - MSH-9.2
O10trigger event: what happened in the real world: pharmacy/treatment order acknowledgment - MSH-9.3
ORP_O10message 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
ORP takes 1 structure.
ORP_O10: Pharmacy/Treatment Order Acknowledgment
Sent when one thing happens: O10: Pharmacy/Treatment Order Acknowledgment.
You must always send: MSH, MSA. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | Message Header | R | 1..1 |
| MSA | Message Acknowledgment | R | 1..1 |
| ERR | Error | O | 0..* |
| SFT | Software | O | 0..* |
| NTE | Notes and Comments (for each RXC) | O | 0..* |
| RESPONSE | a group of 2 segments, repeated together | O | 0..1 |
| PATIENTin RESPONSE | a group of 2 segments, repeated together | O | 0..1 |
| PIDin PATIENT | Patient Identification | R | 1..1 |
| NTEin PATIENT | Notes and Comments (for each RXC) | O | 0..* |
| ORDERin RESPONSE | a group of 3 segments, repeated together | R | 1..* |
| ORCin ORDER | Common Order | R | 1..1 |
| TIMINGin ORDER | a group of 2 segments, repeated together | O | 0..* |
| TQ1in TIMING | Timing/Quantity | R | 1..1 |
| TQ2in TIMING | Timing/Quantity Order Sequence | O | 0..* |
| ORDER_DETAILin ORDER | a group of 4 segments, repeated together | O | 0..1 |
| RXOin ORDER_DETAIL | Pharmacy/Treatment Order | R | 1..1 |
| NTEin ORDER_DETAIL | Notes and Comments (for each RXC) | O | 0..* |
| RXRin ORDER_DETAIL | Pharmacy/Treatment Route | R | 1..* |
| COMPONENTin ORDER_DETAIL | a group of 2 segments, repeated together | O | 0..* |
| RXCin COMPONENT | Pharmacy/Treatment Component | R | 1..1 |
| NTEin COMPONENT | Notes and Comments (for each RXC) | O | 0..* |
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 6 such groups: RESPONSE, PATIENT, ORDER, TIMING, ORDER_DETAIL, COMPONENT.
Trigger events
The trigger event is the real-world thing that made the message get sent. ORP defines 1.
| Event | Name | Structure |
|---|---|---|
| O10 | Pharmacy/Treatment Order Acknowledgment | ORP_O10 |