Due to the federal government shutdown, the eCQI Resource Center has paused updates to site information.
Any updates, questions, and requests will resume when the government is re-opened. Note this includes all eCQM related help desks and Jira.
Top
Official websites use
.gov
A .gov website belongs to an official government organization in the United States.
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, Order"
Performance/Reporting Period
2022
QDM Datatype (QDM Version 5.5 Guidance Update):
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.
- 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 medication order (prescription) is authored.
Notes:
- When calculating cumulative medication duration, the stopTime may be present directly in the medication order. If the stopTime is not available, the duration in days is the difference between the relevantPeriod start and stop times multiplied by (1 + the number of refills).
- 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.
QDM Datatype and Definition
Medication
Medication represents clinical drugs or chemical substances intended for use in the medical diagnosis, cure, treatment, or prevention of disease. Medications are defined as directly referenced values or value sets containing values derived from code systems such as RxNorm.
Data Elements defined by this QDM Datatype:
QDM Attributes
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.
daysSupplied
Amount of medication expressed as a timing amount, i.e., the number of days over which the medication is expected to last.
dosage
Details of how much medication is taken or is to be taken, i.e., the quantity (mg, cc, tablets) to be taken at a single administration.
frequency
Indicates how frequently the medication or substance:
- Is administered to a patient for an active medication (a).
- Was administered to the patient (b).
- Should be taken by the patient or administered to the patient (c).
- Is recommended to be given to the patient (d).
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.
prescriber
The person who ordered the prescription.
The prescriber attribute references the new QDM entities (patient, care partner, practitioner, or organization) and any or all of the attributes of the respective QDM entity. For example, to reference that a physician who prescribed a medication is the same person who was the primary participant in an Encounter and assure the physician's specialty meets the measures requirements, the eCQM can use the Practitioner Entity and its attributes.
Should the eCQM choose to reference a physician practice or a hospital, the performer can reference the Organization Entity and indicate the identifier and/or the organization type.
The CQL can specify which identifier the measure expects to be used (e.g., National Provider Identifier or Tax Identifier Number) or it can avoid referencing an identifier to allow the implementing organization or practice to use its own identifier.
reason
The thought process or justification for the datatype. In some measures, specific treatments are acceptable inclusion criteria only if a justified reason is present. Each of these measures uses a value set (often, but not exclusively, using SNOMED CT) to express acceptable justification reasons. Other measures specify reasons as justification for exclusions. Examples include patient, system, or medical-related reasons for declining to perform specific actions. Each of these measures also uses a value set to express acceptable justification reasons for declining to perform expected actions.
refills
The number of refills allowed by the prescription.
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
route
Refers to the path by which the medication or substance should be taken into the body system, such as intradermally, intrathecally, intramuscularly, intranasally, intravenously, orally, rectally, subcutaneously, sublingually, topically, or vaginally.
setting
Where the medication is expected to be consumed or administered. Examples:
- Inpatient - in the hospital during the current inpatient stay
- Outpatient - in an outpatient facility such as an ambulatory surgical center
- Community - in the ambulatory setting (e.g., at home)
supply
The quantity (amount) of therapeutic agent that was provided to a patient (i.e., number of doses, number of tablets or pills, volume of medication) indicated to be given during a procedure, diagnostic test, or medication, or substance administration.
Note: Prior versions of the QDM (4.3 and earlier) addressed dose with two potential interpretations - (1) the quantity to be taken or administered with each administration and (2) the quantity of medication supplied (i.e., number of doses). QDM 5.0 and subsequent versions clarify the difference by defining dosage and supply, respectively.
- "Medication, Discharge" includes medications the provider has indicated the patient should take after dischange from the hospital. This medication list is part of the discharge instructions provided to a patient. The list may include medication supply if it incorporates medication orders written at discharge even though the supply will not be present for medications the patient already has at home or purchases over-the-counter (without a prescription).
Last Updated: Jul 08, 2021