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

Suggestion: HH-02 historic review for diabetes Dx

XMLWordPrintable

    • Icon: EH/CAH eCQMs EH/CAH eCQMs
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • Hide
      Thank you for your suggestion regarding CMS871v3: Hospital Harm - Severe Hyperglycemia. This eCQM relies on the accurate recording of codes and diagnoses in the patients’ EHR, which is essential for the correct calculation of all eCQMs. As the 2024 Annual Update (2025 specifications) has concluded and eCQM specifications are final, changes to the measure cannot be made at this time. However, we will consider your feedback for future iterations of this measure.
      Show
      Thank you for your suggestion regarding CMS871v3: Hospital Harm - Severe Hyperglycemia. This eCQM relies on the accurate recording of codes and diagnoses in the patients’ EHR, which is essential for the correct calculation of all eCQMs. As the 2024 Annual Update (2025 specifications) has concluded and eCQM specifications are final, changes to the measure cannot be made at this time. However, we will consider your feedback for future iterations of this measure.
    • CMS0871v3
    • Reviewing the entire patient's history to find past diabetes codes is overly burdensome for hospitals when the correct population would be adequately identified by limiting diabetes coding/diagnosis to the current encounter.

      The specs for HH-02 indicate that any diabetes diagnosis before or during the encounter will qualify the patient for this measure. I'd like to suggest limiting it to just a diagnosis present during the encounter, or at least a year prior or something.  If diabetes was a true diagnosis and not an error, it will remain active on every encounter.  We are having issues with people pulling into this measure because there was incorrect coding or an errant diagnosis placed on a chart from a long ago encounter that identified them as incorrectly having diabetes.  It's extremely time consuming to try to track down where this errant code is coming from in the entire patient's history.  As our EHR is shared among several hospitals, once you find it, you may have to try to contact the coding department at another hospital to correct coding from 3 years ago or contact a pharmacist about an errant 'reason for visit' diagnosis code they entered once long ago when a patient came in for education. If these patients really had diabetes, it would be captured again during the current hospital admission the measure is reviewing.

            JLeflore Mathematica EH eCQM Team
            jlharlos Jennifer Harlos
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: