Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Case Management Model and Notation (CMMN): An Introduction
Transcript of Case Management Model and Notation (CMMN): An Introduction
A Case is a proceeding that involves actions taken regarding a subject in a particular situation to achieve a desired outcome
Traditional examples of
A Medical Case involves the care of a patient in the context of a medical history and current medical problems
A Legal Case involves the application of the law to a subject in a certain fact situation
The subject of a Case may be a
or some other focal point around which actions are taken to achieve an objective
Case Management Model and Notation (CMMN)
Member of the CMMN submission team
Member of the CMMN Finalization Task Force (FTF)
but as experience grows in resolving similar Cases over time
a set of common practices and responses can be defined for managing Cases in a more rigorous and repeatable manner
Any individual Case may be resolved in a completely ad-hoc manner
Case Management is often directed by a Knowledge Worker
Run-time planning involves the selection of specific Tasks for a Case, run-time ordering of the sequence in which the Tasks are executed, and ad-hoc collaboration with other knowledge workers on the Tasks
Planning at run-time is a fundamental characteristic of Case management
with minimal predefined encoding of the work to be performed
Case Management come from
the Legal and Medical worlds
Decisions may be triggered by events or new facts that continuously emerge during the course of the Case, such as the receipt of new documents, completion of certain Tasks, or achieving certain Milestones
Documents along with other unstructured or structured data about a Case are captured and referenced in the Case File for decision-making by Case Workers
The collection of data about the Case is often described as a Case File
Is notation for modeling and graphically expressing a Case
An interchange format for exchanging Case Models among different tools
Addressing the need to model activities that are not predefined and repeatable, but instead depend on evolving circumstances and ad hoc decisions by Knowledge Workers regarding a particular situation
Case Plan Model
The CMMN Notation
does not provide for the visual modeling of the information model elements of the Case
provides for the depiction of the behavioral model elements of a Case
As with many other modeling languages, there are many different ways in which to model a Case using CMMN and its notation. It is left to the modeler to choose the best model to capture the essence of the situation at hand for the desired purpose.
The Case Plan Model is the outermost element that defines a Case
The various elements of a Case Plan Model are depicted within the boundary of the Case Plan Model shape
Case File Item
A Case File contains Case File Items that can be anything from a folder or document stored in CMIS, an entire folder hierarchy referring or containing other Case File Items
All information, or references to information, that is required as context for managing a Case, is defined by a Case File
Every Case is associated with exactly one Case File
In CMMN planning is a run-time effort
A Planning Table defines the scope of planning
Users (Case workers) are said to “plan” (in run-time), when they select Discretionary Items from a Planning Table, and move them into the plan of the Case (instance).
Collapsed Planning Table
Discretionary elements are not visible
Expanded Planning Table
Discretionary elements are visible
The Notion of Discretionary
The Case Plan Model comprises both:
all elements that represent the initial plan of the case, and
all elements that support the further evolution of the plan through run-time planning by case workers
Stages can be nested within other Stages
Stages serve as container of any element required to construct and further evolve Case plans
Plan Model Elements
maybe considered "episodes"
of a Case
is an atomic unit of work during a Case
something that "happens" during the course of a Case
an achievable target,
defined to enable evaluation
of progress of the Case
Case management planning is typically concerned with determination of which Tasks are applicable, or which follow-up Tasks are required
Case workers execute the plan, particularly by performing Tasks as planned and adding discretionary Tasks to the plan of the Case instance
A Case File is meant as a logical model. It does not imply any assumptions about physical storage of information.
Case File Items lifecyle transitions
Stages, Tasks and Milestones lifecycle transitions
A blocking Human Task is waiting until the work associated with the Task is completed.
A non-blocking Human Task is not waiting for the work to complete.
It completes immediately upon instantiation.
A Process Task can be used in the Case to call (initiate) a Business Process.
A Case Task can be used to call (initiate) another Case.
User Event Listener enables direct interaction of a user with the Case
Timer Event Listener are used to catch predefined elapses of time
Events may trigger the enabling, activation and termination of Stages and Tasks, or the achievement of Milestones
In CMMN an event is something that "happens" during the course of a Case
Used to influence the proceeding of the Case directly, instead of indirectly via impacting information in the Case File
A Sentry “watches out” for important situations to occur (or “events”), which influence the further proceedings of a Case
A Sentry may consist of two parts:
An On-Part specifies the event that serves as trigger
An If-Part specifies a condition, as Expression that evaluates over the Case File
Structuring a Case
A Milestone represents an achievable target, defined to enable evaluation of progress of the Case
A Sentry is a combination of an Event and/or Condition
Sentry is used as an entry criterion
Sentry is used as an exit criterion
Before any treatment may be chosen "Examine Patient" has to be performed
Depending on the presence of and type of fracture four treatments are possible: "Prescribe Sling", "Prescribe Fixation", "Perform Surgery" and "Apply Cast"
"Perform XRay" is not required if the specialist diagnoses the absence of a fracture when doing "Examine Patient"
If "Perform XRay" is omitted only the treatment "Prescribe Sling" may be applied
The activity "Prescribe Medication" may be executed at any stage of the treatment
All other treatments require "Perform XRay" as proceeding activity in order to rule out the presence of a fracture or decide how to treat it
Simple fractures can be treated by just performing "Apply Cast" while unstable fractures may lead to "Prescribe Fixation"
When "Perform Surgery" is necessary, "Prescribe Rehabilitation" is further advised
A coordinated collection of activities
Business Process Model and Notation
Case management Model and Notation