HL7 RXR Pharmacy/Treatment Route
HL7 field reference RXR 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
RXR describes the route, site, device, and method for administering a pharmacy or treatment item.
The standard describes RXR this way: The Pharmacy/Treatment Route segment contains the alternative combination of route, site, administration device, and administration method that are prescribed as they apply to a particular order. The pharmacy, treatment staff and/or nursing staff has a choice between the routes based on either their professional judgment or administration instructions provided by the physician.
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 RXR in CSU_C09 - CSU - Automated time intervals for reporting like monthly, OMP_O09 - OMP - Pharmacy/treatment order, ORP_O10 - ORP - Pharmacy/treatment order acknowledgment, and PEX_P07 - PEX - Unsolicited initial individual product experience report, and 19 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.
RXR-1 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 0162. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
RXR-2 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 0163. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
RXR-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.
The generated panel links this to HL7 table 0164; many real interfaces narrow that list further, so follow the receiver's implementation guide.
RXR-4 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 0165. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
RXR-5 carries Routing Instruction 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.
RXR-6 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 0495. 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
- RXD - Pharmacy/Treatment Dispense
- RXG - Pharmacy/Treatment Give
- RXA - Pharmacy/Treatment Administration
- TQ1 - Timing/Quantity
- ORC - Common Order
- CSU_C09 - CSU - Automated time intervals for reporting like monthly
- OMP_O09 - OMP - Pharmacy/treatment order