Uploaded image for project: 'MADiE Issue Tracker'
  1. MADiE Issue Tracker
  2. MADIE-518

Varying Bonnie Coverage after measure package updates

    • Icon: Bug/Issue Bug/Issue
    • Resolution: Answered
    • Icon: Critical Critical
    • Measure View
    • DIABETIC RETINOPATHY: COMMUNICATION WITH THE PHYSICIAN MANAGING ONGOING DIABETES CARE
    • CMS142
    • 16
    • Affecting AU Process.

      I am noticing some issues with Bonnie today. After updating CMS142 with the most current package, I am seeing 16 test cases fail at 28% coverage. Upon logging out, and reloading the package, I was able to get it back to 100% coverage. I decided to retest and performed a reload of the same package, but now Bonnie is saying 28% coverage and 16 test cases failing once again for CMS142.

       

          [MADIE-518] Varying Bonnie Coverage after measure package updates

          James Bradley (Inactive) added a comment - - edited

          Hi Eduardo,

          Yes, the VSAC API issue was resolved yesterday afternoon. We are unable to replicate the issue you were experiencing. If you continue to experience this issue please let us know, but I believe it has been resolved with the VSAC API connectivity issue being resolved. As for the Value Set Version drop down question, it depends on your use case. In Bonnie during measure upload we provide the following information (in the help icons): 

          "Select an expansion profile from the dropdown to query VSAC for value sets contained in the measure. An expansion profile is a set of instructions for calculating value set content based on specific code system versions and retired legacy codes. For more information on expansion profiles, visit the NLM VSAC website. The default selected profile is ‘Latest eCQM’. ‘Latest eCQM’ represents either an upcoming profile or the latest published profile, which is identified in the angle brackets following ‘Latest eCQM’ in the drop down. If the 'Draft' option is checked and the VSAC user has authoring permissions, value sets in draft will be fetched and calculated using the given profile."

          "Select a program release from the dropdowns to query VSAC for value sets contained in the measure. A program release is a group of value set expansions (code lists) that are published under one program release label. For more information on program releases, visit the NLM VSAC website. The default selected program is 'CMS eCQM' and the default selected release is the latest release from the selected program. " 

          I hope this helps.

          Thanks,

          -James

           

          James Bradley (Inactive) added a comment - - edited Hi Eduardo, Yes, the VSAC API issue was resolved yesterday afternoon. We are unable to replicate the issue you were experiencing. If you continue to experience this issue please let us know, but I believe it has been resolved with the VSAC API connectivity issue being resolved. As for the Value Set Version drop down question, it depends on your use case. In Bonnie during measure upload we provide the following information (in the help icons):  "Select an expansion profile from the dropdown to query VSAC for value sets contained in the measure. An expansion profile is a set of instructions for calculating value set content based on specific code system versions and retired legacy codes. For more information on expansion profiles, visit the NLM VSAC website. The default selected profile is ‘Latest eCQM’. ‘Latest eCQM’ represents either an upcoming profile or the latest published profile, which is identified in the angle brackets following ‘Latest eCQM’ in the drop down. If the 'Draft' option is checked and the VSAC user has authoring permissions, value sets in draft will be fetched and calculated using the given profile." "Select a program release from the dropdowns to query VSAC for value sets contained in the measure. A program release is a group of value set expansions (code lists) that are published under one program release label. For more information on program releases, visit the NLM VSAC website. The default selected program is 'CMS eCQM' and the default selected release is the latest release from the selected program. "  I hope this helps. Thanks, -James  

          Hi James:

          Is there a reason why they passed will 100% Coverage and 100% Pass at some point in time yesterday? Has the VSAC API issues been resolved? Also, do you have recommendations on the defaults to use for the Value Set Version drop down selection?

          -Eduardo

          Debra Harper (Inactive) added a comment - Hi James: Is there a reason why they passed will 100% Coverage and 100% Pass at some point in time yesterday? Has the VSAC API issues been resolved? Also, do you have recommendations on the defaults to use for the Value Set Version drop down selection? -Eduardo

          Hi Eduardo, 

          While investigating your issue we went into the patient builder view of your failing test cases. Each failing test case has a warning banner at the top saying: "Warning: There are elements in the Patient History that do not use any codes from this measure's value sets…" this indicates that the data elements (listed in the warning), are using codes that are no longer contained in the value sets that are associated with the Measure.

          In order to fix this, you can do one of the following things:

          • Delete the existing code on the data element listed in the warning banner (by clicking the ‘X’ next to each code listed on the data element) which will cause Bonnie to auto populate the data element with codes that exist in the value set.
          • Select new codes from the drop down for each data element listed in the warning banner.
          • Modify the codes contained in the value sets and re-upload the measure.

           

          James Bradley (Inactive) added a comment - Hi Eduardo,  While investigating your issue we went into the patient builder view of your failing test cases. Each failing test case has a warning banner at the top saying: "Warning: There are elements in the Patient History that do not use any codes from this measure's value sets…" this indicates that the data elements (listed in the warning), are using codes that are no longer contained in the value sets that are associated with the Measure. In order to fix this, you can do one of the following things: Delete the existing code on the data element listed in the warning banner (by clicking the ‘X’ next to each code listed on the data element) which will cause Bonnie to auto populate the data element with codes that exist in the value set. Select new codes from the drop down for each data element listed in the warning banner. Modify the codes contained in the value sets and re-upload the measure.  

          See most recent measure package attached. 

          Debra Harper (Inactive) added a comment - See most recent measure package attached. 

          Hi Eduardo,

          Thank you for reporting this issue, we will investigate and get back to you as soon as possible. Can you please attach a copy of the relevant measure to this ticket? 

          Thanks,

          -James

          James Bradley (Inactive) added a comment - Hi Eduardo, Thank you for reporting this issue, we will investigate and get back to you as soon as possible. Can you please attach a copy of the relevant measure to this ticket?  Thanks, -James

          MADiE Team added a comment -

          Thank you for submitting your question/issue. We will assign this to a team member and respond in one business day. If your question/issue is related to a particular measure, please upload the corresponding measure package.

          MADiE Team added a comment - Thank you for submitting your question/issue. We will assign this to a team member and respond in one business day. If your question/issue is related to a particular measure, please upload the corresponding measure package.

            Unassigned Unassigned
            esegovia712 Debra Harper (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: