Clarification on Denominator Inclusion for ED STEMI Cases When Final Diagnosis Rules Out STEMI

XMLWordPrintable

    • Type: Hosp Outpt eCQMs - Hospital Outpatient eCQMs
    • Resolution: Answered
    • Priority: Moderate
    • Component/s: None
    • None
    • Kris Majumdar
    • 5738842373
    • University of Missouri Health Care
    • Hide
      Thank you for your inquiry regarding CMS996v5: Appropriate Treatment for ST-Segment Elevation Myocardial Infarction (STEMI) Patients in the Emergency Department (ED).

      It is the measure’s intent to only capture events occurring in the ED encounter, not outside of it. As noted in the response to your initial inquiry, a patient with a STEMI diagnosis may be captured in the measure in two ways, as indicated by the measure logic definition below found in version 5 of the measure’s HTML file [https://ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS996v5.html#d1e649].

      ED Encounter with STEMI Diagnosis
      "ED Encounter with Encounter Diagnosis of STEMI"
        union "ED Encounter with Diagnosis of STEMI"

      ED Encounter with Encounter Diagnosis of STEMI
      "ED Encounter During MP" EDEncounter
        with EDEncounter.diagnoses EncounterDiagnosis
          such that EncounterDiagnosis.code in "STEMI"

      ED Encounter with Diagnosis of STEMI
      "ED Encounter During MP" EDEncounter
        with ["Diagnosis": "STEMI"] DxSTEMI
          such that DxSTEMI.prevalencePeriod starts during EDEncounter.relevantPeriod

      An ED encounter with STEMI diagnosis is defined as either (i) a STEMI diagnosis coded during the encounter, which corresponds to the “ED Encounter with Encounter Diagnosis of STEMI” logic definition and uses the “Encounter, Performed” diagnoses attribute, or (ii) a STEMI diagnoses pulled from a claim, problem list, or other source within the EHR where the prevalence period starts (i.e., the onset dateTime of the diagnosis) during the ED encounter. The latter corresponds to the “ED Encounter with Diagnosis of STEMI” logic definition and uses the “Diagnoses” data type. Please note that STEMI diagnoses are identified using the codes in the STEMI value set (OID: 2.16.840.1.113883.3.3157.4017).

      For context, the Quality Data Model (QDM) provides the language that defines the criteria for clinical quality measurement. In other words, it defines the type of data required, rather than the source of the data or how data is represented in real-world systems. It was designed to support heterogeneous data sources, enable human abstraction, and provide flexibility across systems.

      Per the QDM 5.6, the “Encounter, Performed” diagnoses attribute is intended to capture ALL diagnoses addressed during the encounter. If the ED initially suspected STEMI, and the patient was treated as such during the ED encounter, the patient would be counted in the measure denominator. Additionally, the “Diagnosis” data type represents a practitioner’s identification of a patient’s disease, illness, injury, or condition by means of examination, diagnostic test results, patient history, and/or family history.

      For more information regarding “Diagnosis” and “Encounter, Performed” QDM datatypes and their attributes, please see the QDM 5.6: https://ecqi.healthit.gov/sites/default/files/QDM-v5.6-508.pdf.
      Show
      Thank you for your inquiry regarding CMS996v5: Appropriate Treatment for ST-Segment Elevation Myocardial Infarction (STEMI) Patients in the Emergency Department (ED). It is the measure’s intent to only capture events occurring in the ED encounter, not outside of it. As noted in the response to your initial inquiry, a patient with a STEMI diagnosis may be captured in the measure in two ways, as indicated by the measure logic definition below found in version 5 of the measure’s HTML file [ https://ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS996v5.html#d1e649 ]. ED Encounter with STEMI Diagnosis "ED Encounter with Encounter Diagnosis of STEMI"   union "ED Encounter with Diagnosis of STEMI" ED Encounter with Encounter Diagnosis of STEMI "ED Encounter During MP" EDEncounter   with EDEncounter.diagnoses EncounterDiagnosis     such that EncounterDiagnosis.code in "STEMI" ED Encounter with Diagnosis of STEMI "ED Encounter During MP" EDEncounter   with ["Diagnosis": "STEMI"] DxSTEMI     such that DxSTEMI.prevalencePeriod starts during EDEncounter.relevantPeriod An ED encounter with STEMI diagnosis is defined as either (i) a STEMI diagnosis coded during the encounter, which corresponds to the “ED Encounter with Encounter Diagnosis of STEMI” logic definition and uses the “Encounter, Performed” diagnoses attribute, or (ii) a STEMI diagnoses pulled from a claim, problem list, or other source within the EHR where the prevalence period starts (i.e., the onset dateTime of the diagnosis) during the ED encounter. The latter corresponds to the “ED Encounter with Diagnosis of STEMI” logic definition and uses the “Diagnoses” data type. Please note that STEMI diagnoses are identified using the codes in the STEMI value set (OID: 2.16.840.1.113883.3.3157.4017). For context, the Quality Data Model (QDM) provides the language that defines the criteria for clinical quality measurement. In other words, it defines the type of data required, rather than the source of the data or how data is represented in real-world systems. It was designed to support heterogeneous data sources, enable human abstraction, and provide flexibility across systems. Per the QDM 5.6, the “Encounter, Performed” diagnoses attribute is intended to capture ALL diagnoses addressed during the encounter. If the ED initially suspected STEMI, and the patient was treated as such during the ED encounter, the patient would be counted in the measure denominator. Additionally, the “Diagnosis” data type represents a practitioner’s identification of a patient’s disease, illness, injury, or condition by means of examination, diagnostic test results, patient history, and/or family history. For more information regarding “Diagnosis” and “Encounter, Performed” QDM datatypes and their attributes, please see the QDM 5.6: https://ecqi.healthit.gov/sites/default/files/QDM-v5.6-508.pdf .
    • CMS0996v6
    • eSTEMI (OP-40) eCQM

      I previously reached out with a question regarding which diagnosis should be included in the capture of STEMI in CMS996v6 – Appropriate Treatment for ST‑Segment Elevation Myocardial Infarction (STEMI) eCQM. Unfortunately, the response (did not address the specific scenario we are concerned about.

      As I understand it, the measure denominator includes all emergency department (ED) encounters with a documented STEMI diagnosis during the ED visit, typically based on the admitting or initial ED diagnosis, while the numerator requires that the patient receive timely STEMI-specific treatment (fibrinolysis or PCI) during the ED encounter.

      We seek clarification on the following scenario:

      A patient presents to the ED with an admitting/provisional diagnosis of STEMI, but after further evaluation outside the ED (e.g., following hospital admission or CathLab evaluation), the final confirmed diagnosis is determined not to be STEMI.

      1. Does the initial ED/admitting diagnosis alone place the patient in the CMS996v6 denominator, even if STEMI-specific treatment is not administered?
      1. If the final diagnosis rules out STEMI after leaving the ED, should the patient still be counted in the denominator for measure reporting purposes?
      1. Does CMS provide guidance or exceptions for cases where the ED initially suspected STEMI, but subsequent evaluation confirms STEMI was not present?

      We note that the measure specifications (as posted in [eCQI|Appropriate Treatment for ST-Segment Elevation Myocardial Infarction (STEMI) Patients in the Emergency Department (ED) 5.1.000]) do not define the type of diagnosis required, which creates potential confusion. Clinically, only a confirmed STEMI would warrant STEMI-specific treatment such as fibrinolysis or PCI. Including patients whose STEMI was ruled out after ED evaluation could result in denominator cases where treatment is not appropriate, thereby artificially lowering performance.

      We are seeking explicit verification of how CMS defines “diagnosis” for this measure in scenarios where the final confirmed diagnosis occurs after the ED encounter, to ensure accurate and compliant reporting.

      Thank you for your guidance and clarification.

            Assignee:
            Mathematica EH eCQM Team
            Reporter:
            Kris Majumdar
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: