popHealth API Issue: Measure Calculation API is resulting in an 422 Unprocessable Entity Error






Hello,
I am using the popHealth API exposed to upload a QRDA-1 file and receive the measure calculated in popHealth.
With regards to this integration, after uploading the QRDA 1 files, we tried to get the measure calculated using the “start a Measure Calculation” API for popHeath, POST http://popHealthlocalserver/api/queries/
We are getting a 422 Unprocessable Entity Error response from popHealth.  The parameters required to calculate the measure have been sent in a JSON format as per the API help document of popHealth, which is mentioned
as below:
​{
"measure_id":"40280381-52FC-3A32-0153-1A4425A90B6C",
"effective_end_date":"1451606399",
"effective_start_date":"1420070400"
}
Since providers id is not a required field, this has been omitted in the Request JSON.
​Appreciate help with any valuable comments and provide link to resource that provides an answers on technical issues of popHeath Integration.
Thanks
 
Ranjeev Appukuttan 
Eye Care Leaders,
O – 1.239.280.2301x6839 |
 
 
This electronic communication is intended by the sender only for the access and use by the addressee and may contain confidential information. If you are not the addressee, you are notified
that any transmission, disclosure, use, access to, storage or photocopying of this e-mail and any attachments is strictly prohibited. The confidentiality attached to this e-mail and any attachments is not waived, lost or destroyed by reason of a mistaken delivery
to you. If you have received this e-mail and any attachments in error please immediately delete it and all copies from your system and notify the sender by e-mail. Nothing in this communication is intended to operate as an electronic signature under any applicable
law.



like0

Comments

popHealth API Issue: Measure Calculation API is resulting in...

Peter Li's picture


Sorry, we have not updated the API documentation.  The provider is actually required.  Please try it with the provider id.

 

Peter

 

From: Apache <apache@groups.osehra.org> On Behalf Of RANJEEV APPUKUTTAN
Sent: Tuesday, May 15, 2018 11:48 AM
To: pophealth-user@groups.osehra.org
Cc: Vasu Pichikala <Srinivas.Pichikala@eyecareleaders.com>
Subject: [pophealth-user] popHealth API Issue: Measure Calculation API is resulting in an 422 Unprocessable Entity Error

 

Hello,

I am using the popHealth API exposed to upload a QRDA-1 file and receive the measure calculated in popHealth.

With regards to this integration, after uploading the QRDA 1 files, we tried to get the measure calculated using the “start a Measure Calculation” API for popHeath, POST http://popHealthlocalserver/api/queries/

We are getting a 422 Unprocessable Entity Error response from popHealth.  The parameters required to calculate the measure have been sent in a JSON format as per the API help document of popHealth, which is mentioned as below:

​{

"measure_id":"40280381-52FC-3A32-0153-1A4425A90B6C",

"effective_end_date":"1451606399",

"effective_start_date":"1420070400"

}

Since providers id is not a required field, this has been omitted in the Request JSON.

​Appreciate help with any valuable comments and provide link to resource that provides an answers on technical issues of popHeath Integration.

Thanks

 

Ranjeev Appukuttan 

Eye Care Leaders,

O – 1.239.280.2301x6839 |

 

 

This electronic communication is intended by the sender only for the access and use by the addressee and may contain confidential information. If you are not the addressee, you are notified that any transmission, disclosure, use, access to, storage or photocopying of this e-mail and any attachments is strictly prohibited. The confidentiality attached to this e-mail and any attachments is not waived, lost or destroyed by reason of a mistaken delivery to you. If you have received this e-mail and any attachments in error please immediately delete it and all copies from your system and notify the sender by e-mail. Nothing in this communication is intended to operate as an electronic signature under any applicable law.

like1

popHealth API Issue: Measure Calculation API is resulting in an

RANJEEV APPUKUTTAN's picture

Hi Peter,

I tried to add the provider id as well which is the response of my another API which provides me with the pophealth specific provider id for the uploaded file.

Here is the summary of what have been tried.

I have uploaded a QRDA file for Measure 157vs Oncology: Medical and Radiation - Pain Intensity Quantified with Measure ID 40280381-52FC-3A32-0153-1A4425A90B6C

 
When I do a POST to calculate the measure for the provider id that was returned in GET /api/providers response to the body of
Start Measure API POST /api/queries/, I am still getting a similar failure response.
What could be the likely issue, that i am missing here.
Could you help point where i have gone worng or any other suggestion on using the correct paramters and how?
 
