| Seq# | DataElement | Description | Must Implement | Flags | Cardinality | Length | C.LEN | Vocabulary | DataType |
|---|---|---|---|---|---|---|---|---|---|
RXD
|
|||||||||
1
|
00334 | Dispense Sub-ID Counter | SHALL | = | [1..1] | 4 | NM | ||
|
2
|
00335 | Dispense/Give Code | SHALL | [1..1] | CWE | ||||
|
3
|
00336 | Date/Time Dispensed | SHALL | [1..1] | DTM | ||||
|
4
|
00337 | Actual Dispense Amount | SHALL | [1..1] | NM | ||||
5
|
00338 | Actual Dispense Units |
MAY
True:
False:
|
C |
[1..1] [0..1] |
CWE | |||
|
6
|
00339 | Actual Dosage Form | [0..1] | CWE | |||||
|
7
|
00325 | Prescription Number | SHALL | = | [1..1] | 20 | ST | ||
|
8
|
00326 | Number of Refills Remaining |
MAY
True:
False:
|
C |
[1..1] [0..1] |
NM | |||
|
9
|
00340 | Dispense Notes | = | [0..*] | 200 | ST | |||
|
10
|
00341 | Dispensing Provider | B | [0..*] | XCN | ||||
|
11
|
00322 | Substitution Status | [0..1] | [1..1] | ID | ||||
|
12
|
00329 | Total Daily Dose | [0..1] | CQ | |||||
|
13
|
01303 | Dispense-to Location | SHALL NOT | W | [0..0] | ||||
|
14
|
00307 | Needs Human Review | [0..1] | [1..1] | ID | ||||
|
15
|
00330 | Special Dispensing Instructions | [0..*] | CWE | |||||
|
16
|
01132 | Actual Strength | [0..1] | NM | |||||
|
17
|
01133 | Actual Strength Unit | [0..1] | CWE | |||||
|
18
|
01129 | Substance Lot Number | = | [0..*] | 20 | ST | |||
|
19
|
01130 | Substance Expiration Date | [0..*] | DTM | |||||
|
20
|
01131 | Substance Manufacturer Name | [0..*] | CWE | |||||
|
21
|
01123 | Indication | [0..*] | CWE | |||||
|
22
|
01220 | Dispense Package Size | [0..1] | NM | |||||
|
23
|
01221 | Dispense Package Size Unit | [0..1] | CWE | |||||
|
24
|
01222 | Dispense Package Method | [0..1] | [1..2] | ID | ||||
|
25
|
01476 | Supplementary Code | [0..*] | CWE | |||||
|
26
|
01477 | Initiating Location | [0..1] | CWE | |||||
|
27
|
01478 | Packaging/Assembly Location | [0..1] | CWE | |||||
|
28
|
01686 | Actual Drug Strength Volume | = | [0..1] | 5 | NM | |||
|
29
|
01687 | Actual Drug Strength Volume Units | [0..1] | CWE | |||||
|
30
|
01688 | Dispense to Pharmacy | B | [0..1] | CWE | ||||
|
31
|
01689 | Dispense to Pharmacy Address | B | [0..1] | XAD | ||||
|
32
|
01690 | Pharmacy Order Type | [0..1] | [1..1] | ID | ||||
|
33
|
01691 | Dispense Type | [0..1] | CWE | |||||
|
34
|
02311 | Pharmacy Phone Number | [0..*] | XTN | |||||
|
35
|
03392 | Dispense Tag Identifier | [0..*] | EI | |||||
(Definition from RXD.1 in Ch. 4A)
Definition: This field starts with 1 the first time that medication/treatment is delivered/dispensed for this order. Increments by one with each additional issuance.
(Definition from RXG.2 in Ch. 4A)
Definition: This is the dispense sub-ID to which this give message is related.
Definition: This field identifies the medical substance or treatment ordered to be given to the patient; it is equivalent to OBR-4-Universal Service ID. See the RXE segment for a complete definition of the RXE-2-give code. If the substance dispensed is a vaccine, CVX codes may be used to code this field (see HL7 Table 0292 - Vaccines Administered in Chapter 2C, Code Tables).
Note: The contents of RXD-2-dispense/give code should be compatible with the comparable field in the RXE (RXE-2-give code). The RDS message refers ONLY to the dispensing of the drug or treatment by the pharmacy or treatment supplier.
Definition: This field indicates when the pharmaceutical/treatment is dispensed from the pharmacy or treatment supplier. Use the time stamp format.
Definition: This field indicates the amount dispensed.
Definition: This field indicates the units dispensed. Site-defined table. This field is required if the units are not implied by the actual dispense code. If present, it overrides units implied by the actual dispense code. This must be in simple units that reflect the actual quantity of the substance dispensed. It does not include compound units. Refer to Table 0704 - Actual Dispense 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 RXD-2-dispense/give code. Use this field when the give code and the dispense code do not specify the dosage form. Refer to Table 0705 - Actual Dosage Form in Chapter 2C for valid values.
(Definition from RXE.15 in Ch. 4A)
Definition: This field contains the prescription number as assigned by the pharmacy or treatment application. Equivalent in uniqueness to the pharmacy/treatment filler order number. At some sites, this may be the pharmacy or treatment system (internal) sequential form. At other sites, this may be an external form. This is a required field in RXE when used in pharmacy/treatment messages, but it is not required when used in product experience messages (see Chapter 7).
(Definition from RXD.7 in Ch. 4A)
Definition: This field is equivalent in uniqueness to the pharmacy/treatment supplier filler order number. At some sites, this may be the pharmacy/treatment supplier (internal) sequential form. At other sites, this may be an external number.
(Definition from FT1.42 in Ch. 6)
Definition: This field contains the prescription number as assigned by the pharmacy or treatment application. Equivalent in uniqueness to the pharmacy/treatment filler order number. At some sites, this may be the pharmacy or treatment system (internal) sequential form. At other sites, this may be an external form.
(Definition from RXE.16 in Ch. 4A)
Definition: Number of refills remaining. This field is conditional because it is required when a prescription is dispensed to an outpatient. It is not relevant to inpatient treatment orders.
(Definition from RXD.8 in Ch. 4A)
Definition: This field is conditional because it is required when a prescription is dispensed to an outpatient. It is not relevant to inpatient treatment orders.
Definition: This field contains free text notes to the person dispensing the medication/treatment (may include the ordering provider's original notes, as well as any notes from the formulary or the pharmacy or treatment supplier). This may contain free text describing a custom IV, mixture, or salve for example.
Definition: This field is retained for backward compatibility only as of v 27. The reader is referred to the PRT segment described in Chapter.7.
This field contains the provider ID of the person dispensing the pharmaceutical. If the person referenced in this field is also referenced in PRT segment, they must contain the same information. However, if there is a difference, then PRT segment takes precedence.
(Definition from RXE.9 in Ch. 4A)
Definition: Refer to HL7 Table 0167 - Substitution Status in Chapter 2C, Code Tables, for valid values. If a substitution has been made, and a record of the original requested give code (RXO-1-requested give code) is needed, the optional RXO segment can be included in the RDE message.
(Definition from RXD.11 in Ch. 4A)
Definition: Refer to HL7 Table 0167 - Substitution Status in Chapter 2C, Code Tables, for suggested values.
(Definition from RXG.10 in Ch. 4A)
Definition: Refer to HL7 Table 0167 - Substitution Status in Chapter 2C, Code Tables, for valid values.
Note: The next two fields are equivalent to the corresponding fields of the RXE segment. They are included (optionally) in the RXG so that it may "stand alone" as a "give" instruction segment.
(Definition from RXO.23 in Ch. 4A)
Definition: This field contains the total daily dose for this particular pharmaceutical as expressed in terms of actual dispense units.
(Definition from RXE.19 in Ch. 4A)
Definition: This field contains the total daily dose for this particular pharmaceutical as expressed in terms of actual dispense units.
(Definition from RXD.12 in Ch. 4A)
Definition: This field contains the total daily dose being dispensed as expressed in terms of the actual dispense units.
Note: The next two fields are equivalent to the corresponding fields of the RXE segment. They are included (optionally) in the RXD so that it may "stand alone" as a dispense result instruction segment.
(Definition from RXD.13 in Ch. 4A)
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 toRXD-30 and RXD-31.
(Definition from RXG.11 in Ch. 4A)
Definition: This field is retained for backward compatibility only as of v 2.6 and removed from the standard as of v 2.8. The reader is referred to RXG-27 and RXG-28.
(Definition from RXO.16 in Ch. 4A)
Definition: This field uses HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables. The values have the following meaning for this field:
Y Yes - Indicates that the pharmacist or non-pharmacist treatment supplier filling the order needs to pay special attention to the text in the RXO-6-provider's pharmacy/treatment instructions. A warning is present.
N No - No warning is present. This is the equivalent default (null) value.
An example of the use of this field is given by the following case:
A smart Order Entry application knows of a possible drug or treatment interaction on a certain order, but the provider issuing the order wants to override the condition. In this case, the pharmacy or treatment application receiving the order will want to have a staff pharmacist or non-pharmacist treatment supplier review the interaction and contact the ordering physician.
(Definition from RXE.20 in Ch. 4A)
Definition: This field uses HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables. The values have the following meaning for this field:
Y Yes - Indicates that a warning is present. The application receiving the encoded order needs to warn the person administering the drug or treatment to pay attention to the text in RXE-21-pharmacy/treatment special dispensing instructions.
N No - Indicates no warning is present. This is the equivalent default (null) value.
(Definition from RXD.14 in Ch. 4A)
Definition: Refer to HL7 Table 0136 - Yes/no indicator for valid values. The values have the following meaning for this field:
Y Yes - Indicates that a warning is present. The application receiving the dispense order needs to warn the person dispensing/administering the drug or treatment to pay attention to the text in RXD-15-Special dispensing instructions.
N No - Indicates no warning is present. This is the equivalent default (null) value.
(Definition from RXG.12 in Ch. 4A)
Definition: Refer to HL7 Table 0136 - Yes/No Indicator for valid values. The values have the following meaning for this field:
Y Yes - Indicates that a warning is present. The application receiving the dispense order needs to warn the person dispensing/administering the drug or treatment to pay attention to the text in RXG-13-Special administration instructions.
N No - Indicates no warning is present. This is the equivalent default (null) value.
(Definition from RXE.21 in Ch. 4A)
Definition: This field contains the pharmacy or treatment supplier's provider-generated special instructions to the provider dispensing/administering the order. Refer to Table 0721 - Special Dispensing Instructions in Chapter 2C for valid values.
(Definition from RXD.15 in Ch. 4A)
Definition: This field contains pharmacy or treatment supplier-generated special instructions to the provider dispensing/administering the order. Refer to Table 0706 - Special Dispensing Instructions in Chapter 2C for valid values.
Definition: Use when RXD-2-Dispense/Give Code does not specify the strength. This is the numeric part of the strength, of a single dosage unit of the dispensed product, used in combination with RXD-17-actual strength unit.
Definition: Use when RXD-2-Dispense/Give Code does not specify the strength. This is the unit of the strength, of a single dosage unit of the dispensed product, used in combination with RXD-16-actual strength. Refer to Table 0707 - Actual Strength Unit 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 from RXD.18 in Ch. 4A)
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 from RXG.19 in Ch. 4A)
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 from RXA.15 in Ch. 4A)
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 from SID.2 in Ch. 13)
Definition: This field specifies the lot number assigned by the manufacturer during production of the substance.
(Definition from RXD.19 in Ch. 4A)
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^L.
(Definition from RXG.20 in Ch. 4A)
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 from RXA.16 in Ch. 4A)
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 from RXD.20 in Ch. 4A)
Definition: This field contains the manufacturer of the medical substance administered when it is a manufactured substance.
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.
(Definition from RXG.21 in Ch. 4A)
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 section4A.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.
(Definition from RXA.17 in Ch. 4A)
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 from RXO.20 in Ch. 4A)
Definition: This field identifies the condition or problem for which the drug/treatment was prescribed. May repeat if multiple indications are relevant. Refer to Table 0758 - Indication in Chapter 2C for valid values.
(Definition from RXD.21 in Ch. 4A)
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 0708 - Indication in Chapter 2C for valid values.
(Definition from RXG.22 in Ch. 4A)
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 0743 - Indication in Chapter 2C for valid values.
(Definition from RXA.19 in Ch. 4A)
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 from RXE.28 in Ch. 4A)
Definition: This field contains the size of package to be dispensed. Units are transmitted in RXE-29-dispense package size unit.
(Definition from RXD.22 in Ch. 4A)
Definition: This field contains the size of package to be dispensed. Units are transmitted in RXD-23-dispense package size unit.
(Definition from RXE.29 in Ch. 4A)
Definition: This field contains the units in which RXE-28-dispense package size is denominated. Refer to Table 0726 - Dispense Package Size Unit in Chapter 2C for valid values.
(Definition from RXD.23 in Ch. 4A)
Definition: This field contains the units in which RXE-28-dispense package size is denominated. The advertised number of units in the manufacturer's package, i.e., the package as it comes from the supplier. Refer to Table 0709 - Dispense Package Size Unit in Chapter 2C for valid values.
(Definition from RXE.30 in Ch. 4A)
Definition: This field contains the method by which treatment is dispensed. Refer to HL7 Table 0321 - Dispense Method in Chapter 2C, Code Tables, for valid values.
(Definition from RXD.24 in Ch. 4A)
Definition: This field contains the method by which treatment is dispensed. Refer To HL7 Table 0321 - Dispense Method in Chapter 2C, Code Tables, for valid values.
(Definition from RXO.24 in Ch. 4A)
This field accommodates the identification of any codes that might be associated with the pharmaceutical substance. Common codes include: the Generic Product Identifier (GPI), Generic Code Number_Sequence Number (GCN_SEQNO), National Drug Code (NDC). Refer to Table 0762 - Supplementary Code in Chapter 2C for valid values.
(Definition from RXC.7 in Ch. 4A)
Definition: This field accommodates the identification of any codes that might be associated with the pharmaceutical or other treatment substance. Common codes include: the Generic Product Identifier (GPI), Generic Code Number_Sequence Number (GCN_SEQNO), National Drug Code (NDC). Refer to Table 0700 - Supplementary Code in Chapter 2C for valid values.
(Definition from RXE.31 in Ch. 4A)
Definition: This field accommodates the identification of any codes that might be associated with the pharmaceutical substance. Common codes include: the Generic Product Identifier (GPI), Generic Code Number_Sequence Number (GCN_SEQNO), National Drug Code (NDC). Refer to Table 0727 - Supplementary Code in Chapter 2C for valid values.
(Definition from RXD.25 in Ch. 4A)
Definition: This field accommodates the identification of any codes that might be associated with the pharmaceutical substance. Common codes include: the Generic Product Identifier (GPI), Generic Code Number_Sequence Number (GCN_SEQNO), National Drug Code (NDC). Refer to Table 0710 - Supplementary Code in Chapter 2C for valid values.
Definition: This field identifies the pharmacy or other treatment dispensing service (e.g., respiratory) that received the initial request. Refer to Table 0711 - Initiating Location in Chapter 2C for valid values.
Example: Pharmacy A (the Intake/Receiving) receives a phone call from the patient requesting a medication refill, but stipulates that the prescription will be picked up in pharmacy B. In accordance with the business process the prescription will be packaged/assembled in Pharmacy C.
Definition: This field identifies the pharmacy which packaged/assembled request. Refer to Table 0712 - Packaging/Assembly Location in Chapter 2C for valid values.
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 RXD-16, RXD-17, RXD-28 and RXD-29 as
RXD||||||||||||||||120|mg^^ISO|||||||||||5|ml^^ISO ...<cr>
Description: This field indicates the volumetric unit associated with RXD-28 Actual Drug Strength Volume. See example in RXD-28. Refer to Table 0713 - Actual Drug Strength Volume Units in Chapter 2C for valid values.
(Definition from RXD.30 in Ch. 4A)
Definition: This field is retained for backward compatibility only as of v 27. The information formerly communicated using this field should now be communicated using the PRT segment. The reader is referred to chapter 7 for a description of that segment. Refer to Table 0714 - Dispense to Pharmacy in Chapter 2C for valid values.
This field specifies the pharmacy that will dispense or has dispensed the prescription. In the context of an order/request (i.e., in an RXO segment) this field represents the requested dispensing pharmacy. In the context of a registered order (i.e., in an RXE segment) this field represents the intended dispensing pharmacy, the pharmacy that is expected to dispense the prescription.
(Definition from RXG.27 in Ch. 4A)
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 from RXD.31 in Ch. 4A)
Definition: This field is retained for backward compatibility only as of v 27. The information formerly communicated using this field should now be communicated using the PRT segment. The reader is referred to chapter 7 for a description of that segment.
This field specifies the address of the dispensing facility or the patient's location where the dispensing will occur.
(Definition from RXG.28 in Ch. 4A)
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: 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 is the type of dispensing event that occurred. Refer to User-defined Table 0484 – Dispense Type for suggested values.
Definition: This field contains the telecommunication contact information for the pharmacy. Repetitions may be supplied for various device types or use codes, or multiple instances of the same type or use. This concept also exists as RXO-36 and RXE-45 to support pharmacy contact information in the context of the order, the encoded order and the dispense.
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 a.m. 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.
®© HL7.org 2019+. HL7 v2+ generated on December 11, 2020
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
