Healthcare EDI ANSI X12 Parser API
High-performance edge parser converting 837P, 835, and 270/271 EDI to clean JSON
The Healthcare EDI ANSI X12 Parser API transforms complex, delimited HIPAA EDI transactions into strongly-typed, developer-friendly JSON in milliseconds. Built specifically for telehealth platforms, EHR integrations, medical billing clearinghouses, and healthcare SaaS applications.
Traditional EDI processing involves brittle desktop software, bloated Java runtimes, or exorbitant enterprise SaaS retainers. This API runs entirely at the Cloudflare edge: linear O(N) stream tokenization autodetects custom delimiters from the ISA header, traverses hierarchical loops (Billing Provider, Subscriber, Patient, Claim, Service Lines, Adjustments), and delivers validated JSON in sub-15ms latency.
Pure compute with zero external subrequests: your sensitive healthcare claim payloads are processed instantaneously in memory without storage or third-party leakage, ensuring strict data protection and zero cold-start latency.
Features
- Full support for 837P (Professional Health Care Claims)
- Full support for 835 (Electronic Remittance Advice & Claim Payments)
- Full support for 270/271 (Eligibility & Benefit Inquiry and Response)
- Automatic delimiter detection from 106-character ISA headers (element, component, segment separators)
- Interchange and Functional Group envelope validation (control number & count integrity)
- Sub-15ms edge execution across 300+ global locations
- Pure compute: zero external network calls, deterministic and ReDoS-safe
Endpoints
| Method | Path | Description | Example |
|---|---|---|---|
POST | /api/v1/x12/parse | Parse raw ANSI X12 text (837P, 835, 270, 271) into structured JSON | /api/v1/x12/parse |
POST | /api/v1/x12/validate | Validate ANSI X12 interchange envelopes and segment loop integrity | /api/v1/x12/validate |
GET | /health | Service health and supported transaction sets | /health |
FAQ
Which ANSI X12 transaction sets are supported?
The parser natively extracts complete hierarchical data for 837P (Health Care Claim: Professional), 835 (Health Care Claim Payment / Advice), and 270/271 (Health Care Eligibility / Benefit Inquiry & Response). Any other transaction set is safely tokenized into structured generic X12 segment trees.
How does delimiter detection work?
ANSI X12 defines delimiters dynamically within the first 106 characters of the ISA header. The parser inspects ISA[3] for element separator, ISA[104] for component separator, ISA[105] for segment terminator, and ISA[82] for repetition separator.
Does the parser retain or store any PHI/EDI data?
No. Processing is completely stateless pure compute. Payloads are parsed in-memory at the Cloudflare edge worker and streamed back immediately. Zero data is persisted to disk, databases, or logs. Note that zero-retention is an architecture property, not a HIPAA compliance certification.
Is this API HIPAA compliant? Can I submit real patient data?
Not yet. This parser handles HIPAA-standard X12 5010 transaction formats, but a formal HIPAA compliance program (security risk assessment, BAA execution, third-party audit) is still in progress. Until formally announced, submit only synthetic, test, or fully de-identified payloads — never real PHI or PII.
What is the maximum payload size supported?
The API supports raw EDI payloads up to 512KB per request, which comfortably fits large multi-claim 837 files and multi-page 835 remittance batches.