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

CMS69v11, CMS22v11, CMS143v11 - Telehealth guidance clarification

XMLWordPrintable

    • Icon: EC eCQMs - Eligible Clinicians EC eCQMs - Eligible Clinicians
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • Sharanya
    • Hide

      Thank you for your inquiry regarding CMS69v11: Preventive Care and Screening: Body Mass Index (BMI) Screening and Follow-Up Plan. Per the measure guidance, an eligible professional or their staff is required to measure both height and weight and self-reported values cannot be used for the BMI used to satisfy numerator criteria.



      In the first scenario you provide, if the BMI documented during the telehealth encounter on January 10 is self-reported by the patient, then it does not satisfy numerator criteria per the guidance. In the second scenario you provide, the patient will meet the numerator criteria if they have a qualifying in-person encounter, a documented BMI using a height and weight measured by an eligible professional or their staff, and a qualifying follow-up plan during the measurement period.
      Show
      ​ Thank you for your inquiry regarding CMS69v11: Preventive Care and Screening: Body Mass Index (BMI) Screening and Follow-Up Plan. Per the measure guidance, an eligible professional or their staff is required to measure both height and weight and self-reported values cannot be used for the BMI used to satisfy numerator criteria. In the first scenario you provide, if the BMI documented during the telehealth encounter on January 10 is self-reported by the patient, then it does not satisfy numerator criteria per the guidance. In the second scenario you provide, the patient will meet the numerator criteria if they have a qualifying in-person encounter, a documented BMI using a height and weight measured by an eligible professional or their staff, and a qualifying follow-up plan during the measurement period.
    • CMS0022v11, CMS0069v11, CMS0143v11
    • CMS0022v10, CMS0069v10
    • High. Telehealth exclusion is important to accurately evaluate the patients for measure eligibility/satisfaction

      This is regarding the Telehealth exclusion for the 3 eCQMs wherein according to the guidance section, it states Clinical actions cannot be done via telehealth and hence not eligible.

       

      In CMS69v11 (https://ecqi.healthit.gov/sites/default/files/ecqm/measures/CMS69v11.html), only the Denominator definition states telehealth encounters are ineligible as identified by a new "virtual" class parameter. The CMS69v11 numerator states BMI and the follow-up can be placed anytime during the measurement period.

      However, for the Numerator part, ie., BMI recorded or follow-up placed, there is no relation to the telehealth encounter.

       

      Say for example -

       

      1. if a patient has a 1st encounter marked by a telehealth class (modifier), dated Jan 10th, then it is not eligible for the measure on the first instance.

      For the same patient, another valid encounter dated July 1st is faced without any telehealth class, then this particular encounter will be eligible and measure qualifies.

       

      If a BMI of normal value is recorded on the date of telehealth ir., Jan 10th, will this BMI be counted for the numerator evaluation and satisfy the measure?

       

      1. If a patient has a 1st encounter billed normally with a valid encounter code - dated Jan 20th and BMI is recorded on Jan 22nd. Say, another encounter is scheduled as a telehealth dated Jan 30th and a follow-up order is placed on the same day 30th Jan, will this be still counted for the numerator as pass?

       

      As the CMS69v11 CQL definition has no clear indication of any conjunction of telehealth and BMI or follow-up intervention.

      Kindly clarify.

       

            edave Mathematica EC eCQM Team
            P Sharanya (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: