Earlier this week I participated in the BPM and Case Management Global Summit conference with my good friend and colleague, John Matthias of the NCSC Court Services Division. He shared some of his recent work on court case management systems including decision mapping.
At the conference we received the new book, Innovation in Adaptive Case Management: Best Practices for Knowledge Workers (available at: http://www.futstrat.com/) . John has a chapter in the book: “Decisions: Where Process Meet Capabilities in Court PCM Requirements.” In the chapter he points out that case events can be connected not only to work roles, tasks, and queues, but also to decisions; more specifically to a decision table (https://en.wikipedia.org/wiki/Decision_table).
This design provides a logical database structure that allows the system to for example help a clerk to determine whether a filing should be charged a fee or not? In a related hypothetical example, let’s say that Form #100 is filed at the clerk’s office and that it is not an initial case document filing. The decision table could be linked to the case parties that would capture whether the filer was indigent or not. If so. the clerk then would be instructed not to collect the fee. The decision table is where these relationships could be mapped in the database structure.
I have created the following diagram adapting John’s work for this article to show how these database relationship entities might be thought via a graphic.
We owe a big thanks to John for his good work and for getting us thinking about how new CCMS design has the potential to do more useful work for the courts.
Update, July 13, 2016 The full chaper - “Decisions: Where Process Meet Capabilities in Court PCM Requirements” can be viewed and downloaded by clicking here.