Changelog

You can now download documents for a transaction enrollment request directly from its details page in the Stedi portal. This includes documents signed by Stedi on your behalf if you use delegated signature authority.

For more information, see our documentation.

You can now use the Stedi Agent in sandbox accounts and test mode.

In sandbox accounts and test mode, you run predefined mock eligibility requests that return realistic responses. The Stedi Agent is the Stedi portal’s built-in AI assistant. It helps you recover failed eligibility checks.

Previously, you could only use the Stedi Agent for failed eligibility checks in production. Now, you can try the agent out in sandbox accounts and test mode using a predefined mock check.

For more information, check out the announcement blog.

You can now filter results more precisely in the List Enrollments and List Providers API endpoints.

We’ve also updated the Enrollments page and Providers page in the Stedi portal to surface these filters.

List Enrollments endpoint

We’ve added new query parameters to the List Enrollments endpoint. You can use the parameters to filter by:

• Partial term: filter lets you search across multiple fields at once.
  
  

• Status: Filter by one or more enrollment statuses—such as DRAFT, SUBMITTED, PROVISIONING, LIVE, CANCELED, or REJECTED.
  
  

• Provider details: Filter by NPI (providerNpis), tax ID (providerTaxIds), or name (providerNames).
  
  

• Payer: Filter by payer IDs (payerIds).
  
  

• Source: Limit results by how the enrollment was created: API, UI, or IMPORT.
  
  

• Transaction type: Filter by transaction types, like eligibilityCheck, claimStatus, or claimSubmission.
  
  

• Date: Filter enrollments by when they were created (createdFrom, createdTo) or when their status last changed (statusUpdatedFrom, statusUpdatedTo).
  
  

• Import ID: If an enrollment was created through CSV import, filter by the returned importId.

Several of these query parameters accept arrays. You can include an array parameter more than once in the URL to filter by multiple values.

List Providers endpoint

The List Providers endpoint now accepts a filter parameter for searching by provider name, NPI, or tax ID. Filtering is case-insensitive and supports partial matches.

Updated filters in the Stedi portal

Alongside API improvements, we’ve updated the Stedi portal to surface these new filters on the Enrollments page and Providers page.

On the Enrollments page:

On the Providers page:

Now available in Stedi's Eligibility Manager, the Stedi Agent brings AI-powered automation to healthcare clearinghouse workflows, beginning with eligibility check recovery.

Use the Stedi Agent to recover failed eligibility checks. If a check fails with a known recoverable error, a Resolve with Stedi Agent option appears next to the related search. The agent runs in Debug view, where you can watch it work – step by step, in real time.

For more information, see our announcement blog.

Stedi now enriches most Blue Cross Blue Shield (BCBS) eligibility responses by automatically including the member’s home payer name and primary payer ID whenever possible.

This info appears in a related benefitsInformation.benefitsRelatedEntities entry in our JSON eligibility responses and in a 2120C or 2120D loop in X12 responses.

For more information, see our announcement blog.

Stedi is now e1 certified by the HITRUST for foundational cybersecurity.

HITRUST e1 Certification demonstrates that Stedi’s healthcare clearinghouse platform is focused on the most critical controls to demonstrate that essential cybersecurity hygiene is in place. The e1 assessment is one of three progressive HITRUST assessments that leverage the HITRUST Framework (HITRUST CSF) to prescribe cyber threat adaptive controls that are appropriate for each assurance type.

You can now run real-time eligibility checks using our CAQH CORE–compliant SOAP API endpoint.

Most Stedi customers use our JSON API for real-time eligibility. But if you're already using CAQH CORE SOAP, this new endpoint is the fastest way to start running eligibility checks with Stedi.

The endpoint supports CAQH CORE Connectivity Rule vC2.2.0. We plan to support CAQH CORE Connectivity Rule vC4.0.0 as industry adoption increases.

For complete details, see our documentation.

Today, Stedi announces the release of its Model Context Protocol (MCP) server.

The MCP server gives AI agents plug-and-play access to Stedi’s Real-Time Eligibility and Search Payers API endpoints, along with built-in guidance for common errors. You can connect your agents without having to write integration code or copy documentation.

For more information, see the announcement blog and our documentation.

You can now use the Retrieve Payer API endpoint to get a single payer record by its Stedi payer ID:

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

The endpoint returns the same payer information as our existing JSON-based Payer API endpoints: payer ID, name, payer ID aliases, transaction support, enrollment requirements, and more. Just for a single payer.

For more information, see the Stedi docs and the announcement blog.

You can now use the Stedi Platform Partners directory to find RCM, EHR, and practice management systems that use Stedi.

Many healthcare companies are looking for modern RCM solutions – and can’t or don’t want to build one themselves. The directory helps you find solutions that are powered by Stedi’s API-first clearinghouse rails.

For more information, see the announcement blog.

You can now authorize Stedi to sign enrollment forms for you using delegated signature authority, eliminating over 90% of your team’s enrollment paperwork.

Delegated signature authority is available to all Stedi customers. To get started, reach out to Stedi support.

