Skip to content
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.

Process Data Sharing Description v0.3.0

Jump to bottom
Reto Wettstein edited this page Nov 16, 2022 · 1 revision

The data-sharing process can be used in projectathons by a HRP to coordinate the project results aggregation from Data Integration Centers (DIC) using a Coordinating Site (COS, also called Data Management Site). The infrastructure and communincation messages on which the process is based can be seen in the following figure. The organizations use the Data Sharing Framework (DSF) for deployment and execution of the process.

Projectathon Data-Transfer: Process Figure

In the following descriptions is important to differentiate between the DSF FHIR server and the KDS FHIR store. The DSF FHIR server contains all FHIR resources of the DSF needed for process flow and the KDS FHIR store (shown as database symbol in the process figure) contains the project results (i.e. the actual data) to be transmitted. These are two different FHIR servers.

The data-sharing process in v0.3.0 is composed of 3 different subprocesses:

Data-Sharing: Coordinate Process

The data-sharing coordinate process is used at a HRP to prepare and coordinate a data transmission of a specific projectathon project result from DICs to a COS. This subprocess performs the following steps:

  • Start the data-sharing merge subprocess at the correspondig COS
  • Start the data-sharing execute subprocess at the DICs participating in the specific projectaton project
  • Receive a notification about successfully transmitted data transfer Bundles from a DIC to the COS
  • Receive the url from the COS for researchers to access the final merged project result

Data-Sharing: Execute Process

The data-sharing execute process is used at a DIC to prepare and initiate a data transmission of a specific projectathon project result to a COS. This subprocess performs the following steps:

  • Manually release the project results on the KDS FHIR store
  • Read the project results from a dedicated KDS FHIR store
  • Validate the project results and create a data transfer Bundle
  • Download the public-key from the COS and encrypt the data transfer Bundle
  • Provide the encrypted data transfer Bundle on the local DSF FHIR server for the COS
  • If configured: Notification of the DIC via e-mail about the successful provisioning of the encrypted data transfer Bundle
  • Automatically delete the encrypted data transfer Bundle on the local DSF FHIR server after 20 minutes

Data-Sharing: Merge Process

The data-sharing merge process is used at a COS to download and store results of a specific projectathon project from participating DIC, merge all received results after a predefined extraction period and to provide a final merged project result to researchers. This subprocess performs the following steps:

  • During process deployment: store a public-key Bundle on the local DSF FHIR server (if not already exists) to be used by a DIC for encryption of results to be transmitted
  • Download a data transfer Bundle from a DIC DSF FHIR server
  • Decrypt the data transfer Bundle using the private-key of the COS
  • Validate the data transfer Bundle
  • Store the resources contained in the data transfer Bundle on the dedicated KDS FHIR store
  • If configured: Notification of the COS via e-mail about the successful storage of resources included in the data transfer Bundle and the corresponding links to access these resources
  • Communicate successfully received data transfer Bundles from a DIC to the HRP
  • Merge the received resources included in the individual data transfer Bundles to a final project result
  • Manually release the final merged project result
  • Communicate the url to the HRP for researchers to access the final merged project result
Clone this wiki locally