HL7 OMS_O05 (Stock Requisition Order) | Integration Soup HL7 Reference Guide

HL7 OMS_O05 Stock Requisition Order

An order message for requesting stocked supplies or materials.

HL7 message structure OMS_O05 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
NTE	Notes and Comments	No	Yes
OMS_O05.PATIENT	Patient group	No	No
PID	Patient Identification	Yes	No
PD1	Patient Additional Demographic	No	No
NTE	Notes and Comments	No	Yes
OMS_O05.PATIENT_VISIT	Patient Visit group	No	No
PV1	Patient Visit	Yes	No
PV2	Patient Visit - Additional Information	No	No
OMS_O05.INSURANCE	Insurance group	No	Yes
IN1	Insurance	Yes	No
IN2	Insurance Additional Information	No	No
IN3	Insurance Additional Information, Certification	No	No
GT1	Guarantor	No	No
AL1	Patient Allergy Information	No	Yes
OMS_O05.ORDER	Order group	Yes	Yes
ORC	Common Order	Yes	No
OMS_O05.TIMING	Timing group	No	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
RQD	Requisition Detail	Yes	No
RQ1	Requisition Detail-1	No	No
NTE	Notes and Comments	No	Yes
OMS_O05.OBSERVATION	Observation group	No	Yes
OBX	Observation/Result	Yes	No
NTE	Notes and Comments	No	Yes
BLG	Billing	No	No

OMS_O05 is a stock requisition order. It is used when a department, ward, clinic, or service requests an item that the receiving system treats as stocked inventory. The business question is not "perform this clinical service"; it is "fulfill this stock request."

OMS uses the order wrapper you already know from other order messages: ORC for order control and identifiers, then RQD and optional RQ1 for the requisition item details.

A small OMS O05 example

MSH|^~\&|WARDSTOCK|CITYHOSP|SUPPLY|CITYHOSP|20260717121000||OMS^O05^OMS_O05|OMS050001|P|2.5.1 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L PV1|1|I|WARD3^312^A^CITYHOSP ORC|NW|REQ5001^WARDSTOCK||||||20260717121000|||12345^Careful^Clara TQ1|1||||||20260717160000 RQD|1|GLOVE-M^Medium exam gloves^INV||HOSP-GLOVE-M^Medium exam gloves^L|4|BOX|WARD3|651200|SUPPLYROOM^Main supply room^L|20260717 RQ1|12.50|ACME^Acme Medical^L|GM-200|SUPPLYVENDOR^Supply Vendor^L|ACME-GM-200|N|Y BLG|WARD3^Ward cost center^L

What workflow it represents

The sender wants the receiving supply or inventory system to pick, allocate, deliver, or reserve stocked material. The receiver may respond with ORS_O06, assign a filler requisition number, or update the request state in its own workflow.

Stock requisitions live close to inventory counts and cost centers. Quantities, units, item codes, and delivery location need to be clean enough for fulfillment staff and inventory software to agree.

How to read the structure

The optional patient group can appear when the requisition belongs to a patient context, but many stock workflows are department-driven. The required ORDER group starts with ORC, may include timing, and then requires RQD. RQ1 adds manufacturer, vendor, catalog, taxable, and substitution details when needed.

Optional OBX segments can support the request, while BLG carries billing or charging context. Keep clinical notes and inventory identifiers in their own places; do not bury a catalog number in a comment.

Implementation traps

The main trap is unit mismatch. Four boxes, four each, and four cases are three different orders. RQD-5 and RQD-6 need to travel together and match the receiver's unit vocabulary.

Another trap is item-code drift. If the sender uses one internal code and the receiver fulfills using another, preserve both when possible and document which one is authoritative for matching.

Reference notes

The HL7 v2+ OMS_O05 material notes that stock requisitions can also use ORM with RQD for backward compatibility, while OMS and ORS provide dedicated stock requisition order and acknowledgment structures.