Claims Responses and Reports v1

Summary API Attachments FAQ CHANGE LOG     

Overview

The Claims Responses and Reports API provides a direct connection to your mailbox where payers will send their responses and reports to your claims.

Change Healthcare provides comprehensive reports that allow you to monitor the flow of transactions as we process them for you. Specifically for claims, Change Healthcare will deliver available payer reports back to you as the payers present them to us, providing you the most recent and best information available. Electronic reports are available to support all available transactions, including claims, medical statements, and Electronic Remittance Advice (ERA).

API Onboarding

See the Security and Authorization section in this portal to learn more about using our APIs. Most of our APIs are private and require credentials to gain access.

After receiving your client_id and client_secret for our sandbox environment, you can test the API from within our interactive documentation, using an application such as Postman, or from your own stack.

Try our Postman Collection Run in Postman

Do you have a sandbox that I can test before signing a contract?

We sure do. After receiving your client_id and client_secret for our sandbox environment, you can test the API from within our interactive documentation, using an application such as Postman, or from your own stack.

Try our Postman Collection Run in Postman

What information needs to go in the request header?

In the header for an Reports API request, you need to pass an authorization token. You can get the token by making an API call to:

curl -X POST \
  'https://sandbox.apis.changehealthcare.com/apip/auth/v2/token' \
  -H 'Content-Type: application/json' \
  -d '{
  "client_id": "<Your-ClientId>",
  "client_secret": "<Your-ClientSecret>",
  "grant_type": "client_credentials"
}'

This is a precursor to making an Reports API call, which might have the following headers:

Content-Type: application/json
Authorization: Bearer <Your-Access-Token>

Read all about our protocols in the Security -> Authorization section of this portal.

When you're ready for production, simply remove sandbox from the URL.

What does a typical reports API call look like?

The Reports API uses a GET HTTPS call:

GET /medicalnetwork/reports/v1 HTTP/1.1
Host: sandbox.apis.changehealthcare.com
Authorization: Bearer <Your-Access-Token>
Content-Type: application/json

What does a typical reports API response look like?

{
    "reports": [
        "05011338.00",
        "XB200654.PV",
        "XB200654.N2",
        "XB200654.QH",
        "XB200654.OE",
        "XB200654.OK",
        "06271006.00",
        "report.0405090800",
        "XB200654.OP",
        "XB200654.KG",
        ...
    ]
}

What does a typical reports filename API call look like?

The Reports API uses a GET HTTPS call:

GET /medicalnetwork/reports/v1/{filename} HTTP/1.1
Host: sandbox.apis.changehealthcare.com
Authorization: Bearer <Your-Access-Token>
Content-Type: application/json

What does a typical reports filename API response look like?

{
    "report_content": "ISA~00~          ~00~          ~ZZ~CLAIMSCH       ~ZZ~010414         ~180511~1112~|~00501~100321569~0~P~^_TA1~020120501~131121~1506~A~000_GS~FA~ECGCLAIMS~K10353~20180511~1112~000000001~X~005010X231A1_ST~999~0001~005010X231A1_AK1~HC~1~005010X223A1_AK2~837~00704~005010X223A1_IK5~A_AK9~A~000001~000001~000001_SE~0000000006~0001_GE~000001~000000001_IEA~00001~100321569_"
}

Example system error:

{
    "description": "Report <filename> not found",
    "error": 404
}

File Name and File Types

Review File_Name_Matrix in the Attchments tab.

Change Log

API Name API Version Date Introduced Available Until
Reports v1 11/01/19 TBD

Release Notes:

v1

  • Initial offering of Reports