JP6810674B2 - Contract management support device and contract management support method - Google Patents

Description

The present invention relates to a contract management support device and a contract management support method. Specifically, the present invention accurately presents the scope of compensation for relatives who are insured of a plurality of insurances and the appropriateness thereof, and as a result, appropriately relates to the insurance. Regarding technology that enables various review proposals.

Nowadays, various uncertainties about the future, such as uncertainty about the future of the lifetime employment system and social security system, and the increase in large-scale natural disasters, have been pointed out. Against this background, people are considering taking out a wide variety of insurance such as life insurance, fire insurance, automobile insurance, medical insurance, accident insurance, etc. as a preparation for future risks, and taking out multiple insurances individually or in households. There are many cases of doing so.

As a conventional technique related to such an insurance contract business, for example, in a contract information presentation method of presenting information about a contract to the customer when renewing a contract related to a service to the customer, the service is a plurality. For each of the requirements that make up the contract, customer contract information that indicates whether or not there was a selection at the time of the previous update, customer request information that indicates whether or not the customer requested at the time of the previous update, A contract record associated with the characteristic information indicating the customer's characteristics is stored in the contract record storage unit, a contract renewal request including the information specifying the contract is received, and a contract corresponding to the specified information is received. By searching the record, giving priority to the requirement indicating that the customer desired information is present in the searched contract record, and adding it to the requirement indicating that the customer contract information is present, the contract information that is a candidate for update is generated. A method of presenting contract information (see Patent Document 1), which comprises outputting the generated contract information and presenting it to the customer, has been proposed.

JP-A-2010-244442

However, when a plurality of individuals or households take out a wide variety of insurances as described above, it is difficult to say that the policyholder has an accurate grasp of the contents of the insurance policy.

In particular, in the case of insurance that covers a wide range of people, such as family-type insurance, there are many cases where the policyholder himself forgets the contract details. In addition, there are cases where the insured cannot recognize the contract details, etc. without being clearly informed that they are covered by the insurance.

In that case, even if an incident corresponding to the reason for insurance claim occurs in the insured, both policyholders are not even aware that it is the trigger for claiming insurance claim, and it is easy to miss the claim for insurance claim. It is in a state that can occur in.

In addition, the above situation is whether or not relatives such as parents and siblings are guaranteed / compensated for what kind of risk by various insurances contracted by someone in the relative, or not. Of course, it is also difficult to accurately grasp insurance coverage, such as whether or not necessary compensation is available. This problem becomes even more difficult as the life stages of each of these relatives change over time, and the above-mentioned criteria for determining the presence or absence of coverage and suitability continue to change.

Therefore, an object of the present invention is to provide a technique capable of accurately presenting the scope of compensation for relatives who are insured of a plurality of insurances and their suitability, and eventually making an appropriate review proposal regarding the insurance.

The contract management support device of the present invention that solves the above problems has identification information that identifies an insured person in each insurance, attribute information, a contractual position, and insured person information that links relationships between insured persons. It is provided with a storage device that stores the above and at least one of the relationships and attributes that conforms to at least one of the insurance coverage and insurance conditions in the contract contents by obtaining information on the contract contents of each insurance from the predetermined device. A process of identifying the insured person based on the insured person information, and a process of storing the specified insured person identification information in a storage device in association with the insured object and the insurance condition in the contract contents. , The insured person is the policyholder based on the insured person information based on the insured person's identification information indicated by the output request after obtaining the output request of the insurance coverage range by the predetermined insured person from the predetermined device. Or other insurance that identifies the insurance linked from the standpoint of the insured and has a relationship with the insured in the insurance linked by the insured from the standpoint of the policyholder in the insured information. The process of identifying the insured person and the identification information of the insured person and the other insured person are collated with the information of the contract contents of each insurance, and the insurance target and the insurance conditions in the contract contents are set. The process of identifying each insurance associated with the identification information and the coverage indicated by the information on the contract details of each of the specified insurances are aggregated for each insured person covered by the insurance, and at least the coverage and its duplication are informationed. It is characterized by including a process of generating and outputting to a predetermined device, and a computing device for executing the process.

In addition, the contract management support method of the present invention stores identification information that identifies the insured person in each insurance, attribute information, a contractual position, and insured person information that links the relationships between the insured persons. An information processing device equipped with a storage device obtains information on the contents of each insurance contract from a predetermined device, and at least one of the relationships and attributes conforming to at least one of the insurance coverage and insurance conditions in the contract contents. The process of identifying the insured person with the above based on the insured person information and the identification information of the specified insured person are stored in the storage device in association with the insured object and the insurance condition in the contract contents. And the output request of the insurance coverage range by the predetermined insured person is obtained from the predetermined device, and based on the identification information of the insured person indicated by the output request, the insured person is used in the insured person information. Identifyes the insurance linked from the standpoint of the policyholder or the insured, and the insured has a relationship with the insured in the insurance linked from the standpoint of the policyholder in the insured information. The process of identifying the other insured person and the identification information of the insured person and the other insured person are collated with the information of the contract contents of each insurance, and the insurance target and the insurance conditions in the contract contents are collated. The process of identifying each insurance to which the identification information is linked to any of them and the coverage indicated by the information of the contract contents of each of the specified insurances are aggregated for each insured person covered by the insurance, and at least the coverage and its coverage. It is characterized by executing a process of generating information about duplication and outputting it to a predetermined device.

According to the present invention, it is possible to accurately present the scope of compensation for relatives who are insured of a plurality of insurances and their suitability, and to make an appropriate review proposal regarding the insurance.

It is a network configuration diagram including the contract management support device in this embodiment. It is a figure which shows the hardware configuration example of the contract management support apparatus of this embodiment. It is a figure which shows the hardware configuration example of the user terminal of this embodiment. It is a figure which shows the data structure example of the insurance product master of this embodiment. It is a figure which shows the data structure example of the risk master of this embodiment. It is a figure which shows the data structure example of the user master of this embodiment. It is a figure which shows the data structure example of the contractor master of this embodiment. It is a figure which shows the data structure example of the insured person master of this embodiment. It is a figure which shows the data structure example of the asset master of this embodiment. It is a figure which shows the data structure example of the contract content master of this embodiment. It is a figure which shows the data structure example of the display setting master of this embodiment. It is a figure which shows the data structure example of the cooperation application master of this embodiment. It is a figure which shows the data structure example of the user use application master of this embodiment. It is a figure which shows the data structure example of the application data DB of this embodiment. It is a figure which shows the data structure example of the event definition master of this embodiment. It is a figure which shows the data structure example of the detection event DB of this embodiment. It is a figure which shows the data structure example of the parameter master of this embodiment. It is a figure which shows the data structure example of the event correspondence risk master of this embodiment. It is a figure which shows the conceptual example of the user registration and the contractor registration of this embodiment. It is a figure which shows the conceptual example of the insured person registration of this embodiment. It is a figure which shows the conceptual example of the asset registration of this embodiment. It is a figure which shows the flow example 1 of the contract management support method in this embodiment. It is a figure which shows the conceptual example of the contract content registration of this embodiment. It is a figure which shows the example of the association concept of the family relation by the relationship of this embodiment. It is a figure which shows the flow example 2 of the contract management support method in this embodiment. It is a figure which shows the flow example 3 of the contract management support method in this embodiment. It is a figure which shows the flow example 4 of the contract management support method in this embodiment. It is a figure which shows the conceptual example of the screen output of this embodiment. It is a figure which shows the flow example 5 of the contract management support method in this embodiment. It is a figure which shows the flow example 6 of the contract management support method in this embodiment. It is a figure which shows the flow example 7 of the contract management support method in this embodiment. It is a figure which shows the conceptual example of the screen output of this embodiment. It is a figure which shows the design concept example 1 of the coverage display screen of this embodiment. It is a figure which shows the design concept example 2 of the coverage display screen of this embodiment. It is a figure which shows the information display concept example of the duplication compensation of this embodiment. It is a figure which shows the flow example 8 of the contract management support method in this embodiment. It is a figure which shows the flow example 9 of the contract management support method in this embodiment. It is a figure which shows the flow example 10 of the contract management support method in this embodiment. It is a figure which shows the flow example 11 of the contract management support method in this embodiment. It is a figure which shows the flow example 12 of the contract management support method in this embodiment. It is a figure which shows the flow example 13 of the contract management support method in this embodiment. It is a figure which shows the conceptual example of the cooperation application recommendation of this embodiment.

