Changelog

Introducing the Stedi plugin for ChatGPT

Stedi’s ChatGPT plugin is now available in OpenAI’s ChatGPT plugin directory. It lets healthcare providers run patient insurance eligibility checks from within their business’s ChatGPT account.

For example, once connected, you can ask ChatGPT to:

@Stedi Check Jane Doe's coverage before I schedule her appointment.
She's on Aetna, member ID AETNA12345, born April 4, 2004.
Provider is Stedi, NPI 1999999984.

The plugin only takes a few clicks to set up and requires no configuration or custom integration. To access it, you’ll need the ChatGPT Enterprise plan; the plugin isn't available on ChatGPT plans for individuals (Free/Go/Plus/Pro).

To learn more, see our announcement blog.

Introducing the eligibility checks view

You can now track individual eligibility check attempts in the new checks view of the Stedi portal's Eligibility page.

Previously, the Stedi portal’s Eligibility page grouped all related retries of the same eligibility check into a single record, called an eligibility search. To view individual check attempts, you had to click into the search record.

Now, the Eligibility page has two views, which you can toggle between:

  • Checks – Lists every eligibility check attempt as its own row. When you retry a check, the retry appears as a separate row alongside the original. Now the default view.

  • Searches – Groups all retries of the same check into a single record, called an eligibility search.

The checks view lets you reference the result of any single attempt and spot failure patterns. For example, you can filter by payer to see whether every check in the last hour failed, which can signal a payer outage.

Eligibility checks in the checks view are sorted by processed date, newest first. You can filter by processed date, result, member ID, payer, provider NPI, error code, and search ID.

Search statuses now reflect the prevailing check

In the searches view, a single eligibility search can contain several checks with different results. To determine the status of a search, Stedi has to pick which check’s result represents the search as a whole.

Previously, each search showed the status from the most recent check. For example, a search whose latest check failed had a Failed status, even if an earlier attempt returned active coverage.

Now, each eligibility search shows the status and data from the check with the highest-priority status, called the prevailing check. Stedi ranks statuses in the following order: Active → Inactive → Investigate → Failed. If two checks have the same status, the more recent check wins.

The prevailing check’s data applies to all search-level data, not just status. Patient information, payer details, Service Type Codes (STCs), and error metadata now come from the prevailing check.

For example, a search with a failed check, then an active check, then a second failed check now shows as Active. The active check is the prevailing result, even though it isn't the most recent.

For more information, see our Eligibility views docs.

Claim edit: Missing other payer adjudication date in COB claims

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that list a previous payer but are missing that payer's adjudication date.

How the edit works

When a patient has more than one insurance plan, say a child covered by both parents' health insurance, claims go to the primary payer first, then the secondary, and so on. This is called coordination of benefits (COB).

Claims sent to non-primary payers must report each previous payer's payments and adjustments. These claims must also include the date on which each previous payer adjudicated – or determined how to pay – the claim. This information helps the payer establish the sequence of benefits as well as timely filing determinations.

You can provide the adjudication date for either the entire claim or each service line.

Claim-level adjudication date

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.otherSubscriberInformation[].otherPayerName.otherPayerAdjudicationOrPaymentDateDTP*573 (Adjudication or Payment Date) of Loop 2330B (Other Payer Name)
837I institutionalclaimInformation.otherSubscriberInformation.otherPayerName.otherPayerAdjudicationOrPaymentDateDTP*573 (Adjudication or Payment Date) of Loop 2330B (Other Payer Name)
837D dentalclaimInformation.otherSubscriberInformation[].otherPayerName.otherPayerAdjudicationOrPaymentDateDTP*573 (Adjudication or Payment Date) of Loop 2330B (Other Payer Name)

Service line adjudication date

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.serviceLines[].lineAdjudicationInformation[].adjudicationOrPaymentDateDTP*573 (Adjudication or Payment Date) of Loop 2430 (Line Adjudication Information)
837I institutionalclaimInformation.serviceLines[].lineAdjudicationInformation[].adjudicationOrPaymentDateDTP*573 (Adjudication or Payment Date) of Loop 2430 (Line Adjudication Information)
837D dentalclaimInformation.serviceLines[].lineAdjudicationInformation[].adjudicationOrPaymentDateDTP*573 (Adjudication or Payment Date) of Loop 2430 (Line Adjudication Information)

If you don't specify a previous adjudication date in a COB claim, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Missing Claim Check or Remittance Date. This date is required when the identified other payer, [other payer name], has previously adjudicated the claim and the line check or remittance date is not provided. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A6>516>PR*[DATE]*U*[AMOUNT]********Missing Claim Check or Remittance Date. This date is required when the identified other payer, [other payer name], has previously adjudicated the claim and the line check or remittance date is not provided. Correct and resubmit.~

Claim edit: Duplicate occurrence span codes in institutional claims

Stedi now rejects 837I institutional claims that include the same occurrence span code more than once within a single occurrence span group.

How the edit works

In institutional claims, occurrence spans are a range of dates for a significant event in a patient's care. Occurrence span codes tell the payer what each span of dates represents. These codes can affect how much a payer will approve or pay for a claim.

For example, occurrence span code 70 reports the qualifying inpatient stay dates that establish eligibility for a skilled nursing facility claim. Code 74 reports a noncovered level of care or leave of absence. Occurrence span codes are defined by the National Uniform Billing Committee (NUBC).

A claim can contain up to two groups of occurrence span codes. Each group can contain up to 12 codes.

Occurrence span code

Claim typeJSON API fieldX12 element
837I institutionalclaimInformation.occurrenceSpanInformations[][].occurrenceSpanCodeHI-02 (Occurrence Span Code) of Loop 2300 (Claim Information), where HI-01 is BI (Occurrence Span)

The NUBC states that each occurrence span code must be unique within a single group. If a claim includes the same occurrence span code more than once within a single group, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Occurrence Span Code(s). If submitting multiple occurrence span codes, each code must be unique. The submitted occurrence span code(s) are submitted more than once, 70. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>721*[DATE]*U*[AMOUNT]******A7>732**Invalid Occurrence Span Code(s). If submitting multiple occurrence span codes, each code must be unique. The submitted occurrence span code(s) are submitted more than once, 70. Correct and resubmit.~

Related claim edits

Stedi has another edit for duplicate occurrence codes. Occurrence codes report a single event on a specific date. Occurrence span codes report a condition that applied over a range of dates. See Duplicate occurrence codes in institutional claims.

Claim edit: Insurance type code not allowed for the primary payer

Stedi now rejects 837P professional and 837D dental claims that include an insurance type code for the primary payer.

What is an insurance type code?

Insurance type codes are only required in coordination of benefits (COB) scenarios where Medicare – or a Medicare Administrative Contractor (MAC) – is not the primary payer.

In COB scenarios, the patient is covered by insurance from more than one payer. The primary payer pays first, then the secondary payer, and so on. Payer responsibility level codes, also called payment responsibility sequence number codes, indicate this order. A code of P indicates the primary payer.

An insurance type code indicates why Medicare is not the primary payer on a claim. For example, code 12 means the patient has an employer group health plan that pays before Medicare.

Claims should only include an insurance type code when providing information about the non-primary payer, such as the secondary or tertiary payer. You can provide an insurance type code in two places, depending on whether it's for the payer you're sending the claim to or one of the patient's other payers:

Insurance type code for the payer you’re sending the claim to

Claim typeJSON API fieldX12 element
837P professionalsubscriber.insuranceTypeCodeSBR-05 (Insurance Type Code) of Loop 2000B (Subscriber Information)
837D dentalsubscriber.insuranceTypeCodeSBR-05 (Insurance Type Code) of Loop 2000B (Subscriber Information)

Insurance type codes for the patient’s other payers

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.otherSubscriberInformation[].insuranceTypeCodeSBR-05 (Insurance Type Code) of Loop 2320 (Other Subscriber Information)
837D dentalclaimInformation.otherSubscriberInformation[].insuranceTypeCodeSBR-05 (Insurance Type Code) of Loop 2320 (Other Subscriber Information)

How the edit works

A claim shouldn’t include an insurance type code for the primary payer. If it does, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid insurance type code usage. When the payer is primary for the subscriber, an insurance type code is not allowed. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A7>578>HK*[DATE]*U*[AMOUNT]******A8>742**Invalid insurance type code usage. When the payer is primary for the subscriber, an insurance type code is not allowed. Correct and resubmit.~

Claim edit: Invalid paid amount

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that report a negative or non-numeric other payer paid amount on a service line.

How the edit works

When a patient has more than one insurance plan, say a child covered by both parents’ health insurance, claims go to the primary payer first, then the secondary, and so on. This is called coordination of benefits (COB).

Claims sent to non-primary payers must report each previous payer’s payments for each service line.

Service line paid amount

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.serviceLines[].lineAdjudicationInformation[].serviceLinePaidAmountSVD-02 (Service Line Paid Amount) of Loop 2430 (Line Adjudication Information)
837D dentalclaimInformation.serviceLines[].lineAdjudicationInformation[].serviceLinePaidAmountSVD-02 (Service Line Paid Amount) of Loop 2430 (Line Adjudication Information)
837I institutionalclaimInformation.serviceLines[].lineAdjudicationInformation[].serviceLinePaidAmountSVD-02 (Service Line Paid Amount) of Loop 2430 (Line Adjudication Information)

A service line's paid amounts must be non-negative numbers. If they aren't, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Other Payer Paid Amount. The service line other payer paid amount must be a valid number greater than or equal to zero. The submitted value on line 1 is invalid, -150.00. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A7>643>PR*[DATE]*U*[AMOUNT]******A8>710**Invalid Other Payer Paid Amount. The service line other payer paid amount must be a valid number greater than or equal to zero. The submitted value on line 1 is invalid, -150.00. Correct and resubmit.~

Claim edit: Missing last name

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a person entity with no last name.

How the edit works

In a claim, each entity, such as the billing provider or subscriber, is identified as either a person or a non-person using an entity type qualifier.

When an entity is a person, both a first name and last name are required. In X12, this is the entity’s NM1-03 element. If a person’s last name is missing, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

How entity type qualifiers are specified

If you use Stedi's JSON Claim Submission API endpoints, Stedi sometimes infers the entity type qualifier. For example, if you provide a firstName and lastName for the billing provider in a JSON 837P Professional Claims API request, the entity is treated as a person.

If you use X12, you set the entity type qualifier in NM1-02 (Entity Type Qualifier). 1 indicates a person and 2 indicates a non-person entity, such as a hospital or billing organization.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A6>504>85*[DATE]*U*[AMOUNT]********Missing Last Name. Last name is required when Billing Provider is reported as a person by the entity type qualifier 1. Correct and resubmit.~

Related claim edits

Stedi has a companion edit for missing first names. See Claim edit: Missing first name.

Claim edit: Payer responsibility level codes must be in order

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that skip a level in the payer responsibility sequence.

What are payer responsibility level codes?

In coordination of benefits (COB) scenarios, the patient is covered by insurance from more than one payer. The primary payer pays first, then the secondary payer, and so on.

COB claims must include information about all previous payers. Payer responsibility level codes, also called payment responsibility sequence number codes, indicate each payer’s payment order: P (primary), S (secondary), T (tertiary), then A through H for the fourth through eleventh payers.

Payer responsibility level code for the payer you’re sending the claim to

Claim typeJSON API fieldX12 element
837P professionalsubscriber.paymentResponsibilityLevelCodeSBR-01 (Payer Responsibility Sequence Number Code) in Loop 2000B (Subscriber Hierarchical Level)
837D dentalsubscriber.paymentResponsibilityLevelCodeSBR-01 (Payer Responsibility Sequence Number Code) in Loop 2000B (Subscriber Hierarchical Level)
837I institutionalsubscriber.paymentResponsibilityLevelCodeSBR-01 (Payer Responsibility Sequence Number Code) in Loop 2000B (Subscriber Hierarchical Level)

Payer responsibility level codes for the patient’s other payers

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.otherSubscriberInformation[].paymentResponsibilityLevelCodeSBR-01 (Payer Responsibility Sequence Number Code) in Loop 2320 (Other Subscriber Information)
837D dentalclaimInformation.otherSubscriberInformation[].paymentResponsibilityLevelCodeSBR-01 (Payer Responsibility Sequence Number Code) in Loop 2320 (Other Subscriber Information)
837I institutionalclaimInformation.otherSubscriberInformation[].paymentResponsibilityLevelCodeSBR-01 (Payer Responsibility Sequence Number Code) in Loop 2320 (Other Subscriber Information)

How the edit works

If a claim reports a secondary or later payer, it must also report every prior payer level before it in the order. Otherwise, the payer may reject the claim.

For example, the payer may reject a claim that reports a tertiary payer without a secondary payer.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Note: A responsibility level code of U (Unknown) won’t trigger this edit. A code of U doesn’t indicate a specific payment order.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Payer Responsibility Sequence. Any payer responsibility level above primary must follow the prior levels in order. The submitted payer responsibility values are out of order, P, T. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>742*[DATE]*U*[AMOUNT]******A7>732**Invalid Payer Responsibility Sequence. Any payer responsibility level above primary must follow the prior levels in order. The submitted payer responsibility values are out of order, P, T. Correct and resubmit.~

Related claim edits

Stedi has another edit for duplicate payer responsibility level codes. See Duplicate payer responsibility level codes.

Stedi also rejects claims that don't report a primary payer. See Missing primary payer.

Introducing paper claim submissions

You can now submit paper claims through Stedi.

Some payers don't accept electronic claims. Payers may also require paper claims for workers’ compensation, automobile, or liability-related claims.

Until now, you had to print and mail those paper claims yourself. That meant running a separate manual process outside your electronic claims workflow.

With paper claim submission, you submit through the same workflows as electronic claims: API, SFTP, or the Stedi portal. Stedi prints the claim and mails it to the payer for you.

Supported claim types

You can submit two claim types for printing and mailing:

Claim typeSubmission methods
Professional claim (CMS-1500 paper form)API: JSON API, Raw X12 API SFTP: 837P X12 EDI Stedi portal UI: CMS-1500 Claim Form or X12 upload
Institutional claim (UB-04 paper form)API: JSON API, Raw X12 API SFTP: 837I X12 EDI Stedi portal UI: X12 upload

How paper claims work

To submit a paper claim:

  • Set the receiver ID – the ID for the entity receiving the transaction – to PAPER ("Print and Mail – All Payers"). If using the Stedi portal UI's CMS-1500 Claim Form, select By mail under Send instead.

  • Set the payer ID, payer name, and payer address to the payer you’d like to mail the claim to.

  • Fill out the rest of the claim as usual.

Transaction enrollment isn't required for paper claims.

For more detailed examples and instructions, see our documentation.

Availability and pricing

Paper claim submission is available on all Stedi production accounts.

Stedi charges for paper claims based on the number of printed and mailed pages. The number of pages varies based on the claim’s type and service line count:

Claim typeService lines per page
Professional claim (CMS-1500 form)Up to 6
Institutional claim (UB-04 form)Up to 22

A claim spills onto additional pages when its service lines exceed what one form holds. For example, a professional claim (CMS-1500 form) with 10 service lines requires 2 pages.

See stedi.com/pricing for per-page pricing.

Learn more

For more details, see our announcement blog and documentation.

Claim edit: Invalid CLIA number format

Stedi now rejects 837P professional claims that report a Clinical Laboratory Improvement Amendments (CLIA) number in an invalid format.

What is a CLIA number?

A Clinical Laboratory Improvement Amendments (CLIA) number identifies a lab authorized to test human specimens. CLIA is a federal laboratory regulatory program administered by the Centers for Medicare & Medicaid Services (CMS) and applies to the operation of the laboratory. Medicare and Medicaid claims that bill for lab services require this number. Most other payers have the same requirement.

You can specify CLIA numbers at the claim level or on individual service lines.

Claim-level CLIA number

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.claimSupplementalInformation.cliaNumberREF-02 (Reference Identification) of Loop 2300 (Claim Information)

Line-level CLIA number

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.serviceLines[].serviceLineReferenceInformation.clinicalLaboratoryImprovementAmendmentNumberREF-02 (Reference Identification) of Loop 2400 (Service Line)

How the edit works

Each CLIA number is 10 characters with a fixed NNDNNNNNNN format: a two-digit state code, the literal D, then a seven-digit facility and check identifier.

