HL7 ORS_O06 Stock Requisition Acknowledgment

The response that tells a stock-request sender what supply services accepted.
HL7 message structure ORS_O06 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

SegmentNameRequiredRepeatable
MSH
 Message Header Yes No
MSA
 Message Acknowledgment Yes No
ERR
 Error No Yes
SFT
 Software Segment No Yes
NTE
 Notes and Comments No Yes
ORS_O06.RESPONSE
 Response group No No
ORS_O06.PATIENT
 Patient group No No
PID
 Patient Identification Yes No
NTE
 Notes and Comments No Yes
ORS_O06.ORDER
 Order group Yes Yes
ORC
 Common Order Yes No
ORS_O06.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

ORS_O06 is the acknowledgment response for an OMS_O05 stock requisition. It tells the requester whether the stock request was accepted, rejected, or accepted with returned order detail.

It follows the same practical response pattern as other order acknowledgments: MSA confirms the message, ERR explains problems, and ORC carries the order-level acceptance and identifiers.

A small ORS O06 example

MSH|^~\&|SUPPLY|CITYHOSP|WARDSTOCK|CITYHOSP|20260717121003||ORS^O06^ORS_O06|ORS060001|P|2.5.1 MSA|AA|OMS050001 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L ORC|OK|REQ5001^WARDSTOCK|FUL7001^SUPPLY||||||20260717121002 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

What systems do with it

The requester uses ORS_O06 to update the requisition status and capture the receiver's filler number. If the supply system cannot fulfill the item, it should use ERR and order-level status clearly enough that a user can pick a substitute, correct the unit, or cancel the request.

In repeated stock workflows, this response is also an audit trail. It records what the supply system thought was requested and what it accepted.

How to read the structure

The response starts with MSH, MSA, optional ERR, optional software details, and notes. The optional RESPONSE group can include patient context and one or more ORDER groups. Each ORDER has ORC, optional timing, required RQD, optional RQ1, and notes.

ORC is the stateful piece. RQD repeats the item and quantity being acknowledged. RQ1 can echo manufacturer or vendor information if that detail affected fulfillment.

Implementation traps

Do not reduce the response to MSA alone if the requester needs the filler requisition ID. Without that ID, later updates and support calls will only have the sender's original request number.

Also be clear about partial fulfillment. If only two of four boxes can be supplied, the response should not look identical to a full acceptance.

Reference notes

The HL7 v2+ ORS_O06 page shows a stock requisition acknowledgment with MSA, ERR, an optional response group, and order detail built around ORC, RQD, and RQ1.