HL7 RQ1 Requisition Detail-1
HL7 field reference RQ1 fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
RQ1 carries additional requisition detail, usually around supplies or service-specific request information.
The standard describes RQ1 this way: RQ1 contains additional detail for each nonstock requisitioned item. This segment definition is paired with a preceding RQD segment.
These segments describe clinical goals, problems, roles, referrals, requisitions, incidents, variances, and resource groupings that sit around the core patient/order/result traffic.
They are most useful when responsibilities, dates, identifiers, and status values are kept explicit. Otherwise they become narrative fragments that are hard to act on.
The v2.5.1 structures show RQ1 in OMN_O07 - OMN - Non-stock requisition order, OMS_O05 - OMS - Stock requisition order, ORN_O08 - ORN - Non-stock requisition acknowledgment, and ORS_O06 - ORS - Stock requisition acknowledgment. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
RQ1-1 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
RQ1-2 identifies the Manufacturer Identifier for this care-plan or referral workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0385; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RQ1-3 helps identify the product, software, device, or equipment involved. It is particularly useful when support needs to trace behaviour back to a specific build, lot, instrument, or manufacturer.
RQ1-4 identifies the Vendor ID for this care-plan or referral workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
RQ1-5 carries Vendor Catalog for this care-plan or referral workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
RQ1-6 carries Taxable for this care-plan or referral workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0136; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RQ1-7 carries Substitute Allowed for this care-plan or referral workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0136; many real interfaces narrow that list further, so follow the receiver's implementation guide.