Layer - Data Exchange
What is the purpose of the Data Exchange layer?
The Data Exchange layer makes it possible to design and control the flow of data between systems. Data Exchange can be internally or between parties in the value network. The industry currently recognizes three distinct models: federated, centralized, and hybrid.
Federated Data Exchange
Federated is a decentralized approach that emphasizes partial, controlled sharing among autonomous databases. Components (systems) of a federated architecture represent the various systems/machines. Each system controls its interactions with others by means with the support of Data Formats. The federated architecture provides a means to share data and transactions using messaging services, combining information from several components, and providing the coordination of data exchange among autonomous components.
DataPorts is an example of Federated Data Exchange, where machines exchange data (push & pull) using IoT technologies.
Centralized Data Exchange
Centralized architecture emphasizes full control over data sharing through a centralized repository. Components in a centralized architecture refer to the central data repository. The repository authenticates the requester, authorizes the transaction, and records it for audit and reporting purposes.
DataPools like GS1-GDSN, EZBase, 2BA, InstallData and PS in Foodservice are based on centralized data exchange.
Hybrid Data Exchange
Hybrid is a combination of the two architecture types used to achieve the actual exchange of clinical data. For instance, trade conditions may occur through the use of a federated model, while public product data is shared through a centralized database.
Data Exchange Technologies
- RestAPI
- SOAP API
- DataPorts (IOT based)
- FTP/sFTP/FTPs
- AS2
- Fileshare solutions like: Dropbox, Box.com and Sharepoint
