WO1997041524A9 - Legal claims processing system and methods of litigation management using the same - Google Patents

Abstract

An Integrated and automated system for use in caseload management is disclosed. The system includes a central hub (20) having an authorized subscriber database (26), a routeur (22), and a selector (24). Each authorized subscriber is linked (27) to the central hub (20) via a subscriber system (30). The subscriber system (30) includes a workstation at which information may be displayed and entered and a data storage medium having a new cases database (34), a communications management database (36), and a billing database. Each source or insurer is connected (28) to the central hub (20) via a source system (40). The source system includes a workstation at which information may be displayed and entered and a data storage medium having a new claims database (42), a communication management database (44), and billing database (46). New claims are submitted by the source and undergo a new claims authorization process carried out by the disclosed system. The claims authorization process involves the selection of a subscriber and an option conflict check process and a budget approval process. After a new case is authorized, a communication link is established through the central hub (20) between the source (40) where the claim originated and the selected and authorized subscriber (30). The system also provides processes for requesting approval in connection with certain activities for cost-containment purposes.

Description

LEGAL CLAIMS PROCESSING SYSTEM AND METHODS OF LITIGATION MANAGEMENT USING THE SAME

FIELD OF THE INVENTION

The present invention relates generally to data processing systems and networks. More particularly, the present invention relates to a legal claims processing system and methods of using the legal claims processing system for caseload management.

BACKGROUND

The rising costs associated with insurance-based claims litigation has prompted a concerted effort by both legal service providers and insurers to establish cost-containment measures. Such measures have been implemented with technology- based solutions. These solutions have included, for example, automated computer systems used by a legal service provider for tracking the status and managing cases handled by that legal service provider (see e.g., U.S. Patent No. 5,182,705 issued January 26, 1993). However, such system fail to provide automated processes between the insurers and legal service providers whereby necessary information can be easily communicated and exchanged. For example, when a claim is filed by an insured with his or her insurance company, a claims adjuster must make personal contact with a legal service provider to represent the insurance company in relation to that claim. The claim adjuster currently makes this contact by telephone or by mail. The legal service provider often will perform an internal conflict check to ensure that it can represent the insurer on the designated claim. If the legal service provider requires additional information to perform this conflict check, then the legal service provider must call the claims adjuster and request additional information. Often what ensues is a series of telephone tag between legal service provider and claims adjuster even before the claim is successfully assigned to counsel. Therefore, there is a need for a more efficient process to assign a claim to counsel.

Once a legal service provider acknowledges that it has no conflict and is willing to represent the insurance company on the claim, the insurer often request a proposed budget plan from the legal service provider. The budget plan may be transferred by mail. In the event that the budget plan requires modifications or is otherwise unacceptable to the insurer, the claims adjuster must convey that information by telephone or by mail back to the legal service provider. The process of agreeing on an acceptable budget for the case often requires substantial time. Thus, there exists a need for a more expeditious budget proposal and acceptance process for case management purposes.

After a claim is assigned, information from the claims adjuster's files or electronic data that may already be available in an automated insurance policy tracking and management system such as that disclosed in U.S. Patent No. 5,191,522 issued March 2, 1993, must be forwarded to the legal service provider. That information is typically transferred via mail and thus the legal service provider upon receipt of that information must manually enter into its internal case tracking and management system or merely maintain a paper file. As more information is received either by the insurer or the legal service provider, the information is routed up and back via mail in paper form so that both the insurer and the legal service provider can maintain complete files relating to the adjudication of the claim. Therefore, there is a need for a more efficient means for both legal service providers and insures to share and access relevant information.

During the course of litigation, the insurer often requires that the legal service providers request authorization before proceeding with certain litigation related tasks, e.g. , deposition of an expert witness, filing of a motion for summary judgment, etc. Thus legal service providers, typically must request authorization in writing by mail or facsimile and await written authorization from the claims adjuster via mail or by facsimile before proceeding with the task. If the insurer or claims adjuster needs more information before providing authorization, the claims adjuster and the legal service provider may then engage in further rounds of telephone tag until the requisite information can be obtained. This process often takes days or even weeks before authorization is granted by the claims adjuster and received by the legal service provider. Consequently, there exists a need for an expedient method of authorizing litigation tasks during the course of litigation.

Decisions regarding settlement and alternative dispute resolution are made by the insurer, and therefore, the claims adjuster should have access to the same information maintained by the legal service provider to track and manage cases being handled by the legal service providers. Thus, there additionally, exists a further need for the insurer to have access to the information maintained by the legal service provider.

While much of the claim-related information may now be transmitted between legal service providers and insurers using electronic communications, no integrated system currently exists for management and control of this information in one system. Importantly, without such a system there currently exists no integrated and automated approach to case assignment procedures, budget proposal acceptance, case tracking and evaluation by both legal service providers and insurers, litigation task authorization and the like.

SUMMARY OF THE INVENTION

The present invention fulfills the aforementioned needs by providing an automated litigation management system and methods for automating the different cost- containment approaches utilized by insurers and legal service providers in a single integrated efficient system. This is accomplished by providing a method of managing litigation using an automated litigation management system networking a source of the litigation to a plurality of subscribers through a central hub. The method includes steps for entering new claim information relating to a new litigation into a source new claims databases associated with the source; transmitting a new claim signal in response to the entry of the new claim information into the source new claim database to a central processing means associated with the central hub and interfaced to a plurality of subscriber processing means each being associated with one of the plurality of subscribers; selecting one of the plurality of subscribers in response to the transmission of the new claims signal; transmitting at least some of the new claims information to the selected subscriber; and automatically storing the new claim information so transmitted in a subscriber new cases database accessible by the subscriber processing means associated with the selected subscriber.

In a preferred embodiment, the method additionally includes steps for verifying that no conflict exists within the selected subscriber based on the new case information stored in the subscriber new cases database; and generating an electronic response indicative of the verification and transmitting the same to the source. In another preferred embodiment, the method also includes selecting a different one of the plurality of subscribers if based on the electronic response a conflict exists. In a more preferred embodiment, the method further includes steps for preparing a litigation proposal based on the new claim information stored in the subscriber new cases database; transmitting proposal data indicative of the litigation proposal to the source; storing the proposal data in the source new cases database; and transmitting a proposal response to the selected subscriber indicating whether the litigation proposal is acceptable. Preferably, the proposal response is representative of any one of a proposal acceptance, a proposal denial, and a request for more information. The new case information may be stored in a subscriber case database associated with the selected subscriber if the litigation proposal is acceptable.

The aforemention needs are also fulfilled by the present invention in which another method of managing litigation using an automated litigation management system networking a source of the litigation to a plurality of subscribers through a central hub is disclosed. This method includes steps for generating a request for approval to perform a litigation activity; transmitting the request for approval from a subscriber processing means associated with one of the plurality of subscribers to a source processing means associated with the source; transmitting an activity response indicative of a decision to approve or deny the activity request; and updating a subscriber authorization database accessible by a subscriber processing means associated with the one subscriber. In a preferred embodiment, this method also includes steps for generating a request for payment associated with the activity when the activity is completed; enabling a transmission of the request for payment if the activity request was approved; and disabling the transmission of the request for payment if the activity request was denied.

A litigation management system interconnecting at least one source of information and a plurality of subscribers where each of the plurality of subscribers has an associated office litigation administration system for facilitating the administration of litigation by the subscriber is also provided by the present invention. The system according to the invention includes a source system for providing source information relating to new and on-going litigations and for receiving subscriber information relating to the same litigations; a plurality of subscriber interfaces configured to receive source information and store the source information in the associated office litigation administration systems and to retrieve subscriber information from the associated office litigation administration systems and transmit the subscriber information so retrieved to the source system; and a central processing means interfaced to receive source information from the source system and subscriber information from the plurality of subscriber interfaces for establishing authorized links between the source and the plurality of subscribers based on predetermined criteria.

In a preferred embodiment, the system also includes a subscriber database interfaced with the central processing means for storing data relating to each of the plurality of subscribers. The central processing means preferably includes a selection means for selecting one of the plurality of subscribers based on at least some of the source information and the data stored in the subscriber database. In yet another preferred embodiment, the system includes a new claims database for storing new case information relating to new litigations. The source system preferably transmits at least some of the new claim information as source information to the central processing means thereby initiating a procedure to establish one authorized link. In a more preferred embodiment, the system additionally includes a database or multiple databases for storing subscriber information relating to the authorization of the predefined activities carried out by each subscriber connected to the source through one of the authorized links established by the central processing means. Still further, the system preferably includes a new cases database for storing source information received from the central processing means to establish one authorized link between the subscriber associated with the same subscriber interface. The same subscriber interface preferably transfers the new case information from the new cases database to the associated office litigation administration system after the central processing means establishes the authorized link.

BRIEF DESCREPTION OF THE DRAWINGS

The present invention will be better understood, and its numerous objects and advantages will become apparent by reference to the following detailed description of the invention, when taken in conjunction with the following drawings, in which: Figure 1 shows an exemplary network provided by a litigation management system according to the present invention;

Figure 2 shows a block diagram of a legal claims processing system according to the present invention including its functional and database components and the interfaces between those components; Figure 3 shows a flow diagram of the overall process carried out in accordance with the present invention;

Figures 4A and 4B show a more detailed flow diagram of the steps carried out in connection with the new case authorization process in accordance with the present invention; Figure 5 shows a detailed flow diagram of the activity authorization process in accordance with the present invention;

Figure 6 shows a block diagram of the billing control function residing within the subscriber system in accordance with a preferred embodiment of the invention; Figure 7 shows an example of a main menu displayed when logging into the subscriber system in accordance with a preferred embodiment of the invention;

Figure 7A shows an example of an initial screen displayed in connection with the insurance claims database;

Figure 8 shows an example of a new claim database interface in accordance with a preferred embodiment of the invention; Figure 8A shows an example of a policy information field used in accordance with the claims database with a preferred embodiment of the invention ;

Figure 9 shows an example of the claims database interface in "Edit" function mode in a preferred embodiment of the invention; Figure 9A shows an example of "request types" available in the new claim database within the source system in a preferred embodiment of the invention;

Figure 9B shows an example of a list of subscribers available within the source system to assign a new claim in a preferred embodiment of the invention;

Figure 9C shows an example of a screen in the claim database to add additional notes to a claim within the source system in a preferred embodiment of the invention;

Figure 10 shows an example of a screen with a product liability claim available in the claims database within the source system in a preferred embodiment of the invention; Figure 11 shows an example of a screen with a workers' compensation claim available in the new claim database within the source system in a preferred embodiment of the invention;

Figure 12 show an example of options for selecting a claim type available in the claims database within the source system in a preferred embodiment of the invention;

Figure 13 shows an example of a selected claim type in the claims database within the source system in a preferred embodiment of the invention;

Figure 14 shows that a claims processor has selected a product liability claim type from the claims database within the source system in a preferred embodiment of the invention;

Figure 15 shows an example of a screen available to allow a claims processor to select a subscriber to assign a new claim in a preferred embodiment of the invention;

Figure 15A shows a partially completed claim screen as imputed by a claim processor within the source system in a preferred embodiment of the invention;

Figure 15B shows a new claim assignment selection process in which a claims processor selects a subscriber to assign to a new claim within the source system in a preferred embodiment of the invention;

Figure 15C shows an acknowledgment of a successfully completed assignment of a new claim by the source system in a preferred embodiment of the invention; Figure 16 shows an assignment of an investigation request from a claims processor to an outside investigator or adjuster within a source system in a preferred embodiment of the invention;

Figure 16A shows a completed investigation report sent by an investigator or adjuster to a claims processor in a preferred embodiment of the invention;

Figure 17 shows an example of a request for a status report available within the source system sent by claims processor to subscriber in a preferred embodiment of the invention;

Figure 17A shows an example of a collapsed status report and how a subscriber returns it to the claims processor in a preferred embodiment of the invention;

Figure 18 shows the lists of requests available to a subscriber in the cases database within the subscriber system in a preferred embodiment of the invention; Figure 18A shows an example of a requestor comments pop-up box available to a subscriber in the cases database in a preferred embodiment of the invention;

Figure 19 shows an authorization request as completed by a subscriber and sent to the source system in a preferred embodiment of the invention; Figure 19A shows an example of how source transmits acceptance or rejection of authorization back to the subscriber in a preferred embodiment of the invention;

Figure 20 shows an example of a deposition report completed and sent by a subscriber to the claims processor in a preferred embodiment of the invention; Figure 21 shows a request for a pre-trial report sent by a claims processor to a subscriber available within the source system in a preferred embodiment of the invention; Figure 21 A shows how the pre-trial report is transmitted back to the claims processor by the subscriber in a preferred embodiment of the invention; and

Figure 22 shows an example of the communications management database within both the source and subscriber systems in a preferred embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides an automated data processing system adapted to network providers of legal services such as law firms, clients, and other necessary parties such as court reporters, investigators, expert witnesses, etc. to enhance communication between these entities and to improve workflow and efficiency. While the present invention will be described herein by reference to a litigation management system for law firms (hereinafter "subscribers") and the insurance companies which process a substantial volume of claims filed against insured individuals, it should be understood that the invention may be used to provide caseload management between legal service providers, clients other than insurers, and a variety of legal support vendors, informational sources, and other third party users of the system. Thus a detailed description of one embodiment of the invention is described in connection with Figure 1-22 wherein like reference numerals refer to like elements in the respective drawings. An exemplary network provided by a litigation management system according to the invention is shown in Figure 1. Each insurer provides an insurer server 2 that is interconnected to a central server system (hereinafter "central server") 4 via communication links 3. The central server 4 functions as a central hub such that all information transported in the network passes through the hub. As shown in Figure 1 , the central server 4 also interfaces with a plurality of subscriber servers 6 via communication links 5. Each subscriber server is associated with one particular subscriber. Each of the subscriber servers 6 may be coupled to one or more terminals or workstations 11 (only a single terminal is generally designated in the figure). Similarly each of the insurer servers 2 and the central server 4 is connected to one or more terminals or server/ workstations 9 and 13 respectively. Thus, the network effectively provides communications between a plurality of subscribers and a number of insurers through the central hub. While only two insurer servers and three subscriber servers are shown, it should be understood that any number of either may be supported by the network within practical limitations of the network hardware and software. The hardware and software required to support the invention are substantially unrestricted. The servers 2, 4, 6 may be supported by a variety of platforms such as X86 Intel platforms including WINDOWS/NT, OS/2 and NOVELL NETWARE and UNIX platforms including SUN SPARC, IBM R/6000 and HP PA- Risc, to name a few examples. The communication links 3, 5, may be implemented via standard telephone lines and interconnected via local area networks (LANs), wide area networks (WANs), or Internet access links. However, other forms of communications could also be used and the invention is not intended to be so limited to the examples set forth herein. Server/workstations 9, 11 , 13, are also essentially application independent in that they may be configured for various platforms such as WINDOWS 3.1 , WINDOWS 95, WINDOWS/NT, OS/2 and MACOS.

To provide such a platform independent system, LOTUS NOTES which is available from Lotus Development Corp. is preferably used to implement the present invention. However, other database and network software applications could similarly be used. In a preferred embodiment, one or more affiliated users having user workstation 8 may also be included in the network through a communication link 7 to the central server 4. It should be understood that each user may alternatively provide a server with one or more terminals or workstations connected thereto. The users may be legal support vendors or other third party users of the litigation management system (i.e. , travel agents).

In a further preferred embodiment, the central server 4 and terminal 13 are duplicated to provide system redundancy. As shown in Figure 1 a central back-up server 10 and a terminal or workstation 14 coupled thereto are connected to the central server 4 with its terminals or workstations 13 through a high speed interconnection 12, such as ISDN so that all of the information stored on the central server 4 may be duplicated and stored on the central back-up server 10. Preferably, the central back-up server(s) and workstations are physically located at a different facility than the central server. In the event of a failure at the central hub, communications can be promptly reestablished through the central back-up server.

Figure 2 is a block diagram showing the legal claims processing system according to the invention including its functional and database components and the interfaces between those components. A router 22, selector 24 and a subscriber database are preferably provided by the central hub system 20. Each subscriber has a subscriber system 30 which transmits subscriber information via links 27 to the central hub system 20. Router 22 receives subscriber information transmitted from any of the subscriber systems and routes the transmission to the intended source system 40. Because an insurer is a source of new claims, it is referred to as a

"source. " Each insurer or source has a source system 40 connected to the central hub through a link 28 over which subscriber information may be routed from router 22. In a similar manner, source information which is described in detail below is generated by the source systems and transmitted to the router over links 28. The router 22 operates to transmit the source information to a designated subscriber system via the appropriate link 27.

Each subscriber system functions as an interface between an internal office case administration system 32 and the legal claims processing system. Conventional internal office case administration system may store information relating to each case being handled in the office, client information and staff assignments. Moreover, such systems may also be capable of tracking the status of calls, appointments, documents, litigation activities and client billing. One such system is INTERTRAC FOR LAW which was developed and is marketed by Computer works, Inc. Albany, NY. The subscriber systems 30 each preferably include an insurance claims database 34, a communications management database 36, and a billing controller 38. The source systems 40 each preferably include a new claims database 42, a communications management database 44, and a billing status database 46. The functionality of each of the components shown and the use of each database will become apparent by reference to Figures 3-22 and the following description which accompanies the figures.

Figure 3 shows a flow diagram of the overall process carried out in

11

SUBSΠΠΠE SHEET (RULE 26) accordance with the invention. A claims processor at an insurer receives a new claim 50 and initiates a new case authorization process at step 52. Once a subscriber is selected and approved by the insurer as is described in detail below in connection with the description of the new case authorization process, the central hub system establishes an authorized link between the source system and the selected subscriber s subscriber system at step 54.

During on-going litigation, the subscriber may be required to seek approval from the insurer for certain activities such as taking various depositions, retaining an expert witness, attending a settlement conference, etc. The selected subscriber may transmit a request and receive approval through the activity authorization process shown at step 56. Once an approved activity has been completed, the billing controller may be used to control the transmission of requests for payment of services associated with the activity as shown at step 58.

In addition, during an on-going litigation the claims processor may review the status of the insurer s cases or status of the billing for cases handled for that insurer as shown at 62 and described in more detail below.

In a preferred embodiment, a record keeping utility may be provided to store any of the case billing, activity, case disposition, etc. information for a given case after its final disposition so that information may be purged from the system s working databases and used subsequently for analysis, statistics, and educational purposes.

Figures 4A and 4B show a more detailed flow diagram of the steps carried out in connection with the new case authorization process in accordance with the invention. When a new claim is submitted to the insurer, information relating to the claim is entered into the source insurance claims database at step 70. The source system transmits at least some of the information that is entered as new claim information to the central hub system at step 72. The new claims information may be processed by the central to access a list of possible subscribers which are transmitted to the source system and displayed by the claims adjuster. The selector may be used in this process for identifying possible subscribers based on criteria specified by the source, e.g. particular subscribers that the source likes to work with. The claims adjuster may then select one of the subscribers from the list and transmit the selection to the central hub. The router establishes an initial communications link between the selected subscriber and the source transmitting the new claim information at step 78. Upon doing so, the router forwards at least some of the new claim information to the subscriber system of the selected subscriber. In an alternative embodiment, the selection of the subscriber may be made automatically by the litigation management system. In this embodiment, the new claims information contains at least certain predetermined fields with information that may be extracted by the router and provided to the selector at step 74. The subscriber database contains information relating to each of the subscribers in the network such as identification and address. The selector searches the subscriber database at step 76 to select one of the subscribers based on the extracted information. The selector then outputs the identity of the selected subscriber to the router.

The selected subscriber system receives the information transmitted by the router and stores it in the subscriber new cases database at step 80. The subscriber may perform an internal conflict check at step 82 and enter a new case budget proposal at step 86 if no conflict exists. If a conflict exists as determined at step 82, a conflict resolution procedure is initiated at step 84 so that a new subscriber may be selected at step 76. In a preferred embodiment, the subscriber new cases database is purged once a conflict is identified and prior to initiation of the conflict resolution procedure to select a different subscriber. The selection of a subscriber at step 76 and the conflict resolution procedure shown at step 84 are described in more detail below.

The new case budget proposal includes budget proposal data indicative of the strategy for litigating the claim and the anticipated costs associated with that strategy. The new case budget is transmitted from the selected subscriber s subscriber system through the router and ultimately to the source system that transmitted the new claim information as shown at step 88. The budget proposal data is stored in the source new claims database at step 91 so that it can be reviewed by the claims processor or insurer. If the new case budget proposal is acceptable as determined at step 90, an acceptance is transmitted back to the selected subscriber at step 96. The central hub system then may establish an authorized link between the selected subscriber and the source at step 98. Upon receipt of the acceptance, the selected subscriber transfers the new case information stored in the subscriber new cases database to the internal office case administration system associated with the selected subscriber at step 100.

If the insurer does not accept the new case budget proposal, then the insurer and subscriber may negotiate or the new claim information may be purged from the subscriber's new cases database. Alternatively, the insurer may ask for additional information or modification of the new case budget proposal as shown at step 92 and 102 until acceptance is obtained.

Figure 5 shows a detailed flow diagram of the activity authorization process in accordance with the invention. Certain litigation-related activities may be designated as requiring authorization from the insurer prior to performance of such activities. For example, authorization might be required before a subscriber deposes an expert witness. If such authorization is required, the litigation management system in accordance with the invention provides an automated system for seeking and receiving approval for such activities. In addition, the automated authorization can be used in connection with an automated billing control function. As is described below, the billing control function disables any request for payment from being submitted until authorization for the services, i.e., the activity, has been received.

As shown in Figure 5, a subscriber may request authorization by entering activity related information into the subscriber new case database at step 110. The activity information is then submitted with a request for authorization at step 112. The source communications management database is then updated with the request for authorization and the related activity information at step 114. A claims processor at the insurer may then review the request and information and decide whether or not to approve the activity at step 116. If the claims processor approves the activity, the approval is entered through the source communications management database and submitted at step 118. The subscriber communications management database is then updated to reflect the approval at step 119 and the billing controller may likewise be notified of the approval at step 120.

If the claims processor requires more information to evaluate the request for authorization at steps 116 and 122, the claims processor may specify the additional information needed by entering the information into the source communications management database and submitting the request for more information at step 124.

14

SUBSΠTUTE SHEET (RULE 26) The subscriber communications management database is then updated to reflect the additional information required at step 126. The subscriber may respond by repeating steps 110 and 112 with the requested activity information.

If the claims processor denies the request at steps 116 and 122, the claims processor enters the denial response into the source communications management database and submits it at step 128. The subscriber communications management database is then updated at step 129 to reflect that authorization for the designated activity has been denied. If the request for authorization is denied the subscriber may appeal the denial at step 125 by effectively resending the request with a modified case budget proposal. In a preferred embodiment, the billing controller may be notified that the request was denied as shown at step 120.

As discussed in connection with Figures 4 A and 4B, the central hub system is preferably configured to select an appropriate subscriber or a multiplicity of possible subscribers to handle a new claim filed against a connected insurer. In one preferred embodiment, a primary and alternate subscriber per specified geographic region, e.g. , based on judicial jurisdiction, may be networked to the litigation management system. In such an embodiment, a field may be provided in the insurance claims database to indicate in which jurisdiction the claim has been filed. The central hub system preferably has access to the information contained in this field so that the information may be extracted. In this embodiment, the subscriber database may list each primary and alternate subscriber by jurisdiction or geographic region. The selector at the central hub shown in Figure 2, may then search the subscriber database to identify the primary subscriber in the jurisdiction identified in the new claim information transmitted from a source system. The central hub system then transmits the new claim information to the primary subscriber. In a more preferred embodiment, however, the central hub identifies each connected subscriber within the judicial district and transmits a list of identified subscribers to the source from which the new claim information originated for the purpose so that a claims processor may select one of the identified subscribers. If the first selected subscriber has a conflict as discussed above or if the insurer is unable to approve the first selected subscriber s case budget proposal, another subscriber in the same jurisdiction may be selected by the claims processor or by the litigation management system. The alternate subscriber would follow the same authorization process described above in connection with Figures 4A and 4B. It should be understood, that more than one alternate subscriber may be referenced to a particular jurisdiction to increase the probability of a successful authorization. It should further be understood that subscribers could be selected based on numerous other criteria. If such other criteria are used, then the subscriber database would contain the networked subscribers referenced to the selection criteria. Consequently, the invention is not intended to be limited to the selection of the subscriber based on location. Referring back to Figures 4A and 4B, it is also preferred to provide the insurers with a means for monitoring the insurers' cases handled by each of the subscribers. So long as the subscribers use an internal office case administration system that stores status and other information related to the cases handled by the subscriber, such information can be transferred to the source cases database so that the insurer has access to this information through the source system. It should be understood that the information may be transferred at regular programmed intervals, upon status changes or upon request.

Similarly, an insurer may wish to review the billing status as time to matters for that insurer accrue. So long as this information is maintained by the internal office case administration system used by the subscriber, the billing status information may be transferred to the source billing status database. Again it should be understood that the information may be transferred at regular programmed intervals, upon status changes or upon request.

A block diagram showing the billing control function residing in the subscriber system is shown in Figure 6. A request for payment 130 may be generated by the internal office case administration system. The request is preferably received by the billing controller 132. The billing controller may then check an activity approval database 134. The activity approval database may be incorporated in the subscriber Communications Management database or may be a separate database including only the activities that were approved or denied by the insurers. If the activity for which the request for payment has been generated was approved, then the billing controller may transmit the request for payment 136 to the source system. If the request for authorization for the activity for which payment is required had been denied, the billing controller may hold the request for payment in a preferred embodiment and provide an indication 138 that the request for payment has held to the internal office case administration system. This may signal a billing discrepancy and permits staff at the subscriber to take whatever action is appropriate.

While the invention has been described in detail regarding the communication and procedures employed between subscriber systems and source systems, it should be understood that other user systems may communicate in a similar fashion. For example, after the taking of a deposition is approved, the activity information may be transferred through the central hub to a selected court reporter having a networked reporting system. In this example, the activity information might include, the name and address of the person to be deposed, the place of deposition, and the date and time of the deposition. The court reporting system could indicate the availability of its court reporters, and moreover, include the deposition testimony after the deposition is taken in fields relating to the case information. The deposition testimony text may be formatted based on network specifications.

To better describe the new claim authorization process and the activity authorization process described above, the processes will again be described in connection with examples of the user interfaces provided to carry out these procedures. Figure 7 shows an example of the main menu that might be displayed when logging into the subscriber system. A number of buttons are shown, however, only the Insurance Claims button 200 and the Communications Management button 202 are described herein in connection with the invention. Many of the other buttons shown are provided by an internal office case administration system. Thus, a similar menu is preferably displayed by the source system that may contain internal office administration buttons for the source, but they are separate and distinct from the subscriber's internal office administration system.

Selecting the Insurance Claims button 200 from the main menu from the source system preferably brings up the insurance claims database user interface. Figure 7A shows an example of an initial screen displayed in connection with the insurance claims database. Each claim currently entered in the insurance claims database is preferably listed in selection area 204. A single claim can be selected to

17

SUBSΠTUTE SHEET (RULE 26) display the information stored in the database or new claim information may be entered by clicking on the new claim button 212.

A claim may be selected, for example claim number COO 11 in Figure 7A and then opened by clicking on the open designator to bring up the claims interface with the information stored pertaining to the selected claim. An example of a claim interface is shown in Figure 8. The components of the interface will change depending on the type of claim, i.e. , a product liability claim will preferably employ a product liability screen and a workers' compensation claim will preferably employ a workers' compensation screen. The interface shown in Figure 8 is shown in PREVIEW mode which allow the viewer to review the data. As shown, the claims processor is provided with a number of fields 208 that may be selected to open a pop-up box or entry interface 206, shown in Figure 8A. For example, in Figure 8A, the policy information field has been selected and the entry interface associated therewith has been opened. The entry interface shows the data input from the claims processor relating to policy information, such as limits of insurance, deductibles and endorsements, etc. Returning to Figure 8, each of the fields 208 preferably has an entry interface for receiving and storing the data input from either the claims processor or subscriber.

If the user wishes to edit the data, the "Edit" function 209 may be selected from the menu bar to bring up an edit interface screen. An example of a claim information edit interface screen is shown in Figure 9. Once the editing is complete, the claims processor clicks on the Save button 231 to retain the edited information. If the user wishes to delete the edited material, the Cancel button 232 is clicked. A plurality of buttons 214 are shown in Figure 8 to, for example, request an action as shown in Figure 9A by clicking on the "Request" button, to assign a legal service provider as shown in Figure 9B by clicking on the "Assign" button, or to add additional notes as shown in Figure 9C by clicking on the "Notes" button.

The entry interface shown in Figure 8 preferably serves as the Conflict Check screen. The Conflict Check screen allows the claims processor to check with the selected subscriber or other player (i.e. , claims processor, investigator, etc.) for any conflict of interest within that subscriber/player that might prevent assignment of

18

SUESTΪTDTE SHEET (RULE 26) the claim. The Conflict Check screen is the same for all types of claims, i.e. , workers' compensation, products liability, auto, etc. The last action field 220 on the Conflict Check screen in Figure 8 preferably indicates the last completed action by any player connected to the litigation management system. Use of the Conflict Check screen signified by interface 210 in Figure 8 is preferably made optional for the claims processor. In a preferred embodiment of the invention, the claims processor completes a conflict check by entering the appropriate information in claims interface 210, assigning a law firm in connection with Figure 9A, and transmitting just the information entered in interface 210 to the selected subscriber. The system is designed to transmit the conflict check information only when the claims processor chooses this option. The claims processor upon receipt of an approval from the subscriber preferably completes the remaining fields 208 and then transmits that information to the selected subscriber.

In a preferred embodiment, a new claim may be added to the litigation management system. As mentioned above, the claims processor clicks on the new claim button 212, shown in Figure 7A. A screen is then preferably displayed with options for selecting a claim type as shown in Figure 12. In a more preferred embodiment, a general claim type may be highlighted as shown in Figure 13, whereupon the OK button is selected to proceed to more specific claim types as shown in Figure 14. After the claim type selection has been made, the claims processor preferably proceeds to fill in the information required in the claims interface 210 and relevant fields 208 as shown in Figures 8, 10, and 11. For example, a workers' compensation claim preferably employs a workers' compensation screen and additional screens such as one for the employer, the employee, relating to the occurrence of the accident or injury, one for contacts or witnesses, and one for treatment information (see Figure 11).

After the sub-fields of entry interface 208 have been completed as partially shown in Figure 15 A, the claims processor then preferably clicks on the assign button 221 in Figure 15 to assign the selected subscriber. An exemplary listing of potential subscribers 224 are shown in Figure 15B. The source system then preferably displays the assignment of the claim to the selected subscriber as shown in Figure 15C. Referring back to Figure 9A, as the claim adjudication process progresses, the claims processor may select options from the list shown. If an investigation, for example, is needed to be conducted by an outside adjuster or investigator, the claims adjuster selects the "investigation" option and clicks on the OK button. That action preferably brings up a listing of the possible investigative companies from a listing in the central hub database similar to the subscriber listing shown in Figure 9B. Preferably, the subscriber database shown in figure 2 stores information related to each of the systems intended users. Upon selection of a company, Figure 16 will appear and the claims processor completes instructions in the Requestor Comments section. The claims processor sends the Investigation Request through the central server system to the Investigator. The selected investigator receives the request as shown in Figure 16. When the investigation is completed, the investigator fills out the report and clicks on the Return button 225 to send it back to the claims processor as shown in Figure 16A. If the claims processor desires a status report on the claim from the subscriber, the claims processor selects the "Status Report" shown in Figure 9 A and clicks on the OK button. The request goes to the subscriber as shown in Figure 17, which shows the expanded pre-designed categories. After the subscriber completes the report by filling in information in each pre-designed category, the Return button 226 is clicked as shown in Figure 17A, which shows the categories in a collapsed state. If the subscriber requires authorization from the claims processor to perform a task, the subscriber clicks on the request button in the cases database, which brings up Figure 18. The subscriber clicks on the Authorization button as shown in Figure 18. A pop-up box entitled Requester Comments is then preferably brought up by the system as shown in Figure 18A. The subscriber preferably describes the specific authority request in the box and submits it to the user by clicking the OK button. The claims processor reviews the request as shown in Figure 19 and clicks on the Edit button 227. The screen changes to allow the claims processor to either Accept or Reject the request, with or without comment as shown in Figure 19A. The claims processor then clicks on the Return button 228 in Figure 19A to transmit the acceptance or rejection back to the subscriber.

The subscriber can report to the source on the results of the deposition by clicking on the Deposition Report button shown in Figure 18. The subscriber completes the report as shown in Figure 20 and clicks on the Return button. The report is sent on to the source.

The claims processor may request a Pre-Trial Report from the subscriber by selecting "Pre-Trial Report" from the option list shown in Figure 9A and then clicking on the OK button. An example of a pre-trial report is shown in Figure 21 and is then transmitted to the subscriber. The subscriber is notified by assessing the Communications Management database of the request and completes the information in the pre-designed categories, then clicks on the Return button as shown in Figure 21 A. The Communications Management Database is designed to maintain the various Request Types when they are sent by the source or subscriber and are awaiting action. An example of the Communication Management screen is shown in Figure 22 and the Request Types are shown in field 229. To view a particular Request Type, the user highlights the Request 230, and clicks on it. Figure 19 shows the displayed Request. In a preferred embodiment, this screen provides the same information at both the source system and the subscriber system. Once the request has been acted upon and is completed, the Request Type will then be transferred and made part of the source claim and the subscriber case databases.

Examples of specific database structure and programs that may be used to implement the invention are included in Appendix A attached hereto. Appendix A is a printout of an exemplary LOTUSNOTES synopsis used to implement a preferred embodiment of the invention.

While the invention has been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles of the invention as described hereinabove and set forth in the following claims.

APPENDIX A Insurance Claims File Synopsis

Lotus Notes Database Synopsis - Generated at 01 :28:52 PM on 04/11/97

Form Information:

Form: Access Control Form

Last Modification: 12/16/96 10:29:13 AM

Type: Document

Window Title Formula: SELECT "Document Access

Control"

Include in Compose Menu: Yes

Include in Query by Form: Yes

Default Database Form: No

Automatically Refresh Fields. No

Mail New Documents When Saving: No

Store Form In Documents: No

Inherit Default Field Values: No

Updates Become Responses: No

Retain Prior Versions As Responses: No

Activate Objects When Composing: No

Activate Objects When Editing: NO

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: Document_Author

Datatype: Author Names

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: (Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Documeπt.Readers

Datatype: Reader Names input Multi- Value Separators): Comma, Semicolon, New Line

Display Multi-Value Separator: New Line

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Document_Editors

Datatype: Author Names

Input Multi-Value Separators): Comma, Semicolon, New Line

Display Multi-Value Separator: New Line

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled Update Requires Editor Access: No

Formula. Field: Author

Datatype: Author Names

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Formula: mi Field: Document_Managers

Datatype: Author Names

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula:

Form: Automobile

Last Modification: 12/15/96 12:59:15 PM

Type: Document

Window Title Formula: SELECT "Automobile"

Include in Compose Menu: No

Include in Query by Form: Yes

Default Database Form: No

Automatically Refresh Fields: No

Mail New Documents When Saving: No

Store Form In Documents: No

Inherit Default Field Values: No

Updates Become Responses: No

Retain Prior Versions As Responses: No

Activate Objects When Composing: No

Activate Objects When Editing: No

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: lns_Policy

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Policy Field: lns_Policy From

Datatype. Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled Update Requires Editor Access: No

Default Value Formula: Policy_Period_From Field: lns_Policy_To

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Policy_Period_To Field: lns_Claim_Number

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Claim Field: LName

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: FName

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Address

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: City

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: State

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Zip

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption : Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Caption

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Caption Field: Jurisdiction

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Jurisdiction Field: Opposing Counsel

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Opposing_Counsel Field: Opp_Counsel_Address

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: lnsured_Address Field: Last_Action

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Last_Action Field: TimesModified

Datatype: Number

Number Format: General

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No Help Description: The number of times that the document has been modified

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @lf(@lsNewDoc; 0;

TimesModified != "";

TimesModified +

©IsDocBeingSaved; 0);

Field: PastAuthors

Datatype: Text

Input Multi-Value Separators): Semicolon Display Multi-Value Separator: Semicolon Help Description: This field will track the past authors

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf«g>lsDocBeingSaved;

@V2lf(TimesModified <= 0;

@ProperCase(@Name([CN];

@V3UserName)); PastAuthors :

@Name([CN];

@V3Usen\lame)); PastAuthors)

Field: PastEditDates

Datatype: Text

Input Multi- Value Separators): Semicolon Display Multi-Value Separator: Semicolon Help Description: This field will track the past edit dates

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ V2lf (@ IsDocBeiπgSaved ;

@V2lffTimesModifιed <= 0;

@Text(@Now); PastEditDates :

@Text(@Now)); PastEditDates)

Field: Author

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ProperCase(@Name([CN];

@V3UserName))

Field: Created

Datatype: Time

Time Format: 04/11/97 01 :28:53 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled Update Requires Editor Access: No Formula: ©Now Field: E1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := @Elements(PastAuthors)

- 0;y := x -

TimesModified ;@V2if(@lsNew Doc; " "; @V2lf(y >= 0; @Text(x - 1) ♦ "."; " "))

Field: A1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@ProperCase(@Subset(@Sub set(PastAuthors; -1); 1)))

Field: D1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 0;

@Subset(@Subset(PastEditDat es; -1); 1); - -))

Field: E2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := @Elements(PastAuthors)

- 1;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1)

))

Field: A2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Maiiing/ln Section: No

Encryption: Disabled Update Requires Editor Access: No Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 1 ;

@ProperCase(@Subset(@Sub set(PastAuthors; -2); 1)); " "))

Field: D2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 1 ;

@Subset(@Subset(PastEditDat es; -2); 1); " "))

Field: E3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := @Elements(PastAuthors)

- 2;@V2lf(@lsNewDoc; " ";

@V2lf(X - 1 >= 0; @Text(x - 1) tt n. « w

'))

Field: A3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNβwDoc; " "; @V2lf(TimesModified >= 2; @ProperCase«g>Subset(@Sub set(PastAuthors; -3); 1)); " "))

Field: D3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " "; @V2lf(TimesModifιed >= 2; @Subset(@Subset(PastEditDat es; -3); 1); " "))

Field: E4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := @Elements(PastAuthors)

- 3;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1)

Field: A4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf (TimesModified >= 3;

@ProperCase(@Subset(@Sub set(PastAuthors; -4); 1)); " "))

Field: D4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 3;

@Subset(@Subset(PastEditDal es; -4); 1); " "))

Field: E5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := @Elements(PastAuthors)

- 4;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1)

Field: A5 ^'

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access. No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 4;

@ProperCase(@Subset(@Sub set(PastAuthors; -5); 1)); " "))

Field: D5

Datatype: Text Help Description. [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf (TimesModified >= 4;

@Subset(@Subset(PastEditDat es; -5); 1); " "))

Field: Status

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: "0" Field: Date_Closed

Datatype: Time

Time Format: 04/11/97 01:28:53 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Closed_By

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: ID_Claim

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: ID_Case

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: ID_Budget

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Contact Name

30

SUBSTTTUTE SHEET (RULE 26) Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @lf(LName != "" & FName !=

""; LName + ", " + FName;

LName = ""; FName; LName)

Field: Document_Author

Datatype: Author Names

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DBName :=

@Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "\\");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "\V +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

@Name([Abbreviate];

@V3UserName);View2 :=

"Server_View";Key2 :=

©NameflO];

@V3UserName);Hit1 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

View1 ; Key1 ; 1)); "";

@DbLookup(ClassCache ;

Server : Database; Viewl ;

Key1; 1));Hit2 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

@DbLookup(ClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; HΛ2 != "";

"Server"; "NoAccess");View :=

©If (Direction = "Remote";

Viewl; View2);Key :=

@lf(Direction = "Remote";

Key1;

Key2);@DbLookup(ClassCache

; Server : Database; View; Key;

2);

Field: Document_Editors

Datatype: Author Names Input Multi- Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Document_Readers

Datatype: Reader Names

Input Multi- Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Document_Managers

Datatype: Reader Names

Input Multi-Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption. Disabled

Update Requires Editor Access: No

Formula: DBName :=

@Text(@DbName);Server := @Subset(DBName; 1);Path := @LeftBack(@Subset(@DbNam e; -1); "\\");Database := @lf(path = "";

"ITPLAYER.NSF"; path + "\\" + "ITPLAYER.NSF");ClassCache := "Notes" : "NoCache";View1 := "Remote_View";Key1 := @Name([Abbreviate] ; @V3UserName);Vιew2 := "Server_View";Key2 := @Name([0]; @V3UserName);Hit1 := (8>lf(@lsEσor(@DbLookup(Clas sCache; Server : Database; Viewl ; Key1 ; 1 )); ""; @DbLookup(ClassCache; Server : Database; Viewl ; Key1; 1));Hit2 := @lf(@lsError(@DbLookup(Clas sCache; Server : Database; View2; Key2; 1)); ""; @DbLookup(ClassCache ; Server : Database; View2; Key2; 1));Dιrection := @lf(Hit1 != ""; "Remote"; Hit2 != ""; "Server"; "NoAccess");View := @lf(Direction = "Remote"; Viewl; View2);Key := @lf(Direction = "Remote"; Key1 ;

Key2) ;@DbLookup(ClassCache ; Server : Database; View; Key;

5);

Field: lns_Company

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

@Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "\\");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "tt" +

"ITPLAYER. NSπ;ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

@Name([Abbreviate];

@V3UserName);View2 :=

"Server_, View";Key2 :=

@Name([0];

@V3UserName);Hit1 :=

@tf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl ; Key1; 1)); "";

@DbLookup(ClassCache;

Server : Database; Viewl ;

Key1; 1));HJt2 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

@DbLookup(C!assCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl ; View2);Key :=

@lf(Direction = "Remote";

Key1;

Key2) ;@DbLookup(ClassCache

; Server : Database; View; Key;

"Company_Name");

Field: Ins Contact

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled Update Requires Editor Access: No Formula: ©ProperCase(@Name([CN] ;

@V3UserName));

Field: lns_Contact_Phone

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

@Text(@DbName);Server :=

©Subset (DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "\\");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "\\" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

©NamefjAbbreviate];

@V3UserName);View2 :=

"Server, View";Key2 :=

@Name~([0];

@V3UserName);Hit1 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl; Key1 ; 1)); "";

@DbLookup(ClassCache;

Server : Database; Viewl ;

Key1 ; 1));Hit2 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

@DbLookup(ClassCache;

Server : Database; View2,

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");Viβw :=

©If (Direction = "Remote";

Viewl ; View2);Key :=

©lf(Direction = "Remote";

Key1 ;

Key2);©DbLookup(ClassCache

; Server : Database; View; Key;

"Phone");

Field: ScratchHist

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula:

Form: Environment Last Modification: 12/15/96 12:59:59 PM

Type: Document

Window Title Formula: SELECT "Environment"

Include in Compose Menu: No

Include in Query by Form: Yes

Default Database Form: No

Automatically Refresh Fields: No

Mail New Documents When Saving: No

Store Form In Documents: No

Inherit Default Field Values: No

Updates Become Responses: No

Retain Prior Versions As Responses: No

Activate Objects When Composing: No

Activate Objects When Editing: No

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: lns_Policy

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Policy Field: Ins Policy_From

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Policy_Period_From Field: lns_Policy_To

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Policy_Period_To Field: lns_Claim_Number

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Claim Field: LName

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

35

SUBSTITUTE SHEπ (RULE 26) Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: FName

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Address

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence Made Field: City

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: State

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Zip

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Caption

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Caption Field: Jurisdiction

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

36

SUBSmUTE SHEET (RULE 26) Update Requires Editor Access: No

Default Value Formula: Jurisdiction Field: Opposing_Counsel

Datatype: Text

Help Description. [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Opposing_Counsel Field: Opp_Counsel_Address

Datatype: Text^"

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: lnsured_Address Field: Last_Action

Datatype: Text^"

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Last_Action Field: TimesModified

Datatype: Number

Number Format: General

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description. The number of times that the document has been modified

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @lf(@lsNewDoc; 0;

TimesModified != "";

TimesModified +

©IsDocBeingSaved; 0);

Field: PastAuthors

Datatype: Text input Multi-Value Separators): Semicolon Display Multi-Value Separator: Semicolon Help Description: This field will track the past authors

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsDocBeingSaved;

@V2lf(TimesModified <= 0;

@ProperCase(@Name([CN];

@V3UserName)); PastAuthors

37

SUBSTTTUTE SHEET (RULE26) @Name([CN];

@V3UserName)); PastAuthors)

Field: PastEditDates

Datatype: Text

Input Multi- Value Separators): Semicolon Display Multi-Value Separator: Semicolon Help Description: This field will track the past edit dates

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©V2lf(@lsDocBeingSaved;

@V2lf(TimesModified <= 0;

©Text (©Now); PastEditDates :

@Text(@Now)); PastEditDates)

Field: Author

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ProperCase(©Name([CN];

@V3UserName))

Field: Created

Datatype: Time

Time Format: 04/11/97 01:28:53 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©Now Field: E1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula. DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := @Elemeπts(PastAuthors)

- 0;y := x -

TimesModified;©V2lf(@!sNew

Doc; " "; @V2lf(y >= 0;

@Text(x - 1) + "."; " "))

Field: A1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " "; @ProperCase(@Subset(@Sub set(PastAuthors; -1); 1)))

Field: D1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 0;

©Subset(©Subset(PastEditDat es; -1); 1); " "ϊ)

Field: E2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

O.DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 1 ;@V2lf(@lsNewDoc; " ";

@V2lf(X - 1 >= 0; @Text(x - 1)

Field: A2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 1 ;

©ProperCase(@Subset(@Sub set(PastAuthors; -2); 1)); " "))

Field: D2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 1 ; bset(PastEditDat

Field:

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors := 0;DEFAULT TimesModified := 0;X := ©Elements(PastAuthors) - 2;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1) m w

'))

Field: A3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 2;

©ProperCase(©Subset(©Sub set(PaslAuthors; -3); 1)); " "))

Field: D3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lffπmesModifιed >= 2;

@Subset(©Subset(PastEditDat es; -3); 1); " "))

Field: E4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 3;@V2lf(@lsNewDoc; " ";

@V2lf(X - 1 >= 0; ©Text(x - 1)

Field: A4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula. @V2lf(©lsNewDoc; " ";

©V2lf(TimesModifιed >= 3;

©ProperCase(@Subset(@Sub seUPastAuthors; -4); 1)); " "))

Field: D4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

40

SUBSTrrUTE SHEET (RULE 26) Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TιmesModified >= 3;

@Subset(@Subset(PastEditDat es; -4); 1); " "))

Field: E5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

Field: A5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 4;

©ProperCase(©Subset(©Sub set(PastAuthors; -5); 1)); " "))

Field: D5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 4;

©Subset(©Subset(PastEditDat es; -5); 1); " "))

Field: Status

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: "0" Field: Date_Closed

Datatype: Time

Time Format: 04/11/9701:28:53 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled Update Requires Editor Access: No

Formula: Field: Closed_By

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: ID_Claim

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: ID_Case

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: ID_Budget

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Contact_Name

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @lf(LName != "" & FName »=

""; LName + ", " + FName;

LName = ""; FName; LName)

Field: Documeπt_Author

Datatype: Author Names

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description. [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DBName :=

@Text(@DbName);Server :=

©Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "\\");Database :=

@lf(ρath = -;

42

SUBSTTπTfESHEET(RULE26) "ITPLAYER.NSF"; path + "\\" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

©NameflAbbreviate] ;

@V3UserName);View2 :=

"Server_View";Key2 :=

@Name([0];

@V3UserName);Hit1 :=

© If (@ lsError(@DbLookup(Clas sCache; Server : Database;

Viewl; Key1; 1 )); "";

@DbLookup(ClassCache ;

Server : Database; Viewl ;

Key1 ; 1));Hit2 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

@DbLookup(ClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hlt1

!= ""; "Remote"; Hit2 != "";

"Server; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl ; View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2) ;@DbLookup(ClassCache

; Server : Database; View; Key;

2);

Field: Document_Editors

Datatype: Author Names

Input Multi-Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Documeπt_Readers

Datatype: Reader Names

Input Multi- Value Separator(s): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description : [Not Assigned]

Field Type: Computed when composed

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Document_Managers

Datatype: Reader Names input Multi-Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

43

SUBSTΠUTE SHEET (RULE26) Sign When Mailing/In Section: No

Encryption. Disabled

Update Requires Editor Access: No

Formula: DBName :=

@Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "\\");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "\\" +

"ITPLAYER. NSF") ;ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

©NamefJAbbreviate];

@V3UserName);View2 :-

"Server_View";Key2 :=

@Name([0];

@V3UserName);Hit1 :=

@lf(©lsError(@DbLookup(Clas sCache; Server : Database;

Viewl ; Key1 ; 1)); "";

@DbLookup(ClassCache;

Server : Database; Viewl ;

Key1; 1));Hit2 :=

© If (@ lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

©DbLookup(CiassCache;

Server : Database; Vιew2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

©If (Direction = "Remote";

Viewl; View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2);@DbLookup(ClassCache

; Server : Database; View; Key;

5);

Field: lns_Company

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

@Text(@DbName); Server :=

@Subset(DBName; 1);Path :=

@LeftBack(©Subset(@DbNam e; -1); "tt"); Database :=

@lf(path = -;

"ITPLAYER.NSF"; path + "V +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

44

SUBSTTTUTE SHEET (RULE 26) @Name([Abbreviate] ;

@V3UserName);View2 :=

"Server_View";Key2 :=

@Name([0];

@V3UserName);Hit1 :=

@lf(@lsError(©DbLookup(Clas sCache; Server : Database;

Viewl; Key1; 1)); "";

©DbLookup(ClassCache;

Server : Database; Viewl ;

Key1; 1));Hit2 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

©DbLookupjClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@ff(Direction = "Remote";

Viewl ; View2);Key :=

@lf(Direction = "Remote";

Key1;

Key2) ;@DbLookup(ClassCache

; Server : Database; View; Key;

"Company_Name");

Field: lns_Contact

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ProperCase(@Name([CNJ;

@V3UserName));

Field: lns_Contact_Phone

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

@Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "tt");Database :=

@lf(path = "";

"ITPLAYER.NSP; path + "tt" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

@Name([Abbreviate];

@V3UserName);View2 :=

"Server_View";Key2 :=

@Name([0];

45

SUBSTITUTE SHEET (RUU 26) @V3UserName);Hit1 :=

©lf(@lsEπror(@DbLookup(Clas sCache; Server : Database;

Viewl ; Key1 ; 1 )); "";

@DbLookup(ClassCache;

Server : Database; Viewl ;

Key1 ; 1));Hit2 :=

@lf(©isError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

@DbLookup(ClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != ~;

"Server"; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl ; View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2);@DbLookup(ClassCache

; Server : Database; View; Key;

"Phone");

Field: ScratchHist

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula:

Form: Excess

Last Modification: 12/15/96 01 :01 :11 PM

Type: Document

Window Title Formula: SELECT "Excess" include in Compose Menu: No

Include in Query by Form: Yes

Default Database Form: No

Automatically Refresh Fields: No

Mail New Documents When Saving: No

Store Form In Documents: No

Inherit Default Field Values: No

Updates Become Responses: No

Retain Prior Versions As Responses: No

Activate Objects When Composing: No

Activate Objects When Editing: No

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: lns_Policy

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/in Section: No

Encryption: Disabled

46

SUBSmUTE SHEET (RULE 26) Update Requires Editor Access: No

Default Value Formula: Policy Field: lπs_Policy_From

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula. Policy_Period_From Field: lns_Policy_To

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula. Poiicy_Period_To Field: lπs_Claim_Number

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Claim Field: LName

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: FName

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occureπce.Made Field: Address

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence Made Field: City

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

47

SKBSTTTUTE SHEET (RULE 26) Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: State

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Zip

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Caption

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula. Caption Field: Jurisdiction

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Jurisdiction Field: Opposing_Counsel

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Opposing_Counsel Field: Opp_Counsel Address

Datatype: Text

Help Description: (Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: lnsured_Address Field: Last_Action

Datatype. Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled Update Requires Editor Access: No Formula: Last_Action Field: TimesModified

Datatype: Number Number Format: General Percentage (value ^* 100)%: No Parentheses on Negative Numbers: No Punctuated at Thousands: No Help Description: The number of times that the document has been modified

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @lf(@lsNewDoc; 0;

TimesModified != "";

TimesModified +

©IsDocBeingSaved; 0);

Field: PastAuthors

Datatype: Text

Input Multi-Value Separators): Semicolon Display Multi- Value Separator. Semicolon Help Description: This field will track the past authors

Field Type: Computed

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©V2lf(@lsDocBeingSaved;

@V2lfO^"imesModifιed <= 0;

@ProperCase(©Name([CNj;

@V3UserName)), PastAuthors :

@Name([CN];

@V3UserName)); PastAuthors)

Field: PastEditDates

Datatype. Text

Input Multi-Value Separator(s): Semicolon Display Multi-Value Separator: Semicolon Help Description: This field will track the past edit dates

Field Type: Computed

Sign When Mailing/fn Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf (©IsDocBeingSaved;

@V2lf(TimesModified <= 0;

@Text(@Now); PastEditDates :

@Text(@Now)); PastEditDates)

Field: Author

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ProperCase(@Name([CN]; @V3UserName))

Field: Created

Datatype: Time

Time Format: 04/11/97 01 :28:53 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©Now Field: E1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 0;y :^« x -

TimesModifιed;@V2lf(@lsNew

Doc; " "; @V2lf(y >= 0;

@Text(x - 1) + "."; " "))

Field: A1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

©ProperCase(©Subset(@Sub set(PastAuthors; -1); 1)))

Field: D1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 0;

@Subset(@Subset(PastEditDat es; -1); 1 ); " "))

Field: E2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0; DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 1 ;@V2lf(@lsNewDoc; " ";

50

SUBSTΠUTE SHEET (RULE 26) @V2lf(X - 1 >= 0; @Text(x - 1)

Field: A2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 1 ;

@ProperCase(@Subset(@Sub set(PastAuthors; -2); 1)); " "))

Field: D2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 1 ;

@Subset(@Subset(PastEditDat es; -2); 1); " "))

Field: E3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X :« @Elemeπts(PastAuthors)

- 2;@V2lf(@lsNewDoc; " ";

@V2lf(X - 1 >= 0; @Text(x - 1)

Field: A3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/tn Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@JsNewDoc; " ";

@V2lf(TimesModified >= 2;

@PrσperCase(@Subset(@Sub set(PastAuthors; -3); 1)); " "))

Field: D3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

51

SUBSTfTUTE SHEET (RULE26) @V2lf (TimesModified >= 2;

©Subset(©Subset(PastEditDat es; -3); 1); " "))

Field: E4

Datatype. Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 3;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1)

Field: A4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

©V2lf(TimesModifιed >= 3;

@ProperCase(©Subset(©Sub set(PastAuthors; -4); 1)); " "))

Field: D4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©V2lf(@lsNewDoc; " ";

@V2lf (TimesModified >= 3;

©Subset(©Subset(PastEditDat es; -4); 1); " "))

Field: E5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := ©Elemeπts(PastAuthors)

- 4;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1)

Field: A5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

52

SUBSTTTUTE SHEET (RULE 26) Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2tf(@lsNewDoc; " ";

@V2lf(TimesModified >= 4;

©ProperCase(©Subset(@Sub set(PastAuthors; -5); 1)); " "))

Field: D5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 4;

©Subset(©Subset(PastEditDat es; -5); 1); " "))

Field: Status

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: "0" Field: Date_Closed

Datatype: Time

Time Format: 04/11/97 01:28:53 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Closed By

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: ID_Claim

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: ID_Case

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access. No

53

SUBSTTTuTE SHEET (RULE 26) Field: ID_Budget

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Contact_Name

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @lf(LName != "" & FName !=

""; LName + ", " + FName;

LName = ""; FName; LName)

Field: Document_Author

Datatype. Author Names

Input Multi-Value Separator(s): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DBName :=

©Text(@DbName);Server :=

©Subset(DBName; 1);Path :-

@LeftBack(@Subset(©DbNam e; -1); "tt");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "tt" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

©Name([Abbreviate] ;

@V3UserName);View2 :=

"Server_View";Key2 :=

@Name([OJ;

©V3UserName);Hit1 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl; Key1 ; 1 )); "";

©DbLookup(ClassCache;

Server : Database; Viewl ;

Key1; 1));Hit2 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

©DbLookup(ClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@lf(Direction = "Remote"; Viewl ; View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2);@DbLookup(ClassCache

; Server : Database; View; Key;

2);

Field: Document_Editors

Datatype: Author Names

Input Multi-Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Document_Readers

Datatype- Reader Names Input Multi- Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption. Disabled

Update Requires Editor Access: No

Formula: Field: Document_Managers

Datatype: Reader Names

Input Multi-Value Separators): Comma, Semicolon

Display Multi-Value Separator Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DBName :=

@Text(@DbName),Server :=

©Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "\\");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "tt" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache"; Viewl :=

"Remote_View";Key1 :=

©Name([Abbreviate];

@V3UserName);View2 :=

"Server_View";Key2 :=

©NameflO];

@V3UserName);Hit1 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl; Key1; 1)); "";

@DbLookup(ClassCache ;

Server : Database; Viewl ;

Key1 ; 1));Hit2 :=

55

SUBSTTTUTE SHEET (RULE 26) @lf(@lsError(@DbLookup(Clas sCache; Server : Database; View2; Key2; 1)); ""; @DbLookup(ClassCache; Server : Database; Vιew2; Key2; 1));Direction := @lf(Hrt1 != ""; "Remote"; Hit2 != ""; "Server"; "NoAccess");View := @lf(Direction = "Remote"; Viewl ; View2);Key := @lf(Direction = "Remote"; Key1;

Key2);@DbLookup(ClassCache ; Server : Database; View; Key;

5);

Field: lns_Company

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

@Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

@LeftBack(©Subset(©DbNam e; -1); "tt"); Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "tt" +

"ITPLAYER.NSFOjClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

©Name([Abbreviate];

@V3UserName);View2 :=

"Server_View";Key2 :=

©Name([0],

@V3UserName);Hit1 :=

©lf(@lsError(©DbLookup(Cias sCache; Server : Database;

Viewl; Key1 ; 1)); "";

@DbLookup(ClassCache;

Server : Database; Viewl;

Key1 ; 1));Hit2 :=

@tf(@lsEπOr(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

©DbLookuptClassCache;

Server : Database; View2;

Key2; 1));Directioπ := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl; View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2);@DbLookup(ClassCache ; Server : Database; View; Key,

"Company_Name"),

Field: lns_Contact

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ProperCase(@Name([CN];

@V3UserName));

Field: lns_Contact_Phone

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

@Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "\\"); Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "W" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

©NamefJAbbreviate];

@V3UserName);View2 :=

"Server_View";Key2 :=

©Name([0];

@V3UserName);Hit1 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl; Key1; 1)); "";

@DbLookup(ClassCache ;

Server : Database; Viewl ;

Key1; 1));Hit2 :=

@lf(©lsError(@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

@DbLookup(ClassCache ;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl; View2);Key :=

©lf(Direction = "Remote";

Key1;

Key2);@DbLookuρ(ClassCache

; Server : Database; View; Key;

"Phone");

Field: ScratchHist

Datatype. Text Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption. Disabled

Update Requires Editor Access: No

Formula:

Form: General Liability - Damages Shared

Last Modification: 11/02/96 02:58:18 PM

Type: Document

Include in Compose Menu: No

Include in Query by Form: Yes

Default Database Form: No

Automatically Refresh Fields: No

Mail New Documents When Saving: No

Store Foπn In Documents: No

Inherit Default Field Values: No

Updates Become Responses: No

Retain Prior Versions As Responses: No

Activate Objects When Composing: No

Activate Objects When Editing: No

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: Property Description

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Prαperty_Estimate

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Property Seen_Location

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Property_Seen

Datatype: Keywords Input Multi- Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Property Seen?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Property_Seen_Date

Datatype: Time

Time Format: 04/11/97

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: WHness_Name

Datatype: Text

Help Description. [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access. No

Default Value Formula. Field: Witness Address

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption. Disabled

Update Requires Editor Access: No

Default Value Formula: nit Field: Witness_Phone

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Reported To

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Date_Reported

Datatype: Time^"

Time Format: 04/11/97

Help Description: [Not Assigned]

Field Type: Editable Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Reiπsurer_Notified

Datatype: Keywords

Input Multi- Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Excess/Reinsurer Notified?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Reinsurer_Notifed_Date

Datatype: Time

Time Format: 04/11/97

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula:

Form: General Liability - Details Shared

Last Modification: 11/03/96 01 :40:59 PM

Type: Document

Include in Compose Menu: No include in Query by Form: Yes

Default Database Form: No

Automatically Refresh Fields: No

Mail New Documents When Saving: No

Store Form In Documents: No

Inherit Default Field Values: No

Updates Become Responses: No

Retain Prior Versions As Responses: No

Activate Objects When Composing: No

Activate Objects When Editing: No

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: Claimant

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Loss_Date

Datatype: Time

Time Format: 04/11/97 Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Loss_Location

Datatype: Text^"

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Alleged_Damages

Datatype: Keywords

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Radio Buttons

Allowable Keywords: Bodily Injury

Property Damage

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access. No

Default Value Formula: Field: Fatality

Datatype: Keywords

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Computed when composed

Keyword User Interface: Check Boxes

Allowable Keywords: Fatality?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Date_Of_Death

Datatype: Time

Time Format: 04/11/97

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Claims_Facts

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Claim_ln_Suit

Datatype: Keywords Input Multi- Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Claim In Suit?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Date_Suit_Filed

Datatype: Time

Time Format: 04/11/97

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Date_Suit_Served

Datatype: Time

Time Format: 04/11/97

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Liability_Claimant_Pct

Datatype: Number

Number Format: General

Percentage (value * 100)%: Yes

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: LiabilityJ nsured_Pct

Datatype: Number

Number Format: General

Percentage (value * 100)%: Yes

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Curr_Reserve Loss

Datatype: Text^"

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

62

SUBSTTTUTE SHEET (RULE 26) Update Requires Editor Access: No Field: C urr_Reserve_Exp

Datatype: Text

Help Description : [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Form: General Liability - Incident - Shared

Last Modification: 11/03/96 01:40:13 PM

Type: Document

Include in Compose Menu: No

Include in Query by Form: Yes

Default Database Form: No

Automatically Refresh Fields: No

Mail New Documents When Saving: No

Store Form In Documents: No

Inherit Default Field Values: No

Updates Become Responses: No

Retain Prior Versions As Responses: No

Activate Objects When Composing: No

Activate Objects When Editing: No

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: lnjury_Type

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: 0_Cause

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Defense_MD

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Defense Expert

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Plaintiff_MD

Datatype: Number

Number Format: General

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access. No

Default Value Formula: Field: Plaintiff Expert

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Discjnt

Datatype: Keywords

Input Multi- Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: lnterrogatories?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Disc_Req

Datatype: Keywords

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User interface: Check Boxes

Allowable Keywords: Request for Prod, of Doc.|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Depositions

Datatype: Keywords

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Depositions Taken?|Y Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Case_Date

Datatype: Time

Time Format: 04/11/97

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Plaintiff_Demand

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Defense_Offer

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption. Disabled

Update Requires Editor Access: No Field: Settlement_Value

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Verdict From

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Verdict To

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Mediation

Datatype: Keywords

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Mediation/Arbitration Attempted?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: Defense_Pd

Datatype: Number

Number Format: General

Percentage (value * 100)%: Yes

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Plaintiff_Pct

Datatype: Number

Number Format: General

Percentage (value * 100)%: Yes

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Medical_Bills

Datatype: Keywords

Input Multi- Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Medical Bills?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: LosMrVages

Datatype: Keywords

Input Multi- Value Separators): Comma

Display Multi-Value Separator Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Lost Wages?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Out Of Work From

Datatype: Texf

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

66

SUBSTTfUTE SHEET (RULE 26) Default Value Formula: Field: Out_Of_Work_To

Datatype: TexT

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: WC_Eligible

Datatype: Keywords

Input Multi- Value Separators): Comma

Display Multi-Value Separator Comma

Help Description. [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Eligible for WC?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Field: WC.Paid

Datatype. Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No Field: WC Medical

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: WC Indemnity

Datatype. Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Form: General Liability - Policy Shared

Last Modification: 11/01/96 04:36:25 PM Type: Document include in Compose Menu: No Include in Query by Form: Yes Default Database Form: No Automatically Refresh Fields: No Mail New Documents When Saving: No Store Form In Documents: No Inherit Default Field Values: No Updates Become Responses: No Retain Prior Versions As Responses: No

67

_ιBδSrfHJTESHEET(RULE26) Activate Objects When Composing: No

Activate Objects When Editing: No

Activate Objects When Reading: No

Document Encryption Keys: [None Assigned]

Composed Documents May Be Read By: All Users

Form May Be Composed By: All Users

Field: Claims_Made

Datatype: Keywords

Input Multi- Value Separators): Comma

Display Multi-Value Separator. Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Claims Made?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Claims_Made Field: Retro

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access. No

Default Value Formula: Retro_Date Field: PL Ext Period

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Ext_Period Field: PL_Agg_Limit

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Aggegrate_Limit Field: PL_ProdJJmit

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption. Disabled Update Requires Editor Access. No

Default Value Formula: PL_Prod_Limit Field: PL_Personal_Limit

Datatype. Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Personal_Limit Field: PL_Each_Limit

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands. No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Each_Limit Field: PL_Fire_Limit

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula. PL_Fire_Limit Field: PL_MedTcal_Limit

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL Medical Limit Field: DE^"b_Per

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value ^* 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DED_Per Field: DED_Aggregate

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section. No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DED_Aggregate Field: DED_Retained

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DED_Retained Field: Occurence_Made

Datatype: Keywords input Multi- Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Occurence Made?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Endorsements

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula. Endorsements

Form: General Liability Completed Operations

Foπn Alias: GL Complete Last Modification: 12/15/96 01:02:41 PM Type: Document Window Title Formula: SELECT "General Liability

Claim - Completed Operations"

Include in Compose Menu: No Include in Query by Form: Yes Default Database Form: No Automatically Refresh Fields: No Mail New Documents When Saving: No Store Form In Documents. No Inherit Default Field Values: No Updates Become Responses: No Retain Prior Versions As Responses: No Activate Objects When Composing: No Activate Objects When Editing: No Activate Objects When Reading: No Document Encryption Keys: [None Assigned] Composed Documents May Be Read By: All Users Foπn May Be Composed By: All Users Field: Ins Policy

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Policy Field: lns_PolicyJ=rom

Datatype. Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Policy_Period_From Field: lns_Policy To

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Poiicy_Pβriod_To Field: lns_Claim Number

Datatype: Text

Help Description. [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Claim Field: LName

Datatype: Text

Help Description. [Not Assigned]

Field Type: Editable

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

71

SUBSFfFUTE SHEET (RULE 26) Default Value Formula: Occurence_Made Field: FName

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Address

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: City

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: State

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Zip

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Occurence_Made Field: Caption

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Caption Field: Jurisdiction

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

72

ilrøfTBΪE SHEET (RULE26) Default Value Formula: Jurisdiction Field: Opposing_Counsel

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Opposing_Counsel Field: Opp_Counsel_Address

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: lnsured_Address Field: Last_Action

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption. Disabled

Update Requires Editor Access: No

Formula: Last_Action Field: TimesModified

Datatype: Number

Number Format: General

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: The number of times that the document has been modified

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @lf(@lsNewDoc; 0;

TimesModified l^« "";

TimesModified +

©IsDocBeingSaved; 0);

Field: PastAuthors

Datatype: Text

Input Multi-Value Separators): Semicolon Display Multi-Value Separator. Semicolon Help Description: This field will track the past authors

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©V2lf(@lsDocBeingSaved;

@V2lf(TimesModified <= 0;

@ProperCase(©Name([CN];

@V3UserName)); PastAuthors

@Name([CNJ;

73

UlSTfrUTI SHEET (RULE 26) @V3UserName)); PastAuthors)

Field: PastEditDates

Datatype: Text

Input Multi-Value Separators): Semicolon Display Multi-Value Separator Semicolon Help Description: This field will track the past edit dates

Field Type: Computed

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf (©IsDocBeingSaved;

@V2lf(TimesModifιed <= 0;

@Text(@Now); PastEditDates :

@Text(@Now)); PastEditDates)

Field: Author

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ProperCase(@Name([CN];

@V3UserName))

Field: Created

Datatype: Time

Time Format: 04/11/97 01:28:54 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©Now Field: E1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 0;y :«= x -

TimesModifιed;@V2lf(©lsNew

Doc; " "; @V2lf(y >= 0;

@Text(x - 1) + "."; " "))

Field: A1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

©ProperCase(@Subset(©Sub

74

liiSTϋyTE SHEET (RULE 26) set(PastAuthors; -1); 1)))

Field: D1

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(©lsNewDoc; " ";

@V2lf(TimesModifιed >= 0;

©Subset(©Subset(PastEditDat es; -1); 1 ); " "))

Field: E2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 1;@V2lf(@lsNewDoc; " ";

@V2lf(X - 1 >= 0; ©Text(x - 1)

Field: A2 ^'

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section. No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(©lsNewDoc; " ";

@V2lf(TimesModified >= 1;

©ProperCase(©Subset(©Sub set(PastAuthors; -2); 1)); " "))

Field: D2

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

©V2lf(TimesModified >= 1;

@Subset(©Subset(PastEditDat es; -2); 1); " "))

Field: E3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access. No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

75

SUOTra! SHEET (RULE 26) 0;X := ©Elements(PastAuthors)

- 2;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1)

Field: A3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 2;

@ProperCase(@Subset(@Sub set(PastAuthors; -3); 1)); " "))

Field: D3

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(©lsNewDoc; " ";

@V2lf(TimesModifιed >= 2;

©Subset(@Subset(PastEditDat es; -3); 1 ); " "))

Field: E4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X := ©Elements(PastAuthors)

- 3;@V2lf(@lsNewDoc; " "; @V2lf(X - 1 >= 0; @Text(x - 1)

Field: A4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption. Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 3;

©ProperCase(@Subset(@Sub set(PastAuthors; -4); 1)); " "))

Field: D4

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

76