If one or more CLIA numbers in a professional claim don’t follow this format, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid CLIA Number. A valid CLIA number must be 10 characters with position 1-2 being the numeric state code, position 3 must be 'D', and positions 4-10 must also be numeric. The submitted value, 45X2167451, is not valid. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>544*[DATE]*U*[AMOUNT]********Invalid CLIA Number. A valid CLIA number must be 10 characters with position 1-2 being the numeric state code, position 3 must be 'D', and positions 4-10 must also be numeric. The submitted value, 45X2167451, is not valid. Correct and resubmit.~

Claim edit: Invalid email format

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include an invalid email address.

How the edit works

A claim can include email addresses for different contacts, such as the submitter, billing provider, subscriber, or patient.

To be valid, an email address must start with a local name, followed by the @ symbol, followed by a domain. For example: johndoe@example.com. A value such as johndoe example.com is invalid; it’s missing the @ symbol.

When a claim contains an email address with an invalid format, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Email Address. A valid email address must include a local name, an \"@\" symbol, and a domain (name@example.com). Submitted email address for Submitter is invalid, johndoe example.com. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A7>127>41*[DATE]*U*[AMOUNT]********Invalid Email Address. A valid email address must include a local name, an "@" symbol, and a domain (name@example.com). Submitted email address for Submitter is invalid, johndoe example.com. Correct and resubmit.~

Claim edit: Missing revenue code

Stedi now rejects 837I institutional claims that are missing a revenue code on a service line.

What are revenue codes?

Revenue codes are standardized 4-digit codes that hospitals and other care facilities use to group charges into billable categories, such as the type of room, service, or supply billed. Example revenue codes include:

  • 0450 – Emergency Room

  • 0360 – Operating Room Services

  • 0300 – Laboratory

Revenue code

Claim typeJSON API fieldX12 element
837I institutionalserviceLines[].institutionalService.serviceLineRevenueCodeSV2-01 (Revenue Code) of Loop 2400 (Service Line)

How the edit works

Every service line on an institutional claim must report a revenue code. Payers use the revenue code to classify the service line, price the claim, and validate the services billed. If a service line is missing a revenue code, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Missing Revenue Code. A revenue code is required for each service line on institutional claims. Line 1 is missing a revenue code. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A6>455*[DATE]*U*[AMOUNT]********Missing Revenue Code. A revenue code is required for each service line on institutional claims. Line 1 is missing a revenue code. Correct and resubmit.~

Related claim edits

Stedi has another edit that validates the format of a revenue code. See Invalid revenue code.

Claim edit: Social Security Number with an unassigned area number

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that contain a Social Security Number (SSN) with an unassigned area number.

How the edit works

A claim can include a Social Security Number (SSN) for the billing provider, subscriber, patient, or other subscriber.

The first three digits of an SSN are the area number. The Social Security Administration (SSA) never issues an SSN whose area number is 000, 666, or in the 900-999 range, which is reserved for IRS Individual Taxpayer Identification Numbers (ITINs).

An SSN with one of these area numbers can't be valid, so it won't match any record at the payer. If a claim includes an SSN with an unassigned area number, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Social Security Number (SSN). The submitted SSN for Subscriber, 900123456, has an unassigned area number. The first 3 digits cannot be 000, 666, or in the 900-999 range. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A7>148>HK*[DATE]*U*[AMOUNT]********Invalid Social Security Number (SSN). The submitted SSN for Subscriber, 900123456, has an unassigned area number. The first 3 digits cannot be 000, 666, or in the 900-999 range. Correct and resubmit.~

Claim edit: Symptom onset date matches a service date

Stedi now rejects 837P professional claims where the symptom onset date matches a service date.

How the edit works

In a professional claim, the onset of current illness or symptom date, also called the symptom onset date, is when the patient first experienced symptoms of the illness or condition being treated. This date helps payers establish a clinical timeline to support coverage determinations and medical necessity reviews.

The symptom onset date is situational. Submitters only report it when it's relevant to a service line in the claim. It should differ from any service dates on the claim. If the symptom onset date matches a service date, omit it.

Symptom onset date

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.claimDateInformation.symptomDateDTP-03 (Date Time Period) of Loop 2300 (Claim Information)

X12 standards state that the symptom onset date must differ from the date of service, also called the service date, for any service line in a claim.

Service date

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.serviceLines[].serviceDateDTP-03 (Date Time Period) of Loop 2400 (Service Line)

If the symptom onset date matches a service date – or falls within a service date range – the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Onset of Current Illness date. The onset of illness/symptom date must be different from the service date, 20240301. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>397*[DATE]*U*[AMOUNT]******A7>187**Invalid Onset of Current Illness date. The onset of illness/symptom date must be different from the service date, 20240301. Correct and resubmit.~

Resolution tip

When the symptom onset date is the same as a service date in a claim, omit it and report only the service date.

Claim edit: Duplicate condition codes in institutional claims

Stedi now rejects 837I institutional claims that include the same condition code more than once within a single condition code group.

How the edit works

In institutional claims, condition codes report situations that can affect how a payer adjudicates – or determines how to pay – a claim.

For example, condition code 02 means the condition is employment-related. Code 17 means the patient is homeless. Condition codes are defined by the National Uniform Billing Committee (NUBC).

A claim can contain up to two groups of condition codes. Each group can contain up to 12 codes.

Condition code

Claim typeJSON API fieldX12 element
837I institutionalclaimInformation.conditionCodesList[][].conditionCodeHI-02 (Condition Code) of Loop 2300 (Claim Information), where HI-01 is BG (Condition)

The NUBC states that each condition code must be unique within a single group. If a claim includes the same condition code more than once within a single group, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Condition Code(s). If submitting multiple condition codes, each code must be unique. The submitted condition code(s) are submitted more than once, 17. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>460*[DATE]*U*[AMOUNT]******A7>732**Invalid Condition Code(s). If submitting multiple condition codes, each code must be unique. The submitted condition code(s) are submitted more than once, 17. Correct and resubmit.~

Claim edit: Duplicate occurrence codes in institutional claims

Stedi now rejects 837I institutional claims that include the same occurrence code more than once within a single occurrence code group.

How the edit works

In institutional claims, occurrence codes report significant events in a patient's care. These codes can affect how much a payer will approve or pay for a claim or service.

For example, occurrence code 11 reports the onset of symptoms or illness. Code 42 reports the date of discharge. Occurrence codes are defined by the National Uniform Billing Committee (NUBC).

A claim can contain up to two groups of occurrence codes. Each group can contain up to 12 codes.

Occurrence code

Claim typeJSON API fieldX12 element
837I institutionalclaimInformation.occurrenceInformationList[][].occurrenceSpanCodeHI-02 (Occurrence Code) of Loop 2300 (Claim Information), where HI-01 is BH (Occurrence)

The NUBC states that each occurrence code must be unique within a single group. If a claim includes the same occurrence code more than once within a single group, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Occurrence Code(s). If submitting multiple occurrence codes, each code must be unique. The submitted occurrence code(s) are submitted more than once, 45. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>719*[DATE]*U*[AMOUNT]******A7>732**Invalid Occurrence Code(s). If submitting multiple occurrence codes, each code must be unique. The submitted occurrence code(s) are submitted more than once, 45. Correct and resubmit.~

Related claim edits

Stedi has another edit for duplicate occurrence span codes. Occurrence codes report a single event on a specific date. Occurrence span codes report a condition that applied over a range of dates. See Duplicate occurrence span codes in institutional claims.

Claim edit: Invalid admission type code

Stedi now rejects 837I institutional claims with an invalid admission type code.

How the edit works

In institutional inpatient claims, an admission type code indicates the general nature of a patient’s admission. It provides context about the urgency or purpose of the hospital admission.

Admission type code

Claim typeJSON API fieldX12 element
837I institutionalclaimInformation.claimCodeInformation.admissionTypeCodeCL1-01 (Admission Type Code) of Loop 2300 (Claim Information)

Admission type codes are defined by the National Uniform Billing Committee (NUBC). Valid admission type codes are:

  • 1 – Emergency

  • 2 – Urgent

  • 3 – Elective

  • 4 – Newborn

  • 5 – Trauma Center

  • 9 – Information Not Available

If an institutional claim includes an invalid admission type code, such as 6 or 0, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Admission Type Code. The submitted admission type code, 0 is not a recognized value. The value must be valid per NUBC Priority (Type) of Admission or Visit Codes. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>231*[DATE]*U*[AMOUNT]********Invalid Admission Type Code. The submitted admission type code, 0 is not a recognized value. The value must be valid per NUBC Priority (Type) of Admission or Visit Codes. Correct and resubmit.~

Claim edit: Invalid date range

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims where the start of a date range is later than the end date.

Date formats

X12 standards require that every date on a claim, such as the service date or admission date, use one of two formats:

  • Single date – Eight digits in CCYYMMDD format. Example: 20260515.

  • Date range – Two dates in CCYYMMDD-CCYYMMDD format. Example: 20260515-20260516.

In raw X12, each date has a related qualifier indicating the format: D8 for single dates and RD8 for date ranges.

Date ranges in the JSON API

In Stedi's JSON Claim Submission API endpoints, most dates that support ranges use paired fields. For example, in the JSON Professional Claim Submission endpoint, you can provide a date of service either as:

Some dates accept a range in a single field. For example, in the JSON Dental Claim Submission endpoint, the claim-level serviceDate field accepts either a single date or a date range.

How the edit works

For date ranges in a claim, the start date should never fall after the end date. If it does, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid Service date range. The start date (20250708) cannot be later than the end date (20250608). Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A7>187*[DATE]*U*[AMOUNT]********Invalid Service date range. The start date (20250708) cannot be later than the end date (20250608). Correct and resubmit.~

Claim edit: Missing claim-level place of service code

Stedi now rejects 837P professional and 837D dental claims that are missing a claim-level place of service code.

How the edit works

In a healthcare claim, a place of service code tells the payer where a service was delivered, such as an office or inpatient facility. Place of service codes can have a significant effect on how much a payer will approve or pay for a claim or service.

X12 standards require that 837P professional and 837D dental claims include a place of service code at the claim level. Place of service codes can also be specified at the service line level but should only be included if they differ from the claim-level code.

Claim-level place of service code

Claim typeJSON API fieldX12 element
837P professionalclaimInformation.placeOfServiceCodeCLM-05-01 (Place of Service Code) of Loop 2300 (Claim Information)
837D dentalclaimInformation.placeOfServiceCodeCLM-05-01 (Place of Service Code) of Loop 2300 (Claim Information)

If a professional or dental claim is missing a claim-level place of service code, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Missing Place of Service code. A place of service code is required for this claim. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, and error message.

STC*A6>249*[DATE]*U*[AMOUNT]********Missing Place of Service code. A place of service code is required for this claim. Correct and resubmit.~

Claim edit: ZIP or postal code not allowed outside the U.S. and Canada

Stedi now rejects 837P professional, 837D dental, and 837I institutional claims that include a ZIP or postal code in an address outside the U.S. or Canada.

How the edit works

X12 states that ZIP and postal code fields are specific to the U.S. and Canada. If an address in a claim has a country code other than US or CA, it should not contain a ZIP or postal code. If it does, the payer may reject the claim.

This edit catches the issue before the claim reaches the payer. It prevents payer rejections, which take longer to resolve and delay payment for the provider.

Rejection errors

If you submit a claim using Stedi's Claim Submission API endpoints and the claim fails the edit, you'll get back an error response in real time. The response includes details in the errors array.

{
  "errors": [
    {
      "code": "33",
      "description": "Invalid postal code usage. A ZIP Code must only be submitted when the country is US or CA. The submitted address for Subscriber includes a ZIP Code with country code FR. Correct and resubmit.",
      "followupAction": "Please Correct and Resubmit"
    }
  ]
}

If you submit a claim using SFTP and the claim fails the edit, Stedi will reject the claim with a 277CA claim acknowledgment. The acknowledgment will include a related claim status category code, claim status code, entity identifier code, and error message.

STC*A7>500>HK*[DATE]*U*[AMOUNT]******A8>680>HK**Invalid postal code usage. A ZIP Code must only be submitted when the country is US or CA. The submitted address for Subscriber includes a ZIP Code with country code FR. Correct and resubmit.~