Changelog

Improved transaction view

The transaction details page has the following improvements:

• For 837P (professional) claims, Stedi automatically puts key details, including subscriber information and the claim value, at the top for easy access. You can also instantly download a PDF of the autogenerated 1500 Claim Form. 

• Transactions with a common business identifier are clearly identified and linked, so you can easily move between related transactions.

• The transaction’s raw input and output are available for review and download. 

• Multiple other UX updates to make the transaction’s data easier to understand and digest.

You can review this information by clicking any transaction on the Transactions page in the Stedi app.

Retrieve payer responses with new Report APIs for claim status and ERA processing

You can now use the following APIs to retrieve payer responses in JSON format:

• Get 277 Report: Retrieve processed 277 Claim Acknowledgments

• Get 835 Report: Retrieve processed 835 Electronic Remittance Advice (ERA) transactions

You can either poll or listen for event-driven webhooks to discover new payer responses. Then, you can call the Report APIs to retrieve the processed responses from Stedi. For convenience, Stedi returns 277s and 835s in the same JSON format as the Change Healthcare (CHC) Convert Reports APIs.

Download auto-generated 1500 Claim Form PDFs

For every claim you submit through our Professional Claims APIs, Stedi now automatically generates a complete 1500 Claim Form. You can download these PDF claim forms from the transaction detail page for that claim in the Stedi app.

This feature is useful when you need to export claim forms for record-keeping purposes, physically mail a claim to a payer, or review specific claim information in a familiar format. 

Compare and instantly roll back to previous versions of a Stedi mapping

You can now review a mapping’s version history, compare older versions with the current, and instantly roll back to any published version. This functionality helps you better understand the updates made in each version and debug issues in production mappings.

To review a mapping’s version history, go to the mapping, open the Actions menu, and select Version history. You can choose to publish an older version or compare it with the current version in production. Comparing highlights every difference between the old and current versions to show you what has been added or deleted.

Eligibility Check API supports 200+ new dental payers

You can now send eligibility checks to more than 200 dental payers through Stedi’s growing Payer Network. New dental payers include Guardian, Delta Dental, UHC Dental, Anthem Blue Cross Blue Shield, Pacificare Dental & Vision Plan, Aetna Dental, Cigna Dental, and more.

Search the Payer Network to instantly find the payer ID for any payer and use it to start sending real-time eligibility checks through Stedi’s Eligibility Check API.

New X12 EDI APIs for eligibility checks and claims processing

The following APIs are now available for customers who want to send raw X12 EDI to payers. These APIs are ideal for companies that generate X12 EDI internally and want to use Stedi to validate and deliver these transactions to payers.

• Eligibility Check Raw X12: Send raw X12 EDI 270 Eligibility Benefit Inquiry transactions and receive the payer’s raw X12 EDI 271 Eligibility, Coverage, or Benefit Information in the response - all in real time.

• Professional Claims Raw X12: Send raw X12 EDI 837P (professional) Health Care Claims to payers.

• Claim Status Raw X12: Send raw X12 EDI 276 Claim Status requests and receive the payer’s raw X12 EDI 277 Status Request Response - all in real time.

Major improvements to the Stedi Payer Network

We redesigned the Stedi Payer Network to make it more comprehensive and user friendly. Improvements include:

• Enhanced searching and filtering capabilities so you can instantly find the payers you need for your use case.

• Alternative payer names to help you identify payers using the name most familiar to your organization. For example, “Eaton Benefits Ohio” is an alternative associated with “Cigna”—searching for either name returns the same payer within the database. 

• UX improvements, including clearly showing all of the transaction types supported for each payer as well as the payer ID and any payer ID aliases.

Mappings UI now autosaves and stages updates for publishing

The Mappings UI now autosaves your changes and stages them for publishing. When you’re ready, you can promote changes to production by clicking Publish changes. You can also discard changes to revert back to the previously published version.

List Transactions and Poll Transactions APIs now return business identifiers

The List Transactions and Poll Transactions APIs now return business identifiers for each transaction.

Business identifiers are values you can use to correlate a transaction with related transactions or other data in your business system. For example, Stedi automatically marks the purchase order number (PRF01) as a business identifier for 850 Purchase Orders. 

The following example shows a truncated API response containing the new businessIdentifiers object.

Send mock requests to the real-time Eligibility Check endpoint

