["Medication, Discharge": "Statin Grouper"]
Data Element Scope: This value set may use a model element related to Medication.
Inclusion Criteria: Includes concepts that represent a medication specific to generic, single and multiple ingredient, prescibable statin medication, including oral dose forms.
Exclusion Criteria: No exclusions.
Constrained to codes in the Medication, Discharge: Statin Grouper value set (2.16.840.1.113762.1.4.1110.19)
"Medication, Discharge"
Data elements that meet criteria using this datatype should document that the medications indicated by the QDM category and its corresponding value set should be taken by or given to the patient after being discharged from an inpatient encounter.
Note: the QDM "Medication, Discharge" datatype includes the supply attribute since some EHRs populate some medications on the medications discharge list provided to the patient from prescriptions written at discharge. Therefore, such newly prescribed medications may include the supply prescribed. Other medications on the discharge medication list will not have supply information since they represent medications for which the patient already has a supply at home or those the patient may purchase without prescription (i.e., over-the-counter). Thus, measure developers need to address data availability and feasibility when using the supply attribute with "Medication, Discharge".
Timing: The time the discharge medication list on the discharge instruction form is authored.
The "Medication, Discharge" QDM datatype includes two performers or actors - prescriber and recorder. The list of medications a patient should take after hospital discharge may come from two sources. The first source originates from medications ordered from a community pharmacy directly from the clinical software (e.g., eprescribing). That source will include the prescriber. The second method of providing content for the discharge medication list is via entry of medications known to be present in the home or over-the-counter substances, neither of which result in a prescription. The individual entering these latter medications is the recorder. Hence, content in the discharge medication list may include both performers.
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.
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.
negationRationale
Indicates the reason that an action was not performed. Only QDM datatypes that represent actions (e.g., performed, recommended, communication, order, dispensed) allow the negation rationale attribute. The intent is to indicate a justification that such action did not happen as expected. This attribute specifically does not address the presence or absence of information in a clinical record (e.g., documented absence of allergies versus lack of documentation about allergies). QDM assumes a world view that absence of evidence indicates information does not exist or an action did not happen. To express such lack of evidence, an eCQM author should use the CQL expression not exists with reference to the data element rather than the QDM data model. negation rationale in QDM signifies only a reason for such absence, i.e., the reason must be present to qualify for negation rationale. The syntax in the human readable HQMF is addressed in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, "Procedure, Performed not done." QDM versions starting with 5.3 use the syntax, "Procedure, not Performed." Section A-5 provides examples for expressing negation rationale in CQL.
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.