Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

• relevant dateTime references timing for an assessment that occurs at a single point in time.
• relevant Period references a start and stop time for an assessment that occurs over a time interval
• author dateTime references the time the action was recorded.
• Refer to the eCQM expression to determine allowable timings to meet measure criterion.

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.

Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set.

Timing:

• relevant dateTime references timing for an assessment that occurs at a single point in time.
• relevant Period references a start and stop time for an assessment that occurs over a time interval
• author dateTime references the time the action was recorded.
• Refer to the eCQM expression to determine allowable timings to meet measure criterion.

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.

Data elements that meet criteria using this datatype should document the Condition/Diagnosis/Problem and its corresponding value set. The onset dateTime corresponds to the implicit start dateTime of the datatype and the abatement dateTime corresponds to the implicit stop dateTime of the datatype. If the abatement dateTime is not present, then the diagnosis is considered to still be active. When this datatype is used with timing relationships, the criterion is looking for an active diagnosis for the time frame indicated by the timing relationships.

Timing: The prevalencePeriod references the time from the onset date to the abatement date.

Data elements that meet criteria using this datatype should document the Condition/Diagnosis/Problem and its corresponding value set. The onset dateTime corresponds to the implicit start dateTime of the datatype and the abatement dateTime corresponds to the implicit stop dateTime of the datatype. If the abatement dateTime is not present, then the diagnosis is considered to still be active. When this datatype is used with timing relationships, the criterion is looking for an active diagnosis for the time frame indicated by the timing relationships.

Timing: The prevalencePeriod references the time from the onset date to the abatement date.

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here. 

Timing:

• The relevantPeriod addresses:
  • startTime - The time the encounter began (admission time).
  • stopTime - The time the encounter ended (discharge time).
• author dateTime references the time the action was recorded.
• Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

• 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.
• The locationPeriod is an attribute of the attribute facility location that addresses:
  • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
  • stopTime - the time the patient departed from the location.

Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here. 

Timing:

• The relevantPeriod addresses:
  • startTime - The time the encounter began (admission time).
  • stopTime - The time the encounter ended (discharge time).
• author dateTime references the time the action was recorded.
• Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

• 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.
• The locationPeriod is an attribute of the attribute facility location that addresses:
  • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
  • stopTime - the time the patient departed from the location.

Data elements that meet criteria using this datatype should document a request to perform the intervention indicated by the QDM category and its corresponding value set.

Timing: The time the order is signed; author dateTime.

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.

Data elements that meet criteria using this datatype should document a request to perform the intervention indicated by the QDM category and its corresponding value set.

Timing: The time the order is signed; author dateTime.

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.

Data elements that meet criteria using this datatype should document the completion of the intervention indicated by the QDM category and its corresponding value set.

Timing:

• relevant dateTime references the time the intervention is performed when the intervention occurs at a single point in time.
• relevantPeriod references a start and stop time for an intervention that occurs over a time interval. relevantPeriod addresses:
  • startTime - The time the intervention begins.
  • stopTime - The time the intervention ends.
• author dateTime references the time the action was recorded.
• Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Notes:

• Timing refers to a single instance of an intervention. If a measure seeks to evaluate multiple interventions over a period of time, the measure developer should use CQL logic to represent the query request.
• 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.
   

Data elements that meet criteria using this datatype should document the completion of the intervention indicated by the QDM category and its corresponding value set.

Timing:

• relevant dateTime references the time the intervention is performed when the intervention occurs at a single point in time.
• relevantPeriod references a start and stop time for an intervention that occurs over a time interval. relevantPeriod addresses:
  • startTime - The time the intervention begins.
  • stopTime - The time the intervention ends.
• author dateTime references the time the action was recorded.
• Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Notes:

• Timing refers to a single instance of an intervention. If a measure seeks to evaluate multiple interventions over a period of time, the measure developer should use CQL logic to represent the query request.
• 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.
   

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) or the reason for not ordering the medication (i.e., negationRationale) 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.

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) or the reason for not ordering the medication (i.e., negationRationale) 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.

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.

A QDM Known Issue has been identified related to this attribute. To see this QDM known Issue, please click here.

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.

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.

A QDM Known Issue has been identified related to this attribute. To see this QDM known Issue, please click here.

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.

The "Patient Characteristic Birthdate" should document the patient’s date of birth.

Timing: The "Patient Characteristic, Birthdate" is a single point in time representing the date and time of birth. It does not have a start and stop time.

Note: "Patient Characteristic Birthdate" is fixed to LOINC code 21112-8 (Birth date) and therefore cannot be further qualified with a value set.

Data elements that meet criteria using this datatype should document that the patient has one or more of the ethnicities indicated by the QDM category and its corresponding value set.

Timing: Ethnicity does not have a specific timing. Measures using "Patient Characteristic, Ethnicity" should address the most recent entry in the clinical record.

Data elements that meet criteria using this datatype should document that the patient has one or more of the payers indicated by the QDM category and its corresponding value set.

Timing:

The relevantPeriod addresses:

• startTime – the first day of insurance coverage with the referenced payer.
• stopTime – the last day of insurance coverage with the referenced payer.

Data elements that meet criteria using this datatype should document the patient’s race.

Timing: Race does not have a specific timing. Measures using "Patient Characteristic, Race" should address the most recent entry in the clinical record.

Data elements that meet criteria using this datatype should document that the patient's sex matches the QDM category and its corresponding value set.

Timing: Birth (administrative) sex does not have a specific timing.

The final consequences or data collected from the datatype. results can be used in four ways to express:

• That a result is present in the electronic record but any entry is acceptable
• A numerical result is reported directly as a value. Values may be integers or decimal numbers without units, or as a quantity with a value and units - examples:
  • 100mg/dL for a lab test
  • 140 mmHg for blood pressure
  • as a percentage (actually as a quantity with % as units)
  • as a titer or ratio (e.g., 1:4, 1:80)
• A result that matches one of a specific set of coded concepts in a value set or a code that matches a direct reference code
• A result as a dateTime ("Assessment, Performed" and components)

The final consequences or data collected from the datatype. results can be used in four ways to express:

• That a result is present in the electronic record but any entry is acceptable
• A numerical result is reported directly as a value. Values may be integers or decimal numbers without units, or as a quantity with a value and units - examples:
  • 100mg/dL for a lab test
  • 140 mmHg for blood pressure
  • as a percentage (actually as a quantity with % as units)
  • as a titer or ratio (e.g., 1:4, 1:80)
• A result that matches one of a specific set of coded concepts in a value set or a code that matches a direct reference code
• A result as a dateTime ("Assessment, Performed" and components)