HL7 RXD Pharmacy/Treatment Dispense
HL7 field reference RXD 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 |
|---|---|---|---|---|---|
| RXD.1 | Dispense Sub-ID Counter | Yes | No | NM | |
| RXD.2 | Dispense/Give Code | Yes | No | CE | 0292 |
| RXD.3 | Date/Time Dispensed | Yes | No | TS | |
| RXD.4 | Actual Dispense Amount | Yes | No | NM | |
| RXD.5 | Actual Dispense Units | No | No | CE | |
| RXD.6 | Actual Dosage Form | No | No | CE | |
| RXD.7 | Prescription Number | Yes | No | ST | |
| RXD.8 | Number of Refills Remaining | No | No | NM | |
| RXD.9 | Dispense Notes | No | Yes | ST | |
| RXD.10 | Dispensing Provider | No | Yes | XCN | |
| RXD.11 | Substitution Status | No | No | ID | 0167 |
| RXD.12 | Total Daily Dose | No | No | CQ | |
| RXD.13 | Dispense-to Location | No | No | LA2 | |
| RXD.14 | Needs Human Review | No | No | ID | 0136 |
| RXD.15 | Pharmacy/Treatment Supplier's Special Dispensing Instructions | No | Yes | CE | |
| RXD.16 | Actual Strength | No | No | NM | |
| RXD.17 | Actual Strength Unit | No | No | CE | |
| RXD.18 | Substance Lot Number | No | Yes | ST | |
| RXD.19 | Substance Expiration Date | No | Yes | TS | |
| RXD.20 | Substance Manufacturer Name | No | Yes | CE | 0227 |
| RXD.21 | Indication | No | Yes | CE | |
| RXD.22 | Dispense Package Size | No | No | NM | |
| RXD.23 | Dispense Package Size Unit | No | No | CE | |
| RXD.24 | Dispense Package Method | No | No | ID | 0321 |
| RXD.25 | Supplementary Code | No | Yes | CE | |
| RXD.26 | Initiating Location | No | No | CE | |
| RXD.27 | Packaging/Assembly Location | No | No | CE | |
| RXD.28 | Actual Drug Strength Volume | No | No | NM | |
| RXD.29 | Actual Drug Strength Volume Units | No | No | CWE | |
| RXD.30 | Dispense to Pharmacy | No | No | CWE | |
| RXD.31 | Dispense to Pharmacy Address | No | No | XAD | |
| RXD.32 | Pharmacy Order Type | No | No | ID | 0480 |
| RXD.33 | Dispense Type | No | No | CWE | 0484 |
RXD records pharmacy dispense detail: what was dispensed, quantity, timing, lot, package, and pharmacy handling.
The standard describes RXD this way: This is the master pharmacy/treatment order segment.It contains order data not specific to components or additives.Unlike the OBR, it does not contain status fields or other data that are results-only.
Pharmacy/treatment segments split a medication workflow into ordered, encoded, dispensed, administered, component, route, timing, and instruction details.
Be very clear about whether a field describes what was ordered, what the pharmacy dispensed, what was scheduled to be given, or what was actually administered. Those are related, but they are not the same event.
The v2.5.1 structures show RXD in RDR_RDR - Pharmacy/treatment dispense information, RDS_O13 - RDS - Pharmacy/treatment dispense, RRD_O14 - RRD - Pharmacy/treatment dispense acknowledgment, and RSP_K31 - RSP -Dispense History Response, and 3 other message structures. 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.
RXD-1 distinguishes repeated administration or give rows inside the same order context. Treat it as a row-level counter, not as the medication code, order number, or dispense identifier.
RXD-2 identifies the Dispense/Give Code for this pharmacy 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 0292; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RXD-3 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.
RXD-4 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.
RXD-5 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXD-6 carries Actual Dosage Form for this pharmacy 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.
RXD-7 identifies the Prescription Number for this pharmacy 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.
RXD-8 is a count or total for this pharmacy workflow. Make the counting rule explicit before using it for reconciliation, billing, or workflow limits.
RXD-9 is human-readable context. Keep it useful for display and troubleshooting, but do not hide required workflow logic here unless the implementation guide explicitly says the receiver parses it.
Because the field can repeat, separate distinct statements into separate repetitions instead of creating one long hard-to-parse block.
RXD-10 identifies a person, provider, staff member, or contact involved in this pharmacy workflow. Use the structured name or provider datatype instead of flattening everything into display text.
When more than one person is sent, repeats should carry role or identifier context so the receiver can tell who did what.
RXD-11 tells the receiver the state of this pharmacy workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0167 or the narrower table in the local profile.
RXD-12 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.
RXD-13 places the pharmacy workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
RXD-14 carries Needs Human Review for this pharmacy 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.
RXD-15 is human-readable context. Keep it useful for display and troubleshooting, but do not hide required workflow logic here unless the implementation guide explicitly says the receiver parses it.
Because the field can repeat, separate distinct statements into separate repetitions instead of creating one long hard-to-parse block.
RXD-16 carries Actual Strength for this pharmacy 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.
RXD-17 carries Actual Strength Unit for this pharmacy 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.
RXD-18 identifies the Substance Lot Number for this pharmacy 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.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
RXD-19 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.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
RXD-20 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.
If more than one identifier is sent, each repetition should stay attached to the product or device context it belongs to.
RXD-21 carries Indication for this pharmacy 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.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
RXD-22 belongs to the medication/treatment workflow. Be explicit about whether the value describes the original order, encoded order, dispense event, scheduled give, or actual administration.
RXD-23 belongs to the medication/treatment workflow. Be explicit about whether the value describes the original order, encoded order, dispense event, scheduled give, or actual administration.
RXD-24 qualifies the pharmacy workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0321. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
RXD-25 identifies the Supplementary Code for this pharmacy 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.
If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.
RXD-26 places the pharmacy workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
RXD-27 places the pharmacy workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
RXD-28 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.
RXD-29 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXD-30 belongs to the medication/treatment workflow. Be explicit about whether the value describes the original order, encoded order, dispense event, scheduled give, or actual administration.
RXD-31 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
RXD-32 qualifies the pharmacy workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0480. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
RXD-33 qualifies the pharmacy workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0484. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
Related links
- RXO - Pharmacy/Treatment Order
- RXE - Pharmacy/Treatment Encoded Order
- RXC - Pharmacy/Treatment Component Order
- RXG - Pharmacy/Treatment Give
- RXA - Pharmacy/Treatment Administration
- RXR - Pharmacy/Treatment Route
- TQ1 - Timing/Quantity
- ORC - Common Order
- RDR_RDR - Pharmacy/treatment dispense information
- RDS_O13 - RDS - Pharmacy/treatment dispense