This paper gives insights into the ADEPT project. Its target was to develop a next generation process management technology, which is by orders of magnitudes more powerful and flexible than contemporary process management systems. The ADEPT technology should provide advanced features and properties within one system, which seem to exclude each other, but which are required for the support of a broad spectrum of processes: ease-of-use for end users and system developers, high flexibility through the support of non-trivial ad-hoc deviations at the process instance level, quick implementation of process changes through process schema evolution, and correctness guarantees enabling robust execution of implemented processes. This paper describes the background and the real-world cases which motivated our research. It further explains the technological challenges we faced, describes the solutions we elaborated, and discusses the current status of the ADEPT project.
Background -how all beganIn 1992 we started the OKIS 1 project -a pretty large and broadly defined 3-years research project funded by the State of Baden-Württemberg. In this project several clinics, medical service units, and the computing center of our university hospital were involved. The goal of OKIS was to develop a concept for a cross-organizational, clinical information system that is able to integrate autonomous, heterogeneous departmental systems as well as to offer services across system boundaries (e.g., scheduling, resource management, and medical data exchange). At the beginning of OKIS we looked at many aspects of hospital information systems to understand the different types of relevant information, the different kinds of information systems involved (e.g., radiology information system, picture archiving and communication systems, and lab systems), the privacy issues, the different types and roles of doctors and nurses, characteristic properties of planning and scheduling tasks, and so forth. We further investigated new developments (at that point in time) like electronic patient record, communication servers, medical guidelines, and computer-assisted medical diagnostics in order to understand which features a modern hospital information system should have [27].The challenge of the service layer we wanted to develop was rather clear in an early stage of the project: Due to the heterogeneity of the underlying systems and the evolutionary nature of the clinical domain one has to decouple service provision from service implementation. However, the discovery of services and their usage must not be complicated. Therefore, long before web services came into the game, we 1 OKIS is derived from the German name of the project and stands for "Open Clinical Database and Information System for the Integration of Autonomous Subsystems".