MyHealth@Eu Hospital Discharge Report
9.1.0 - qa-preview 150

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

HDR Models Overview

MyHealth@EU logical models (MyHealth@EU Hospital Discharge Report Content) refine the EHDS logical information models provided by the Xt-EHR project. These models use obligations on the logical models to highlight the elements identified by the MyHealth@EU Functional Requirements. Three types of obligations are defined based on the MyHealth@EU requirements:

  • Mandatory: the data element must be provided
  • Required: the data element must be provided, although exceptional justifications can be provided
  • Optional: the data element can be completely omitted

These obligations are implemented using the following rule sets:

  • ObligationMandatory - SHALL:handle for mandatory elements
  • ObligationRequired - SHOULD:handle for required elements
  • ObligationOptional - MAY:able-to-populate for optional elements

Information Models

Hospital Discharge Report

The hospital discharge report is structured using the MyHealthEuHdrDischargeReport model which is divided into a document header, a structured body with multiple clinical sections, and optional attachments.

MyHealthEuHdrDischargeReportHeaderSubject (MyHealthEuPatient)IdentifierAuthor (MyHealthEuHealthProfessional/Organisation/Device)DateStatusLanguageDocument TypeDocument TitleVersionCustodian (MyHealthEuOrganisation)AttestationAttester (MyHealthEuHealthProfessional/Device)DatetimeLegal AuthenticationLegal Authenticator (MyHealthEuHealthProfessional/Organisation)DatetimeIntended Recipient (MyHealthEuPatient/HealthProfessional/Organisation)BodyAlertsAllergy/Intolerance (MyHealthEuHdrAllergyIntolerance)Medical Alert (MyHealthEuHdrAlert)Encounter InformationEncounter (MyHealthEuHdrEncounter)Type / PeriodAdmission / DischargeService ProviderReasonAdmission EvaluationObjective Findings (MyHealthEuHdrObservation)Functional Status (MyHealthEuHdrCondition/Observation)Patient HistoryPast Problems (MyHealthEuHdrCondition)Devices and Implants (MyHealthEuHdrDeviceUse)Procedures (MyHealthEuHdrProcedure)Course of EncounterDiagnostic Summary (MyHealthEuHdrCondition)Procedures (MyHealthEuHdrProcedure)Medical Devices (MyHealthEuHdrDeviceUse)Pharmacotherapy (MyHealthEuHdrMedicationUse)Test Results (MyHealthEuHdrObservation)Discharge DetailsObjective Findings (MyHealthEuHdrObservation)Functional Status (MyHealthEuHdrCondition/Observation)Medication SummaryMedication Use (MyHealthEuHdrMedicationUse)Care PlanCare Plan (MyHealthEuHdrCarePlan)Other RecommendationsAttachments

The body of the report covers the following clinical sections:

  • Alerts – allergies, intolerances and medical alerts relevant to the hospital stay
  • Encounter information – details of the inpatient encounter including admission and discharge
  • Admission evaluation – objective findings and functional status at admission (if relevant)
  • Patient history – past problems, devices, and procedures relevant to the current episode
  • Course of encounter – diagnostic summary, significant procedures, devices, pharmacotherapy, and test results during hospitalisation
  • Discharge details – objective findings and functional status at discharge
  • Medication summary – medication recommended after discharge
  • Care plan – care plan and other recommendations after discharge

Encounter

The encounter is described using the MyHealthEuHdrEncounter model, capturing admission and discharge details, service provider, reason for admission, and locations visited during the stay.

Clinical Content Models

Clinical content within the report body is described by the following models:

Detail MyHealth@EU information models for Hospital Discharge Report

Core Models Used

The MyHealth@EU HDR models utilize the following core models:

Supporting Information