Looking at Electronic Data Interchange (EDI) Reminds Me that the API Economy is Just Getting Started
I am neck deep in the expansion of what I consider to be my API toolbox, and I have been spending time mapping out the world of EDI. If you aren’t familiar with the Electronic Data Interchange (EDI), it “is the electronic interchange of business information using a standardized format; a process which allows one company to send information to another company electronically rather than with paper. Business entities conducting business electronically are called trading partners.” EDI is the original API by providing a, “technical basis for automated commercial “conversations” between two entities, either internal or external. The term EDI encompasses the entire electronic data interchange process, including the transmission, message flow, document format, and software used to interpret the documents”. EDI is everywhere, and truly the backbone of the global supply chain, but one that you only hear lightly about as part of the overall API conversation.
I have regularly come across the overlap between EDI and API over the last 10 years of doing API Evangelist, and while I have engaged in discussion around modernizing legacy EDI approaches in healthcare and commerce, most other fundamental building blocks of the global supply chain are entirely new to me. Revealing how little I know about the bigger picture of EDI, and how small my API world actually is. I don’t claim to know everything about information exchange and interoperability, but EDI is something that should be a bigger part of my storytelling, and the fact that it isn’t I think is revealing about how much more work we actually have in front of us when it comes to delivering on the promise of the API economy.
Take a look at some of the major EDI standards to get a sampling of the scope I am talking about. These are the electronic data interchange standards that have governed commerce before the Internet was around, and continues to define how data moves around.
- Edig@s (EDIGAS) – The Edig@s Workgroup decided to implement EDI messages to: Reduce the number of different messages currently used; Achieve a more efficient and more flexible way of handling the dispatching activities; Allow a faster reaction to a changed working environment. The EDI standard selected for those messages is the UN/EDIFACT standard and starting from Edig@s version 4 we introduced the XML standard.
- GS1 EDI – GS1 EDI is a set of global electronic messaging standards for business documents used in Electronic Data Interchange (EDI). The standards are developed and maintained by GS1. GS1 EDI is part of the overall GS1 system, fully integrated with other GS1 standards, increasing the speed and accuracy of the supply chain. Examples of GS1 EDI standards include messages such as: Order, Despatch Advice (Shipping Notice), Invoice, Transport Instruction, etc.
- HIPAA – The Health Insurance Portability and Accountability Act of 1996 was enacted by the 104th United States Congress and signed by President Bill Clinton in 1996. It was created primarily to modernize the flow of healthcare information, stipulate how Personally Identifiable Information maintained by the healthcare and healthcare insurance industries should be protected from fraud and theft, and address limitations on healthcare insurance coverage
- Hl7 – Health Level Seven International (HL7) is a not-for-profit, ANSI-accredited standards developing organization dedicated to providing a comprehensive framework and related standards for the exchange, integration, sharing and retrieval of electronic health information that supports clinical practice and the management, delivery and evaluation of health services.
- IATA Cargo-IMP – Cargo data exchange automation between airlines and other parties works much more efficiently if messaging procedures and standards are applied. IATA’s Cargo-IMP is the legacy standard for exchanging critical cargo operations information.
- Odette– Odette is a pan-European collaboration and services platform working for the entire automotive network. We bring together supply chain professionals and technology experts to create standards, develop best practice and provide services which support logistics management, e-business communications and engineering data exchange throughout the world.
- SCRIPT – SCRIPT is a standard promulgated by the National Council for Prescription Drug Programs (NCPDP) for the electronically transmitted medical prescriptions in the United States.
- Swift – The Society of Worldwide Interbank Financial Telecommunication was formed in 1973 and is headquartered in Brussels. SWIFT operates a worldwide financial messaging network which exchanges messages between banks and financial institutions. SWIFT also markets software and services to financial institutions, much of it for use on the SWIFTNet Network.
- TRADACOMS – Tradacoms is an early standard for EDI primarily used in the UK retail sector. It was introduced in 1982 as an implementation of the UN/GTDI syntax, one of the precursors of EDIFACT, and was maintained and extended by the UK Article Numbering Association.
- UN/EDIFACT – An international EDI standard developed under the United Nations, providing a set of syntax rules to structure data, an interactive exchange protocol (I-EDI), and standard messages which allow multi-country and multi-industry exchange.
- X12 Electronic data interchange (EDI) – The X12 Electronic data interchange (EDI) and Context Inspired Component Architecture (CICA) standards along with XML schemas which drive business processes globally. The membership of ASC X12 includes technologists and business process experts, encompassing health care, insurance, transportation, finance, government, supply chain and other industries.
EDI is API. These standards employ FTP, SFTP, FTPS, Email, HTTP, AS1, AS2, and AS4 to move data around. If SOAP is the father of API, then EDI is the grandfather. Each of these standards provide the technical details of the exchange of data, and providers can use any of these protocols to move the data around between providers. Going beyond the standards themselves, you can look at some of the EDI efforts out of enterprise and federal government agencies who set the tone for how markets work each day.
EDI is the supply chain API, orchestrating purchasing, fulfillment, logistics, invoices, and other elements of commerce, automative, healthcare, aerospace, and other top industries. If you want the road map for API industry over the next 30 years, take a look at the EDI space. If we want the backbone of the API economy to move into the future and use modern API practices, we are going to need to target this layer of the economy that governs how data is moved around and incentivize companies to employ HTTP, and HTTP/2 and standardize on XML, JSON, Avro, Protocol Buffers, and other common data exchange and serialization formats. If you map out the world of EDI, you could plot what is needed when it comes to API adoption in the next couple of decades.
The EDI space is messy and specialized, but it is very busy. There are many different agencies and governing bodies out there servicing the EDI layer of the global economy. Next, I will be diving more into each of the standards, as well as who are some of the dominant brokers when it comes to the certification and brokering of EDI discovery, integration, and ultimately evolution. If we want to modernize this legacy world of APIs we are going to have to focus on these power brokers, helping make them more aware of APIs, and why they represent the future of data interoperability. The most movement I have seen in this area to showcase is the work around HL7 and the FHIR specification for healthcare, but I’m going to need to assess the other business sectors serviced by EDI to understand their current state. After studying the world of EDI for a few days it is painfully clear how early in this whole API journey we are, and that the way we move data around with APIs is just in its infancy when it comes to the maturity and scope of EDI. Demonstrating to me that I’m going to be spending the rest of my career evangelizing APIs, and helping people understand the benefits of standardizing how we move bits and bytes around using HTTP.
This article originally appeared here.