Change Log/Release Notes
Change Log
API Name | API Version | Date Introduced | Available Until |
---|---|---|---|
Eligibility | v3 | 4-17-19 | |
Eligibility | v2 | 1-1-19 | Deprecated |
Eligibility | v1 | 1-1-18 | Deprecated |
Release Notes:
v3 Updates (9/20/2021)
Change Healthcare Medical Network APIs support a significant troubleshooting feature called metadata. API users do not need to enable this capability; it is automatic and has no effect on information in any medical transaction. If you encounter any issues with a transaction and need to work with CHC technical support, you can furnish the representative with the values provided in the meta
object. This enables the technician to get a head start on addressing the problem.
{
"meta": {
"senderId": "Xxxx.Xxxxxx",
"applicationMode": "prod",
"traceId": "bc409414-70ed-e387-e7d8-7addd7a7b599"
},
The meta
object obtains its data from the request headers and the transaction token.
v3 Updates (9/2/2021)
Medical Network APIs are now deployed to an enhanced cloud-native network connection, which offers improved API speed and reliability. We recommend updating your systems to the following API endpoint URLs at the first opportunity::
- Production: apigw.changehealthcare.com/medicalnetwork/eligibility/v3
- Sandbox: sandbox.apigw.changehealthcare.com/medicalnetwork/eligibility/v3
v3 Updates (03/05/2021)
- Added two arrays - benefitsRelatedEntities and eligibilityAdditionalInformationList. Each JSON object in benefitsRelatedEntities maps to objects within Loop 2120C. Each JSON object in eligibilityAdditionalInformationList maps to objects in Loop 2115C. Objects in the array will be equal to the number of times the loop repeats. In the future, we will deprecate the legacy benefitsRelatedEntity and eligibilityAdditionalInformation objects because information is already captured in objects that are part of their respective arrays.
- Documentation updates
v3 Updates (11/30/2020)
- Security and Authorization changes in v3
- Host and url changes
- Removed the Accept application/vnd.changehealthcare.medicaleligibility-v2+json header mentioned in v2, no need to send or increment, Versioning will be managed via the url path.
- Documentation updates
v2
- Request/response is now a single medical eligibility request/response
- Error response schema changed
- Adding address to subscriber and dependents in response
- Must send Header: Accept application/vnd.changehealthcare.medicaleligibility-v2+json
v1
- Initial offering of Eligibility
Updated over 1 year ago