The coronavirus dashboard gives up-to-date information about the development of the coronavirus in the Netherlands. It was launched 5 june 2020. Read more about the dashboard: link.
With the information on the dashboard, early signs that the rate of infection is increasing can be picked up. This project describes the definitions and calculations on various indicators to that purpose. For more information on data calculation and presentation for the corona dashboard: link.
In this section,the different indicators are listed that the dashboard uses, where the numbers of these indicators originate from, certain design and technological choices in order to visuals to the data on the dashboard.
| # | Indicator | Translation (NLD) | Abbr. |
|---|---|---|---|
| 1 | Intensive Care admissions | IC opnames | |
| 2 | Hospital Admissions | Ziekenhuis opnames | LCPS |
| 3 | Positive Tested People | Positief Geteste Personen | |
| 4 | Positive Tested People Per Region (i.e VR) | Positief Geteste Personen Per Regio | |
| 5 | Positive Tested Per Age Group | Positief Geteste Personen Per Leeftijdscategorie | |
| 6 | Infectious People | Besmettelijke Personen | |
| 7 | Nursinghomes | Verpleeghuizen | |
| 8 | Sewer Measurements | Rioolwater Metingen | |
| 9 | Sewage Treatment Plant | Rioolwaterzuiveringsinstallatie | RWZI |
| 10 | Growth number | Groeigetal | G-Number |
The backend was made in assignment of the Ministry of Healthcare and Sports of the Netherlands (i.e. Volksgezondheid, Welzijn en Sport; VWS). The backend application must be as robust as possible hence the choice was made to export the the processed data from the indicators in JSON format and to be made available for the frontend application.
The requirements for the back-end and front-end are all according to the RIVM standards, since the requirement was to be able to migrate the Corona Dashboard to the RIVM infrastructure. In addition, for the architecture design of the back-end, robustness was the choice over speed to minimize the loss of data integrity and minimize security risk. Hence, before the data is published online the data is checked by RIVM and the Ministery.
For most figures, we simply take the source data and apply little to no transformations to it. At most, we would add an extra date or replace a date with its UNIX counterpart. However, for some indicators we need to make a calculation, e.g. to calculate the 3 or 7 days averages. In this section we try to explain as much as possible what we have done in that case. In addition to the source code, we have also supplied the locations where you can find the data yourself. We are working on getting these sources available to the general public. In general, any user should be able to recreate the figures that are shown in the dashboard.
| # | Indicator | Source | Data Supplier | Definition |
|---|---|---|---|---|
| 1 | Administered Boostershots | VWS_COVID-19_Booster_gezette_prikken.csv | RIVM/GGD | t.b.d. |
| 2 | Planned Boostershots | VWS_COVID-19_geplande_afspraken.csv | RIVM/GGD | t.b.d. |
| 3 | Third Vaccinations Administered | 3e_vaccinaties_IC.csv | RIVM | t.b.d. |
Static data is used by linking sporadic changing transactional data and expand more insights, e.g. percentages per total citizens. In the below table an overview is created of the static table, which stored procedures process them and which destination tables they impact.
- Inhabitants Per Municipality
- Inhabitants Per Safety Region
- Sewage Treatment Plant AWZI
- Sewage Treatment Plant Per Municipality Code
- Safety Regions Per Municipality
- Nursing Home Locations Per Region
NOTE! Including the tracked and planned releases on the README.md started on 2022-04-05!
Hereby the tracked and planned changes that are implemented on the Acceptance and Production environments.
| Date of release | Source | Change | Environments |
|---|---|---|---|
| 2022-04-06 | vws_vaccine_deliveries_administered.ipynb | Added "Novavax" within the JSON-object vaccine_administered. | Acceptance Production |
| 2022-04-05 | vws_manual_input_vaccine_shots_planned.ipynb | Replaces a workflow to populate the JSON-object vaccine_administered_planned. Previously the JSON-object was populated by vws_vaccine_deliveries_administered.ipynb. | Acceptance |
| 2022-04-06 | vws_behavior_annotations_nl.ipynb | Temporary workflow to include annotations to the Behavior Graphs within the JSON-object behavior_annotation. | Acceptance Production |