E-mail
Case Management Demo
Notes from a demo of a "reference" case management system (Safety Net)
Case and Activity Lists
- Top level navigation uses folders: All Documents >> List of Cases >> Drilldown list of all activities
- Activity rows show "person that entered info" in parentheses after the Note / Text
- Icons are associated with some Activity Types
- Activity rows are color-coded based on whether they contain protected (encrypted) data. The summary (listing level) info for protected activities is viewable by everyone who as access to the case. The details are encrypted via private key and only viewable by selected users.
Case "Views"
- Case Snapshot - A cache of the case's most important data elements, includes a list of "roles" associated iwth the case the when available the name of the person in the role
Input Forms
- New Activity form ("standard / not extended")
- Encounter medium (f 2 f, in bound phone, out bound phone, letter ... configurable list)
- Body (description) is rich text, can attach documents
- Time Spent
- Includes ability to pick contactt(s) or a "role(s)" to send an email with a copy of the information being recorded. Sensitive / identifiying data about the client (e.g. SSN, Phone #, etc.) can be included or excluded from the email (included by default)
- (user who created / modified the activity, and when are automatically recorded)
- "Special Activities" - several types, e.g. Milestone
- User selects "category" of Milestone, then type of Milestone from filtered list of milestones. then "type" defines x # of additional fields
Case Configuration
- Case types define a pre-configued set of expected scheduled activities ("Timelines") with "Assignees" by Role
- In this implementation, the activity type definitions include "PHP code" which says which cases they should be auto-assigned to.
- When user changes the type for a case - they have the option to replace the auto-generated "Timeline" entries with ones that are configured for the new case type (only future scheduled activities are "replaced).
- NOTE: Auto-populated activities will need to be flagged
- Case type also define "Required Activity Types" which are evaluated whenever a "Case Summary" is requested.
- Case Summary - a snapshot (stored as an activity) of what's been done vs. what's missing relative to "required activities" either for the entire case (based on it's type), or possibly a defined, named subset of those activities. (Named subsets / summaries are likely a phase 2+ feature.)
Labels:
