JP2006039718A - Event information management system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To efficiently manage varied kinds of information about an event. <P>SOLUTION: In receipt of basic information about the event, the event management server 1 generates a unique event information ID to give and register it in an event database. In receipt of respective document data created in relation to the event from a user terminal 3, the event management server 1 registers the respective document data in the event database in association with the event information ID of the event. In response to input showing completion of the event from the user terminal 3, the event management server 1 reads the document data associated with the event information ID of the event from the event database and transmits the document data to a document management server 2 based on the event type included in the basic information about the event for classifying the document data by event type and storing them in the document database. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an incident information management system and the like for managing various information related to incidents for each incident.

  Conventionally, various types of information related to incidents at law firms and the like have been generally distributed and managed in various forms. For example, in the case of document data, the lawyer in charge of the case stores the data in paper or stores the document data in a medium such as an FD. In addition, cash management related to incidents, billing, deposits, etc. was managed by accounting staff etc. in a handwritten ledger.

For example, there is a project management system for managing documents created in a project.
JP 2003-108735 A (page 5, FIG. 2)

As described above, in the method of managing information related to incidents in a distributed manner, for example, when various types of information related to the same incident are required, information relating to the same incident must be extracted from a document, FD, ledger, etc. It was efficient.
In addition, there is a need for a mechanism that can avoid duplication of the schedule of attending attorneys when setting a schedule for cases, such as due dates for trials.
In addition, there was a need for a mechanism that can efficiently manage the amount of deposits for incidents.

The present invention has been made in view of the above circumstances, and an object thereof is to provide an incident information management system and the like for efficiently managing various information related to incidents.
Another object of the present invention is to provide an incident information management system or the like that can avoid duplication of schedules of incident personnel.
Another object of the present invention is to provide a case information management system or the like that can efficiently manage the amount of deposits for cases.

In order to achieve the above object, an incident information management system according to the first aspect of the present invention provides:
Storage means for storing various data related to the incident;
A means to input basic information including incident type data regarding the incident,
Means for generating an incident information ID in response to the input of the basic information;
Means for assigning the incident information ID to the received basic information and registering it in the storage means;
Means for acquiring document data generated with respect to the case, associating the acquired document data with the case information ID of the case, and registering it in the storage means;
In response to the notification indicating the completion of the case, the document data associated with the case information ID of the case is read from the storage means, and based on the case type data included in the basic information of the case, a predetermined data Means for classifying and registering each case type in the database;
It is characterized by providing.

With respect to the case schedule, means for entering case schedule information including information on the person in charge,
Referring to a schedule database in which individual schedules are registered, it is determined whether there is a duplication of the schedule of the person in charge in the inputted incident schedule information. A schedule registration means for assigning the case information ID of the case to the information and registering it in the storage means, and storing schedule information of a person in charge based on the case schedule information in the schedule database;
May be further provided.

  The schedule registration means determines the priority according to a predetermined standard for the duplicate schedule when the schedule of the person in charge for the incident case information that has been input occurs, and activates the schedule with the higher priority. Also good.

Deposit amount storage means for storing the amount information of deposits for each incident;
A means of entering deposit / withdrawal information regarding the deposit / withdrawal of the case;
The incident information ID of the incident is assigned to the input money acquisition information and registered in the storage means, and the deposit amount storage means stores the deposit amount based on the deposit / withdrawal information indicated by the deposit / withdrawal information. A means of updating the case deposit,
Expense calculation means for updating the deposit amount of the case stored in the deposit amount storage means based on information on the expense of the case;
May be further provided.

  The expense calculation means calculates a transportation cost associated with the movement of a schedule related to an incident registered in a schedule database in which a personal schedule is registered, and uses the calculated transportation expenses as a withdrawal amount to deposit the incident. May be updated.

In response to an output request for a document related to an incident, the apparatus may further include means for counting the number of output documents for each incident.
The expense calculating means may calculate the document cost for each case based on the counted number of output documents, and update the deposit amount of the case with the calculated document cost as a withdrawal amount.

A program according to the second aspect of the present invention is
Computer
Storage means for storing various data related to the incident,
A means of receiving basic information about the case, including case type data,
Means for generating an incident information ID in response to the input of the basic information;
Means for assigning the incident information ID to the received basic information and registering it in the storage means;
Means for acquiring document data generated with respect to the case and registering the acquired document data in the storage means in association with the case information ID of the case;
In response to the notification indicating the completion of the case, the document data associated with the case information ID of the case is read from the storage means, and the document data is classified and stored for each case type in another database. Means to register,
To function as.

  According to the present invention, it is possible to efficiently manage various information related to the incident.

Hereinafter, an incident information management system according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 shows a configuration example of an incident information management system according to an embodiment of the present invention. As shown in the figure, the incident information management system includes an incident management server 1, a document management server 2, a user terminal 3, and a digital multifunction peripheral 4, which are connected via a network 10. The network 10 includes, for example, a LAN, the Internet, a dedicated line, a public line network, a mobile communication network, a wireless communication network, and the like.

  For example, as shown in FIG. 2, the case management server 1 includes a computer that manages the entire system, and includes a control unit 11, a storage unit 12, an input unit 13, a display unit 14, a communication control unit 15, and the like. .

  The control unit 11 includes a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like, and reads and executes an operation program stored in the storage unit 12 in advance, thereby The input unit 111, deposit management unit 112, data management unit 113, completion case registration unit 114, and the like are logically realized.

  The data input unit 111 receives various types of information about the case from the user terminal 3, assigns the case information ID of the case to the received information about the case, and registers the information in the case database (DB) 121 of the storage unit 12. I do.

Specifically, when receiving a basic information registration request from the user terminal 3, the data input unit 111 requests the user terminal 3 to input data related to the basic information by transmitting an input screen related to the basic information. When input data for this is received, a unique case information ID and a password are generated for each case, and basic information is generated by adding the case information ID to the received input data, and is registered in the case DB 121. . The generated case information ID and password are stored in the storage unit 12 and transmitted to the user terminal 3 together with the notification of the completion of basic information registration.
Basic information includes, for example, case information ID, case name, case number, requester data (requester name, status, address, date of birth, age, gender, telephone number, FAX number, e-mail address, work address / Telephone number, personal / corporate type, etc.), lawyer data (lawyer name, etc.), partner data (partner name, position, address, date of birth, age, gender, phone number, fax number, email address, work) Previous address / phone number, personal / corporate type, etc.), agent data (agent name, office name / address / phone number / fax number / email address, etc.), court data (court name, phone number, Includes data such as judges, departments in charge (for example, “civil”, “criminal”, “housework”, “mediation”, etc.), telephone numbers, fax numbers, etc.).

  Further, after registering the basic information in the case DB 121, the data input unit 111 generates deposit information and output number information (initial value 0) for the case information ID of the basic information and stores them in the storage unit 12. As shown in FIG. 3, for example, the deposit information includes data such as an incident information ID, a deposit meter (total amount of deposit), a withdrawal total (total amount of deposit), a deposit balance, and the like. The output number information includes data such as the case information ID and the output number.

  In addition, when the data input unit 111 receives from the user terminal 3 a registration request for various information related to the incident other than the basic information (date information, acquisition information, document data, etc. described later), A case information ID and password input request is transmitted to the user terminal 3 to obtain input data (case information ID and password), and the input case information ID and password are registered in the storage unit 12. Screen of the input operation screen that verifies the case information ID and password, and if it matches, accepts a request for registration of various information and supplies the user terminal 3 with an input operation screen for inputting and displaying various information related to the case The configuration is arbitrary. For example, by using tabs, switching buttons, etc., the input / display screen for various information related to one incident can be switched. It may be as a possible display configuration. An example of the input operation screen is shown in FIG.

  For example, if the received registration request is a request for registration of due date information (case schedule information) related to the date of the case (the date and time when persons involved in the case meet and perform various litigation actions), etc. The data is transmitted to the user terminal 3 and the input data corresponding thereto is received. And the schedule duplication check process which checks whether the duplication of a schedule generate | occur | produces about the received input data is performed. In this schedule duplication check process, for example, the data input unit 111 determines whether schedule information corresponding to “date” and “attendant lawyer name” included in the received data is already registered in the schedule DB 122. If the corresponding schedule information is not registered, it is determined that there is no duplication of schedules, and the case information ID input earlier is assigned to the received input data to generate due date information and stored in the case DB 121. While registering, schedule information based on the due date information is generated and registered in the schedule DB 122 of the storage unit 12. The date information includes, for example, case information ID, date, start time, end time, place, attending attorney name, presence / absence of the person, etc., submission documents, and the like. If the corresponding schedule information has already been registered, the data input unit 111 determines the priority of the schedule according to a preset criterion and sets the schedule with the higher priority to be valid. To do. For example, if the input schedule has a higher priority, the input of change is accepted for the schedule information with the lower priority, and the setting information of the corresponding schedule information is changed in the schedule DB 122 according to the received contents. Thereafter, as described above, due date information may be stored in the storage unit 12 and corresponding schedule information may be registered in the schedule DB 122. In addition, if the input schedule has lower priority, it accepts the input of the change regarding the information regarding the input date, and sets the changed input data after checking the duplicate schedule again. It may be. As an example of the criteria for determining the priority of the schedule, for example, the priority is determined based on the set value of a predetermined data item in the basic information or other information that gives priority to the schedule related to the due date (for example, the “complaint amount” For example, the higher value is given priority, the “court” is ranked, the higher one is given priority, etc.).

Further, for example, when the received registration request is a registration request for deposit / withdrawal information, input screen data relating to the money received is transmitted to the user terminal 3 and input data corresponding thereto is received. Then, the case information ID input earlier is added to the received input data to generate deposit / withdrawal information, and is registered in the case DB 121. The deposit / withdrawal information includes, for example, data such as case information ID, date, requester name, deposit amount, withdrawal amount, summary, and the like.
For example, when the received registration request is a document data registration request, the user terminal 3 is requested for document data to be registered. Then, when the document data to be registered is received from the user terminal 3, for example, a document data folder having the case information ID input earlier as a folder name is generated under the case DB 121, and the document data is stored. Then, the document data is registered in the case ID 121 in association with the case information ID. The type and content of the document to be registered is arbitrary, and includes, for example, documents such as custody documents, submitted documents, reports, and memos. The method of associating the document data with the case information ID is arbitrary. For example, the file name of the document data may be set to “case information ID + document name”.

  The deposit management unit 112 performs a deposit automatic calculation process for each case information ID. Specifically, for example, when deposit / withdrawal information is registered in the storage unit 12, the corresponding deposit information is specified using the case information ID included in the registered deposit information. Then, the value of “Deposit amount” in the registered deposit / withdrawal information is added to the value of “Deposit amount” in the specified deposit information, and the value of “Withdrawal amount” in the deposit / withdrawal information is added to the deposit amount. It is added to the value of “withdrawal” in the information. Then, after adding each value, for the deposit information, a value obtained by subtracting the value of “withdrawal meter” from the value of “deposit” is set and stored in “deposit balance”.

Further, the deposit management unit 112 extracts movement content data (case information ID, destination, etc.) related to the case for the lawyer in charge of each case from the schedule DB 122 at a predetermined timing (for example, once / day). The transportation cost is calculated based on the extracted movement content data. Specifically, for each basic information registered in the case DB 121, data such as “case information ID” and “name of lawyer in charge” are taken out, and the data of “case information ID” and “lawyer in charge” taken out are included. , "Date" is a predetermined value (for example, the date of the current day when the check timing is once / day), and the destination data is extracted from the extracted schedule information, for example, destination data and address data The address data corresponding to the acquired destination data is acquired by referring to the database associated with. Then, by referring to a database in which the address data and the nearest station data are associated, the nearest station data corresponding to the obtained address data is obtained. And, for example, by designating a departure station and a destination station, a transportation cost calculation system in which a transportation cost between designated stations is calculated, etc., “the nearest station of the office” preset in the storage unit 12 Is designated as the departure station, the “nearest station” obtained as described above is designated as the destination station, and the transportation cost data output for these inputs is obtained. In addition, about a transportation expense calculation system, you may utilize the service provided from another computer via the network 10, and memorize | stores the program for implement | achieving this system in the memory | storage part 12, The control unit 11 may read and execute this.
Then, the deposit management unit 112 provides data such as the case information ID, date, deposit amount (0), withdrawal amount (transportation amount), summary ("transportation cost"), etc., regarding the schedule information for calculating the transportation cost. Is generated and registered in the case DB 121. Then, the deposit information specified by the case information ID of the registered deposit information is updated as described above.

  Further, the deposit management unit 112 reads out data on the number of output documents of each case stored in the storage unit 12 at a predetermined timing (for example, once a day), and calculates a predetermined calculation formula ( For example, the document cost is calculated for each case information ID according to document cost = output cost of 1 sheet × number of output sheets. Then, as described above, the deposit information specified by the case information ID is updated, and the output number information in the storage unit 12 is cleared.

  When the data management unit 113 receives a document data request specifying the case information ID and the document name from the user terminal 3 for the document data registered in the storage unit 12, the data management unit 113 sets the specified case information ID and the document name. The corresponding document data file (for example, stored in the folder having the folder name “case information ID”) is read from the storage unit 12 and transmitted to the user terminal 3 that made the request. When the print request for the document data is received from the user terminal 3, the designated document data is read from the storage unit 12 and transmitted to the digital multifunction peripheral 4 together with the print request. Then, for the output number information stored in the storage unit 12, the output number information corresponding to the case information ID given to the designated document data is specified, and the “output number” value of the specified output number information is set. Then, the value of the number of prints this time is added.

When the completed case registration unit 114 receives a notification that the case has been completed and the case information ID from the user terminal 3, the completed case registration unit 114 reads out the document data associated with the received case information ID from the case DB 121, together with a predetermined registration request. To the document management server 2. At this time, the completed case registration unit 114 specifies the basic information including the specified case information ID from the case DB 121, retrieves the case number data in the specified basic information, and sets the case information ID and the case number as described above. Include in your registration request.
In addition, the completed case registration unit 114, for example, in response to receiving notification of the completion of the case, reads the money acquisition information to which the designated case information ID is assigned, and obtains the money acquisition history from the read data. After automatically generating report data to be shown and storing the report data in the storage unit 12 in association with the case information ID (for example, after storing the report data in a folder with the folder name “case information ID”), from the storage unit 12, All the document data associated with the designated case information ID may be read and transmitted to the document management server 2.

The storage unit 12 stores an operation program executed by the control unit 11 and various data necessary for processing.
The storage unit 12 includes an incident DB 121 and a schedule DB 122.
The incident DB 121 stores basic information to which an incident information ID is assigned, related information, and the like.
In the schedule DB 122, schedule information of employees (lawyers, secretaries, etc.) is registered. The schedule information includes data such as staff name, date and time (start time, end time), destination, contents (in case of schedule related to due date, case information ID is set). Among the schedule information registered in the schedule DB 122, the schedule information related to the due date is registered together with the registration of the due date information to the incident DB 121 as described above, and the schedule information related to other than the due date is registered by a predetermined schedule registration tool. The The schedule registration tool is activated on a predetermined server (or the case management server 1). When activated by the case management server 1, for example, the control unit 11 functions as a schedule registration unit by reading and executing an operation program stored in the storage unit 12. In response to a schedule registration request from the user terminal 3, the schedule registration unit requests a schedule input by transmitting a schedule input screen to the request source, receives input data for the schedule, and schedules as schedule information. Register in DB122.

The input unit 13 includes an input device such as a keyboard and a pointing device, and transmits input data to the control unit 11.
The display unit 14 is constituted by a display device such as a display device, for example, and outputs various screens according to instructions from the control unit 11.
The communication control unit 15 controls communication with other devices via the network 10 in accordance with instructions from the control unit 11.

  The document management server 2 is composed of a computer that manages various types of information on completed cases. For example, as shown in FIG. 5, the storage unit 21, the control unit 22, the display unit 23, the input unit 24, and communication control Unit 25.

  The storage unit 21 stores an operation program executed by the control unit 22 and various data necessary for processing. The storage unit 21 includes a document DB 211 in which document data is stored for each case type and for each year. The document DB 211 includes an “case type folder” set in advance for each type of case. The case type folder is generated for each code included in the case number, for example, and each code is set as a folder name. In addition, in the subfolders of each case type folder, a “year folder” in which the year is set as the file name is generated in advance for each year.

The control unit 22 includes a CPU, a ROM, a RAM, and the like. By reading and executing an operation program or the like stored in advance in the storage unit 21, the control unit 22 receives various document data related to the incident and stores it in the document DB 211 of the storage unit 21. Document data registration processing for classifying and storing each incident type and year.
In this document data registration process, when a plurality of document data is received together with a registration request from the case management server 1, the document DB 211 in the storage unit 21 is applied based on the code included in the case number included in the received registration request. The case type folder to be specified is specified, and the corresponding year folder is specified from the subfolder of the specified case folder based on the year included in the case number. For example, when the case number is “2004 (Wa) XXX”, the case type folder corresponding to the code “W” is specified, and then in the subordinate folder of the specified case type folder The year folder corresponding to “2004” is identified. Then, the control unit 22 creates a document storage folder with the case information ID as the folder name under the specified year folder, and stores the received document data.

  In addition, when receiving a search request specifying a search condition from the user terminal 3, the control unit 22 searches the document data registered in the document DB 211 according to the specified search condition, and transmits the search result to the user terminal 3. To do.

The display unit 23 is configured by a display device such as a display device, for example, and outputs various screens according to instructions from the control unit 22.
The input unit 24 is configured by an input device such as a keyboard and a pointing device, for example, and transmits input data to the control unit 22.
The communication control unit 25 controls communication with other devices via the network 10 in accordance with instructions from the control unit 22.

The user terminal 3 includes a computer that includes a control unit, a storage unit, a display unit, an input unit, and a communication control unit.
The control unit of the user terminal 3 reads out and executes an operation program or the like stored in advance in the storage unit, thereby connecting to the case management server 1 via the network 10 and receiving various screen data from the case management server 1. Displaying and transmitting the input data to the incident management server 1, for example, performs processing for registering various information related to the incident. The control unit also performs processing for generating various document data related to the incident. The method of generating document data is arbitrary, and includes creation by various document creation software such as word processor software, spreadsheet software, presentation software, and reading of a paper document by a scanner. Further, the control unit requests and receives document data registered in the incident management server 1, and displays the received document data on the display unit. When a print instruction is input for the displayed document data, a print instruction specifying a file name or the like of the displayed document is transmitted to the case management server 1. Further, the control unit transmits a search request including the search condition input from the input unit to the document management server 2, receives a search result for the search request, and displays the search result on the display unit.

  In addition, the storage unit of the user terminal 3 is configured by, for example, a hard disk device or the like, and stores an operation program to be executed by the control unit, various data necessary for processing, and the like. The input unit includes an input device such as a keyboard and a pointing device, and transmits input data to the control unit. The display unit is configured by a display device such as a display device, for example, and outputs various data according to an instruction from the control unit. The communication control unit controls communication with other devices via the network 10 in accordance with an instruction from the control unit.

  The digital multifunction peripheral 4 includes a control unit including a CPU, ROM, RAM, and the like, a reading unit including a scanner, a printing unit, a communication unit, a storage unit, and the like. The control unit reads out and executes various programs stored in the storage unit, thereby controlling the reading unit, the printing unit, the communication unit, and the like to realize various functions such as a copying machine and a facsimile.

Next, the operation of the incident information management system according to the embodiment of the present invention will be described.
First, an incident information registration process for registering various information related to an incident in the incident DB 121 will be described with reference to the flowchart of FIG.
For example, the control unit 11 of the incident management server 1 performs a predetermined authentication process using a preset user ID, password, etc. in response to a login request from the user terminal 3, and then displays the initial menu screen on the user terminal 3 to send. When “registration of incident information” is selected on the initial menu screen, data to that effect is transmitted from the user terminal 3 to the incident management server 1.
In response to this, the control unit 11 of the incident management server 1 transmits, for example, input screen data for selectively inputting whether or not the registration is a new registration (basic information registration) to the user terminal 3, and the input data corresponding thereto. Is received (step S1). Then, when data indicating new registration is received (step S2: YES), an input screen related to basic information is transmitted to the user terminal 3, and input data for this is received (step S3). A unique case information ID is generated (step S4), and the generated case information ID is added to the input data to generate basic information (step S5). Then, the control unit 11 registers the generated basic information in the incident DB 121 of the storage unit 12 (Step S6).

  In step S2, if data indicating that the registration is not new is received (step S2: NO), the control unit 11 transmits the case information ID and password input screen data to the user terminal 3, and responds to this. Input data is received (step S7). Then, the received input data (case information ID and password) is compared with the case information ID and password registered in the storage unit 12 to determine whether or not they match (step S8). (Step S8: NO), the control unit 11 performs predetermined error processing such as transmitting an error message (Step S41) and ends. Further, if they match (step S8: YES), the control unit 11 displays, inputs, outputs, etc. various information related to the case (the case specified by the case information ID input in step S7). An input operation screen (see FIG. 4) for receiving various instruction inputs is supplied to the user terminal 3 (step S9), input for specifying information to be registered is received, and data input necessary for registration is performed for the specified information. And processing for registering the input data in the case DB 121 (various information registration processing) is performed (step S10). Next, specific contents of the various information registration processes will be described with reference to FIGS.

For example, due date information registration processing when “date information” is designated from the user terminal 3 as information to be registered will be described with reference to the flowchart of FIG.
The control part 11 transmits the input screen data of the information regarding a due date to the user terminal 3, and receives the input data corresponding thereto (step S11).
Then, it is determined whether schedule information corresponding to “date” and “attendant lawyer name” included in the received input data is already registered in the schedule DB 122 (step S12).
If it is determined that the schedule information is not registered in the schedule DB 122 (step S12: NO), the control unit 11 assigns the incident information ID input in step S7 to the received input data. Date information is generated and registered in the incident DB 121 (step S13). Also, schedule information based on the due date information is generated and registered in the schedule DB 122 of the storage unit 12 (step S14).

Further, when it is determined in step S12 that the schedule information is registered in the schedule DB 122 (step S12: YES), the control unit 11 determines the priority of the schedule according to a preset criterion. (Step S15). Then, based on the determination result, a process for effectively setting the schedule with the higher priority is performed (step S16).
Thereby, the date information linked | related with case information ID is registered into case DB121.

Next, for example, acquisition money information registration processing in the case where “acquisition information” is designated from the user terminal 3 as information to be registered will be described with reference to the flowchart of FIG.
The control part 11 transmits the input screen data of the information regarding acquisition money to the user terminal 3, and receives the input data with respect to this (step 21).
And the control part 11 produces | generates acquisition information by giving the case information ID input by step S7 to the received input data, and registers it into case DB121 (step S22).
As a result, the money acquisition information associated with the case information ID is registered in the case DB 121.

Next, for example, document data registration processing when “document data” is designated as registration target information from the user terminal 3 will be described with reference to the flowchart of FIG. 9.
The control unit 11 requests the document data to be registered from the user terminal 3, and receives the document data corresponding thereto (step S31). Then, when the document data to be registered is received from the user terminal 3, for example, a document data folder having the case information ID input earlier as a folder name is generated under the case DB 121, and the document data is stored. Then, the document data is associated with the case information ID and registered in the case DB 121 (step S32).

  Next, a document transmission process in which the case management server 1 transmits document data of a completed case to the document management server 3 will be described with reference to FIG.

For example, the control unit 11 of the incident management server 1 receives the incident information ID and data indicating that the incident has been completed from the user terminal 3 (step S51). Specifically, for example, in the case information registration process (FIG. 6) described above, steps S1, S2, and S7 (case information ID and password input), S8, and S9 are sequentially executed, and an input regarding the case is input to the user terminal 3. In the scene where the operation screen (see FIG. 4) is displayed, for example, a completion button provided on the input operation screen is pressed, and the control unit 11 of the case management server 1 receives data from the user terminal 3 to that effect. .
In response to this, the control unit 11 specifies basic information including the case information ID received from the user terminal 3 from the case DB 121, and takes out the data of the case number in the specified basic information (step S52). Moreover, the control part 11 reads the document data linked | related with case information ID from case DB121 (step S53).
And the control part 11 transmits the registration request | requirement containing incident information ID and an incident number to the document management server 2 with the document data read from incident DB121 (step S54).

Next, a document registration process in which the document management server 2 registers the document data received from the incident management server 1 in the document DB 211 will be described with reference to FIG.
The control unit 22 of the document management server 2 receives a plurality of document data from the case management server 1 together with a registration request (step S61).
Then, the control unit 22 specifies the corresponding case type folder based on the code included in the case number included in the received registration request in the document DB 211 of the storage unit 21, and from the subordinate folder of the specified case folder, Based on the year included in the case number, the corresponding year folder is specified (step S62).
Then, the control unit 22 generates a document storage folder with the case information ID as the folder name under the specified year folder (step S63), and stores the received document data (step S64).

  As described above, according to the present invention, it is possible to efficiently manage various information related to an incident by associating it with an incident information ID. In addition, when registering a schedule related to a due date, it is possible to avoid a schedule being registered twice. In addition, for completed cases, document data relating to the cases can be classified and registered in the database according to the type of the case. In addition, by referring to the schedule DB, the transportation cost of the lawyer in charge of the case can be calculated and recorded as a case-by-case expense.

The present invention can be variously modified and applied.
For example, the case management server 1 may be provided with a function of faxing document data registered in the case DB 121 to a client or the like.
Specifically, when the user selects and inputs “Yes” on the presence / absence of a cover page on the input operation screen supplied from the case management server 1 to the user terminal 3 after designating the case information ID, the case management server 1 The control unit 11 reads out data such as the name of the client of the case from the basic information corresponding to the case information ID specified in advance, and the destination area of the format of the FAX document registered in the storage unit 12 in advance By setting to, invoice data is generated. For example, when a user selects an attached document from a list of document data of the case displayed on the input operation screen and the FAX button is pressed, the control unit 11 converts the document data selected by the user into the case. Along with the invoice data read and generated from the DB 121, the fax may be sent to the fax number of the client set in the basic information.

The case management server 1 may further include a function of automatically generating a document draft using basic information registered in the case ID 121 or the like.
Specifically, the storage unit 12 of the case management server 1 stores information on format data of various documents (reports, submitted documents, etc.) and insertion patterns (indicating which items are inserted where) into each format data. Is stored. Then, on the input operation screen supplied from the incident management server 1 to the user terminal 3 after the user specifies the incident information ID, a list of various documents registered in the incident management server 1 is called, When an input for selecting a document is made, the control unit 11 of the incident management server 1 reads the format data of the designated document, refers to the insertion pattern information corresponding to the format data, and reads predetermined data ( For example, a document is automatically generated by inserting a client name, address, etc.) into a predetermined position (area) of the format data.

The system of the present invention can be realized using a normal computer system, not a dedicated system. For example, a program for executing the above operation is stored in a computer-readable recording medium (FD, CD-ROM, DVD, etc.) and distributed, and the program is installed in the computer to execute the above processing. The incident management server 1, the document management server 2, the user terminal 3, and the like may be configured. Alternatively, it may be stored in a disk device of a server device on a network such as the Internet and downloaded to a computer, for example.
In addition, when the OS realizes the above functions by sharing the OS or jointly with the OS and the application, etc., only the part other than the OS may be stored and distributed in the medium, or may be downloaded to the computer. Good.

It is a figure which shows the structural example of the incident information management system which concerns on embodiment of this invention. It is a figure which shows the structural example of the case management server used with the case information management system of FIG. It is a figure for demonstrating deposit information. It is a figure which shows an example of an input operation screen. It is a figure which shows the structural example of the document management server used with the incident information management system of FIG. It is a flowchart for demonstrating case information registration processing. It is a flowchart for demonstrating a date information registration process. It is a flowchart for demonstrating acquisition money information registration processing. It is a flowchart for demonstrating document data registration processing. It is a flowchart for demonstrating a document transmission process. It is a flowchart for demonstrating a document registration process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Case management server 2 Document management server 3 User terminal 4 Digital multifunction device 10 Network 11 Control part 12 Storage part 13 Input part 14 Display part 15 Communication control part 111 Data input part 112 Deposit management part 113 Data management part 114 Completion case registration Part 121 Incident DB
122 Schedule DB
21 Storage Unit 22 Control Unit 23 Display Unit 24 Input Unit 25 Communication Control Unit 211 Document DB

Claims (7)

Storage means for storing various data related to the incident;
A means to input basic information including incident type data regarding the incident,
Means for generating an incident information ID in response to the input of the basic information;
Means for assigning the incident information ID to the received basic information and registering it in the storage means;
Means for acquiring document data generated with respect to the case, associating the acquired document data with the case information ID of the case, and registering it in the storage means;
In response to the notification indicating the completion of the case, the document data associated with the case information ID of the case is read from the storage means, and based on the case type data included in the basic information of the case, a predetermined data Means for classifying and registering each case type in the database;
An incident information management system characterized by comprising: With respect to the case schedule, means for entering case schedule information including information on the person in charge,
Referring to a schedule database in which individual schedules are registered, it is determined whether there is a duplication of the schedule of the person in charge in the inputted incident schedule information. A schedule registration means for assigning the case information ID of the case to the information and registering it in the storage means, and storing schedule information of a person in charge based on the case schedule information in the schedule database;
The incident information management system according to claim 1, further comprising: The schedule registration means determines the priority according to a predetermined standard for the duplicate schedule when the schedule of the person in charge for the input incident schedule information occurs, and the schedule with the higher priority is valid. To
The incident information management system according to claim 2, wherein: Deposit amount storage means for storing the amount information of deposits for each incident;
A means of entering deposit / withdrawal information regarding the deposit / withdrawal of the case;
The incident information ID of the incident is assigned to the input money acquisition information and registered in the storage means, and the deposit amount storage means stores the deposit amount based on the deposit / withdrawal information indicated by the deposit / withdrawal information. A means of updating the case deposit,
Expense calculation means for updating the deposit amount of the case stored in the deposit amount storage means based on information on the expense of the case;
The incident information management system according to any one of claims 1 to 3, further comprising: The expense calculation means calculates a transportation cost associated with the movement of a schedule related to an incident registered in a schedule database in which a personal schedule is registered, and uses the calculated transportation expenses as a withdrawal amount to deposit the incident. Update,
The incident information management system according to claim 4, wherein: In response to a document output request relating to an incident, the apparatus further comprises means for counting the number of output documents for each incident,
The expense calculation means calculates a document cost for each case based on the counted number of output documents, and updates the deposit amount of the case with the calculated document cost as a withdrawal amount.
The incident information management system according to claim 4 or 5, characterized by the above. Computer
Storage means for storing various data related to the incident,
A means of entering basic information about the case, including case type data,
Means for generating an incident information ID in response to the input of the basic information;
Means for assigning the incident information ID to the received basic information and registering it in the storage means;
Means for acquiring document data generated with respect to the case and registering the acquired document data in the storage means in association with the case information ID of the case;
In response to the notification indicating the completion of the case, the document data associated with the case information ID of the case is read from the storage means, and the document data is classified and stored for each case type in another database. Means to register,
Program to function as.

Images