MyHealth@Eu Hospital Discharge Report - Local Development build (v9.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON
• TTL

Logical Model: MyHealth@EU Hospital Discharge Report model

MyHealthEu refined model for hospital discharge report.

Usages:

• This Logical Model is not used by any profiles in this Implementation Guide

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

• Key Elements Table
• Differential Table
• Snapshot Table
• Statistics/References
• All

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHdrDischargeReport		0..*	EHDSDischargeReport	MyHealth@EU Hospital Discharge Report model Elements defined in Ancestors:header, header, presentedForm, body, attachments
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle HDR Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle HDR Handler
author[x]	O	1..*		The author of the report. Obligations Actor SHALL:handle HDR Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle HDR Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle HDR Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle HDR Handler
documentType	O	1..1	CodeableConcept	Type of the document (e.g. '34105-7 Hospital discharge summary) Binding Description: (preferred): LOINC Obligations Actor SHALL:handle HDR Handler
documentTitle	O	1..1	string	Title of the document, possibly autogenerated from the structured fields (e.g. 'Hospital discharge report. Jane Green. 07.10.2025-10.10.2025') Obligations Actor SHALL:handle HDR Handler
period		0..1	Period	Time of service that is being documented (typically the same as the time/period of encounter)
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle HDR Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate HDR Handler
attester[x]	O	1..1		Attester who validated the document Obligations Actor SHOULD:handle HDR Handler
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime	O	1..1	dateTime	Date and time of the approval of the document by Attester Obligations Actor SHOULD:handle HDR Handler
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle HDR Handler
legalAuthenticator[x]	O	1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it) Obligations Actor SHOULD:handle HDR Handler
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime	O	1..1	dateTime	Date and time when the document was authorised Obligations Actor SHOULD:handle HDR Handler
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
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle HDR Handler
intendedRecipient[x]	O	0..*		Intended recipient(s) of the information, i.e. a person or organisation that should be notified or be aware of the content. This element is used to indicate explicit communication intent and does not represent routine storage or passive availability of information (e.g. in portals). Listing an intended recipient does not create an assignment or responsibility. Obligations Actor MAY:able-to-populate HDR Handler
intendedRecipientMyHealthEuPatient			MyHealthEuPatient
intendedRecipientEHDSRelatedPerson			EHDSRelatedPerson
intendedRecipientMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
intendedRecipientMyHealthEuOrganisation			MyHealthEuOrganisation
presentedForm		0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
body	O	0..1	Base	Structured body of the discharge report document Obligations Actor SHALL:handle HDR Handler
alerts	O	0..1	Base	Section: Alerts. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicalAlert	O	0..*	MyHealthEuHdrAlert	Description of medical alerts in textual format: any clinical information that is imperative to know so that the life or health of the patient does not come under threat. Obligations Actor MAY:able-to-populate HDR Handler
encounterInformation	O	1..1	Base	Section: Encounter information. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
encounter	O	0..1	MyHealthEuHdrEncounter	Encounter information Obligations Actor SHALL:handle HDR Handler
note		0..1	string	Free text notes by the health professional
admissionEvaluation	O	0..1	Base	Section: Admission evaluation. Admission evaluation section should be reported only if it is relevant to ensure continuity of care. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the evaluation performer
patientHistory	O	0..1	Base	Section: Patient health history (anamnesis) containing only information that is highly relevant for this specific episode of care. The model is designed with the expectation that patient summary is available. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section. In case the section includes structured information, it should also be included in generatedNarrative.
note		0..1	string	Free text notes by the health professional
courseOfEncounter	O	0..1	Base	Course of inpatient or outpatient encounter. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
diagnosticSummary	O	0..*	MyHealthEuHdrCondition	Problems that were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the encounter. At least one treated problem should be marked. Other problems are recorded only if they are important for continuity of care (after discharge). Obligations Actor SHALL:handle HDR Handler
procedures	O	0..*	MyHealthEuHdrProcedure	Procedures performed during encounter which are significant for continuity of care, e.g. surgeries and other instrumental interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. Diagnostic procedures are typically captured as observation results and not repeated here. Obligations Actor MAY:able-to-populate HDR Handler
medicalDevicesAndImplants	O	0..*	MyHealthEuHdrDeviceUse	Medical devices (including implants) whose use was started, stopped, or otherwise modified during the encounter. Obligations Actor MAY:able-to-populate HDR Handler
pharmacotherapy	O	0..*	MyHealthEuHdrMedicationUse	Significant medication treatments during encounter. The content of this section may be repeated in the medication summary for full overview of patient's medications. Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings		0..*	EHDSObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination. The line between objective findings and test results is not clear and it is up to the implementers to decide how to logically display different measurements.
testResults		0..*	EHDSObservation	Significant medical test results of functional, diagnostic (including laboratory), and imaging examinations performed during encounter. This may include orders for which the results have not yet arrived.
note		0..1	string	Free text notes by the health professional
dischargeDetails	O	0..1	Base	Discharge details Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the health professional
medicationSummary	O	0..1	Base	Summary information on the medication recommended for the period after discharge, indicating whether the medication is changed or newly started. Compared to previous practices, the overview is supplemented with medication that has been discontinued. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicationUse	O	1..1	MyHealthEuHdrMedicationUse	Details about medication and dosage Obligations Actor MAY:able-to-populate HDR Handler
note		0..1	string	Free text notes by the health professional
carePlan	O	0..1	Base	Care plan and other recommendations after discharge. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
carePlan	O	0..*	MyHealthEuHdrCarePlan	Structured care plan after discharge. Multiple care plans could be provided. Obligations Actor MAY:able-to-populate HDR Handler
otherRecommendations		0..1	string	Other recommendations (advice) after discharge. E.g., recommendation to suggest hip replacement, reduce number of cigarettes, stop smoking, increase physical exercises, etc.
synthesis		0..1	string	Clinical synthesis (e.g. description of reasons and course of encounter) clustered by managed conditions. Clinical synthesis may include clinical reasoning (differential diagnostics, explanation of clinical context) in clinically complex conditions.
attachments	O	0..*	EHDSAttachment	Report attachments. Implementations may define what kind of attachments are allowed and may ignore unexpected attachments for security reasons. Obligations Actor MAY:able-to-populate HDR Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHdrDischargeReport.​header.language	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.documentType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.eventType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.serviceSpecialty	Base	preferred		Not State	Unknown

This structure is derived from EHDSDischargeReport

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHdrDischargeReport		0..*	EHDSDischargeReport	MyHealth@EU Hospital Discharge Report model Elements defined in Ancestors:header, header, presentedForm, body, attachments
header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle HDR Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle HDR Handler
author[x]	O	1..*		The author of the report. Obligations Actor SHALL:handle HDR Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle HDR Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle HDR Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Obligations Actor SHALL:handle HDR Handler
documentType	O	1..1	CodeableConcept	Type of the document (e.g. '34105-7 Hospital discharge summary) Obligations Actor SHALL:handle HDR Handler
documentTitle	O	1..1	string	Title of the document, possibly autogenerated from the structured fields (e.g. 'Hospital discharge report. Jane Green. 07.10.2025-10.10.2025') Obligations Actor SHALL:handle HDR Handler
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle HDR Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate HDR Handler
attester[x]	O	1..1		Attester who validated the document Obligations Actor SHOULD:handle HDR Handler
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime	O	1..1	dateTime	Date and time of the approval of the document by Attester Obligations Actor SHOULD:handle HDR Handler
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle HDR Handler
legalAuthenticator[x]	O	1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it) Obligations Actor SHOULD:handle HDR Handler
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime	O	1..1	dateTime	Date and time when the document was authorised Obligations Actor SHOULD:handle HDR Handler
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle HDR Handler
intendedRecipient[x]	O	0..*		Intended recipient(s) of the information, i.e. a person or organisation that should be notified or be aware of the content. This element is used to indicate explicit communication intent and does not represent routine storage or passive availability of information (e.g. in portals). Listing an intended recipient does not create an assignment or responsibility. Obligations Actor MAY:able-to-populate HDR Handler
intendedRecipientMyHealthEuPatient			MyHealthEuPatient
intendedRecipientEHDSRelatedPerson			EHDSRelatedPerson
intendedRecipientMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
intendedRecipientMyHealthEuOrganisation			MyHealthEuOrganisation
body	O	0..1	Base	Structured body of the discharge report document Obligations Actor SHALL:handle HDR Handler
alerts	O	0..1	Base	Section: Alerts. Obligations Actor MAY:able-to-populate HDR Handler
medicalAlert	O	0..*	MyHealthEuHdrAlert	Description of medical alerts in textual format: any clinical information that is imperative to know so that the life or health of the patient does not come under threat. Obligations Actor MAY:able-to-populate HDR Handler
encounterInformation	O	1..1	Base	Section: Encounter information. Obligations Actor SHALL:handle HDR Handler
encounter	O	0..1	MyHealthEuHdrEncounter	Encounter information Obligations Actor SHALL:handle HDR Handler
admissionEvaluation	O	0..1	Base	Section: Admission evaluation. Admission evaluation section should be reported only if it is relevant to ensure continuity of care. Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
patientHistory	O	0..1	Base	Section: Patient health history (anamnesis) containing only information that is highly relevant for this specific episode of care. The model is designed with the expectation that patient summary is available. Obligations Actor MAY:able-to-populate HDR Handler
courseOfEncounter	O	0..1	Base	Course of inpatient or outpatient encounter. Obligations Actor SHALL:handle HDR Handler
diagnosticSummary	O	0..*	MyHealthEuHdrCondition	Problems that were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the encounter. At least one treated problem should be marked. Other problems are recorded only if they are important for continuity of care (after discharge). Obligations Actor SHALL:handle HDR Handler
procedures	O	0..*	MyHealthEuHdrProcedure	Procedures performed during encounter which are significant for continuity of care, e.g. surgeries and other instrumental interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. Diagnostic procedures are typically captured as observation results and not repeated here. Obligations Actor MAY:able-to-populate HDR Handler
medicalDevicesAndImplants	O	0..*	MyHealthEuHdrDeviceUse	Medical devices (including implants) whose use was started, stopped, or otherwise modified during the encounter. Obligations Actor MAY:able-to-populate HDR Handler
pharmacotherapy	O	0..*	MyHealthEuHdrMedicationUse	Significant medication treatments during encounter. The content of this section may be repeated in the medication summary for full overview of patient's medications. Obligations Actor MAY:able-to-populate HDR Handler
dischargeDetails	O	0..1	Base	Discharge details Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
medicationSummary	O	0..1	Base	Summary information on the medication recommended for the period after discharge, indicating whether the medication is changed or newly started. Compared to previous practices, the overview is supplemented with medication that has been discontinued. Obligations Actor MAY:able-to-populate HDR Handler
medicationUse	O	1..1	MyHealthEuHdrMedicationUse	Details about medication and dosage Obligations Actor MAY:able-to-populate HDR Handler
carePlan	O	0..1	Base	Care plan and other recommendations after discharge. Obligations Actor MAY:able-to-populate HDR Handler
carePlan	O	0..*	MyHealthEuHdrCarePlan	Structured care plan after discharge. Multiple care plans could be provided. Obligations Actor MAY:able-to-populate HDR Handler
attachments	O	0..*	EHDSAttachment	Report attachments. Implementations may define what kind of attachments are allowed and may ignore unexpected attachments for security reasons. Obligations Actor MAY:able-to-populate HDR Handler
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHdrDischargeReport		0..*	EHDSDischargeReport	MyHealth@EU Hospital Discharge Report model Elements defined in Ancestors:header, header, presentedForm, body, attachments
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle HDR Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle HDR Handler
author[x]	O	1..*		The author of the report. Obligations Actor SHALL:handle HDR Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle HDR Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle HDR Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle HDR Handler
documentType	O	1..1	CodeableConcept	Type of the document (e.g. '34105-7 Hospital discharge summary) Binding Description: (preferred): LOINC Obligations Actor SHALL:handle HDR Handler
documentTitle	O	1..1	string	Title of the document, possibly autogenerated from the structured fields (e.g. 'Hospital discharge report. Jane Green. 07.10.2025-10.10.2025') Obligations Actor SHALL:handle HDR Handler
period		0..1	Period	Time of service that is being documented (typically the same as the time/period of encounter)
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle HDR Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate HDR Handler
attester[x]	O	1..1		Attester who validated the document Obligations Actor SHOULD:handle HDR Handler
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime	O	1..1	dateTime	Date and time of the approval of the document by Attester Obligations Actor SHOULD:handle HDR Handler
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle HDR Handler
legalAuthenticator[x]	O	1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it) Obligations Actor SHOULD:handle HDR Handler
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime	O	1..1	dateTime	Date and time when the document was authorised Obligations Actor SHOULD:handle HDR Handler
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
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle HDR Handler
intendedRecipient[x]	O	0..*		Intended recipient(s) of the information, i.e. a person or organisation that should be notified or be aware of the content. This element is used to indicate explicit communication intent and does not represent routine storage or passive availability of information (e.g. in portals). Listing an intended recipient does not create an assignment or responsibility. Obligations Actor MAY:able-to-populate HDR Handler
intendedRecipientMyHealthEuPatient			MyHealthEuPatient
intendedRecipientEHDSRelatedPerson			EHDSRelatedPerson
intendedRecipientMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
intendedRecipientMyHealthEuOrganisation			MyHealthEuOrganisation
presentedForm		0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
body	O	0..1	Base	Structured body of the discharge report document Obligations Actor SHALL:handle HDR Handler
alerts	O	0..1	Base	Section: Alerts. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicalAlert	O	0..*	MyHealthEuHdrAlert	Description of medical alerts in textual format: any clinical information that is imperative to know so that the life or health of the patient does not come under threat. Obligations Actor MAY:able-to-populate HDR Handler
encounterInformation	O	1..1	Base	Section: Encounter information. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
encounter	O	0..1	MyHealthEuHdrEncounter	Encounter information Obligations Actor SHALL:handle HDR Handler
note		0..1	string	Free text notes by the health professional
admissionEvaluation	O	0..1	Base	Section: Admission evaluation. Admission evaluation section should be reported only if it is relevant to ensure continuity of care. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the evaluation performer
patientHistory	O	0..1	Base	Section: Patient health history (anamnesis) containing only information that is highly relevant for this specific episode of care. The model is designed with the expectation that patient summary is available. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section. In case the section includes structured information, it should also be included in generatedNarrative.
note		0..1	string	Free text notes by the health professional
courseOfEncounter	O	0..1	Base	Course of inpatient or outpatient encounter. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
diagnosticSummary	O	0..*	MyHealthEuHdrCondition	Problems that were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the encounter. At least one treated problem should be marked. Other problems are recorded only if they are important for continuity of care (after discharge). Obligations Actor SHALL:handle HDR Handler
procedures	O	0..*	MyHealthEuHdrProcedure	Procedures performed during encounter which are significant for continuity of care, e.g. surgeries and other instrumental interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. Diagnostic procedures are typically captured as observation results and not repeated here. Obligations Actor MAY:able-to-populate HDR Handler
medicalDevicesAndImplants	O	0..*	MyHealthEuHdrDeviceUse	Medical devices (including implants) whose use was started, stopped, or otherwise modified during the encounter. Obligations Actor MAY:able-to-populate HDR Handler
pharmacotherapy	O	0..*	MyHealthEuHdrMedicationUse	Significant medication treatments during encounter. The content of this section may be repeated in the medication summary for full overview of patient's medications. Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings		0..*	EHDSObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination. The line between objective findings and test results is not clear and it is up to the implementers to decide how to logically display different measurements.
testResults		0..*	EHDSObservation	Significant medical test results of functional, diagnostic (including laboratory), and imaging examinations performed during encounter. This may include orders for which the results have not yet arrived.
note		0..1	string	Free text notes by the health professional
dischargeDetails	O	0..1	Base	Discharge details Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the health professional
medicationSummary	O	0..1	Base	Summary information on the medication recommended for the period after discharge, indicating whether the medication is changed or newly started. Compared to previous practices, the overview is supplemented with medication that has been discontinued. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicationUse	O	1..1	MyHealthEuHdrMedicationUse	Details about medication and dosage Obligations Actor MAY:able-to-populate HDR Handler
note		0..1	string	Free text notes by the health professional
carePlan	O	0..1	Base	Care plan and other recommendations after discharge. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
carePlan	O	0..*	MyHealthEuHdrCarePlan	Structured care plan after discharge. Multiple care plans could be provided. Obligations Actor MAY:able-to-populate HDR Handler
otherRecommendations		0..1	string	Other recommendations (advice) after discharge. E.g., recommendation to suggest hip replacement, reduce number of cigarettes, stop smoking, increase physical exercises, etc.
synthesis		0..1	string	Clinical synthesis (e.g. description of reasons and course of encounter) clustered by managed conditions. Clinical synthesis may include clinical reasoning (differential diagnostics, explanation of clinical context) in clinically complex conditions.
attachments	O	0..*	EHDSAttachment	Report attachments. Implementations may define what kind of attachments are allowed and may ignore unexpected attachments for security reasons. Obligations Actor MAY:able-to-populate HDR Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHdrDischargeReport.​header.language	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.documentType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.eventType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.serviceSpecialty	Base	preferred		Not State	Unknown

This structure is derived from EHDSDischargeReport

Summary

Key Elements View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHdrDischargeReport		0..*	EHDSDischargeReport	MyHealth@EU Hospital Discharge Report model Elements defined in Ancestors:header, header, presentedForm, body, attachments
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle HDR Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle HDR Handler
author[x]	O	1..*		The author of the report. Obligations Actor SHALL:handle HDR Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle HDR Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle HDR Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle HDR Handler
documentType	O	1..1	CodeableConcept	Type of the document (e.g. '34105-7 Hospital discharge summary) Binding Description: (preferred): LOINC Obligations Actor SHALL:handle HDR Handler
documentTitle	O	1..1	string	Title of the document, possibly autogenerated from the structured fields (e.g. 'Hospital discharge report. Jane Green. 07.10.2025-10.10.2025') Obligations Actor SHALL:handle HDR Handler
period		0..1	Period	Time of service that is being documented (typically the same as the time/period of encounter)
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle HDR Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate HDR Handler
attester[x]	O	1..1		Attester who validated the document Obligations Actor SHOULD:handle HDR Handler
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime	O	1..1	dateTime	Date and time of the approval of the document by Attester Obligations Actor SHOULD:handle HDR Handler
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle HDR Handler
legalAuthenticator[x]	O	1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it) Obligations Actor SHOULD:handle HDR Handler
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime	O	1..1	dateTime	Date and time when the document was authorised Obligations Actor SHOULD:handle HDR Handler
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
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle HDR Handler
intendedRecipient[x]	O	0..*		Intended recipient(s) of the information, i.e. a person or organisation that should be notified or be aware of the content. This element is used to indicate explicit communication intent and does not represent routine storage or passive availability of information (e.g. in portals). Listing an intended recipient does not create an assignment or responsibility. Obligations Actor MAY:able-to-populate HDR Handler
intendedRecipientMyHealthEuPatient			MyHealthEuPatient
intendedRecipientEHDSRelatedPerson			EHDSRelatedPerson
intendedRecipientMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
intendedRecipientMyHealthEuOrganisation			MyHealthEuOrganisation
presentedForm		0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
body	O	0..1	Base	Structured body of the discharge report document Obligations Actor SHALL:handle HDR Handler
alerts	O	0..1	Base	Section: Alerts. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicalAlert	O	0..*	MyHealthEuHdrAlert	Description of medical alerts in textual format: any clinical information that is imperative to know so that the life or health of the patient does not come under threat. Obligations Actor MAY:able-to-populate HDR Handler
encounterInformation	O	1..1	Base	Section: Encounter information. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
encounter	O	0..1	MyHealthEuHdrEncounter	Encounter information Obligations Actor SHALL:handle HDR Handler
note		0..1	string	Free text notes by the health professional
admissionEvaluation	O	0..1	Base	Section: Admission evaluation. Admission evaluation section should be reported only if it is relevant to ensure continuity of care. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the evaluation performer
patientHistory	O	0..1	Base	Section: Patient health history (anamnesis) containing only information that is highly relevant for this specific episode of care. The model is designed with the expectation that patient summary is available. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section. In case the section includes structured information, it should also be included in generatedNarrative.
note		0..1	string	Free text notes by the health professional
courseOfEncounter	O	0..1	Base	Course of inpatient or outpatient encounter. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
diagnosticSummary	O	0..*	MyHealthEuHdrCondition	Problems that were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the encounter. At least one treated problem should be marked. Other problems are recorded only if they are important for continuity of care (after discharge). Obligations Actor SHALL:handle HDR Handler
procedures	O	0..*	MyHealthEuHdrProcedure	Procedures performed during encounter which are significant for continuity of care, e.g. surgeries and other instrumental interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. Diagnostic procedures are typically captured as observation results and not repeated here. Obligations Actor MAY:able-to-populate HDR Handler
medicalDevicesAndImplants	O	0..*	MyHealthEuHdrDeviceUse	Medical devices (including implants) whose use was started, stopped, or otherwise modified during the encounter. Obligations Actor MAY:able-to-populate HDR Handler
pharmacotherapy	O	0..*	MyHealthEuHdrMedicationUse	Significant medication treatments during encounter. The content of this section may be repeated in the medication summary for full overview of patient's medications. Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings		0..*	EHDSObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination. The line between objective findings and test results is not clear and it is up to the implementers to decide how to logically display different measurements.
testResults		0..*	EHDSObservation	Significant medical test results of functional, diagnostic (including laboratory), and imaging examinations performed during encounter. This may include orders for which the results have not yet arrived.
note		0..1	string	Free text notes by the health professional
dischargeDetails	O	0..1	Base	Discharge details Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the health professional
medicationSummary	O	0..1	Base	Summary information on the medication recommended for the period after discharge, indicating whether the medication is changed or newly started. Compared to previous practices, the overview is supplemented with medication that has been discontinued. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicationUse	O	1..1	MyHealthEuHdrMedicationUse	Details about medication and dosage Obligations Actor MAY:able-to-populate HDR Handler
note		0..1	string	Free text notes by the health professional
carePlan	O	0..1	Base	Care plan and other recommendations after discharge. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
carePlan	O	0..*	MyHealthEuHdrCarePlan	Structured care plan after discharge. Multiple care plans could be provided. Obligations Actor MAY:able-to-populate HDR Handler
otherRecommendations		0..1	string	Other recommendations (advice) after discharge. E.g., recommendation to suggest hip replacement, reduce number of cigarettes, stop smoking, increase physical exercises, etc.
synthesis		0..1	string	Clinical synthesis (e.g. description of reasons and course of encounter) clustered by managed conditions. Clinical synthesis may include clinical reasoning (differential diagnostics, explanation of clinical context) in clinically complex conditions.
attachments	O	0..*	EHDSAttachment	Report attachments. Implementations may define what kind of attachments are allowed and may ignore unexpected attachments for security reasons. Obligations Actor MAY:able-to-populate HDR Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHdrDischargeReport.​header.language	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.documentType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.eventType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.serviceSpecialty	Base	preferred		Not State	Unknown

Differential View

This structure is derived from EHDSDischargeReport

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHdrDischargeReport		0..*	EHDSDischargeReport	MyHealth@EU Hospital Discharge Report model Elements defined in Ancestors:header, header, presentedForm, body, attachments
header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle HDR Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle HDR Handler
author[x]	O	1..*		The author of the report. Obligations Actor SHALL:handle HDR Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle HDR Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle HDR Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Obligations Actor SHALL:handle HDR Handler
documentType	O	1..1	CodeableConcept	Type of the document (e.g. '34105-7 Hospital discharge summary) Obligations Actor SHALL:handle HDR Handler
documentTitle	O	1..1	string	Title of the document, possibly autogenerated from the structured fields (e.g. 'Hospital discharge report. Jane Green. 07.10.2025-10.10.2025') Obligations Actor SHALL:handle HDR Handler
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle HDR Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate HDR Handler
attester[x]	O	1..1		Attester who validated the document Obligations Actor SHOULD:handle HDR Handler
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime	O	1..1	dateTime	Date and time of the approval of the document by Attester Obligations Actor SHOULD:handle HDR Handler
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle HDR Handler
legalAuthenticator[x]	O	1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it) Obligations Actor SHOULD:handle HDR Handler
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime	O	1..1	dateTime	Date and time when the document was authorised Obligations Actor SHOULD:handle HDR Handler
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle HDR Handler
intendedRecipient[x]	O	0..*		Intended recipient(s) of the information, i.e. a person or organisation that should be notified or be aware of the content. This element is used to indicate explicit communication intent and does not represent routine storage or passive availability of information (e.g. in portals). Listing an intended recipient does not create an assignment or responsibility. Obligations Actor MAY:able-to-populate HDR Handler
intendedRecipientMyHealthEuPatient			MyHealthEuPatient
intendedRecipientEHDSRelatedPerson			EHDSRelatedPerson
intendedRecipientMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
intendedRecipientMyHealthEuOrganisation			MyHealthEuOrganisation
body	O	0..1	Base	Structured body of the discharge report document Obligations Actor SHALL:handle HDR Handler
alerts	O	0..1	Base	Section: Alerts. Obligations Actor MAY:able-to-populate HDR Handler
medicalAlert	O	0..*	MyHealthEuHdrAlert	Description of medical alerts in textual format: any clinical information that is imperative to know so that the life or health of the patient does not come under threat. Obligations Actor MAY:able-to-populate HDR Handler
encounterInformation	O	1..1	Base	Section: Encounter information. Obligations Actor SHALL:handle HDR Handler
encounter	O	0..1	MyHealthEuHdrEncounter	Encounter information Obligations Actor SHALL:handle HDR Handler
admissionEvaluation	O	0..1	Base	Section: Admission evaluation. Admission evaluation section should be reported only if it is relevant to ensure continuity of care. Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
patientHistory	O	0..1	Base	Section: Patient health history (anamnesis) containing only information that is highly relevant for this specific episode of care. The model is designed with the expectation that patient summary is available. Obligations Actor MAY:able-to-populate HDR Handler
courseOfEncounter	O	0..1	Base	Course of inpatient or outpatient encounter. Obligations Actor SHALL:handle HDR Handler
diagnosticSummary	O	0..*	MyHealthEuHdrCondition	Problems that were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the encounter. At least one treated problem should be marked. Other problems are recorded only if they are important for continuity of care (after discharge). Obligations Actor SHALL:handle HDR Handler
procedures	O	0..*	MyHealthEuHdrProcedure	Procedures performed during encounter which are significant for continuity of care, e.g. surgeries and other instrumental interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. Diagnostic procedures are typically captured as observation results and not repeated here. Obligations Actor MAY:able-to-populate HDR Handler
medicalDevicesAndImplants	O	0..*	MyHealthEuHdrDeviceUse	Medical devices (including implants) whose use was started, stopped, or otherwise modified during the encounter. Obligations Actor MAY:able-to-populate HDR Handler
pharmacotherapy	O	0..*	MyHealthEuHdrMedicationUse	Significant medication treatments during encounter. The content of this section may be repeated in the medication summary for full overview of patient's medications. Obligations Actor MAY:able-to-populate HDR Handler
dischargeDetails	O	0..1	Base	Discharge details Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
medicationSummary	O	0..1	Base	Summary information on the medication recommended for the period after discharge, indicating whether the medication is changed or newly started. Compared to previous practices, the overview is supplemented with medication that has been discontinued. Obligations Actor MAY:able-to-populate HDR Handler
medicationUse	O	1..1	MyHealthEuHdrMedicationUse	Details about medication and dosage Obligations Actor MAY:able-to-populate HDR Handler
carePlan	O	0..1	Base	Care plan and other recommendations after discharge. Obligations Actor MAY:able-to-populate HDR Handler
carePlan	O	0..*	MyHealthEuHdrCarePlan	Structured care plan after discharge. Multiple care plans could be provided. Obligations Actor MAY:able-to-populate HDR Handler
attachments	O	0..*	EHDSAttachment	Report attachments. Implementations may define what kind of attachments are allowed and may ignore unexpected attachments for security reasons. Obligations Actor MAY:able-to-populate HDR Handler
Documentation for this format

Snapshot View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHdrDischargeReport		0..*	EHDSDischargeReport	MyHealth@EU Hospital Discharge Report model Elements defined in Ancestors:header, header, presentedForm, body, attachments
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle HDR Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle HDR Handler
author[x]	O	1..*		The author of the report. Obligations Actor SHALL:handle HDR Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle HDR Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle HDR Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle HDR Handler
documentType	O	1..1	CodeableConcept	Type of the document (e.g. '34105-7 Hospital discharge summary) Binding Description: (preferred): LOINC Obligations Actor SHALL:handle HDR Handler
documentTitle	O	1..1	string	Title of the document, possibly autogenerated from the structured fields (e.g. 'Hospital discharge report. Jane Green. 07.10.2025-10.10.2025') Obligations Actor SHALL:handle HDR Handler
period		0..1	Period	Time of service that is being documented (typically the same as the time/period of encounter)
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle HDR Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate HDR Handler
attester[x]	O	1..1		Attester who validated the document Obligations Actor SHOULD:handle HDR Handler
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime	O	1..1	dateTime	Date and time of the approval of the document by Attester Obligations Actor SHOULD:handle HDR Handler
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle HDR Handler
legalAuthenticator[x]	O	1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it) Obligations Actor SHOULD:handle HDR Handler
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime	O	1..1	dateTime	Date and time when the document was authorised Obligations Actor SHOULD:handle HDR Handler
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
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle HDR Handler
intendedRecipient[x]	O	0..*		Intended recipient(s) of the information, i.e. a person or organisation that should be notified or be aware of the content. This element is used to indicate explicit communication intent and does not represent routine storage or passive availability of information (e.g. in portals). Listing an intended recipient does not create an assignment or responsibility. Obligations Actor MAY:able-to-populate HDR Handler
intendedRecipientMyHealthEuPatient			MyHealthEuPatient
intendedRecipientEHDSRelatedPerson			EHDSRelatedPerson
intendedRecipientMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
intendedRecipientMyHealthEuOrganisation			MyHealthEuOrganisation
presentedForm		0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
body	O	0..1	Base	Structured body of the discharge report document Obligations Actor SHALL:handle HDR Handler
alerts	O	0..1	Base	Section: Alerts. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicalAlert	O	0..*	MyHealthEuHdrAlert	Description of medical alerts in textual format: any clinical information that is imperative to know so that the life or health of the patient does not come under threat. Obligations Actor MAY:able-to-populate HDR Handler
encounterInformation	O	1..1	Base	Section: Encounter information. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
encounter	O	0..1	MyHealthEuHdrEncounter	Encounter information Obligations Actor SHALL:handle HDR Handler
note		0..1	string	Free text notes by the health professional
admissionEvaluation	O	0..1	Base	Section: Admission evaluation. Admission evaluation section should be reported only if it is relevant to ensure continuity of care. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the evaluation performer
patientHistory	O	0..1	Base	Section: Patient health history (anamnesis) containing only information that is highly relevant for this specific episode of care. The model is designed with the expectation that patient summary is available. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section. In case the section includes structured information, it should also be included in generatedNarrative.
note		0..1	string	Free text notes by the health professional
courseOfEncounter	O	0..1	Base	Course of inpatient or outpatient encounter. Obligations Actor SHALL:handle HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
diagnosticSummary	O	0..*	MyHealthEuHdrCondition	Problems that were treated or affected provisioning of care (diagnostics, therapy, nursing, monitoring) during the encounter. At least one treated problem should be marked. Other problems are recorded only if they are important for continuity of care (after discharge). Obligations Actor SHALL:handle HDR Handler
procedures	O	0..*	MyHealthEuHdrProcedure	Procedures performed during encounter which are significant for continuity of care, e.g. surgeries and other instrumental interventions (endoscopic, intravascular), chemotherapy, radiotherapy, purification methods (dialysis, hemoperfusion), circulation support methods (counterpulsation, etc.), administration of blood derivatives or others. Diagnostic procedures are typically captured as observation results and not repeated here. Obligations Actor MAY:able-to-populate HDR Handler
medicalDevicesAndImplants	O	0..*	MyHealthEuHdrDeviceUse	Medical devices (including implants) whose use was started, stopped, or otherwise modified during the encounter. Obligations Actor MAY:able-to-populate HDR Handler
pharmacotherapy	O	0..*	MyHealthEuHdrMedicationUse	Significant medication treatments during encounter. The content of this section may be repeated in the medication summary for full overview of patient's medications. Obligations Actor MAY:able-to-populate HDR Handler
objectiveFindings		0..*	EHDSObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination. The line between objective findings and test results is not clear and it is up to the implementers to decide how to logically display different measurements.
testResults		0..*	EHDSObservation	Significant medical test results of functional, diagnostic (including laboratory), and imaging examinations performed during encounter. This may include orders for which the results have not yet arrived.
note		0..1	string	Free text notes by the health professional
dischargeDetails	O	0..1	Base	Discharge details Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
objectiveFindings	O	0..*	MyHealthEuHdrObservation	Objective findings, such as anthropometric measurements, vital signs, or objective anatomical findings of physical examination Obligations Actor MAY:able-to-populate HDR Handler
functionalStatus[x]	O	0..*		An individual's ability to perform normal daily activities required to meet basic needs, fulfil usual roles and maintain health and well-being Obligations Actor MAY:able-to-populate HDR Handler
functionalStatusMyHealthEuHdrCondition			MyHealthEuHdrCondition
functionalStatusMyHealthEuHdrObservation			MyHealthEuHdrObservation
note		0..1	string	Free text notes by the health professional
medicationSummary	O	0..1	Base	Summary information on the medication recommended for the period after discharge, indicating whether the medication is changed or newly started. Compared to previous practices, the overview is supplemented with medication that has been discontinued. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
medicationUse	O	1..1	MyHealthEuHdrMedicationUse	Details about medication and dosage Obligations Actor MAY:able-to-populate HDR Handler
note		0..1	string	Free text notes by the health professional
carePlan	O	0..1	Base	Care plan and other recommendations after discharge. Obligations Actor MAY:able-to-populate HDR Handler
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
carePlan	O	0..*	MyHealthEuHdrCarePlan	Structured care plan after discharge. Multiple care plans could be provided. Obligations Actor MAY:able-to-populate HDR Handler
otherRecommendations		0..1	string	Other recommendations (advice) after discharge. E.g., recommendation to suggest hip replacement, reduce number of cigarettes, stop smoking, increase physical exercises, etc.
synthesis		0..1	string	Clinical synthesis (e.g. description of reasons and course of encounter) clustered by managed conditions. Clinical synthesis may include clinical reasoning (differential diagnostics, explanation of clinical context) in clinically complex conditions.
attachments	O	0..*	EHDSAttachment	Report attachments. Implementations may define what kind of attachments are allowed and may ignore unexpected attachments for security reasons. Obligations Actor MAY:able-to-populate HDR Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHdrDischargeReport.​header.language	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.documentType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.eventType	Base	preferred		Not State	Unknown
MyHealthEuHdrDischargeReport.​header.serviceSpecialty	Base	preferred		Not State	Unknown

This structure is derived from EHDSDischargeReport

Summary