While it retains the core structure of DCAT-AP, HealthDCAT-AP introduces additional classes and metadata elements specifically adapted to the health sector. The purpose of HealthDCAT-AP is to streamline (meta)data exchange within the healthData@EU infrastructure and ensure interoperability with other EU Data Spaces. |
EHDS Regulation Article 77) Dataset description and dataset catalogue |
1. Health data access bodies shall, through a publicly available and standardised machine-readable dataset catalogue, provide a description in the form of metadata of the available datasets and their characteristics. The description of each dataset shall include information concerning the source, scope, main characteristics, and nature of the electronic health data in the dataset and the conditions for making those data available. |
What is DCAT-AP? |
DCAT-AP and any DCAT Application Profiles like HealthDCAT-AP is a descriptive metadata standard designed to ensure the interoperability and exchange of metadata records across multiple dataset catalogues within the EU. By providing a common structure, it allows different catalogues to seamlessly exchange metadata, improving the discoverability and accessibility of datasets across sectors and borders. It ensures that datasets are described in a consistent manner, making it easier to search for, find, and access data across various platforms. By providing a common structure for metadata, DCAT-AP allows different dataset catalogues to interoperate, which is crucial for integrating datasets from different sources. It improves the discoverability of datasets by ensuring that key descriptive information (such as title, description, keywords, and access information) is available and formatted in a uniform way. It supports the sharing of data across borders and sectors within the EU by ensuring that all dataset catalogues can interpret and use the metadata in a compatible manner. While the adoption of DCAT-AP as a standard for EU dataset catalogues is encouraged through various legal acts, such as Article 33 of the Data Act, DCAT-AP itself is not explicitly mentioned in EU legal texts. This is because DCAT-AP is a technological framework, and the possibility of disruptive technical evolution is always present. However, it is widely recognised by experts as the best technical solution currently available for implementing EU data spaces. |
Data Act - Article 33 |
Essential requirements regarding interoperability of data, of data sharing mechanisms and services, as well as of common European data spaces 1. Participants in data spaces that offer data or data services to other participants shall comply with the following essential requirements to facilitate the interoperability of data, of data sharing mechanisms and services, ... |
What DCAT-AP is not: |
Although DCAT-AP is a powerful tool for metadata exchange, it is not commonly used for internal data management due to its reliance on RDF (Resource Description Framework), a graph-based structure. Many organisations still rely on relational databases with tabular formats, making it more challenging to integrate DCAT-AP without additional technological adjustments. They do not perceive the need for a standardised metadata model like DCAT-AP. Moreover the most popular database management systems are typically relational databases, which use a table-based structure with rows and columns. In contrast, DCAT-AP is based on RDF (Resource Description Framework), a graph-based structure that uses triples (subject-predicate-object) to represent data. IT departments are more accustomed to traditional database management and may be unfamiliar with linked-data technologies such as DCAT-AP. This fundamental difference means that organisations would need to implement an additional layer of technology to integrate DCAT-AP as a metadata standard within their existing data management systems (Ref: mapping to DCAT-AP). In summary, DCAT-AP may not align with the current technical infrastructure or needs of many organisations, especially those that do not prioritise interoperability or lack expertise in Semantic web technologies. Impact of the EHDS Regulation: Entities subject to the EHDS Regulation - including natural or legal persons, public authorities, healthcare providers, research institutions, and others managing health data - must ensure that the data they hold is discoverable and interoperable within the healthData@EU infrastructure. These data holders are required to create, manage and make metadata about their datasets (as outlined in Article 33 of the EHDS Regulation) available in a standardised, machine-readable format in the National dataset catalogue. The use of HealthDCAT-AP supports compliance with the interoperability and data exchange standards necessary for the secure, cross-border sharing of health data across the EU. |
EHDS Regulation Article 60) Duties of health data holders |
3. The health data holder shall communicate to the health data access body a description of the dataset it holds in accordance with Article 77. The health data holder shall, at a minimum on an annual basis, check that its dataset description in the national dataset catalogue is accurate and up to date. |
EHDS Regulation Article 51 Minimum categories of electronic data for secondary use |
1. Health data holders shall make the following categories of electronic health data available for secondary use in accordance with this Chapter: |