ORL: Laboratory acknowledgment message (unsolicited)
This page lists the structures and trigger events ORL defines, taken from the standard. The written commentary that theADT page carries has not been written for ORL.
Recognising ORL messages
ORL announces itself in MSH-9 like this:
ORL^O22^ORL_O22- MSH-9.1
ORLmessage code: what kind of message this is - MSH-9.2
O22trigger event: what happened in the real world: general laboratory order response message to any oml - MSH-9.3
ORL_O22message 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
ORL takes 3 structures.
ORL_O22: general laboratory order response message to any OML
Sent when one thing happens: O22: general laboratory order response message to any OML.
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 | R | 1..1 | |
| MSA | R | 1..1 | |
| ERR | O | 0..* | |
| SFT | O | 0..* | |
| NTE | O | 0..* | |
| RESPONSE | a group of 1 segments, repeated together | O | 0..1 |
| PATIENTin RESPONSE | a group of 2 segments, repeated together | O | 0..1 |
| PIDin PATIENT | R | 1..1 | |
| ORDERin PATIENT | a group of 3 segments, repeated together | O | 0..* |
| ORCin ORDER | R | 1..1 | |
| TIMINGin ORDER | a group of 2 segments, repeated together | O | 0..* |
| TQ1in TIMING | R | 1..1 | |
| TQ2in TIMING | O | 0..* | |
| OBSERVATION_REQUESTin ORDER | a group of 2 segments, repeated together | O | 0..1 |
| OBRin OBSERVATION_REQUEST | R | 1..1 | |
| SPECIMENin OBSERVATION_REQUEST | a group of 2 segments, repeated together | O | 0..* |
| SPMin SPECIMEN | R | 1..1 | |
| SACin SPECIMEN | 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, OBSERVATION_REQUEST, SPECIMEN.
ORL_O34
Sent when one thing happens: O34: O34.
| 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 Header) | O | 0..* |
| RESPONSE | a group of 1 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 |
| SPECIMENin PATIENT | a group of 4 segments, repeated together | R | 1..* |
| SPMin SPECIMEN | Specimen | R | 1..1 |
| OBXin SPECIMEN | Observations related to specimen | O | 0..* |
| SACin SPECIMEN | Specimen Container Details | O | 0..* |
| ORDERin SPECIMEN | a group of 3 segments, repeated together | O | 0..* |
| 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..* |
| OBSERVATION_REQUESTin ORDER | a group of 2 segments, repeated together | O | 0..1 |
| OBRin OBSERVATION_REQUEST | Observation Request | R | 1..1 |
| ORL_O34.SPECIMENin OBSERVATION_REQUEST | 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, SPECIMEN, ORDER, TIMING, OBSERVATION_REQUEST.
ORL_O36
Sent when one thing happens: O36: O36.
| 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 Header) | O | 0..* |
| RESPONSE | a group of 1 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 |
| SPECIMENin PATIENT | a group of 3 segments, repeated together | R | 1..* |
| SPMin SPECIMEN | Specimen | R | 1..1 |
| OBXin SPECIMEN | Observations related to specimen | O | 0..* |
| SPECIMEN_CONTAINERin SPECIMEN | a group of 2 segments, repeated together | R | 1..* |
| SACin SPECIMEN_CONTAINER | Specimen Container | R | 1..1 |
| ORDERin SPECIMEN_CONTAINER | a group of 3 segments, repeated together | O | 0..* |
| 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..* |
| OBSERVATION_REQUESTin ORDER | a group of 1 segments, repeated together | O | 0..1 |
| OBRin OBSERVATION_REQUEST | Observation Request | R | 1..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 7 such groups: RESPONSE, PATIENT, SPECIMEN, SPECIMEN_CONTAINER, ORDER, TIMING, OBSERVATION_REQUEST.
Trigger events
The trigger event is the real-world thing that made the message get sent. ORL defines 3.
| Event | Name | Structure |
|---|---|---|
| O22 | general laboratory order response message to any OML | ORL_O22 |
| O34 | O34 | ORL_O34 |
| O36 | O36 | ORL_O36 |