Generated Narrative: StructureDefinition EHDSDocument Name Flags Card. Type Description & Constraints EHDSDocument 0..* EHDSDataSet Elements defined in Ancestors:header Document model Instances of this logical model can be the target of a Reference #xD; header 1..1 Base Document header elements #xD; identifier 1..* Identifier Unique identifier of the document #xD; documentType 1..1 CodeableConcept Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC #xD; documentTitle 1..1 string Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024' #xD; period 0..1 Period Time of service that is being documented #xD; version 0..1 string Business version of the document. #xD; attestation 0..* Base Document attestation details #xD; attester 1..1 EHDSHealthProfessional Attester who validated the document. Mulitple attesters could be provided. #xD; datetime 1..1 dateTime Date and time of the approval of the document by Attester. #xD; legalAuthentication 0..1 Base Document legal authentication details #xD; legalAuthenticator 1..1 EHDSHealthProfessional The person taking responsibility for the medical content of the document #xD; datetime 1..1 dateTime Date and time when the document was authorised. #xD; <a href="StructureDefinition-EHDSDocument-definitions.html#EHDSDocument.header.eventType" title="Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.">eventType 0..* CodeableConcept Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes. Binding Description: (preferred): LOINC, SNOMED CT, dicom-cid-33-Modality #xD; serviceSpecialty 0..* CodeableConcept Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT #xD; custodian 0..1 EHDSOrganisation Organisation that is in charge of maintaining the document/report. #xD; confidentiality 0..1 CodeableConcept Level of confidentiality of the document. Implicit value is normal. Binding Description: (preferred): hl7:Confidentiality #xD; presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document #xD; Documentation for this format
EHDS refined base model for common document data elements, including the common header. Data relevant to document type and its content for administrative and searching purposes.
Common header for all patient-related data
Author(s) by whom the resource was/were authored. Multiple authors could be provided.
Date and time of the last update to the resource (may be used for technical corrections).
Reason for the current status of the resource.
Language in which the resource is written. Language is expressed by the IETF language tag.
Type of document at hand, e.g. 60591-5 Patient summary document.
Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024'
Time of service that is being documented
Attester who validated the document. Mulitple attesters could be provided.
Date and time of the approval of the document by Attester.
The person taking responsibility for the medical content of the document
Date and time when the document was authorised.
Categorisation of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement between data sharing parties. This meta-data element serves primarily for searching and filtering purposes.
Additional details about where the content was created (e.g. clinical specialty)
Organisation that is in charge of maintaining the document/report.
Level of confidentiality of the document. Implicit value is normal.
A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document