Changelog

We’re replacing the SUBMITTED transaction enrollment status with two new statuses that show who needs to act next:

• STEDI_ACTION_REQUIRED – Stedi needs to take action.

• PROVIDER_ACTION_REQUIRED – You or the provider need to take action.

The SUBMITTED status is now deprecated. Any existing requests will keep the SUBMITTED status and use the previous status workflow until they're live, canceled, or rejected.

We've also clarified the PROVISIONING status to mean only thing: the request has been submitted to the payer.

These changes make it easier to see which requests need your attention. You can filter by the PROVIDER_ACTION_REQUIRED status in the Stedi portal or List Enrollments endpoint to see which requests require action by you or your provider. For example, using the endpoint:

https://enrollments.us.stedi.com/2024-09-01/enrollments?status=PROVIDER_ACTION_REQUIRED

How enrollment statuses work now

Requests submitted through the Stedi portal or a bulk CSV now start in the STEDI_ACTION_REQUIRED status. If you’re using the Create Enrollment endpoint, you can set the status to STEDI_ACTION_REQUIRED to start processing the enrollment.

You can now submit 837I institutional claims as X12 EDI using the Institutional Claims X12 API endpoint.

Most Stedi customers submit 837I claims using our JSON-based Institutional Claims endpoint. JSON is familiar and easy to work with. You can build an integration faster.

But if you already work with X12, converting to JSON wastes time. The new endpoint accepts X12 directly. 

Previously, X12 submissions of 837I claims required SFTP. With SFTP, you have to wait for files to get errors or validation. With the API, you get instant responses. Development is faster, and debugging is easier.

For complete details, check out the Institutional Claims (837I) Raw X12 API reference.

Stedi integrated accounts and Stedi apps are now available. Together, this new set of capabilities allows end customers of Stedi’s Platform Partners to have Stedi accounts of their own.

Integrated accounts drastically reduce the amount of clearinghouse functionality that partners need to build themselves.

Integrated accounts
Integrated accounts are simplified Stedi accounts that are designed to be friendly to non-technical users. The more complex developer-focused functionality – such as configuring API access and webhooks, and viewing raw JSON payloads – has been removed.

Stedi apps
Integrated accounts can install Stedi apps, which are Stedi’s pre-built integrations to a growing list of third-party RCM, PMS, EHR, and other platforms.

Stedi apps allow providers to quickly connect their Stedi account to these external systems using preconfigured SFTP credentials and API keys.

They can also grant Stedi portal access for external support and implementation teams to assist with setup and ongoing support.

Learn more
See our announcement blog.

You can now correct and resubmit claims directly from the transaction detail page of any claim in the Stedi portal. 

We’ve also made other UI improvements that make the portal’s Claims section simpler and faster to use. Here’s what’s new:

• Streamlined list views and filters on the Transactions and Files pages help you find what you need, fast.

• Cleaner detail pages for transactions and files put the most important information front and center.

For more information, see our announcement blog.