2018 Sandbox Benchmark Scoring Seems Incorrect

88 views
Skip to first unread message

Randal Roe (Alpha II Registry)

unread,
Jan 25, 2019, 3:20:08 PM1/25/19
to Developer Group for QPP APIs
The attached text file is the response we received after a recent sandbox submission.

Quality measure 69 (Registry/QCDR submission), which starts at line 113 of the attached text file, has a performance rate of 83.33%. From the sandbox it received a decile score (achievement score) of 10 points:

                    "metadata": {
                      "performanceRate": 83.33,
                      "reportingRate": 97.67,
                      "measurementSetId": "03d0cbf4-27d4-43db-8f57-65f6f734db5f",
                      "measurementId": "03d0cbf4-4d59-44e1-a861-e699d52f2e80",
                      "measureClass": "Class 1",
                      "measureTitle": "Hematology: Multiple Myeloma: Treatment with Bisphosphonates",
                      "highPriorityBonusEligible": false,
                      "endToEndBonusEligible": false,
                      "endToEndBonus": 0,
                      "outcomeOrPatientExperienceBonus": 0,
                      "highPriorityBonus": 0,
                      "decileScore": 10,
                      "performanceDenominator": 84,
                      "performanceNumerator": 70,
                      "eligiblePopulation": 86,
                      "partialDecileScore": 0,
                      "partialPoints": 0,
                      "decile": -1,
                      "deciles": [
                        0,
                        100,
                        100,
                        100,
                        100,
                        100,
                        100,
                        100,
                        100

Looking at the benchmark file (also attached), we thought that a performance rate of 83.33% should result in a score of just the floor of 3 points, since all the deciles from 3 to 9 are empty. However, the sandbox returned a score of 10 points and assigned this measure to decile -1.

Our questions:
  • For measure 69, wouldn't it require a performance rate of 100% to get a score of 10 points?
  • Wouldn't anything less than 100% for the performance rate result in a score of 3 points (the "floor score")?
  • What does "decile": -1 mean?
  • In the "deciles" section, does each entry represent the left-side limit (the lower value for a non-inverse measures) of deciles 2-10?
Measure 110 seems to bear this out:
                      "deciles": [
                        0,
                        26.89,
                        40.49,
                        50,
                        57.07,
                        64.79,
                        73.08,
                        82.71,
                        96.44
                      ],

Thank you.

Randal Roe
Alpha II Registry
000106106_0125533694_ecdebced-abed-421e-a2f6-e123d667db8b_Score.txt
2018 MIPS Quality Benchmarks_01032019.xlsx

Randal Roe (Alpha II Registry)

unread,
Jan 31, 2019, 12:59:30 PM1/31/19
to Developer Group for QPP APIs
Just wondering if anyone has had a chance to review this?

Thanks.

Randal Roe
Alpha II Registry.

Sarah White

unread,
Jan 31, 2019, 1:37:56 PM1/31/19
to Randal Roe (Alpha II Registry), Developer Group for QPP APIs
Hi Randal,

We're looking into it. I'll let you know when I have more information to share shortly.

Sarah White
Business Analyst


--
You received this message because you are subscribed to the Google Groups "Developer Group for QPP APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/qpp-apis.
To view this discussion on the web visit https://groups.google.com/d/msgid/qpp-apis/e142ca63-04b5-4b97-93fa-7a00453c664f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages