# EDI X12 270 Eligibility Inquiry Parser & Validator
> Parse inbound real-time and batch HIPAA 270 eligibility check requests into structured JSON payloads in under 3ms.

- **Canonical URL:** https://stanzaapi.com/tools/x12-parser/transaction/270-eligibility-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 270 transaction is used by healthcare providers, EHRs, and practice management tools to query payer databases for patient insurance active status and benefit coverage.

Traverses Loop 2100A (Information Source), Loop 2100B (Information Receiver / Provider), Loop 2100C (Subscriber), and Loop 2110C (Eligibility Request).

Extracts EQ segments containing Service Type Codes (e.g. 30 = Health Benefit Plan Coverage, 1 = Medical Care, 33 = Chiropractic, 88 = Pharmacy).

## Specification Matrix
| Segment | Description | Key Elements Extracted | Usage |
| --- | --- | --- | --- |
| NM1 | Information Source / Receiver / Subscriber | NM101 (PR=Payer, 1P=Provider, IL=Insured), NM109 (Member ID) | Party routing |
| DMG | Demographic Information | DMG02 (DOB: YYYYMMDD), DMG03 (Gender: M/F) | Patient verification |
| DTP | Date of Service | DTP01 (291=Plan, 472=Service), DTP03 (Date) | Coverage active check |
| EQ | Eligibility or Benefit Inquiry | EQ01 (Service Type Code: 30, 1, 88, AL) | Requested benefit categories |

## Standard JSON Response Model
```json
{
  "transactionSet": "270",
  "payer": {
    "id": "PAYER99",
    "name": "AETNA HEALTH"
  },
  "provider": {
    "npi": "1882993049",
    "name": "CITY HEALTH CLINIC"
  },
  "subscriber": {
    "memberId": "AET9823412",
    "firstName": "ROBERT",
    "lastName": "DAVIS",
    "dateOfBirth": "19840312"
  },
  "serviceTypeCodes": [
    "30",
    "1"
  ]
}
```

## Frequently Asked Questions & Edge Cases
### Q: Can this validate both 270 batch and real-time streams?
**A:** Yes. The parser supports both single-encounter real-time 270 transactions and multi-patient batch inquiry files.