Metadata Editor

Create, validate and publish HealthDCAT-AP metadata aligned with the European Health Data Space Regulation
Metadata profile
Select the metadata profile to be used.
A profile defines which metadata fields are shown, which rules are applied, how the record is validated, and where it can be published.
Level 1 Metadata Empty
0 Point
Untitled metadata record
Target catalogue
No catalogue title

Dataset Discovery

Discovery metadata (title, keywords, description, scope, time, space, etc.)
A name given to the dataset.
This property can be repeated for parallel language versions of the name.
A keyword or tag describing the dataset.
This is a generic free-text property. Enter only one keyword per field and add as many entries as needed. For more structured tagging, consider using semantic concepts (e.g., Health Theme / Code Values) when available.
A free-text account of the dataset.
This property can be repeated for parallel language versions of the description.
A statement about the lineage of a dataset.
Information about how the data was collected, including methodologies, tools, and protocols used.
A free text statement of the purpose of the processing of data or personal data.
Describe why the data are processed/used. You can repeat this field for multiple languages and add multiple entries if needed.
A definition of the population within the dataset.
Describe the population targeted by the dataset. This can be repeated for multiple language versions.
A geographic region that is covered by the dataset.
Select one or more countries and/or NUTS regions. If the dataset covers an entire country, do not also select sub-regions within it (avoid semantic contradiction).
You can select multiple values.
Alternative title of the dataset such as an acronym.
You can repeat this property for multiple language versions if needed.
A language of the dataset.
This property can be repeated if there are multiple languages in the dataset.
You can select multiple values.
The frequency at which the dataset is updated.
Select one entry from the EU frequency authority list.
You can select one value.
A temporal period that the dataset covers.
Provide start and end dates of the coverage period.
The minimum spatial separation resolvable in a dataset, measured in meters.
Provide a decimal value (e.g., 10.3).
The minimum time period resolvable in the dataset.
Provide an xsd:duration value (e.g., P1Y, P3M, P10D, PT6H).
P
T
ISO 8601 duration format
P = duration prefix
Y = years
M = months (before T)
D = days
T = time section
H = hours
M = minutes (after T)
S = seconds

Examples: P1D = 1 day, PT2H30M = 2 hours 30 minutes, P1Y2M10DT5H = 1 year 2 months 10 days 5 hours.
The date of formal issuance (e.g.: publication) of the dataset.
Use a date value (YYYY-MM-DD).
The most recent date on which the Dataset was changed or modified.
Use a date value (YYYY-MM-DD).
A temporal period for which the dataset is available for secondary use.
Provide start/end dates and optionally a note (repeatable with language tags).

Contacts

Publisher, custodian, HDAB, contact point, creator.
An entity (organisation) responsible for making the dataset available.
In addition to the Publisher information, the Publisher Type must be provided as well as a Publisher Note (description of the publisher activities).
Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource.
Use this property to identify the entity that technically holds and maintains the dataset. In the EHDS context, this field represents the legally defined health data holder (Article 2(6) EHDS Regulation).
Health Data Access Body supporting access to data in the Member State.
Provide HDAB details (name, URL, mail) and the HDAB type.
Contact information that can be used for sending comments about the dataset.
In many cases, the contact point may be the same as the creator or publisher. You may reuse the same organization or person URI across these roles when appropriate.
An entity responsible for producing the dataset.
In many cases, the creator may be the same as the contact point or publisher. You may reuse the same organization or person URI across these roles when appropriate.

Documentation

Documentation pages, provenance links, relations, versions, legal basis, quality annotations.
A page or document about this dataset.
Provide one or more documentation resources (URIs). Optionally add a label and a note (repeatable in multiple languages).
A web page that provides access to the dataset, its distributions and/or additional information.
Provide one or more landing page URIs.
A description of a relationship with another resource.
Provide the related resource URI and select one or more roles describing the nature of the relationship.
An Agent having some form of responsibility for the resource.
Provide the agent details and select one or more roles (e.g., processor).
An activity that generated, or provides the business context for, the creation of the dataset.
Describe one or more activities behind the creation of the dataset. Provide activity information (label, type, documentation, additional info, start date) and optionally the main agent involved (name, mail, URL, acted on behalf of).
A statement related to quality of the Dataset, including rating, quality certificate, feedback that can be associated to the dataset.
Provide one or more quality annotations by specifying the target URI and the annotation body/certificate URI.
The version indicator (name or identifier) of a resource.
Provide the version label/number of the current dataset (e.g., "3.0").
A description of the differences between this version and a previous version of the Dataset.
Describe the changes for this version. Repeatable for parallel language versions.
A related dataset that is a version, edition, or adaptation of the described dataset.
Provide URI(s) to the newer/next version(s) of this dataset.
This property refers to a related dataset of which the described dataset is a version, edition, or adaptation.
Provide URI(s) to the previous/parent version(s) of this dataset.
A related dataset from which the described dataset is derived.
Provide one or more URIs pointing to datasets/resources from which this dataset is derived.
The legal basis used to justify processing of personal data.
Add one or more legal bases. Provide a description (with language tag) and a source URI.
A related resource, such as a publication, that references, cites, or otherwise points to the dataset.
Provide URI(s) for publications or resources that cite/reference this dataset.
A related resource.
Use this for a general association when no more specific property fits (e.g., source, inSeries, qualifiedRelation, hasVersion/isVersionOf).
A secondary identifier of the dataset, such as MAST/ADS, DataCite, DOI, EZID or W3ID.
Add one or more secondary identifiers as structured objects (notation + schema agency).
A dataset series of which the dataset is part.
Provide URI(s) of the main dataset series (e.g., the overarching series covering all yearly editions).

Categorisation

Themes, type, health categories/themes, coding systems, personal data, conformance, size indicators.
A type of the Dataset.
Select one or more dataset types. The EU Dataset-type controlled vocabulary (http://publications.europa.eu/resource/authority/dataset-type) SHOULD be used.
You can select multiple values.
A category of the Dataset.
Select one or more themes using the EU data-theme controlled vocabulary: http://publications.europa.eu/resource/authority/data-theme.
You can select multiple values.
Indicates whether the Dataset contains structured data for which a machine-readable description of the data variables can be provided.
Use this boolean property to state whether the dataset contains structured data. Set it to true when a machine-readable description of the data variables can be published, and to false when such structured variables do not apply. When the value is true, at least one healthdcatap:hasVariables should be provided. RDF example: healthdcatap:hasStructuredData
Links the Dataset to a CSVW TableGroup that provides a machine-readable description of the data variables.
Use this property to link a structured dataset to a CSVW TableGroup that documents its data variables, columns, or fields in a machine-readable way. This property becomes mandatory when healthdcatap:hasStructuredData is true. RDF example: healthdcatap:hasVariables
The legislation that mandates the creation or management of the Dataset.
Provide one or more legal resources (ELI URIs) that apply to this dataset. For EHDS Regulation (published March 2025) you may use: http://data.europa.eu/eli/reg/2025/327/oj (where relevant).
You can select multiple values.
The health category to which this dataset belongs as described in the EHDS Regulation list of categories of electronic data for secondary use (Art. 51).
Select one or more EHDS health data categories using the controlled vocabulary: https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/healthcategories/.
You can select multiple values.
A category of the Dataset or tag describing the Dataset.
A dataset may have multiple health themes. Use the Health Theme controlled vocabulary: https://hdeu-dcat.acceptance.data.health.europa.eu/resource/authority/health-theme.
You can select multiple values.
Types of personal data contained in the dataset (the actual data, not the metadata record).
Select one or more personal data categories using DPV-PD (https://w3id.org/dpv/dpv-pd). Examples: Gender → https://w3id.org/dpv/dpv-pd#Gender ; Age → https://w3id.org/dpv/dpv-pd#Age.
You can select multiple values.
An established standard to which the described resource conforms.
If your dataset conforms to an established standard or specification, provide one or more URIs here.
You can select multiple values.
Coding systems in use (e.g., ICD-10-CM, DRGs, SNOMED CT).
Specify one or more standards used for coding/classification in the dataset (e.g., ICD-10-CM, SNOMED CT, DRGs) to improve discovery and machine-actionability.
You can select multiple values.
A free-text description of any health classification, terminology, ontology, thesaurus, or coding system used in the dataset.
Describe in free text any relevant code values used (e.g., U07.1, Y59.0). One entry per field; repeat as needed. No controlled vocabulary required here.
Size of the dataset in terms of the number of records.
Provide the total number of records (or an approximate count if exact is unavailable). Use a non-negative integer.
Number of records for unique individuals represented in the dataset.
Provide the total (or approximate) number of distinct individuals represented. Use a non-negative integer.
Minimum typical age of the population within the dataset.
Provide an approximate minimum age (non-negative integer). Approximation may help protect sensitive information.
Maximum typical age of the population within the dataset.
Provide an approximate maximum age (non-negative integer). Approximation may help protect sensitive information.

Data access

Access rights, distributions, samples (incl. tables/variables), analytics.
Information that indicates whether the Dataset is publicly accessible, has access restrictions or is not public.
Indicate the access status using one of these values: :public, :restricted, :non-public.

NON_PUBLIC — Not publicly available; access is restricted.
PUBLIC — Openly accessible to everyone.
RESTRICTED — Access restrictions apply (may be available under conditions).
You can select one value.
An available Distribution for the Dataset.
For HealthDCAT-AP, at least one distribution is mandatory independently of access rights. Each distribution should include information on the Health Data Access Body supporting access.
A sample distribution of the dataset.
Provide one or more sample distributions (e.g., anonymized/synthetic sample, or a data dictionary in CSVW).
An analytics distribution of the dataset.
Publishers are encouraged to provide URLs pointing to document repositories where users can access or request associated resources such as technical reports, quality measurements, usability indicators, etc.

Identifiers

Technical identifiers and local extensions used to uniquely reference the dataset and support internal system integration.
Unique identifier of the dataset.
This field is managed by the catalogue and cannot be edited here.
The main identifier for the Dataset, e.g. the URI or other unique identifier in the context of the Catalogue.
The use of persistent dereferenceable URIs is mandatory in the HealthDCAT-AP profile (i.e., HTTP URIs).
This field is managed by the catalogue and cannot be edited here.
The catalogue that this dataset belongs to.
This field is managed by the catalogue and cannot be edited here.
Metadata status.
This field is managed by the catalogue and cannot be edited here.
You can select one value.

Catalog Record

Metadata about the catalogue entry itself.
Unique identifier of the catalog record.
This field is managed by the catalogue and cannot be edited here.
Title of the CatalogRecord (in your output: dataset UUID).
Generated from the dataset UUID. RDF example: dct:title
This field is managed by the catalogue and cannot be edited here.
Human-friendly label for the record (in your output: dataset UUID).
Generated from the dataset UUID. RDF example: rdfs:label
This field is managed by the catalogue and cannot be edited here.
The catalogue that this CatalogRecord belongs to.
Written by the editor during export. RDF example: dct:isPartOf
This field is managed by the catalogue and cannot be edited here.
Agent describing who first created the metadata record in the editor context.
Blank node Agent: foaf:name / foaf:mbox / foaf:accountName. RDF example: tech:firstEditor
This field is managed by the catalogue and cannot be edited here.
The dataset described by this CatalogRecord.
Points to the dataset URI. RDF example: foaf:primaryTopic
This field is managed by the catalogue and cannot be edited here.
Links child resources (distributions/samples/analytics) that are part of the dataset graph, used for applying shared technical metadata status.
Custom helper predicate used by the editor. Repeated for each child URI.
This field is managed by the catalogue and cannot be edited here.
Creation/issuance timestamp of this CatalogRecord (technical layer).
Written from metadataIssuedCatalogRecord (fallback: metadataIssuedDatasetRecord). RDF example: tech:issued
This field is managed by the catalogue and cannot be edited here.
Last modification timestamp of this CatalogRecord (technical layer).
Set automatically at export time to now(). RDF example: tech:modified
This field is managed by the catalogue and cannot be edited here.
Version string of the metadata editor used to create/modify this record.
Captured from the UI header (e.g., vX.Y.Z). RDF example: tech:metadataEditorVersion
This field is managed by the catalogue and cannot be edited here.
Standard/profile that the metadata record is considered to conform to (set by editor logic).
Your script conditionally adds DCAT-AP 3.0.1 or HealthDCAT-AP release URI based on completeness. RDF example: dct:conformsTo
This field is managed by the catalogue and cannot be edited here.
Links to DQV QualityMeasurement nodes computed by the editor (general/mandatory/recommended/optional).
Generated at export time. RDF example: dqv:hasQualityMeasurement
This field is managed by the catalogue and cannot be edited here.