# EDI that tells you what broke.
Canonical: https://siua.io/labs/edi/
Playground: https://siua.io/labs/edi/playground/
If you have ever lost half a day to one broken segment, this is for you. We built the parser we wanted: fast, readable, and portable.
Status: Live today: 834 and 837 parsing, structured output, inspector tooling, and readable diagnostics. More transaction types are still coming.
## Overview
I've spent more hours than I want to admit staring at raw X12 trying to figure out why a transaction failed. The error says "parse error." Thanks. The segment dump is six thousand characters of pipe-delimited nothing. And the tools that are supposed to help — they're ancient desktop apps, or so welded to one stack that moving them anywhere is a rewrite.

We hit this building our own claims and enrollment products. We needed something fast. Something that could tell us, in plain language, what went wrong and where. Something we could drop into Node or Python or the browser without rebuilding it each time. Nothing we found did all of that. Most didn't do any of it well.

So we started building it. Healthcare first — that's where we needed it — but the parser doesn't know or care. It handles X12. Any transaction set. We're sharing it here because if you've been fighting the same fight, you shouldn't have to start from scratch.
## Who It Is For
- Product teams building on EDI data
- Integration and claims engineers
- Technical leadership evaluating parsers
- Anyone tired of legacy EDI tools
## How It Works
- Feed it a raw X12 file: The parser auto-detects the transaction type and processes it immediately — no configuration, no schema files to manage.
- Get structured output: Clean hierarchical JSON, XML, or FHIR — nested by loop structure and ready for your systems.
- Understand what's broken: Every validation issue includes the exact segment, byte offset, and a clear explanation. No more guessing.
- Deploy it your way: Native bindings for Node, Python, Java, .NET, C++, PHP, Swift — or run it in the browser via WebAssembly.
## Product Notes

### Try it in 30 seconds
Getting started
The fastest way to see EDI Core is the browser playground — no install, no signup. Paste a file or load a sample and see the parsed output immediately.

- Load a sample 834 or 837 transaction to see the parser in action
- Switch between segment view, JSON output, and diagnostics
- Click any segment to drill into elements, data types, and byte offsets

### Supported transactions
What it parses
Currently handling the two most common healthcare X12 transaction types, with more in progress.

- 834 — Benefit enrollment and maintenance
- 837 — Healthcare claims (professional, institutional, dental)
- Auto-detection of transaction type from file headers
- Full loop structure validation and segment cardinality

### What comes out the other side
Output formats
The parser outputs structured data in the format your systems actually need.

- Hierarchical JSON — nested by loop structure, ready for APIs and databases
- XML — for systems that expect XML-based interchange
- FHIR R4 bundles — for healthcare interoperability workflows
- Structured diagnostics — validation results as data you can pipe into alerting

### Runs in your stack
Integration
Native bindings for every major language. Runs in-process — no HTTP overhead, no subprocess, no CLI wrapper.

- Node / TypeScript
- Python
- Java
- .NET
- C++ / Swift
- PHP
- Browser (WebAssembly)

### Your data stays where you put it
Data safety
The browser playground runs entirely client-side. Production deployments run in your own infrastructure. No data is sent anywhere.

- Browser: all parsing happens locally via WebAssembly
- Production: deploy in your own cloud, on-prem, or embedded
- No data retention, no telemetry on parsed content
- PHI/PII detection coming as an additional safety layer
## Roadmap
- Parse 834 and 837 files accurately: done
- Structured output in JSON and XML: done
- Export to FHIR R4: done
- Human-readable validation diagnostics: done
- Use it from any language — Node, Python, Java, .NET, C++, PHP, and Swift: done
- Run it in the browser: done
- More transaction types — eligibility, claim status, remittance: in-progress
- Claims workflow tooling: in-progress
- Built-in PHI/PII detection: planned
- Synthetic test data generator: planned
The browser preview is live. If you want to use the parser in your own stack, email us. We will tell you where it is solid, where it is still moving, and whether it is actually a fit.