An Overview of Tools for an Integrated and Adaptive Healthcare Approach Felix Michel Department of Informatics Software Engineering for Business Information Systems Technische Universit¨ at M¨ unchen 85748 Garching b. M¨ unchen, Germany felix.michel@tum.de Adrian Hernandez-Mendez Department of Informatics Software Engineering for Business Information Systems Technische Universit¨ at M¨ unchen 85748 Garching b. M¨ unchen, Germany adrian.hernandez@tum.de Florian Matthes Department of Informatics Software Engineering for Business Information Systems Technische Universit¨ at M¨ unchen 85748 Garching b. M¨ unchen, Germany matthes@tum.de Abstract—Integrated care approaches are becoming increas- ingly relevant with the current aging population. In the context of an integrated healthcare project, we developed a smart adaptive case management system for professionals that is currently being used for clinical trials. In this paper, we present the modeling requirements for integrated healthcare applications and use them to categorize and compare existing implementation approaches used in practice. Index Terms—Modeling, Adaptive Case Management, ACM, Healthcare I. I NTRODUCTION The demographic change in Europe is leading to a signifi- cantly aging population. The number of aged chronic patients increases. The objective of the Personalized Connected Care for Complex Chronic Patients (CONNECARE) project is to provide an integrated patient-centered health-care approach [1]. This research project focuses on medical aspects, informa- tion and communications technology evaluated within clinical trials at four hospitals across Europe. Conceptually, the pro- totypical system contains Smart Adaptive Case Management (SACM), which is used by clinical professionals, and the Self- management System (SMS), which provides patient-centered mobile applications that provide instructions prescribed by the clinical professionals. In the following, we are focusing on aspects of SACM. In [2], we present a holistic model- based adaptive case management approach for healthcare that focuses on challenges of integrated care approaches, iteratively derived requirements, conceptual features of user interfaces and related conceptual model elements. In [3], we present a practice-proven reference architecture for model-based collab- orative information systems that is used as a core modeling engine to provide Adaptive Case Management (ACM) support. This paper presents an overview of tools based on our derived requirements from [2]. A summary of the high-level requirements is provided in Section II, a sample use case from the clinical trials is described in Section III, and the existing tools are categorized, summarized and compared according their related requirements in Section IV. This work has received funding from the European Research Council (ERC) under the EuropeanUnions Horizon 2020 research and innovation programme (grant agreement n 689802). II. REQUIREMENTS We iteratively collected and adapted the high-level SACM requirements for each hospital. The high diversity across the different sites lead to several agile iterations. The initial requirements presented in [2] as follows: R1 Support a model-based full stack approach To cope with the high diversity across treatments and hospital sites, a fully model based approach should be used, and the treatment or site-specific adap- tations should be applied within the related meta- model including different clinical questionnaires or languages. R1.1 Support data schema models Data that are generated during the execution of the process models need to be modeled. In addition, they are needed to model data that will be integrated from third-party systems, e.g., patient data from hospital information systems. R1.2 Support adaptive process models The system needs and support to define adaptive treatment plans that are customized to the specific needs of the hospital and treatment. As a reference methodology for defining the processes, Adaptive Case Management (ACM) should be used. To support integrated care, these processes need to be synchronized with other subsystems. R1.3 Support role-based access right models The system needs to support granular role-based access control mechanisms to define which clinicians are allowed to access which patient data. In addition, clinical tasks need to be assigned based on roles. R1.4 Support simple user interface models In general, the user interface needs to represent each model ele- ment in a generic model-based manner. To support clinical use cases, special representations need to be generated that can also be reused as a model elements. 27 2018 IEEE 22nd International Enterprise Distributed Object Computing Workshop 2325-6605/18/$31.00 ©2018 IEEE DOI 10.1109/EDOCW.2018.00015