- Call this endpoint with a JSON payload.
- Stedi generates the X12 276 EDI transaction and sends it to the payer.
- The endpoint returns a synchronous 277 claim status response from the payer in JSON format. The response contains information about the claims matching the criteria you provided in the request and their current status.
Authorizations
A Stedi API Key for authentication.
Body
An integer used to identify the transaction. It does not need to be globally unique. It is returned in the response as controlNumber
.
9
This is the Payer ID. Visit the Payer Network for a complete list. You can send requests using the Primary Payer ID, the Stedi Payer ID, or any alias listed in the payer record.
2 - 80
Information about the billing and/or service providers related to the referenced claim. For each provider, you must set the providerType
and one of the following identifiers: npi
, taxId
, or etin
.
- When the providerType
= BillingProvider
, you must include the provider's etin
.
- When providerType
= ServiceProvider
, you must include the npi
if the provider has one. Otherwise, include the taxId
.
1 - 2147483647
elementsInformation about the subscriber listed in the referenced claim.
- You must set both the
dateOfBirth
andgender
properties when the subscriber is the patient unless the gender is unknown. Stedi determines that the subscriber is the patient when thedependent
object is not included in the request. - If either
dateOfBirth
orgender
is set, you must include both properties unless the gender is unknown.
This is the payer name, such as Cigna or Aetna.
Information about the dependent listed in the referenced claim. You must submit the dependent's firstName
, lastName
, dateOfBirth
, and gender
(if known). If the claim set the dependent's gender to U
for unknown, you should omit the gender
property.
Information about the referenced claim or claims for which you want to retrieve status information.
We recommend supplying a date range that is at least plus or minus 7 days from the date of the services listed in the claim, using the beginningDateOfService
and endDateOfService
properties. The payer may have stored a different date for the encounter than the one in your records, so providing a date range increases the likelihood that the payer will find a match.
1
Response
ClaimStatus 200 response
The control number the payer provided in the claim status response. This is used to identify the transaction.
An ID for the payer you identified in the original claim status request. This value may differ from the tradingPartnerServiceId
you submitted in the original request because it reflects the payer's internal concept of their ID, not necessarily the ID Stedi uses to route requests to this payer.
Information about the payer listed in the referenced claim.
Information about the billing and/or service providers related to the referenced claim.
Information about the subscriber listed in the referenced claim.
Information about the dependent listed in the referenced claim.
The status information for the claim referenced in the original claim status request.
The payer may return multiple claims in the response if they have more than one claim on file that matches the information you provided.
The control number for the transaction.
The status of the entire claim.
The acknowledgment code in the 999 Implementation Acknowledgment, an EDI file generated by the payer to acknowledge receipt of the claim status request. It indicates whether the claim status request was accepted or rejected due to errors in the EDI request syntax.
The syntax error code in the 999 Implementation Acknowledgment. It indicates the type of error (if present) in the EDI request syntax. Visit IK502
in the Implementation Acknowledgment specification for a complete list.
The raw X12 response from the payer.
Metadata about the response.