{KFfOTI SHEET (RULE 26) Update Requires Editor Access: No Formula: @V2tf(@lsNewDoc; " ";

@V2lf(TimesModifιed >= 3;

©Subset(©Subset(PastEditDat es; -4); 1); " "))

Field: E5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DEFAULT PastAuthors :=

0;DEFAULT TimesModified :=

0;X :^» ©Elements(PastAuthors)

- 4;@V2lf(@lsNewDoc; " ";

@V2lf(X - 1 >= 0; @Text(x - 1)

Field: A5 '

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 4;

@ProperCase(©Subset(©Sub set(PastAuthors; -5); 1)); " "))

Field: D5

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed for display

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @V2lf(@lsNewDoc; " ";

@V2lf(TimesModified >= 4;

©Subset(©Subset(PastEditDat es; -5); 1); " "))

Field: Status

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: "0" Field: Date_Closed

Datatype. Time

Time Format: 04/11/97 01:28:54 PM

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption. Disabled

Update Requires Editor Access: No

77

IBSTETUTE SHEET (RULE 26) Formula: Field: Closed_By

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: ID_Claim

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: ID_Case

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: ID_Budget

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No Field: Contact_Name

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: ©lf(LName != "" & FName !=

""; LName + ". " + FName;

LName = ""; FName; LName)

Field: Document_Author

Datatype: Author Names

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: DBName :=

©Text(©DbName);Server :=

©Subset(DBName; 1);Path :=

@LeftBack(@Subset(@DbNam e; -1); "tt");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "tt" +

78

IKπiBTE SHEET (RULE 26) "ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Keyt :=

©Name([Abbreviate];

@V3UserName);View2 :=

"Server_View";Key2 :=

©Name([0],

@V3UserName);Hit1 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl; Key1; 1 )); "";

@DbLookup(ClassCache;

Server : Database; Viewl ;

Key1; 1));Hit2 :=

@lf(@isEπor(©DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

@DbLookup(CiassCache;

Server : Database, View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@tf(Direction = "Remote";

Viewl ; View2);Key :=

@lf(Direction = "Remote";

Keyl;

Key2);@DbLookup(ClassCache

; Server : Database; View; Key;

2);

Field: Document_Editors

Datatype: Author Names

Input Multi-Value Separators): Comma, Semicolon

Display Multi-Value Separator Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Maiiing/ln Section. No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Document_Readers

Datatype: Reader Names

Input Multi- Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/in Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: Field: Document_Managers

Datatype: Reader Names

Input Multi-Value Separators): Comma, Semicolon

Display Multi-Value Separator: Semicolon

Help Description: [Not Assigned]

Field Type: Computed when composed

Sign When Mailing/In Section: No

79

Al

* UBSTTTUTE SHEET (RULE 26) Encryption: Disabled

Update Requires Editor Access. No

Formula: DBName :=

©Text(©DbName);Server :=

@Subset(DBName; 1);Path :=

©LeftBack(©Subset(©DbNam e; -1); "tt");Database :=

©lf(path = "";

"ITPLAYER.NSF"; path + "W" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

©Name([Abbreviate] ;

@V3UserName);View2 :=

"Server_View";Key2 :=

@Name~([0],

@V3UserName);Hit1 :=

©lf(©lsEπor(©DbLookup(Clas sCache; Server : Database;

Viewl; Key1; 1)); "";

©DbLookup(ClassCache;

Server : Database; Viewl ;

Key1 ; 1));Hit2 :=

@lf(©lsError(©DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

©DbLookup(ClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl , View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2);©DbLookup(ClassCache

; Server : Database; View; Key;

5);

Field: lns_Company

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

©Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

©LeftBack(©Subset(©DbNam e; -1); "tt");Database :=

@lf(path = "";

"ITPLAYER.NSF"; path + "tt" +

"ITPLAYER.NSP);ClassCache

:= "Notes" : "NoCache";View1 :=

"Remote_View";Key1 :=

@Name([Abbreviate] ; @V3UserName);View2 :=

"Server_View";Key2 :=

©NameflOJ;

@V3UserName);Hit1 :=

@lf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl ; Key1; 1 )); "";

©DbLookup(CtassCache;

Server : Database; Viewl ;

Key1; 1));Hit2 :=

@lf(©lsError(©DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

©DbLookup(ClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hit1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl ; View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2);@DbLookup(ClassCache

; Server : Database; View; Key;

"Company_Name") ;

Field: lns_Contact

Datatype: Text

Help Description: [Not Assigned]

Field Type: Computed

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Formula: @ProperCase(@Name([CN];

@V3UserName));

Field: lns_Contact_Phone

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DBName :=

©Text(@DbName);Server :=

@Subset(DBName; 1);Path :=

©LeftBack(©Subset(©DbNam e; -1); "tt");Database :=

@lf(path = "^■;

"ITPLAYER.NSF"; path + "tt" +

"ITPLAYER.NSF");ClassCache

:= "Notes" : "NoCache";V1ew1 :=

"Remote_View";Key1 :«

©NamefjAbbreviate];

@V3UserName);View2 :=

"Server_View";Key2 :=

©NamerJO];

@V3UserName);Hit1 := @lf(@lsError(@DbLookup(Clas sCache; Server : Database;

Viewl; Key1 ; 1)); "";

©DbLookup(CiassCache ;

Server : Database; Viewl ;

Key1 ; 1));Hit2 :=

@lf(@tsError@DbLookup(Clas sCache; Server : Database;

View2; Key2; 1)); "";

©DbLookup(ClassCache;

Server : Database; View2;

Key2; 1));Direction := @lf(Hlt1

!= ""; "Remote"; Hit2 != "";

"Server"; "NoAccess");View :=

@lf(Direction = "Remote";

Viewl; View2);Key :=

@lf(Direction = "Remote";

Key1 ;

Key2);@DbLookup(ClassCache

; Server : Database; View; Key;

"Phone");

Field: Claims_Made

Datatype: Keywords

Input Multi- Value Separator(s): Comma

Display Multi-Value Separator Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Claims Made?|Y

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Ctaims.Made Field: Retro

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: Retro_Date Field: PL_Ext_Period

Datatype: Text

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Ext_Period Field: PL_Agg_Limit

Datatype: Number

Number Format: Cuπency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers. No

Punctuated at Thousands: No

Help Description: [Not Assigned] Field Type: Editable

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Aggegrate_Limit Field: PL_Prod_Limit

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Prod_Limit Field: PL_Persona!_Limit

Datatype. Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands. No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Personal_Limit Field: PL_Each_Limit

Datatype: Number

Number Format: Cuπency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Each_Limit Field: PL_Fire_Limit

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Fire_Limit Field: PL_Medical_Limit

Datatype: Number

Number Format: Cuπency (2 Decimal Places) Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: PL_Medical Limit Field: DED_Per

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DED_Per Field: DED_Aggregate

Datatype: Number

Number Format: Cuπency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula. DED_Aggregate Field: DED_Retained

Datatype: Number

Number Format: Currency (2 Decimal Places)

Percentage (value * 100)%: No

Parentheses on Negative Numbers: No

Punctuated at Thousands: No

Help Description: [Not Assigned]

Field Type: Editable

Sign When Mailing/In Section: No

Encryption: Disabled

Update Requires Editor Access: No

Default Value Formula: DED_Retained Field: Occurence_Made

Datatype: Keywords

Input Multi-Value Separators): Comma

Display Multi-Value Separator: Comma

Help Description: [Not Assigned]

Field Type: Editable

Keyword User Interface: Check Boxes

Allowable Keywords: Occurence Made?|Y

Sign When Maiiing/ln Section: No

Encryption: Disabled

Update Requires Editor Access: No

86

99

103

117

123

136

149

166

172

174

176

182

189

194

97/41524 PO7US97/07207

198

204

220

222

238

247

261

273

Claims

in the subscriber new claims database; transmitting proposal data indicative of the litigation proposal to the source; storing the proposal data in the source new claims database; and transmitting a proposal response to the selected subscriber indicating whether the litigation proposal is acceptable.

5. The method of claim 4, wherein the proposal response is representative of any one of a proposal acceptance, a proposal denial, and a request for more information.

6. The method of claim 4, further comprising the step of: electronically transmitting additional claim-related information from the source to the selected subscriber if the litigation proposal is acceptable; and storing the additional claim-related information in the subscriber case database associated with the selected subscriber along with the new claim information.

7. A method of managing litigation using an automated litigation management system networking a source of the litigation to a plurality of subscribers through a central hub, comprising the steps of: generating a request for approval to perform a litigation activity; transmitting the request for approval from a subscriber processing means associated with one of the plurality of subscribers to a source processing means associated with the source; transmitting an activity response indicative of a decision to approve or deny the activity request; and updating a subscriber authorization database accessible by a subscriber processing means associated with the one subscriber.

8. The method of claim 7, further comprising the steps of: generating a request for payment associated with the activity when the activity is completed; enabling a transmission of the request for payment if the activity request is approved; and disabling the transmission of the request for payment if the activity request is denied.

9. A litigation management system interconnecting at least one source of information and a plurality of subscribers, each of the plurality of subscribers having an associated office litigation administration system for facilitating the administration of litigation by the subscriber, the system comprising: a source system for providing source information relating to new and on- going litigations and for receiving subscriber information relating to the same litigations; a plurality of subscriber interfaces configured to receive source information and store the source information in the associated office litigation administration systems and to retrieve subscriber information from the associated office litigation administration systems and transmit the subscriber information so retrieved to the source system; and a central processing means interfaced to receive source information from the source system and subscriber information from the plurality of subscriber interfaces for establishing authorized links between the source and the plurality of subscribers based on predetermined criteria.

10. The system of claim 9, further comprising: a subscriber database interfaced with the central processing means for storing data relating to each of the plurality of subscribers; and wherein the central processing means comprises a selection means for selecting one of the plurality of subscribers based on at least some of the source information and the data stored in the subscriber database.

11. The system of claim 10, wherein the predetermined criteria includes the location of the subscriber. 12. The system of claim 9, wherein the source system comprises: a new claims database for storing new case information relating to new litigations, the source system transmitting at least some of the new claim information as source information to the central processing means thereby initiating a procedure to establish one authorized link.

13. The system of claim 9, wherein the plurality of subscribers require authorization to carry out predefined activities, the source system comprising: a database means for storing subscriber information relating to the authorization of the predefined activities carried out by each subscriber connected to the source through one of the authorized links established by the central processing means.

14. The system of claim 9, wherein each of the plurality of subscriber interfaces comprises: a new cases database for storing source information received from the central processing means to establish one authorized link between the subscriber associated with the same subscriber interface, the source information so stored relating to new litigation and defining new case information, the same subscriber interface transferring the new case information from the new cases database to the associated office litigation administration system after the central processing means establishes the one authorized link.

15. The system of claim 9, wherein the plurality of subscribers require authorization to carry out predefined activities and each of the plurality of subscriber interfaces comprises: a database means for storing source information relating to the authorization of the predefined activities received from the source system; and a billing verification means for generating a request for payment after the completion of each predefined activity and for transmitting the request for payment based on information stored in the authorizations database.