Issue in CMS benchmark sheet Vs CMS Github

[Satyajeet Aparadh]

Hello Team,

We have observed a discrepancy for a few measures in the CMS benchmark sheet and the CMS Github.

Measures for which we have observed a discrepancy are:  Measure 19 and Measure 131

As per the CMS benchmark sheet Measure 19 and Measure 131 do not have a 7 point cap. 

As per CMS Github available at https://raw.githubusercontent.com/CMSgov/qpp-measures-data/master/measures/2019/measures-data.json;  Measure 19 and Measure 131 are topped out. 

If we report both these measures with submission method as registry - we observed that max points can be achieved i.e. 10. However, we have also observed that in the response we are receiving a flag as true for topped out. 

If a measure is topped out, it should be capped at max 7 possible points. 

See the response below where the topped out flag is received as true.:

                      },

                      "noBenchmarks": false,

                      "benchmarkType": "registry",

                      "eMeasureId": "CMS142v7",

                      "toppedOut": true,

                      "isGhost": false,

                      "submissionMethod": "registry",

                      "performanceStart": "2019-01-01",

                      "performanceEnd": "2019-12-31",

                      "isCpcPlus": false,

                      "unroundedScoreValue": 10

My assumption is that there are more measures that are affected by this.

Could you please confirm the issue and also let us know by when can we expect a fix. The topped out flag should ideally be set at the Collection type level and not for the entire measure ID since there are chances that for an equivalent measure (measure with MIPS CQM and eCQM collection type), one collection type is topped out and the other is not. 

Thanks,

Satyajeet Aparadh

--

[Michelle Ingle]

Satyajeet, 

Thanks for the question.

isToppedOutByProgram varies by submissionMethod thus the value for isToppedOutByProgram for each submissionMethod is stored in the Benchmarks file.  For both of these measures the scoring is accurate, as both are topped out only for the Claims submission method but NOT for Registries.

I am working with the team to deprecate the isToppedOutByProgram at the Measure level as it is misleading.  If true it only means that at least one of the benchmarks for each of the submissions methods is topped out, which is confusing.

Thanks!

Michelle