What is an EDI standard?
Let's assume that a fictional customer, A wants to trade with a fictional vendor, B. When A needs something from B, it sends out a request message detailing what it wants. Then B responds with another message to either confirm or reject parts or the request in full. This is an oversimplified analogy of a "commercial conversation" between any two partners, and the contents of the messages represent any of the various business, healthcare, or other data types. The EDI Standards govern the format of these messages.
Note
EdiFabric unified all EDI formats into one, so you can support them all in exactly the same way.
Why do EDI standards exist?
The reason behind the necessity for data to be formatted in a specific way is to allow the message exchange to be fully automated using software applications. EDI Standards improve the overall speed and accuracy of data exchange, translation, and validation, and at the same time, reduce errors and roundtrips.
There are several major EDI Standards, and their respective dialects, in circulation today. This diversity is due to various historical, business, and evolutionary reasons. However, in general, EDI is not confined to trade only but spans across multiple verticals such as healthcare, medicine, logistics, manufacturing, maritime, etc.
Download the free examples
How are EDI standards supported?
The range of EDI formats, versions, and message types poses a well-known complexity when implementing them in a standard way. The EDI Standards are only useful when agreed upfront between partners. The act of "agreeing" is the key here - the EDI format must be as comprehensive and as clear as possible and agreed on by both humans AND machines. EDI messages usually contain vital and critical information, and mishandling such information might lead to significant and unrecoverable damages.
The closest thing to providing a unified "EDI meta-format" was SEF (Standard Exchange Format). A software application that can work with SEF is always a sign of credibility because the predominant technique to ensure that machines "agree" on an EDI format is when they support SEF. Thus, surpassing the number of EDI Standards, an even more significant number of "EDI Software Applications" emerged. To weed out the hobbyist software, one can check whether it supports SEF - the good ones do, and the bad ones don't. It's as simple as that.
We created a powerful online SEF import tool that can convert any SEF-compliant SEF file (yes, unfortunately, SEF files that do not adhere to SEF exist) to EDI Template(s).
Learn about EDI SEF Import Online Tool
SEF is an EDI format itself and is still widely used; however, it is fairly complex to get into and is not well-aligned with the modern programming languages and data technologies.
How does ediFabric support EDI standards?
ediFabric comes in three forms that share the same EDI models and one serial key: ediFabric .NET, an SDK for .NET 8, 9, 10 and .NET Framework 4.8; ediFabric Native, a native library for Python, Java, Node.js, Go, Rust, C and C# on Windows, Linux and macOS (X12 and HIPAA today); and ediFabric Cloud, a REST API for any language. Install and get started.
ediFabric supports all of the major EDI Standards by representing EDI documents as models, as in Model-View-Controller (MVC). MVC is a standard pattern adopted in every significant programming language nowadays and allows developers of any background to start working with EDI quickly. Models, aka EDI Templates, provide a familiar concept for developers and massively reduce the learning curve compared to SEF.
Learn about EDI Templates
"Supporting an EDI Standard" in EdiFabric's terminology means that it supports the standard in full, e.g., irrespective of message types, versions, or dialects. EdiFabric is data-context agnostic; it doesn't "know" what an invoice or a medical claim is; it only knows how to process EDI Templates. The format specifics are reflected in the EDI Templates using a set list of attributes and patterns. This allows developers to create EDI Templates from scratch or customize existing ones, thus supporting any EDI format-specific version, message type, or dialect.
EANCOM GS1
GS1 EANCOM® is a GS1 subset of the UN/EDIFACT standard (United Nations Electronic Data Interchange for Administration, Commerce, and Transport). It contains only the message elements required by business applications and mandated by the syntax.
EANCOM is used in the retail and supply chain industries; some of the most popular messages are ORDERS, ORDRSP, OSTRPT, ORDCHG, INVOIC, etc.
The following EDI templates for EANCOM are provided out-of-the-box:
ediFabric .NET translates EANCOM files using EdifactReader and EdifactWriter:
ediFabric Native supports X12 and HIPAA today, with more standards to follow. For EANCOM, use ediFabric .NET or ediFabric Cloud. About ediFabric Native
ediFabric Cloud translates EANCOM files with the REST API, from any language:
EANCOM transaction examples with the structure, a sample file, JSON and code:
EDIFACT UN
UN/EDIFACT (the United Nations rules for Electronic Data Interchange for Administration, Commerce, and Transport) comprise a set of internationally agreed standards, directories, and guidelines for the electronic interchange of structured data between independent computerized information systems.
EDIFACT is the most popular EDI standard outside the U.S. and Canada, and is used across multiple industries with retail, supply chain, logistics, ocean shipping, manufacturing, and customs the prominent ones. Some of the most popular messages are ORDERS, INVOIC, DESADV, BAPLIE, COPARN, IFTMIN, etc.
The following EDI templates for EDIFACT are provided out-of-the-box:
ediFabric .NET translates EDIFACT files using EdifactReader and EdifactWriter:
ediFabric Native supports X12 and HIPAA today, with more standards to follow. For EDIFACT, use ediFabric .NET or ediFabric Cloud. About ediFabric Native
ediFabric Cloud translates EDIFACT files with the REST API, from any language:
EDIFACT transaction examples with the structure, a sample file, JSON and code:
X12 ASC
X12 defines and maintains transaction sets that establish the data content exchanged for specific business purposes. Transaction sets are identified by a numeric identifier and a name. Each transaction set is maintained by a subcommittee operating within X12’s Accredited Standards Committee.
X12 standard is used by hundreds of businesses, non-profit associations and government organizations spanning supply chain, transportation, health care, insurance, finance, and other industries. Some of the most popular messages are 850, 945, 210, 837, 810, 404, etc.
The following EDI templates for X12 are provided out-of-the-box:
ediFabric .NET translates X12 files using X12Reader and X12Writer:
ediFabric Native translates X12 files to JSON and back from Python, Java, Node.js, Go, Rust, C and C#:
ediFabric Cloud translates X12 files with the REST API, from any language:
X12 transaction examples with the structure, a sample file, JSON and code:
X12 HIPAA
HIPAA 5010 expands HIPAA regulation to include electronic transmission of healthcare transactions, including eligibility, claim status, referrals, claims, and remittances. ASC X12 Version 5010 is the adopted standard format for transactions, except those with retail pharmacies.
HIPAA standard is used by physicians, clearinghouses, hospitals, pharmacies, payers, and dentists. Some of the most popular messages are 837P, 270, 271, 278, 276, 834, etc.
The following EDI templates for X12 HIPAA are provided out-of-the-box:
ediFabric .NET translates HIPAA files using X12Reader and X12Writer:
ediFabric Native translates HIPAA files to JSON and back from Python, Java, Node.js, Go, Rust, C and C#:
ediFabric Cloud translates HIPAA files with the REST API, from any language:
HIPAA transaction examples with the structure, a sample file, JSON and code:
HL7
HL7 and its members provide a framework (and related standards) for the exchange, integration, sharing, and retrieval of electronic health information. These standards define how information is packaged and communicated from one party to another, setting the language, structure, and data types required for seamless integration between systems.
HL7 standards support clinical practice and the management, delivery, and evaluation of health services and are recognized as the most commonly used in the world. Some of the most popular messages are ADT, ORU, OSR, MDM, QBP, RDS, etc.
The following EDI templates for HL7 are provided out-of-the-box:
ediFabric .NET translates HL7 files using Hl7Reader and Hl7Writer:
ediFabric Native supports X12 and HIPAA today, with more standards to follow. For HL7, use ediFabric .NET or ediFabric Cloud. About ediFabric Native
ediFabric Cloud translates HL7 files with the REST API, from any language:
NCPDP Telecommunications and SCRIPT
National Council for Prescription Drug Programs (NCPDP) is an ANSI-accredited, standards development organization providing healthcare solutions. The Telecommunication Standard includes transactions for eligibility verification, claim and service billing, predetermination of benefits, prior authorization and information reporting.
The SCRIPT standard is used to interchange prescription data and related information in the medical provider community.
Some of the most popular messages are B1, B2, B3, MDM, QBP, RDS, etc.
The following EDI templates for NCPDP are provided out-of-the-box:
ediFabric .NET translates NCPDP Telecommunication files using NcpdpTelcoReader and NcpdpTelcoWriter:
ediFabric .NET translates NCPDP SCRIPT files using NcpdpScriptReader and NcpdpScriptWriter:
ediFabric Native supports X12 and HIPAA today, with more standards to follow. For NCPDP, use ediFabric .NET or ediFabric Cloud. About ediFabric Native
ediFabric Cloud translates NCPDP files with the REST API, from any language:
VDA
VDA develops standards and best practices to serve the needs of companies within the German automotive industry. The VDA has developed over thirty messages to meet the need of companies such as VW, Audi, Bosch, Continental, and Daimler AG.
Some of the most popular messages are 4905, 4906, 4908, 4913, etc.
The following EDI templates for VDA are provided out-of-the-box:
ediFabric .NET translates VDA files using VdaReader and VdaWriter:
ediFabric Native supports X12 and HIPAA today, with more standards to follow. For VDA, use ediFabric .NET or ediFabric Cloud. About ediFabric Native
ediFabric Cloud translates VDA files with the REST API, from any language:
VDA transaction examples with the structure, a sample file, JSON and code:
IATA PADIS
The IATA Passenger and Airport Data Interchange Standards (IATA PADIS) is used with both EDIFACT and XML syntaxes. IATA's passenger data comprises of Advance Passenger Information (API) and Passenger Name Records (PNR). This data can be a useful tool for governments' border control or security processing as it can help them pre-identify travelers and patterns.
The main messages are PADIS PNRGOV Message Standards, which are subsets of the EDIFACT standard. These messages are intended to facilitate the exchange of data relevant to government requirements on PNR data and Airlines reservation systems.
The following EDI templates for IATA are provided out-of-the-box:
ediFabric .NET translates IATA files using EdifactReader and EdifactWriter:
ediFabric Native supports X12 and HIPAA today, with more standards to follow. For IATA, use ediFabric .NET or ediFabric Cloud. About ediFabric Native
ediFabric Cloud translates IATA PNRGOV files with the REST API, from any language:
IATA transaction examples with the structure, a sample file, JSON and code:
IAIABC
IAIABC EDI Claims Standards are used by claims administrators to report workers' compensation first report of injury and subsequent report of injury claims data to U.S. jurisdictions.
The main message is 837, which is a modified version of X12 HIPAA's 837P.
ediFabric .NET translates IAIABC files using X12Reader and X12Writer. The following EDI templates for IAIABC are provided out-of-the-box:
EDIGAS
The Edig@s standard is a collection of electronic EDI messages used to send and receive operational data between trading partners in the gas industry.
ediFabric .NET translates EDIGAS files using EdifactReader and EdifactWriter. The following EDI templates for EDIGAS are provided out-of-the-box: