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

Process Data Transfer Description v0.3.1

Jump to bottom
Mathias Rühle edited this page Oct 25, 2023 · 2 revisions

The data-transfer process can be used in projectathons to send data from a Data Integration Center (DIC) to a Coordinating Site (COS, also called Data Management Site). The infrastructure and communication 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-transfer process in v0.3.1 is composed of 2 different subprocesses:

Data-Transfer: Send Process

The data-transfer send 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:

  • 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 transfer Bundle
  • Automatically delete the encrypted data transfer Bundle on the local DSF FHIR server after 20 minutes

Data-Transfer: Receive Process

The data-transfer receive process is used at a COS to download and store a result of a specific projectathon project from a participating DIC. 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 local 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
Clone this wiki locally