Changelog

Batch eligibility CSVs now support up to 10,000 checks

You can now upload batch eligibility CSV files containing up to 10,000 checks – 10x the previous 1,000-check limit for CSV.

If you need to run more checks, you can upload and run multiple files at the same time.

For details, check out our Batch eligibility CSV upload docs.

Horizon Blue
Cross Blue Shield of New Jersey is now one-click enrollment

Horizon Blue
Cross Blue Shield of New Jersey (Payer ID: 22099) now supports one-click transaction enrollment for Electronic Remittance Advice (ERAs).

What is transaction enrollment?
Transaction enrollment is the process of registering a provider to exchange specific healthcare transactions with a payer. Payers always require transaction enrollments for ERAs.

You can submit and track enrollments using Stedi's transaction enrollment API, the Stedi portal, or a bulk CSV.

One-click enrollment
Enrollment requirements vary by payer. Some payers may require the submitter to sign PDFs or complete tasks in the payer's portal.

If a payer supports one-click enrollment, you only need to submit the enrollment request. There are no follow-up steps. Stedi handles everything else.

You can check whether a payer requires enrollment – and supports one-click enrollment – for ERAs and other transaction types using the Stedi Payer Network or the Payer APIs.

For details, see our transaction enrollment docs.

Introducing the ERA PDF API endpoint

You can now programmatically retrieve PDF versions of your 835 Electronic Remittance Advice (ERAs) using Stedi’s new ERA PDF API endpoint. The {transactionId} path parameter is the ERA's transaction ID.

By default, the endpoint returns the PDF as a base64-encoded string. To get the unencoded PDF data, include the Accept: application/pdf request header. To view the PDF, save the PDF data to a file with a .pdf extension.

curl -X GET \
  "https://healthcare.us.stedi.com/2024-04-01/electronic-remittance-advice/{transactionId}/pdf" \
  -H "Authorization: <api_key>" \
  -H "Accept: application/pdf" \
  > era.pdf

The PDFs are the same as the ones you can download from the Stedi portal:

For more, check out our announcement blog or the API reference.

Introducing enrollment document uploads

You can now upload documents required for transaction enrollment requests directly in the Stedi portal. Only PDF documents are supported.

What is transaction enrollment?

Transaction enrollment is the process of registering a provider to exchange specific healthcare transactions with a payer.

For 835 Electronic Remittance Advice (ERAs), enrollment is always required. A payer only sends ERAs to the clearinghouse the provider has enrolled with, and a provider can only enroll with the payer through one clearinghouse at a time.

Stedi offers fully-managed, API-based transaction enrollment. You can use Stedi’s enrollment API to programmatically submit and track enrollments for providers. You can also use the Stedi portal, which supports bulk CSV imports.

When possible, we handle all enrollment paperwork on your behalf. When we can’t, we let you know what’s needed next.

Upload required enrollment documents

Enrollment requirements vary by payer. Some payers require additional documents, such as:

• A signed form

• A practice W-9

• A voided check

Previously, Stedi emailed you to request these documents and asked you to email them back to us.

With this update, we’ll still email you when an enrollment requires action. But, now, you can upload completed documents by clicking Upload new document in the Documents section of the enrollment’s details page in the Stedi portal.

For more information, see our documentation.

Get payer website URLs in the Stedi Payer Network and Payers API

You can now get a payer’s website URL using the Stedi Payer Network and the Payers API.

Stedi payer records now list the payer’s website URL, when provided.

View payer URLs in the Stedi Payer Network
Each payer now includes a Visit payer website link, when available in the payer’s record, in the Payer pane:

The Payer page also includes the link:

Retrieve payer URLs using the Payers API
All Payers API endpoints also now return the urls.website response property, if available, for payer records.

{
    "displayName": "Blue Cross Blue Shield of Texas",
    "primaryPayerId": "84980",
    ...
    "urls": {
      "website": "https://www.bcbstx.com"
    }
  }
}

Download ERA PDFs without a Stedi logo

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:

1. Go to the Transactions page.

2. Click the ERA transaction you want to download.

3. On the Overview tab, click Fetch artifact. Then click … and select Download 835 ERA PDF without Stedi logo.

Resubmit professional claims using Stedi's CMS-1500 form

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.

Claim edit: Missing admission source code

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 admissionSourceCode field is missing or empty.
    AND

  • The placeOfServiceCode field does not contain 14 (Non-Patient Laboratory).

• Raw X12
  If you’re using raw X12, the edit fails if:

  • CL1-02 (Admission Source Code) of Loop 2300 (Claim Information) is missing or empty.
    AND

  • C023-01 (Facility Type Code) of Loop 2300 is NOT 14 (Non-Patient Laboratory).

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:

{
  "errors": [
    {
      "code": "33",
      "description": "Missing admission source code. This code is required on all institutional claims with the exception of non-patient laboratory claims (Type of Bill 014x). Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

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.

Automatically add support users for Stedi apps

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 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 can install a Stedi app to connect their Stedi account to their EHR.

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.

Blue Cross Blue Shield of Kansas City is now one-click enrollment

Blue Cross Blue Shield of Kansas City (Payer ID: 47171) now supports one-click transaction enrollment for Electronic Remittance Advice (ERAs).

What is transaction enrollment?
Transaction enrollment is the process of registering a provider to exchange specific healthcare transactions with a payer. Payers always require transaction enrollments for ERAs.

You can submit and track enrollments using Stedi's transaction enrollment API, the Stedi portal, or a bulk CSV.

One-click enrollment
Enrollment requirements vary by payer. Some payers may require the submitter to sign PDFs or complete tasks in the payer's portal.

If a payer supports one-click enrollment, you only need to submit the enrollment request. There are no follow-up steps. Stedi handles everything else.

You can check whether a payer requires enrollment – and supports one-click enrollment – for ERAs and other transaction types using the Stedi Payer Network or the Payer APIs.

For details, see our transaction enrollment docs.