US 6,098,070 AGrant
Case Management for a Personal Injury Plaintiff's Law Office Using a Relational Database
Issue Date:2000-08-01
•6 Claims
•34 Drawing Sheets
Abstract
An electronic case manager for a personal injury plaintiffs law office in which client and defendant level data related to an injury incident are collected and organized in an efficient manner. The electronic case manager include a relational database having a number of tables, and a database management program.
Metadata
Assignee
- Hipersoft Corp.
Inventor
- John M. Maxwell
Application Information
Application Number:US 0942030
Filing Date:1998-06-09
Priority Date:1998-06-09
Art Unit:271
Classifications
IPC:
G06F 1700
Field of Search:
7071-206
Patent Drawings (34 sheets)
Description
NOTICE OF COPYRIGHTS AND TRADE DRESS
A portion of the disclosure of this patent document contains material which is subject to copyright protection. This patent document may show and/or describe matter which is or may become trade dress of the owner. The copyright and trade dress owner has no objection to the facsimile reproduction by any one of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright and trade dress rights whatsoever.
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates generally to automation of law offices, and more particularly to automation of personal injury law practices.
2. Description of Related Art
For an attorney experienced in personal injury plaintiff's work, cases proceed in a fairly predictable process. The client usually retains the attorney on a contingency basis, so that the attorney only is paid if there is a recovery for the client's injuries. The client usually has injuries which are treated by various professionals, such as doctors, dentists, physical therapists and chiropractors. The client typically seeks compensation for the costs of these treatments. The client may have other costs for which he seeks compensation, such as for repair of auto damage. Finally, the client may seek compensation for other things, such as pain and suffering, lost consortium, lost wages, etc.
It is well-known that most personal injury cases are settled. Of all personal injury cases, only a small percentage advance to the filing of a complaint, and fewer still advance through final judgement. The plaintiff's attorney is motivated to settle because of the high cost for the attorney to pursue a lawsuit. The defense attorney is motivated to settle because of the risk of a huge damage award against his client in litigation. In fact, early settlement is the norm in personal injury cases. Profitability of a personal injury law office often depends on efficient movement of cases toward settlement.
In running a personal injury law practice, an attorney or trained staff-member must spend hours to complete the necessary forms and documents needed to prepare a personal injury case for settlement. At the outset, letters must be sent to the client and insurance companies, and as the case progresses, letters and documents must be exchanged with medical providers, opposing attorneys, and eventually the courts. The time spent preparing these documents can severely distract personal injury attorneys from more important matters such as researching and investigating their cases and building their practices.
In many jurisdictions, the courts have promulgated required forms for practice before them. In California, personal injury lawyers commonly use a type of document called a Judicial Council form. The Judicial Council forms are official forms promulgated by the California Judicial Council, a court agency.
Studies have shown that an experienced personal injury lawyer spends approximately 25 hours working up a case to the point of settlement. Assuming a billing rate of $100/hour, the cost to settle the average case is $2,500. The attorney fees generated in a settlement of an average case are $3,200.
By automating the case handling and document production processes, software can reduce the amount of time required to prepare a case for settlement. By reducing the amount of time required to work up the average case, the profit margin can increase substantially. Furthermore, the attorney has more time to spend investigating and preparing their cases and obtaining new clients.
There are a number of computer programs which a personal injury plaintiff's law office can use for case management. These case management systems include databases for various relevant information, and often can generate calendars of previously entered due dates. These case management systems also serve as contact managers, and frequently will handle billing and accounting as well.
One of the major impediments to efficient management of data in a personal injury plaintiff's law office is the complex nature of the data. For a given case, the law office may represent many clients, each with differing claims and injuries. There may be many defendants. Many third parties are also involved in the process: defendants' lawyers, doctors, witnesses, expert witnesses, police departments, auto body shops, insurance companies, attorneys for the insurance companies, etc. Because there is so much information, typical systems have been unable to provide for efficient data entry and management. These are critical precedent steps toward gaining the benefits from these types of programs.
Relational databases have been known for quite some time. A relational database consists of a collection of tables, each having a unique name. A row in a table represents a relationship among a set of values. Thus a table represents a collection of relationships.
A relational database normally is considered to have two primary components. First, a relational database has a database scheme, which is the logical design of how data is organized withing the database. The database scheme includes the names of the tables, the names of the fields (or columns) within each table, and the attributes of the fields (e.g., text, numeric, date, etc.). Second, a relational database has a database instance, which is the data in the database at a point in time.
Despite the benefits of relational databases, most case management systems for personal injury plaintiff's law offices use simpler, hierarchical databases. Even those which have utilized relational databases have done so in a limited fashion. Without a well-designed relational database, a case management system for personal injury plaintiff's law offices requires double-entry of data and the case management system can be unable to handle the complex nature of the case's data. Without the ability to easily enter data, without the ability to enter certain types of data, and without the ability to logically organize the data, such systems have provided very limited benefit and have therefore seen limited commercial success.
SUMMARY OF THE INVENTION
The previously described problems are solved in an electronic case manager for a personal injury plaintiffs law office in which client and defendant level data related to an injury incident are collected and organized in an efficient manner. The electronic case manager includes a relational database having a number of tables and a case management program for interfacing with a user to receive data, manage the data and to provide output.
The electronic case manager for a personal injury plaintiffs law office includes a data structure programmed and arranged for classifying data in a relational structure and a database manager programmed and arranged for managing the data structure to allow users to generate documents on the output device.
The relational structure comprises a plurality of tables, the tables comprising plural records relating to personal injury-causing incidents. Each record comprises at least one field. The tables of the relational structure include:
a clients table for storing information about clients in client records,
a defendants table for storing information about prospective and actual defendants for claims by law office clients for personal injuries in defendant records,
an insurers table for storing information about insurers in insurer records,
an attorneys table for storing information storing about defense and insurance attorneys in attorney records,
an incidents table for storing information about injury-causing incidents in incidents records,
a property damage table for storing information about property damage in property damage records,
a loss of earning table for storing information about loss of earnings in loss of earnings records,
a medical bills table for storing information about medical bills in medical bills records,
a witnesses table for storing information about witnesses in witness records,
an expert witnesses table for storing information about expert witnesses in expert witness records,
an evidence table for storing information about evidence in evidence records,
a litigation table for storing information about litigation in litigation records,
depositions table for storing information about depositions in deposition records,
a discovery table for storing information about discovery in discovery records,
a motions table for storing information about motions in motion records,
a costs table for storing information about costs in costs records,
an arbitrations table for storing information about arbitrations in arbitration records, and
a police reports table for storing information about police reports in police report records.
The tables are linked through certain identical fields. The links include a file number field included in and required in the records of the clients table, the defendants table, the insurers table, the attorneys table, the incidents table, the property damage table, the loss of earning table, the medical bills table, the witnesses table, the expert witnesses table, the evidence table, the litigation table, the depositions table, the discovery table, the motions table, the costs table, the arbitrations table and the police reports table, the file number field comprising a unique reference number for referencing incidents. Another link is through a client name field included in and required in the records of the clients table, the loss of earning table, the medical bills table, the discovery table and the costs table, the client name field comprising a client's name and is unique in each table for each file number.
The database manager includes instructions for merging data stored in records in the tables with document templates in accordance with predefined merge rules. The database manager manages the relational data structure in accordance with predefined structure rules. These structure rules include:
for each incident there will be at least one client record,
for each incident there will be at least one defendant record,
for each incident there will be at least one insurer record,
for each incident there may be one or more attorney records,
for each incident there will be only one incident record,
for each incident there may be one or more property damage records,
for each incident there may be one or more loss of earnings records,
for each incident there may be one or more medical bills records,
for each incident there may be one or more witness records,
for each incident there may be one or more expert witness records,
for each incident there may be one or more evidence records,
for each incident there may be one litigation record,
for each incident there may be one or more deposition records,
for each incident there may be one or more discovery records,
for each incident there may be one or more motion records, and
for each incident there may be one or more costs records.
Still further objects and advantages attaching to the device and to its use and operation will be apparent to those skilled in the art from the following particular description.
DESCRIPTION OF THE DRAWINGS
Further objects of this invention, together with additional features contributing thereto and advantages accruing therefrom, will be apparent from the following description of a preferred embodiment of the present invention which is shown in the accompanying drawings with like reference numerals indicating corresponding parts throughout and which is to be read in conjunction with the following drawings, wherein:
FIG. 1 is a block diagram of a general purpose computer in accordance with the invention.
FIG. 2 is a diagram of relational database tables having file number linkages in accordance with the invention.
FIG. 3 is a diagram of relational database tables having file number and client name linkages in accordance with the invention.
FIG. 4 is a diagram of relational database tables having linkages other than file number in accordance with the invention.
FIG. 5A is a screen shot of a client record data entry screen in accordance with the invention.
FIG. 5B is a screen shot of a settlement data entry screen in accordance with the invention.
FIG. 6 is a screen shot of a defendant record data entry screen in accordance with the invention.
FIG. 7 is a screen shot of a insurer record data entry screen in accordance with the invention.
FIG. 8 is a screen shot of an attorney record data entry screen in accordance with the invention.
FIG. 9 is a screen shot of an incident record data entry screen in accordance with the invention.
FIG. 10 is a screen shot of a property damage record data entry screen in accordance with the invention.
FIG. 11 is a screen shot of a loss of earnings record data entry screen in accordance with the invention.
FIGS. 12A and 12B are screen shots of medical bills record data entry screens in accordance with the invention.
FIG. 13 is a screen shot of a witness record data entry screen in accordance with the invention.
FIG. 14 is a screen shot of an expert witness record data entry screen in accordance with the invention.
FIG. 15 is a screen shot of a evidence record data entry screen in accordance with the invention.
FIG. 16 is a screen shot of a litigation record data entry screen in accordance with the invention.
FIG. 17 is a screen shot of a deposition record data entry screen in accordance with the invention.
FIG. 18 is a screen shot of a discovery record data entry screen in accordance with the invention.
FIG. 19 is a screen shot of a motion record data entry screen in accordance with the invention.
FIG. 20 is a screen shot of a cost record data entry screen in accordance with the invention.
FIG. 21 is a screen shot of a arbitration record data entry screen in accordance with the invention.
FIG. 22 is a screen shot of a police report record data entry screen in accordance with the invention.
FIG. 23 is a screen shot of a body shop record data entry screen in accordance with the invention.
FIG. 24 is a screen shot of an attorney contact record data entry screen in accordance with the invention.
FIG. 25 is a screen shot of an adjuster contact record data entry screen in accordance with the invention.
FIG. 26 is a screen shot of an expert contact record data entry screen in accordance with the invention.
FIG. 27 is a screen shot of a medical provider contact record data entry screen in accordance with the invention.
FIG. 28 is a screen shot of an arbitrator contact record data entry screen in accordance with the invention.
FIG. 29 is a flowchart of a method of generating documents in accordance with the invention.
FIG. 30 is a screen shot of a firm attorney record data entry screen in accordance with the invention.
FIG. 31 is a screen shot of an appearances record data entry screen in accordance with the invention.
FIG. 32 is a screen shot of a courts record data entry screen in accordance with the invention.
These and additional embodiments of the invention may now be better understood by turning to the following detailed description wherein an illustrated embodiment is described.
DETAILED DESCRIPTION OF THE INVENTION
Throughout this description, the preferred embodiment and examples shown should be considered as exemplars, rather than limitations on the apparatus and methods of the present invention.
The invention is embodied in Personal Injury Powertool, published by HiPerSoft Corporation (Long Beach, Calif.) and first sold on or after Jun. 9, 1997. The substance, functionality, screens, documentation, and on-line help of the P.I. Powertool are incorporated herein by reference.
FIG. 1 shows a general purpose computer 100. The computer 100 preferably includes an Intel Corporation (San Jose, Calif.) processor 155 and runs a Microsoft Corporation (Redmond, Wash.) Windows operating system. In conjunction with the processor 155, the computer 100 has a short term memory 150 (preferably RAM) and a long term memory 180 (preferably a hard disk) as known in the art. The computer 100 further includes a LAN interface 115, a display 105, a display adapter 120, a keyboard 130, a mouse 140, a bus 110 and a printer 125 as known in the art.
Before proceeding, a few terms are defined. By "software" it is meant one or more computer interpretable programs and/or modules related and preferably integrated for performing a desired function. By "document" it is meant a named, structural unit of text, graphics and/or other data that can be stored, retrieved and exchanged among systems and users as a separate unit. By "case" it is meant. By "incident" it is meant the action or event which gave rise to the injuries for which the law firm's client seeks compensation, and could be, for example, a car accident, a dog bite, a slip and fall, or an assault and batter. By "client" it is meant a client of the law firm who the law firm is representing with respect to the client's claim arising from an incident. By "defendant" it is meant a party which is potentially liable for a client's damages, and encompasses such parties regardless of whether the client sues the party.
The most time consuming process in the practice of law involves the preparation of various documents. In accordance with the invention, various databases are defined and used in conjunction with form documents to easily, efficiently, and quickly prepare documents. Two types of documents are produced in accordance with the invention: Judicial Council forms and custom forms. Both Judicial Council forms and custom forms can be created by the user with one or two keystrokes or mouse clicks. In most cases, the user need only select the type of document to be prepared and the client from a list and the document is automatically generated with all necessary information.
The Judicial Council forms are grouped as follows: General, Pleading, Discovery, Case Management, Los Angeles County, Miscellaneous, Case Management, and DMV. Other forms include letters to clients, medical providers, insurance companies, witnesses and opposing attorneys.
When preparing forms in accordance with the invention, the electronic case manager of the invention gathers data from a relational database. Because the program generates output dynamically as desired by a user, the output will reflect the current state of the relational database in the electronic case manager.
Overview of the Tables
The block diagrams of FIGS. 2-4 collectively show an electronic case manager relational database in accordance with the invention.
The database includes the tables shown in Tables IA, IB and IC. These tables include columns identifying the tables of the data structure of the invention, a description of the data stored in the table, the table's essentiality, and the corresponding reference number in FIGS. 2-4. The tables of Table IA are shown in FIG. 2. The tables of Table IB are shown in FIG. 3. The tables of Table IC are shown in FIG. 4. Table IA lists the tables which store records specific to incidents where the primary linkage is by an incident key. Table IB lists the tables which store records specific to incidents where the primary linkage is by incident key plus a client key. Table IC lists the tables which store records which are not specific to incidents, and are also not specific to clients.
In the following tables, the fourth column is labeled "Essential?" If there is a check in this column, then the table (or field in the case of Tables II through XXVI) in that row is an essential part of the data structure of the invention. However, while a given table or field may be essential, a user need not necessarily enter data in that table or field.
In some cases, a table may not be marked as essential, but one or more of the fields in the table may be marked as essential. In this circumstance, the table is not considered to be essential, but if the table is included, then the marked fields are essential.
The tables in Table IC are not essential. However, they are preferably provided to allow for reuse of the indicated data. This reuse may take place across the cases, so none of these tables includes a file number field, as shown further below.
Preferably, data entry screens for the data structure of the invention include editing and ease of use features as known in the art. This includes intelligent field length limiting, automatic formatting of dates, numbers, monetary amounts, etc., drop-down lists which may or may not be edited depending on the nature of the data, etc.
Information About Each Table
Before describing the individual fields of each table, several fields which appear in the tables are described, including a file number field, name fields, a client ID field, a defendant ID field, and address fields.
The file number field in the various tables, in most law offices, will be the firm's own file number for the case. However, the file number need only be unique for each case, and could even be generated by the database manager.
The various name fields preferably are comprised of a first name, middle name and last name field.
Each client must have a unique client ID field for each case. Each defendant must have a unique defendant ID field for each case. Preferably, the client IDs and defendant IDs are unique amongst each other for each case as well. This permits linkages between the insurers table and discovery tables. Alternatively, for tables which might have an ID field which could be filled by a client ID or a defendant ID, flags may be provided to indicate whether an ID is a client ID or a defendant ID, or separate fields may be provided for client ID and defendant ID.
The various address fields are preferably comprised of a street address field, a state field, a city field, a zip code field, and one or more phone number fields.
Turning now to the tables, the fields in the clients table 305 are shown in Table II. These fields and additional fields are shown in FIGS. 5A and 5B and will be appreciated by those of skill in the art. The client table must be linked to the incident table. Preferably, this linkage is arranged by including a file number field in the client table.
The fields in the defendants table 220 are shown in Table III. These fields and additional fields are shown in FIG. 6 and will be appreciated by those of skill in the art.
The fields in the insurers table 210 are shown in Table IV. These fields and additional fields are shown in FIG. 7 and will be appreciated by those of skill in the art.
The fields in the attorneys table 260 are shown in Table V. These fields and additional fields are shown in FIG. 8 and will be appreciated by those of skill in the art.
The fields in the incidents table 205 are shown in Table VI. These fields and additional fields are shown in FIG. 9 and will be appreciated by those of skill in the art.
Table VI-Incidents Table Structure
The fields in the property damage table 315 are shown in Table VII. These fields and additional fields are shown in FIG. 10 and will be appreciated by those of skill in the art.
The fields in the loss of earnings table 320 are shown in Table VIII. These fields are shown in FIG. 11 and will be appreciated by those of skill in the art.
The fields in the medical bills table 310 are shown in Table IX. These fields and additional fields are shown in FIGS. 12A and 12B and will be appreciated by those of skill in the art.
The fields in the witnesses table 215 are shown in Table X. These fields and additional fields are shown in FIG. 13 and will be appreciated by those of skill in the art.
The fields in the expert witnesses table 250 are shown in Table XI. These fields and additional fields are shown in FIG. 14 and will be appreciated by those of skill in the art.
The fields in the evidence table 245 are shown in Table XII. These fields are shown in FIG. 15 and will be appreciated by those of skill in the art.
The fields in the litigation table 230 are shown in Table XIII. These fields and additional fields are shown in FIG. 16 and will be appreciated by those of skill in the art.
The fields in the depositions table 255 are shown in Table XIV. These fields and additional fields are shown in FIG. 17 and will be appreciated by those of skill in the art.
The fields in the discovery table 330 are shown in Table XV. These fields are shown in FIG. 18 and will be appreciated by those of skill in the art. Although only one discovery table is shown, it is preferred to provide to discovery tables--one table for discovery propounded by a client, and a second table for discovery propounded by a defendant on a client. In such an embodiment, the "from" and "to" fields do not include a defendant ID. Rather, it is preferred to have only the typed name of the defendant in the field.
The fields in the motions table 240 are shown in Table XVI. These fields are shown in FIG. 19 and will be appreciated by those of skill in the art.
The fields in the costs table 325 are shown in Table XVII. These fields are shown in FIG. 20 and will be appreciated by those of skill in the art.
The fields in the arbitrations table 235 are shown in Table XVIII. These and additional fields are shown in FIG. 21 and will be appreciated by those of skill in the art.
The fields in the police reports table 225 are shown in Table XIX. These and additional fields are shown in FIG. 22 and will be appreciated by those of skill in the art.
The fields in the body shops table 335 are shown in Table XX. These and additional fields are shown in FIG. 23 and will be appreciated by those of skill in the art.
The fields in the attorney contacts table 410 are shown in Table XXI. These fields are shown in FIG. 24 and will be appreciated by those of skill in the art.
The fields in the adjuster contacts table 425 are shown in Table XXII. These fields are shown in FIG. 25 and will be appreciated by those of skill in the art.
The fields in the expert contacts table 430 are shown in Table XXIII. These and additional fields are shown in FIG. 26 and will be appreciated by those of skill in the art.
The fields in the medical provider contacts table 420 are shown in Table XXIV. These and additional fields are shown in FIG. 27 and will be appreciated by those of skill in the art.
The fields in the arbitrator contacts table 415 are shown in Table XXV. These and additional fields are shown in FIG. 28 and will be appreciated by those of skill in the art.
The fields in the firm attorneys table 405 are shown in Table XXVI. These and additional fields are shown in FIG. 30 and will be appreciated by those of skill in the art.
The fields in the appearances table 265 are shown in Table XXVII. These fields are shown in FIG. 31 and will be appreciated by those of skill in the art.
The fields in the courts table 435 are shown in Table XXVIII. These fields are shown in FIG. 32 and will be appreciated by those of skill in the art.
Table Linkages
Tables preferably linked by file number field: clients, incidents, insurers, witnesses, defendants, police reports, litigation, arbitrations, motions, evidence, expert witnesses, attorneys, depositions, medical bills, property damage, loss of earnings, costs, discovery, body shops, appearances.
Tables preferably linked by client ID field: clients, medical bills, property damage, loss of earnings, costs, insurers (through insured ID field), evidence (through party supported field), depositions (through noticed by field), discovery (through to and from fields), motions (through moving party field and responding party field).
Tables preferably linked by attorney assigned field: clients, firm attorneys (through attorney ID field).
Tables preferably linked by adjuster ID field: insurers, adjuster contacts.
Tables which could be linked by defendant ID field: defendants, insurers (through insured ID field), evidence (through party supported field), depositions (through noticed by field), discovery (through to and from fields), motions (through moving party field and responding party field).
Tables preferably linked by attorney ID field: attorneys, attorney contacts.
Tables preferably linked by medical provider ID field: medical bills, medical providers.
Tables preferably linked by expert ID field: expert witnesses, expert contacts.
Tables preferably linked by arbitrator ID field: arbitrations, arbitrator contacts.
Tables preferably linked by court ID field: litigation, courts.
Several of the tables have very similar fields, but are not linked. For example, the attorney contacts table, the adjuster contacts table, the experts contacts table and the arbitrator contacts table include name, address and salutation fields, but are not linked. These tables could be embodied as a single contact table having the fields of all of the tables, plus a field which indicates the type of contact.
Database Manager
In conjunction with the data structure described above, the electronic case manager for a personal injury plaintiffs law office includes a database management program having instructions and arranged for managing the data structure to allow users to generate documents on an output device such as display 105 or printer 125.
The operation of the database management program is further described with reference to FIG. 29. After the database management program is started (step 2905), the database management program provides prompts and controls the input of data by a user and stores the data in the long term memory 180 (step 2910). Next, the database management program provides prompts for the user to select an output (e.g., an analytical report or a form document) and controls the user's input of criteria data to be used by the database management program to generate the output (step 2915). The database management program next generates the desired output (step 2920), and processing is complete (step 2925).
The electronic case manager manages the data structure in accordance with predefined structure rules in the database management program. Some of these structure rules are also evident from FIGS. 2-4, wherein some tables are shown as a single box, to show one record in that table per case, and other tables are shown as staggered boxes, to show multiple possible records in that table per case. The structure rules include:
For each case there will be only one linked incident record.
For each incident record there will be at least one linked client record.
For each incident record there will be at least one linked defendant record.
For each incident record there will be at least one linked insurer record.
For each incident record there may be one or more linked attorney records.
For each incident record there may be one or more linked property damage records.
For each incident record there may be one or more linked loss of earnings records.
For each incident record there may be one or more linked medical bills records.
For each incident record there may be one or more linked witness records.
For each incident record there may be one or more linked expert witness records.
For each incident record there may be one or more linked evidence records.
For each incident record there may be only one linked litigation record.
For each incident record there may be one or more linked deposition records.
For each incident record there may be one or more linked discovery records.
For each incident record there may be one or more linked motion records.
For each incident record there may be one or more linked costs records.
For each incident record there may be one or more linked police report records.
For each incident record there may be one or more linked arbitration records.
For each incident record there may be one or more linked body shop records.
For each client record there may be one or more linked medical bill records.
For each client record there may be only one linked property damage records.
For each client record there may be only one linked loss of earnings records.
For each client record there may be one or more linked cost records.
For each client record there may be one or more linked insurer records.
For each client record there may be one or more linked evidence records.
For each client record there may be one or more linked deposition records.
For each client record there may be one or more linked discovery records.
For each client record there may be one or more linked motion records.
For each client record there will be one linked firm attorney record.
For each insurer record there will be one linked adjuster contact record.
For each defendant record there may be one or more linked insurer records.
For each defendant record there may be one or more linked evidence records.
For each defendant record there may be one or more linked deposition records.
For each defendant record there may be one or more linked discovery records.
For each defendant record there may be one or more linked motion records.
For each attorney record there must be one linked attorney contact record.
For each medical bill record there must be one linked medical provider record.
For each expert witness record there must be one linked expert contact records.
For each arbitration record there must be one linked arbitrator contact record.
The database management program includes instructions for merging data stored in records in the tables with document templates in accordance with predefined merge rules. Thus, after the database management program guides the user through selection of a particular type of document to have generated and database record selection criteria, the database management program generate the selected document on the printer 125 (FIG. 1).
For example, if the user desired to print a blank pleading, the user navigates the database management program until he reaches a list of documents which the database management program can generate. Document choices may be organized into one or more hierarchical or linked menus. Preferably, the database management program responds by requesting the user select a client to which the document will relate. The database management program preferably provides a scrollable list or other device to permit simple and friendly selection of a desired client record. Next, the database management program provides the user with a sub-menu from which the user selects the specific document to be produced--"Blank pleading" in this example.
The database management program then gathers data from the tables to generate the document. In the case of a blank pleading and some other documents, the database management program generates the document in an editable format, such as in a wordprocessor format. The PI Powertool accomplishes this by exporting the data needed by the blank pleading document, and through macros causes WordPerfect to generate the bank pleading.
To generate the blank pleading, the database management program uses the client ID of the client selected by the user to determine the file number of the client's case. From the file number, the database management program can access all of the related defendant records in the defendants table 220, and can obtain the names 602 of all of the defendants in the case. The client ID will also provide access to a client record in the clients table 305, so the database management program can determine which firm attorney 508 is assigned to the case. The identity of the firm attorney from the client record links to the firm attorneys table 405, which will have the name of the attorney 3001 so that the attorney's name is printed at the top of the pleading. The database management program obtains the name of the court through the court ID in the related incident record in the incidents table 205, from which the court's name can be found in the courts table 435. Of course the particular data needed by each document will vary, and one of ordinary skill in the art can identify the tables and fields having the desired data to produce the document and the linked fields necessary to find that data.
The database management program preferably can also print generated documents directly. For example, Judicial Council Forms are in a format which is generally incompatible with most word processors. Accordingly, the Judicial Council Forms are stored in a graphic-type format, and the database management program places the data in the proper position in the desired form. If the user has properly entered all needed data into the database, then the database management program can gather this data, through linkages such as the client ID, fill in the data in the form, and print the form.
Although exemplary embodiments of the present invention have been shown and described, it will be apparent to those having ordinary skill in the art that a number of changes, modifications, or alterations to the invention as described herein may be made, none of which depart from the spirit of the present invention. All such changes, modifications and alterations should therefore be seen as within the scope of the present invention.
Claims
It is claimed:
1. An electronic case manager for a personal injury plaintiffs law office in which client and defendant level data related to an injury incident are collected, the electronic case manager including a computer having a storage device, an output device, and system software for inputting, managing and outputting case data comprising: (a) a data structure programmed and arranged for classifying data in a relational structure comprising a plurality of tables, the tables comprising plural records relating to personal injury-causing incidents, each record comprising at least one field, the tables comprising: (i) a clients table for storing information about clients in client records, (ii) a defendants table for storing information about prospective and actual defendants for claims by law office clients for personal injuries in defendant records, (iii) an insurers table for storing information about insurers in insurer records, (iv) an attorneys table for storing information storing about defense and insurance attorneys in attorney records, (v) an incidents table for storing information about injury-causing incidents in incidents records, (vi) a property damage table for storing information about property damage in property damage records, (vii) a loss of earning table for storing information about loss of earnings in loss of earnings records, (viii) a medical bills table for storing information about medical bills in medical bills records, (ix) a witnesses table for storing information about witnesses in witness records, (x) an expert witnesses table for storing information about expert witnesses in expert witness records, (xi) an evidence table for storing information about evidence in evidence records, (xii) a litigation table for storing information about litigation in litigation records, (xiii) a depositions table for storing information about depositions in deposition records, (xiv) a discovery table for storing information about discovery in discovery records, (xv) a motions table for storing information about motions in motion records, (xvi) a costs table for storing information about court costs in costs records, (xvii) an arbitrations table for storing information about arbitrations in arbitration records, (xviii) a police reports table for storing information about police reports in police report records wherein the tables are linked through certain identical fields, the linkages comprising: a file number field is included in and required in the records of the clients table, the defendants table, the insurers table, the attorneys table, the incidents table, the property damage table, the loss of earning table, the medical bills table, the witnesses table, the expert witnesses table, the evidence table, the litigation table, the depositions table, the discovery table, the motions table, the costs table, the arbitrations table and the police reports table, the file number field comprising a unique reference number for referencing incidents, a client name field is included in and required in the records of the clients table, the loss of earning table, the medical bills table, the discovery table and the costs table, the client name field comprising a client's name and is unique in each table for each file number, (b) a database manager programmed and arranged for managing the data structure to allow users to generate documents on the output device, (i) the database manager including instructions for merging data stored in records in the tables with document templates in accordance with predefined merge rules, (ii) the database manager managing the data structure in accordance with predefined structure rules, the structure rules including: 1) for each incident there will be at least one client record, 2) for each incident there will be at least one defendant record, 3) for each incident there will be at least one insurer record, 4) for each incident there may be one or more attorney records, 5) for each incident there will be only one incident record, 6) for each incident there may be one or more property damage records, 7) for each incident there may be one or more loss of earnings records, 8) for each incident there may be one or more medical bills records, 9) for each incident there may be one or more witness records, 10) for each incident there may be one or more expert witness records, 11) for each incident there may be one or more evidence records, 12) for each incident there may be one litigation record, 13) for each incident there may be one or more deposition records, 14) for each incident there may be one or more discovery records, 15) for each incident there may be one or more motion records, 16) for each incident there may be one or more costs records.
2. The electronic case manager for a personal injury plaintiffs law office set forth in claim 1, the client records comprising: (a) a file number field for storing the file number associated with the given incident, (b) a name field for storing a name of a given client having an injury arising from the given incident, (c) an address field for storing the given client's mailing address, (d) a date of birth field for storing the given client's date of birth, (e) a first government identification field for storing the given client's drivers licence number, (f) a second government identification field for storing the given client's social security number, (g) a salutation field for a salutation to the given client, (h) an event type field for storing a type of event which led to the given client's injury, (i) an assigned attorney field for storing a name of a law office attorney assigned to represent the given client, wherein the table includes pre-defined, standard types with filled-in values such that when product components and product component specifications are added, a user may choose from a list of common components to copy thereby promoting efficiency and data integrity.
3. The electronic case manager for a personal injury plaintiffs law office set forth in claim 1, the defendant records comprising: (a) a file number field for storing the file number associated with the given incident, (b) a name field for storing a name of a given prospective or actual defendant in the given incident, (c) an address field for storing the given defendant's mailing address, (d) a date of birth field for storing the given defendant's date of birth, (e) a first government identification field for storing the given defendant's drivers licence number, (f) a defendant entity type field for storing whether the given defendant is male, female or corporate, (g) a service date field for storing a date when the given defendant was served with a complaint.
4. The electronic case manager for a personal injury plaintiffs law office set forth in claim 1, the insurer records comprising: (a) a file number field for storing the file number associated with the given incident, (b) an insured name field for storing a name of a party having insurance coverage relating to the given incident, (c) an adjuster name field for storing a name of an insurance adjuster assigned to represent an insurer in the given incident with respect to the insured whose name is in the insured name field, (d) an insurance policy number field for storing an insurance policy number for the insurance policy of the insured whose name is in the insured name field, (e) a claim number field for storing a claim number used by the insurer with respect to the incident, (f) a policy limits field for storing the monetary limits of the insurance policy of the insured whose name is in the insured name field, (g) a medical payments field, (h) a reimbursement field, (i) a rental car field for storing whether the insurance policy provides for payment for a rental car, (j) an uninsured motorist field for storing whether the insurance policy provides for payment for uninsured motorist claims, (k) an uninsured motorist limits field for storing an amount of coverage for uninsured motorist claims.
5. The electronic case manager for a personal injury plaintiffs law office set forth in claim 1, the incident records comprising: (a) a file number field for storing the file number associated with the given incident, (b) an incident date field for storing the date of the given incident, (c) an accident type field for storing the type of incident, (d) a location field for storing the location of the incident, (e) a description field for storing a narrative description of the incident, (f) a code violation field for storing references to governmental rules, regulations and laws under which a citation was issued for the given incident, (g) a conditions field for storing a description of any environmental conditions relevant to the given incident, (h) a prior accidents field.
6. The electronic case manager for a personal injury plaintiffs law office set forth in claim 1, the tables further comprising: (a) a body shops table for storing information about body shops in body shop records, (b) an attorney information table for storing information about attorneys in attorney name records, (c) an adjusters table for storing information about insurance adjusters, (d) a medical providers table for storing information about medical care providers; wherein the tables are linked through identical fields, the linkages comprising: a body shop name field is included in and required in the records of the body shops table and the property damage table, the body shop name field comprising a unique key for referencing a body shop, an attorney name field is included in and required in the records of the attorneys table and the attorney names table, the attorney name field comprising a unique key for referencing an attorney, an adjuster field is included in and required in the records of the adjusters table and the insurance table, the adjuster field comprising a unique key for referencing an insurance adjuster, a medical provider name field is included in and required in the records of the medical providers table and the medical bills table, the medical provider name field comprising a unique key for referencing a medical care provider; the structure rules including: there may be one or more body shops records for each property damage record, and multiple property damage records may have identical data in their body shop name fields, there will be one attorney name record for each attorney record, and multiple attorney records may have identical data in their attorney name fields, there will be one adjuster record for each insurance record, and multiple insurance records may have identical data in their adjuster name fields, there will be one medical provider record for each medical bill record, and multiple medical bill records may have identical data in their medical provider name fields.
Patent Citations (7)
Non-Patent Literature (7)
- Robert Reilly, "Mapping Legal Metaphors in Cyberspace: Evolving the Underlying Paradigm", The John Marshall Journal of Computer and Information Law, pp. 579-581, Spring, 1998.
- www.amicus.ca/forms/supportmail.html, Feb. 2000.
- www.apollosoftware.net, Feb. 2000.
- http://courtstuff.com/5th/index.html, Feb. 2000.
- www.state.nj.us/judiciary/demrpt.htm, Feb. 2000.
- wysiwyg://41/http://www.amicus.ca/, Feb. 2000.
- www.amicusattorney.com/upgrade/index.html, Feb. 2000.