RAS: Pharmacy/treatment administration message
This page lists the structures and trigger events RAS defines, taken from the standard. The written commentary that theADT page carries has not been written for RAS.
Recognising RAS messages
RAS announces itself in MSH-9 like this:
RAS^O17^RAS_O17- MSH-9.1
RASmessage code: what kind of message this is - MSH-9.2
O17trigger event: what happened in the real world: pharmacy/treatment administration message - MSH-9.3
RAS_O17message 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
RAS takes 1 structure.
RAS_O17: Pharmacy/Treatment Administration Message
Sent when one thing happens: O17: Pharmacy/Treatment Administration Message.
You must always send: MSH, ORC, RXA, RXR. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| NTE | O | 0..* | |
| PATIENT | a group of 5 segments, repeated together | O | 0..1 |
| PIDin PATIENT | R | 1..1 | |
| PD1in PATIENT | O | 0..1 | |
| NTEin PATIENT | O | 0..* | |
| AL1in PATIENT | O | 0..* | |
| PATIENT_VISITin PATIENT | a group of 2 segments, repeated together | O | 0..1 |
| PV1in PATIENT_VISIT | R | 1..1 | |
| PV2in PATIENT_VISIT | O | 0..1 | |
| ORDER | a group of 6 segments, repeated together | R | 1..* |
| ORC | R | 1..1 | |
| TIMING | a group of 2 segments, repeated together | O | 0..* |
| TQ1in TIMING | R | 1..1 | |
| TQ2in TIMING | O | 0..* | |
| ORDER_DETAIL | a group of 2 segments, repeated together | O | 0..1 |
| RXOin ORDER_DETAIL | R | 1..1 | |
| ORDER_DETAIL_SUPPLEMENTin ORDER_DETAIL | a group of 3 segments, repeated together | O | 0..1 |
| NTEin ORDER_DETAIL_SUPPLEMENT | R | 1..* | |
| RXRin ORDER_DETAIL_SUPPLEMENT | R | 1..* | |
| COMPONENTSin ORDER_DETAIL_SUPPLEMENT | a group of 2 segments, repeated together | O | 0..* |
| RXCin COMPONENTS | R | 1..1 | |
| NTEin COMPONENTS | O | 0..* | |
| ENCODING | a group of 4 segments, repeated together | O | 0..1 |
| RXEin ENCODING | R | 1..1 | |
| TIMING_ENCODEDin ENCODING | a group of 2 segments, repeated together | R | 1..* |
| TQ1in TIMING_ENCODED | R | 1..1 | |
| TQ2in TIMING_ENCODED | O | 0..* | |
| RXRin ENCODING | R | 1..* | |
| RXCin ENCODING | O | 0..* | |
| ADMINISTRATION | a group of 3 segments, repeated together | R | 1..* |
| RXA | R | 1..* | |
| RXR | R | 1..1 | |
| OBSERVATION | a group of 2 segments, repeated together | O | 0..* |
| OBXin OBSERVATION | R | 1..1 | |
| NTEin OBSERVATION | O | 0..* | |
| CTI | 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 11 such groups: PATIENT, PATIENT_VISIT, ORDER, TIMING, ORDER_DETAIL, ORDER_DETAIL_SUPPLEMENT, COMPONENTS, ENCODING, TIMING_ENCODED, ADMINISTRATION, OBSERVATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. RAS defines 1.
| Event | Name | Structure |
|---|---|---|
| O17 | Pharmacy/Treatment Administration Message | RAS_O17 |