{
 "measure_id":"40280381-52FC-3A32-0153-1A4425A90B6C",
 "effective_date": "1451606399",
    "effective_start_date": "1420070400",
 "providers": ["5afaab60fef5f50f577a5513"] 
}
 
GET /api/providers output
[
    {
        "_id": "5ac6648bfef5f57b7be89484",
        "cda_identifiers": [
            {
                "_id": "5ac6648bfef5f57b7be89485",
                "extension": "Administrator",
                "root": "Organization"
            }
        ],
        "depth": 0,
        "family_name": null,
        "given_name": "Administrator",
        "level": null,
        "parent_id": null,
        "parent_ids": [],
        "phone": null,
        "specialty": null,
        "title": null,
        "practice": null
    },
 {
        "_id": "5afaab60fef5f50f577a5513",
        "addresses": [
            {
                "_id": "5afaab60fef5f50f577a5514",
                "city": "Janyburgh",
                "country": "US",
                "state": "NJ",
                "street": [
                    "12345 Boyer Drive Expressway",
                    "Suite 100"
                ],
                "use": "HP",
                "zip": "07653"
            }
        ],
        "cda_identifiers": [
            {
                "_id": "5afaab60fef5f50f577a5517",
                "extension": "1956226363",
                "root": "2.16.840.1.113883.4.6"
            },
            {
                "_id": "5afaab60fef5f50f577a5518",
                "extension": "113408529",
                "root": "2.16.840.1.113883.4.2"
            }
        ],
        "depth": 1,
        "family_name": "Test",
        "given_name": "Provider",
        "level": null,
        "organization": {
            "_id": "5afaab60fef5f50f577a5515",
            "addresses": [
                {
                    "_id": "5afaab60fef5f50f577a5516",
                    "city": "Janyburgh",
                    "country": "US",
                    "state": "NJ",
                    "street": [
                        "12345 Boyer Drive Expressway",
                        "Suite 100"
                    ],
                    "use": "HP",
                    "zip": "07653"
                }
            ],
            "name": null
        },
        "parent_id": "5af5b67efef5f577142bd31f",
        "parent_ids": [
            "5af5b67efef5f577142bd31f"
        ],
        "phone": null,
        "specialty": "207Q00000X",
        "title": null,
        "practice": "StagingFileTest"
    }
]

 

like0

popHealth API Issue: Measure Calculation API is resulting in an

RANJEEV APPUKUTTAN's picture
The issue with the StartMeasure Calculation API have been resolved with the use of below JSON query structure:
 
{
  "measure_id": "40280381-52FC-3A32-0153-1A4425A90B6C",
  "effective_date": 1451520000,
  "effective_start_date": 1420070400,
  "patient_results": null,
  "providers": [
    "5b0e9db7fef5f53b6b8cf26a" // This is the _id of the JSON of the Provider ( found from the upload QRDA CAT-1 file) and using API http://api/providers
  ],
  "query": {
    "measure_id": "40280381-52FC-3A32-0153-1A4425A90B6C",
    "effective_date": 1451520000,
    "effective_start_date": 1420070400,
    "patient_results": null,
    "providers": [
      "5b0e9db7fef5f53b6b8cf26a"
    ]
  }
}
like0

popHealth API Issue: Measure Calculation API is resulting in...

Peter Li's picture


Thanks for the update.

 

Peter

 

From: Apache <apache@groups.osehra.org> On Behalf Of RANJEEV APPUKUTTAN
Sent: Monday, June 4, 2018 3:43 AM
To: PopHealth® User Group <pophealth-user@groups.osehra.org>
Subject: Re: [pophealth-user] popHealth API Issue: Measure Calculation API is resulting in an 422 Unprocessable Entity Error

 

The issue with the StartMeasure Calculation API have been resolved with the use of below JSON query structure:

 

{

  "measure_id": "40280381-52FC-3A32-0153-1A4425A90B6C",

  "effective_date": 1451520000,

  "effective_start_date": 1420070400,

  "patient_results": null,

  "providers": [

    "5b0e9db7fef5f53b6b8cf26a" // This is the _id of the JSON of the Provider ( found from the upload QRDA CAT-1 file) and using API http://10.1.13.116/api/providers

  ],

  "query": {

    "measure_id": "40280381-52FC-3A32-0153-1A4425A90B6C",

    "effective_date": 1451520000,

    "effective_start_date": 1420070400,

    "patient_results": null,

    "providers": [

      "5b0e9db7fef5f53b6b8cf26a"

    ]

  }

}

--
Full post: https://www.osehra.org/post/pophealth-api-issue-measure-calculation-api-resulting-422-unprocessable-entity-error
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/7932

like0