CMS 996 STEMI Denominator Exception

XMLWordPrintable

    • Type: Hosp Outpt eCQMs - Hospital Outpatient eCQMs
    • Resolution: Answered
    • Priority: Moderate
    • Component/s: None
    • None
    • Hide
      Thank you for your inquiry regarding CMS996v6, Appropriate Treatment for ST-Segment Elevation Myocardial Infarction (STEMI) Patients in the Emergency Department (ED). According the QDM 5.6, (https://ecqi.healthit.gov/sites/default/files/QDM-v5.6-508.pdf ) the negation rationale attribute value indicates a one-time documentation of a reason an activity is not performed. Since the negation rationale indicates the documentation of the reason, and not the clinical identification of the reason, “negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing”. The QDM currently does not have an attribute to specify the period a negation rationale is clinically relevant.
      Show
      Thank you for your inquiry regarding CMS996v6, Appropriate Treatment for ST-Segment Elevation Myocardial Infarction (STEMI) Patients in the Emergency Department (ED). According the QDM 5.6, ( https://ecqi.healthit.gov/sites/default/files/QDM-v5.6-508.pdf ) the negation rationale attribute value indicates a one-time documentation of a reason an activity is not performed. Since the negation rationale indicates the documentation of the reason, and not the clinical identification of the reason, “negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing”. The QDM currently does not have an attribute to specify the period a negation rationale is clinically relevant.
    • CMS1244v1
    • CMS0996v6
    • CMS0996v5
    • CMS0996v4

      Specifications say:
          • ED Encounter With A Documented Reason For No PCI Performed Within 90 Minutes Of ED Arrival 
                      §   "ED Encounter With STEMI Diagnosis" EDwSTEMI
          with (["Procedure, Not Performed": "Percutaneous Coronary Intervention"] NoPCI
                where (NoPCI.negationRationale in "Patient Refusal" or NoPCI.negationRationale in "Procedure Not Indicated/Contraindicated")) PCIRefused
          such that PCIRefused.authorDatetime during EDwSTEMI.relevantPeriod
        
          • ED Encounter With A Documented Reason For Not Administering Fibrinolytic Therapy Within 30 Minutes Of ED Arrival 
                      §   "ED Encounter With STEMI Diagnosis" EDwSTEMI
          with (["Medication, Not Administered": "Fibrinolytic Therapy"] NoFibrinolytic
                where (NoFibrinolytic.negationRationale in "Patient Refusal" or NoFibrinolytic.negationRationale in "Drug Intervention Not Indicated/Contraindicated")) FibrinolyticRefused
          such that FibrinolyticRefused.authorDatetime during EDwSTEMI.relevantPeriod

      Both data elements are looking at authorDatetime.

      Referencing https://oncprojectracking.healthit.gov/support/si/jira.issueviews:issue-html/CQM-8628/CQM-8628.html "Therefore, in the example you provided, if the contraindication is clinically identified at 2:00 AM, but is documented at 5:00 AM, the author Datetime associated with the entry would be 5:00 AM. If the ED encounter ended after 5:00 AM (e.g., 6:00 AM), then the encounter would meet the denominator exception criteria. However, if the ED encounter ends before 5:00 AM, (e.g., 4:00 AM), then the encounter would not meet the denominator exception criteria."

      In order to qualify for a denominator exception it would seem based on measure intent, that the time of the contraindication (Reason for not) should not matter as long as there is documentation at some point during to indicate. But based on the feedback and CQL it is using authorDatetime.

      Can you please explain why and for what purpose authorDatetime is used vs using a clinically relevant time (in the example above 2AM) and allowing that to qualify instead?

            Assignee:
            Mathematica EH eCQM Team
            Reporter:
            Becky Crellin (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: