JP2007011758A - Insurance data management device and method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a management burden of insurance data in an insurance data management device and method, and a program. <P>SOLUTION: The insurance management device capable of communicating with a client 5 is provided with a storage conversion data storage means 6 for storing storage conversion data 6a representing the corresponding relation between data items of an input format and data items of a storage format; an acquiring means 9 for acquiring input insurance data D1 from the client 5; a storage conversion means 10 for converting the input insurance data D1 acquired from the client 5 by the acquiring means 9, into storage insurance data D2 based on the storage conversion data 6a stored in the storage conversion data storage means 6; and a data storage means 7 for storing the storage insurance data D2 obtained by the storage conversion means 10. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an insurance data management apparatus, method, and program for centrally managing data relating to insurance (hereinafter referred to as “insurance data”) such as insurance customer information.

  In corporate insurance, insurance data including customer information is exchanged between an insurance company and a customer (company, contractor) through a recording medium.

As a system relating to insurance, Japanese Patent Application Laid-Open No. 2004-326822 describes a method for managing a reserve of insurance premiums.
JP 2004-326822 A

  When an insurance company exchanges insurance data with a customer, a standard (general purpose) format is defined for the data layout, data items, and the recording medium for recording insurance data, and exchanges are made according to this format. Encourage

  However, in recent years, the format of insurance data received from customers may differ from the standard format of insurance companies due to the integration of insurance companies.

  Even when there is an insurance company integration or the like, the customer may request “continue use of the previous format”.

  In addition, a customer may have a plurality of insurances and a unique format may be defined for the customer.

  Therefore, the insurance company needs to be able to handle the insurance data that does not follow the standard format flexibly.

  In order to receive insurance data in a customer's own format, an insurance company needs to develop and test a system that makes its own data management server compatible with that format.

  Also, in the insurance company's office, when handling insurance data in a unique format, the burden of insurance data verification work and the like is greater than when handling insurance data in a standard format.

  Insurers suggest using a standard format for customers who use such proprietary formats. In this case, it takes time and labor for the discussion between the insurance company and the sales office of the insurance company and the customer.

  When an original format is approved, the insurance company needs to incorporate a conversion program into the data management device for each customer who uses the original format, which requires a development cost, requires a development period, and manages a new program. A load is generated.

  In a conventional insurance data management device, when creating predetermined data based on insurance data, it is necessary to input an instruction to create this data on the day of data creation via online.

  However, in the method of manually inputting the data creation instruction on the data creation day, the person in charge of data creation may forget to enter the creation instruction on the data creation day, or the creation instruction may be erroneously input.

  In addition, when there are many manual operations by the person in charge of data creation, there are many opportunities to perform verification work on the created data, and the load of the verification work increases.

  Further, since the verification work of the created data is performed using a dump list that is a list in which numerical values are arranged, there is a problem that the workload of the verification worker and the work load are high.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to provide an insurance data management device, method, and program for reducing insurance data management burden and facilitating insurance data verification. To do.

  In an aspect of the present invention, an insurance data management device capable of communicating with a client includes a conversion data storage unit for storage that stores conversion data for storage that represents a correspondence relationship between data items in an input format and data items in a storage format. , An acquisition means for acquiring input insurance data from the client, and the input insurance data acquired from the client by the acquisition means based on the conversion data for storage stored in the conversion data storage means for storage Storage conversion means for converting into data, and data storage means for storing storage insurance data obtained by the storage conversion means are provided.

  In addition, said aspect is expressed as an apparatus. However, the present invention is not limited to this, and the above aspect may be expressed by a method, a program, a computer-readable storage medium, and the like.

  According to the present invention, the burden of insurance data management can be reduced.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, the same code | symbol is attached | subjected about the same part in each following figure, and description is abbreviate | omitted.

  FIG. 1 is a block diagram showing an example of an insurance data management apparatus (insurance data verification infrastructure system) according to the present embodiment.

  The insurance data management device 1 includes an arithmetic device 2 such as a processor and various storage devices 3, 6 to 8, 16, and 17. The data management device 1 can communicate with the client 5 via the network 18. The insurance data management device 1 may be communicable with a plurality of clients via the network 18. A database may be used as the storage devices 3, 6 to 8, 16, and 17.

  As the network 18, for example, a LAN (Local Area Network) or the Internet can be used.

  The insurance data management device 1 reads and executes the program 4a recorded on the recording medium 4. The program 4a is read into the insurance data management device 1 and the contents thereof are executed by the arithmetic device (for example, processor) 2, thereby functioning as an upload unit 9, a storage conversion unit 10, an output conversion unit 11, and a download unit 12. .

  The schedule storage device 3 converts the date / time when the input insurance data D1 is uploaded from the client 5 and the date / time when the saved insurance data D2 is converted into the output insurance data (verification insurance data) D3 and downloaded to the client 5. Schedule data 3a representing time is stored.

  In the present embodiment, it is assumed that the insurance data for input D1 is formed based on a unique format (input format) of the customer who operates the client 5.

  The input insurance data storage device 16 stores the input insurance data D1 acquired by the upload unit 9 from the client 5 via the network 18.

  The storage conversion data storage device 6 stores storage conversion data 6a representing rules for converting the input insurance data D1 received from the client 5 into the storage insurance data D2.

  The data storage device 7 stores saved insurance data D2.

  In the present embodiment, the storage insurance data D2 is formed based on a standard format (storage format) adopted by the insurance company for management.

  The output conversion data storage device 8 includes output conversion data (including layout information data, sort information data, calculation information data, etc.) 8a representing rules for converting the saved insurance data D2 into the output insurance data D3. Remember.

  The output insurance data D3 is formed based on a display / verification format (output format) adopted by a user operating the client 5. For example, based on the display content of the output insurance data D3, the user verifies, confirms, and examines the content of the insurance data. It is assumed that the insurance data for output D3 is data that can be displayed, edited, and operated by spreadsheet software that is activated on the client 5.

  The output insurance data storage device 17 stores output insurance data D3.

  The upload unit 9 receives schedule data 3a, storage conversion data 6a, and output conversion data 8a from the client 5 via the network 18, and schedules the schedule data 3a, storage conversion data 6a, and output conversion data 8a, respectively. The data is stored in the storage device 3, the saved conversion data storage device 6, and the output conversion data storage device 8.

  Further, the upload unit 9 uploads the input insurance data D1 from the client 5 at the upload date and time represented by the schedule data 3a stored in the schedule storage device 3, and the input insurance data D1 is input to the input insurance data. Store in the storage device 16.

  The storage conversion unit 10 converts the insurance data for input D1 stored in the input insurance data storage device 16 into the insurance data for storage D2 based on the storage conversion data 6a stored in the storage conversion data storage device 6. The stored insurance data D2 is stored in the data storage device 7.

  The output conversion unit 11 is based on the output conversion data 8a stored in the output conversion data storage device 8 at the date and time when the data conversion represented by the schedule data 3a stored in the schedule storage device 3 is performed. The stored insurance data D2 stored in the data storage device 7 is converted into output insurance data D3, and the output insurance data D3 is stored in the output insurance data storage device 17.

  The download unit 12 sends the output insurance data D3 stored in the output insurance data storage device 17 to the client via the network 18 at the download date and time represented by the schedule data 3a stored in the schedule storage device 3 via the network 18. 5 is provided.

  FIG. 2 is a system configuration diagram showing an example of a schematic configuration of the insurance data management apparatus 1 according to the present embodiment.

  In FIG. 2, the insurance data management apparatus 1 of FIG. 1 is realized by an SQL server 13 and a host computer 14.

  The client 51 is used in a clerical department (for example, a corporate service department that handles group insurance). The client 52 is used in the system department.

  The user who operates the clients 51 and 52 inputs work request contents. The clients 51 and 52 notify the SQL server 13 of the input work request content. Further, the client 51 displays a screen for prompting data verification based on the output insurance data D3 received from the host computer 14 via the SQL server 13.

  Here, the work request content includes, for example, schedule data 3a, storage conversion data 6a, output conversion data 8a, input insurance data D1, and the like. In addition, the work request content includes recording medium designation data for designating the type of the recording medium 15 used for recording the output insurance data D3.

  The SQL server 13 and the host computer 14 cooperate to realize each function of the insurance data management apparatus 1 described above.

  In the present embodiment, data creation work such as schedule data 3a, storage conversion data 6a, output conversion data 8a, and input insurance data D1 is performed in cooperation between the office department and the system department.

  The clients 51 and 52 in the office department and the system department access the common SQL server 13 and notify the SQL server 13 of the contents of the work request.

  The SQL server 13 performs processing for realizing sharing of various data, management of work progress, and the like.

  The data stored in the SQL server 13 is transmitted to the host computer 14 on the day before the creation date of the output insurance data D3.

  The host computer 14 creates storage insurance data D2 and output insurance data D3 based on data such as storage conversion data 6a, output conversion data 8a, and input insurance data D1 received from the SQL server 13. .

  The generated output insurance data D3 is transmitted from the host computer 14 to the SQL server 13 and further transmitted to the clients 51 and 52. In the office department and the system department, the person in charge performs verification work while referring to the display contents of the output insurance data D3.

  FIG. 3 is a flowchart showing an operation example of the insurance data management apparatus 1 according to the present embodiment.

  In step S <b> 1, the client 51 operated by the office worker displays a screen that prompts the drafting of the work request form, inputs the work request content, and stores it in the SQL server 13.

  When the same or similar contents as the work request contents input in the past are inputted, the work request contents inputted in the past are edited by a copy function or the like, and new work request contents are inputted.

  In step S2, the client operated by the manager of the office worker displays a screen prompting the manager of the office worker to review the work request contents stored in the SQL server 13, accepts the confirmation input, and after confirmation. Are stored in the SQL server 13.

  In step S3, the client 52 operated by the person in charge of the system department displays a screen prompting a close examination of the work request contents after confirmation stored in the SQL server 13, accepts an approval input, and accepts the work request contents after the approval. Is stored in the SQL server 13. If there is new data, the person in charge of the system department inputs this new data, and if there is a change in layout, the output conversion data 8a corresponds to the changed layout. Rewrite.

  In step S4, the host computer 14 uploads the approved work request content stored in the SQL server 13. This upload is preferably done at night.

  In step S5, the client 51 of the office worker receives the inquiry form data for verification from the host computer 14 via the SQL server 13 as necessary, displays an online screen, and verifies the inquiry form data. Prompt.

  In step S6, the host computer 14 creates and stores storage insurance data D2 based on the data uploaded from the SQL server 13, creates output insurance data D3, and outputs the insurance data D3 for output. To the client via.

  In step S7, the client 51 operated by the office worker or the client operated by the manager of the office worker receives the output insurance data D3 from the host computer 14 via the SQL server 13, and based on the output insurance data D3. Display the verification screen. The verification screen may be displayed on the client 52 of the system department. In particular, when new data is added or the layout is changed in step S3, the system department also performs verification.

  In step S8, the output insurance data D3 verified by various clients is recorded on the recording medium 15 and provided to the customer.

  As described above, the SQL server 13 and the host computer 14 according to the present embodiment include, for example, schedule data 3a, storage conversion data 6a, output conversion data (layout information data, sort information data, calculation information data). Etc.), and a function of accepting work request contents including the input insurance data D1 from the clients 51 and 52.

  Further, the SQL server 13 and the host computer 14 according to the present embodiment have a function of managing the progress of the work situation by changing the status by the input actions of the clients 51 and 52 and the system processing.

  The SQL server 13 has a function of transmitting various data and a work instruction trigger to the host computer 14 on the night before the work instruction based on the contents of the registered schedule data 3a.

  The host computer 14 executes data conversion processing, processing processing, and recording on the recording medium 15 based on the data received from the SQL server 13 at night before the work instruction.

  The user who operates the clients 51 and 52 can verify the result of the conversion process and the processing process executed by the host computer 14 from the next day of the work instruction. The customer can be provided with the recording medium 15 in which the output insurance data D3 is recorded in a minimum of two business days.

  FIG. 4 is a diagram showing an example of a screen that displays the work progress status and prompts the user to input work request contents.

  For example, a layout for displaying insurance data can be designated by dragging and dropping on this screen.

  FIG. 5 is a diagram showing an example of a verification screen displayed based on the output insurance data D3 according to the present embodiment.

  This verification screen is displayed in accordance with an output format defined for verification by the user operating the clients 51 and 52. In this way, the user can perform the verification work easily and efficiently by displaying the verification screen divided by cells for each item by the spreadsheet software instead of the dump result.

  FIG. 6 is a block diagram illustrating an example of conversion processing of the storage conversion unit 10 according to the present embodiment.

  The conversion data for storage 6a designates the correspondence between each item (data item) X to Z, P to R of the input insurance data D1 before conversion and each item A to F of the storage insurance data D2 after conversion. is doing.

  For example, items Y, Q, P, and R before conversion correspond to items A, C, D, and F after conversion. Further, for example, a percentage is calculated based on the value of the item X, and the calculation result is inserted into the converted item B. For example, the item E after conversion has the first 10 digits and the last 10 digits, the constant value “0” is inserted in the first 10 digits, and the value of the item Z before conversion is inserted in the last 10 digits. . Thus, when the number of digits differs between the pre-conversion item and the post-conversion item associated with each other, the number of digits is adjusted.

  In addition, an average value or the like may be calculated based on the value of the item before conversion, and the calculated average value or the like may be included in the saved insurance data D2 as the value of the item after conversion. Further, a unit change calculation such as converting a value in a yen unit into a value in a hundred yen unit may be performed.

  The storage conversion unit 10 changes the position of each item value based on the correspondence relationship between the items represented by the storage conversion data 6a, the item position information (start position and number of digits), and the contents instructed by the arithmetic expression. Inserting constant values, editing special patterns (various operations), etc., create post-conversion saved insurance data D2 from pre-conversion input insurance data D1.

  FIG. 7 is a block diagram illustrating an example of conversion processing of the output conversion unit 11 according to the present embodiment.

  The output conversion data 8a specifies the correspondence between the items A to F of the storage insurance data D2 before conversion and the items G to K of the output insurance data D3 after conversion.

  For example, items A, B, F, and E before conversion correspond to items G, I, J, and K after conversion. Further, for example, an average value is calculated based on the values of the items C and D before conversion, and the calculated average value is inserted into the item H after conversion.

  In the output conversion data 8a, the converted items G to K are related to the start position indicating the position in the output conversion data 8a and the number of digits.

  In addition, in the output conversion data 8a, it is specified whether values are displayed right-justified or left-justified for the converted items G to K.

  Further, in the conversion data for output 8a, for the items G to K after conversion, a constant value when a constant value is inserted and a special pattern are specified.

  The output conversion unit 11 changes the position of each item value based on the correspondence between the items represented by the output conversion data 8a, the item position information (start position and number of digits), and the contents instructed by the arithmetic expression. Inserting constant values, editing special patterns (various operations), etc., create post-conversion output insurance data D3 from pre-conversion storage insurance data D2.

  FIG. 8 is a flowchart showing an example of processing by the insurance data management apparatus 1 according to the present embodiment.

  In step T <b> 1, the upload unit 9 receives the schedule data 3 a from the client 5 via the network 18 and stores the schedule data 3 a in the schedule storage device 3.

  In step T2, the upload unit 9 determines whether or not the current date and time has exceeded the upload execution date and time represented by the schedule data 3a.

  If the current date does not exceed the upload date, the process repeats step T2.

  When the current date and time exceeds the upload execution date and time, in step T3, the upload unit 9 receives the saved conversion data 6a, the output conversion data 8a, and the input insurance data D1 from the client 5 via the network 18. The storage conversion data 6a, the output conversion data 8a, and the input insurance data D1 are stored in the storage conversion data storage device 6, the output conversion data storage device 8, and the input insurance data storage device 16, respectively.

  In step T3, when the current date / time exceeds the upload execution date / time, the storage conversion data 6a, the output conversion data 8a, and the input insurance data D1 are received together. However, the storage conversion data 6a and the output conversion data 8a are stored in advance, and the input insurance data D1 may be received when the current date and time exceeds the upload execution date and time.

  In step T4, the storage conversion unit 10 converts the input insurance data D1 into the storage insurance data D2 based on the storage conversion data 6a, and stores the storage insurance data D2 in the data storage device 7.

  In step T5, the output conversion unit 11 and the download unit 12 determine whether or not the current date and time has exceeded the download execution date and time represented by the schedule data 3a.

  If the current date does not exceed the download date indicated by the schedule data 3a, the process repeats the process of step T5.

  In step T5, when the current date and time does not exceed the download date and time, the process may repeat step T2 and subsequent steps.

  When the current date and time exceeds the download execution date and time, in step T6, the output conversion unit 11 converts the saved insurance data D2 into the output insurance data D3 based on the output conversion data 8a, and outputs the output insurance data. Store in the storage device 17.

  In step T 7, the download unit 12 transmits the output insurance data D 3 stored in the output insurance data storage device 17 to the client 5 via the network 18.

  In the present embodiment described above, the user can easily set the output conversion data 8a using the client 5 in accordance with his / her intention.

  In the present embodiment, by uploading the output conversion data 8a to the insurance data management apparatus 1, the output conversion data 8a can be easily incorporated as a data conversion parameter, and the contents of the output insurance data D3 are changed to the customer. It can be easily customized to suit your needs.

  In the present embodiment, a special pattern is defined in the storage conversion data 6a and the output conversion data 8a, and conversion according to the special pattern is executed by the storage conversion unit 10 and the output conversion unit 11. For this reason, it is not necessary to individually develop and test the conversion program, so that the labor of the system department can be reduced, and the customer's request can be quickly responded.

  Customers can continue to use the previous format even if there is an insurance company integration. Insurance companies need to be able to handle insurance data that does not follow a standard format flexibly.

  In the present embodiment, the schedule data 3a is used to automatically upload data necessary for data verification from the client 5 to the insurance data management apparatus 1 at night before work. Thereby, the output insurance data D3 used for the verification work can be automatically created. Further, since it is possible to create and input data necessary for data verification with a margin in advance, it is possible to prevent the user from forgetting to input or erroneous input.

  According to the present embodiment, data verification is performed using a spreadsheet software function by referring to an easy-to-view screen with item headings, instead of performing data verification using a list of dumped data that is difficult to grasp. This can be done, and the workload of verification work can be reduced.

  In the present embodiment, it is possible to increase the number of parts to be automated in the data verification work process, to increase the accuracy of the work, and to reduce the work load and office work load of the verification worker.

  In the insurance data management apparatus 1 according to the present embodiment, data may be input and viewed on a Web browser or spreadsheet software.

  In the present embodiment, each component may be rearranged as long as the same operation can be realized, each component may be freely combined, and each component may be freely divided. Some components may be deleted. That is, the present embodiment is not limited to the above-described configuration as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage.

  In the present embodiment, the program 4a can be applied to the insurance data management apparatus 1 by writing it in the recording medium 4 such as a magnetic disk (flexible disk, hard disk, etc.), optical disk (CD-ROM, DVD, etc.), semiconductor memory, etc. It is. The technical document management program 4a can also be applied to the insurance data management apparatus 1 by being transmitted through a communication medium.

  The program 4a may be distributed and arranged in a plurality of computers, and the processing may be executed while cooperating with each other between the plurality of computers.

  In the present embodiment, each storage device may be realized by a database. Each storage device can be freely integrated and divided.

  The present invention is effective in the field of verifying insurance data.

