This is a critical addition, as understanding the purpose behind data collection is relevant to any dataset, whether personal or non-personal. While this type of metadata is beneficial for all datasets, it becomes especially relevant in the case of personal data, as it aligns with the requirements of the General Data Protection Regulation (GDPR). Under GDPR, organisations must clearly articulate the legal basis and purpose for processing personal data, making this information essential for datasets involving personal information. The inclusion of such properties within HealthDCAT-AP ensures a more complete understanding of the context and rationale for data collection, improving dataset transparency and aiding users in making informed decisions when accessing and utilising health data. |
|
|
HealthDCAT-AP also incorporates the Personal Data extension of the Data Privacy Vocabulary (DPV) specification providing additional concepts to represent different types and categories of personal data. The Personal Data extension (DPV-PD) offers as such a harmonised, standardised RDF framework of describing sensitive information in the context of HealthDCAT-AP. By extending DCAT-AP with DPV-PD, it enables the sensitive nature of health datasets containing personal information to be uniformly described and understood across various dataset catalogues, promoting interoperability and consistency. |
|
Real-world example: |
The dataset 'Linking of registers for COVID-19 vaccine surveillance' links selected variables from existing registries for COVID-19 vaccine surveillance, in order to ensure the monitoring of COVID- 19 vaccines in the phase following their marketing authorization. Given that this dataset contains personal-level information on Belgian citizens, its creation required approval from the Information Security Committee. The dataset's legal basis, purpose, and personal data categories are transparently communicated to data users through the use of the Data Privacy Vocabulary properties: dpv:hasLegalBasis, dpv:hasPurpose, and dpv:hasPersonalData. |
dpv:hasPurpose dpv:Purpose |
|
dpv:hasLegalBasis dpv:LegalBasis |
|
dpv:hasPersonalData dpv:PersonalData |
|