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 |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM # |
ELEMENT NAME |
1 |
4 |
NM |
R |
00342 |
Give Sub-ID Counter |
||
2 |
4 |
NM |
R |
00344 |
Administration Sub-ID Counter |
||
3 |
26 |
TS |
R |
00345 |
Date/Time Start of Administration |
||
4 |
26 |
TS |
R |
00346 |
Date/Time End of Administration |
||
5 |
100 |
CE |
R |
0292 |
00347 |
Administered Code |
|
6 |
20 |
NM |
R |
00348 |
Administered Amount |
||
7 |
60 |
CE |
C |
00349 |
Administered Units |
||
8 |
60 |
CE |
O |
00350 |
Administered Dosage Form |
||
9 |
200 |
CE |
O |
Y |
00351 |
Administration Notes |
|
10 |
200 |
XCN |
O |
00352 |
Administering Provider |
||
11 |
200 |
CM |
C |
00353 |
Administered-at Location |
||
12 |
20 |
ST |
C |
00354 |
Administered Per (Time Unit) |
||
13 |
20 |
NM |
O |
01134 |
Administered Strength |
||
14 |
60 |
CE |
O |
01135 |
Administered Strength Units |
||
15 |
20 |
ST |
O |
Y |
01129 |
Substance Lot Number |
|
16 |
26 |
TS |
O |
Y |
01130 |
Substance Expiration Date |
|
17 |
60 |
CE |
O |
Y |
0227 |
01131 |
Substance Manufacturer Name |
18 |
200 |
CE |
O |
Y |
01136 |
Substance Refusal Reason |
|
19 |
200 |
CE |
O |
Y |
01123 |
Indication |
|
20 |
2 |
ID |
O |
0322 |
01223 |
Completion Status |
|
21 |
2 |
ID |
O |
0323 |
01224 |
Action Code |
|
22 |
26 |
TS |
O |
01225 |
System Entry Date/Time |
4.8.14.0 RXA field definitions
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 fields value is zero.
Definition: This field starts with 1 the first time that medication is administered for this order. Increments by one with each additional administration of medication.
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.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the identifier of the medical substance administered. It is equivalent to OBR-4-universal service ID code in function. If the substance administered is a vaccine, CVX codes may be used to code this field (see HL7 table 0292 - Vaccines administered).
Definition: This field contains the amount administered.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: The dosage form indicates the manner in which the medication 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.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains notes from the provider administering the medication. 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|.
Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID )> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the provider ID of the person administering the pharmaceutical.
Components: <point of care (IS)> & <room (IS) ^ <bed (IS)> & <facility (HD) & <location status (IS) & <patient location type (IS)> & <building (IS)> & <floor (IS)> ^ < street address (ST)> & <other designation (ST)> & <city (ST)> & <state or province (ST)> & <zip or postal code (ST)> & <country (ID)> & <address type (ID)> & <other geographic designation (ST)>
Definition: The first component contains the inpatient or outpatient location at which the drug or treatment was administered (if applicable). The default (null) value is the current census location for the patient. Site specific table. This first component has the same form as PV1-3-assigned patient location.
The second component can be used to specify an address. This could be used to fill mail orders to a patient or provider, or to account for home health care.
Definition: This field contains the rate at which this medication 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 unit.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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.
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 (ug/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. |
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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 4.10, "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. |
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains the reason the patient refused the medical substance. Any entry in the field indicates that the patient did not take the substance.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
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.
Definition: Status of treatment administration event. Refer to HL7 table 0322 - Completion status for valid values.
Table 0322 - Completion status
Value |
Description |
CP |
Complete |
RE |
Refused |
NA |
Not Administered |
PA |
Partially Administered |
Definition: Status of record. The information in this field enables the use of the RXA in the vaccine messages (see Section 4.13, "RXA SEGMENT USAGE IN VACCINE MESSAGES"), where a method of correcting vaccination information transmitted with incorrect patient identifying information is needed. Refer to HL7 table 0323 - Action code for valid values.
Table 0323 - Action code
Value |
Description |
A |
Add |
D |
Delete |
U |
Update |
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.