Health-RI wiki v4.0 -> consultatie (open tot 03-12-2024)

Data exchange platform

Owned by Health-RI
Nov 18, 2024
2 min read

datE: 13-11-2024 Status: FOR REVIEW

nlFlag.png

 

This article describes the data exchange platform. The data exchange platform is managed by the data broker and enables the delivery of data upon request, as described in the https://health-ri.atlassian.net/wiki/spaces/HWV4/pages/793618793.

See also the https://health-ri.atlassian.net/wiki/spaces/HWV4/pages/793620399

Description

Health-RI defines a Data Exchange Platform (DEP) as an environment that guarantees secure and efficient data exchange between different parties and systems.

Function of data exchange platform


A DEP supports the the https://health-ri.atlassian.net/wiki/spaces/HWV4/pages/793618793. After a data request has been approved and the necessary contracts have been concluded, each data holder can deliver the requested data to the DEP, after which only authorized data users can retrieve or use it in a secure processing environment. This environment makes it possible to create temporary cohorts and link data from different sources, in order to then issue it to a secure processing environment. Data can be exchanged both physically and via access tokens. An entity that can provide such a DEP is a data broker, which also provides other forms of exchange, such as virtualization.

Modalities still to consider for DEP:

  1. The DEP functions as a ‘data catalogue’ and, based on Identity and Access management, available datasets are published with the associated metadata, data profile and permitted data usage. In this case, the data exchange takes place directly between the data holder and data user.

Example: https://tweakers.net brokers between customer and supplier. Customer and supplier themselves enter into a bilateral relationship.

  1. The DEP functions as a virtualisation layer for all data holders. The data user queries the DEP and it processes the data request to the underlying data holders. Depending on the performance requirements, the data of the data holder can be ‘cached’.

Example: https://www.bol.com brokers between customer and supplier, but the customer only sees the bol.com context.

  1. Data of the data holder is replicated and stored in the DEP. Subvariants of this option depend on the functionalities offered.

Example: Data Transfer Zone of Erasmus MC and Data Landing Zone of anDREa BV (https://support.mydre.org/portal/en/kb/articles/data-landing-zone-dlz)

This document focuses on the third modality: Data Exchange Platform as a central service to exchange data.

Â