# EDI X12 276 Health Care Claim Status Request Parser
> Extract claim status query parameters, provider identifiers, and patient encounter lookups from ANSI X12 276 streams.

- **Canonical URL:** https://stanzaapi.com/tools/x12-parser/transaction/276-claim-status-inquiry
- **Governing Standard:** ANSI ASC X12 Standards (005010) (Accredited Standards Committee X12 / HIPAA 5010)
- **Latency:** <2ms Edge
- **Privacy:** In-memory execution only (zero data stored or logged)

## Technical Overview & Governing Rules
The ANSI X12 276 transaction is used by healthcare providers and billing clearinghouses to verify the processing status of previously submitted claims.

Extracts Loop 2200D (Claim Status Tracking) with Claim Submitter Identifier, service dates (DTP), and total billed charge amounts (AMT).

## Specification Matrix
| Segment | Description | Key Elements Extracted | Usage |
| --- | --- | --- | --- |
| TRN | Claim Identification Trace | TRN01 (1=Current), TRN02 (Claim Submitter Trace #) | Tracking key |
| REF | Payer Claim Control Number | REF01 (1K=Payer Claim #), REF02 (Assigned ID) | Payer matching |
| AMT | Monetary Amount | AMT01 (T3=Total Claim Charge Amount), AMT02 (Charge) | Charge amount filter |
| DTP | Date of Service | DTP01 (472=Service Date), DTP03 (Date Range) | Encounter date query |

## Standard JSON Response Model
```json
{
  "transactionSet": "276",
  "inquiryId": "TRK-99128",
  "payerId": "PAYER01",
  "providerNpi": "1992837465",
  "claimInquiry": {
    "patientAccountNumber": "CLM001",
    "serviceDate": "20260810",
    "billedAmount": 150
  }
}
```

## Frequently Asked Questions & Edge Cases
### Q: Can this match 276 inquiries with corresponding 277 responses?
**A:** Yes, tracking numbers in TRN02 enable clean automated re-association.