The ORC must have the filler order number and the order control code RE. As a site-specific variant, the RXO and associated RXCs and/or the RXE (and associated RXCs) may be present if the receiving application needs any of their data. The RXA carries the administration data.
| Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
|---|---|---|---|---|---|---|---|---|---|
RXA
|
|||||||||
1
|
Give Sub-ID Counter | NM | R | [1..1] | 00342 | 4 | # | ||
|
2
|
Administration Sub-ID Counter | NM | R | [1..1] | 00344 | 4 | # | ||
|
3
|
Date/Time Start of Administration | DTM | R | [1..1] | 00345 | ||||
|
4
|
Date/Time End of Administration | DTM | R | [1..1] | 00346 | ||||
|
5
|
Administered Code | CWE | R | [1..1] | 00347 | ||||
|
6
|
Administered Amount | NM | R | [1..1] | 00348 | ||||
|
7
|
Administered Units | CWE | C | [0..1] | 00349 | ||||
|
8
|
Administered Dosage Form | CWE | O | [0..1] | 00350 | ||||
|
9
|
Administration Notes | CWE | O | [0..*] | 00351 | ||||
|
10
|
Administering Provider | W | [0..1] | 00352 | |||||
|
11
|
Administered-at Location | W | [0..1] | 00353 | |||||
|
12
|
Administered Per | ST | C | [0..1] | 00354 | 20 | # | ||
|
13
|
Administered Strength | NM | O | [0..1] | 01134 | ||||
|
14
|
Administered Strength Units | CWE | O | [0..1] | 01135 | ||||
|
15
|
Substance Lot Number | ST | O | [0..*] | 01129 | 20 | # | ||
|
16
|
Substance Expiration Date | DTM | O | [0..*] | 01130 | ||||
|
17
|
Substance Manufacturer Name | CWE | O | [0..*] | 01131 | ||||
|
18
|
Substance/Treatment Refusal Reason | CWE | O | [0..*] | 01136 | ||||
|
19
|
Indication | CWE | O | [0..*] | 01123 | ||||
|
20
|
Completion Status | ID | O | [0..1] | 01223 | [2..2] | |||
|
21
|
Action Code – RXA | ID | O | [0..1] | 01224 | [1..1] | |||
|
22
|
System Entry Date/Time | DTM | O | [0..1] | 01225 | ||||
|
23
|
Administered Drug Strength Volume | NM | O | [0..1] | 01696 | 5 | # | ||
|
24
|
Administered Drug Strength Volume Units | CWE | O | [0..1] | 01697 | ||||
|
25
|
Administered Barcode Identifier | CWE | O | [0..1] | 01698 | ||||
|
26
|
Pharmacy Order Type | ID | O | [0..1] | 01699 | [1..1] | |||
|
27
|
Administer-at | PL | O | [0..1] | 02264 | ||||
|
28
|
Administered-at Address | XAD | O | [0..1] | 02265 | ||||
29
|
Administered Tag Identifier | EI | O | [0..*] | 03396 | ||||
Definition: Use this field if matching this RXA segment to its corresponding RXG segment. If the two applications are not matching RXG and RXA segments, this field's value is zero (0).
Definition: This field starts with 1 the first time that medication/treatment is administered for this order. Increments by one with each additional administration of the medication/treatment.
Note: More than one RXA segment can be "matched" to a single RXG segment, as is the case when recording a change of the rate of administration of an IV solution.
Definition: If the order is for a continuous administration (such as an IV), and the rate is changed at a certain time after the start, an RAS message can be issued to record the change. For such an RAS message, this field records the time the rate was changed to the new value recorded in the RXA-12-Administered Per (time unit) of the same message.
Definition: If null, the date/time of RXA-3-Date/Time Start of Administration is assumed.
Definition: This field contains the identifier of the medical substance/treatment administered. It is equivalent to OBR-4-universal service ID in function. If the substance administered is a vaccine, CVX codes may be used to code this field (see HL7 Table 0292 - Vaccines Administered). If CVX code is used to identify vaccines, the coding system component (RXA-5.3) should be valued as "CVX", not as "HL70292."
Definition: This field contains the amount administered.
Definition: This field is conditional because it is required if the administered amount code does not imply units. This field must be in simple units that reflect the actual quantity of the substance administered. It does not include compound units. Refer to Table 0689 - Administered Units in Chapter 2C for valid values.
Definition: The dosage form indicates the manner in which the medication/treatment is aggregated for dispensing, e.g., tablets, capsules, suppositories. In some cases, this information is implied by the dispense/give code in RXA-5-Administered Code. Use this field when the administered code does not specify the dosage form. Refer to Table 0690 - Administered Dosage Form in Chapter 2C for valid values.
Definition: This field contains notes from the provider administering the medication/treatment. If coded, requires a user-defined table. If free text (describing a custom IV, mixture, or salve, for example) place a null in the first component and the text in the second, e.g., |^this is a free text administration note|. Refer to Table 0691 - Administration Notes in Chapter 2C for valid values.
Attention: This field was retained for backward compatibilty only as of v 2.7 and the detail was withdrawn and removed from the standard as of v 2.9. The reader is referred to the PRT segment described in Chapter 7.
Definition: This field is retained for backward compatibility only as of v 2.6 and withdrawn from the standard as of v 2.8. The reader is referred to RXA-27 and RXA-28..
Definition: This field contains the rate at which this medication/treatment was administered as calculated by using RXA-6-administered amount and RXA-7-administered units. This field is conditional because it is required when a treatment is administered continuously at a prescribed rate, e.g., certain IV solutions.
Definition: Use when RXA-5-Administered Code does not specify the strength. This is the numeric part of the strength, used in combination with RXA-14-Administered Strength Units.
Definition: Use when RXA-5-Administered Code does not specify the strength. This is the unit of the strength, used in combination with RXA-13-Administered Strength. Refer to Table 0692 - Administered Strength Units in Chapter 2C for valid values.
Note: These units can be a "compound quantity;" i.e., the units may express a quantity per unit of time. For example, micrograms per hour (micg/h) is an acceptable value. These compound units are contained in the ISO+ table. See Chapter 7 for full definition of ISO+ units.
Definition: This field contains the lot number of the medical substance administered.
Note: The lot number is the number printed on the label attached to the container holding the substance and on the packaging which houses the container. If the substance is a vaccine, for example, and a diluent is required, a lot number may appear on the vial containing the diluent; however, any such identifier associated with a diluent is not the identifier of interest. The substance lot number should be reported, not that of the diluent.
Definition: This field contains the expiration date of the medical substance administered.
Note: Vaccine expiration date does not always have a "day" component; therefore, such a date may be transmitted as YYYYMM.
Definition: This field contains the manufacturer of the medical substance administered.
Note: For vaccines, code system MVX may be used to code this field. See section 4A.7.1, "Vaccine administration data." This field may be used if the manufacturer of the substance is not identified by the code used in RXA-5- administered code. When using this code system to identify vaccines, the coding system component of the CWE field should be valued as "MVX", not as "HL70227."
Definition: This field contains the reason the patient refused the medical substance/treatment. Any entry in the field indicates that the patient did not take the substance. Refer to Table 0693 - Substance/Treatment Refusal Reason in Chapter 2C for valid values.
Definition: This field contains the identifier of the condition or problem for which the drug/treatment was prescribed. May repeat if multiple indications are relevant. Refer to Table 0694 - Indication in Chapter 2C for valid values.
Definition: Status of treatment administration event. Refer to HL7 Table 0322 - Completion Status in Chapter 2C, Code Tables, for valid values.
Definition: Status of record. The information in this field enables the use of the RXA in the vaccine messages (see Section 4A.8, "Vaccine Segments"), where a method of correcting vaccination information transmitted with incorrect patient identifying information is needed. Refer To HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.
Definition: Date/time the administration information was entered into the source system. This field is used to detect instances where treatment administration information is inadvertently entered multiple times by providing a unique identification field. Under usual circumstances, this field would be provided automatically by the computer system rather than being entered by a person.
Description: This numeric field defines the volume measurement in which the drug strength concentration is contained. For example, Acetaminophen 120 MG/5ML Elixir means that 120 MG of the drug is in a solution with a volume of 5 ML , which would be encoded in RXA-13, RXA-14, RXA-23 and RXA-24 as:
RXA|||||||||||||120|mg^^ISO|||||||||5|ml^^ISO ...<cr>
Description: This field indicates the volumetric unit associated with RXA-23 Administered Drug Strength Volume. See example in RXA-23. Refer to Table 0695 - Administered Drug Strength Volume Units in Chapter 2C for valid values.
Definition: This field contains the pharmacy system's assigned barcode number for the give occurrence. For IV orders, many pharmacy systems generate a barcode number to identify a specific bag/bottle of the order. This number can be an instance identifier; unique for the patient, drug combination, and schedule instance or it may be just a drug identifier. Refer to Table 0696 - Administered Barcode Identifier in Chapter 2C for valid values.
The composition and use of the barcode number is dependent on application negotiation. An example of this field follows: The barcode number is in the following format, 9XXXXXXX000. The number '9' is a constant, XXXXXXX is seven (7) characters for a unique identifier assigned or derived from the patient account and order ID and 000 is the zero-filled three (3) character IV bottle number.
The maximum length of the first component of this field is 40 characters to allow for the maximum existing barcode length in use today. The second component contains the description of the item being coded and the third component may define the barcode type.
Example: 12345678901^IV bottle^3X9
Definition: The Pharmacy Order Type field defines the general category of pharmacy order which may be used to determine the processing path the order will take. Refer to HL7 Table 0480 - Pharmacy Order Types in Chapter 2C, Code Tables, for valid values.
This field may also be used for grouping of related orders for processing and/or reports. For example, Medication Administration Records (MARs) often group large volume solutions, medications and small volume solutions differently based upon site-specific workflow.
Usage Rule: This field is optional for all Pharmacy transactions. When not populated, a default value of "M" is assumed.
Definition: This field specifies the location where the drug or treatment was administered.
Definition: This field specifies the address of the location where the drug or treatment was administered.
Definition: This field contains an identifier for the individual product instance for the dispense occurrence. This may represent a barcode, RFID or other means of automatically-readable product instance. Repetitions represent the same instance where more than one barcode, RFID or other identification is present.
For example, the medication preparer, e.g., a semi-automatic system, can inform the nurse that “for the 8.am administration event, the medication that has been assigned and available at the patient bedside has the barcode BBBBBBBBBBB.” The nurse would scan the barcode, to ensure that the right medication is being administered.
This differs from RXA-25 Administered Barcode Identifier in that RXA-25 may include other workflow content or the product at various levels of granularity. RXA-29 specifically identifies the product instance.
®© HL7.org 2019+. HL7 v2+ generated on March 23, 2022
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
