Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Medication, Active and Medication, Dispensed.
Inclusion Criteria: Includes only relevant concepts associated with semantic clinical drugs (concepts associated with component, form and strength); generic; prescribable; ADHD medications only.
Exclusion Criteria: No exclusions.
Constrained to codes in the Medication, Dispensed: ADHD Medications value set
Data elements that meet criteria using this datatype should document that a prescription for the medication indicated by the QDM category and its corresponding value set has been dispensed and provided to the patient or patient proxy. In the ambulatory setting, medications are primarily taken directly by patients and not directly observed. Hence, dispensed, or fulfillment, information is the closest health provider documentation of medication compliance. In settings where patients attest to taking medications in electronic format (perhaps a Personal Health Record), patient attestation of medication taken may be available. The QDM datatype, Medication, Administered addresses medication taken; to address the source of the information, a measure addressing such patient attestation would require use of the dataflow attribute, source.
Timing: The time the medication dispensing event occurs; the Author dateTime.
Timing: The Relevant Period addresses:
- startTime - when the first administration of the medication is expected. If not specified. the startTime defaults to the Author dateTime (the time the medication dispensing event occurs).
- stopTime - when the medication supply provided by the dispensing event is expected to be completed.
Note that when calculating cumulative medication duration, the medication dispensed stopTime may be present directly in the fulfillment record. If the stopTime is not available, the duration in days is the difference between the Relevant Period start and stop times. The record may indicate which of the available refills the fulfillment represents but each dispensing event is unique. Therefore, the measure developer should use CQL logic to address multiple dispensing events over a period of time.