Log inContact us

Changelog

Never miss a new feature - Follow Stedi on Twitter and LinkedIn

July 17, 2024

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:

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.


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.


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.

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.


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.


Send mock requests to the real-time Eligibility Check endpoint

You can now submit mock requests to the Eligibility Check 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.


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.


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.


Track payer uptime on Stedi’s real-time Payer Status page

Stedi supports a growing list of payers for real-time eligibility checks and claim status. On our new Payer Status page, you can now review the current and historical uptime for these payers and subscribe to outage notifications. 

You can receive outage notifications for any payer through email, Slack, Microsoft Teams, and Google Chat. These notifications can help you debug payer errors and understand when to retry requests.


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.


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.






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 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.


View destination attempts from the event details page

The Stedi app now displays Destination webhook delivery attempts to help with testing and debugging. This page includes metadata about the delivery attempt, including the destination, the time of the attempted delivery, and detailed logs about each delivery stage. 

To review delivery attempts, click a processed file or transaction, click any event to view its details page, and then go to the Destination attempts tab.



Require Multi-factor Authentication for your account

You can now require all users to enable Multi-Factor Authentication (MFA) before accessing your Stedi account. To enforce MFA for all users:

  1. Click the account name.
  2. Select Account settings and toggle MFA to ON.

The next time each user logs into the account, Stedi prompts them to set up their MFA token. Once you enable MFA for a Stedi account, it cannot be disabled.


Mappings UX improvements

The following improvements make it easier to build and update Stedi mappings.

You can now view more context about Stedi guide segments and elements when you hover over them, allowing you to understand which part of the guide you are mapping more easily. This is especially helpful for large guides, including many X12 HIPAA guides, that repeat the same loop or segment in multiple locations. 

You can now search within a mapping’s source or target fields for a specific text string and jump to each matching value. For example, you might search for the name of a specific segment or element.



X12 HIPAA guides preloaded into Stedi guide builder

It’s now easier to build custom healthcare guides that conform to X12 HIPAA specifications. When creating a new guide, set the X12 Release to 5010 HIPAA. Stedi automatically preloads every HIPAA transaction set from the Stedi Network for you to choose as a base for customization. 

Stedi guides are machine-readable versions of the EDI requirements trading partners typically provide as PDF, CSV, or Word documents. You can use Stedi’s guide builder to customize any X12 HIPAA transaction for your EDI integration. Then, you can make your guides public to share them with trading partners as user-friendly, interactive web pages.


Idempotency for Generate EDI API

The Generate EDI API now supports idempotent requests. 

When you send a request to the Generate EDI API, you can include an idempotency key to prevent sending duplicate data to your trading partners. In the event of network errors or other intermittent failures, you can safely retry requests with the same idempotency key as many times as necessary within 24 hours after making the first request. Learn more.


Stedi app UX improvements

We made the following improvements to the Stedi app:

Execution metadata: You can now view file execution metadata, which includes the X12 Interchange and Functional Group values, along with other processing information. To view a file’s execution metadata, go to the Files page, click the file you want to view, and select Raw Metadata in the Results tab.

Event retries: You can now retrigger individual events from both the transaction details page and the file details page. 

AS2 certificate validation: Stedi now gives you immediate feedback about errors in your local and partner signing and encryption certificates. For example, you will now receive an error when your certificate is improperly formatted, when a certificate doesn’t validate against a certificate chain, when a public and private key pair don’t match, and more.


New HIPAA guides in the Stedi Network

You can now find the following X12 HIPAA guides in the Stedi Network:

The Stedi Network is a free and open catalog of Stedi guides for hundreds of popular trading partners. You can import any X12 HIPAA guide into your account for free and use it in your EDI integration. 

Request guides: If you don’t see your partner’s guides in the Stedi Network, submit a request, and we’ll build the guides you need for free in 1-2 business days.


Authorization Header update

We updated the authorization scheme in our API to better align with OpenAPI specifications.

The Authorization header no longer requires the Key prefix. Instead, you should now provide API keys directly (Authorization ${STEDI_API_KEY}). This change aligns with the OpenAPI standard and allows for out-of-the-box compatibility with OpenAPI tools and services.

Previously, our APIs required API keys to be passed with a Key prefix (Authorization: Key ${STEDI_API_KEY}), which required manual setup to work with OpenAPI. We will continue to support the previous format for backward compatibility, but we encourage you to adopt the new format to leverage the benefits of OpenAPI compliance.


Support for new X12 release 008050

You can now read and write EDI for X12 release 008050, the latest version approved in December 2023 and released in February 2024. Stedi now supports every release from 002001 (released in 1987) to present.

The 008050 release is supported throughout the entire Stedi platform. You can review every 008050 transaction set in EDI Reference, create PDF and machine-readable 008050 Stedi guides for your trading partners and EDI integrations, and process live 008050 transactions instantly.


Pre-filled settings for OAuth 2.0 Destination webhooks

Stedi Destinations now pre-fills the grant_type header for OAuth 2.0.

When you create or edit a Stedi Destination with OAuth 2.0 configured, the Header parameter grant_type is now pre-populated with client_credentials. This is the most common grant type used when the client is acting on its own behalf. You can change this value in the Advanced menu if you need to use a different grant type.

This change helps ensure that your OAuth 2.0 connections are set up correctly and securely, without extra manual configuration.

For more details on the OAuth 2.0 protocol, visit RFC 6749 section 4.4, which outlines the protocol for the client credentials grant.


Custom Interchange Version Control Number Code

You can now set a custom Interchange Version Control Number Code (ISA-12) for generated EDI files. 

When you call the Generate EDI API, the outbound transaction setting ID you provide dictates which Stedi Guide will be used for validation and translation. By default, Stedi sets ISA-12 to be the X12 release number of the associated guide. However, some trading partners may require that you specify a different release for the transaction and the ISA envelope – for example, you might send a transaction from X12 release 003020 inside an ISA envelope with an Interchange Version Control Number Code of 00401.

Visit the Generate EDI docs for complete details about ISA and GS overrides.


Support for additional X12 releases and custom GS identifier codes

You can now use Stedi to read and write any transaction set from all releases in the 1980s-era X12 Version 2:

With this update, Stedi now has complete coverage of all transaction sets across all releases from X12 002001 to X12 008040.

Stedi also now supports custom GS-08 Industry Identifier Codes for all X12 releases when reading and writing EDI.

Industry Identifier Codes are the 1-6 characters appended to the end of a release in the GS-08 element – for example, 005010UCS and 004010VICS or 005010X279A1 in the X12 HIPAA standard. You can now define your own custom identifier for any transaction set as needed. Custom identifiers are helpful when trading with automotive OEMs such as Ford (which uses 002002FORD) and Chrysler (which uses 002040CHRY).


Improved Stedi app navigation

We consolidated the top navigation bar to make the Stedi app easier to use and understand. 

The top navigation is now organized into three sections:

  • Files: Review, sort, filter, and inspect every file flowing through Stedi. This page was previously called File executions.
  • Transactions: Review, sort, filter, and inspect every EDI transaction flowing through Stedi. 
  • Setup: Access all the tools and configurations required to onboard and manage trading partners. This menu includes Trading partners, Guides, Destinations, EDI settings, and Mappings (if applicable). 

We also consolidated documentation and resources into a single menu and co-located key account admin pages, such as Account settings, under the account selection menu.


Retrieve file execution metadata

Stedi stores metadata about each successful file execution, such as the processing timestamp and X12 Interchange and Functional Group values. You can now retrieve this metadata through the following methods:


Retry individual events without reprocessing a file

You can now retrigger events for successfully processed files. This feature makes it easier to test your end-to-end integration – for example, triggering webhooks – without continually reprocessing the same files.

To retry an event:

  1. Go to the Files page.
  2. Click the name of the processed file.
  3. Go to the Events tab.
  4. Click the ellipses (...) next to an event and select Retry.

X12 HIPAA 999 Implementation Acknowledgment added to the Stedi Network

The HIPAA 999 Implementation Acknowledgment is now available in the Stedi Network’s collection of X12 HIPAA guides. 

The Stedi Network is a free and open catalog of Stedi guides for hundreds of popular trading partners. Stedi guides are a machine-readable format for EDI requirements that Stedi uses to automatically validate, translate, and generate EDI according to trading partner’s requirements.

You can import the 999 into your account for free and add it to transaction settings for your EDI integration. 

Request guides: If you don’t see your partner’s guides in the Stedi Network, submit a request, and we’ll build the guides you need for free in 1-2 business days.


Set the log level for Destination webhooks

To make debugging easier, you can now set the log level for each Destination webhook. Destination webhooks allow you to send transaction data and events from Stedi to any external API. 

You can edit the webhook to switch between the following log levels at any time:

  • OFF - no logs
  • ERROR - errors only
  • INFO - errors and select execution steps, such as successful deliveries
  • TRACE - all execution steps

To review a webhook’s logs, click its name and then go to the Logs tab.


Test your mapping for multiple use cases

When building a Stedi mapping for reading EDI, you can now switch between the sample files attached to the source guide. Sample files typically represent the use cases when you could receive that transaction set from your trading partner. For example, the X12 HIPAA 834 Benefit Enrollment and Maintenance guide includes samples for adding subscriber coverage, canceling a dependent, changing subscriber information, and more.

