Defining various pathway terms

No abstract

MyPHRMachines : personal health desktops in the cloud

Personal Health Records (PHRs) should remain the lifelong property of patients, who should be enabled to show them conveniently and securely to selected caregivers and institutions. Current solutions for PHRs focus on standard data exchange formats and transformations to move data across health information systems. In this paper we present MyPHRMachines, a PHR system taking a radically new architectural solution to health record interoperability. In MyPHRMachines, health-related data and the application software to view and/or analyze it are separately deployed in the PHR system. After uploading their medical data to MyPHRMachines, patients can access them again from remote virtual machines that contain the right software to visualize and analyze them without any conversion. Patients can share their remote virtual machine session with selected caregivers, who will need only aWeb browser to access the pre-loaded fragments of their lifelong PHR. We discuss a prototype of MyPHRMachines applied to two use cases, i.e. radiology image sharing and personalized medicine. The first use case demonstrates the ability of patients to build robust PHRs across the space and time dimensions, whereas the second use case demonstrates the ability of MyPHRMachines to preserve the privacy of PHR data deployed in the cloud

BPMN 2.0 execution semantics formalized as graph rewrite rules : extended version

The Business Process Model and Notation (BPMN) standard version 2.0 informally defines a precise execution semantics. This paper defines that execution semantics formally, by defining the execution rules as graph rewrite rules. The paper shows that the formal definition of execution rules in this manner is intuitive and simple, in particular because they can be specified graphically, using the BPMN symbols, while maintaining mathematical rigour. Using graph rewriting tools, the resulting formal execution semantics can be used to directly execute models that are created in the BPMN. Therefore, it can be used as a reference implementation of the execution semantics and to test BPMN 2.0 engines, in combination with a set of BPMN test models that we also provide

MyPHRMachines: Lifelong Personal Health Records in the Cloud

Personal Health Records (PHRs) should remain the lifelong property of patients and should be showable conveniently and securely to selected caregivers. Regarding interoperability, current solutions for PHRs focus on standard data exchange formats and transformations to move data across health information systems. In this paper we propose MyPHRMachines, a patient-centric system that takes a radically new architectural solution to health record interoperability. We propose to deploy besides the medical data also the related software to the PHR system. After uploading their medical data to MyPHRMachines, patients can access them again from remote virtual machines that contain the right software to visualize and analyze them without any conversion. Patients can share their remote virtual machine session with a selected health provider, who will need only a Web browser to access the pre-loaded fragments of the lifelong PHR. We illustrate how our prototype already supports the use case of a real-world patient and discuss the research agenda required to translate this prototype into a viable solution for the international healthcare industry

Fujaba hits the Wall(-e)

With the ever increasing pervasiveness of software in every day's life, it is quite easy to explain children the importance of software development. Especially when using gadgets such as LEGO robots, one can fascinate young pupils. It is much harder though to and fair link to the actual educational and research programs from a particular university without blowing the audience away with details of a particular Java framework. This paper illustrates how one can use Fujaba to involve children from 8 to 18 years old in realistic requirements elicitation workshops. The children implicitly get in touch with the object-oriented paradigm by playing in the real world the communication between objects in a robot's computer. Fujaba's visual object browser provides a convincing means to illustrate that the game adequately represents the robot's internals

Tracebook : a dynamic checklist support system

It has recently been demonstrated that checklist scan enable significant improvements to patient safety. However, their clinical acceptance is significantly lower than expected. This is due to the lack of good support systems. Specifically, support systems are too static: this holds for paper-based support as well as for electronic systems that digitize paper-based support naively. Both approaches are independent from clinical process and clinical context. In this paper, we propose a process-oriented and context-aware dynamic checklist support system: Tracebook. This system supports the execution of complex clinical processes and rules involving data from Electronic Medical Record systems. Workflow activities and forms are specific to individual patients based on clinical rules and they are dispatched to the right user automatically based on a process model. Besides describing the Tracebook functionality in general, this paper demonstrates the support system specifically on an example application that we are preparing for a controlled clinical evaluation. At last we discuss the difference between Tracebook and other support systems which also rely on a checklist format

DCCSS:a meta-model for dynamic clinical checklist support systems

Clinical safety checklists receive much research attention since they can reduce medical errors and improve patient safety. Computerized checklist support systems are also being developed actively. Such systems should individualize checklists based on information from the patient’s medical record while also considering the context of the clinical workflows. Unfortunately, the form definitions, database queries and workflow definitions related to dynamic checklists are too often hard-coded in the source code of the support systems. This increases the cognitive effort for the clinical stakeholders in the design process, it complicates the sharing of dynamic checklist definitions as well as the interoperability with other information systems. In this paper, we address these issues by contributing the DCCSS meta-model which enables the model-based development of dynamic checklist support systems. DCCSS was designed as an incremental extension of standard meta-models, which enables the reuse of generic model editors in a novel setting. In particular, DCCSS integrates the Business Process Model and Notation (BPMN) and the Guideline Interchange Format (GLIF), which represent best of breed languages for clinical workflow modeling and clinical rule modeling respectively. We also demonstrate one of the use cases where DCCSS has already been applied in a clinical setting

Fujaba days 2009 : proceedings of the 7th international Fujaba days, Eindhoven University of Technology, the Netherlands, November 16-17, 2009

Fujaba is an Open Source UML CASE tool project started at the software engineering group of Paderborn University in 1997. In 2002 Fujaba has been redesigned and became the Fujaba Tool Suite with a plug-in architecture allowing developers to add functionality easily while retaining full control over their contributions. Multiple Application Domains Fujaba followed the model-driven development philosophy right from its beginning in 1997. At the early days, Fujaba had a special focus on code generation from UML diagrams resulting in a visual programming language with a special emphasis on object structure manipulating rules. Today, at least six rather independent tool versions are under development in Paderborn, Kassel, and Darmstadt for supporting (1) reengineering, (2) embedded real-time systems, (3) education, (4) specification of distributed control systems, (5) integration with the ECLIPSE platform, and (6) MOF-based integration of system (re-) engineering tools. International Community According to our knowledge, quite a number of research groups have also chosen Fujaba as a platform for UML and MDA related research activities. In addition, quite a number of Fujaba users send requests for more functionality and extensions. Therefore, the 7th International Fujaba Days aimed at bringing together Fujaba developers and Fujaba users from all over the world to present their ideas and projects and to discuss them with each other and with the Fujaba core development team

Synthesizing data-centric models from business process models

Data-centric business process models couple data and control flow to specify flexible business processes. However, it can be difficult to predict the actual behavior of a data-centric model, since the global process is typically distributed over several data elements and possibly specified in a declarative way. We therefore envision a data-centric process modeling approach in which the default behavior of the process is first specified in a classical, imperative process notation, which is then transformed to a declarative, data-centric process model that can be further refined into a complete model. To support this vision, we define a semi-automated approach to synthesize an object-centric design from a business process model that specifies the flow of multiple stateful objects between activities. The object-centric design specifies in an imperative way the life cycles of the objects and the object interactions. Next, we define a mapping from an object-centric design to a declarative Guard-Stage-Milestone schema, which can be refined into a complete specification of a data-centric BPM system. The synthesis approach has been implemented and tested using a graph transformation tool

Synthesizing object life cycles from business process models

Business process models expressed in UML activity diagrams can specify the flow of stateful business objects among activities. Such business process models implicitly specify the life cycles of those objects. To check the consistency of a business process model with an existing object life cycle or to generate or configure software supporting the business process, these implicit life cycles need to be discovered. This paper presents an approach for synthesizing an object life cycle from a business process model in which the object occurs in different states. The synthesized object life cycles are expressed as hierarchical statecharts. The approach makes implicit life cycles contained inside business process models explicit. The synthesis approach has been implemented using a graph transformation tool and has been applied to case studies