JP2011203998A - Insurance contract investigation system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent a situation where a recipient cannot receive insurance money due to him or her.SOLUTION: A plurality of computer systems (local systems) for a plurality of insurance companies and a central computer system (central system) are connected to a dedicated network. Each local system stores insurance contract information of an insurance company corresponding to the local system, while it does not store that of other companies. In response to a request an inquiry into the insurance contract information, the central system investigates the contract of the insurance corresponding to a target contractor from the plurality of local systems via the dedicated network, and stores investigation result information showing the result of the investigation. The stored investigation result information is provided to the terminal of the user who has made an inquiry into the insurance contact information.

Description

  The present invention relates to a technique for conducting a survey on insurance contracts using a computer.

  As a technique relating to provision of information on insurance contracts, for example, a technique disclosed in Patent Document 1 is known.

JP 2008-146338 A

  Incidentally, a service is known in which an insurance company collectively displays information on all insurance contracts between the insurance company and the contractor for the contractor.

  However, in general, a policyholder of a certain insurance company often has some insurance contract with another insurance company. As an example of such a case, there is a case where a life insurance is contracted with a life insurance company and a non-life insurance such as fire insurance is contracted with a non-life insurance company.

  In such a case, policyholders do not always know which insurance company and which insurance contracts, but rather, it seems that there are few policyholders who know all such things. It is done.

  For this reason, a case in which the beneficiary of the insurance money (for example, the contractor or a member of the family member) cannot receive the insurance money that should be received, that is, an “unintentional non-payment” occurs.

  Therefore, an object of the present invention is to reduce the possibility that a case in which a recipient cannot receive insurance money that should be received will occur.

  A plurality of local systems, which are a plurality of computer systems for a plurality of insurance companies, and a central system, which is another computer system, are connected to the dedicated network. Each local system stores insurance contract information of an insurance company corresponding to the local system, but does not store insurance contract information of an insurance company other than the insurance company corresponding to the local system. Communication between the local system and the central system is possible, but communication between the local systems is impossible. The central system responds to an inquiry request for insurance contract information, and the existence of an insurance contract for which the target person identified from the inquiry request is a contractor (for example, whether there is insurance contract information) And / or insurance contract information representing the details of the insurance contract itself) is investigated from each local system via a dedicated network, and the investigation result information representing the result of the investigation is stored. The survey result information stored in the central system is provided to an information processing terminal of a user who wishes to inquire about insurance contract information.

  The present invention is applicable to various insurance companies (life insurance company, non-life insurance company, etc.).

1 shows a configuration of an insurance contract investigation system according to an embodiment of the present invention. Show the relationship between systems. The 1st part of the flow of an insurance contract information provision process is shown. The 2nd part of the flow of an insurance contract information provision process is shown. The remaining part of the flow of the insurance contract information provision process is shown.

  Hereinafter, an embodiment of the present invention will be described. In the following description, a person who inquires for insurance contract information is referred to as a “user”, and a person who is an object of inquiry is referred to as a “subject”. A “user” is, for example, a policyholder or payee of a certain insurance company or a family of the policyholder or payee. Therefore, the user and the target person may be the same person.

  According to this embodiment, the user can acquire insurance contract information of all insurance companies whose target person is a contractor.

  FIG. 1 shows a configuration of an insurance contract investigation system according to the present embodiment. In the following description, in order to make the explanation easy to understand, it is assumed that there are three insurance companies, Company A, Company B, and Company C (of course, the number of insurance companies related to this embodiment is more than three. Or less). The database is abbreviated as “DB”.

  A central system 10, three local systems 20, 30, and 40 respectively corresponding to three insurance companies, a neutral institution system 805, a WEB server 801 of company A, and a user terminal 803 are provided. In order to make the explanation of the present embodiment easy to understand, a WEB server is shown only for company A, but in reality, each insurance company may have a WEB server.

  The neutral engine system 805 and the WEB server 801 are connected to a so-called open communication network such as the Internet 900. On the other hand, the central system 10 and the local systems 20, 30 and 40 are connected to a so-called closed communication network called a dedicated network 100. The neutral engine system 805 is connected not only to the Internet 900 but also to the dedicated network 100. The WEB server 801 is communicably connected to the common server 24 of company A.

  The neutral engine system 805 is a computer system of a neutral engine. The “neutral institution” here is an institution different from any insurance company. The neutral engine system 805 includes, for example, a processor (for example, a CPU (Central Processing Unit)) and a storage resource (for example, a memory), and the processor can execute various processes described later by executing a computer program.

  The user terminal 803 is an information processing terminal used by a user and has a display device. The user terminal 803 can communicate with the WEB server 801 and the neutral engine system 805 via the Internet 900 in a wired or wireless manner.

  The local systems 20, 30 and 40 are all computer systems, and have basic systems 21, 31 and 41, basic DBs 22, 32 and 42, and common systems 23, 33 and 43, respectively. Hereinafter, taking the local system 20 as an example, the above-described elements of the local systems 20, 30 and 40 will be described. In the description, the insurance company having the local system 20 is Company A as shown in FIG.

  The backbone system 21 is a computer system having functions and / or structures unique to the company A. The backbone system 21 manages the backbone DB 22.

  The backbone DB 22 is stored in a storage device connected to the backbone system 21. The basic DB 22 includes, for example, insurance contract information of customers of the company A, and does not include insurance contract information of customers of other insurance companies. The insurance contract information is information related to the insurance contract made with the customer. For example, the customer's personal information (for example, name, address, date of birth) and details of the insurance contract made with the customer (for example, the product name) , Maturity, special contract, etc.).

  The format of the insurance contract information included in the backbone DB 22 is a format unique to the company A (strictly, the backbone system 21 of the company A). For example, when an employee of Company A inputs insurance contract information into the backbone system 21 using an information processing terminal (not shown) connected to the backbone system 21, the insurance contract information in a format specific to Company A Is stored in the backbone DB 22.

  The common system 23 includes a common server 24 and a common DB 25.

  The common server 24 is a computer having a processor and storage resources, for example. The common server 24 can perform various processes described later, for example, when a processor in the common server 24 executes a computer program.

  The common DB 25 is stored in a storage device connected to the common server 24. The common DB 25 has insurance contract information read from the core DB 22 and converted in format. The format of information in the common DB is a format common to all insurance companies. The common system 23 also serves as an interface to the central system 10. The common server 24 has, for example, information (hereinafter referred to as conversion rule information) indicating a correspondence relationship between a format before conversion (a format peculiar to Company A) and a format after conversion (a format common to all insurance companies). Therefore, format conversion may be performed using the conversion rule information. For example, in the insurance contract information in the format unique to the company A, the value “1” has the first meaning, and in the insurance contract information in the common format, the value “3” has the first meaning. The conversion rule information possessed by the company common server 24 includes information representing a conversion rule of “1 → 3”. In the format conversion, conversion according to the conversion rule is performed.

  The common systems 23, 33 and 43 have substantially the same function and configuration, but the function and / or configuration may be customized for each insurance company. For example, the conversion rule information described above may be different for each common server.

  The local system 20 can communicate only with the central system 10 when the common system 23 (common server 24) is connected to the central system 10 (central server 11) via the dedicated network 100.

  The central system 10 is managed by an organization other than the insurance company (neutral organization or another organization). The central system 10 includes, for example, a central server 11 and a management DB 12.

  The central server 11 is, for example, a computer having a processor (for example, CPU) and a storage resource (for example, memory). For example, the central server 11 can perform various processes described later when a processor in the central server 11 executes a computer program.

  The management DB 12 is stored in a storage device connected to the central server 11. The management DB 12 stores all insurance contract information (hereinafter referred to as insurance contract information group) collected from the local systems 20, 30 and 40, as will be described later.

  FIG. 2 shows the relationship between the systems.

  As shown in FIG. 2A, the local systems 20, 30 and 40 are not communicably connected to each other, and therefore cannot communicate with each other. On the other hand, as shown in FIG. 2 (b), the central system 10 and the local systems 20, 30 and 40 are connected to each other so that they can communicate with each other. That is, each local system 20, 30 and 40 can communicate only with the central system 10, and the central system 10 can communicate with all the local systems 20, 30 and 40. Such control can be realized by, for example, a group VPN (Virtual Private Network).

  In the insurance contract research system as described above, insurance contract information provision processing is performed for providing the user with information on all insurance contracts of the target person desired by the user. Hereinafter, the process will be described with reference to FIGS. In the following description, it is assumed that the WEB server 801 of company A is used because the user desired by the user (or the user himself / herself) is a person who has contracted with the insurance of company A.

  As shown in FIG. 3, first, the user uses the user terminal 803 to access the company A top page screen 900 provided by the company A WEB server 801. Then, the user designates (clicks) the banner 801 of “Insurance Contract My Page” on the screen 900.

  Then, a login screen 910 provided from the WEB server 801 is displayed on the user terminal 803.

  The user inputs login information of the target person such as an ID and a password on the login screen 9110 and presses the login button 911.

  In response to this, the WEB server 801 refers to the customer DB 899 using the input login information, and determines whether there is a target person (personal information) corresponding to the login information. The customer DB 899 is a database that includes a set of personal information and login information of a customer of company A.

  If the result of the determination is affirmative, the subject has been authenticated. In that case, the WEB server 801 transmits information representing the My Page screen 920 to the user terminal 803. My page screen 920 is displayed on user terminal 803. My page screen 920 is a screen of a web page dedicated to the target person corresponding to the login information.

  The My Page screen 920 has a “contract information collection / inquiry” button 921. The user presses a “collection / inquiry of contract information” button 921. That is, the user requests collection and inquiry of the contract information of the target person. In the present embodiment, collection of contract information is performed in batches. For this reason, the process is once completed for the user, and the user waits for information provision later (for example, several minutes, several hours, or several days later).

  When the “contract information collection / inquiry” button 921 is pressed, the WEB server 801 transmits a contract information collection request to the common server 24. The common server 24 receives the contract information collection request and transmits the request to the central server 11. The contract information collection request is a request for collecting information on an insurance contract in which the target person is a contractor, and the request includes identification information of the target person. The identification information (for example, name and date of birth) of the target person is information included in the personal information specified from the customer DB 899 based on the login information, for example.

  The central server 11 receives the contract information collection request from the WEB server 801. At that time, the central server 11 stores, for example, a transaction ID (for example, a serial number assigned to the received collection request) and a status “unsent” for each local system in a storage resource (for example, memory) in the central server 11. The contract information provision request is stored. The status “unsent” means that the contract information provision request has not yet been transmitted to the local system corresponding to the status. The contract information provision request is a request for providing information on an insurance contract in which the target person is a contractor, and has the same identification information as the target person identification information included in the contract information collection request from the WEB server 801.

  As shown in FIG. 4, each common server 24, 34 and 44 checks a predetermined storage area (for example, a folder or a DB) at the time of system startup or periodically, and makes an inquiry request to an insurance company having the common server. Determine the presence or absence. Specifically, for example, each of the common servers 24, 34, and 44 checks the status corresponding to the common server when the system is started or periodically. If the status is “unsent” and there is a contract information provision request, the common server determines that there is an inquiry request. At that time, the common server changes the status from “unsent” to “waiting for reply” and acquires the contract information provision request from the central server 11 (instead of this, the central server 11 The contract information provision request may be transmitted to the common servers 24, 34 and 44 in the systems 20, 30 and 40 via the dedicated network 100).

  In response to the contract information collection request, the common servers 24, 34, and 44 search the common DBs 22, 32, and 42 for insurance contract information having personal information that matches the target person identification information included in the request. The common servers 24, 34, and 44 store the found insurance contract information (contract information in which the contract information based on the specifications of each company is standardized into a standardized data format by the format conversion described above) to the central server 11. Send. The common servers 24, 34 and 44 transmit information indicating no contract information to the central server 11 when the corresponding insurance contract information is not found.

  The central server 11 receives response information (corresponding insurance contract information or information indicating no contract information) from the common servers 24, 34 and 44. The central server 11 temporarily stores the answer information in the management DB 12 and changes the status corresponding to the transmission source local system of the answer information from “waiting for answer” to “answered”. The status may be changed from “waiting for reply” to “answered” by the common server that sent the reply information.

  When the central server 11 detects that all the statuses for a certain transaction ID are “answered”, it creates insurance contract list information based on all the response information corresponding to the transaction ID, The contract list information is stored in the management DB 12. The insurance contract list information is a set of corresponding insurance contract information.

  As shown in FIG. 5, the insurance contract list information stored in the management DB 12 is stored in a DB (neutral engine DB) 601 included in the neutral engine system 805. For example, the central server 11 sends a notification that the insurance contract list information has been generated to the neutral institution system 805, and the neutral institution system 805 requests the insurance contract list information from the central server 11 in response to the notification. Thus, the insurance contract list information is received from the central server 11 and stored in the neutral organization DB 601.

  The neutral engine system 805 transmits an e-mail 621 to the user terminal 803. The e-mail 621 has a URL of a screen (WEB page) for viewing a list of insurance contract information. Note that the address of the e-mail 621 can be an address manually input when the user requests collection and inquiry of the contract information of the target person.

  The user terminal 803 accesses the URL. As a result, the insurance contract list screen 850 is provided and displayed from the neutral institution system 805 on the user terminal 803. The screen 850 displays a list of insurance contract information according to the insurance contract list information stored in the neutral organization DB 601. In the list, for example, the company name or product name of the insurance company is displayed. When the user wants to know details about a desired insurance contract, the user designates the desired insurance contract with respect to the user terminal 803 (for example, clicks on a desired insurance contract line). In that case, more detailed information of the insurance contract is provided and displayed from the neutral backbone system 805 to the user terminal 803. The detailed information is also included in the insurance contract list information in the neutral backbone DB 601.

  As described above, according to the present embodiment, the user can grasp all the insurance contract information with which the target person has contracted. Also, if the contractor's login information is shared with someone other than the contractor (for example, the recipient, the contractor's family), for example, all insurance contracted by the contractor even if the contractor dies. Other people can know. Thus, in the present embodiment, it is possible to prevent “unintentional non-payment” from occurring.

  Further, according to the present embodiment, the insurance contract information collected by the central server 11 is acquired by the neutral engine system 805 and provided to the user terminal 803 from the neutral engine system 805. Thereby, even if collection of insurance contract information is requested via the WEB page of company A, it is possible to prevent the company A from referring to insurance contract information of insurance companies other than company A.

  The embodiment of the present invention described above is an example for explaining the present invention, and is not intended to limit the scope of the present invention only to the embodiment. Those skilled in the art can implement the present invention in various other modes without departing from the spirit of the present invention.

  For example, the local system may not have a common system. In that case, the central system transmits a contract information provision request to the core system, the core system acquires corresponding insurance contract information from the core DB in response to the request, and provides the acquired information to the central system. Can do.

  In addition, for example, instead of the insurance contract information itself, information indicating which insurance company has the insurance contract information (that is, information indicating which insurance company has an insurance contract) is collected in the central system 10, and It may be provided to the user. In this case, the user can know the insurance company that may have an insurance contract for the target person, so contact the insurance company separately to see if the insurance contract exists or is still valid. You may inquire about detailed information.

  Further, for example, a neutral institution system 805 may exist at the back of various insurance companies. Specifically, for example, regardless of the insurance company's My Page (personal WEB page), the neutral organization system 805 accepts the inquiry request, and the neutral organization system 805 (A request for checking the existence of a target person's insurance contract and including a target person's identification information) may be transmitted to the central server 11. In this case, in response to the inquiry request, the central server 11 may investigate the existence of the insurance contract of the target person from a plurality of local systems, and write survey result information representing the result of the survey in the management DB 12. The neutral institution system 805 may acquire survey result information from the management DB 12 and transmit the survey result information to the user terminal 803.

  Further, for example, various insurance companies may exist in the back of the neutral institution system 805. Specifically, for example, the neutral institution system 805 provides the user terminal 803 with a common My Page (personal WEB page) for various insurance companies, and receives an inquiry request via the common My Page. good. In response to the inquiry request, the neutral institution system 805 transmits an inquiry request (a request for checking the existence of the target person's insurance contract and including the target person's identification information) to the central server 11. Good.

10 Central system 11 Central server 20, 30, 40 Local system 801 WEB server 803 User terminal 805 Neutral engine system

Claims (5)

Multiple local systems that are multiple computer systems for multiple insurance companies connected to a dedicated network;
A central system that is a computer system connected to the dedicated network;
Each local system stores the insurance contract information of the insurance company corresponding to the local system, but does not store the insurance contract information of insurance companies other than the insurance company corresponding to the local system,
Communication between each local system and the central system is possible, but communication between local systems is not possible,
In response to the inquiry request for insurance contract information, the central system detects the existence of an insurance contract whose target is the person identified from the inquiry request through the dedicated network. Investigate from multiple local systems, store survey result information representing the results of the survey,
The survey result information stored in the central system is provided to a user terminal which is an information processing terminal used by a user who wishes to inquire for insurance contract information.
Insurance contract research system. The system of claim 1, comprising:
The central system acquires the insurance contract information from the local system having the insurance contract information for which the target person is the contractor as a survey of the existence of the insurance contract,
The survey result information includes contract information of the acquired insurance.
Insurance contract research system. The system of claim 1, comprising:
The survey result information stored in the central system cannot be referenced from any insurance company system.
Insurance contract research system. The system according to claim 3, wherein
The user terminal logs in using login information via a predetermined WEB page and desires to refer to insurance contract information;
In response to the request, the query request is entered into the central system;
The inquiry request includes identification information of the target person,
The identification information of the target person is information specified based on the login information,
The neutral engine system acquires survey result information stored in the central system from the central system, and provides the acquired survey result information to the user terminal.
Insurance contract research system. In response to the insurance contract information inquiry request, the central system is a plurality of local systems, which are a plurality of computer systems for insurance companies, and a target person who is identified from the inquiry request is a contractor. Investigating the existence of an existing insurance contract and storing survey result information representing the results of the survey;
Providing the survey result information stored in the central system to a user terminal that is an information processing terminal used by a user who wishes to inquire for insurance contract information;
The plurality of local systems and the central system are connected to the dedicated network;
Each local system stores insurance contract information of an insurance company corresponding to the local system, but does not store insurance contract information of an insurance company other than the insurance company corresponding to the local system,
Communication between the local system and the central system is possible, but communication between local systems is not possible.
Insurance policy survey method.

Images