OMS: Stock requisition order message
This page lists the structures and trigger events OMS defines, taken from the standard. The written commentary that theADT page carries has not been written for OMS.
Recognising OMS messages
OMS announces itself in MSH-9 like this:
OMS^O05^OMS_O05- MSH-9.1
OMSmessage code: what kind of message this is - MSH-9.2
O05trigger event: what happened in the real world: stock requisition order message - MSH-9.3
OMS_O05message 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
OMS takes 1 structure.
OMS_O05: stock requisition order message
Sent when one thing happens: O05: stock requisition order message.
You must always send: MSH, ORC, RQD. 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 OBX) | 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 OBX) | 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 7 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..* |
| RQD | Requisition Detail | R | 1..1 |
| RQ1 | Requisition Detail-1 | O | 0..1 |
| NTE | Notes and Comments (for OBX) | 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 OBX) | O | 0..* |
| BLG | Billing Segment | 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 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. OMS defines 1.
| Event | Name | Structure |
|---|---|---|
| O05 | stock requisition order message | OMS_O05 |