["Medication, Dispensed": "Antidepressant Medication"]
Data Element Scope: This value set may use a model element related to Medication.
Inclusion Criteria: Includes concepts that represent generic, human use and prescribable antidepressant medications.
Exclusion Criteria: Excludes concepts that represent non-prescribable or branded drugs and excludes concepts that represent components or ingredients.
Constrained to codes in the Medication, Dispensed: Antidepressant Medication value set (2.16.840.1.113883.3.464.1003.196.12.1213)
"Medication, Dispensed"
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 entity fulfilling the role of the performer attribute for the administration event.
Timing:
- relevant dateTime references the dateTime the prescription dispensing event occurred, i.e., the time the prescription was handed over to the patient or patient’s representative.
- relevantPeriod addresses the time referenced in the dosage instruction indicating when the medication administration should start and end.
- In the initial publication of QDM 5.5, relevantPeriod referenced the validity period, i.e., the time period for which the ordered supply is authorized by the prescription authorizing the dispensing event.
- For clarification, see Appendix 6.4 with additional guidance for referencing relevantPeriod updating the definition for "Medication, Order", "Medication Dispensed", and "Substance, Order".
- author dateTime references the date and time the dispensing event is recorded.
Notes:
- 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 relevantPeriod 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.
- negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
Refer to Special Cases in Appendix A (Section 5.7) for scenarios to consider in calculating cumulative medication duration.
relevantDateTime
relevantPeriod
Relevant Period addresses the time between the start of an action to the end of an action. Each datatype using relevant period defines specific definitions for the start and stop time for the action listed.
Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatyperelated actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod