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

CMS 122 and CMS 145

XMLWordPrintable

    • Icon: EC eCQMs - Eligible Clinicians EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • David Compton
    • 417-576-7039
    • CoxHealth
    • Hide
      Thank you for your question related to CMS122v12 and CMS145v12. The initial population logic for CMS122v12 requires that the diabetes diagnosis overlaps the measurement period. The overlaps function means the diagnosis must be present in the EHR anytime during the measurement period, e.g., starting during the measurement period, or starting before the measurement period and continues into the measurement period. Presence of a diabetes diagnosis code from the "Diabetes" value set (2.16.840.1.113883.3.464.1003.103.12.1001) in the patient’s EHR meeting this timing requirement is what determines whether the patient meets criteria for being in the initial population and denominator.

      Similarly, according to the measure specification for CMS145v12, in order for a patient to be included in the initial population for this measure, a patient must have two Qualifying Encounters during the measurement period as well as a Qualifying CAD encounter. In the measure logic a Qualifying CAD Encounter is defined as a Qualifying Encounter in which a diagnosis of Coronary Artery Disease (without a history of Myocardial Infarction) overlaps after the day of the encounter. This means any Qualifying Encounter for patients who have a CAD diagnosis documented prior to or during the encounter is considered a Qualifying CAD Encounter, so long as the CAD diagnosis does not have an abatement date/time documented in the medical record prior to the end of the encounter date/time. This includes CAD diagnoses documented any time prior to the measurement period.
      Show
      Thank you for your question related to CMS122v12 and CMS145v12. The initial population logic for CMS122v12 requires that the diabetes diagnosis overlaps the measurement period. The overlaps function means the diagnosis must be present in the EHR anytime during the measurement period, e.g., starting during the measurement period, or starting before the measurement period and continues into the measurement period. Presence of a diabetes diagnosis code from the "Diabetes" value set (2.16.840.1.113883.3.464.1003.103.12.1001) in the patient’s EHR meeting this timing requirement is what determines whether the patient meets criteria for being in the initial population and denominator. Similarly, according to the measure specification for CMS145v12, in order for a patient to be included in the initial population for this measure, a patient must have two Qualifying Encounters during the measurement period as well as a Qualifying CAD encounter. In the measure logic a Qualifying CAD Encounter is defined as a Qualifying Encounter in which a diagnosis of Coronary Artery Disease (without a history of Myocardial Infarction) overlaps after the day of the encounter. This means any Qualifying Encounter for patients who have a CAD diagnosis documented prior to or during the encounter is considered a Qualifying CAD Encounter, so long as the CAD diagnosis does not have an abatement date/time documented in the medical record prior to the end of the encounter date/time. This includes CAD diagnoses documented any time prior to the measurement period.
    • CMS0122v12, CMS0145v12
    • Patients would be erroneously included in the denominator.

      Both measures include the need for a Diagnosis during the reporting period. Can past medical history (e.g. Problems list) meet the need for a Diagnosis, even if the condition is not assessed or specifically diagnosed during a qualifying encounter during the reporting period? 

      "Diagnosis": "Coronary Artery Disease No MI - CMS 145
      "Diagnosis": "Diabetes"] Diabetes - CMS 122

            AIR EC eCQM Team AIR EC eCQM Team
            david.compton@coxhealth.com David Compton
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: