Healthcare EDI ANSI X12 Parser API
Transform raw HIPAA ANSI X12 EDI streams into strongly-typed hierarchical JSON with automated delimiter autodetection, loop traversal, and syntax validation.
NOT YET HIPAA COMPLIANT — DO NOT SUBMIT REAL PHI/PII. This API parses HIPAA-standard X12 5010 transaction formats, but our formal HIPAA compliance program (security risk assessment, BAA execution, third-party audit) is in progress. Until formally announced, use synthetic, test, or fully de-identified payloads only.
⚡ Live Pure-Compute Playground
Test deterministic edge parsing with sub-2ms execution across 330+ Cloudflare V8 edge locations. Zero persistent storage, zero cold-starts, pure function $f(x)=y$.
Key Capabilities & Performance Architecture
- ✓ Native parsing for 837P, 837I, 835, 270, 271, 834, 850, 810, 276, and 277 EDI transaction sets
- ✓ Automatic ISA 106-character delimiter autodetection (element, component, segment separators)
- ✓ Full hierarchical loop traversal (Billing Provider, Subscriber, Patient, Claim, Service Line, Adjustments)
- ✓ Deterministic pure compute on Cloudflare Workers edge runtime (<5ms latency, zero cold-starts)
- ✓ ReDoS-safe linear O(N) stream tokenization with strict 512KB payload capacity
Transaction Set Specifications (10 Specifications)
Explore full structural breakdowns, checksum logic, and field schemas for every supported format.
EDI X12 837P Professional Health Care Claim Parser & Validator
Instant sub-5ms parsing of ANSI X12 837P (5010X222A1) professional medical claims into structured JSON with full Hierarchical Loop (HL) resolution.
View Specification →EDI X12 837I Institutional Health Care Claim Parser & Validator
Automated institutional claim parser for hospital inpatient and outpatient EDI 837I files with UB-04 revenue code mapping.
View Specification →ANSI 835 EDI Remittance Advice (ERA) Parser & Payment Engine
High-speed ANSI 835 ERA parser extracting payer payments, deductible/coinsurance CAS adjustments, CARC/RARC codes, and PLB provider adjustments.
View Specification →EDI X12 270 Health Care Eligibility & Benefit Inquiry Parser
Parse inbound real-time and batch HIPAA 270 eligibility check requests into structured JSON payloads in under 3ms.
View Specification →EDI X12 271 Health Care Eligibility & Benefit Response Parser
Extract copays, remaining deductibles, out-of-pocket maximums, and in-network coverage terms from 271 EDI response streams.
View Specification →EDI X12 834 Benefit Enrollment and Maintenance Parser
Process employer benefit enrollments, terminations, and demographic modifications with high-speed 834 EDI to JSON parsing.
View Specification →EDI X12 850 Purchase Order Parser & JSON Converter
B2B supply chain EDI parser converting retail and enterprise ANSI X12 850 purchase orders into structured JSON.
View Specification →EDI X12 810 Electronic Commercial Invoice Parser
High-performance 810 commercial invoice parser extracting line item charges, discounts, taxes, and payment terms into JSON.
View Specification →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.
View Specification →EDI X12 277 Health Care Claim Status Notification Parser
Parse payer 277 claim status responses, STC segment claim adjudication status codes, and pending payment dates in JSON.
View Specification →API Endpoints & Request Signatures
| Method | Path | Description |
|---|---|---|
POST |
/api/v1/x12/parse |
Parse raw ANSI X12 text (837P, 835, 270, 271) into structured JSON |
POST |
/api/v1/x12/validate |
Validate ANSI X12 interchange envelopes and segment counts |
Sample Response JSON Payload
All endpoints deliver strongly-typed envelopes with deterministic parsing and performance metrics.
{
"success": true,
"data": {
"transactionType": "837",
"standard": "005010X222A1",
"interchangeControlNumber": "000000001",
"delimiters": {
"element": "*",
"component": ":",
"segment": "~"
},
"claims": [
{
"claimId": "CLM001",
"totalClaimChargeAmount": 150,
"billingProvider": {
"name": "DR DOE CLINIC",
"npi": "1992837465"
},
"patient": {
"firstName": "JANE",
"lastName": "SMITH",
"memberId": "W123456780"
},
"serviceLines": [
{
"line": 1,
"procedureCode": "99213",
"chargeAmount": 150,
"units": 1
}
]
}
]
},
"meta": {
"latency_ms": 1.84,
"version": "1.0.0"
}
}Multi-Language Integration Code
Copy and paste ready-to-run snippets with your direct API credentials:
curl --request POST \
--url "https://healthcare-edi-ansi-x12-parser-837p-835-271.stanzaapi.com/api/v1/x12/parse" \
--header "Content-Type: application/json" \
--header "x-api-key: YOUR_API_KEY" \
--data '{
"raw": "ISA*00* *00* *ZZ*SUBMITTER1 *ZZ*RECEIVER01 *260830*1200*^*00501*000000001*0*P*:~GS*HC*SENDER*RECEIVER*20260830*1200*1*X*005010X222A1~ST*837*0001*005010X222A1~BHT*0019*00*CLAIM001*20260830*1200*CH~NM1*41*2*DR DOE CLINIC*****46*1234567890~PER*IC*SUPPORT*TE*8005551212~HL*1**20*1~NM1*85*2*DR DOE CLINIC*****XX*1992837465~HL*2*1*22*0~NM1*IL*1*SMITH*JANE****MI*W123456780~CLM*CLM001*150.00***11::1*Y*A*Y*Y~LX*1~SV1*HC:99213*150.00*UN*1***1~SE*11*0001~GE*1*1~IEA*1*000000001~"
}'const response = await fetch("https://healthcare-edi-ansi-x12-parser-837p-835-271.stanzaapi.com/api/v1/x12/parse", {
method: "POST",
headers: {
"Content-Type": "application/json",
"x-api-key": process.env.API_KEY || "YOUR_API_KEY"
},
body: JSON.stringify({
"raw": "ISA*00* *00* *ZZ*SUBMITTER1 *ZZ*RECEIVER01 *260830*1200*^*00501*000000001*0*P*:~GS*HC*SENDER*RECEIVER*20260830*1200*1*X*005010X222A1~ST*837*0001*005010X222A1~BHT*0019*00*CLAIM001*20260830*1200*CH~NM1*41*2*DR DOE CLINIC*****46*1234567890~PER*IC*SUPPORT*TE*8005551212~HL*1**20*1~NM1*85*2*DR DOE CLINIC*****XX*1992837465~HL*2*1*22*0~NM1*IL*1*SMITH*JANE****MI*W123456780~CLM*CLM001*150.00***11::1*Y*A*Y*Y~LX*1~SV1*HC:99213*150.00*UN*1***1~SE*11*0001~GE*1*1~IEA*1*000000001~"
})
});
const data = await response.json();
console.log(data);import requests
import json
url = "https://healthcare-edi-ansi-x12-parser-837p-835-271.stanzaapi.com/api/v1/x12/parse"
headers = {
"Content-Type": "application/json",
"x-api-key": "YOUR_API_KEY"
}
payload = {
"raw": "ISA*00* *00* *ZZ*SUBMITTER1 *ZZ*RECEIVER01 *260830*1200*^*00501*000000001*0*P*:~GS*HC*SENDER*RECEIVER*20260830*1200*1*X*005010X222A1~ST*837*0001*005010X222A1~BHT*0019*00*CLAIM001*20260830*1200*CH~NM1*41*2*DR DOE CLINIC*****46*1234567890~PER*IC*SUPPORT*TE*8005551212~HL*1**20*1~NM1*85*2*DR DOE CLINIC*****XX*1992837465~HL*2*1*22*0~NM1*IL*1*SMITH*JANE****MI*W123456780~CLM*CLM001*150.00***11::1*Y*A*Y*Y~LX*1~SV1*HC:99213*150.00*UN*1***1~SE*11*0001~GE*1*1~IEA*1*000000001~"
}
response = requests.post(url, json=payload, headers=headers)
print(response.json())package main
import (
"bytes"
"fmt"
"io"
"net/http"
"os"
)
func main() {
url := "https://healthcare-edi-ansi-x12-parser-837p-835-271.stanzaapi.com/api/v1/x12/parse"
payload := []byte(`{"raw":"ISA*00* *00* *ZZ*SUBMITTER1 *ZZ*RECEIVER01 *260830*1200*^*00501*000000001*0*P*:~GS*HC*SENDER*RECEIVER*20260830*1200*1*X*005010X222A1~ST*837*0001*005010X222A1~BHT*0019*00*CLAIM001*20260830*1200*CH~NM1*41*2*DR DOE CLINIC*****46*1234567890~PER*IC*SUPPORT*TE*8005551212~HL*1**20*1~NM1*85*2*DR DOE CLINIC*****XX*1992837465~HL*2*1*22*0~NM1*IL*1*SMITH*JANE****MI*W123456780~CLM*CLM001*150.00***11::1*Y*A*Y*Y~LX*1~SV1*HC:99213*150.00*UN*1***1~SE*11*0001~GE*1*1~IEA*1*000000001~"}`)
req, _ := http.NewRequest("POST", url, bytes.NewBuffer(payload))
req.Header.Add("Content-Type", "application/json")
req.Header.Add("x-api-key", os.Getenv("API_KEY"))
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}Frequently Asked Questions
The API features dedicated high-speed parsers for 837P (Professional Claims), 837I (Institutional Claims), 835 (Electronic Remittance Advice / Payments), 270/271 (Eligibility Inquiry and Response), 834 (Benefit Enrollment), 850 (Purchase Orders), 810 (Invoices), and 276/277 (Claim Status Inquiry & Response).
ANSI X12 defines separators dynamically inside the 106-character ISA segment. Our parser inspects ISA[3] for the data element separator, ISA[104] for the component element separator, ISA[105] for the segment terminator, and ISA[82] for repetition separators.
Zero PHI or EDI data is ever stored. All processing occurs in-memory at Cloudflare Workers edge nodes and streams back directly to your application. Note: zero-retention is an architecture property, not a HIPAA compliance certification — see the compliance status notice above.
Not yet. The parser handles HIPAA-standard X12 5010 formats (837P, 837I, 835, 270/271, 834) and is engineered with data-minimization and zero-retention principles, but our formal HIPAA compliance program — security risk assessment, Business Associate Agreement (BAA) execution, and third-party audit — is still in progress. Until it is formally announced, submit only synthetic, test, or fully de-identified payloads. Never send real PHI or PII through the endpoint.
Requests accept up to 512KB of raw EDI text per request, accommodating multi-claim 837 batches and large 835 electronic remittance files.