The block diagram which shows an example of the insurance data management apparatus which concerns on embodiment of this invention. The system block diagram which shows the example of schematic structure of the insurance data management apparatus which concerns on this Embodiment. The flowchart which shows the operation example of the insurance data management apparatus which concerns on this Embodiment. The figure which shows an example of the screen which prompts the input of the content of work request while displaying a work progress state. The figure which shows an example of the verification screen displayed based on the insurance data for output which concerns on this Embodiment. The block diagram which shows the example of the conversion process of the preservation | save conversion part which concerns on this Embodiment. The block diagram which shows the example of the conversion process of the output conversion part which concerns on this Embodiment. The flowchart which shows an example of the process by the insurance data management apparatus which concerns on this Embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Insurance data management apparatus, 2 ... Arithmetic apparatus, 3 ... Schedule storage apparatus, 3a ... Schedule data, 4,15 ... Recording medium, 4a ... Program, 5, 51, 52 ... Client, 6 ... Conversion data storage part for preservation | save 6a ... Conversion data for storage, 7 ... Data storage device, 8 ... Conversion data storage device for output, 8a ... Conversion data for output, 9 ... Upload unit, 10 ... Storage conversion unit, 11 ... Output conversion unit, 12 ... Download , 13 ... SQL server, 14 ... host computer, 16 ... input insurance data storage device, 17 ... output insurance data storage device, 18 ... network, D1 ... input insurance data, D2 ... storage insurance data, D3 ... Insurance data for output

