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

CMS69 - Numerator Reason Requirement

XMLWordPrintable

    • Icon: EC eCQMs EC eCQMs
    • Resolution: Answered
    • Icon: Moderate Moderate
    • None
    • None
    • Hide
      Thank you for your inquiry about CMS69v9 "Preventive Care and Screening: Screening for Body Mass Index (BMI) and Follow Up Plan." The required reason codes for follow up plans associated with an above or below normal BMI assessment can be found in the terminology section of the logic:

      code "Underweight (finding)" ("SNOMEDCT Code (248342006)"
      valueset "Overweight or Obese" (2.16.840.1.113762.1.4.1047.502)
      The BMI value is the criteria evaluated to determine a reason for a follow up plan. Therefore, the answer to your second question is yes; the reason code is required to link the follow up provided to the documented BMI assessment. A reason is required for the follow up plans other than medication because some interventions such as referral to nutritional counseling could be recommended for either an above or below normal BMI. For medications a reason is not required because the medications are inherently for either an above normal or below normal BMI.
      Show
      Thank you for your inquiry about CMS69v9 "Preventive Care and Screening: Screening for Body Mass Index (BMI) and Follow Up Plan." The required reason codes for follow up plans associated with an above or below normal BMI assessment can be found in the terminology section of the logic: code "Underweight (finding)" ("SNOMEDCT Code (248342006)" valueset "Overweight or Obese" (2.16.840.1.113762.1.4.1047.502) The BMI value is the criteria evaluated to determine a reason for a follow up plan. Therefore, the answer to your second question is yes; the reason code is required to link the follow up provided to the documented BMI assessment. A reason is required for the follow up plans other than medication because some interventions such as referral to nutritional counseling could be recommended for either an above or below normal BMI. For medications a reason is not required because the medications are inherently for either an above normal or below normal BMI.
    • CMS0069v10
    • CMS69v9/NQFna

      As part of the 2021 changes to CMS69, there is a requirement added for Above/Below Normal BMI interventions to have a reason code:

      • "Most Recent Documented BMI" MostRecentBMI
        with ["Intervention, Performed": "Follow Up for Above Normal BMI"] AboveNormalFollowUp
        such that MostRecentBMI.relevantDatetime 12 months or less on or before day of start of AboveNormalFollowUp.relevantPeriod
        and AboveNormalFollowUp.reason in "Overweight or Obese" where MostRecentBMI.result >= 25 'kg/m2'

       

      • "Most Recent Documented BMI" MostRecentBMI
        with ["Intervention, Performed": "Follow Up for Below Normal BMI"] BelowNormalFollowUp
        such that MostRecentBMI.relevantDatetime 12 months or less on or before day of start of BelowNormalFollowUp.relevantPeriod
        and BelowNormalFollowUp.reason ~ "Underweight (finding)" where MostRecentBMI.result < 18.5 'kg/m2'

       

      Clinically speaking, the BMI value itself may serve as a "reason" for the follow up without an diagnosis code being documented, which is the reason for the following 2 questions:

      1. Given that a patient may not have any diagnosis of "overweight" or "underweight" in a given visit, is the BMI value sufficient to provide numerator credit if a patient has an above or below normal vitals value for BMI and Intervention is provided?

      OR

      2. Is it required that code is documented by the provider seeing the patient that the followup provided was explicitly for "Overweight or Obese" or "Underweight (finding)"

       

      And 3. If reason is required, why is it not required for medication orders?

            edave Mathematica EC eCQM Team
            crintoul Cory Rintoul
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              Solution Posted On: