docs.healthdata.beLast updated: 2025-04-30 15:05
Please find below the schematic overview of the Epilabo data collection within the be.Prepared architecture. The architecture components and data flows in red are not used by the Epilabo data collection. The be.Prepared architecture combined with the Epilabo data collection allows for scalability in terms of pandemic preparedness and for support of the reporting systems of mandatory notifiable diseases managed by the federated health authorities.
The Epilabo data collection makes use of the following components:
| Component Ref. | Component name | Component Description |
| C1 | HCO (LIMS) | Data provider (DP) Healthcare organisation (HCO)/Laboratory Information (Management) System (LIMS). |
| C2 | HD4DP v2 | Full Health Data 4 Data Providers version 2 (HD4DP v2) Front end installation at the DP side. |
| C4 | be.Prepared ODS | be.Prepared Operational Data Store. |
| C5 | HD-DWH | HealthData Data WareHouse. |
| C7 | Web Service | Web Service for federated health authorities |
| eHealth | eHealth TTP | Pseudonymization of data via eHealth as Trusted Third Party |
The Epilabo data collection uses the following flows:
| Flow Ref. | Flow name | Flow Description |
| F2 | Transfer of Epilabo data to HD4DP v2.0 | Epilabo data is transferred from the HCO by the use of Data Collection Definitions (DCDs). Two DCDs are in use: CB_MO_NOM – the DCD used for the nominative dataflow for test results from patients residing in the Walloon / Brussels Capital region / German speaking community; data will be transmitted to the federated health authorities (AVIQ and Vivalis) to support the reporting systems of mandatory notifiable infectious diseases; CB_MO_PSEUD – the DCD used for the pseudonomized dataflow for test results from patients residing in Flanders. |
| F4 | Transfer to be.Prepared ODS | Transfer of complete data of CB_MO_NOM and business data of CB_MO_PSEUD to be.Prepared ODS |
| F13 | Pseudonymization via eHealth | Transfer of subset of CB_MO_PSEUD to eHealth for pseudonymization of identifiers |
| F6 | Transfer to be.Prepared ODS | Transfer of complete data of CB_MO_NOM and business data of CB_MO_PSEUD to be.Prepared ODS |
| F7 | Pseudonymization via eHealth | Transfer of subset of CB_MO_NOM to eHealth for pseudonymization of identifiers |
| F8 | Transfer to HD-DWH | Transfer of pseudonymized subset of CB_MO_NOM and of CB_MO_PSEUD to HD-DWH |
| F15 | Transfer to Web Service | Transfer of CB_MO_NOM data to Web Service for federated health authorities (AViQ and Vivalis) |
| F12 | Transfer to HD-DWH | Transfer of business data of CB_MO_NOM and of CB_MO_PSEUD to HD-DWH |
| F14 | Feedback loop HD-DWH/be.Prepared ODS | Feedback loop between HD-DWH and be.Prepared ODS for data load confirmation |
This documentation is being updated regularly. We try to provide as correct, complete and clear as possible information on these pages. Nevertheless, if you see anything in the documentation that is not correct, does not match your experience or requires further clarification, please create a support ticket via our portal (https://healthdatabe.atlassian.net/servicedesk/customer/portals) or send us an e-mail via support.healthdata@sciensano.be to report this documentation issue. Please, do not forget to mention the URL or web address of the page with the documentation issue. We will then adjust the documentation as soon as possible. Thank you!