EDI, for Electronic Data Interchange, accordingly replaces the interchange of hard copy documents and data with the electronic<\/strong> transfer of data <\/strong>through standardised, automated messages<\/strong>. EDI consequently avoids multi-stage procedures entailing data entry and re-entry, and the impact of such steps in terms of time and risk of error (e.g. creating an order, dispatch, receipt, entering the order again into the supplier’s system, then repeated in reverse for the invoice).<\/p>\n\n\n\n A more precise definition is provided by France\u2019s National Institute of Statistics and Economic Studies (INSEE) : \u201cElectronic data interchange (EDI) is a technique that replaces physical exchanges of documents between companies<\/strong> (orders, invoices, delivery notes, etc.) with exchanges, following a standardised format, between computers connected through specialised connections or through a (private) value-added network (VAN). The data are structured according to reference international technical standards.\u201d<\/p>\n\n\n\n EDI was first used to automate commercial procedures in the US car industry. It is now used in all countries, in all sectors of the economy, and for various types of data, although it is still mainly used for processing data between a buyer and a supplier, and in particular in the context of procurement transactions.<\/p>\n\n\n\n How process (BPM) and data (ESB) integration can create value for IT and business departments ?<\/p>\n\n\n\n One of the foundations of EDI is data structuring through technical standards<\/strong> (such as EDIFACT, meaning Electronic Data Interchange for Administration, Commerce and Transport, EDI X12, Odette, XML, etc.).<\/p>\n\n\n\n Standardisation of data exchanged is based on a common language between all stakeholders, and therefore between the different information systems and applications involved. EDI standards define how data is structured within an EDI message, thereby enabling data to be transferred directly from one application to another. This standardisation is essential to ensure different businesses can communicate.<\/strong><\/p>\n\n\n\n Several organisations are responsible for defining EDI standards such as GS1, Etebac, Odette, Tradacoms, Peppol, ASC X12, etc.<\/p>\n\n\n\n To implement electronic data interchange, companies can make use of specific EDI software to generate, translate and track messages following the defined format. Such software will consequently:<\/p>\n\n\n\n These are, of course, the most basic functions. The scope often extends beyond these basics, to storing messages, tracking interchanges, etc.<\/p>\n\n\n\n The pharmaceutical industry has to deal with considerable data integrity<\/a><\/u><\/strong> constraints, and work with a variety of partners, such as CDMO firms, suppliers, hospitals, pharmacies, government bodies, etc.<\/p>\n\n\n\n Control over the data produced and information continuity through the entire lifecycle are essential to the pharmaceutical quality system<\/a> and Good Manufacturing Practice. Digitalising interchanges with partners directly helps improve continuity in the information chain, boosting both performance and quality.<\/p>\n\n\n\n As in other industries, standardised messages are a pre-requisite for digitalised interchange<\/strong>. Historically in France, the role of codifying medicinal products (market authorisation code, dispensing unit code) and standardising messages and documents to fit EDI processes has fallen to the Club Inter Pharmaceutique (CIP). The medicinal product sector (manufacturers, government health insurance funding bodies, healthcare providers) collectively opted to use EDIFACT as its message standard.<\/p>\n\n\n\n With the requirements for pharmaceutical product serialisation, interchange standardisation and automation will only continue to develop. Pharmaceutical manufacturers must, for example, upload serialisation data to the EMVS (European Medicines Verification System) hub, which then makes the link with national systems (NMVS).<\/p>\n\n\n\n ESB vs ETL ? The distinction between is no longer relevant relative to today’s business requirements.<\/p>\n\n\n\n EDI offers certain long-standing benefits, in that it provides a first level of automation through the structured exchange of data:<\/p>\n\n\n\n However, while EDI has evolved, it did first appear in the 1960s, when the context surrounding B2B interchanges was different. Digitalisation has also continued on its path, and digital communications (to replace fax, mail, etc.) are no longer an innovation. <\/strong><\/p>\n\n\n\n Companies are no longer transforming alone.<\/strong> The development of new business models, the creation of new services, the enrichment of your own services… all these now require the involvement of the ecosystem, with suppliers, customers, partners, and open data all relevant.<\/p>\n\n\n\n Digital transformation is becoming synonymous with flexibility and agility in integrating with other firms in the value chain<\/strong>. This ecosystem is constantly developing, becoming more complex and expanding. Organisations are seeking to gain control over data interchanges not just partner by partner, but with their whole, changing ecosystem. Transformation has to be scalable in its application<\/strong>.<\/p>\n\n\n\n As regards these crucial factors of agility, speed of response and scalability, EDI does have some limitations<\/strong>:<\/p>\n\n\n\n When EDI is already implemented in long-standing areas of application (ordering, billing, supply chain, etc.), it often meets requirements. However, EDI\u2019s inertia and standardisation difficulties are obstacles to providing a response to the new boom in interchanges and the challenges of connectivity.<\/strong><\/p>\n\n\n\n Adding to EDI, APIs provide a connectivity and interchange solution that is more flexible, scalable, upgradeable, lends itself to standardisation, etc<\/strong>.<\/p>\n\n\n\n APIs can provide interchange in real time, which EDI cannot. They are customisable and can be used to create new services.<\/p>\n\n\n\n However, it should not be forgotten that one of EDI\u2019s strengths is standardised interchanges and formats<\/strong>, reinforced by its longevity. Formats such as EDIFACT have had time to become established and to be used by organisations extensively.<\/p>\n\n\n\n We firmly believe that APIM (API Management)<\/a><\/u><\/strong> and API governance<\/a> are crucial <\/strong>if APIs are to truly add value to a business.<\/p>\n\n\n\n We define API Management as the discipline of making the best use of APIs without compromising the information system and without adversely affecting the user experience. The purpose of API Management is therefore to manage and standardise API (Application Programming Interface) exposure, i.e. the publication, promotion and supervision of interchanges between a supplier service and a client service. <\/p>\n\n\n\n Of the many promises held by API and APIM, three in particular leap out, in comparison with EDI:<\/strong><\/p>\n\n\n\n At Blueway, we firmly believe that the response to data stream management issues is not just a technical or technological matter<\/strong>. The real question is that of your crucial transformation needs and how interchanges with your ecosystem are changing. How many services do you need to expose to suppliers and customers? Is scalability of data interchange a priority? Do you want to monetise your services, or at least monitor their consumption?<\/p>\n\n\n\n Want to discuss interoperability challenges with an expert?<\/p>\n\n\n\n![\"esb-bpm](\"https:\/\/www.blueway.fr\/wp-content\/uploads\/mockup\/en\/mockup-lb-esb-bpm-EN.png\")
<\/figure>How does an EDI system work?<\/h3>\n\n\n\n
\n
Focus on electronic data interchange in the pharmaceutical industry<\/h3>\n\n\n\n
![\"expert](\"https:\/\/www.blueway.fr\/wp-content\/uploads\/Mockup_ITW_Distinction_ESB_vs_ETL-EN.png\")
<\/figure>Limitations of EDI as the pace of interchange with the ecosystem increases<\/h2>\n\n\n\n
\n
EDI does not fully meet the challenges of agility and scalability<\/h3>\n\n\n\n
\n
From EDI to APIM<\/h2>\n\n\n\n
\n
![\"Schedule](\"https:\/\/www.blueway.fr\/wp-content\/uploads\/Equipes\/Collaborateurs\/visuel-rdv-blueway-1.png\")
<\/figure>