Changelog

You can now submit five new mock requests for dental benefits 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 now for Ameritas, Anthem Blue Cross Blue Shield of CA, Cigna, Metlife, and UnitedHealthcare.

Use the new List Payers API to programmatically retrieve information about thousands of supported payers in our Payer Network. 

The following Blue Cross Blue Shield of North Carolina response example shows that real-time eligibility checks, real-time claim status requests, and professional claims are supported for this payer. The response also indicates that payer enrollment is required for 835 ERAs (claim remittances).

{
  "stediId": "UPICO",
  "displayName": "Blue Cross Blue Shield of North Carolina",
  "primaryPayerId": "BCSNC",
  "aliases": [
    "1411",
    "560894904",
    "61473",
    "7472",
    "7814",
    "BCBS-NC",
    "BCSNC",
    "NCBCBS",
    "NCPNHP"
   ],
   "names": [
     "Blue Cross Blue Shield North Carolina"
   ],
   "transactionSupport": {
     "eligibilityCheck": "SUPPORTED",
     "claimStatus": "SUPPORTED",
     "claimSubmission": "SUPPORTED",
     "claimPayment": "ENROLLMENT_REQUIRED"
   }
}

We adapted the National Uniform Claim Committee (NUCC) 1500 Claim Form into a user-friendly digital form you can use to submit claims manually. 

Our in-app form validates provider NPIs and other key information to reduce errors and payer rejections. You can also review a live preview of the autogenerated JSON payload for our Professional Claims API to understand how the form relates to the request structure.

To submit a manual claim, visit the Create manual claim page in the Stedi app.

You can now use the CMS-1500 Claim Form PDF API to programmatically retrieve auto-generated claim forms for submitted 837 professional claims. All you need is an API Key for authentication and Stedi’s transaction ID for the processed claim. 

curl --request GET \
  --url https://healthcare.us.stedi.com/2024-04-01/export/{transactionId}/1500/pdf \
  --header 'Authorization: <api-key>'

You can use the API to make auto-generated claim form PDFs available for download within an EHR, practice management, or revenue cycle system. You can also automate retrieving them for internal use, such as record-keeping, mailing and faxing claims to payers, or reviewing claim information in a familiar format.

Stedi can now automatically generate and deliver negative TA1s for inbound transactions. TA1 Interchange Acknowledgments indicate receipt of an interchange and identify any errors in the interchange’s envelope (ISA and IEA) information.

Stedi can generate two types of negative TA1s:

• Accepted with errors: TA1s with code E in TA104 indicate that the interchange was accepted with errors. Stedi proceeds with processing the transaction and creates a record in the Stedi app

• Rejected because of errors: TA1s with code R in TA104 indicate that the interchange was rejected and that Stedi won’t continue processing the transaction.

You can enable automatic TA1s in each partnership’s Acknowledgments settings. Visit the Acknowledgments documentation for complete details. 

You can use the new List Payers API to programmatically retrieve information about every supported payer in our Payer Network. The response includes:

• The payer’s name, Payer ID, aliases, and alternative names.

• Whether the following transactions are supported: real-time eligibility checks, professional claims, real-time claim status requests, and ERAs (claim payments).

• Whether payer enrollment is required for each transaction type.

Note: The API is currently in BETA, meaning we may make breaking changes. We recommend only using this API for prototyping.

Stedi can now automatically generate positive TA1s for inbound transactions and deliver them to your trading partners. 

TA1 Interchange Acknowledgments indicate receipt of an interchange and identify any errors in the interchange’s envelope (`ISA` and `IEA`) information. Positive TA1s contain code `A` in the `TA104` element to indicate you received the interchange successfully, and it contains no errors.

Enable automatic TA1s for each partnership in the Acknowledgments settings. You can send TA1s for every inbound file or only when your trading partner requests them. Visit the Acknowledgments documentation for complete details. 

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.

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.

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. 

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.