Put Endpoint for Measurement Sets and Scoring Issue in Preview Environment

[Robert Simons]

Hello,

I have noticed the following issue in the preview environment when updating a measurement set and then viewing the associated scoring information:

1. Check score for existing submission and notice the two IA measures returned (IA_CC_8 and IA_PSPA_19)

            

Request: curl -X GET "https://preview.qpp.cms.gov/api/submissions/submissions/03706829-9249-4584-9841-a3c6033be8be/score" -H "accept: application/json" -H "Authorization: Bearer REMOVED"

Response:

2. 

2. Update measurement set with only 1 IA measure (IA_CC_8):

Request: curl -X PUT "https://preview.qpp.cms.gov/api/submissions/measurement-sets/03706ad5-4639-4913-a061-a36a48921d60" -H "accept: application/json" -H "Authorization: Bearer REMOVED" -H "Content-Type: application/json" -d "{\"submissionId\":\"03706829-9249-4584-9841-a3c6033be8be\",\"measurementSetId\":\"03706ad5-4639-4913-a061-a36a48921d60\",\"measurements\":[{\"measureId\":\"IA_CC_8\",\"value\":true}],\"category\":\"ia\",\"submissionMethod\":\"registry\",\"performanceStart\":\"2018-01-01\",\"performanceEnd\":\"2018-12-31\",\"programName\":null,\"practiceId\":null}"

Response:

3. Check score again to see updates reflected in score but the submissions has not been modified and score is the same as before. The two IA measures are still appearing:

Request: curl -X GET "https://preview.qpp.cms.gov/api/submissions/submissions/03706829-9249-4584-9841-a3c6033be8be/score" -H "accept: application/json" -H "Authorization: Bearer REMOVED"

Response: 

Please investigate and let me know why the measurement set is not being updated and the score is not reflecting the changes.

Thanks,

Robert

[sa...@navapbc.com]

Hi Robert,

This issue is now resolved. Thank you for surfacing it. Certain API requests were being cached due to a configuration issue in the Developer Preview environment causing stale data to be returned for those particular requests. The cached responses contained potentially outdated information which made it appear that related GET/PUT endpoints were not functioning correctly, but in reality the cached requests never made it to the API and so the cached responses didn't reflect the actual data stored in the API. 

Sarah