Stedi's drop-in replacements for critical Change Healthcare APIs
Mar 3, 2024
Products
The prolonged Change Healthcare outage due to a cyberattack has left thousands of healthcare providers unable to submit claims, eligibility checks, and other critical transactions to payers. The outage is expected to continue for weeks. Companies have been scrambling to implement solutions to get back online but are faced with large development efforts to switch to bespoke API formats offered by other clearinghouses.
Stedi's drop-in replacement for Change Healthcare's Professional Claims V3 and Eligibility V3 APIs allow customers who have been using Change to directly switch with minimal development effort. Customers can use the same Change API JSON or X12 request format with Stedi’s APIs, and Stedi will automatically submit transactions to payers and other clearinghouses as necessary. Our APIs are Generally Available today and we are able to get customers live on a same-day turnaround.
Our primary goal is to help providers submit claims and eligibility checks as quickly as possible. We’ve created a streamlined contracting process along with a standardized price list and the ability to match volume pricing previously provided by Change. We’ve set up a dedicated email address for inquiries – change@stedi.com – and can establish a dedicated Slack channel to start working with engineering teams in under an hour from first contact.
Stedi’s Claims and Eligibility APIs
Our APIs are designed as drop-in replacements for Change Healthcare’s Professional Claims V3 and Eligibility V3 APIs. The APIs:
Accept Change Healthcare's JSON request format.
Translate it to X12 837P for claims and X12 270 for eligibility.
Submit the transactions to payers and clearinghouses using SFTP and real-time EDI.
Return the Claims and Eligibility API response in Change Healthcare's JSON format.
Have full support for returning 277/835 files as JSON-formatted webhooks to endpoints of your choosing (to replace Change’s Claims Responses and Reports V2 API functionality), as well as 999s and other transaction types.
Visit our API documentation for details on API endpoints available as well as example request and response payloads.
Security-first architecture
Stedi is SOC 2 Type II and HIPAA compliant. We view these certifications as a minimum floor and have built security into our platform from the ground up:
Stedi’s Healthcare APIs are built 100% on AWS infrastructure with no other external vendor dependencies.
Customer resources are stored in dedicated single-tenant AWS accounts for strict tenancy isolation, with one customer per AWS account.
Stedi HIPAA accounts are secured by mandatory multi-factor Authentication (MFA) and have role-based access control (RBAC) powered by Amazon Verified Permissions.
You can see more in our Trust Center.
Get in touch
To get into our priority queue for an immediate response, visit stedi.com/healthcare to submit a contact request or email us at change@stedi.com. We can start working with you immediately to get back online.
The prolonged Change Healthcare outage due to a cyberattack has left thousands of healthcare providers unable to submit claims, eligibility checks, and other critical transactions to payers. The outage is expected to continue for weeks. Companies have been scrambling to implement solutions to get back online but are faced with large development efforts to switch to bespoke API formats offered by other clearinghouses.
Stedi's drop-in replacement for Change Healthcare's Professional Claims V3 and Eligibility V3 APIs allow customers who have been using Change to directly switch with minimal development effort. Customers can use the same Change API JSON or X12 request format with Stedi’s APIs, and Stedi will automatically submit transactions to payers and other clearinghouses as necessary. Our APIs are Generally Available today and we are able to get customers live on a same-day turnaround.
Our primary goal is to help providers submit claims and eligibility checks as quickly as possible. We’ve created a streamlined contracting process along with a standardized price list and the ability to match volume pricing previously provided by Change. We’ve set up a dedicated email address for inquiries – change@stedi.com – and can establish a dedicated Slack channel to start working with engineering teams in under an hour from first contact.
Stedi’s Claims and Eligibility APIs
Our APIs are designed as drop-in replacements for Change Healthcare’s Professional Claims V3 and Eligibility V3 APIs. The APIs:
Accept Change Healthcare's JSON request format.
Translate it to X12 837P for claims and X12 270 for eligibility.
Submit the transactions to payers and clearinghouses using SFTP and real-time EDI.
Return the Claims and Eligibility API response in Change Healthcare's JSON format.
Have full support for returning 277/835 files as JSON-formatted webhooks to endpoints of your choosing (to replace Change’s Claims Responses and Reports V2 API functionality), as well as 999s and other transaction types.
Visit our API documentation for details on API endpoints available as well as example request and response payloads.
Security-first architecture
Stedi is SOC 2 Type II and HIPAA compliant. We view these certifications as a minimum floor and have built security into our platform from the ground up:
Stedi’s Healthcare APIs are built 100% on AWS infrastructure with no other external vendor dependencies.
Customer resources are stored in dedicated single-tenant AWS accounts for strict tenancy isolation, with one customer per AWS account.
Stedi HIPAA accounts are secured by mandatory multi-factor Authentication (MFA) and have role-based access control (RBAC) powered by Amazon Verified Permissions.
You can see more in our Trust Center.
Get in touch
To get into our priority queue for an immediate response, visit stedi.com/healthcare to submit a contact request or email us at change@stedi.com. We can start working with you immediately to get back online.
The prolonged Change Healthcare outage due to a cyberattack has left thousands of healthcare providers unable to submit claims, eligibility checks, and other critical transactions to payers. The outage is expected to continue for weeks. Companies have been scrambling to implement solutions to get back online but are faced with large development efforts to switch to bespoke API formats offered by other clearinghouses.
Stedi's drop-in replacement for Change Healthcare's Professional Claims V3 and Eligibility V3 APIs allow customers who have been using Change to directly switch with minimal development effort. Customers can use the same Change API JSON or X12 request format with Stedi’s APIs, and Stedi will automatically submit transactions to payers and other clearinghouses as necessary. Our APIs are Generally Available today and we are able to get customers live on a same-day turnaround.
Our primary goal is to help providers submit claims and eligibility checks as quickly as possible. We’ve created a streamlined contracting process along with a standardized price list and the ability to match volume pricing previously provided by Change. We’ve set up a dedicated email address for inquiries – change@stedi.com – and can establish a dedicated Slack channel to start working with engineering teams in under an hour from first contact.
Stedi’s Claims and Eligibility APIs
Our APIs are designed as drop-in replacements for Change Healthcare’s Professional Claims V3 and Eligibility V3 APIs. The APIs:
Accept Change Healthcare's JSON request format.
Translate it to X12 837P for claims and X12 270 for eligibility.
Submit the transactions to payers and clearinghouses using SFTP and real-time EDI.
Return the Claims and Eligibility API response in Change Healthcare's JSON format.
Have full support for returning 277/835 files as JSON-formatted webhooks to endpoints of your choosing (to replace Change’s Claims Responses and Reports V2 API functionality), as well as 999s and other transaction types.
Visit our API documentation for details on API endpoints available as well as example request and response payloads.
Security-first architecture
Stedi is SOC 2 Type II and HIPAA compliant. We view these certifications as a minimum floor and have built security into our platform from the ground up:
Stedi’s Healthcare APIs are built 100% on AWS infrastructure with no other external vendor dependencies.
Customer resources are stored in dedicated single-tenant AWS accounts for strict tenancy isolation, with one customer per AWS account.
Stedi HIPAA accounts are secured by mandatory multi-factor Authentication (MFA) and have role-based access control (RBAC) powered by Amazon Verified Permissions.
You can see more in our Trust Center.
Get in touch
To get into our priority queue for an immediate response, visit stedi.com/healthcare to submit a contact request or email us at change@stedi.com. We can start working with you immediately to get back online.
Share
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.