Case Management Model And Notation Research Articles

Toward an interoperable, intraoperative situation recognition system via process modeling, execution, and control using the standards BPMN and CMMN

PurposeFor the modeling, execution, and control of complex, non-standardized intraoperative processes, a modeling language is needed that reflects the variability of interventions. As the established Business Process Model and Notation (BPMN) reaches its limits in terms of flexibility, the Case Management Model and Notation (CMMN) was considered as it addresses weakly structured processes.MethodsTo analyze the suitability of the modeling languages, BPMN and CMMN models of a Robot-Assisted Minimally Invasive Esophagectomy and Cochlea Implantation were derived and integrated into a situation recognition workflow. Test cases were used to contrast the differences and compare the advantages and disadvantages of the models concerning modeling, execution, and control. Furthermore, the impact on transferability was investigated.ResultsCompared to BPMN, CMMN allows flexibility for modeling intraoperative processes while remaining understandable. Although more effort and process knowledge are needed for execution and control within a situation recognition system, CMMN enables better transferability of the models and therefore the system. Concluding, CMMN should be chosen as a supplement to BPMN for flexible process parts that can only be covered insufficiently by BPMN, or otherwise as a replacement for the entire process.ConclusionCMMN offers the flexibility for variable, weakly structured process parts, and is thus suitable for surgical interventions. A combination of both notations could allow optimal use of their advantages and support the transferability of the situation recognition system.

Evaluating user acceptance of knowledge-intensive business process modeling languages

Case Management has been evolving to support knowledge-intensive business process management, resulting in different modeling languages, e.g., Declare, Dynamic Condition Response (DCR), and Case Management Model and Notation (CMMN). A language will die if users do not accept and use it in practice—similar to extinct human languages. Thus, evaluating how users perceive languages is important to improve them. Although some studies have investigated how the process designers perceived Declare and DCR, there is a lack of research on how they perceive CMMN—especially in comparison with other languages. Therefore, this paper investigates and compares how process designers perceive these languages based on the Technology Acceptance Model. The paper includes two studies conducted in 2020 and 2022, both performed by educating participants through a course, with feedback on their assignments, to reduce biases. The perceptions are collected through questionnaires before and after feedback on the final practice. Results show that the perceptions change is insignificant after feedback due to the participants being well-trained. The reliability of responses was tested using Cronbach’s alpha. The results of the first study show that both DCR and CMMN were perceived as having acceptable usefulness and ease of use, but CMMN was perceived as significantly better than DCR in terms of ease of use. The results of the second study show that only DCR was perceived significantly better than Declare in terms of usefulness. The participants’ feedback shows potential areas for improvement in languages and tool support to enhance perceived usefulness and ease of use.

Exploring CMMN applicability to knowledge‐intensive process modeling: An empirical evaluation by modelers

AbstractKnowledge‐intensive processes (KiPs) have emerged characterizing tasks that are data‐driven, change dynamically and depend on the knowledge and experience of knowledge workers. Case Management Model and Notation (CMMN) language was introduced for modeling unstructured, agile human‐centric processes. As the available Business Process Modeling (BPM) methods and practices are not adequate for modeling KiPs, this paper presents an empirical study of the applicability of CMMN to modeling KiPs. After experienced modelers designed the models of three KiPs scenarios utilizing CMMN, their perceptions were collected assessing the support of CMMN to the KiPs characteristics. Specifically, the modelers assessed the support of the newly introduced CMMN notation elements to the KiPs characteristics. Three of them, that is, knowledge‐driven, unpredictable, and goal‐oriented, were highlighted as the ones that get the greater support by CMMN when it comes to modeling KiPs; the participating modelers suggested that the applicability of CMMN to modeling KiPs is mostly reinforced by the Sentries element. Considering that in a knowledge‐driven economy, organizations are called to transform their way of thinking and manage KiPs, we value the modelers' opinions since they shall apply such practices in the future. This research is a first step to assess whether CMMN may be a “fit” for modeling KiPs. When considering the potential of CMMN for KiPs modeling, the perceptions of such real CMMN users are also first indications of the CMMN future in terms of application.

DISASTER RESPONSE MODELING BASE ON LANDSLIDE EARLY WARNING USING CASE MANAGEMENT MODEL AND NOTATION

There are a few handling steps in the emergency response to landslides that need thorough explanation. The flexibility of emergency response situations is ineffectively supported by traditional modeling methodologies because they are excessively inflexible. Companies have traditionally modeled their business processes using the Business Process Management Approach and Notation (BPMN) model. For design case management, such as the emergency reaction to a landslide disaster, BPMN modeling is unsuitable. because the BPMN modeling focuses how business processes flow inside a company. The Case Management Model and Notation (CMMN), the newest modeling approach from the Object Management Group (OMG), was launched in 2013 with the purpose of completing the BPMN modeling approach. The unstructured and adaptable CMMN claims to be able to handle urgent situations. This study's intention is to develop a CMMN model of a landslide emergency reaction scenario based on an emergency alert from an Early Warning System (EWS) sensor. In order to acquire the qualitative data for this study, the researcher first conducted a literature review. Then used the interview and observation methods to gather data, and from this data, we created the model using the CMMN modeling approach. The Yogyakarta Special Region Disaster Management Agency's (BPBD DIY) data flow of a disaster management information system, which was already operational, was analyzed by researchers. Then, the researchers used CMMN to model the data in order to find out opportunities to improve the disaster management information system already in use at BPBD DIY. Two CMMN models—the BPBD DIY disaster management information system model and the recommendation model for system improvements—were created in this study. The analysis of the current disaster management information system model resulted in the recomendation of this model. A prototype of feature recommendation is created as part of this research and given to specialists in natural disasters for model validation.

CMMN evaluation: the modelers’ perceptions of the main notation elements

Case Management Model and Notation (CMMN) has been introduced as a graphical modeling language targeting the modeling of human-centric processes. Despite its growing reputation since 2016, when the OMG standant was released, the usage and the adoption potential of CMMN is not yet evaluated. The goal of this paper is to evaluate CMMN language and the contribution of its main notation elements to its future adoption, based on the experience of modelers. A CMMN workshop was conducted, where groups of modelers modeled two different human-centric, real-world processes with CMMN. The effectiveness and efficiency of the language and modelers’ usage experience were evaluated. Their perception of the role of the CMMN notation elements to their future adoption CMMN have been recorded through a survey. A multi-criteria decision making method (Analytic Hierarchy Process–AHP) was utilized for analyzing the answers and generating the results. The evaluation results showed that CMMN language could be adopted for modeling non-structural processes and the study participants showed a positive attitude towards adopting CMMN driven by the fact that they overall perceived it as useful. To the best of our knowledge, this is the first attempt to evaluate CMMN language’s usability and prospects of adoption. Moreover, this is the first empirical study that explores the syntax of a process modeling language and its effect on its usage and adoption. Overall, since interest in CMMN is increasing, this work could inspire future researchers and practitioners to further explore the CMMN usage and adoption potential.

Empirical evaluation of CMMN models: a collaborative process case study

Case Management Model and Notation (CMMN) was introduced by the Object Management Group as an alternative modeling language, targeting human-centric processes characterized by lack of structure and agility. However, although it is adequately supported by well-known process management tools, CMMN applicability as a modeling language is being questioned in practice. In this work, an empirical evaluation of CMMN models is presented, through a real-world case study where CMMN has been used for the analysis and implementation of a collaborative process by independent groups of process engineers. Their experience is being discussed, based on their modeling perspective. The produced models in the analysis and implementation phase are evaluated, using pre-existing metrics customized for CMMN. Based on the experience of engineers, CMMN applicability is evaluated, highlighting aspects in which its application might be limited, that should be addressed.

Semiotic clarity of Case Management Model and Notation (CMMN)

ContextBusiness processes are an important asset of every organisation and can be divided into a group of structured processes (i.e. procedural) and loosely structured ones (i.e. declarative). A good example of procedural notations is Business Process Model and Notation (BPMN), a technologically accepted Standard, used by many organisations. A representative of declarative models is a fairly new specification, Case Management Model and Notation (CMMN), used for presenting cases. AimsThe main aim of this article is twofold. Firstly, we will provide an overview of the CMMN standard. Secondly, we will determine the degree of acceptance of CMMN with loosely structured processes by considering the acceptance of BPMN for structured processes. MethodThe acceptance of CMMN will be determined by relying on the theory for identifying cognitive effectiveness, which is one of the indicators for technology acceptance. We used the semiotic clarity principle to identify the degree of compliance for CMMN. ResultsThe results show that 24% of all CMMN elements defined in Specifications, Version 1.1, ensure semiotic clarity. The rest of the elements were classified as one of four anomalies, which are also acceptable to some extent and do not create additional confusion or incomprehensibility to CMMN. ConclusionSemiotic clarity and theory of cognitive effectiveness are good indicators for detecting the degree of technology acceptance of a notation. CMMN is a relatively new notation, and our research is offering a brief presentation of CMMN while also providing a detailed analysis of semiotic clarity, which is part of the theory for cognitive effectiveness.

Towards knowledge interoperability between the UML, DMN, BPMN and CMMN models

Development of modern software systems consists of many different phases, the sequence of whom is referred to as the software life cycle. During these phases, business analysts gather requirements from clients and try to design a system in order to fulfil these requirements. Software design of complex systems exploits various notations for representing knowledge about system structure and behaviour, decisions, processes and different cases. These elements are modelled using such graphical notations, maintained by Object Management Group (OMG), such as UML (Unified Modelling Language), DMN (Decision Model and Notation), BPMN (Business Process Model and Notation), and CMMN (Case Management Model and Notation). In this paper, we present our work-in-progress analysis of the current state of the art in knowledge interchange for these notations. Moreover, we identify the integration or interchange approaches in terms of application areas. Our goal is to provide an input for an integrated method of designing systems with the use of these notations.

Modelling emergency response process using case management model and notation

Emergency response is a knowledge-intensive process that is very hard to model and automate. This primarily returns to the unpredictability and unrepeatability nature that characterises such process. Traditional modelling approaches are too rigid and do not effectively support the flexibility and dynamicity required by emergency response process. Case Management Model and Notation (CMMN) is a new standard modelling specification that has recently been released by Object Management Group (OMG) to standardise the modelling of Case Management approach. The objective of this study is to demonstrate how the CMMN can be used to model emergency response process. The authors use the CMMN to build a template model for a generic emergency response process. This model can easily be extended or interchanged among different modelling tools or execution platforms. In addition, they present a case study of a flood management process as a concrete example of using CMMN in modelling emergency response process. Finally, they conclude that the CMMN has a great potential to model case-based processes such as emergency response, but CMMN still in its infancy. As a result, there is a lack of mature modelling tools and execution engines to execute the CMMN models.

Application fields for the new Object Management Group (OMG) Standards Case Management Model and Notation (CMMN) and Decision Management Notation (DMN) in the perioperative field.

Medical processes can be modeled using different methods and notations. Currently used modeling systems like Business Process Model and Notation (BPMN) are not capable of describing the highly flexible and variable medical processes in sufficient detail. We combined two modeling systems, Business Process Management (BPM) and Adaptive Case Management (ACM), to be able to model non-deterministic medical processes. We used the new Standards Case Management Model and Notation (CMMN) and Decision Management Notation (DMN). First, we explain how CMMN, DMN and BPMN could be used to model non-deterministic medical processes. We applied this methodology to model 79 cataract operations provided by University Hospital Leipzig, Germany, and four cataract operations provided by University Eye Hospital Tuebingen, Germany. Our model consists of 85 tasks and about 20 decisions in BPMN. We were able to expand the system with more complex situations that might appear during an intervention. An effective modeling of the cataract intervention is possible using the combination of BPM and ACM. The combination gives the possibility to depict complex processes with complex decisions. This combination allows a significant advantage for modeling perioperative processes.

Extending CMMN with entity life cycles

In the domain of business process modeling, a case denotes a situation that requires a customized treatment, and this may take place if the case workers are entitled to decide the tasks to perform as well as their ordering. In the recent CMMN (Case Management Model and Notation) standard, a case involves both an information structure and a process. The former is patterned on the file system structure and the latter is made up of stages, which are groupings of interrelated tasks. The standard leaves some open issues, such as the determination of the performers of the tasks, and the definition of the inputs and outputs of the tasks in terms of the information items affected. To address these issues, this paper proposes an extension to CMMN in which stages represent states of information items whose types along with their attributes and relationships are defined in an information model. The benefits of the extension are illustrated by means of an example that concerns the handling of papers submitted to conferences.