--- Network configuration ---

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a network configuration diagram including the contract management support device 100 of the present embodiment. The contract management support device 100 shown in FIG. 1 is a computer device that can accurately present the scope of compensation for relatives who are insured of a plurality of insurances and their suitability, and can also appropriately review and propose the insurance. ..
The contract management support device 100 is connected to the network 10 and is capable of data communication with the user terminal 200 and the insurance company system 300.

Of these, the user terminal 200 is a terminal that can be used by an insurance policyholder who has purchased and contracted insurance sold by an insurance company, or a relative and insured person of this policyholder. Specifically, the user terminal 200 can be assumed to be a smartphone, a tablet terminal having a communication function, a PC, or the like, but the user terminal 200 is not limited thereto.

It also does not limit the types of insurance sold by insurance companies and contracted by policyholders. To give an example of such insurance, various types such as life insurance, fire insurance, automobile insurance, medical insurance, accident insurance, etc. can be assumed.

The insurance company system 300 is a system operated by the above-mentioned insurance company. Specifically, it manages various information related to insurance products sold by the insurance company, and, for example, in response to a request from the contract management support device 100 or the user terminal 200 (of course, the predetermined authentication process has been successfully performed). (Above) A device that distributes the information. Specifically, the insurance company system 300 can be assumed to be a server device, but the insurance company system 300 is not limited to this.
--- Hardware configuration ---

Further, the hardware configuration of the contract management support device 100 in this embodiment is as follows. FIG. 2 shows a hardware configuration example of the contract management support device 100 of this embodiment.

That is, the contract management support device 100 is held in a storage device 101 composed of an appropriate non-volatile storage element such as an SSD (Solid State Drive) or a hard disk drive, a memory 103 composed of a volatile storage element such as a RAM, and a storage device 101. The program 102 is read into the memory 103 and executed to perform overall control of the device itself, and is connected to a computing device 104 such as a CPU that performs various determinations, calculations and control processes, and a network 10 to perform communication processing with other devices. A communication device 105 is provided.

In addition to the program 102 for implementing the functions required as the contract management support device 100 of the present embodiment, the insurance product master 125, the risk master 126, the user master 127, and the contractor master 128 are stored in the storage device 101. , Insured person master 129, asset master 130, contract content master 131, display setting master 132, linked application master 133, user-used application master 134, application data DB 135, event definition master 136, detection event DB 137, parameter master 138, and , The event response risk master 139 is at least stored. Details of these masters and DBs will be described later.

Further, FIG. 3 shows an example of the hardware configuration of the user terminal 200 of the present embodiment. The user terminal 200 of the present embodiment includes a storage device 201 composed of an appropriate non-volatile storage element such as an SSD (Solid State Drive) or a hard disk drive, a memory 203 composed of a volatile storage element such as a RAM, and a storage device 201. The held program 202 is executed by reading it into the memory 203 to perform overall control of the device itself, and the arithmetic device 204 such as the CPU that performs various determinations, calculations, and control processes, and the policyholders and insureds who are users. An input device 205 that accepts key input and voice input, an output device 206 such as a display that displays processing data, a communication device 207 that connects to the network 10 and is responsible for at least communication processing with the contract management support device 100, a GPS unit 208, And a gyro unit 209.

In addition to the program 202 for implementing the functions required as the user terminal 200 of the present embodiment, at least the cooperation application 210 and the application data 225 are stored in the storage device 201.

Of these, the cooperative application 210 is an application for observing events that occur with respect to the policyholder or the insured who possesses the user terminal 200. Specifically, existing so-called life log apps such as a weather app, a step count app, a golf log management app, and a household account book app can be assumed.

Of these, the weather application is an application that acquires weather information in the relevant area from a predetermined information distribution server or the like based on the current position of the user terminal 200 (eg, acquired from the GPS unit 208).

The step count application is an application that counts the steps of policyholders and insured persons based on the data obtained from the gyro unit 209 provided in the user terminal 200.
In addition, the golf log management application is an application for inputting and managing a score or the like when a policyholder or an insured person plays golf.

In addition, the household account book application obtains various information used for household management such as the balance of deposits and savings in bank accounts owned by policyholders and insureds, deposit / withdrawal information, credit card usage information, etc. from predetermined resources. It is an application for managing.

Further, the application data 225 is data obtained by the above-mentioned linked application 210 regarding the corresponding event. In the above example, the data is related to the weather, the number of steps, the golf score, the household budget, and the like. The application data 225 is appropriately collected by the contract management support device 100 of the present embodiment and managed by the application data DB 135.
--- Data structure example ---
Subsequently, the tables used by the contract management support device 100 of the present embodiment will be described. FIG. 4 shows an example of the insurance product master 125 in this embodiment.

The insurance product master 125 in the present embodiment is, for example, distributed from the insurance company system 300 of each insurance company, or a person in charge of each insurance company operates the terminal to access and input the contract management support device 100. This is a table that aggregates and accumulates information on insurance products (the same applies to risk master 126, etc. for such stored information resources).

The data structure uses the insurance product ID that uniquely identifies the insurance product as a key, the insurance company that sells the insurance product, the product name / special contract name such as fixed-term insurance and medical insurance, the insured person and his / her spouse, and assets. It is a collection of records consisting of data such as insurance coverage such as, conditions such as age and relatives, and risk ID indicating the risk covered by the coverage of the insurance product. Of these, the risk ID is common to that of the risk master 126 described later.

Further, FIG. 5 shows an example of data configuration of the risk master 126 of the present embodiment. The risk master 126 in this embodiment is a table accumulating information on risks covered by the coverage of insurance products.

The data structure is a collection of records composed of data such as a target of the risk, a risk label which is a keyword indicating the risk, and the content of the risk, using the risk ID that uniquely identifies the risk as a key.

Further, FIG. 6 shows an example of data configuration of the user master 127 of the present embodiment. The user master 127 in the present embodiment is a table accumulating information on a user who uses the contract management support service provided by the contract management support device 100, that is, an insurance policyholder and an insured person.

The contractor and the insured, such as the user master 127, the policyholder master 128 described later, the insured master 129, the asset master 130, and the contract content master 131, and various masters related to insurance covering them are, for example, contracts. The person or the insured person operates the user terminal 200 to access the contract management support device 100 and stores the input information (the same applies hereinafter).

The data structure is a collection of records composed of data such as a user's name, gender, date of birth, and address, using a user ID that uniquely identifies the user as a key.

Further, FIG. 7 shows an example of data configuration of the contractor master 128 of the present embodiment. The policyholder master 128 in this embodiment is a table that stores information on policyholders of insurance products.

The data structure uses the contractor ID that uniquely identifies the contractor as a key, and the name, gender, date of birth, address, and corresponding user ID of the contractor (the user ID of the contractor, which is described above. It is a collection of records composed of data such as (common to that of the user master 127).

Further, FIG. 8 shows an example of data configuration of the insured master 129 of the present embodiment. The insured person master 129 in the present embodiment is a table in which information on a person who is insured in the insurance product contracted by the policyholder registered in the above-mentioned policyholder master 128 is accumulated.

The data structure shows the name of the insured person, the relationship with the policyholder, the gender, the date of birth, the address, and the status of living with the policyholder, using the insured person ID that uniquely identifies the insured person as a key. Living together flag (example: "1" if living together, "0" if not living together), marriage history flag (example: "1" if married, "0" if single), registered contractor ID, and corresponding user ID, It is a collection of records consisting of such data.

Further, FIG. 9 shows an example of data configuration of the asset master 130 of the present embodiment. The asset master 130 in this embodiment is a table accumulating information on assets covered by insurance by the above-mentioned policyholder.

The data structure is a collection of records composed of data such as the type, name, location, and registered contractor ID of the asset, using the asset ID that uniquely identifies the asset as a key.

Further, FIG. 10 shows an example of data configuration of the contract content master 131 of the present embodiment. The contract content master 131 in the present embodiment is a table in which information on the contract content of the insurance product contracted by the above-mentioned policyholder is accumulated.

The data structure is based on the insurance product ID of the target insurance product, the policyholder ID of the policyholder, and the insured person in the contract, using the policy number of the insurance policy that uniquely identifies the relevant contract as a key. It is a collection of records consisting of data such as insurer ID, insurance coverage, conditions, risks, and public flags.

Of these, the "insurance target" column includes a certificate column as opposed to the insured ID and asset ID setting column. This certificate column is a column in which items to be described regarding the insurance coverage in the certificate of the relevant insurance policy are set. That is, the insured person ID or asset ID and the items described in the certificate are linked. This configuration is the same for the "conditions" column, and the insured ID of the insured who meets this condition is set for the "certificate" column where the items to be described in the certificate are set as the conditions for insurance application. It has a structure that corresponds to the column.

Further, FIG. 11 shows an example of data configuration of the display setting master 132 of the present embodiment. The display setting master 132 in the present embodiment is a table that defines information on the insured person and the risk of not displaying the compensation range of the asset in the screen output described later.
The data structure is a collection of records composed of data such as a target insured person ID and an asset ID as a key and a risk of hiding.

Further, FIG. 12 shows an example of data configuration of the linked application master 133 of the present embodiment. The linked application master 133 in this embodiment stores information on an application that provides data (related to an event that occurs to a contractor or an insured person) that can be used for processing the contract management support device 100 of this embodiment. It is a table. This application is a linked application 210. Therefore, specifically, it can be said that it is a list of applications that can be installed on the user terminal 200.

The data structure is a collection of records composed of data such as the application name and data type of the linked application 210, using the application ID that uniquely identifies the linked application 210 as a key. In the example of FIG. 12, a data structure in which a plurality of data types can be set is used. For example, as data provided by the "Tell me weather" app regarding weather events, for each event such as "area" where rainfall or lightning strikes occur, "precipitation amount" corresponding to the scale, and "lightning strike" that accompanies it. Data is assumed to be included.

Further, FIG. 13 shows an example of data configuration of the user-used application master 134 of the present embodiment. The user-used application master 134 in the present embodiment is a table in which information on the linked application 210 installed and used by each user such as a contractor or an insured person on the user terminal 200 is stored.

The data structure is an application that is an application ID of the cooperation application 210 used by the user and a login ID when using the cooperation application 210, using a user ID that uniquely identifies the policyholder or the insured as a key. It is a collection of records consisting of data such as a user ID and an application password used at login.

Further, FIG. 14 shows a data configuration example of the application data DB 135 of the present embodiment. The application data DB 135 in the present embodiment is a database that stores application data 225 held by the linked application 210 of each user terminal 200 with respect to the corresponding event.

The data structure is a collection of records composed of data such as the application ID of the linked application 210 and the application data, using the date of data acquisition and the user ID as keys. Of these, the application data naturally includes data corresponding to each event in the data type column specified in the linked application master 133.

Further, FIG. 15 shows an example of data configuration of the event definition master 136 of the present embodiment. The event definition master 136 in the present embodiment is a table that stores information on events that may occur to the policyholder and the insured.

The data structure is a collection of records consisting of data such as an event name, support type, usage data, and definition, using an event ID that uniquely identifies the event as a key.

Of these, the type of support is the type of proposal that should be made regarding insurance products to policyholders and insured persons who were the source of the event or were located near the place of occurrence when the event occurred. It is a specified value. Examples of this type of support include "claims" that encourage insurance claims, "subscription" that encourages new insurance product contract reviews, "subscription, review" that encourages new insurance product contract reviews and reviews of existing contracts. Can be assumed.
Further, the usage data corresponds to the value specified in the data type column of the linked application master 133.

In addition, the definition sets the conditions for determining whether or not to accept the proposal set in the support type column. For example, when the application data related to the weather event is obtained from the weather cooperation application 210 of the user terminal 200, the contract management support device 100 sets the location of the property of the contractor who is the user of the user terminal 200 to the weather event. If "lightning" is obtained as a value related to the event of the weather event, it is determined that the event name "lightning to the neighborhood" has occurred, and the user terminal 200 of the contractor concerned. In response to this, a support type "claim", that is, a notification prompting an insurance claim, etc. will be delivered.

Further, FIG. 16 shows an example of data configuration of the detection event DB 137 of the present embodiment. The detection event DB 137 in the present embodiment is a user related to the event when the contract management support device 100 collates the stored data of the application data DB 135 with each record of the event definition master 136 and detects the occurrence of the event. It is a database that stores information about policyholders and insured persons.

The data structure is data such as the event ID of the event and the support type determined to be performed for the user when the event is detected, using the date when the event was detected and the user ID of the user related to the event as a key. It is a collection of records consisting of.

Further, FIG. 17 shows an example of data configuration of the parameter master 138 of the present embodiment. The parameter master 138 in the present embodiment is a table in which the specified values for each user are accumulated with respect to the numerical values, that is, the parameters among the conditions specified in the definition column of the event definition master 136 described above.
The data structure is a collection of records composed of data such as a target user and a value, using the above-mentioned parameter (example: XX) as a key.

Further, FIG. 18 shows an example of data configuration of the event response risk master 139 of the present embodiment. The event response risk master 139 in this embodiment is a table in which information on risks associated with the above-mentioned events is accumulated.

The data structure is a collection of records composed of data such as a risk label and an event ID, using a risk ID (common with the risk master 126) that uniquely identifies a risk as a key. In the example of FIG. 18, for example, the risk ID “R20112” is a risk related to the risk label “building lightning strike”, and the event IDs of the events that can cause this are defined as “EV0001” and “EV0002”. There is. According to the event definition master 136, this "EV0001" is a "lightning strike to the neighborhood" event, and "EV0002" is a "frequent lightning strike to the neighborhood" event. That is, "R20112" is defined as a risk associated with "lightning strike".
--- Concept of user registration and contractor registration ---

FIG. 19 is a diagram showing a conceptual example of user registration and contractor registration according to this embodiment. Here, first, the concept of user registration and contractor registration will be outlined. The content shown here corresponds to the content that is the preprocessing of the contract management support method executed by the contract management support device 100 of the present embodiment.

In this case, for example, a contractor who has purchased some insurance product operates the user terminal 200 and registers his / her own information in the contract management support device 100. At this time, the contractor downloads the application distributed by the contract management support device 100 on the network 10 by launching an appropriate browser on the user terminal 200, and installs the application on the user terminal 200.

This application is an application that can serve as an interface for a contract management support service provided by the contract management support device 100 by executing a contract management support method. Therefore, the contractor starts this application on the user terminal 200, and inputs information such as a name, a gender, a date of birth, and an address according to the user registration items requested by the application.

On the other hand, the contract management support device 100 receives the above input from the user terminal 200, assigns a user ID to the contractor, and stores a record using this as a key in the user master 127. The record will include information such as name, gender, date of birth, and address acquired via the above-mentioned application.

Further, as described above, the target of user registration this time is an insurance policyholder. Therefore, the application displays a question about the attributes of such a user and identifies whether the registration target is a contractor or an insured person. The contract management support device 100 obtains this specific result from the user terminal 200, and based on the fact that the registration target is the "contractor", the contractor master 128 generates a record including the contractor ID for the contractor. , The same value as the value registered in the user master 127 is associated with this, and the user ID of the contractor is further set. As a result, the contractor ID and the user ID are associated with each other. That is, the contractor is also a user, and has both a user ID and a contractor ID.
--- Concept of insured registration ---

FIG. 20 is a diagram showing a conceptual example of insured person registration according to the present embodiment. Next, the concept of insured registration will be explained. Unlike the above case, when the target of user registration is not the policyholder but the insured person, the above-mentioned policyholder is the name, gender, and date of birth of the relatives who were insured in the insurance product contracted by him / her. , Address, etc. are input in the application of the user terminal 200 in the same manner as described above. However, in the case of insured person registration, the relationship with the policyholder, the status of living together, and the marriage history of the insured person are also entered.

Of course, the policyholder can be insured, that is, insured. Therefore, from now on, unless otherwise specified, the explanation will be given on the premise that the insured can include a policyholder.

The contract management support device 100 stores the above-mentioned insured person information received from the user terminal 200 in a record newly generated for the insured person by the insured person master 129. In the "Registered contractor ID" column in the record of the insured master 129, the contractor ID of the contractor who registered the insured person (example: the one obtained by the application at the time of login and contracted). The one set in the person master 128) is set.

Further, the contract management support device 100 sets the user ID of the insured person specified by the above-mentioned contractor in the user master 127 in the "corresponding user ID" column of the above-mentioned records.
--- Concept of asset registration ---

FIG. 21 is a diagram showing a conceptual example of asset registration according to the present embodiment. Next, the concept of asset registration will be explained. When the insurance target of the insurance product is an asset rather than a person, the above-mentioned policyholder registers the information in the contract management support device 100.

In that case, the policyholder operates the user terminal 200 and inputs information on the assets covered by the insurance product under contract among his / her own assets in response to the above-mentioned application question or the like. The information to be input includes the type of asset such as a building or an automobile, the name of the asset such as a specific vehicle type name, and its location.

On the other hand, the contract management support device 100 acquires information on such assets from the user terminal 200, assigns an asset ID to each asset, generates a record, and stores this in the asset master 130. At this time, in the "registered contractor ID" field, the contractor ID of the above-mentioned contractor shall be read from the contractor master 128 and set.
--- Flow example 1 ---

Hereinafter, the actual procedure of the contract management support method in the present embodiment will be described with reference to the figure. Various operations corresponding to the contract management support method described below are realized by a program read by the contract management support device 100 into a memory or the like and executed. The program is composed of code for performing various operations described below.

FIG. 22 is a diagram showing a flow example 1 of the contract management support method in the present embodiment. Here, the flow in which the contract management support device 100 acquires necessary information from the insurance company system 300 regarding the insurance product under contract by the above-mentioned contractor and performs a predetermined process will be described.

In this case, the user terminal 200 receives input of its own name, contractor ID, and securities number of the insurance product from the above-mentioned contractor, and notifies the contract management support device 100 of the contract content inquiry request including the input. It shall be.
On the other hand, the contract management support device 100 receives the above notification and transmits a request for acquisition of the contract content including the information included in the notification to the insurance company system 300 (s1).

In response to this acquisition request, the insurance company system 300 confirms the existence of the relevant securities number and the life or death of the contract with a predetermined contract management branch system or the like, and if the securities number does not exist or the contract has been terminated. (That is, there is no valid contract and the contract content is not answered), and the contract management support device 100 is notified that the contract content cannot be answered. On the other hand, as a result of this confirmation, if the securities number exists and the contract is still in existence (that is, a valid contract exists and the contract details can be answered), the insurance company system 300 provides information on the contract details. Is returned to the contract management support device 100.
When the contract management support device 100 receives the notification that the above-mentioned valid contract does not exist, the contract management support device 100 replies to the above-mentioned user terminal 200 that registration is not possible, and ends the process.
On the other hand, when the contract management support device 100 obtains the contract content information from the insurance company system 300, the contract management support device 100 stores the contract content information in the contract content master 131 (s2) and ends the process.

As shown again in FIG. 23, the contract content information stored here is a value such as a securities number, an insurance product ID, a policyholder ID, an insured person ID, an insurance target, conditions, risks, and a public flag. Will be included.

In addition, when the contract management support device 100 stores such information in the contract content master 131, a certificate such as insurance coverage (example: insured person, spouse, cohabiting relatives) and conditions (example: 26 years old or older cohabiting relatives) The insured person ID of the corresponding insured person is specified, and this is linked and set.

In this case, the contract management support device 100 identifies an insured person having at least one of the relations and attributes suitable for the above-mentioned insurance coverage and conditions in the insured person master 129. In the example of FIG. 23, the relative of the policyholder ID “CONT011” corresponding to the “insured person, spouse, relatives living together, unmarried child living separately” which is the “insurance target” in the insurance contract with the securities number “IPNE1001”. Can be identified as "FML011" (this is the contractor himself), "FML012", and "FML013" from the insured master 129.

Similarly, the asset of the contractor ID "CONT011", which corresponds to the attribute of "high-class bonsai" (which is an asset), which is the "insurance target", can be specified as "PRP003" from the asset master 130.

Further, the contract management support device 100 sets the insured person ID of the insured person and the asset ID of the asset specified as described above to the "insurance target" and "condition" columns in the corresponding record of the contract content master 131. Store it in association with the "Certificate" column.

The contract management support device 100 sets the value of the risk ID obtained from the insurance product master 125 in the risk column of the contract content master 131 based on the value of the insurance product ID of the contract content master 131. That is, the ID of the risk covered by the coverage of the insurance product is set.

The contract management support device 100 is a person who is not the insured person directly registered by the contractor in the insured person master 129 thus generated, but a person who is a relative of the contractor can also be specified.

As shown in FIG. 24, the insured persons registered by the contractor "Taro" are only the spouse "Kiku" and the child "Hanako". However, of these, "Hanako" is also the spouse of "Gorrow," a policyholder for other insurance products. There is a child "Taichi" between this "Gorrow" and "Hanako", and this "Taichi" is a relationship of "children", that is, "grandchildren" from the above-mentioned contractor "Taro". The contract management support device 100 performs a process of tracing the relationship with the insured master 129 in this way, so that the relatives having the relationship and attributes of the contents specified by the insurance coverage and conditions of the contract content master 131 can be accurately identified. It is possible to specify to.
--- Flow example 2-7 ---

