This profile defines obligations for the Hospital Discharge Report for the scope of this guide.

This profile defines obligations for a Hospital Discharge Report (HDR) for the scope of this guide.

This profile defines obligations for the AllergyIntolerance resource for the purpose of this project.

This profile defines obligations for the CarePlan resource for the purpose of this guide.

This profile defines obligations for the Condition in the scope of this guide. It supports the Diagnostic summary part of the eHN data model adding two additional categories: first category distinguishes conditions present at admission and acquired during hospital stay, while second category is used to indicate impact of the condition to the treatment during hospital stay (treated, untreated).

This profile represents the constraints applied to the Device resource for the purpose of this guide. A device used by or implanted on the patient is described in the hospital discharge report as an instance of a Device resource constrained by this profile.

This profile represents the constraints applied to the DeviceUseStatement resource for the purpose of this guide. A device used by or implanted on the patient is described in the hospital discharge report as an instance of a Device resource constrained by this profile.

This profile defines obligations for Inpatient Encounter in HL7 FHIR for the scope of this guide.

This profile defines obligations for the Flag resource to represent alerts or warnings in FHIR for the purpose of this project.

This profile defines obligations for an human Patient name in FHIR for the purpose of this guide.

This profile defines obligations for the Immunization resource for the purpose of this guide.

This profile defines obligations for laboratory observations in the scope of this guide.

This profile defines obligations for the Medication resource for the purpose of this guide, adapted from the MPD work.

This profile defines obligations for the MedicationAdministration resource for the purpose of this guide, adapted from the MPD work.

This profile defines obligations for the MedicationDispense resource for the purpose of this guide, adapted from the MPD work.

This profile defines obligations for the MedicationRequest resource for the purpose of this guide, adapted from the MPD work.

This profile defines obligations for the MedicationStatement resource for the purpose of this guide, adapted from the MPD work.

This profile defines obligations for observations in the scope of this guide.

This profile defines obligations for an organization in FHIR for the purpose of this guide.

This profile defines obligations for a human Patient in FHIR for the purpose of this guide.

This profile defines obligations for a health professional represented as a Practitioner in FHIR for the purpose of this guide.

This profile defines obligations for a health professional role in FHIR for the purpose of this guide.

This profile defines obligations for the Procedure resource by this guide.

This profile defines obligations for a related person in FHIR for the purpose of this guide.

This profile defines obligations for Specimen in FHIR for the purpose of this guide.

Clinical document used to represent a Hospital Discharge Report for the scope of this guide.

This profile constrains the CarePlan resource for the purpose of this guide.

Clinical document used to represent a Hospital Discharge Report (HDR) for the scope of this guide.

This profile represents the constraints applied to the Device resource for the purpose of this guide. A device used by or implanted on the patient is described in the hospital discharge report as an instance of a Device resource constrained by this profile.

This profile represents the constraints applied to the DeviceUseStatement resource for the purpose of this guide. A device used by or implanted on the patient is described in the hospital discharge report as an instance of a Device resource constrained by this profile.

This profile defines how to represent Inpatient Encounter in HL7 FHIR for the scope of this guide.

Goal profile aligned with the Care Plan logical model.

This profile constrains the MedicationAdministration resource for the purpose of this guide, adapted from the MPD work.

This profile constrains the MedicationDispense resource for the purpose of this guide, adapted from the MPD work.

Hospital Discharge Report Admission Urgency value set includes selected codes from HL7 v3-ActPriority code system.

Hospital Discharge Report Condition value set includes selected codes from recommended EU code systems for health conditions (WHO-ICD-10, SNOMED CT and Orphacodes).

Hospital Discharge Report Document Category value set includes concepts from the LOINC code system that are used to classify the document as a discharge summary note.

Hospital Discharge Report Encounter Class value set includes codes from the HL7 v3-ActCode code system that are used to classify the general type of inpatient encounter.

Hospital Discharge Report Encounter Status value set includes codes from the FHIR R4 EncounterStatus code system that are used to represent the state of the inpatient encounter.

Hospital Discharge Report Encounter Type value set includes concepts from SNOMED CT descendants of 225351009 (Care provision regime) that are used to classify the care provision regimen during the inpatient encounter.

A high-priority allergy to Penicillin, with a specific reaction and severity.

HL7 FHIR Bundle example for HL7 Europe Hospital Discharge Report (HDR) Luigi De Luca.

HL7 FHIR Bundle example for HL7 Europe Hospital Discharge Report (HDR) Reijer Wolff.

HL7 FHIR Bundle example for HL7 Europe Hospital Discharge Report (HDR) Paolo Marcheschi.

HL7 FHIR Bundle example for HL7 Europe Hospital Discharge Report (HDR) Fiona Swart.

Care plan for diabetes management, including referrals and HbA1c measurement.

HL7 FHIR Composition example for HL7 Europe Hospital Discharge Report (HDR) Luigi De Luca

Condition representing type 2 diabetes mellitus, coded with ICD-10 and SNOMED CT.

A system that receives electronic health data originating from another system and processes or displays that data. In this role, the system is responsible for ingesting and validating the received data and for preserving the meaning, structure, and associated metadata of the information in accordance with the applicable Consumer obligations, ensuring correct interpretation and presentation to end users or other systems.

A sample Device resource for an implantable pacemaker, referenced in a DeviceUseStatement.

A DeviceUseStatement documenting the use of an implanted pacemaker in the hospital discharge report.

A sample Encounter resource for a hospital admission and discharge.

Mother has a history of type 2 diabetes mellitus.

A high-priority allergy alert referencing the specific AllergyIntolerance resource.

A clinical flag advising care teams to avoid using the patient's left arm for procedures.

An example record of an administered COVID-19 vaccine dose.

1A. Cefuroxime 1500mg (1.5g) powder for solution in a vial. Generic product, defined by attributes.

1C. Cefuroxime 1500mg (1.5g) powder for solution in a vial (10 vials per package). Branded packaged product, defined by attributes.

A sample MedicationAdministration resource for Paracetamol.

400D-1. Medication dispense fulfilling the first part of the order: 1 package containing 10 vials.

400C. A prescription/request with one medication and changing dosage. Uses the 'actionable' tag. Cefuroxime sodium.

A sample MedicationStatement for a patient taking Enalapril, used in the context of the European Hospital Discharge Report.

ABO blood group type in blood.

Vital signs observation representing the body weight of the patient.

Organization representing the Erasmus MC, Sophia kinderziekenhuis.

Patient resource representing Fiona Swart, a Dutch patient.

A planned cesarean section procedure.

A system that generates or makes available structured electronic health data for exchange. In this role, the system is responsible for being technically capable of populating the relevant data elements in accordance with the applicable “able-to-populate” obligations and for associating the required metadata, such as authorship, provenance, status, and temporal information, before the data are made available to downstream systems.