Back to top
Top
U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

["Medication, Dispensed": "Antidepressant Medication"]

Performance/Reporting Period
2021
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent antidepressant medications.
Data Element Scope: This value set may use the Quality Data Model (QDM) datatype related to Medication, Active or Medication, Dispensed.
Inclusion Criteria: Includes only relevant concepts associated with semantic clinical drugs (concepts associated with component, form and strength); generic; prescribable. Includes only relevant concepts associated with antidepressant medication. This is a grouping of RxNorm codes.
Exclusion Criteria: Excludes branded drugs; components or ingredients only; non-prescribable.

Constrained to codes in the Medication, Dispensed: Antidepressant Medication value set (2.16.840.1.113883.3.464.1003.196.12.1213)

QDM Datatype and Definition

"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. This timing corresponds to the HL7® FHIR® MedicationDispense.whenHandedOver.
  • relevantPeriod addresses the time referenced in the dosage instruction indicating when the medication administration should start and end. This timing corresponds to the HL7® FHIR® MedicationDispense.dosageInstruction.timing.
  • author dateTime is reserved for use only for documentation of negationRationale, the reason the dispensing event did not happen.

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 relevant dateTime or relevantPeriod.

Refer to Special Cases in Appendix A (Section 5.7) for scenarios to consider in calculating cumulative medication duration.

QDM Attributes

relevantDateTime

Relevant dateTime addresses the time an activity occurs as a single point in time. If the activity occurs over a period of time, use Relevant Period.

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