Claim edit: Symptom onset date matches a service date

Claim edits

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 type

JSON API field

X12 element

837P professional

claimInformation.claimDateInformation.symptomDate

DTP-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 type

JSON API field

X12 element

837P professional

claimInformation.serviceLines[].serviceDate

DTP-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"
    }
  ]
}
{
  "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"
    }
  ]
}
{
  "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
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
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.

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 type

JSON API field

X12 element

837P professional

claimInformation.claimDateInformation.symptomDate

DTP-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 type

JSON API field

X12 element

837P professional

claimInformation.serviceLines[].serviceDate

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

Get started with Stedi

Get started with Stedi

Start free with a sandbox account. Upgrade to production when you're ready. There are no monthly minimums or setup fees. You only pay for the transactions you use. See our pricing.

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Get updates on what’s new at Stedi

Backed by

Stedi and the S design mark are registered trademarks 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.

Get updates on what’s new at Stedi

Backed by

Stedi and the S design mark are registered trademarks 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.

Get updates on what’s new at Stedi

Backed by

Stedi and the S design mark are registered trademarks 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.