Changes to Submitting Non-proportion Measures in Year 2

182 views
Skip to first unread message

Developer Group for QPP APIs

unread,
Nov 29, 2018, 9:43:26 AM11/29/18
to Developer Group for QPP APIs

CMS is making changes to the non-proportion metric type for Year 2 submissions. Non-proportion measurements are applicable to quality measures. They are exclusively authored by QCDRs and are used to attest to measures that are otherwise categorized as 'ratio', 'continuous variable', or a combination of 'proportion' and the former.

 

The Year 1 non-proportion metric schema in the Submissions API did not support non-proportion measure benchmarking. Therefore, these measures could only receive a score of 3. This change to the non-proportion metric type enables scoring of non-proportion measures using performance year benchmarks. This will increase the amount of points available to be earned for non-proportion measures.

 

This update also allows for successful submission of quality measures: Average Change in Back Pain following Lumbar Discectomy / Laminotomy (measure ID 459), Average Change in Back Pain following Lumbar Fusion (measure ID 460), and Average Change in Leg Pain following Lumbar Discectomy and/or Laminotomy (measure ID 461). 

 

In Year 1, the "nonProportion" measure schema for the Submissions API looked like:

{

  "id": string,

  "measurementSetId": string,

  "measureId": string,

  "value": {

    "numerator": float,

    "denominator": float,

    "isEndToEndReported": boolean,

    "denominatorException": float,

    "numeratorExclusion": float

  }

}

 

In Year 2, we are adding one field to capture data completeness. Adding data completeness to the captured information about the measure will enable scoring non-proportion measures against a benchmark. In the Submissions API, this is referred to as "reportingRate":

{

  "id": string,

  "measurementSetId": string,

  "measureId": string,

  "value": {

    "numerator": float,

    "denominator": float,

    "isEndToEndReported": boolean,

    "denominatorException": float,

    "numeratorExclusion": float,

    "reportingRate": float

    }

}

 

Please see the attached document for more information about the update to the non-proportion metric type, including reporting examples. 

 

If you have any questions about this change, please contact the Quality Payment Program at Q...@cms.hhs.gov or 1-866-288-8292 (TTY: 1-877-715-6222).

Non-Proportional Format and Examples.pdf

abhijeet mahajan

unread,
Nov 29, 2018, 11:37:33 AM11/29/18
to Developer Group for QPP APIs
Hello QPP team,

Could you please confirm if this 'reportingRate' field is going to be a mandatory field and it will be supported in both, XML and JSON requests ?

Thanks,
Abhijeet

Sarah White

unread,
Nov 29, 2018, 1:37:22 PM11/29/18
to abhijeet mahajan, qpp-...@googlegroups.com
Hi Abhijeet,

Yes, it's a required writeable field and is supported in QPP JSON and QPP XML.

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/9c2e8f90-7ba2-4db5-aaba-968b235c6f3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages