HealthDCAT-AP Release 7 – Changelog

This page documents all changes introduced in Release 7 of HealthDCAT-AP, including new model elements, controlled vocabulary updates, infrastructure migrations, a new latest release URL, a new complete dataset example, and resolved community issues.

1. New Model Elements

1.1 Structured Data New

A new mandatory property healthdcatap:hasStructuredData has been introduced on the Dataset class to indicate whether the dataset contains structured data for which a machine-readable description of the data variables can be provided.

1.2 Variables — Migration from Sample to Dataset Updated

2. Controlled Vocabulary Updates

2.1 Infrastructure Migration Updated

All DG SANTE's created controlled vocabulary base URLs have been migrated from a temporary environment to HealthData@EU Acceptance environment.

Controlled VocabularyBefore (Release 6 URL)After (Release 7 URL)
Health Categories http://13.81.34.152:1101/resource/authority/healthcategories https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/healthcategories
Health Theme http://13.81.34.152:1101/resource/authority/health-theme https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/health-theme
Publisher Type http://13.81.34.152:1101/resource/authority/publisher-type https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/publisher-type
Health Activity http://13.81.34.152:1101/resource/authority/health-activity https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/health-activity

2.2 New Controlled Vocabularies New

Two new controlled vocabularies have been introduced for the fields conforms to (dct:conformsTo) and coding system (healthdcatap:hasCodingSystem).

Controlled VocabularyPropertyURL
Standard dct:conformsTo https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/standard/
Coding System healthdcatap:hasCodingSystem https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/coding-system/

3. Latest Release URL New

A latest URL has been introduced that automatically redirects users to the most recent published release of HealthDCAT-AP:

https://healthdataeu.pages.code.europa.eu/healthdcat-ap/releases/latest/

Bookmarking or linking to this URL ensures users always land on the current release without needing to update their links between versions.

4. New Dataset Example New

A Dataset example has been introduced to help implementers understand how HealthDCAT-AP properties are used together in practice.
It covers a complete Dataset description including Distribution, Variables, and key HealthDCAT-AP specific properties.

The example is available in the specification under Section 16 — HealthDCAT-AP Examples, and can be accessed directly here:
example-healthdcat-dataset.ttl

The example is illustrative and non-normative.

5. Resolved Community Issues

The following issues reported on the Code Europa issue tracker have been resolved in this release.

IssueTitle
#30HTML dataset description in multiple languages
#29Missing dct:title in continent scheme
#27Release 6 — Catalog.publisher cardinality not in line with DCAT-AP 3.0.1
#26Release 6 — healthdcatap:hasCodeValues should not enforce language-tagged literals
#25Release 6 — SHACL constraint for cv:email should use sh:nodeKind sh:Literal (aligned with CPOV)
#22"alternative" vs "other" — property naming clarification
#21"alternative" vs "alternative name" — label alignment with Dublin Core
#19Release 6 — Align dct:creator agent contact details with cv:ContactPoint pattern
#18Release 6 — Incorrect use of language tag on foaf:name in custodian example
#17Release 6 — Inconsistency between Quick Reference table and Distribution section for dcatap:applicableLegislation cardinality
#16Release 6 — Inconsistency in Publisher contact point: dcat:contactPoint used instead of cv:contactPoint in TTL example
#13Unclear usage of dpv:hasPurpose
#11Conformance statement and cardinality of property dcat:dataset do not match
#10Introduction of mandatory dcat:contactPoint for foaf:Agent subclass :HealthAgent is unworkable
#9Properties that link classes are not listed in the UML inside the class listed properties and may therefore be missed
#8Broken vocabulary links
#6Quick Reference section
#3How to specify standards and coding systems?