Data elements that meet criteria using this datatype should document that the vaccine indicated by the QDM category and its corresponding value set was actually administered to the patient. Timing: The time the immunization is administered, i.e., a single point in time, or Author dateTime.
A statement that asserts an action relating to the subject. The subject is often the patient, but may....
The time the data element was entered into the clinical software. Note, some datatypes include both Relevant Time and Author dateTime attributes. The purpose is to accommodate Author dateTime if the actual start and stop times are not available when evaluating for feasibility, and also to allow specification of a time for Negation Rationale.
DataTypeCardinalityThe 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.
DataTypeCardinalityDetails of how medication is taken or is to be taken, i.e., the quantity (mg, cc, tablets) to be taken at a single administration.
DataTypeCardinalityThe 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. Note: 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).
DataTypeCardinalityRefers to the path by which the medication or substance should be taken into the body systems, such as intradermally, intrathecally, intramuscularly, intranasally, intravenously, orally, rectally, subcutaneously, sublingually, topically, or vaginally.
DataTypeCardinalityIndicates 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 Vs lack of documentation about allergies). The syntax in the human readable HQMF is address in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, “Procedure, Performed not done.” QDM 5.0 DRAFT uses the syntax, “Procedure, not Performed.” Note: Some datatypes include both Relevant Time and Author dateTime attributes. The purpose is to accommodate Author dateTime if the actual start and stop times are not available when evaluating for feasibility, and also to allow specification of a time for Negation Rationale.
DataTypeCardinality