v0.3.0 Released — X12, HIPAA & EANCOM Support for TypeScript

[hello-ediflow]

After months of work, EDIFlow v0.3.0 is out — and it's the biggest release yet.

"Water doesn't fight obstacles. It flows." — Lao Tzu

EDIFlow is built on this principle: EDI data should move through systems naturally, adapt to any standard, and connect everything. The Way of Water.

We now support EDIFACT, X12, HIPAA and EANCOM — all in one TypeScript library with Clean Architecture, strict types, and zero config.

💧 Finds its way — intelligent parsing, adaptive error handling
🌊 Adapts to any form — EDIFACT, X12, HIPAA, EANCOM, more to come
💪 Powerful but gentle — enterprise-grade performance, developer-friendly API
🔄 Connects everything — one unified interface for all EDI standards

---

What's new in v0.3.0

🔷 X12 support — full public release
Parse, validate and build X12 transactions in TypeScript.
ISA/GS/ST/SE/GE/IEA envelope handling across two full versions:

Package	Version	Transaction Sets
@ediflow/x12-004010	X12 004010	293 transaction sets
@ediflow/x12-006040	X12 006040	319 transaction sets

850, 810, 856, 837, 835, 997, 820, 214, 204, 210 and hundreds more — all standards-compliant, no custom setup needed.

import { X12ServiceBuilder } from '@ediflow/x12';
import { x12_004010Repository } from '@ediflow/x12-004010';
// or: import { x12_006040Repository } from '@ediflow/x12-006040';

const service = new X12ServiceBuilder()
  .withRepository(x12_004010Repository)
  .build();

const result = await service.parse(rawX12String);
console.log(result.message.segments);

🏥 HIPAA X12 005010 — 14 transaction sets: 837P, 837I, 835, 270/271, 276/277, 834, 820, ...

🌍 EDIFACT — full coverage across 4 versions
All four EDIFACT versions are supported with complete message sets:

Package	Version	Messages
@ediflow/edifact-d96a	D.96A	126 message types
@ediflow/edifact-d01b	D.01B	full standard
@ediflow/edifact-d12a	D.12A	full standard
@ediflow/edifact-d20b	D.20B	195 message types

Every message type defined in the standard — ORDERS, INVOIC, DESADV, SLSRPT, RECADV, PRICAT, REMADV, IFTMIN, COPARN, and hundreds more — is available out of the box. No custom definitions needed.

npm install @ediflow/core @ediflow/edifact @ediflow/edifact-d20b

🛒 EANCOM 2002 — full GS1 retail standard
50 GS1 retail message types built on EDIFACT syntax.
Covers the complete retail supply chain: ORDERS, ORDRSP, DESADV, RECADV, INVOIC, REMADV, SLSRPT, PRICAT, INVRPT, PRODAT and more — all with GS1 GLN party identification and EAN-13/GTIN product codes.

npm install @ediflow/core @ediflow/edifact @ediflow/eancom-2002

🔄 Business Object Mapping — Round-Trip
Map any EDI message directly to/from typed JSON objects — no manual field extraction:

// EDI → Business Object (JSON)
const order = mappingService.map(message);
console.log(order['BGM']['1004']); // Document number

// Business Object → EDI (rebuild)
const rebuilt = mappingService.unmap(order);

⚙️ CLI enhancements

# Parse to business object
npx @ediflow/cli parse invoice.edi --output-type business-object

# Export full schema for a message type
npx @ediflow/cli export-schema --standard x12 --version 004010 --message 850

# Build EDI from JSON
npx @ediflow/cli build order.json --standard edifact --version d20b --message ORDERS

---

📂 Ready-to-run examples

All examples are in the repo under examples/ — clone and run with npx tsx:

X12

npx tsx examples/x12/parse-850/index.ts        # Parse Purchase Order
npx tsx examples/x12/build-850/index.ts        # Build 850 + round-trip
npx tsx examples/x12/validate-837/index.ts     # Validate Healthcare Claim
npx tsx examples/x12/schema-export/index.ts    # Load X12 004010 schema
npx tsx examples/x12/multi-message/index.ts    # Parse 850 + 810 + 856 + 997

EDIFACT

npx tsx examples/edifact/parse-orders/index.ts    # Parse ORDERS
npx tsx examples/edifact/build-invoic/index.ts    # Build INVOIC + round-trip
npx tsx examples/edifact/validate-desadv/index.ts # Validate DESADV

HIPAA

npx tsx examples/hipaa/parse-837/index.ts     # Parse 837P Professional Claim
npx tsx examples/hipaa/validate-835/index.ts  # Validate 835 Remittance Advice

EANCOM

npx tsx examples/eancom/parse-desadv/index.ts     # Parse DESADV (GLN + EAN-13)
npx tsx examples/eancom/validate-desadv/index.ts  # Validate DESADV

---

By the numbers

• 📦 13 packages on NPM
• 🔷 X12: 293 + 319 transaction sets (2 versions)
• 🌍 EDIFACT: 126 + 195 message types (4 versions)
• 🛒 EANCOM: 50 GS1 retail messages
• 🏥 HIPAA: 14 transaction sets
• ✅ 711 tests passing
• 📊 ≥ 90% code coverage (@ediflow/core)
• 0 TypeScript errors
• ⚖️ MIT License

---

Install

# X12 004010 (293 transaction sets)
npm install @ediflow/core @ediflow/x12 @ediflow/x12-004010

# X12 006040 (319 transaction sets)
npm install @ediflow/core @ediflow/x12 @ediflow/x12-006040

# EDIFACT D.20B (195 messages — or use d96a / d01b / d12a)
npm install @ediflow/core @ediflow/edifact @ediflow/edifact-d20b

# HIPAA (14 transaction sets)
npm install @ediflow/core @ediflow/x12 @ediflow/hipaa-x12-005010

# EANCOM 2002 (50 GS1 retail messages)
npm install @ediflow/core @ediflow/edifact @ediflow/eancom-2002

→ Full changelog: https://github.com/ediflow-lib/core/blob/main/CHANGELOG.md
→ Examples: https://github.com/ediflow-lib/core/tree/main/examples
→ Quick Start: https://github.com/ediflow-lib/core/blob/main/docs/QUICK_START.md

---

A personal note 🌊⭐

EDIFlow is a solo open-source project — no team, no funding, just code and a belief that TypeScript developers deserve modern EDI tooling that actually flows.

The name isn't accidental. Inspired by the Taoist "Way of Water": EDI data should move through systems naturally — adapting, connecting, never fighting complexity. That philosophy drives every architectural decision in this library.

If you think the same — or if you work in supply chain, logistics or healthcare and are tired of fighting brittle EDI parsers — a GitHub Star goes a long way. It helps the project get discovered by others who need it.

⭐ Star EDIFlow on GitHub

---

What are you building with EDI?
Drop a comment below — I'd love to know which standards and message types matter most to you. Your feedback directly shapes what comes next (IDOC? VDA? More HIPAA sets?).

---