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

CMS 144/145 Pacemaker Time Constraints

XMLWordPrintable

    • Icon: EC eCQMs - Eligible Clinicians EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • Hide
      Thank you for reaching out with your question concerning CMS144v11/12 and CMS145v11/12 Heart Failure: Beta-Blocker Therapy for Left Ventricular Systolic Dysfunction (LVSD) & CAD: Beta-Blocker Therapy-Prior MI or Left Ventricular Systolic Dysfunction. You are correct that there is no procedural logic expression that would allow a patient to meet this exception if they’ve ever had a cardiac pacer implantation procedure. This element is intentionally authored this way, as per our clinical experts,”patients who have advanced atrioventricular block requiring cardiac pacer are usually pacer dependent and usually require a pacemaker re-implantation, even if the original pacer is removed or modified”. Due to these patients having a clinical dependency on cardiac pacer, there is no provision for pacer removal.

      Show
      Thank you for reaching out with your question concerning CMS144v11/12 and CMS145v11/12 Heart Failure: Beta-Blocker Therapy for Left Ventricular Systolic Dysfunction (LVSD) & CAD: Beta-Blocker Therapy-Prior MI or Left Ventricular Systolic Dysfunction. You are correct that there is no procedural logic expression that would allow a patient to meet this exception if they’ve ever had a cardiac pacer implantation procedure. This element is intentionally authored this way, as per our clinical experts,”patients who have advanced atrioventricular block requiring cardiac pacer are usually pacer dependent and usually require a pacemaker re-implantation, even if the original pacer is removed or modified”. Due to these patients having a clinical dependency on cardiac pacer, there is no provision for pacer removal.
    • CMS0144v12, CMS0145v12
    • CMS0144v11, CMS0145v11
    • We want to ensure our SQL reports are aligning with the intention of the measure, despite the specification logic seemingly being inconsistent.

      For the CMS 144/145, there is a denominator exception for when a patient has an active diagnosis of atrioventricular block and not a pacemaker. In the specifications, this is described in the "Has Diagnosis of Cardiac Pacer in Situ" ** and "Has Cardiac Pacer Device Implanted" data terms. 

      For "Has Diagnosis of Cardiac Pacer in Situ", the specifications make it clear that this diagnosis must overlap the Heart Failure encounter:
      such that CardiacPacerDiagnosis.prevalencePeriod overlaps after ModerateOrSevereLVSDHFOutpatientEncounter.relevantPeriod
      For the "Has Cardiac Pacer Device Implanted", the specifications make it clear that this procedure has to have happened prior to the Heart Failure encounter:
      such that ( Global."NormalizeInterval" ( ImplantedCardiacPacer.relevantDatetime, ImplantedCardiacPacer.relevantPeriod ) ) starts before
      end of ModerateOrSevereLVSDHFOutpatientEncounter.relevantPeriod

      The logic seems to be inconsistent, as the latter suggests that once a cardiac pacemaker has been implanted, they will never be able to meet this exception, while the former suggests that if the diagnosis is made inactive/historical by the time the encounter occurs, then they would be able to qualify.

      If a patient had a pacemaker, and that pacemaker was removed prior to the heart failure encounter, then would they qualify for this exception since they did not currently have the pacemaker diagnosis, or would they not qualify since they had a history of having the procedure? 

            edave Mathematica EC eCQM Team
            areed Angela Reed (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: