Uploaded image for project: 'eCQM Issue Tracker'
  1. eCQM Issue Tracker
  2. CQM-5756

CMS871v2 - Exclusion Query Question

XMLWordPrintable

    • Icon: EH/CAH eCQMs - Eligible Hospitals/Critical Access Hospitals EH/CAH eCQMs - Eligible Hospitals/Critical Access Hospitals
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • Hide
      ​Thank you for your inquiry specific to CMS871v2 (Hospital Harm – Severe Hyperglycemia). We agree with the expectation that the denominator exclusion should be constrained to the specific qualifying encounter. We will evaluate the logic in the next Annual Update.
      Show
      ​Thank you for your inquiry specific to CMS871v2 (Hospital Harm – Severe Hyperglycemia). We agree with the expectation that the denominator exclusion should be constrained to the specific qualifying encounter. We will evaluate the logic in the next Annual Update.
    • CMS0871v2

      Hello,

      We have a follow up question to https://oncprojectracking.healthit.gov/support/browse/CQM-5379.  In CQM-5379 Scenario A and B are different patients.  If the data represented two separate inpatient encounters for the same patient we believe (and bonnie testing supports this) that the patient would have two exclusion results.  Whether this is intended or not, the CQL as written will produce two exclusion results.  This is due to this clause:

      Since the First Lab above is not bound to a specific encounter, the return result will always be the same.  So using the data from CQM-5379 as data for the same patient, when evaluating the second inpatient encounter (05/10/2023 - 05/16/2023) to see if it qualifies for the exclusion the lab test from 04/11/2023 8:00 AM would be used and would cause the encounter to be excluded.

       

       

      Is this the correct behavior, or is this an issue with the CQL?  

       

      Thank you.

            JLeflore Joelencia Leflore
            jwaite Joshua Waite
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: