POST
/
change
/
medicalnetwork
/
claimstatus
/
v2
/
raw-x12

This endpoint sends 276 Claim Status requests to payers in raw X12 EDI format. This is ideal if you have an existing system that generates X12 EDI files and you want to send them through Stedi’s API.

  • Call this endpoint with a payload in 276 X12 EDI format.
  • Stedi validates the EDI and sends the status request to the payer.
  • The endpoint returns a synchronous response from the payer in JSON format. The response contains information about the referenced claim and its current status.

This endpoint is a direct replacement for the Change Healthcare Claim Status x12 API.

Timeout

Requests to payers typically time out at 1 minute, though Stedi’s API can keep connections open longer than that if needed.

Payer limitations

Payers generally only allow a provider organization to check the status of the claims they submitted. This means that you likely won’t be able to check the status of a claim submitted by a different provider organization or by the patient themselves, even if you have all of the details about the claim. Payers impose these access controls to protect plan member privacy and confidential commercial data.

Payers also often archive claims older than 18 months, but this varies by payer. If you try to check the status of a claim from several years ago, the payer may return an error even if the information you submit matches a real historical claim.

Finally, we recommend keeping the dates of service range to 30 days or less. Some payers may reject requests with a date range that is too wide.

Authorizations

Authorization
string
headerrequired

API key authentication via the 'Authorization' header

Body

application/json
x12
string
required

Response

200 - application/json
controlNumber
string

The control number the the payer provided in the claim status response. This is used to identify the transaction.

tradingPartnerServiceId
string

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.

payer
object

Information about the payer listed in the referenced claim.

providers
object[]

Information about the provider making the claim status request.

subscriber
object

Information about the subscriber listed in the referenced claim.

dependent
object

Information about the dependent listed in the referenced claim.

claims
object[]

The status information for the claim referenced in the original claim status request.

reassociationKey
string

The control number for the transaction.

errorResponse
object
status
string

The status of the entire claim.

transactionSetAcknowledgement
string

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.

implementationTransactionSetSyntaxError
string

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.

x12
string

The raw X12 response from the payer.

meta
object

Metadata about the response.

Was this page helpful?