Michigan CaseQ
From PikaDocs
By Matthew Friedlander
Pika Software (http://www.pikasoftware.com/)
| Table of contents |
Introduction
The Michigan CaseQ project was undertaken by both Pika Software and the Michigan Poverty Law Program to create a queue or holding pen of cases transferred between programs. CaseQ acts then as a third party to allow programs to pre-screen cases prior to acceptance into their own case management systems (CMS). As part of this pre-screening users can accept, reject, run conflict checks, and view these cases before entry into their CMS.
CaseQ utilizes LS-XML and the REST Webservice protocol to transfer cases between programs and to promote 3rd party acceptance and use by using a national standard independent of any CMS vendor. This enables CaseQ to import LS-XML files as transfers from any CMS that supports LS-XML and Webservices (not just Pika Software's CMS).
Pika Software has written an interface to the CaseQ system via the CaseQ Manager module for Pika. However, any other vendor could write a similar interface for their own software and trade cases seamlessly with Pika.
CaseQ Manager
The CaseQ manager is the primary interface users of the system will use to interact with their own queue. The interface displays all of the cases associated with that organization ordered by date and status. Items in the queue are assigned a status depending on how they were transferred or received.
Individual cases transferred are displayed in chronological order to the right of the CaseQ summary. For each case there are a series of functions depending on its status. Below is a sample case and a description of each of the items:
- ID - The unique id number assigned to the case by CaseQ
- From/To - The sending organization/The receiving organization
- Client - The case primary client and information (Name, Address, DOB, SSN, %Poverty, Assets)
- Opposing Party - The opposing party of the case (Name, Address, DOB)
Account Management
API Reference
The methods outlined below represent the CaseQ functions that comprise its API. All of these functions have the same base set of POST variables in order for them to work.
- action
- user (caseq user)
- pass (caseq pass)
The following is a list of action values and their required parameters:
- GetCaseQStats
Returns the count of items in each status category in the queue.
getCaseQList
getCaseQItem
getPartners
