The BEWSD Dataflow Description

The BEWSD Dataflow Description

Below we describe (high level) the BEWSD dataflow between the data provider and the healthdata.be platform.

Step 1. (Automatic) data export from systems of data provider towards HD4DP v1 and prefill of forms if not complete.

Step 2. Manual registration (de novo or completion) of data in form component of HD4DP v1.

Step 3. Transfer of patient identifiers and registry data from HD4DP v1 towards eHBox messaging client of HCO (HCO UM/EM)

Step 4. Transfer of patient identifiers and registry data from eHBox messaging client of HCO (HCO UM/EM) towards TTP service of eHealth.

Step 5. Transfer of pseudonymized patient identifiers and registry data from TTP service of eHealth towards eHBox messaging client of HD (HD UM/EM)

Step 6. Transfer of pseudonymized patient identifiers and registry data from eHBox messaging client of HD (HD UM/EM) to HDRES v1

Step 7. Transfer of pseudonymized patient IDs and registry variables from HD4RES v1 towards Data Validation environment on HD DHW.

johanvanbussel Tue, 04/18/2023 - 11:45

Future BEWSD dataflow description

Future BEWSD dataflow description

Below we describe (high level) the BEWSD dataflow between HD4DP v2 and the healthdata.be platform.

Step 1. Automatic data export from systems of data provider towards HD4DP v2 and prefill of forms if not complete.

Step 2. Manual registration (de novo or completion) of data in form component of HD4DP v2.

Step 3. Direct real time transfer of registry variables and technical ID of record from HD4DP v2 towards HD.

Step 4. Transfer of patient identifiers and technical ID of record from HD4DP v2 towards eHBox messaging client of HCO (HCO UM/EM).

Step 5. Transfer of patient identifiers and technical ID of record from eHBox messaging client of HCO (HCO UM/EM) towards TTP service of eHealth.

Step 6. Transfer of pseudonymized patient identifiers and technical ID of record from TTP service of eHealth towards eHBox messaging client of HD (HD UM/EM).

Step 7. Transfer of pseudonymized patient identifiers and technical ID of record from eHBox messaging client of HD (HD UM/EM) to HD Integration engine.

Step 8. Joining of pseudonymized patient IDs and the registry variables based on the technical ID and Transfer of the records from HD Integration engine towards Data Validation environment on DHW.

Adelaide.DAmore Tue, 04/18/2023 - 11:46