| Property Name | Type and Description | Existence | Cardinality |
|---|---|---|---|
type |
CODED_TEXT
Indicates the type of dispensing event that is performed. For example, Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.
|
0..1
| N/A
|
daysSupply |
QUANTITY
Amount of medication expressed as a timing amount
|
0..1
| N/A
|
whenPrepared |
DATE_TIME
The time when the dispensed product was packaged and reviewed.
|
0..1
| N/A
|
whenHandedOver |
DATE_TIME
The time the dispensed product was provided to the patient or their representative.
|
0..1
| N/A
|
destination |
PARTICIPATION
Identification of the facility/location where the medication was shipped to, as part of the dispense event.
|
0..1
| N/A
|
dispenseRecipient |
List<PARTICIPATION>
Identifies the person who picked up the medication. This will usually be a patient or their caregiver, but some cases exist where it can be a healthcare professional.
|
0..1
| 0..*
|
method |
CODED_TEXT
This optional property is included for compatibility to HL7 version 2. It is meant to convey how the medication was supplied, probably for pricing or workflow purposes. No specific federal requirements or uses for this field have been identified.
'Contains the method by which treatment is dispensed.' - HL7 Version 2.8, RXD-24. Possible values (from HL7 Table 321) include: Traditional; Unit Dose; Floor Stock; Automatic Dispensing.
|
0..1
| N/A
|
fillSequenceNumber |
COUNT
This property enumerates how the current fill relates to the number of times that the medication request (prescription) has been filled. It is noted that this concept exists in both NCPDP and in HL7 version 2, yet the numbering is different in these two standards: NCPDP uses zero for the original fill then increments for each refill, while HL7 version 2 uses one for the original fill then increments for each refill. Implementers are cautioned to be cognizant of how this data is locally stored and how it is represented in the target standard.
'This field starts with 1 the first time that medication/treatment is delivered/dispensed for this order. Increments by one with each additional issuance.' - HL7 Version 2.8, RXD-1.
'The code indicating whether the prescription is an original or a refill.' - NCPDP Telecommunication (Field 403-D3, Data Dictionary 201104). Note that while the NCPDP Telecommunication structure treats this field as a code, it contains a number from 0-99, where zero is the original fill, and 1-99 are refills.
|
0..1
| N/A
|
productSelectionCode |
CODED_TEXT
'Code indicating whether or not the prescriber’s instructions regarding generic substitution were followed.' - NCPDP Telecommunication (Field 408-D8, Data Dictionary 201104). Possible values include: Substitution Not Allowed by Prescriber; Substitution Not Allowed-Brand Drug Mandated by Law; Substitution Allowed-Patient Requested Product Dispensed; Substitution Allowed-Pharmacist Selected Product Dispensed; Substitution Allowed-Generic Drug Not in Stock; Substitution Allowed-Brand Drug Dispensed as a Generic; Substitution Allowed-Generic Drug Not Available in Marketplace; Substitution Allowed By Prescriber but Plan Requests Brand; Override; No Product Selection Indicated.
|
0..1
| N/A
|
specialPackaging |
CODED_TEXT
'Code indicating the type of dispensing dose.' - NCPDP Telecommunication (Field 429-DT, Data Dictionary 201104). Possible values include: Not Unit Dose; Manufacturer Unit Dose; Pharmacy Unit Dose; Pharmacy Unit Dose Patient Compliance Packaging; Pharmacy Multi-drug Patient Compliance Packaging; Remote Device Unit Dose; Remote Device Multi- drug Compliance; Manufacturer Unit of Use Package (not unit dose); Not Specified.
|
0..1
| N/A
|
totalDailyDose |
QUANTITY
'Contains the total daily dose being dispensed as expressed in terms of the actual dispense units.' - HL7 Version 2.8, RXD-12.
|
0..1
| N/A
|
archetype_node_id,
name,
archetype_details