RDE: Pharmacy/treatment encoded order message
This page lists the structures and trigger events RDE defines, taken from the standard. The written commentary that theADT page carries has not been written for RDE.
Recognising RDE messages
RDE announces itself in MSH-9 like this:
RDE^O11^RDE_O11- MSH-9.1
RDEmessage code: what kind of message this is - MSH-9.2
O11trigger event: what happened in the real world: pharmacy/treatment encoded order message - MSH-9.3
RDE_O11message 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
RDE takes 1 structure.
RDE_O11: Pharmacy/Treatment Encoded Order Message
2 different trigger events send this structure:
- O11Pharmacy/Treatment Encoded Order Message
- O25Pharmacy/Treatment Refill Authorization Request Message
The segments below are the same for all 2. HL7 varies the meaning, not the shape: there is no separate RDE_O25 layout. What changes is MSH-9, which tells the receiver which of the 2 happened and therefore what to do with the message.
You must always send: MSH, ORC, RXE, TQ1, RXR. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | Message Header | R | 1..1 |
| SFT | Software | O | 0..* |
| NTE | Notes and Comments (for OBX) | O | 0..* |
| PATIENT | a group of 7 segments, repeated together | O | 0..1 |
| PIDin PATIENT | Patient Identification | R | 1..1 |
| PD1in PATIENT | Additional Demographics | O | 0..1 |
| NTEin PATIENT | Notes and Comments (for OBX) | O | 0..* |
| PATIENT_VISITin PATIENT | a group of 2 segments, repeated together | O | 0..1 |
| PV1in PATIENT_VISIT | Patient Visit | R | 1..1 |
| PV2in PATIENT_VISIT | Patient Visit – Additional Info | O | 0..1 |
| INSURANCEin PATIENT | a group of 3 segments, repeated together | O | 0..* |
| IN1in INSURANCE | Insurance | R | 1..1 |
| IN2in INSURANCE | Insurance Additional Info | O | 0..1 |
| IN3in INSURANCE | Insurance Add'l Info - Cert. | O | 0..1 |
| GT1in PATIENT | Guarantor | O | 0..1 |
| AL1in PATIENT | Allergy Information | O | 0..* |
| ORDER | a group of 12 segments, repeated together | R | 1..* |
| ORC | Common Order | R | 1..1 |
| TIMING | 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_DETAIL | a group of 4 segments, repeated together | O | 0..1 |
| RXOin ORDER_DETAIL | Pharmacy/Treatment Prescription Order | R | 1..1 |
| NTEin ORDER_DETAIL | Notes and Comments (for OBX) | 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 (for RXE) | R | 1..1 |
| NTEin COMPONENT | Notes and Comments (for OBX) | O | 0..* |
| RXE | Pharmacy/Treatment Encoded Order | R | 1..1 |
| NTE | Notes and Comments (for OBX) | O | 0..* |
| TIMING_ENCODED | a group of 2 segments, repeated together | R | 1..* |
| TQ1 | Timing/Quantity | R | 1..1 |
| TQ2 | Timing/Quantity Order Sequence | O | 0..* |
| RXR | Pharmacy/Treatment Route | R | 1..* |
| RXC | Pharmacy/Treatment Component (for RXE) | O | 0..* |
| OBSERVATION | a group of 2 segments, repeated together | O | 0..* |
| OBXin OBSERVATION | Results | R | 1..1 |
| NTEin OBSERVATION | Notes and Comments (for OBX) | O | 0..* |
| FT1 | Financial Detail | O | 0..* |
| BLG | Billing Segment | O | 0..1 |
| CTI | Clinical Trial Identification | 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 9 such groups: PATIENT, PATIENT_VISIT, INSURANCE, ORDER, TIMING, ORDER_DETAIL, COMPONENT, TIMING_ENCODED, OBSERVATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. RDE defines 2.
| Event | Name | Structure |
|---|---|---|
| O11 | Pharmacy/Treatment Encoded Order Message | RDE_O11 |
| O25 | Pharmacy/Treatment Refill Authorization Request Message | RDE_O11 |