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

CMS69V10.1 denominator exception question related to lookback period

XMLWordPrintable

    • Icon: EC eCQMs - Eligible Clinicians EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • Hide
      ​​Thank you for your inquiry regarding CMS69v10: Preventive Care and Screening: Body Mass Index (BMI) Screening and Follow-Up Plan. There is no lookback period for the denominator exceptions. Per the measure specifications, the medical reason for not documenting BMI or for not documenting a follow-up plan for a BMI outside normal parameters must be documented on the date of the qualifying encounter.

      Medical Reason for Not Documenting a Follow up Plan for Low or High BMI
       
      ( ["Intervention, Not Ordered": "Referrals Where Weight Assessment May Occur"]
        union ["Intervention, Not Ordered": "Follow Up for Above Normal BMI"]
        union ["Intervention, Not Performed": "Follow Up for Above Normal BMI"]
        union ["Intervention, Not Ordered": "Follow Up for Below Normal BMI"]
        union ["Intervention, Not Performed": "Follow Up for Below Normal BMI"]
        union ["Medication, Not Ordered": "Medications for Above Normal BMI"]
        union ["Medication, Not Ordered": "Medications for Below Normal BMI"] ) NoBMIFollowUp
        with "Qualifying Encounter during Measurement Period" QualifyingEncounter
          such that NoBMIFollowUp.authorDatetime same day as start of QualifyingEncounter.relevantPeriod
        where NoBMIFollowUp.negationRationale in "Medical Reason"
      Medical Reason or Patient Reason for Not Performing BMI Exam
       
      ["Physical Exam, Not Performed": "Body mass index (BMI) [Ratio]"] NoBMI
        with "Qualifying Encounter during Measurement Period" QualifyingEncounter
          such that Global."NormalizeInterval" ( NoBMI.authorDatetime, NoBMI.relevantPeriod ) ends same day as start of QualifyingEncounter.relevantPeriod
        where ( NoBMI.negationRationale in "Medical Reason"
            or NoBMI.negationRationale in "Patient Declined"
        )
      Show
      ​​Thank you for your inquiry regarding CMS69v10: Preventive Care and Screening: Body Mass Index (BMI) Screening and Follow-Up Plan. There is no lookback period for the denominator exceptions. Per the measure specifications, the medical reason for not documenting BMI or for not documenting a follow-up plan for a BMI outside normal parameters must be documented on the date of the qualifying encounter. Medical Reason for Not Documenting a Follow up Plan for Low or High BMI   ( ["Intervention, Not Ordered": "Referrals Where Weight Assessment May Occur"]   union ["Intervention, Not Ordered": "Follow Up for Above Normal BMI"]   union ["Intervention, Not Performed": "Follow Up for Above Normal BMI"]   union ["Intervention, Not Ordered": "Follow Up for Below Normal BMI"]   union ["Intervention, Not Performed": "Follow Up for Below Normal BMI"]   union ["Medication, Not Ordered": "Medications for Above Normal BMI"]   union ["Medication, Not Ordered": "Medications for Below Normal BMI"] ) NoBMIFollowUp   with "Qualifying Encounter during Measurement Period" QualifyingEncounter     such that NoBMIFollowUp.authorDatetime same day as start of QualifyingEncounter.relevantPeriod   where NoBMIFollowUp.negationRationale in "Medical Reason" Medical Reason or Patient Reason for Not Performing BMI Exam   ["Physical Exam, Not Performed": "Body mass index (BMI) [Ratio]"] NoBMI   with "Qualifying Encounter during Measurement Period" QualifyingEncounter     such that Global."NormalizeInterval" ( NoBMI.authorDatetime, NoBMI.relevantPeriod ) ends same day as start of QualifyingEncounter.relevantPeriod   where ( NoBMI.negationRationale in "Medical Reason"       or NoBMI.negationRationale in "Patient Declined"   )
    • CMS0069v10
    • Large impact on our reports for this measure with incorrect outcomes related to our vendor using a lookback period of 12 months from denominator qualifying encounter.

      We have a question on the specification(spec) CMS69V10.1: Preventive Care and Screening: Body Mass Index (BMI) Screening and Follow-Up Plan. The question is related to the lookback period for the Denominator Exception medical reason and patient reason, Spec states: "Patients with a Documented Medical Reason for Not documenting BMI or for not documenting a follow-up plan for a BMI outside normal parameters (e.g., elderly patients 65 years of age or older) for whom weight reduction/weight gain would complicate other underlying health conditions such as illness or physical disability, mental illness, dementia, confusion, or nutritional deficiency such as vitamin/mineral deficiency; patients in an urgent or emergent medical situation where time is of the essence and to delay treatment would jeopardize the patient's health status) - Patient Reason: Patients who refuse measurement of height and/or weight. (Denominator Exception)"   We need clarification of the lookback period for medical reason and patient reason for Denominator Exceptions. In the spec we see " 
      "Qualifying Encounter during Measurement Period" QualifyingEncounter
      such that NoBMIFollowUp.authorDatetime same day as start of QualifyingEncounter.relevantPeriod
      where NoBMIFollowUp.negationRationale in "Medical Reason"
      ( NoBMI.authorDatetime, NoBMI.relevantPeriod ) ends same day as start of QualifyingEncounter.relevantPeriod
      where ( NoBMI.negationRationale in "Medical Reason"
      or NoBMI.negationRationale in "Patient Declined"
      Our vendor had read it as timeline of " at the qualifying encounter or 12 months prior to the qualifying encounter." We are seeking a clarification of - is there a Denominator exception lookback period? We are reading the specifications for this measure with no lookback period, needs to be on Qualifying encounter date for the Denominator exceptions.  Thank you

            edave Mathematica EC eCQM Team
            Tallred Tara Allred (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: