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 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 an order for the device 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.

Coded diagnoses/problems addressed during the encounter. The diagnoses attribute has three components:

• diagnosis (code)
• presentOnAdmissionIndicator (code)
• rank (positive integer)

To reference an encounter diagnosis, the expression must include the diagnosis code component. The other components are optional. The expression should only include the presentOnAdmissionIndicator if it is necessary to reference present on admission and should only include the rank if it is necessary to reference principal diagnosis.

The "Encounter, Performed" diagnoses attribute is intended to capture ALL diagnoses, including the principal diagnosis, i.e., all diagnoses addressed during the encounter represented by the diagnosis (code) used in the expression.The presentOnAdmissionIndicator (code) allows the eCQM developer to include criteria about whether each specific "Encounter, Performed" diagnoses was present at the time of admission (an indicator used to evaluate patient safety and adverse events). See presentOnAdmissionIndicator attribute definition and Section A.1.4 for information about using the "Encounter, Performed" diagnoses attribute.

The "Encounter, Performed" diagnoses (rank) replaces the principal diagnosis attribute. To reference a principal diagnosis, eCQM developers should express the "Encounter, Performed" diagnoses with a diagnosis (code) and a rank of 1. See definition of rank in this attribute table.

With an "Encounter, Performed" diagnoses, there is no dependency on the timing of the diagnosis in relation to the encounter.

Use of the "Encounter, Performed": diagnoses attribute component and the "Diagnosis" datatype is redundant for relating the diagnosis to the "Encounter, Performed". The "Encounter, Performed": diagnoses component syntax is preferred.

• Referencing the same diagnosis using "Encounter, Performed" (diagnoses attribute) and "Diagnosis" (datatype) should only occur if the measure must define a specified length of a prevalencePeriod, e.g.,
  • The measure must assure that the diagnoses:
    • have been present for at least some defined time period before the encounter, and
    • were addressed during the "Encounter, Performed"

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 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 completion of the diagnostic study indicated by the QDM category and its corresponding value set.

Timing:

• relevant dateTime references the time the diagnostic study is performed if it occurs at a single point in time.
• relevantPeriod references a start and stop time for an assessment that occurs over a time interval:
  • startTime - when the diagnostic study is initiated.
  • stopTime - when the diagnostic study is completed.
• author dateTime references the time the action was recorded.
• Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples using relevantPeriod:

• Initiation of a treadmill stress test to the time the treadmill stress test has completed
• Initiation of the ultrasound study until completion of the ultrasound study

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 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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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.6 addresses that concept using the diagnosis rank=1.

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 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 the laboratory test indicated by the QDM category and its corresponding value set was performed.

Timing:

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

Examples:

• Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
• Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

• The time that the result report is available is a separate attribute than the time of the study (specimen collection).
• 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 laboratory test indicated by the QDM category and its corresponding value set was performed.

Timing:

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

Examples:

• Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – use relevant dateTime to reference this single point in time for many specimen collections
• Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection – use relevantPeriod to reference the start to stop time for this event.

Notes:

• The time that the result report is available is a separate attribute than the time of the study (specimen collection).
• 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 that the medication indicated by the QDM category and its corresponding value set is being taken by the patient. Keep in mind that when this datatype is used with timing relationships, the criterion is looking for a medication being taken for the time frame indicated by the timing relationships.

Timing:

• relevant dateTime references the time the medication is active on the medication record if it was given or taken at a single point in time.
• relevantPeriod references a start and stop time for an active medication on the medication record that is given or taken over a time interval:
• The relevantPeriod addresses:
  • startTime = when the medication is first known to be used (generally the time of entry on the medication list).
  • stopTime = when the medication is no longer active.

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.

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

Timing:

• relevant dateTime references the time the procedure is performed when the procedure occurs at a single point in time.
• relevantPeriod references a start and stop time for a procedure that occurs over a time interval. relevantPeriod addresses:
  • startTime - The time the procedure begins.
  • stopTime - The time the procedure 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 a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request.
• The incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.
• 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.
• See section 6.4 for guidance about differentiating between successful and unsuccessful procedures.

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

Timing:

• relevant dateTime references the time the procedure is performed when the procedure occurs at a single point in time.
• relevantPeriod references a start and stop time for a procedure that occurs over a time interval. relevantPeriod addresses:
  • startTime - The time the procedure begins.
  • stopTime - The time the procedure 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 a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request.
• The incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.
• 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.
• See section 6.4 for guidance about differentiating between successful and unsuccessful procedures.

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

Timing:

• relevant dateTime references the time the procedure is performed when the procedure occurs at a single point in time.
• relevantPeriod references a start and stop time for a procedure that occurs over a time interval. relevantPeriod addresses:
  • startTime - The time the procedure begins.
  • stopTime - The time the procedure 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 a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request.
• The incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.
• 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.
• See section 6.4 for guidance about differentiating between successful and unsuccessful procedures.

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)

Data elements that meet criteria using this datatype should document the symptom and its corresponding value set.

Timing:

• The prevalencePeriod references the time from the onset date to the abatement date.
• 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 null, then the symptom is considered to still be active. When this datatype is used with timing relationships, the criterion is looking for whether the symptom was active for the time frame indicated by the timing relationships.