As you switch between samples, Mappings dynamically updates the source JSON shape and the expected mapping results, so you can ensure your mapping works for each use case. 

The Mappings module is a powerful JSON-to-JSON transformation engine that helps you transform Guide JSON into and out of the shape you need for your business system. You can use Stedi’s visual mapper to build mappings for both inbound and outbound transactions.


Import guides when creating transaction settings

You can now import your trading partner’s EDI guides directly from the Stedi Network when creating transaction settings. The Stedi Network has pre-built guides for hundreds of popular trading partners that you can use in your integration for free.

Stedi guides are a machine-readable version of the EDI requirements – sometimes called implementation guides – that your partner would typically provide as PDF, CSV, or Word documents. When you add a guide to a transaction setting, Stedi validates and translates (inbound files) or generates (outbound files) EDI according to the guide’s requirements. 

Request guides: If you don’t see your partner’s guides in the Stedi Network, submit a request and we’ll build the guides you need for free in 1-2 business days.


Trigger Destination webhooks based on connection and data mode

You can now configure transaction.processed.v2 event bindings to trigger a Destination webhook based on the following new filters:

  • Connection: Inbound files from a specific connection. This option is useful when there are multiple connections within the same partnership. For example, you may set up a separate SFTP connection for test files and route them to a test endpoint.
  • Mode: The transaction contains a specific value in the ISA-15 element, which is used in X12 to distinguish between test and production files. This option is useful when you want to send test and production data to separate endpoints.

Destination webhooks allow you to automatically send data and events from Stedi to any external API. You can configure one or more event bindings that conditionally trigger each webhook. The new Connection and Mode filters are available under the Advanced menu.




Send transformed file processed events to your API

You can now use Mappings to automatically transform file.processed.v2 events into a custom JSON shape. You can then attach the mapping to a Destination webhook to automatically forward transformed event data to your API.

For every successful file execution, Stedi emits a file.processed.v2 event that includes information about when Stedi processed the file, the associated partnership configuration, the file size, and more.

Visit the Events documentation for complete details.


Create Stedi mappings faster

Stedi Mappings is our powerful JSON-to-JSON transformation engine. We recently made the following major improvements to the visual mapping tool:

  • The visual mapper now shows warnings when the expected mapping output does not match the target JSON Schema. These warnings highlight issues such as invalid value types and missing properties to help you more easily create a complete, accurate mapping.
  • We added a quickstart workflow that makes it easier to create new mappings. You can choose a quickstart for reading EDI (mapping transactions from Stedi to a custom shape for your API), writing EDI (mapping JSON from your system to the shape required for Stedi’s Generate API), and ingesting Stedi events (for example, mapping `file.failed.v2` events to a custom shape).
  • To help you keep mappings up-to-date, we added clearer notifications when a connected Stedi guide has changed (for example, it has new segments or elements) and provided instructions for pulling those changes into your mapping.
The new Stedi mappings quickstart options

View Destination webhook logs

You can now view detailed logs for each Destination webhook and filter them by a specific date range. The logs provide details about how the webhook is functioning, such as when each webhook is triggered and the response from the configured endpoint, which can help you troubleshoot issues. 

Destination webhooks allow you to send transaction data and events from Stedi to any external API. To view the logs for a destination, click its name to go to its details page, and then navigate to the Logs tab.


Customize the filename for autogenerated acknowledgments

You can now set a custom filename for autogenerated acknowledgments to comply with your trading partner’s requirements.

Stedi can automatically generate a 997 Functional Acknowledgment or a 999 Implementation Acknowledgment for each inbound transaction and deliver it to a specified connection.

To set a custom filename, navigate to the partnership, turn on the Acknowledgments functionality, and enter a JSONata expression into the Filename expression field. For example, the expression "EDI997_" & $millis()would produce filenames that start with EDI997 and then contain a timestamp, such as EDI997-5182341242.edi.


Filter inbound files from Remote SFTP/FTPS connections

You can now specify a regex expression for Stedi to use when retrieving files from a Remote SFTP/FTPS connection. When polling the remote server, Stedi only processes files that match the filter pattern.

For example, your trading partner may place files for multiple different entities on the remote server, with different prefixes for each entity. In this case, you could write a regex expression that matches only files with a given prefix.

You can specify a Filter pattern for the remote poller in the connection’s Inbound settings.

Stedi
(332) 378-5040
228 Park Ave S, Ste 58460, New York, NY 10003, USA
Product
ClaimsEligibility checksEDI platform
Backed by
AdditionBloomberg BetaFirst RoundStripeUSV
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.
Service TermsPrivacy Notice