docs.healthdata.beLast updated: 2025-11-06 13:24
Please find below the schematic overview of the NRC data collection within the be.Prepared architecture. The components and data flows highlighted in red indicate elements that are not used by the NRC data collection. Together, the be.Prepared architecture and the NRC data collection provide a scalable framework that supports pandemic preparedness and enables the integration and linkage of pathogen and health data, such as microbial genomic, laboratory test results, clinical and epidemiological data..
The NRC 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 |
| C3 | BioIT platform | Cloud-based bioinformatics platform |
| C4 | be.Prepared ODS | be.Prepared Operational Data Store |
| C5 | HD-DWH | HealthData Data WareHouse |
| C6 | NRC platform /usability platform (Sciensano) | Platform available for NRCs |
| C7 | Web Service | Web Service for federated health authorities |
| eHealth | eHealth TTP | Pseudonymization of data via eHealth as Trusted Third Party |
NRC data collection uses the following flows (its numbering is not necessarily in chronological order):
| Flow Ref. | Flow name | Flow Description |
| F1 | Transfer of WGS data to BioIT platform | WGS data in the form of FASTQ files is transferred from the HCO via an sFTP connection to the BioIT platform |
| F2 | Transfer of NRC data to HD4DP v2.0 | NRC data is transferred from the HCO by the use of Data Collection Definitions (DCDs). Three DCDs are in use: - Laboratory Test Result NRC – the NRC-specific DCD used for the nominative dataflow for NRC test results - Clinical and Epidemiological Data - the NRC-specific DCD used for the nominative data flow for clinical and epidemiological data available at the NRC - Laboratory test result WGS metadata – the generic DCD used for the dataflow for technical metadata accompanying the WGS data |
| F3 | Transfer WGS metadata to BioIT platform | WGS metadata is transferred from the HCO via HD4DP v2.0 to the BioIT platform. |
| F4 | Transfer to be.Prepared ODS | Transfer of Laboratory Test Result NRC and Clinical and Epidemiological data to from HD4DPv2.0 to the be.Prepared ODS via sFTP connection |
| F5 | Load WGS and WGS metadata | Loading of the WGS data and WGS metadata on the BioIT platform |
| F6 | Load to be.Prepared ODS | Load of Laboratory Test Result NRC and Clinical and Epidemiological data to the be.Prepared ODS |
| F7 | Pseudonymization via eHealth | Transfer of subset of Laboratory Test Result NRC/BioIT and Clinical and Epidemiological data to eHealth for pseudonymization of identifiers |
| F8 | Transfer to HD-DWH | Transfer of pseudonymized subset of Laboratory Test Result NRC and of Clinical and Epidemiological data to the HD-DWH |
| F9 | Transfer of BioIT data to NRC platform | Transfer of BioIT data, structured as Laboratory Test Result BioIT, to the NRC platform |
| F10 | Transfer to NRC platform | Transfer of nominative Laboratory Test Result NRC and Clinical and Epidemiological data from the be.Prepared ODS to the NRC platform |
| F11 | Transfer to be.Prepared ODS | Transfer of Laboratory Test Result BioIT from the NRC platform to the be.Prepared ODS |
| F12 | Transfer to HD-DWH | Transfer of business data of Laboratory Test Result NRC/BioIT and of Clinical and Epidemiological data to the HD-DWH |
| F14 | Feedback loop HD-DWH/be.Prepared ODS | Feedback loop between the HD-DWH and the be.Prepared ODS for data load confirmation |