Implementation of a patient portal with app for iOS/Android/desktop and other device classes (bedside terminals, self-service terminals) for the aforementioned clinics within the meaning of KHZG FTB 2 (§19 para. 1 sentence 2 KHSFV) in 4 lots: Here Lot 1: Implementation of a patient portal framework with appointment management and implementation of the UI/UX recommendations from Lot 2 and existing CI specifications as well as connection of the headless CMS for editorial content from Lot 3 for the five aforementioned clinics of the Immanuel Albertinen Diakonie

LOT-0001
Patientenportal_Los_1_Framework.
In this project, a patient portal framework with APP for iOS/Android/desktop as well as other device classes (beside terminals, self-service terminals) is to be procured and implemented. This framework essentially provides the following functions: -Uniform and secure authentication mechanism and onboarding process -Account management with family/proxy function -File upload and file download -Interface functions -Administrative backend for use by internal departments -Connection of smart devices and medical technology -Visually uniform interface for operation regardless of which functions are provided by the framework itself or in tools connected via interfaces -Functions that at least meet the MUST criteria of the KHZG FTB 2 -Appointment visualization and extended appointment management Furthermore, the framework ensures that other digital value-added applications (including telemedical applications) and appointment management can be integrated and made available to patients. To persist primary health data and administrative data, an existing clinical data repository (CDR) must be used. There is no independent persistence by a patient portal framework. Communication with the CDR takes place via a DMZ (demilitarized zone) that has yet to be procured as a temporary intermediate storage. The existing workflow engine is used to control the processes and data flows. The patient portal framework must ensure that the processes defined on the workflow engine are automatically implemented in the patient portal framework. The patient portal will be operated on-premise. Appointment management can be hosted both on-premise and externally. It is important that the appointment management can be used standa-lone and autonomously from the patient portal in order to be able to map further use cases in MVZs, outpatient clinics and other facilities of the Immanuel Albertinen Diakonie in the future. The security mechanisms of the patient portal must correspond to the current state of the art. The relevant hospitals are currently using two different HIS systems, which must be connected bidirectionally to the framework via suitable interfaces. In order to be able to optimize other internal processes, the creation of editorial content is carried out in a separate, central and yet to be procured headless content management system (CMS), which provides existing content from other sources, e.g. the clinic websites, that can be used for the patient portal. As a result, the framework must work with this CMS via standardized interfaces in order to use the existing editorial content. The patient portal framework to be developed must interoperate with the headless content management system described in Lot 3. This includes the ability to seamlessly receive content from the CMS and display it correctly in the patient portal. User-centricity or user-orientation in user-centered design is one of the most important principles for a good user experience, optimal usability and thus the greatest possible acceptance among both patients and professional users. The core of user-centricity is to design products and processes according to the needs of the actual users (users), i.e. to place the user at the center of all considerations. To this end, user experience workshops will be held and the patient portal will be adapted according to the identified user needs and the applicable corporate design guidelines of the clinics. (For more details, see esp. 03.0_Projektbeschreibung_Auswahlmatrix_Teilnahmewettbewerb, 13_Anlage_unverbindlicher_Vorentwurf_Kriterienkatalog(#IAP-1092). Note: (probably)Factual need for negotiation of the AG (subject to additions)= Hosting Appointment Management (we would like to point out that this information is non-binding and serves to ensure the greatest possible transparency. Please note that further negotiations are reserved): It is intended to put out to tender an extended appointment management in connection with the patient portal framework. For this purpose, a catalogue of content requirements was created. The aim of the tender is to find the best possible solution for the needs of the contracting authorities. As things stand at present, the aim of a negotiation should therefore be to offer the market the opportunity to present different approaches in order to achieve the said objectives in the best possible way. The mandatory requirements of the KHZG and its ancillary regulations are non-negotiable. In particular, the relevant "must-have criteria" of the funding guidelines pursuant to Section 21 (2) KHSFV are non-negotiable (in this case, funding event 2). For more information, please refer to the declaration to be submitted 05.7_Eigenerklärung_KHZG_Richtlinie_FTB2 The must criteria in 13_Anlage_unverbindlicher_Vorentwurf_Kriterienkatalog are non-negotiable.