RDS: Pharmacy/treatment dispense message
This page lists the structures and trigger events RDS defines, taken from the standard. The written commentary that theADT page carries has not been written for RDS.
Recognising RDS messages
RDS announces itself in MSH-9 like this:
RDS^O13^RDS_O13- MSH-9.1
RDSmessage code: what kind of message this is - MSH-9.2
O13trigger event: what happened in the real world: pharmacy/treatment dispense message - MSH-9.3
RDS_O13message 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
RDS takes 1 structure.
RDS_O13: Pharmacy/Treatment Dispense Message
Sent when one thing happens: O13: Pharmacy/Treatment Dispense Message.
You must always send: MSH, ORC, RXD, 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 5 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..* |
| AL1in PATIENT | Allergy Information | 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 |
| ORDER | a group of 10 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 2 segments, repeated together | O | 0..1 |
| RXOin ORDER_DETAIL | Pharmacy /Treatment Order | R | 1..1 |
| ORDER_DETAIL_SUPPLEMENTin ORDER_DETAIL | a group of 3 segments, repeated together | O | 0..1 |
| NTEin ORDER_DETAIL_SUPPLEMENT | Notes and Comments (for OBX) | R | 1..* |
| RXRin ORDER_DETAIL_SUPPLEMENT | Pharmacy/Treatment Route | R | 1..* |
| COMPONENTin ORDER_DETAIL_SUPPLEMENT | a group of 2 segments, repeated together | O | 0..* |
| RXCin COMPONENT | Pharmacy/Treatment Component | R | 1..1 |
| NTEin COMPONENT | Notes and Comments (for OBX) | O | 0..* |
| ENCODING | a group of 5 segments, repeated together | O | 0..1 |
| RXEin ENCODING | Pharmacy/Treatment Encoded Order | R | 1..1 |
| NTEin ENCODING | Notes and Comments (for OBX) | O | 0..* |
| TIMING_ENCODEDin ENCODING | a group of 2 segments, repeated together | R | 1..* |
| TQ1in TIMING_ENCODED | Timing/Quantity | R | 1..1 |
| TQ2in TIMING_ENCODED | Timing/Quantity Order Sequence | O | 0..* |
| RXRin ENCODING | Pharmacy/Treatment Route | R | 1..* |
| RXCin ENCODING | Pharmacy/Treatment Component | O | 0..* |
| RXD | Pharmacy/Treatment Dispense | R | 1..1 |
| NTE | Notes and Comments (for OBX) | O | 0..* |
| RXR | Pharmacy/Treatment Route | R | 1..* |
| RXC | Pharmacy/Treatment Component | 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 Transaction segment | 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 10 such groups: PATIENT, PATIENT_VISIT, ORDER, TIMING, ORDER_DETAIL, ORDER_DETAIL_SUPPLEMENT, COMPONENT, ENCODING, TIMING_ENCODED, OBSERVATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. RDS defines 1.
| Event | Name | Structure |
|---|---|---|
| O13 | Pharmacy/Treatment Dispense Message | RDS_O13 |