Gathering Court Data
Map Out Task Flow
These charts show the process improvements I was able to make for another project required for the class action case. In the course of studying the hospital billing data for our potential class, we discovered about 2000 accounts that had a billing code that seemed to indicate that these accounts were assigned to people who had been sued by the hospital.
We needed to track down more information about these accounts to give us a better picture of the hospitals previous collection practices.
As a first step to find out whether the people on these accounts had actually been sued, Loralee gave a list of these people to her paralegal, Lindsey, so that she could start looking them up by name on a public New Mexico courts database.
Identify Pain Points
The actual court records were not available online, just the court dockets which are sort of like a table of contents to the court record. So Loralee asked Lindsey to gather some pertinent information on each case so that she could later go into the clerks office in person and request the actual contents of each record. Lindsey began this process using an excel spreadsheet, but quickly became discouraged and overwhelmed by the sheer amount of annoying, repetitive work she was facing.
After seeing what she was doing, I was able to build a Filemaker database to significantly cut own on the amount of tasks she was having to do per record. By putting a viewport directly inside the database view and creating actions and scripts to download the whole docket for each case, I was able to reduce her workflow from 24 steps per record to 8 steps per record.