Next, the process of outputting the insurance coverage and its duplication will be described. FIG. 25 is a diagram showing a flow example 2 of the contract management support method in the present embodiment, and FIG. 26 is a diagram showing a flow example 3 of the contract management support display in the present embodiment.

In this case, the contract management support device 100 delivers, for example, a screen such as screen 2500 (FIG. 25) to the user terminal 200 operated by the contractor via the above-mentioned application, and the confirmation button on the screen is displayed. In response to the pressing, the compensation status display request is received (s10). This display request includes at least the user ID that the contractor entered when logging in to the application.

Further, the contract management support device 100 searches the insured person master 129 using the user ID included in the above-mentioned display request as a key, and identifies the corresponding record, that is, the insured person as a display candidate (s11). In the example of the insured master 129 illustrated in FIG. 26, the user ID "USER011" included in the display request is the "principal", that is, the contractor in the "relationship", and the value of the "registered contractor ID" is ""CONT011". Therefore, the contract management support device 100 identifies the corresponding user IDs "USER011", "USER012", and "USER002" from the series of records in which the value "CONT011" of the "registered contractor ID" is set. The insured person ID (FML011, FML012, FML013) is extracted from the corresponding record.

Further, the contract management support device 100 searches with the insured person master 129 using the value of the corresponding user ID specified here as a key, and identifies a person registered as an insured person by another contractor. The insured person ID is also extracted. In the example of FIG. 26, it is specified that "USER002" is registered as an insured person in "CONT001", and the insured person ID "FML002" can be extracted.

Further, the contract management support device 100 executes a search in the contract content master 131 (FIG. 27) using the insured person ID extracted by the above method as a key, and identifies a record including the insured person ID. Further, the contract management support device 100 reads at least each value of "insurance target", "condition", and "risk" from the record specified here, and sets this in a predetermined display screen form. Screen data is generated, distributed to the user terminal 200 and displayed (s12).
FIG. 28 shows an example of the screen 2800 that the contract management support device 100 distributes and displays to the user terminal 200.

As shown here, the contract management support device 100 identifies the insured person and the asset from the insured person master 129 and the asset master 130 based on the value of "insurance target", and a design concept of a predetermined screen configuration. Based on (Fig. 33), the insured person's value (example: name) is set in the individual compensation column 2801 of screen 2800, and the asset value (example: asset name) is set in the asset compensation column 2802 of screen 2800. Set to.

Further, the contract management support device 100 acquires the value of the risk label from the risk master 126 based on the value in the “risk” column of the contract content master 131, sets this as a predetermined display object, and responds to each of them. Place it in the personal compensation column 2801 or the asset compensation column 2802. In the example of FIG. 28, the risk label value is set and arranged on the rectangular icon as the display object.

As shown in the screen design concept of FIG. 33, the contract management support device 100 has the above-mentioned risk label defined by the risk master 126 in addition to the rectangular icon arranged by setting the value of the risk label. As described above, all items that are not specified based on the value in the risk column of the contract content master 131 are set to rectangular icons and arranged in the same manner.

However, the display form of the rectangular icon arranged in this way shall be set so as to visually clearly indicate that it is not within the compensation range, such as graying out or making the border of the rectangular icon a broken line. As illustrated in FIG. 34, the contract management support device 100 does not display the corresponding rectangular icon with respect to the risk of hiding the insured person specified in the display setting master 132.

Further, the contract management support device 100 further displays the rectangular icons arranged in this way, such as those derived from a plurality of insurance products, that is, those having overlapping coverages, such as thickening the border. It shall be different from the rectangular icon of.

When the contract management support device 100 acquires the value of the risk label from the risk master 126 based on the value in the “risk” column of the contract content master 131 described above, if the same risk label is acquired more than once, the contract management support device 100 compensates for the corresponding risk. It can be identified that the range overlaps.

Further, the contract management support device 100 sends an appropriate message (eg, held in advance in the storage device 101) to the interface such as a balloon for the rectangular icon of the risk that the coverage overlaps in this way. Execute display processing such as setting and attaching.

Even in cases where the coverage overlaps, the meaning may differ. Some types of insurance products do not allow duplicate claims with other insurance products if one policyholder has purchased other insurance products for the same coverage. Of course, there are some that allow duplicate insurance claims.

Therefore, as shown in FIG. 35, the contract management support device 100 refers to the insurance product master 125 for the insurance product corresponding to the risk of overlapping insurance claims, extracts the information on whether or not the insurance claims can be duplicated, and extracts the information. It is preferable to include it in the above message.

In addition, unlike the above example, when the insured person (not the contractor) has made the display request, the processing in the contract management support device 100 and its concept are shown in FIGS. 29 to 32. It will be shown.

The difference from the case where the subject of the display request is the contractor is that the insured person is set in the "insurance target" column of the contract content master 131 in the individual compensation column 2801, and the public flag is "1". (That is, only the risk in the "risk" column of the record that is open to the insured is displayed, and in the asset compensation column 2802, the insurance product is the target of the asset. , A record in which a contractor within a predetermined range for the insured person (example: within the third degree in the relationship) is set in the "contractor ID" field of the contract content master 131, and the public flag is "1". The point is that only the display target is displayed.

For example, if the user who made the display request is an insured person with the insured person ID "FML002", the contract management support device 100 puts this in the "insurance target" column as shown in FIG. The included risks "R103", "R104", "R1300" and the like can be identified. As for the compensation of assets, the compensation of home and automobile is displayed, and the compensation of high-class bonsai whose public flag is "0" is not displayed. Then, as shown in FIG. 32, a rectangular icon in which the value of the risk label corresponding to such a risk is set is arranged on the screen 3200, and is distributed and displayed on the user terminal 200 of the insured person “FML002”.
--- Flow example 8 to 13 ---

Subsequently, a process to be performed in response to obtaining application data from the linked application 210 installed on the user terminal 200, that is, in response to the occurrence of an event will be described. FIGS. 36 to 41 are diagrams showing flow examples 8 to 13 of the contract management support method in the present embodiment.
Here, it is assumed that the application data detected by the linked application 210 is acquired from the user terminal 200 of the user ID "USER011".

In this case, the contract management support device 100 refers to the user-used application master 134, acquires each value of the application ID, the application user ID, and the application password from the record of the predetermined user ID, and the application data including the values. Is transmitted to the user terminal 200 of the user, and the application data 225 is acquired (s20). The contract management support device 100 stores the acquired application data 225 in the application data DB 135.

Subsequently, the contract management support device 100 collates the application data 225 obtained in s20 with the event definition master 136, and identifies the corresponding event (s21). In the case of the example of FIG. 37, by collating the value indicated by the application data 225, for example, the application data "area: Setagaya-ku, precipitation: 50 mm, lightning strike: present" of the application "AP0001" with the event definition master 136. , Specify the record of the event "EV0001" including the value of "Region, Lightning Strike" in the "Usage Data" column. Further, the contract management support device 100 reads the value of "region = asset location, lightning strike = present" from the "definition" column of this record.

Further, the contract management support device 100 searches the contractor master 128 for the user ID "USER011" of the corresponding application data, and identifies the contractor ID "CONT011". In addition, using this contractor ID "CONT011" as a key, the asset master 130 is searched, the value of the location of the asset insured by the contractor is referred to, and this is the "region: Setagaya-ku" indicated by the application data 225. Is determined. In this case, the two match.

Therefore, the contract management support device 100 in the above case specifies the event "EV0001" that satisfies the "usage data" and the "definition" in the event definition master 136. The contract management support device 100 stores the information of the specified event "EV0001" (including the specified user ID, the support type that can be acquired from the corresponding record of the event definition master 136, etc.) in the detection event DB 137.

Subsequently, the contract management support device 100, based on the user ID "USER011" among the information stored in the detection event DB 137, has the compensation range and its compensation range as in the above-mentioned flow examples 2 to 4 (FIGS. 25 to 28). Data on the screen 3800 on which display objects are arranged is configured with respect to duplication, and this is distributed to the user terminal 200 and displayed (s22).
Further, the contract management support device 100 determines whether the value of the support type obtained in s21 is any of "billing", "subscription", and "review" (s23).

As a result of this determination, when the support type is "billing" (s23: billing), the contract management support device 100 determines whether the risk of the corresponding event is within the compensation range (corresponding record of the contract content master 131). If the corresponding risk value exists in (s24: Y), a message 3910 (FIG. 39) suggesting the possibility of insurance claim is sent to the user terminal 200 (s25). End the process.

On the other hand, as a result of the above determination, when the support type is "subscribe" (s23: subscription), the contract management support device 100 determines whether the risk of the corresponding event is within the compensation range (contract content master 131). If the value of the corresponding risk exists in the corresponding record of (s26: N), the insurance product that covers the corresponding risk (specified by the insurance product master 125 using the risk ID as a key) The recommendation information 4010 (FIG. 40) of the above is transmitted to the user terminal 200 (s27), and the process ends.

Further, as a result of the above determination, when the support type is "review" (s23: review), the contract management support device 100 determines whether the risk of the corresponding event is within the compensation range (contract content master 131). If the corresponding risk value exists in the corresponding record of (s28: Y), a message 4110 (FIG. 41) proposing an insurance review is sent to the user terminal 200 (s29). End the process.

In addition, other than the case where the contract management support device 100 can acquire the application data for appropriately detecting the event from the user terminal 200 as described above, that is, the case where the appropriate cooperation application 210 is not installed on the user terminal 200. Can also exist.

In order to deal with such a case, the contract management support device 100 refers to the insured person's record defined in the insured person master 129 as shown in the conceptual example of FIG. 42, and refers to the insured person's insured person. The insurer ID is acquired, and using this as a key, the risk ID in the "risk" column of the record in which the insured person is "insured" in the contract content master 131 is acquired. That is, the risk ID of the risk covered by the compensation is specified.

Subsequently, the contract management support device 100 executes a search in the event definition master 136 using the above-mentioned risk ID as a key, and extracts the value in the "usage data" column in the corresponding event from the record including the risk ID.

Further, the contract management support device 100 searches the linked application master 133 using the value in the "usage data" column extracted here as a key, and the value in the "data type" column is the value in the above-mentioned "usage data" column. Identify records that match. The contract management support device 100 refers to the application ID in this record, and determines whether or not the application ID is included in the record of the corresponding user in the user-used application master 134. As a result of this determination, when the application ID is not included in the record of the corresponding user in the user-used application master 134, the contract management support device 100 holds the linked application 210 of the application ID in the user terminal 200. A predetermined message 4200 (FIG. 42) recommending the use of the corresponding linked application 210 is transmitted to the user terminal 200 of the corresponding user, and the process is terminated.

As another form, the contract management support device 100 extracts the event ID of the relevant event from the record including the risk ID specified in the event definition master 136 described above, and includes the event ID in the record. It may be determined whether the data exists in the application data DB 135 for the insured person. In that case, if the application data does not exist, it is determined that the corresponding linked application 210 is not installed on the user terminal 200, and the predetermined message 4200 recommending the use of the linked application 210 (as described above). FIG. 42) is transmitted to the user terminal 200 of the corresponding user.

Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications can be made without departing from the gist thereof.

According to the present embodiment, it is possible to accurately present the coverage and suitability of the relatives who are the insured of a plurality of insurances, and to make an appropriate review proposal regarding the insurance.

The description herein reveals at least the following: That is, in the contract management support device of the present embodiment, the storage device, as the insured person information, includes the first identification information for identifying the insured person in each insurance, the attribute information, the contractual position, and the insured. The relationship between the persons and the second identification information that uniquely identifies the insured person across the insurances are stored in association with each other, and the arithmetic unit determines the information of the contract contents of each insurance. A process of identifying an insured person who has at least one of the relationships and attributes obtained from the device and conforms to at least one of the insurance coverage and insurance conditions in the contract contents based on the insured person information. The process of holding the first identification information of the specified insured person in the storage device in association with the insurance target and the insurance conditions in the contract contents, and the output request of the insurance coverage range by the predetermined insured person. Based on the second identification information of the insured person indicated by the output request obtained from the predetermined device, the insured person is associated with the insured person from the standpoint of the policyholder or the insured person in the insured person information. The first identification information of the insured person is specified, and the insured person is linked to the insured person from the standpoint of the policyholder in the insured person information, and other insured persons having a relationship with the insured person. The process of identifying the first identification information of the person and the first identification information of the insured person and the other insured person are collated with the information of the contract contents of each insurance, and the insurance target and the insurance target in the contract contents are collated. The process of specifying each insurance to which the first identification information is linked to any of the insurance conditions and the coverage indicated by the information of the contract contents of each specified insurance are aggregated for each insured person covered by the insurance, and at least. The process of generating information about the compensation range and its duplication and outputting it to a predetermined device may be executed.

According to this, the user ID (second identification information) registered in advance for the insured person and the insured person ID (first identification information) that identifies the insured person for each insured insurance are used. It can be used as appropriate to improve the efficiency of various processes. As a result, it is possible to efficiently and accurately present the coverage and suitability of the relatives who are the insured of multiple insurances, and to efficiently make appropriate review proposals regarding the insurance.

Further, in the contract management support device of the present embodiment, when the arithmetic unit generates information about the compensation range and its overlap, the insured object for displaying each of the default compensation ranges defined in advance is insured. In addition to arranging each person, different display forms are set for the coverage indicated by the information on the contract contents of each of the specified insurances and other display objects, and the duplication occurs. A different display form may be set for the one corresponding to the compensation range, and the display form may be output to the predetermined device.

According to this, it becomes possible to present the excess or deficiency and duplication of insurance coverage to the insured and the like in a visually clear form. As a result, it is possible to more accurately present the coverage and suitability of the relatives who are the insured of multiple insurances, and to make appropriate review proposals regarding the insurance.

Further, in the contract management support device of the present embodiment, when the arithmetic unit generates information about the compensation range and its overlap, the display object corresponding to the compensation range in which the overlap occurs is covered by the corresponding insurance. Information regarding the possibility of duplicate billing may be set and output to the predetermined device.

According to this, it is possible to clearly present to the insured whether the above-mentioned duplication of coverage is a meaningful duplication that allows duplication claims or a meaningless duplication that cannot be duplicated. .. As a result, it is possible to more accurately present the coverage and suitability of the relatives who are the insured of multiple insurances, and to make appropriate review proposals regarding the insurance.

Further, in the contract management support device of the present embodiment, the storage device is accompanied by information on the insured person or an event occurring in the surrounding environment obtained from the terminal possessed by the insured person, and the event and the event. It further stores information that defines the correspondence with insurance whose coverage is risk, and the calculation device indicates that the information of the event matches a predetermined definition defined in advance. In the case, the process of collating the information of the event with the information for which the correspondence is determined to specify the insurance whose coverage is the risk associated with the event, and the insured person of the specified insurance. If the insured person is the insured person of the specified insurance as a result of the determination, the information proposing the execution of the insurance claim is output to the predetermined device, and the insured person information is output. As a result of the determination, if the insured person is not the insured person of the specified insurance, the information proposing to take out the insurance is output to a predetermined device, and as a result of the determination, the insured person is the specified person. If you are an insured person of the insurance and the information of the event meets the predetermined conditions set in advance, the process of outputting the information proposing a review of the contract contents of the insurance to the predetermined device is further executed. It may be something to do.

According to this, it becomes possible to make an accurate proposal regarding an insurance contract according to the risk of various events that occur regarding the insured. As a result, it is possible to accurately present the coverage and suitability of the relatives who are the insured of multiple insurances, and to make appropriate revision proposals regarding the insurance.

Further, in the contract management support device of the present embodiment, the calculation device performs an event corresponding to the insurance coverage range associated with the insured person among the insured persons specified in the insured person information. The person who is specified by the correspondence information and the information of the specified event is not held in the storage device or the person who does not hold the application for acquiring the information of the event in the terminal is specified by a predetermined algorithm. However, the process of outputting the information of the usage proposal of the application to the terminal of the insured person may be further executed.

According to this, it is possible to secure an appropriate coverage range according to the characteristics of each insured person and the environment in which the insured person is placed, and to avoid risks by that, accurately and quickly. As a result, it is possible to present the coverage and suitability of the relatives who are insured of multiple insurances more accurately and promptly, and to make more appropriate review proposals regarding the insurance.

Further, in the contract management support method of the present embodiment, the information processing device, as the insured person information in the storage device, first identification information for identifying the insured person in each insurance, attribute information, and contractually The position, the relationship between the insured persons, and the second identification information that uniquely identifies the insured person across the insurances are stored in association with each other, and the information on the contract contents of each insurance is stored from the predetermined device. Obtained, the process of identifying an insured person having at least one of the relationship and the attribute conforming to at least one of the insurance coverage and the insurance conditions in the contract contents based on the insured person information, and the above-mentioned identification. A process of holding the first identification information of the insured person in the storage device in association with the insurance target and the insurance condition in the contract contents, and a predetermined device for outputting a request for output of the insurance coverage range by the predetermined insured person. Obtained from the above, based on the second identification information of the insured person indicated by the output request, the insured person is associated with the insured person from the standpoint of the policyholder or the insured person in the insured person information. The first identification information of the insured person is specified, and the insured person has a relationship with the insured person in the insurance linked with the insured person from the standpoint of the policyholder in the insured person information. The process of specifying the first identification information and the first identification information of the insured person and the other insured person are collated with the information of the contract contents of each insurance, and the insurance target and the insurance conditions in the contract contents are collated. The process of identifying each insurance to which the first identification information is linked to any of the above and the coverage indicated by the information on the contract details of each of the specified insurances are aggregated for each insured person covered by the insurance, and at least the coverage range. And the process of generating information about the duplication and outputting it to a predetermined device may be executed.

Further, in the contract management support method of the present embodiment, when the information processing device generates information about the compensation range and its overlap, a predetermined display object of each default compensation range is covered by the insurance. In addition to arranging for each insurer, among the display objects, different display forms are set for the coverage range indicated by the information on the contract contents of each specified insurance and other items, and the duplication occurs. A different display form may be set for the one corresponding to the compensation range, and the output may be output to the predetermined device.

Further, in the contract management support method of the present embodiment, when the information processing device generates information about the compensation range and its duplication, the corresponding insurance is provided for the display object corresponding to the compensation range in which the duplication occurs. Information regarding the possibility of duplicate billing in the above may be set and output to the predetermined device.

Further, in the contract management support method of the present embodiment, the information processing device includes information on an event occurring in the insured person or the surrounding environment obtained from the terminal possessed by the insured person in the storage device. , Information that defines the correspondence between the event and insurance that covers the risk associated with the event, and the information that defines the correspondence between the event and the insurance, and indicates that the information of the event matches the predetermined definition. The process of collating the information of the event with the information for which the correspondence is defined to specify the insurance whose coverage covers the risk associated with the event, and whether the insured person is the insured person of the specified insurance. When the insured person is determined based on the insured person information and the insured person is the insured person of the specified insurance as a result of the determination, the information proposing the execution of the insurance claim is output to the predetermined device, and the determination is made. As a result, when the insured person is not the insured person of the specified insurance, the information proposing to take out the insurance is output to a predetermined device, and as a result of the determination, the insured person has the specified insurance. If the insured person is insured and the information of the event satisfies a predetermined predetermined condition, the process of outputting the information proposing a review of the contract contents of the insurance to the predetermined device is further executed. May be good.

Further, in the contract management support method of the present embodiment, the information processing device corresponds to the insurance coverage range associated with the insured person among the insured persons specified in the insured person information. Is specified by the correspondence information, and a person whose storage device does not hold the information of the specified event or a person who does not hold an application for acquiring the information of the event in the terminal is determined by a predetermined algorithm. It may be specified, and the process of outputting the information of the usage proposal of the application to the terminal of the insured person may be further executed.

10 Network 100 Contract management support device 101 Storage device 102 Program 103 Memory 104 Arithmetic device 105 Communication device 125 Insurance product master 126 Risk master 127 User master 128 Contractor master 129 Insured master 130 Asset master 131 Contract content master 132 Display setting master 133 Linked App Master 134 User-Used App Master 135 App Data DB
136 Event definition master 137 Detection event DB
138 Parameter Master 139 Event Response Risk Master 200 User Terminal 201 Storage Device 202 Program 203 Memory 204 Arithmetic Logic Unit 205 Input Device 206 Output Device 207 Communication Device 208 GPS Unit 209 Gyro Unit 210 Linked App 225 App Data 225
300 insurance company system

Claims (12)

