["Medication, Order": "High Intensity Statin Therapy"]
Data Element Scope: This value set may use a model element related to Medication.
Inclusion Criteria: Includes concepts that represent a medication for high intensity statin therapy as defined by the 2013 American College of Cardiology (ACC) and the American Heart Association (AHA) guideline.
Exclusion Criteria: Excludes concepts that represent any other intensity of statin therapy.
Constrained to codes in the Medication, Order: High Intensity Statin Therapy value set (2.16.840.1.113883.3.526.3.1572)
"Medication, Order"
Data elements that meet criteria using this datatype should document a request to a pharmacy to provide the medication indicated by the QDM category and its corresponding value set.
Timing:
- relevantPeriod addresses the time referenced in the dosage instruction indicating when the medication administration should start and end.
- author dateTime references the date and time the medication order (prescription) is authored.
Notes:
- The medication order (prescription) is unlikely to indicate a relevantPeriod, the time period for which the ordered supply is to be administered/taken including all refills. Therefore, to determine the number of days covered by a single dispensing event, use the daysSupplied attribute and the relevant dateTime of the event to determine when the ordered medication will run out. If daysSupplied is not available, derive it from the supply (quantity of medication ordered) divided by the dosage (amount of medication to be taken at a single administration) times the frequency (number of units per time period – e.g., per day):
daysSupplied = supply / (dosage x frequency)
And multiply the daysSupplied per dispensing event multiplied by one plus the number of refills to determine the total daysSupplied ordered.
daysSupplied x (1 + #refills)
Starting with the relevant dateTime add the total daysSupplied (including refills) to determine when the ordered medication quantity will run out. - 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 Section 5.7 for scenarios to consider in calculating cumulative medication duration.
authorDateTime
The time the data element was entered into the clinical software. Note, some datatypes include both relevant dateTime and author dateTime attributes. When both are present, author dateTime is included to accommodate negation rationale.
The author dateTime addresses when an activity is documented. Documentation can occur at the beginning, during, at the end, or subsequent to the end of the activity. The author dateTime should be used only if the relevantPeriod cannot be obtained or to represent the time negation rationale is documented.
Note: 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.
relevantPeriod
relevantPeriod addresses the time between the start of an action to the end of an action. Each QDM datatype using relevantPeriod 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 datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod