Mapping to DCAT-AP, HealthDCAT-AP

In the context of data sharing, mapping a metadata model to DCAT-AP is a relatively common exercise because organisations are free to adopt any data management and metadata standard that meets their needs, or even develop a custom model.

 
 
However, to ensure interoperability and facilitate the exchange of metadata between dataset catalogues and across different domains, DCAT-AP serves as a common interchange metadata standard.
The mapping process consists in aligning metadata elements from the chosen standard with DCAT-AP properties. While mapping an organisation's metadata model to DCAT-AP is essential for consistent metadata sharing, it often presents significant challenges. To mitigate these challenges, it is necessary to optimise the mapping process to prevent information loss and ensure that all necessary data is accurately represented.
Examples of metadata mapping to DCAT-AP:
ISO 19139 (Geographic MetaData XML (gmd) encoding) to GeoDCAT-AP
SDMX (Statistical Data and Metadata eXchange) to StatDCAT-AP
CKAN (Catalogue system's metadata model) to DCAT-AP
EHDS Regulation Article 79) EU Dataset Catalogue
1. The Commission shall establish an EU dataset catalogue connecting the national (x) dataset catalogues established by the health data access bodies in each Member State as well as the dataset catalogues of authorised participants in HealthData@EU.
Within the HealthData@EU infrastructure, HealthDCAT-AP will serve as the common interchange metadata standard between the national dataset catalogues of health data access bodies and authorised participants, and the EU dataset catalogue. Considering that mapping to DCAT-AP is a complex process often fraught with technical issues, semantic challenges, and potential information loss, it is, therefore, recommended to adopt and standardise the use of HealthDCAT-AP across the entire HealthData@EU infrastructure.

However, specific requirements for particular health domains may arise and must be addressed. In such cases, DCAT allows for extensions to meet these needs. It is crucial that stakeholders ensure the interoperability of HealthDCAT-AP remains intact. Extending HealthDCAT-AP at the national level, the authorised participant level, or customising it at the data holders' level is a viable option, and will likely facilitate the integration and adoption of HealthDCAT-AP within the HealthData@EU infrastructure.