Skip to first unread message
aho...@athenahealth.com
Oct 24, 2017, 1:43:49 PM10/24/17
to Developer Group for QPP APIs
Hello QPP,
I wanted to validate the approach we intend to take with calculating scores for our providers - we intend to use the score-preview API functionality to provide score information, with clear indications that the scores displayed are provisional only and not final scores. Our providers have the option of submitting via Registry or EHR, and so we will include both 'measurementSets' in the submission to score-preview, with the expectation that the scoring engine will chose the optimal measurementSet and measurements. Our primary goal is to help our providers determine which submission mechanism to use, and to give them a general idea of how they're doing.
First, can you confirm that the Score Engine will indeed select the optimal submission mechanism?
Second, how does score-preview indicate which submission method was selected? I see in the 'detail' field the string 'Picked the highest scoring measurement set electronicHealthRecord' - but that's not a structured response. Can we be confident that the 'detail' text will always be in that format so that we can safely parse it? Or could you return the selected submission method in a structured way?
We need this information because submitting via Registry requires an additional sign-off step on the part of our clients, and we need to make know whether to ask them to go through that process. Thank you.
Aaron Homer
Mari Miyachi
Oct 25, 2017, 12:33:03 PM10/25/17
to Developer Group for QPP APIs
Hi Aaron,
Yes, the scoring engine will select the optimal measurement set.
There should be a field that indicates the submission method in the part with titles like "Advancing Care Information Score", in the "detail" field. We plan to add more documentation around the score response to help answer questions like this!
Aaron Homer
Oct 27, 2017, 3:17:56 PM10/27/17
to Developer Group for QPP APIs
Hi Mari,
Here is an example 'score-preview' response, generated from the Swagger environment, in response to a submission that included both an 'electronicHealthRecord' measurementSet and a 'registry' measurementSet. Notice how the top level detail has a text message, which we would have to parse, and which seems fragile if the copy is ever updated. There are lower level details for both registry and electronicHealthRecord with more plainly structured, but don't make clear which submissionMethod was selected overall.
{
"name": "quality",
"title": "QUALITY component of final score",
"detail": "Scoring based on weight of 60%.",
"value": 8,
"original": {
"name": "quality",
"value": 13.3,
"detail": "Picked the highest scoring measurement set electronicHealthRecord",
"parts": [
{
"name": "quality",
"value": 13.3,
"detail": "electronicHealthRecord",
"parts": [
{
"name": "391",
"value": 4,
"detail": "Contributing 4",
"metadata": {
"performanceRate": 66.66666666666666,
"reportingRate": 66.66666666666666,
"measureClass": "Class 2",
"measureTitle": "Follow-Up After Hospitalization for Mental Illness (FUH)",
"endToEndBonus": 1,
"outcomeOrPatientExperienceBonus": 0,
"highPriorityBonus": 0,
"decileScore": 3,
"performanceDenominator": 3,
"performanceNumerator": 2,
"eligiblePopulation": 6,
"partialDecileScore": null,
"partialPoints": 0,
"decile": -1,
"deciles": null,
"processingStatus": "PICKED",
"totalMeasurementPoints": 4,
"totalBonusPoints": 1,
"messages": {
"measurementClass": "Measurement has no benchmarks",
"e2eBonusScore": "Bonus from EHR submission",
"measurementPicker": "Picked at 1",
"totalMeasurementPoints": "Measurement points for PICKED measure include decile score with all bonus points"
},
"noBenchmarks": true,
"benchmarkType": "electronicHealthRecord",
"eMeasureId": null
}
},
{
"name": "093",
"value": 4,
"detail": "Contributing 4",
"metadata": {
"performanceRate": 50,
"reportingRate": 80,
"measureClass": "Class 2",
"measureTitle": "Acute Otitis Externa (AOE): Systemic Antimicrobial Therapy - Avoidance of Inappropriate Use",
"endToEndBonus": 1,
"outcomeOrPatientExperienceBonus": 0,
"highPriorityBonus": 0,
"decileScore": 3,
"performanceDenominator": 0,
"performanceNumerator": 0,
"eligiblePopulation": 0,
"partialDecileScore": null,
"partialPoints": 0,
"decile": -1,
"deciles": null,
"processingStatus": "PICKED",
"totalMeasurementPoints": 4,
"totalBonusPoints": 1,
"messages": {
"measurementClass": "Measurement has no benchmarks",
"e2eBonusScore": "Bonus from EHR submission",
"measurementPicker": "Picked at 2",
"totalMeasurementPoints": "Measurement points for PICKED measure include decile score with all bonus points"
},
"noBenchmarks": true,
"benchmarkType": "electronicHealthRecord",
"eMeasureId": null
}
}
],
"metadata": {
"messages": {
"denominator": "At least 1 high or outcome or patient experience measure available. So denominator is 60",
"totalMeasurementPoints": "Sum of applicable individual measurement points.",
"totalBonusPoints": "Sum of individual measurement bonus points"
},
"measuresPicked": [
"391",
"093"
],
"totalMeasurementPoints": 8,
"totalBonusPoints": 2,
"denominator": 60,
"e2eBonusScore": 2,
"reweightedScore": 8
}
},
{
"name": "quality",
"value": 5,
"detail": "registry",
"parts": [
{
"name": "093",
"value": 3,
"detail": "Contributing 3",
"metadata": {
"performanceRate": 50,
"reportingRate": 80,
"measureClass": "Class 2",
"measureTitle": "Acute Otitis Externa (AOE): Systemic Antimicrobial Therapy - Avoidance of Inappropriate Use",
"endToEndBonus": 0,
"outcomeOrPatientExperienceBonus": 0,
"highPriorityBonus": 0,
"decileScore": 3,
"performanceDenominator": 0,
"performanceNumerator": 0,
"eligiblePopulation": 0,
"partialDecileScore": null,
"partialPoints": 0,
"decile": -1,
"deciles": null,
"processingStatus": "PICKED",
"totalMeasurementPoints": 3,
"totalBonusPoints": 0,
"messages": {
"measurementClass": "Eligible population is greater than 20, has benchmarks and reporting rate is less than 50%",
"measurementPicker": "Picked at 1",
"totalMeasurementPoints": "Measurement points for PICKED measure include decile score with all bonus points"
},
"noBenchmarks": false,
"benchmarkType": "registry",
"eMeasureId": null
}
}
],
"metadata": {
"messages": {
"denominator": "At least 1 high or outcome or patient experience measure available. So denominator is 60",
"totalMeasurementPoints": "Sum of applicable individual measurement points.",
"totalBonusPoints": "Sum of individual measurement bonus points"
},
"measuresPicked": [
"093"
],
"totalMeasurementPoints": 3,
"totalBonusPoints": 0,
"denominator": 60,
"e2eBonusScore": 0,
"reweightedScore": 3
}
}
]
},
"metadata": {
"maxContribution": 60
}
}
Mari Miyachi
Oct 30, 2017, 8:46:27 AM10/30/17
to Developer Group for QPP APIs
Hi Aaron,
I see. Thanks for the feedback - I will pass this along to the team who designs the score schema!
Reply all
Reply to author
Forward
0 new messages