Claims (6)

In the insurance data management device that can communicate with the client,
Conversion data storage means for storage for storing conversion data for storage representing a correspondence relationship between data items in the input format and data items in the storage format;
Obtaining means for obtaining insurance data for input from the client;
Storage conversion means for converting the insurance data for input acquired from the client by the acquisition means into storage insurance data based on the storage conversion data stored in the storage conversion data storage means;
An insurance data management device comprising: data storage means for storing the insurance data for storage obtained by the storage conversion means. The insurance data management device according to claim 1,
Further comprising schedule storage means for storing schedule data representing a time for acquiring the input insurance data from the client;
The said acquisition means acquires the said insurance data for input from the said client in the time which the said schedule data memorize | stored in the said schedule data storage means represents, The insurance data management apparatus characterized by the above-mentioned. In the insurance data management device according to claim 1 or claim 2,
Output conversion data storage means for storing output conversion data representing the correspondence between the data items in the storage format and the data items in the output format;
Output conversion means for converting the saved insurance data stored in the data storage means into output insurance data based on the output conversion data stored in the output conversion data storage means;
The insurance data management device further comprising providing means for providing the output insurance data to the client. In the insurance data management device according to any one of claims 1 to 3,
The insurance data management device, wherein the output insurance data is screen display data. In an insurance data management method executed by an insurance data management device capable of communicating with a client,
The storage conversion data representing the correspondence between the data items of the input format and the data items of the storage format is stored in the storage conversion data storage means, and the insurance data for input is obtained by acquiring the insurance data for input from the client. Memorize it in the memory means,
Based on the storage conversion data stored in the storage conversion data storage means, the input insurance data stored in the input insurance data storage means is converted into storage insurance data,
An insurance data management method, wherein the insurance data for storage is stored in a data storage means. On a computer that can communicate with the client,
A function for storing conversion data for storage representing the correspondence between data items in the input format and data items in the storage format in the conversion data storage means for storage;
A function of acquiring insurance data for input from the client and storing it in the insurance data storage means for input;
A function of converting the insurance data for input stored in the insurance data storage means for input into insurance data for storage based on the conversion data for storage stored in the conversion data storage means for storage;
A program for realizing a function of storing the insurance data for storage in a data storage means.

Images