Tenders Are Invited For Industry Specific Software Package – Patientenportal_Los_1_Framework

Industry Specific Software Package – 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/Deputy Function -File Upload And File Download -Interface Functions -Administrative Backend For Use By Internal Departments -Connection Of Smart Devices And Medical Technology -Optically Uniform Interface For Operation Regardless Of Which Functions Are Carried Out By The Framework Itself Or In Tools Connected Via Interfaces -Functions That At Least Correspond To The Must Criteria Of The Khzg Ftb 2 -Appointment Visualization And Extended Appointment Management Furthermore, The Framework Ensures That Further Digital Value-Added Applications (Including Telemedicine Applications) And Appointment Management Can Be Integrated And Made Available To Patients. An Existing Clinical Data Repository (Cdr) Must Be Used To Persist Primary Health Data And Administrative Data. There Is No Independent Persistence Through A Patient Portal Framework. Communication With The Cdr Takes Place Via A Dmz (Demilitarized Zone) That Has Yet To Be Procured As A Temporary Buffer. 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 Stand-Alone And Independently From The Patient Portal In Order To Be Able To Map Further Use Cases In Mvzs, Outpatient Clinics And Other Immanuel Albertinen Diakonie Facilities In The Future. The Security Mechanisms Of The Patient Portal Must Correspond To The Current State Of The Art. The Relevant Clinics Currently Use 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, Editorial Content Is Created In A Separate, Central And Yet To Be Procured Headless Content Management System (Cms), Which Integrates Existing Content That Can Be Used For The Patient Portal From Other Sources, E.G Provides Clinic Websites. 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 Fa