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.1.0

Jump to bottom
Reto Wettstein edited this page Oct 21, 2022 · 1 revision

This repository contains a Data Transfer Process to be used in Projectathons in order to send data from a Data Integration Center (DIC) to 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

The Data Transfer Process in v0.1.0 is composed of 2 different subprocesses:

Send Process

The send process is used at a DIC to prepare and initiate data transmission of a specific projectathon projects 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 transfer Bundle
  • Provide the encrypted transfer Bundle and the local DSF FHIR server for the COS
  • Automatically delete the encrypted transfer Bundle on the local DSF FHIR server after 2 minutes

Prerequisites

In order to start the send process, the following needs to be known and prepared:

  • DIC identifier of the local organization (dic-identifier)
  • COS identifier which should receive the results (coordinating-site-identifier)
  • Project identifier for which results should be transmitted (project-identifier)
  • A DocumentReference and Binary resource on the KDS FHIR store representing the result to be transmitted
    • An example transaction Bundle to load a result onto a KDS FHIR store for the projects WE-STORM and NT-proBNP can be found here
    • Replace the placeholder <REPLACE-WITH-YOUR-ORGANIZATION-IDENTIFIER> with the dic-identifier
    • Replace the placeholder <REPLACE-WITH-DATE-AND-TIME> with the date and time when the result was created in the form yyyy-MM-dd'T'HH:mm:ssX
    • Replace the placeholder <REPLACE-WITH-BASE64-ENCODED-CSV-FILE> with the base64 encoded CSV result file
    • Check the project-identifier which is already set in the example transaction Bundles

Start Send Process

The send process can be started for the projects WE-STORM and NT-proBNP by sending the Task resources that can be found here to the local DSF FHIR server:

  • Replace the placeholder <REPLACE-WITH-YOUR-ORGANIZATION-IDENTIFIER> with the dic-identifier
  • Replace the placeholder <REPLACE-WITH-DATE-AND-TIME> with the date and time when the result was created in the form yyyy-MM-dd'T'HH:mm:ssX
  • Check the coordinating-site-identifier and the project-identifier which are already set in the example Task resources

Receive Process

The receive process is used at a COS to download and store a result of a specific projectathon projects 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 transfer Bundle from a DIC DSF FHIR server
  • Decrypt the transfer Bundle
  • Validate the transfer Bundle
  • Store the resources contained in the transfer Bundle on the local KDS FHIR Store
Clone this wiki locally