OpenEDI JSON

An OpenAPI 3 schema with EDI extensions, for ediFabric Native, ediFabric Cloud and the EDI Spec Builder. Read what OpenEDI is.

ediFabric .NET template

The ediFabric .NET class for the transaction, with the common segments, composites and codes it needs.

ediFabric Native model

The file ediFabric Native loads to parse and generate EDI from Python, Java, Node.js, Go, Rust, C and C#.

The specs in this library, including their OpenEDI, C# and ediFabric Native files and their structure, are part of ediFabric and are copyright EDI Fabric Limited, like the rest of the product. Use them only with ediFabric and EdiNation. Copying, converting or extracting them into another product, library or format isn't allowed. See section 3.6 of the ediFabric license agreement.

HIPAA 5010 spec pages

The HIPAA 5010 transactions with the errata (A1, A2) applied have their own pages, with the structure and all three formats in one place. More standards follow.

Browse by standard

Pick a standard and version to see all its transactions.

X12 HIPAA 3 versions, 32 transactions

The HIPAA implementation guides for health care claims, remittances, eligibility, claim status, enrollment, premium payments and prior authorization.

X12 IAIABC 1 version, 1 transactions

The IAIABC workers' compensation medical bill implementation guide.

EANCOM 4 versions, 162 transactions

The GS1 EANCOM subset of EDIFACT for retail and consumer goods.

EDIG@S 1 version, 13 transactions

The EDIG@S subset of EDIFACT for gas transmission and nominations.

IATA PADIS 3 versions, 148 transactions

IATA PADIS EDIFACT messages for passenger and airline data, such as PNRGOV and PAXLST.

HL7 1 version, 416 transactions

HL7 version 2 messages for patient administration, orders, results and other clinical data.

NCPDP 3 versions, 52 transactions

NCPDP standards for pharmacy claims and electronic prescriptions.

VDA 1 version, 7 transactions

VDA flat-file messages of the German automotive industry for delivery schedules, dispatch advice and invoices.

How to customize a spec for a trading partner

  1. Open the standard spec. For example, the 837P professional claim.
  2. Copy it. Select Customize in Spec Builder and enter a name for your copy, such as acme_837P. Names starting with EdiNation or EdiFabric are reserved for the standard specs.
  3. Change it. In the Spec Builder, select a loop, segment or element and change its usage, repeats, lengths, formats or codes, or add, move, copy and delete loops, segments and elements.
  4. Use it. Select Update, then parse and validate files against your spec in EdiNation, or download it for ediFabric Native, Cloud or .NET.

Use the specs in your code

Parse and generate EDI against a standard or custom spec with ediFabric .NET, ediFabric Native or ediFabric Cloud. Every HIPAA spec page also shows how to generate classes in Python, Java, Node.js, Go, Rust or C for the JSON that ediFabric Native returns.

Frequently asked questions

They are free to view and download, with or without an account, for use with ediFabric .NET, ediFabric Native, ediFabric Cloud, EdiNation and the EDI Spec Builder. You can share a spec, unchanged, with your team and trading partners to agree an EDI exchange you process with ediFabric or EdiNation. Free to access doesn't mean free to reuse: the specs are copyright EDI Fabric Limited and licensed under section 3.6 of the ediFabric license agreement.
No. You may not copy, scrape, convert or re-create the specs or their structure (loops, segments, elements, usage, lengths and codes) in another format, library, schema set or product, show them to the users of another platform, or use them to train AI models. This applies even if you change the format or the names, or credit ediFabric. To use the specs in your product, use them through ediFabric .NET, Native or Cloud.
OpenEDI is an open format for EDI specifications based on the schema object in OpenAPI 3. The format is open source under the MIT license, and it describes messages from every standard in the library. The MIT license covers the format only, not the specs in this library that are written in it.
Yes. Every spec is built from the official guidelines of its standard and version, and the same specs are used to parse and validate EDI in ediFabric and EdiNation.
The specs in the library are the standard ones and can't be edited. Select Customize in Spec Builder to copy one under your own name and edit the copy, or download the OpenEDI JSON and import it in the EDI Spec Builder.
The transaction guides have a sample file, the same data as JSON, and code to parse, validate and generate each transaction with ediFabric .NET, Native and Cloud.