Changelog
Never miss a new feature - subscribe to email updates
Trusted by the fastest-growing healthtech companies
Dec 15, 2025
You can now correct and resubmit 837P professional claims using the Stedi portal’s CMS-1500 form.
Previously, if you submitted a claim using Stedi’s CMS-1500 form and later needed to fix it, you had two options:
Re-enter all the data into the form by hand.
Use the portal’s Edit and resubmit feature to change the raw X12.
Now, you can revise the previous claim directly in Stedi’s CMS-1500 form. Stedi loads the data from the original claim into the form for you.

For more details, see our announcement blog.
Dec 15, 2025
You can now download unbranded ERA PDFs without a Stedi logo in the Stedi portal.
Stedi generates a PDF version of each Electronic Remittance Advice (ERA) you receive. Previously, all ERA PDFs included “Powered by Stedi” in the page footer. Now, you have the option to download ERA PDFs without this footer.

To download an unbranded ERA PDF:
Go to the Transactions page.
Click the ERA transaction you want to download.
On the Overview tab, click Fetch artifact. Then click … and select Download 835 ERA PDF without Stedi logo.

Dec 12, 2025
Stedi now rejects 837I institutional claims that are missing a required admission source code.
In an institutional claim, the admission source code tells you where the patient came from, such as the emergency room (ER), a doctor’s referral, or another facility.
Most institutional claims require this code. Without it, the payer can’t adjudicate the claim. The one exception is non-patient lab services, where no patient is present.
If the code is missing when required, the payer may reject the claim, which can cause payment delays.
This edit – the industry’s term for an automated validation rule – catches the issue before the claim reaches the payer.
When this edit applies
An institutional claim will fail this edit in the following cases:
JSON API
If you’re using Stedi’s JSON institutional claim submission API endpoint, the edit fails if:The
admissionSourceCodefield is missing or empty.
ANDThe
placeOfServiceCodefield does not contain14(Non-Patient Laboratory).
Raw X12
If you’re using raw X12, the edit fails if:
Rejection errors
If you submit a claim that fails the edit using Stedi’s institutional claim submission API endpoints, you’ll get back an error message in real time. If you’re using the JSON API endpoint, the response includes error details in the errors array:
If you submit a claim that fails the edit using SFTP, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will contain a related claim status category code, claim status code, and error message. You can use the error message to correct and resubmit the claim.
Dec 11, 2025
Stedi app developers can now configure their apps to automatically add one or more support users – called members – to accounts that install their app.
App developers can use the support users to provide support or help with implementation.
This new feature is optional. The support user has the Developer role.
What is a Stedi app?
A Stedi app is a prebuilt integration between Stedi and a third-party platform.
Stedi accounts on the Basic plan can install Stedi apps to quickly connect their account to a third-party Revenue Cycle Management (RCM) system, Practice Management System (PMS), Electronic Health Record (EHR) platform, or other Stedi Platform Partners.
For example, a practice or provider on Stedi’s free Basic plan can install a Stedi app to connect their Stedi account to their EHR.
As an app developer, you can choose to offer your app for free on the Basic plan or require a paid upgrade.
Get started with Stedi apps
To discuss publishing or configuring a Stedi app, contact us. You can also check out Publish your app in our developer docs.
To install a Stedi app, log in the Stedi portal and go to the Apps page. You can also check out our related docs.