For more details, see the blog.

You can now see whether a payer supports medical or dental transactions using the Payers API and Stedi Payer Network.

Every payer in the network now includes a coverageTypes field in responses from Payers API endpoints. For example, in JSON responses:

{
  "items": [
    {
      "displayName": "Blue Cross Blue Shield of North Carolina",
      "primaryPayerId": "BCSNC",
      ...
      "coverageTypes": ["dental"]
      ...
    }
  ]
}

If you’re using the Search Payers API endpoint, you can also filter by coverage type. Example:

GET /payers/search?query=blue+cross&coverageType=dental

For more details, see the blog.

You can now run batch 270/271 eligibility checks by uploading a CSV file in the Stedi portal.

Use the new Eligibility check batches page to run batch checks using a bulk CSV:

• Submit up to 1,000 checks per file.

• Run multiple files at the same time.

• Pull results from any batch using the Poll Batch Eligibility Checks API.

Track all batches – CSV or API – in real time, in one place.

For more details, see the blog.

You can now use the List Payers CSV API to get a full list of Stedi’s supported payers in CSV format:

curl --request GET \
  --url https://healthcare.us.stedi.com/2024-04-01/payers/csv \
  --header 'Authorization: <api-key>'

The CSV includes the same data as the Stedi Payer Network UI and other JSON-based Payer APIs:

• Payer IDs

• Transaction support flags

• Transaction enrollment requirements, and more.

For complete details, see the List Payers CSV API docs.

When the status of a transaction enrollment request changes, Stedi now sends you an automated email.

No setup is needed. These email notifications replace our previous manual notification process.

If an enrollment requires action on your part, we’ll continue to reach out to you via Slack or email with next steps.

For more information, check out our related blog.

CAQH CORE has officially certified Stedi for real-time eligibility checks.

This certification confirms that our 270/271 transactions meet CORE’s strict standards for:

• What data a 271 response must include

• Standardized error messaging

• System uptime and performance under real-world conditions

For more details, see our CORE certification blog.

You can now submit transaction enrollments to select payers in a single step.

Just submit an enrollment request using Stedi’s Enrollments API, UI, or a bulk CSV import. We do the rest.

One-click enrollment is available for 850+ payers. Check the Stedi Payer Network or Payer APIs to see which payers are supported.

To learn more, see our full blog.

Stedi now has a direct connection to Zelis, a multi-payer provider platform.

Many payers use Zelis as their primary way of delivering 835 Electronic Remittance Advice (ERA) files through clearinghouses to providers.

To receive ERAs from Zelis, providers must set up an account in the Zelis portal. This involves selecting a clearinghouse from a prepopulated list. Previously, providers using Stedi had to select an intermediary clearinghouse in order to receive ERAs.

With Stedi’s new direct Zelis connection, you can now choose Stedi from the list of integrated clearinghouses. Once set up, you’ll automatically receive ERAs from all Zelis-connected payers directly through Stedi.

To submit new enrollment requests, use the Enrollments API, UI, or a bulk CSV import. For Zelis-connected payers, we’ll instruct you to select Stedi as the clearinghouse in Zelis when needed.

If you previously submitted a Stedi enrollment for a Zelis-connected payer, you can log into Zelis and select Stedi as the clearinghouse to transition to Stedi’s direct Zelis connection without any interruption or downtime.

For details, see the blog.

Stedi has partnered with Anatomy, a modern healthcare lockbox and document conversion service, to help you turn paper explanations of benefits (EOBs) into standard 835 Electronic Remittance Advice (ERA) transactions.

Previously, providers receiving paper EOBs had to scan and manually enter payment data, slowing down posting and introducing errors. You can now use Anatomy to handle paper EOBs using your existing digital workflow.

Anatomy accepts paper or PDF EOBs and converts them into 835s. Anatomy then securely sends the 835s to Stedi on your behalf. In Stedi, you can enroll to receive 835s from Anatomy just like you would if they were a payer. You get the ERAs using the 835 ERA Report API or the from-stedi directory of your Stedi SFTP connection. You can use webhooks to get notified when new ERAs are available.

Anatomy is now listed as a supported payer in the Stedi Payer Network. For more details, see the blog.

You can now use the Search Payers API to programmatically search the Stedi Payer Network.

The API lets you search by the payer’s name, payer ID, or payer ID alias. The search supports fuzzy matching, so it returns close matches even if the provided payer name isn’t exact. You can further filter the results by supported transaction types, like dental claims (837D) or eligibility checks (270/271).

The following request searches for the “Blue Cross” payer name and filters for payers that support eligibility checks and real-time claim status.

curl --request GET \
  --url https://healthcare.us.stedi.com/2024-04-01/payers/search?query=Blue%20Cross&eligibilityCheck=SUPPORTED&claimStatus=SUPPORTED \
  --header 'Authorization: <api-key>'

Visit the Search Payers API docs for complete details.

We’ve also updated the Stedi Payer Network UI to use the new API. You now get consistent search results across the UI and API.