Yes, you can query EDI files with SQL. DeltaForge parses X12 EDI documents into Delta tables: load an 837 claim file or an 850 purchase order, then query it like any other table.
Parsing support for the major EDI standards
North American standard. Full envelope parsing: ISA/IEA, GS/GE, ST/SE, loops, and segments.
International standard. UNB/UNZ interchange, UNH/UNT message, composite element handling.
UK retail standard. Order, invoice, delivery, and acknowledgment message types.
Built-in transaction lookup table with 200+ codes; common sets shown below
837 (claims), 835 (remittance), 270/271 (eligibility), 834 (enrollment), 820 (premium payment).
850 (purchase order), 856 (advance ship notice), 810 (invoice).
204 (load tender), 214 (shipment status).
DeltaForge sits downstream of your existing EDI plumbing
A query and transformation layer. DeltaForge parses the X12, EDIFACT, and TRADACOMS documents you already receive into Delta tables, so order cycles, remittances, and shipment flows become SQL questions instead of file archaeology.
Not a VAN, translator, or interface engine. DeltaForge does not handle AS2 connectivity, trading-partner management, or outbound document generation. Your existing EDI exchange keeps running; DeltaForge makes its output analyzable.
Parsed EDI lands next to the rest of your lakehouse. Join 837 claims to FHIR resources, reconcile 850 orders against 856 ASNs and 810 invoices, and serve the results to BI tools. See the healthcare overview for the claims side.
Common questions about querying EDI documents with SQL
ANSI X12 (North American), UN/EDIFACT (international), and TRADACOMS (UK retail). For X12 the full envelope is parsed: ISA/IEA, GS/GE, ST/SE, plus loops and segments.
Segments are projected into Delta tables with typed columns and queried with standard SQL. EDI tables join to FHIR resources, HL7 v2 messages, or any other lakehouse table in the same SELECT.
No. It is the analytics layer on top of EDI you already exchange. There is no AS2 or VAN connectivity and no trading-partner management; DeltaForge makes received documents queryable.
Hands-on guides for getting documents into SQL
The full walkthrough: from a raw X12 file on disk to transaction-set tables you can SELECT from.
The same load-then-query pattern applied to CSV, useful for the reference data that sits alongside EDI feeds.
Full DML on the Delta tables your parsed EDI lands in, including upserting corrected documents.
Parse X12 and EDIFACT documents into Delta tables and query them with SQL on your own infrastructure.