Wednesday, November 03, 2010

Towards Case Management

Case management was one of the recurring themes last week at the Business Process Forum. There definitely seems to be a growing need amongst end users for more flexible and adaptive business processes, without ending up with overly complex solutions. Everyone seems to agree that using a process-centric approach only in many cases leads to complex solutions that are hard to maintain. The "knowledge workers" no longer want to be locked into rigid processes but wants to have the power and flexibility to regain more control over the process themselves.

The term case management is often used in that context. I'm not going to try and give a precise definition of what it might or might not mean [1,2], but it refers to the basic idea that many applications in the real world cannot really be described completely from start to finish (including all possible paths, deviations, exceptions, etc.). Case management takes a different approach: instead of trying to model what should happen from start to finish, let's give the end user the flexibility to decide what should happen at runtime. In its most extreme form for example, case management doesn't even require any process definition at all. Whenever a new case comes in, the end user can decide what to do next based on all the case data.

A typical example can be found in healthcare (clinical decision support to be more precise), where care plans can be used to describe how patients should be treated in specific circumstances, but people like general practitioners still need to have the flexibility to add additional steps and deviate from the proposed plan, as each case is unique. And there are similar examples in claim management, helpdesk support, etc.

So, should we just throw away our BPM system then? I don't think so! Even at its most extreme form (where we don't model any process up front), you still need a lot of the other features a BPM system (usually) provides: there still is a clear need for audit logs, monitoring, coordinating various services, human interaction (e.g. using task forms), analysis, etc. And, more importantly, many cases are somewhere in between, or might even evolve from case management to more structured business process over time (when we for example try to extract common approaches from many cases). If we can offer flexibility as part of our processes, can't we let the users decide how and where they would like to apply it?

Let me give you two examples that show how you can add more and more flexibility to your processes. The first example shows a care plan that shows the tasks that should be performed when a patient has high blood pressure. While a large part of the process is still well-structured, the general practitioner can decide himself which tasks should be performed as part of the sub-process. And he also has the ability to add new tasks during that period, tasks that were not defined as part of the process, or repeat tasks multiple times, etc. The process uses an ad-hoc sub-process to model this kind of flexibility, possibly augmented with rules or event processing to help in deciding which fragments to execute.

The second example actually goes a lot further than that. In this example, an internet provider could define how cases about internet connectivity problems will be handled by the internet provider. There are a number of actions the case worker can select from, but those are simply small process fragments. The case worker is responsible for selecting what to do next and can even add new tasks dynamically. As you can see, there is not process from start to finish anymore, but the user is responsible for selecting which process fragments to execute.

And in its most extreme form, we even allow you to create case instances without a process definition, where what needs to be performed is selected purely at runtime. This however doesn't mean you can't figure out anymore what 's actually happening. For example, meetings can be very adhoc and dynamic, but we usually want a log of what was actually discussed. The following screenshot shows how our regular audit view can still be used in this case, and the end user could then for example get a lot more info about what actually happened by looking at the data associated with each of those steps. And maybe, over time, we can even automate part of that by using a semi-structured process.

We hope that already goes a long way in supporting your cases!



  1. I must admit, I'm a little confused on a pretty simple things.

    The first is, you indicate a 'timer event' prior to Escalate case. Timer event takes a single parameter which is expressed in milliseconds. I have a process which is intended to escalate after 40 days. How does the engine get triggered if the process is current suspended. Do I periodically reactivate a process manually and then the engine will trigger the task?

  2. Hi Kris - It's good to see the coverage of Case Management and Adaptive process.

    While I appreciate your concern re: solution complexity, the two examples provided are just the tip of the iceberg.

    Inserting a subroutine, an atomized process fragment, is a common place 'escape' clause for SOA/BPM, providing a workaround for otherwise procedural, control flow driven, BPM.

    The second scenario is the ad hoc client driven scenario. Process is atomized and then chained by the user, which eliminates control flows, but in and of itself doesn't account for compliance.

    If flexibility is understood to be derived in part by process atomization (both examples exhibit this), then it is fair to ask - do we need BPM?

    The real opportunity for declarative rules driven process is dynamic policy matching where policy constraints are applied based on context. We call these emergent processes, as the process unfolds step by step.

    In our system, each interaction is an event that is evaluated against policies and every response is made to order for the circumstances. It allows the system to be as flexible as possible and procedural as necessary.


  3. Any organization that contracts better qualified individuals is guaranteeing that profitability increments and friends benefits. It is a great idea to get numerous additional confirmations as important in your administrative field.ExcelR PMP Certification

  4. This is very useful post for me. This will absolutely going to help me in my project.
    ExcelR pmp certification

  5. It’s good to check this kind of website. I think I would so much from you. ExcelR PMP Certification