OMD: Dietary order
This page lists the structures and trigger events OMD defines, taken from the standard. The written commentary that theADT page carries has not been written for OMD.
Recognising OMD messages
OMD announces itself in MSH-9 like this:
OMD^O03^OMD_O03- MSH-9.1
OMDmessage code: what kind of message this is - MSH-9.2
O03trigger event: what happened in the real world: dietary order - MSH-9.3
OMD_O03message 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
OMD takes 1 structure.
OMD_O03: Dietary Order
Sent when one thing happens: O03: Dietary Order.
You must always send: MSH, ORC. 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 7 segments, repeated together | O | 0..1 |
| PIDin PATIENT | R | 1..1 | |
| PD1in PATIENT | O | 0..1 | |
| NTEin 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 | |
| INSURANCEin PATIENT | a group of 3 segments, repeated together | O | 0..* |
| IN1in INSURANCE | R | 1..1 | |
| IN2in INSURANCE | O | 0..1 | |
| IN3in INSURANCE | O | 0..1 | |
| GT1in PATIENT | O | 0..1 | |
| AL1in PATIENT | O | 0..* | |
| ORDER_DIET | a group of 3 segments, repeated together | R | 1..* |
| ORC | R | 1..1 | |
| TIMING_DIET | a group of 2 segments, repeated together | O | 0..* |
| TQ1in TIMING_DIET | R | 1..1 | |
| TQ2in TIMING_DIET | O | 0..* | |
| DIET | a group of 3 segments, repeated together | O | 0..1 |
| ODSin DIET | R | 1..* | |
| NTEin DIET | O | 0..* | |
| OBSERVATIONin DIET | a group of 2 segments, repeated together | O | 0..* |
| OBXin OBSERVATION | R | 1..1 | |
| NTEin OBSERVATION | O | 0..* | |
| ORDER_TRAY | a group of 4 segments, repeated together | O | 0..* |
| ORCin ORDER_TRAY | R | 1..1 | |
| TIMING_TRAYin ORDER_TRAY | a group of 2 segments, repeated together | O | 0..* |
| TQ1in TIMING_TRAY | R | 1..1 | |
| TQ2in TIMING_TRAY | O | 0..* | |
| ODTin ORDER_TRAY | R | 1..* | |
| NTEin ORDER_TRAY | 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 9 such groups: PATIENT, PATIENT_VISIT, INSURANCE, ORDER_DIET, TIMING_DIET, DIET, OBSERVATION, ORDER_TRAY, TIMING_TRAY.
Trigger events
The trigger event is the real-world thing that made the message get sent. OMD defines 1.
| Event | Name | Structure |
|---|---|---|
| O03 | Dietary Order | OMD_O03 |