You can now submit mock requests to the Legacy Real-Time Eligibility Check JSON endpoint, and Stedi returns mock eligibility responses you can use for testing. To send a mock request, you need a Stedi API key for authentication, and you must set the stedi-test header to true.

Try it for Cigna.

Set a custom filename for outbound EDI files

You can now set custom filenames for generated EDI files within outbound transaction settings.

By default, Stedi autogenerates a unique name for outbound files using a UUID. To specify a custom filename, open Advanced settings in the outbound transaction setting and enter a JSONata expression into the Filename expression field. 

You can use & (Concatenation) or $millis in the expression to generate a unique name based on the processing timestamp. For example, the expression “EDI850-” & $millis() results in filenames like EDI850-5182341242.

Lock production mappings to prevent accidental changes or deletions

You can now lock mappings in your account to prevent accidental changes or deletions. Any user in your Stedi account can lock a mapping, but only an account admin can unlock it. 

You can lock the entire mapping or just the mapping definition. When you lock the mapping definition only, you can add or edit lookup tables, but you cannot edit the mapping source schema, target schema, or mapping expressions. 

To lock a mapping, open it, click the ...(ellipses) menu next to its name, and select Lock settings.

Claims API autocorrects non-Latin characters

Our Professional Claims API now automatically replaces non-Latin characters with their Latin equivalents. 

Claim submissions with non-conforming characters are a common cause of 999 rejections from the payer. The new autocorrect feature will help reduce these types of errors and the (often significant) time and manual work it takes to fix them.

Detailed eligibility check error messages and resolution steps

The Legacy Real-Time Eligibility Check JSON endpoint now returns detailed AAA error messages that specify why the payer rejected the transaction and any recommended follow-up actions. Stedi includes this information in the aaaErrors object in the response JSON.

The following example shows an error at the subscriber level:

Visit our eligibility check troubleshooting docs for a complete list of all possible error types and resolution steps.

EDI platform improvements

We released the following EDI platform features:

You can now lock guides in your account to prevent accidental changes or deletions. Any user in your Stedi account can lock a guide, but only an account admin can unlock them. To lock a guide, go to the Actions menu and select Lock.

When configuring an outbound test file, you can now review the EDI that Stedi will generate from your JSON test data. To generate an outbound test file, go to the Files page, open the Create file menu, and select Test outbound.

Introducing the Stedi Payer Network

Introducing the Stedi Payer Network - a comprehensive list of every payer Stedi supports for eligibility checks, claim submission, and claim status checks. You can search by the payer’s name or payer ID alias to retrieve their payer ID, learn which Stedi APIs are supported, and determine whether or not the payer requires provider enrollment.

Map and retrieve processed inbound files asynchronously

The new Map Transaction Output endpoint applies a Stedi mapping to a previously processed inbound transaction and returns the fully mapped output.

You can use the endpoint to retrieve processed transaction data asynchronously and ingest it into your business system. This approach can be helpful when the mapped output is too large for Stedi to deliver through a Destination webhook.

User-friendly responses from manual eligibility checks

When you perform a manual eligibility check through the Stedi app, you can now review a more user-friendly 271 Eligibility, Coverage, or Benefit Information response organized by coverage type and level. Click a row to review more details about the benefit type, including the Service Type Code (STC) and the raw JSON response data. 

Submitting a manual eligibility check can be useful for testing and when you need to do a one-time eligibility check. Learn more about eligibility checks in our docs.

Introducing Stedi’s real-time Claim Status API

Stedi’s Claim Status endpoint directly replaces the Change Healthcare (CHC) Claim Status API. You can use it to check the status of an existing claim.

• Call Stedi’s endpoint with a JSON payload in the CHC 276 Claim Status format.

• Stedi automatically maps CHC payer IDs to our IDs.

• Stedi translates the JSON to the X12 EDI 276 format and delivers it to the payer or peer clearinghouse.

• The endpoint returns a synchronous 277 response in the CHC Claim Status response JSON format.

Visit the Claim Status API docs for more information.

Send and monitor real-time eligibility checks in the Stedi app

From the Eligibility menu in the Stedi app, you can now perform the following actions:

Submit manual eligibility checks and review the full 271 JSON response. This feature is useful for testing and for operations teams who need to do one-off checks.

Review errors for every eligibility check you send through the Stedi API and the app. You can filter by payer or timeframe (last hour, last day, or last week) and view details about each error code.