A storage device that stores identification information that identifies the insured person in each insurance, attribute information, contractual position, and insured person information that links the relationships between the insured persons.
The insured person who obtains the information of the contract contents of each insurance from a predetermined device and has at least one of the relationship and the attribute conforming to at least one of the insurance coverage and the insurance conditions in the contract contents is insured. The process of specifying based on the insurer information, the process of holding the identified insured person's identification information in the storage device in association with the insurance target and the insurance conditions in the contract contents, and the predetermined insured person. An output request for the coverage of insurance is obtained from a predetermined device, and based on the identification information of the insured person indicated by the output request, the insured person is in the position of a policyholder or an insured person based on the insured person information. Processing to identify the linked insurance and identify other insured persons who have a relationship with the insured person in the insurance linked by the insured person from the standpoint of the policyholder in the insured person information. The identification information of the insured person and the other insured person is collated with the information of the contract contents of each insurance, and the identification information is linked to either the insurance target or the insurance conditions in the contract contents. The process of identifying each insurance and the coverage indicated by the information on the contract details of each of the specified insurances are aggregated for each insured person covered by the insurance, and at least information on the coverage and its duplication is generated in a predetermined device. The processing to output, the arithmetic unit to execute, and
A contract management support device characterized by including. The storage device is
As the insured person information, the first identification information for identifying the insured person in each insurance, the attribute information, the contractual position, the relationship between the insured persons, and the insured person are unique across the insurances. It is stored in association with the second identification information specified in.
The arithmetic unit
The insured person who obtains the information of the contract contents of each insurance from a predetermined device and has at least one of the relationship and the attribute conforming to at least one of the insurance coverage and the insurance conditions in the contract contents is insured. A process of specifying based on the insurer information, a process of associating the specified first identification information of the insured person with the insured object and the insurance conditions in the contract contents and holding it in the storage device, and a predetermined insured. An output request for the coverage of insurance by a person is obtained from a predetermined device, and the insured person is a policyholder or insured based on the insured person information based on the second identification information of the insured person indicated by the output request. The first identification information of the insured person in the insurance linked from the standpoint of the person is specified, and the insured person is the insured in the insurance linked from the standpoint of the policyholder in the insured person information. The process of identifying the first identification information of another insured person having a relationship with the insurer and the first identification information of the insured person and the other insured person are collated with the information of the contract contents of each insurance. Then, the process of specifying each insurance in which the first identification information is linked to either the insurance target or the insurance condition in the contract content and the coverage indicated by the information of the contract content of each specified insurance are covered by the insurance. It aggregates each insured person and executes at least the process of generating information about the coverage and its duplication and outputting it to a predetermined device.
The contract management support device according to claim 1. The arithmetic unit
When generating information about the coverage and its duplication, a predetermined display object of each default coverage is arranged for each insured person to be insured, and the display object is specified. Different display forms are set for the coverage indicated by the information on the contract contents of each insurance and other items, and further different display forms are set for those corresponding to the overlapping coverages. It outputs to a predetermined device,
The contract management support device according to claim 2, wherein the contract management support device is characterized. The arithmetic unit
When generating information on the coverage and its duplication, information on whether or not duplicate claims can be made in the corresponding insurance is set for the display object corresponding to the coverage in which the duplication occurs, and the information is output to the predetermined device. Is,
The contract management support device according to claim 3, wherein the contract management support device is characterized in that. The storage device is
Information on the event that occurred in the insured person or the surrounding environment obtained from the terminal possessed by the insured person, and information that defines the correspondence relationship between the event and the insurance that covers the risk associated with the event. Is to store more
The arithmetic unit
If the event information indicates content that matches a predetermined definition, the insurance covers the risk associated with the event by collating the event information with the information that defines the correspondence. And the process of specifying whether the insured person is the insured person of the specified insurance or not based on the insured person information, and as a result of the determination, the insured person is the insured person of the specified insurance. If, the information proposing the execution of the insurance claim is output to a predetermined device, and if the insured person is not the insured person of the specified insurance as a result of the determination, the insurance is proposed to be taken out. When the information is output to a predetermined device, and as a result of the determination, the insured person is the insured person of the specified insurance and the information of the event satisfies the predetermined predetermined condition of the insurance. The process of outputting information proposing a review of the contract contents to a predetermined device is further executed.
The contract management support device according to claim 1. The arithmetic unit
Among the insured persons specified in the insured person information, the event corresponding to the insurance coverage range associated with the insured person is specified by the corresponding information, and the information of the specified event is stored. A person who is not held in the device or a person who does not hold an application for acquiring the information of the event on the terminal is specified by a predetermined algorithm, and the insured person's terminal is proposed to use the application. It further executes the process of outputting information.
The contract management support device according to claim 5, characterized in that. An information processing device equipped with a storage device that stores identification information that identifies an insured person in each insurance, attribute information, a contractual position, and insured person information that links relationships between insured persons.
The insured person who obtains the information of the contract contents of each insurance from a predetermined device and has at least one of the relations and attributes conforming to at least one of the insurance coverage and the insurance conditions in the contract contents is insured. Processing to identify based on insurer information and
A process of holding the identified insured person's identification information in a storage device in association with the insurance target and the insurance conditions in the contract contents.
An output request for the coverage of insurance by a predetermined insured person is obtained from a predetermined device, and based on the identification information of the insured person indicated by the output request, the insured person is a policyholder or a policyholder in the insured person information. Identify the insurance linked from the insured's standpoint, and use the insured person information to identify other insured persons who have a relationship with the insured in the insurance linked from the insured's standpoint. The process of identifying the insurer and
The identification information of the insured person and the other insured person is collated with the information of the contract contents of each insurance, and each insurance in which the identification information is linked to any of the insurance target and the insurance conditions in the contract contents. And the process of identifying
A process of aggregating the coverage indicated by the information on the contract details of each of the specified insurances for each insured person covered by the insurance, generating information on at least the coverage and its overlap, and outputting it to a predetermined device.
A contract management support method characterized by executing. The information processing device
In the storage device, as the insured person information, the first identification information for identifying the insured person in each insurance, the attribute information, the contractual position, the relationship between the insured persons, and the insured person straddling the insurance. The second identification information that uniquely identifies the insured person is linked and stored.
The insured person who obtains the information of the contract contents of each insurance from a predetermined device and has at least one of the relations and attributes conforming to at least one of the insurance coverage and the insurance conditions in the contract contents is insured. Processing to identify based on insurer information and
The process of holding the first identification information of the specified insured person in the storage device in association with the insurance target and the insurance conditions in the contract contents.
An output request for the coverage of insurance by a predetermined insured person is obtained from a predetermined device, and the insured person makes a contract with the insured person information based on the second identification information of the insured person indicated by the output request. The first identification information of the insured person in the insurance linked from the standpoint of the person or the insured person is specified, and the insured person is linked from the standpoint of the policyholder in the insured person information. To identify the first identification information of another insured person who has a relationship with the insured person in
The first identification information of the insured person and the other insured person is collated with the information of the contract contents of each insurance, and the first identification information is linked to either the insurance target or the insurance conditions in the contract contents. The process of identifying each insurance policy
A process of aggregating the coverage indicated by the information on the contract details of each of the specified insurances for each insured person covered by the insurance, generating information on at least the coverage and its overlap, and outputting the information to a predetermined device.
7. The contract management support method according to claim 7, wherein the method is executed. The information processing device
When generating information about the coverage and its duplication, a predetermined display object of each default coverage is arranged for each insured person to be insured, and the display object is specified. Different display forms are set for the coverage indicated by the information on the contract contents of each insurance and other items, and further different display forms are set for those corresponding to the overlapping coverages. Output to the specified device,
The contract management support method according to claim 8, characterized in that. The information processing device
When generating information on the coverage and its duplication, information on whether or not duplicate claims can be made in the corresponding insurance is set for the display object corresponding to the coverage in which the duplication occurs, and the information is output to the predetermined device.
The contract management support method according to claim 9, characterized in that. The information processing device
In the storage device, the correspondence relationship between the information of the event that occurred in the insured person or the surrounding environment obtained from the terminal possessed by the insured person and the insurance that covers the event and the risk associated with the event. Further store the specified information and
If the event information indicates content that matches a predetermined definition, the insurance covers the risk associated with the event by collating the event information with the information that defines the correspondence. And the process of identifying
Whether the insured person is the insured person of the specified insurance is determined by the insured person information, and as a result of the determination, if the insured person is the insured person of the specified insurance, the insurance claim The information proposing the execution of the above is output to the predetermined device, and as a result of the determination, if the insured person is not the insured person of the specified insurance, the information proposing to join the insurance is output to the predetermined device. However, as a result of the determination, if the insured person is the insured person of the specified insurance and the information of the event satisfies a predetermined condition set in advance, it is proposed to review the contract contents of the insurance. Processing to output the information to be to the specified device and
7. The contract management support method according to claim 7, wherein the method is further executed. The information processing device
Among the insured persons specified in the insured person information, the event corresponding to the insurance coverage range associated with the insured person is specified by the corresponding information, and the information of the specified event is stored. A person who is not held in the device or a person who does not hold an application for acquiring the information of the event on the terminal is specified by a predetermined algorithm, and the insured person's terminal is proposed to use the application. Further execute the process of outputting information,
The contract management support method according to claim 11, characterized in that.

Images