RER: Pharmacy/treatment encoded order information
This page lists the structures and trigger events RER defines, taken from the standard. The written commentary that theADT page carries has not been written for RER.
Recognising RER messages
RER announces itself in MSH-9 like this:
RER^RER^RER_RER- MSH-9.1
RERmessage code: what kind of message this is - MSH-9.2
RERtrigger event: what happened in the real world - MSH-9.3
RER_RERmessage 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
RER takes 1 structure.
RER_RER
Sent when one thing happens: RER: RER.
You must always send: MSH, MSA, QRD, ORC, RXE, RXR. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| MSA | R | 1..1 | |
| ERR | O | 0..* | |
| SFT | O | 0..* | |
| DEFINITION | a group of 4 segments, repeated together | R | 1..* |
| QRD | R | 1..1 | |
| QRF | O | 0..1 | |
| PATIENT | a group of 2 segments, repeated together | O | 0..1 |
| PIDin PATIENT | R | 1..1 | |
| NTEin PATIENT | O | 0..* | |
| ORDER | a group of 4 segments, repeated together | R | 1..* |
| ORC | R | 1..1 | |
| RXE | R | 1..1 | |
| RXR | R | 1..* | |
| RXC | O | 0..* | |
| DSC | O | 0..1 |
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 3 such groups: DEFINITION, PATIENT, ORDER.
Trigger events
The trigger event is the real-world thing that made the message get sent. RER defines 1.
| Event | Name | Structure |
|---|---|---|
| RER | RER | RER_RER |