OP-40 Inclusion of Recent MI Due to ICD-10 Diagnosis Code

XMLWordPrintable

    • Type: Hosp Outpt eCQMs - Hospital Outpatient eCQMs
    • Resolution: Answered
    • Priority: Moderate
    • Component/s: None
    • None
    • Lynee Liermann
    • 402-717-2616
    • CommonSpirit Health
    • Hide
      Thank you for your inquiry regarding CMS996: Appropriate Treatment for ST-Segment Elevation Myocardial Infarction (STEMI) Patients in the Emergency Department (ED).

      We emphasize that the QDM does not prescribe the source of diagnosis data, only the type of data needed. It was designed to support heterogeneous data sources, enable human abstraction, and provide flexibility across systems. Therefore, hospitals may choose to source diagnosis data from a patient’s problem list, encounter diagnosis list, claims data, or other sources within the EHR. Furthermore, the "Encounter, Performed" diagnoses attribute is intended to capture all diagnoses addressed during the encounter represented by the diagnosis (code) used in the expression.
      CMS996 evaluates STEMI diagnoses based on how they are represented and timed within the QDM data model rather than their original clinical or billing context. The measure intends to capture STEMI during the ED encounter only.

      Within QDM, a diagnosis is represented with a prevalence period, where the onset dateTime corresponds to the start dateTime of the diagnosis and the abatement dateTime corresponds to the stop dateTime of the diagnosis. For CMS996, however, the measure logic does not evaluate diagnosis abatement, duration, or whether a diagnosis is ongoing. Instead, the logic evaluates whether a STEMI diagnosis is represented as beginning during the emergency department encounter or whether STEMI appears on the ED encounter diagnosis list.

      As a result, patients may be included in the CMS996 Initial Population when a STEMI diagnosis is represented in either of the following ways during a subsequent emergency department encounter:
      • the STEMI diagnosis onset dateTime (prevalencePeriod.start) is recorded as occurring during the ED encounter relevant period (the time from ED arrival or admission to ED discharge), or
      • the STEMI diagnosis is mapped to the ED encounter diagnosis list.

      In these scenarios, a prior STEMI diagnosis that remains reportable for coding or documentation purposes may be represented in a way that meets the CMS996 inclusion criteria, even when the ED visit is for an unrelated reason.

      To reduce the inclusion of historical STEMI diagnoses in CMS996, we recommend ensuring that STEMI is not documented as an ED encounter diagnosis unless it is actively being evaluated or treated during that encounter. Historical STEMI diagnoses should instead be documented in the patient’s problem list or another longitudinal diagnosis source that maps to the QDM “Diagnosis” datatype, with the onset dateTime accurately reflecting when the STEMI originally occurred. This ensures that the diagnosis does not appear to begin during an unrelated ED encounter and aligns the data representation with the intent of the measure logic.

      For reference, the CMS996 v6.3.000 measure logic defining an ED Encounter with STEMI Diagnosis is included below. This logic is also available on the eCQI Resource Center: [https://ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS996-v6.3.000-QDM.html]:

      ED Encounter with STEMI Diagnosis
      "ED Encounter During MP" EDEncounterinMP
          where (exists (["Diagnosis": "STEMI"] DxSTEMI
            where DxSTEMI.prevalencePeriod starts during EDEncounterinMP.relevantPeriod))
          or (exists( EDEncounterinMP.diagnoses EncounterDiagnosis
            where EncounterDiagnosis.code in "STEMI" ))
      Show
      Thank you for your inquiry regarding CMS996: Appropriate Treatment for ST-Segment Elevation Myocardial Infarction (STEMI) Patients in the Emergency Department (ED). We emphasize that the QDM does not prescribe the source of diagnosis data, only the type of data needed. It was designed to support heterogeneous data sources, enable human abstraction, and provide flexibility across systems. Therefore, hospitals may choose to source diagnosis data from a patient’s problem list, encounter diagnosis list, claims data, or other sources within the EHR. Furthermore, the "Encounter, Performed" diagnoses attribute is intended to capture all diagnoses addressed during the encounter represented by the diagnosis (code) used in the expression. CMS996 evaluates STEMI diagnoses based on how they are represented and timed within the QDM data model rather than their original clinical or billing context. The measure intends to capture STEMI during the ED encounter only. Within QDM, a diagnosis is represented with a prevalence period, where the onset dateTime corresponds to the start dateTime of the diagnosis and the abatement dateTime corresponds to the stop dateTime of the diagnosis. For CMS996, however, the measure logic does not evaluate diagnosis abatement, duration, or whether a diagnosis is ongoing. Instead, the logic evaluates whether a STEMI diagnosis is represented as beginning during the emergency department encounter or whether STEMI appears on the ED encounter diagnosis list. As a result, patients may be included in the CMS996 Initial Population when a STEMI diagnosis is represented in either of the following ways during a subsequent emergency department encounter: • the STEMI diagnosis onset dateTime (prevalencePeriod.start) is recorded as occurring during the ED encounter relevant period (the time from ED arrival or admission to ED discharge), or • the STEMI diagnosis is mapped to the ED encounter diagnosis list. In these scenarios, a prior STEMI diagnosis that remains reportable for coding or documentation purposes may be represented in a way that meets the CMS996 inclusion criteria, even when the ED visit is for an unrelated reason. To reduce the inclusion of historical STEMI diagnoses in CMS996, we recommend ensuring that STEMI is not documented as an ED encounter diagnosis unless it is actively being evaluated or treated during that encounter. Historical STEMI diagnoses should instead be documented in the patient’s problem list or another longitudinal diagnosis source that maps to the QDM “Diagnosis” datatype, with the onset dateTime accurately reflecting when the STEMI originally occurred. This ensures that the diagnosis does not appear to begin during an unrelated ED encounter and aligns the data representation with the intent of the measure logic. For reference, the CMS996 v6.3.000 measure logic defining an ED Encounter with STEMI Diagnosis is included below. This logic is also available on the eCQI Resource Center: [ https://ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS996-v6.3.000-QDM.html ]: ED Encounter with STEMI Diagnosis "ED Encounter During MP" EDEncounterinMP     where (exists (["Diagnosis": "STEMI"] DxSTEMI       where DxSTEMI.prevalencePeriod starts during EDEncounterinMP.relevantPeriod))     or (exists( EDEncounterinMP.diagnoses EncounterDiagnosis       where EncounterDiagnosis.code in "STEMI" ))
    • CMS0996v6

      I have concerned about the inclusion of recent STEMI cases in the OP-40 population. These cases are included because of claims data using ICD-10 acute STEMI diagonsis codes up to 4 weeks after a STEMI (this is correct coding guidance).  Our system had 6 cases in the denominator in 2025 that weren't admitted for a STEMI during the evaluation period. There have been several questions about this topic and the answers from Jira note to ensure there is both an onset and abatement time on the problem list for the STEMI diagnosis. 

      However, the STEMI diagnosis is not coming from a problem list but rather the claims/coding data for the case and coded data does not have an onset or abatement date but just rather an inclusion ICD Code and POA indicator of Yes. Any other thoughts about how to remove these patients from the population? 

      Can we build the logic to not use ICD claims data for the ED Encounter with STEMI diagnosis and only use the problem list? 

            Assignee:
            Mathematica EH eCQM Team
            Reporter:
            Lynee Liermann
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: