Issue on "https://qpp-submissions-sandbox.navapbc.com/submissions/score-preview" endpoint
139 views
Skip to first unread message
anuj Kumar dwivedi
Nov 21, 2017, 8:01:35 AM11/21/17
to Developer Group for QPP APIs
Hi ,
I was doing my testing and found some of multiPerformanceRate Measures (for example 046,394,392,391,122) not allow single strata value as given below example, it is needed of all strata which is related to measure.
Could you please help me and explain how can i know which multiPerformanceRate Measures is accepting single strata value or all ?
following code generating error :
{
"programName":"mips",
"entityType":"individual",
"taxpayerIdentificationNumber":"000456789",
"nationalProviderIdentifier":"0876543210",
"performanceYear":2017,
"measurementSets":[
{
"category":"quality",
"submissionMethod":"registry",
"performanceStart":"2017-01-01",
"performanceEnd":"2017-12-01",
"measurements":[
{
"measureId":"394",
"value":{
"isEndToEndReported":false,
"strata":[
{
"performanceMet":45,
"eligiblePopulation":55,
"stratum":"meningococcal"
}
]
}
}
]
}
]
}
following code is working fine:
{
"programName":"mips",
"entityType":"individual",
"taxpayerIdentificationNumber":"000456789",
"nationalProviderIdentifier":"0876543210",
"performanceYear":2017,
"measurementSets":[
{
"category":"quality",
"submissionMethod":"registry",
"performanceStart":"2017-01-01",
"performanceEnd":"2017-12-01",
"measurements":[
{
"measureId":"394",
"value":{
"isEndToEndReported":false,
"strata":[
{
"performanceMet":45,
"eligiblePopulation":55,
"stratum":"meningococcal"
},
{
"performanceMet":45,
"eligiblePopulation":130,
"stratum":"Tdap"
},
{
"performanceMet":45,
"eligiblePopulation":555,
"stratum":"HPV"
},
{
"performanceMet":67,
"eligiblePopulation":777,
"stratum":"overall"
}
]
}
}
]
}
]
}
Thanks,
Anuj
Sam Keller
Nov 21, 2017, 10:35:16 AM11/21/17
to anuj Kumar dwivedi, Developer Group for QPP APIs
Hi Anuj,
All multi-performance rate measures will require that all strata listed in qpp-measures-data for the given measure be present for the request to succeed. This is not currently working quite right -- which is why it's item #1 in the Known Bugs thread: https://groups.google.com/forum/#!topic/qpp-apis/BiO5nstREDw
Once this is fixed, you'll get an error message explicitly stating that the request failed because not every strata was listed in the payload.
Thanks,
Sam
--
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+unsubscribe@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/713d9b8b-4713-4290-b32d-71e825c085c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
anuj Kumar dwivedi
Nov 22, 2017, 12:04:11 AM11/22/17
to Developer Group for QPP APIs
Hi Sam,
Ok I got your point and could you please let me know how much time would be taken for resolving this issue ?
I am sharing my findings with you please see following things and respond me of my question.
Those are measures having Multi Performance Rate as listed in qpp-measures-data .
Please see MeasureIds (#122, #391, #005, #007, #008, #024, #138, #224, #238, #366, #392, #398, #007, #009, #046, #394)
My observations/questions:
1. MeasureId #009 having no strata while "MetricType" column is "MultiPerformanceRate". Is it ok or not?
2. Some of measures having more than one strata but those measures are accepting one strata or all strata for example MeasureId #398 having 6 strata (5-17,18-50,ACT5-17,ACT18-50,lowRisk5-17,lowRisk18-50). Is this ok ?
sample code for your reference:
{
"programName":"mips",
"entityType":"individual",
"taxpayerIdentificationNumber":"000456789",
"nationalProviderIdentifier":"0876543210",
"performanceYear":2017,
"measurementSets":[
{
"category":"quality",
"submissionMethod":"registry",
"performanceStart":"2017-01-01",
"performanceEnd":"2017-12-01",
"measurements":[
{
"measureId":"398",
"value":{
"isEndToEndReported":false,
"strata":[
{
"performanceMet":45,
"eligiblePopulation":66,
"stratum":"overall"
},
{
"performanceMet":45,
"eligiblePopulation":667,
"stratum":"5-17"
}
]
}
}
]
}
]
}
3. Some of measures having more than one strata and those measures strictly needed all strata , i mean those measures not allow one strata . for example MeasureId #394 having 4 strata (meningococcal,Tdap,HPV,overall).
sample code for your reference :
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+u...@googlegroups.com.
Kalvin Wang
Nov 22, 2017, 7:10:50 PM11/22/17
to anuj Kumar dwivedi, Developer Group for QPP APIs
Hi Anuj, I think #3 is expected behavior and #2 is a result of the bug Sam mentioned is at the top of our known bugs list. I'll let him follow up on that after the Thanksgiving holiday. Re #1, where are you seeing that measureId 009 has no strata? The measures/measures-data.json file does contain two strata and that doesn't seem to have changed in the past couple weeks:
https://github.com/CMSgov/qpp-measures-data/blob/master/measures/measures-data.json
"category": "quality",
"firstPerformanceYear": 2017,
"lastPerformanceYear": null,
"metricType": "multiPerformanceRate",
"title": "Anti-Depressant Medication Management",
"description": "Percentage of patients 18 years of age and older who were treated with antidepressant medication, had a diagnosis of major depression, and who remained on an antidepressant medication treatment. Two rates are reported. \na. Percentage of patients who remained on an antidepressant medication for at least 84 days (12 weeks). \nb. Percentage of patients who remained on an antidepressant medication for at least 180 days (6 months).\n",
"nationalQualityStrategyDomain": "ECC",
"measureType": "process",
"measureId": "009",
"eMeasureId": "CMS128v5",
"nqfEMeasureId": null,
"nqfId": "0105",
"isInverse": false,
"strata": [
{
"description": "Patients who have received antidepressant medication for at least 84 days (12 weeks) of continuous treatment during the 114-day period following the Index Prescription Start Date",
"eMeasureUuids": {
"initialPopulationUuid": "220EBFDC-C2DF-431B-B14A-8982026B10F1",
"denominatorUuid": "50E80E87-0A09-4914-8632-BD0797460B34",
"numeratorUuid": "02A8409A-7B63-4FE9-B865-87C650DD7459",
"denominatorExclusionUuid": "BA926F92-CA87-43B3-A5C4-FD9FF8B59BB5"
},
"name": ">=84Days"
},
{
"description": "Patients who have received antidepressant medications for at least 180 days (6 months) of continuous treatment during the 231-day period following the Index Prescription Start Date",
"eMeasureUuids": {
"initialPopulationUuid": "1E041190-8EE7-46B0-A735-B416C5FA76FC",
"denominatorUuid": "B1C6949E-6854-4182-8BC9-C0EE75B705A2",
"numeratorUuid": "3A4FA8BB-D8BC-4F66-9367-A71DF03A868D",
"denominatorExclusionUuid": "8C51C326-AE19-462B-9745-6C8ABE92AE27"
},
"name": ">=180Days"
}
],To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@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/27fc327a-8756-4362-abf9-114ded63fc44%40googlegroups.com.
anuj Kumar dwivedi
Nov 23, 2017, 4:49:24 AM11/23/17
to Developer Group for QPP APIs
Ok Kavin,
Could you please let me know how much time would be taken for the fixing of #2 point ?
Thanks,
Anuj
anuj Kumar dwivedi
Nov 27, 2017, 10:03:55 AM11/27/17
to Sam Keller, Developer Group for QPP APIs
Ok Thanks :)
Anuj
On Mon, Nov 27, 2017 at 7:53 PM, Sam Keller <s...@navahq.com> wrote:
Hi Anuj,Kalvin was indeed correct! We are hoping to have that bug fixed in the next few weeks -- we'll update that thread when it's fixed.Thanks,Sam
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@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/45170475-5f5b-40e0-9a11-25a4dc7b663c%40googlegroups.com.
Sam Keller
Nov 29, 2017, 6:17:05 PM11/29/17
to anuj Kumar dwivedi, Developer Group for QPP APIs
Hi Anuj,
Kalvin was indeed correct! We are hoping to have that bug fixed in the next few weeks -- we'll update that thread when it's fixed.
Thanks,
Sam
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@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/45170475-5f5b-40e0-9a11-25a4dc7b663c%40googlegroups.com.
anuj Kumar dwivedi
Dec 9, 2017, 12:24:49 AM12/9/17
to Developer Group for QPP APIs
Any update for point #2 ?
Ivana Ng
Dec 12, 2017, 8:01:42 AM12/12/17
to anuj Kumar dwivedi, Developer Group for QPP APIs
Thanks for checking in. #2 is in this current sprint, so it will be resolved within the next two weeks - and definitely before the API is open for official reporting!
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@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/3e38e465-faaa-4fab-af0e-58e5ad1a116e%40googlegroups.com.
Sam Keller
Dec 12, 2017, 12:55:49 PM12/12/17
to anuj Kumar dwivedi, Developer Group for QPP APIs
Hi Anuj,
We've made a fix for this bug, where the stratum names were not being validated, and it should be deployed to our production environment later today. We'll update the Known Bugs thread once it's deployed.
Thanks,
Sam
To unsubscribe from this group and stop receiving emails from it, send an email to qpp-apis+unsubscribe@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/3e38e465-faaa-4fab-af0e-58e5ad1a116e%40googlegroups.com.
Nick Kraemer
Dec 13, 2017, 2:41:30 PM12/13/17
to Developer Group for QPP APIs
Ok.. this explains why I've been having new issues starting this week. We had been sending in our internal names for stratum and this had started blowing up.
Can you potentially update the documentation for the "stratum" string to be more specific for others? https://cmsgov.github.io/qpp-submissions-docs/measurements#stratum
Right now it gives no indication that it needs to be filled in with the exact "name" field from https://raw.githubusercontent.com/CMSgov/qpp-measures-data/master/measures/measures-data.json
Reply all
Reply to author
Forward
0 new messages