Errors and resolutions

A list of potential errors and possible resolutions when submitting 270 eligibility checks.

​

Stedi payer errors

The following Stedi payer error resulted from an unrecognized payer ID:

{
    "controlNumber": "123456789",
    "tradingPartnerServiceId": "FOO",
    "errors": [
        {
            "code": "33",
            "description": "Payer FOO is not configured. Please check our published payer list or contact Stedi support to resolve.",
            "followupAction": "C"
        }
    ],
    "status": "ERROR"
}

​

Validation errors

Stedi validates the structure of your eligibility request and will not submit your request to the payer if it is missing required fields or if the data is not formatted correctly. The following Stedi validation error resulted from a missing provider object:

{
  "controlNumber": "123456789",
  "tradingPartnerServiceId": "CIGNA",
  "errors": [
    {
      "code": "33",
      "description": "Missing required field: provider",
      "followupAction": "C"
    }
  ],
  "status": "ERROR"
}

​

Payer AAA errors

When a payer rejects your eligibility check, the 271 response contains one or more AAA Request Validation segments that specify the reasons for the rejection and any recommended follow-up actions. Stedi includes this information in the aaaErrors object in the response JSON.

Common causes for AAA errors include:

• Missing or incorrect information for the subscriber, dependent, provider, or payer. In this case, you should correct any errors before resubmitting.
• Issues with payer enrollment. Many of these issues require that the provider contact the payer directly to resolve, due to PHI/HIPAA guidelines.
• The payer’s system is down or experiencing issues. In this case, the payer may not have actually validated the data in your request. If you receive these types of errors, you should wait a few minutes and resend the request again.

Each error contains a code field that corresponds to a followupAction:

• C - Please correct and resubmit
• N - Resubmission not allowed
• P - Please resubmit original transaction
• R - Resubmission allowed
• S - Do not resubmit; Inquire initiated to a third party
• Y - Do not resubmit; We will hold your request and respond again shortly

AAA errors can be present at multiple different levels in the response, depending on the type. The following example shows an error at the subscriber level (subscriber.aaaErrors):

    "subscriber": {
        "memberId": "123456789",
        "firstName": "JANE",
        "lastName": "DOE",
        "entityIdentifier": "Insured or Subscriber",
        "entityType": "Person",
        "dateOfBirth": "190001103",
        "aaaErrors": [
            {
                "field": "AAA",
                "code": "75",
                "description": "Subscriber/Insured Not Found",
                "followupAction": "Please Correct and Resubmit",
                "location": "Loop 2100C",
                "possibleResolutions": "- Subscriber was not found."
            }
        ]
    }