Modernization and digitalization projects for a sustainable infrastructure.

Medical communication

The Medical Communication subsystem represents a software solution that serves doctor-to-doctor communication as part of the provision of consulting services. Here, different medical data (documents, structured data, image data) are compiled on a case-by-case basis, medically evaluated across institutions, discussed professionally with the help of video conferencing systems, if necessary, and finally assessed. The target group for this portal are the HDZ clinics with their medical and non-medical staff, as well as referrers and cooperation partners as medical institutions with their respective personnel.

It includes in particular:

- An electronic case file

- Videoconferencing systems

- Virtual case conferences with joint findings analysis

- Data exchange between fixed specialist clinics (virtual center)

Patient communication

The “Patient Communication” subsystem is intended to map the digital processes in the areas of intake management, treatment management, and discharge and transfer management. It thus represents the central interfaces for digital communication between patients and the HDZ with its core IT components. The aim is to relieve and speed up administrative processes in the hospital on the one hand and to support the patient before, during and after the inpatient treatment process on the other.

Although the subsystem is referred to as “patient communication”, three different usage paths are required from the patient's point of view for the technical implementation of the desired functions:

- A browser-based web portal should, in particular, offer digital services prior to treatment;

- a patient kiosk/terminal is intended to support check-in for outpatient or inpatient treatment and, in addition to web-based functions, offer special business incidents using the insurance card (eGK), which cannot be technologically mapped via the browser-based web portal (e.g. reading out the eMP or EPA rights management)

- a patient app that functions as a convenient interface between hospital systems and the patient during the inpatient or outpatient stay and displays information, appointments and data for the patient in connection with the individual treatment steps.

Medical Data Warehouse AI I Structural Data

The Medical Data Warehouse (MDW) AI I and MDW AI II subsystems will provide the data basis for medical decision-making processes in two expansion stages, which can make data-driven recommendations for treatment courses on the basis of AI algorithms and make predictions about the probability of complications that will occur. In stage I of the solution, all

3/10

structures existing HDZ data as well as the corresponding documents as a data basis for the MDW.

The first expansion stage comprises:

- Collection of structured data, cross-system data storage with real-time data

- Identification of medical data that is relevant for patient and case-related storage in the MDW (building a so-called “digital twin”)

- Building a database with comparative data

- Target/actual reconciliation with the support of AI

The following use cases are planned:

- The analysis of intraoperative data (anesthesia, heart/lung machine) is intended to monitor the course of surgery and generate warnings for deviations

- Based on the inpatient treatment data, warnings about an abnormal course of treatment should be generated and displayed in the HIS

- Based on inpatient and outpatient treatment data, decision support should be generated for the indication of the implantation of a mechanical circulatory support system (VAD).

Medical Data Warehouse AI II image data

The Medical Data Warehouse (MDW) AI I and MDW AI II subsystems will provide the data basis for medical decision-making processes in two expansion stages, which can make data-driven recommendations for treatment courses on the basis of AI algorithms and make predictions about the probability of complications that will occur. In stage I of the solution, all structured HDZ data and the corresponding documents are available as the data basis for the MDW.

The first expansion stage comprises:

- Add image data and patterns and artifacts derived from image data

The following use case is planned:

- The use case is intended to support the question of whether a disorder of the aortic valve can be treated by catheters or surgery.

Allocation in lots

The subsystems described are awarded in two lots. The first lot (LOT A) is the “Medical Communication” subsystems in Section 4.4 and “Patient Communication” in Section 4.5. The second lot (LOT B) consists of the Medical Data Warehouse (MDW) KI I and MDW KI II subsystems in sections 4.6 and 4.7.

Medical communication

The Medical Communication subsystem represents a software solution that serves doctor-to-doctor communication as part of the provision of consulting services. Here, different medical data (documents, structured data, image data) are compiled on a case-by-case basis, medically evaluated across institutions, discussed professionally with the help of video conferencing systems, if necessary, and finally assessed. The target group for this portal are the HDZ clinics with their medical and non-medical staff, as well as referrers and cooperation partners as medical institutions with their respective personnel.

It includes in particular:

- An electronic case file

- Videoconferencing systems

- Virtual case conferences with joint findings analysis

- Data exchange between fixed specialist clinics (virtual center)

Patient communication

The “Patient Communication” subsystem is intended to map the digital processes in the areas of intake management, treatment management, and discharge and transfer management. It thus represents the central interfaces for digital communication between patients and the HDZ with its core IT components. The aim is to relieve and speed up administrative processes in the hospital on the one hand and to support the patient before, during and after the inpatient treatment process on the other.

Although the subsystem is referred to as “patient communication”, three different usage paths are required from the patient's point of view for the technical implementation of the desired functions:

- A browser-based web portal should, in particular, offer digital services prior to treatment;

- a patient kiosk/terminal is intended to support check-in for outpatient or inpatient treatment and, in addition to web-based functions, special business incidents using the insurance card

5/10

(eGK) that cannot be displayed technologically via the browser-based web portal (e.g. reading out the eMP or rights management of the EPO)

- a patient app that functions as a convenient interface between hospital systems and the patient during the inpatient or outpatient stay and displays information, appointments and data for the patient in connection with the individual treatment steps.

Medical Data Warehouse AI I Structural Data

The Medical Data Warehouse (MDW) AI I and MDW AI II subsystems will provide the data basis for medical decision-making processes in two expansion stages, which can make data-driven recommendations for treatment courses on the basis of AI algorithms and make predictions about the probability of complications that will occur. In stage I of the solution, all structured HDZ data and the corresponding documents are available as the data basis for the MDW.

The first expansion stage comprises:

- Collection of structured data, cross-system data storage with real-time data

- Identification of medical data that is relevant for patient and case-related storage in the MDW (building a so-called “digital twin”)

- Building a database with comparative data

- Target/actual reconciliation with the support of AI

The following use cases are planned:

- The analysis of intraoperative data (anesthesia, heart/lung machine) is intended to monitor the course of surgery and generate warnings for deviations

- Based on the inpatient treatment data, warnings about an abnormal course of treatment should be generated and displayed in the HIS

- Based on inpatient and outpatient treatment data, decision support should be generated for the indication of the implantation of a mechanical circulatory support system (VAD).

Medical Data Warehouse AI II image data

The Medical Data Warehouse (MDW) AI I and MDW AI II subsystems will provide the data basis for medical decision-making processes in two expansion stages, which can make data-driven recommendations for treatment courses on the basis of AI algorithms and make predictions about the probability of complications that will occur. In stage I of the solution, all structured HDZ data and the corresponding documents are available as the data basis for the MDW.

The first expansion stage comprises:

- Add image data and patterns and artifacts derived from image data

The following use case is planned:

- The use case is intended to support the question of whether a disorder of the aortic valve can be treated by catheters or surgery.

Allocation in lots

The subsystems described are awarded in two lots. The first lot (LOT A) is the “Medical Communication” subsystems in Section 4.4 and “Patient Communication” in Section 4.5. The second lot (LOT B) consists of the Medical Data Warehouse (MDW) KI I and MDW KI II subsystems in sections 4.6 and 4.7.