HL7 RQD Requisition Detail
HL7 field reference RQD 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
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| RQD.1 | Requisition Line Number | No | No | SI | |
| RQD.2 | Item Code - Internal | No | No | CE | |
| RQD.3 | Item Code - External | No | No | CE | |
| RQD.4 | Hospital Item Code | No | No | CE | |
| RQD.5 | Requisition Quantity | No | No | NM | |
| RQD.6 | Requisition Unit of Measure | No | No | CE | |
| RQD.7 | Dept. Cost Center | No | No | IS | 0319 |
| RQD.8 | Item Natural Account Code | No | No | IS | 0320 |
| RQD.9 | Deliver To ID | No | No | CE | |
| RQD.10 | Date Needed | No | No | DT |
RQD carries requisition detail for requested supplies, services, or resources.
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 RQD 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.
RQD-1 identifies the Requisition Line Number 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.
RQD-2 carries Item Code - Internal 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.
RQD-3 carries Item Code - External 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.
RQD-4 identifies the Hospital Item Code 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.
RQD-5 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.
RQD-6 carries Requisition Unit of Measure 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.
RQD-7 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.
The generated panel links this to HL7 table 0319; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RQD-8 is used for reconciliation. The receiver may compare it with the segments, batches, messages, rows, or items actually received, so do not populate it from a stale estimate.
The generated panel links this to HL7 table 0320; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RQD-9 identifies the Deliver To 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.
RQD-10 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.