HL7 RXE Pharmacy/Treatment Encoded Order
HL7 field reference RXE 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 |
|---|---|---|---|---|---|
| RXE.1 | Quantity/Timing | No | No | TQ | |
| RXE.2 | Give Code | Yes | No | CE | 0292 |
| RXE.3 | Give Amount - Minimum | Yes | No | NM | |
| RXE.4 | Give Amount - Maximum | No | No | NM | |
| RXE.5 | Give Units | Yes | No | CE | |
| RXE.6 | Give Dosage Form | No | No | CE | |
| RXE.7 | Provider's Administration Instructions | No | Yes | CE | |
| RXE.8 | Deliver-To Location | No | No | LA1 | |
| RXE.9 | Substitution Status | No | No | ID | 0167 |
| RXE.10 | Dispense Amount | No | No | NM | |
| RXE.11 | Dispense Units | No | No | CE | |
| RXE.12 | Number Of Refills | No | No | NM | |
| RXE.13 | Ordering Provider's DEA Number | No | Yes | XCN | |
| RXE.14 | Pharmacist/Treatment Supplier's Verifier ID | No | Yes | XCN | |
| RXE.15 | Prescription Number | No | No | ST | |
| RXE.16 | Number of Refills Remaining | No | No | NM | |
| RXE.17 | Number of Refills/Doses Dispensed | No | No | NM | |
| RXE.18 | D/T of Most Recent Refill or Dose Dispensed | No | No | TS | |
| RXE.19 | Total Daily Dose | No | No | CQ | |
| RXE.20 | Needs Human Review | No | No | ID | 0136 |
| RXE.21 | Pharmacy/Treatment Supplier's Special Dispensing Instructions | No | Yes | CE | |
| RXE.22 | Give Per (Time Unit) | No | No | ST | |
| RXE.23 | Give Rate Amount | No | No | ST | |
| RXE.24 | Give Rate Units | No | No | CE | |
| RXE.25 | Give Strength | No | No | NM | |
| RXE.26 | Give Strength Units | No | No | CE | |
| RXE.27 | Give Indication | No | Yes | CE | |
| RXE.28 | Dispense Package Size | No | No | NM | |
| RXE.29 | Dispense Package Size Unit | No | No | CE | |
| RXE.30 | Dispense Package Method | No | No | ID | 0321 |
| RXE.31 | Supplementary Code | No | Yes | CE | |
| RXE.32 | Original Order Date/Time | No | No | TS | |
| RXE.33 | Give Drug Strength Volume | No | No | NM | |
| RXE.34 | Give Drug Strength Volume Units | No | No | CWE | |
| RXE.35 | Controlled Substance Schedule | No | No | CWE | 0477 |
| RXE.36 | Formulary Status | No | No | ID | 0478 |
| RXE.37 | Pharmaceutical Substance Alternative | No | Yes | CWE | |
| RXE.38 | Pharmacy of Most Recent Fill | No | No | CWE | |
| RXE.39 | Initial Dispense Amount | No | No | NM | |
| RXE.40 | Dispensing Pharmacy | No | No | CWE | |
| RXE.41 | Dispensing Pharmacy Address | No | No | XAD | |
| RXE.42 | Deliver-to Patient Location | No | No | PL | |
| RXE.43 | Deliver-to Address | No | No | XAD | |
| RXE.44 | Pharmacy Order Type | No | No | ID | 0480 |
RXE carries the encoded pharmacy/treatment order, turning the ordered medication into structured dose, route, quantity, and instruction data.
The standard describes RXE this way: The RXE segment details the pharmacy or treatment application's encoding of the order. It also contains several pharmacy-specific order status fields, such as RXE-16-number of refills remaining, RXE-17-number of refills/doses dispensed, RXE-18-D/T of most recent refill or dose dispensed, and RXE-19-total daily dose. Note that ORC-7-quantity/timing has a different meaning from RXE-1-quantity/timing and RXG-3-quantity/timing. The pharmacy or treatment department has the "authority" (and/or necessity) to schedule dispense/give events. Hence, the pharmacy or treatment department has the responsibility to encode this scheduling information in RXE-1-quantity/timing and RXG-3-quantity/timing. ORC-7-quantity/timing does not change: it always specifies the requested give/dispense schedule of the original order.
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 RXE in PEX_P07 - PEX - Unsolicited initial individual product experience report, RAR_RAR - Pharmacy/treatment administration information, RAS_O17 - RAS - Pharmacy/treatment administration, and RDE_O11 - RDE - Pharmacy/treatment encoded order, and 10 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.
RXE-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.
RXE-2 identifies the 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.
RXE-3 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.
RXE-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.
RXE-5 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXE-6 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.
RXE-7 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.
RXE-8 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.
RXE-9 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.
RXE-10 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.
RXE-11 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXE-12 is a count or total for this pharmacy workflow. Make the counting rule explicit before using it for reconciliation, billing, or workflow limits.
RXE-13 identifies the Ordering Provider's DEA 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.
RXE-14 identifies the Pharmacist/Treatment Supplier's Verifier ID 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.
RXE-15 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.
RXE-16 is a count or total for this pharmacy workflow. Make the counting rule explicit before using it for reconciliation, billing, or workflow limits.
RXE-17 is a count or total for this pharmacy workflow. Make the counting rule explicit before using it for reconciliation, billing, or workflow limits.
RXE-18 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.
RXE-19 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.
RXE-20 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.
RXE-21 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.
RXE-22 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.
RXE-23 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.
RXE-24 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXE-25 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.
RXE-26 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXE-27 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.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
RXE-28 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.
RXE-29 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.
RXE-30 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.
RXE-31 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.
RXE-32 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.
RXE-33 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.
RXE-34 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXE-35 carries Controlled Substance Schedule 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 0477; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RXE-36 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 0478 or the narrower table in the local profile.
RXE-37 carries Pharmaceutical Substance Alternative 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.
RXE-38 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.
RXE-39 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.
RXE-40 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.
RXE-41 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.
RXE-42 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.
RXE-43 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.
RXE-44 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.
Related links
- RXO - Pharmacy/Treatment Order
- RXC - Pharmacy/Treatment Component Order
- RXD - Pharmacy/Treatment Dispense
- RXG - Pharmacy/Treatment Give
- RXA - Pharmacy/Treatment Administration
- RXR - Pharmacy/Treatment Route
- TQ1 - Timing/Quantity
- ORC - Common Order
- PEX_P07 - PEX - Unsolicited initial individual product experience report
- RAR_RAR - Pharmacy/treatment administration information