Real-time claim status

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

Changed on

Submit a 276/277 real-time claim status check in raw X12 EDI format

Request

  • Base URL
    https://healthcare.us.stedi.com/2024-04-01
  • URL
    https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/claimstatus/v2/raw-x12
  • Auth
    API key in header Authorization

Request body

x12string required

Response

ClaimStatusRawX12 200 response

controlNumberstring

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

idstring

A globally unique identifier for this claim status check across all Stedi accounts. It's formatted as csc_<uuid>. For example: csc_550e8400-e29b-41d4-a716-446655440000. You can use this ID to track this claim status check and to construct deep links to claim status checks in the Stedi portal.

implementationTransactionSetSyntaxErrorstring

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.

reassociationKeystring

The control number for the transaction.

statusstring

The status of the entire claim.

tradingPartnerServiceIdstring

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.

transactionSetAcknowledgementstring

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.

x12string

The raw X12 EDI response, which is either a 277 Status Request Response or a 999 Implementation Acknowledgment. A 999 indicates that the request data failed validation. Common failure reasons are missing required segments and invalid values.

Changes

    • info

      added the optional property to the response with the status

    • info

      added the optional property / to the response with the status

    • info

      added the optional property to the response with the status