OMI: Imaging order
This page lists the structures and trigger events OMI defines, taken from the standard. The written commentary that theADT page carries has not been written for OMI.
Recognising OMI messages
OMI announces itself in MSH-9 like this:
OMI^O23^OMI_O23- MSH-9.1
OMImessage code: what kind of message this is - MSH-9.2
O23trigger event: what happened in the real world: imaging order message - MSH-9.3
OMI_O23message 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
OMI takes 1 structure.
OMI_O23: Imaging Order Message
Sent when one thing happens: O23: Imaging Order Message.
You must always send: MSH, ORC, OBR, IPC. 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 Results) | 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 Results) | 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 8 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..* |
| OBR | Observation | R | 1..1 |
| NTE | Notes and Comments (for Results) | O | 0..* |
| CTD | Contact Data | O | 0..1 |
| DG1 | Diagnosis | O | 0..* |
| OBSERVATION | a group of 2 segments, repeated together | O | 0..* |
| OBXin OBSERVATION | Observation/Result | R | 1..1 |
| NTEin OBSERVATION | Notes and Comments (for Results) | O | 0..* |
| IPC | Imaging Procedure Control | R | 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 6 such groups: PATIENT, PATIENT_VISIT, INSURANCE, ORDER, TIMING, OBSERVATION.
Trigger events
The trigger event is the real-world thing that made the message get sent. OMI defines 1.
| Event | Name | Structure |
|---|---|---|
| O23 | Imaging Order Message | OMI_O23 |