reportingRate field for 2019 submission

44 views
Skip to first unread message

Satyendra Pandey

unread,
Jul 25, 2019, 5:17:34 AM7/25/19
to Developer Group for QPP APIs
Hello,
I came across information to remove the 'reportingRate' field from measure-set value. This is supposed to be a change for 2019 submission compare to 2018.

Can some one please share more insight on what kind of measure this field was applicable in 2018?
Also, was it a mandatory or optional field in 2018? ( the public/validate-submission ) fails for 2018 if the field is not added in "some" quality measures for MIPS.

Also, what would the response if this field is sent in 2019? Is it optional to remove or mandatory?

Thanks
Satyendra

Satyendra Pandey

unread,
Aug 1, 2019, 2:58:59 AM8/1/19
to Developer Group for QPP APIs
Sarah, others can you please help with the information?

SRIDHAR G

unread,
Aug 1, 2019, 10:37:18 AM8/1/19
to Developer Group for QPP APIs
Hi Satyendra,


'reportingRate' field was not a mandatory in 2018, so validate submission should not fail because of this. 

 Even in 2019 I am expecting this to work the same way, 

 'reportingRate' in API response in dependent on "submissionMethod", "measureId", "isEndToEndReported", "performanceMet","performanceNotMet","eligiblePopulation","eligiblePopulationException","eligiblePopulationExclusion","stratum" but not 'reportingRate' in request.


@Sarah Please correct me If am wrong.

Sridhar Galipalli

 

Population Health Analytics

 

eClinicalWorks

Reply all
Reply to author
Forward
0 new messages