HL7 RXG Pharmacy/Treatment Give
HL7 field reference RXG 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 |
|---|---|---|---|---|---|
| RXG.1 | Give Sub-ID Counter | Yes | No | NM | |
| RXG.2 | Dispense Sub-ID Counter | No | No | NM | |
| RXG.3 | Quantity/Timing | No | No | TQ | |
| RXG.4 | Give Code | Yes | No | CE | 0292 |
| RXG.5 | Give Amount - Minimum | Yes | No | NM | |
| RXG.6 | Give Amount - Maximum | No | No | NM | |
| RXG.7 | Give Units | Yes | No | CE | |
| RXG.8 | Give Dosage Form | No | No | CE | |
| RXG.9 | Administration Notes | No | Yes | CE | |
| RXG.10 | Substitution Status | No | No | ID | 0167 |
| RXG.11 | Dispense-to Location | No | No | LA2 | |
| RXG.12 | Needs Human Review | No | No | ID | 0136 |
| RXG.13 | Pharmacy/Treatment Supplier's Special Administration Instructions | No | Yes | CE | |
| RXG.14 | Give Per (Time Unit) | No | No | ST | |
| RXG.15 | Give Rate Amount | No | No | ST | |
| RXG.16 | Give Rate Units | No | No | CE | |
| RXG.17 | Give Strength | No | No | NM | |
| RXG.18 | Give Strength Units | No | No | CE | |
| RXG.19 | Substance Lot Number | No | Yes | ST | |
| RXG.20 | Substance Expiration Date | No | Yes | TS | |
| RXG.21 | Substance Manufacturer Name | No | Yes | CE | 0227 |
| RXG.22 | Indication | No | Yes | CE | |
| RXG.23 | Give Drug Strength Volume | No | No | NM | |
| RXG.24 | Give Drug Strength Volume Units | No | No | CWE | |
| RXG.25 | Give Barcode Identifier | No | No | CWE | |
| RXG.26 | Pharmacy Order Type | No | No | ID | 0480 |
RXG describes a scheduled or given treatment instance in give-style pharmacy workflows.
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 RXG in RGR_RGR - Pharmacy/treatment dose information, RGV_O15 - RGV - Pharmacy/treatment give, RRG_O16 - RRG - Pharmacy/treatment give acknowledgment, and RSP_Z86 - . 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.
RXG-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.
RXG-2 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.
RXG-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.
RXG-4 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.
RXG-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.
RXG-6 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.
RXG-7 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXG-8 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.
RXG-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.
RXG-10 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.
RXG-11 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.
RXG-12 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.
RXG-13 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.
RXG-14 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.
RXG-15 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.
RXG-16 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXG-17 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.
RXG-18 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXG-19 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.
RXG-20 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.
RXG-21 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.
RXG-22 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.
RXG-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.
RXG-24 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
RXG-25 identifies the Give Barcode Identifier 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.
RXG-26 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
- RXE - Pharmacy/Treatment Encoded Order
- RXC - Pharmacy/Treatment Component Order
- RXD - Pharmacy/Treatment Dispense
- RXA - Pharmacy/Treatment Administration
- RXR - Pharmacy/Treatment Route
- TQ1 - Timing/Quantity
- ORC - Common Order
- RGR_RGR - Pharmacy/treatment dose information
- RGV_O15 - RGV - Pharmacy/treatment give