MyHealth@Eu Medical Imaging Report
9.1.1 - ci-build
150
MyHealth@Eu Medical Imaging Report - Local Development build (v9.1.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
MyHealth@EU logical models 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:
These obligations are implemented using the following rule sets:
ObligationMandatory - SHALL:handle for mandatory elementsObligationRequired - SHOULD:handle for required elementsObligationOptional - MAY:able-to-populate for optional elementsThe diagram below shows the dependencies between the MyHealth@EU imaging logical models:
The imaging report is structured using the MyHealthEuImagingReport model, which could be divided into several parts: a document header, a body containing the examination report, and optionally DICOM study metadata and attachments.
The header captures administrative and identification information such as the subject, author, status, document type, legal authentication, and accession number. The body contains the clinical content of the report, including order information, examination findings, conclusions, and recommendations. The dicomStudyMetadata element links the report to the associated imaging study described by the MyHealthEuImagingStudy model.
The imaging study metadata is structured using the MyHealthEuImagingStudy model. This model captures the DICOM study information including modality, body site, study endpoint, and the series with their instances. Key images within each series instance are marked as required by the MyHealth@EU requirements.
Following actors have been specified:
The MyHealth@EU imaging models utilize the following core models: