Insurance payment review device, insurance payment review system, and insurance payment review method

Abstract

To allow compensation for damage caused by an incident involving a mistake in prediction.SOLUTION: An insurance money payment examination system 10 comprises a determination unit 114 that receives an insurance claim for the incident, and approves the claim when the prediction probability of occurrence of the incident is equal to or less than a predetermined value. The determination unit 114 refers to the recording of maintenance work for an object of insurance, and if predetermined maintenance work is not executed for the object of insurance, the determination unit may reject the claim. The insurance money payment examination system 10 may further comprise a detection unit 113 that refers to the recording of the maintenance work for the object of insurance, and detects the occurrence of the incident.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an insurance payment review system, a program, and an insurance payment review method for reviewing the eligibility of insurance payments.

Background Art

[0002] In the insurance business, the introduction of the use of drones for damage surveys due to natural disasters, the automation of call center operations using voice recognition technology, and the automation of insurance payment reviews using machine learning technology is progressing. In addition, it is predicted that insurance that collects data on insurance targets such as people, facilities, and machines to predict risks and determine insurance premiums will spread.

[0003] According to the invention described in Patent Document 1, it is possible to predict the malfunction of a technical entity, and it is possible to calculate the probability of malfunction at any future time without depending on the component type. Further, according to the invention described in Patent Document 2, it is possible to evaluate and approve claims very quickly according to the insurance industry standard.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] To avoid unexpected incidents such as equipment failures, using a prediction technique like the invention described in Patent Document 1, the equipment operator can maintain the equipment based on the prediction results. However, the possibility of unexpected incidents cannot be eliminated. Here, "unexpected (prediction error)" means that an incident predicted to have a low occurrence probability occurs. When maintaining equipment for which a malfunction is predicted based on the prediction results, if there are many prediction errors (low prediction accuracy), appropriate maintenance cannot be performed, resulting in damage. In an automatic loss verification system that evaluates the validity of claims under an insurance contract or debt protection contract, such as Patent Document 2, damage caused by prediction errors is not compensated.

[0006] The present invention has been made in view of such a background, and an object thereof is to provide an insurance payment review system, a program, and an insurance payment review method that enable compensation for damage caused by prediction errors.

Means for Solving the Problems

[0007] To solve the above-described problems, the insurance payment review according to the present invention Device is An insurance payment review device that is a computer and is transmitted via a network, to receive a claim for insurance payment for an incident, Stored in a storage device provided in the insurance payment review device, and include a determination unit that approves the claim when the predicted occurrence probability of the incident is equal to or less than a predetermined value. Determined to do

Effects of the Invention

[0008] According to the present invention, it is possible to provide an insurance payment review system, a program, and an insurance payment review method that enable compensation for damage caused by prediction errors. Problems, configurations, and effects other than those described above will be clarified by the description of the following embodiments.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Modes for Carrying Out the Invention

[0010] Hereinafter, an insurance payment review system in a mode (embodiment) for carrying out the present invention will be described. The insurance payment review system confirms that an incident with a low predicted occurrence probability has occurred and caused damage, and approves the claim for the insurance payment of the equipment / apparatus that is the insurance target.

[0011] According to such an insurance payment review system, an insurance payment for compensating damage caused by an incident that is predicted to have a low occurrence probability due to maintenance will be paid. Among existing insurances, there was no insurance for compensating damage caused by a mistake in predicting the occurrence of an incident. The present invention enables the provision of insurance for compensating damage caused by a mistake in predicting the occurrence of an incident, which serves as a basis for determining maintenance work. By using such insurance, the operator of the equipment / apparatus can easily perform maintenance work according to the prediction of the occurrence of an incident. For example, the operator can focus on maintenance corresponding to an incident predicted to have a high occurrence probability, and can handle an incident predicted to have a low occurrence probability with insurance, enabling efficient maintenance.

[0012] ≪Overall Configuration of Insurance Payment Review System≫ FIG. 1 is an overall configuration diagram of an insurance payment review system 10 according to the first embodiment. The insurance payment review system 10 includes an incident prediction device 210, a maintenance management device 220, and an insurance payment review device 100. The incident prediction device 210, the maintenance management device 220, and the insurance payment review device 100 can communicate with each other via a network 280. A terminal 270 that can communicate with the insurance payment review device 100 via the network 280 may be connected. When an incident occurs in the equipment / devices that are the insurance target and damage is caused, the insurance contract holder may claim insurance benefits using the terminal 270.

[0013] An incident prediction unit 211 provided in the incident prediction device 210 predicts the probability that an incident will occur in the equipment / devices that are the insurance target at a predetermined timing. The predetermined timing is, for example, within 1 month, within 1 month to 2 months, etc. The incident prediction unit 211 predicts the probability that an incident will occur based on, for example, the type, years of use, usage environment, maintenance status, failure rate, etc. of the equipment / devices. Also, the incident prediction unit 211 transmits the incident prediction data 131 (see FIG. 2 described later), which is the prediction result, to the insurance payment review device 100, for example, periodically. In the following description, it will be described as being transmitted on a monthly cycle.

[0014] As described above, the insurance payment review system 10 includes an incident prediction unit 211 that calculates the predicted probability of an incident occurring. Thus, the predicted probability of an incident occurring is based on the probability (failure rate) that a failure will occur in the insurance target.

[0015] A maintenance management unit 221 provided in the maintenance management device 220 acquires a maintenance management form 141 (see FIG. 3 described later), which is a record of maintenance work performed on the equipment / devices that are the insurance target, and transmits it to the insurance payment review device 100. The timing of transmission may be periodic or the timing when the record of the maintenance work is acquired.

[0016] <<Functional Configuration of Insurance Payment Review Device>> The insurance payment review device 100 is a computer, and includes a processing unit 110, a storage unit 120, and an input / output unit 180. User interface devices such as a display, a keyboard, and a mouse are connected to the input / output unit 180. The input / output unit 180 includes a communication device and is capable of data transmission and reception with the incident prediction device 210 and the maintenance management device 220. A media drive may also be connected to the input / output unit 180 to enable data exchange using a recording medium. The insurance payment review device 100 may take the form of a cloud server that constitutes one logical device with a plurality of physical devices.

[0017] ≪Insurance Payment Review Device: Storage Unit≫ The storage unit 120 is configured to include storage devices such as a ROM (Read Only Memory), a RAM (Random Access Memory), and an SSD (Solid State Drive). The storage unit 120 stores an incident prediction database 130 (see FIG. 2 described later), a maintenance database 140 (see FIG. 3 described later), a compensation target database 121, and a program 128. In the compensation target database 121, facilities / devices and incidents that are the insurance compensation targets for the facilities / devices are stored in an associated manner. The program 128 includes a description of the processing of the insurance payment review process (see FIG. 4 described later).

[0018] ≪Insurance Payment Review Device: Incident Prediction Database≫ FIG. 2 is a data configuration diagram of the incident prediction database 130 according to the first embodiment. Incident prediction data 131 transmitted from the incident prediction device 210 on a monthly basis is stored in the incident prediction database 130. The incident prediction data 131 is tabular data, and one row (record) indicates a predicted value of the occurrence probability of an incident. Specifically, one row includes columns (attributes) such as an incident, a facility / device (described as a facility in FIG. 2), within 1 month, within 2 months, within 3 months, and the like. The facility / device is identification information of the facility / device, and the incident is identification information (for example, name) of the incident that occurs in the facility / device. Within 1 month is a predicted value of the probability that an incident will occur in the facility / device within 1 month, and within 2 months is a predicted value of the probability that it will occur within 1 month or more and within 2 months. The same applies to within 3 months, within 4 months, and so on.

[0019] ≪Insurance Payment Review Device: Maintenance Database≫ FIG. 3 is a data configuration diagram of the maintenance database 140 according to the first embodiment. The maintenance management form 141 transmitted from the maintenance management device 220 is stored in the maintenance database 140. The item of "maintenance target" in the maintenance management form 141 includes identification information of the insured device / facility that is the maintenance target. The maintenance management form 141 also includes information such as "phenomenon", "phenomenon occurrence date and time", "maintenance work name", "maintenance date and time", etc., which triggered the maintenance work. The item of "phenomenon" includes descriptions such as "elapsed a certain period", indicating the time of regular maintenance, and "fire occurrence", indicating the occurrence of an incident such as a fire.

[0020] ≪Insurance Payment Review Device: Processing Unit≫ Returning to FIG. 1, the description of the processing unit 110 will be continued. The processing unit 110 includes a CPU (Central Processing Unit) and is provided with an acquisition unit 111, a prediction accuracy calculation unit 112, a detection unit 113, and a determination unit 114. The acquisition unit 111 receives the incident prediction data 131 from the incident prediction device 210 and stores it in the incident prediction database 130. The acquisition unit 111 also receives the maintenance management form 141 from the maintenance management device 220 and stores it in the maintenance database 140.

[0021] The prediction accuracy calculation unit 112 refers to the data in the incident prediction database 130 and the maintenance database 140, and calculates the accuracy of the prediction probability calculated by the incident prediction device 210. For example, the prediction accuracy calculation unit 112 refers to the data in the maintenance database 140, groups the same or similar models and equipment with similar years of use, and calculates the incident occurrence frequency for each group. The prediction accuracy calculation unit 112 compares this occurrence frequency with the prediction probability of the equipment / devices belonging to the group to calculate the accuracy of the prediction probability. In this way, the insurance payment review device 100 provided in the insurance payment review system 10 includes a prediction accuracy calculation unit 112 that calculates the accuracy of the predicted probability of the occurrence of an incident.

[0022] The detection unit 113 refers to the maintenance management form 141 in the maintenance database 140 to detect the occurrence of an incident and identify the incident that has occurred. For example, the detection unit 113 detects the incident that has occurred from the "phenomenon" and "maintenance work name", and identifies the equipment / device on which the incident has occurred and the occurrence date and time from the "maintenance target" and "phenomenon occurrence date and time". In this way, the insurance payment review device 100 provided in the insurance payment review system 10 includes a detection unit 113 that refers to the record of the maintenance work for the insurance target (refer to the maintenance database 140) and detects the occurrence of an incident.

[0023] ≪Insurance Payment Review Device: Judgment Unit≫ When the determination unit 114 receives an insurance payment claim, it examines the insurance payment claim. The insurance payment claim includes the identification information of the facility / equipment where the incident occurred. The determination unit 114 instructs the detection unit 113 to obtain the incident that occurred in the facility / equipment, and determines whether the incident is a compensable item by referring to the compensable item database 121.

[0024] In addition, when the detection unit 113 detects the occurrence of an incident by referring to the maintenance management ticket 141 stored in the acquisition unit 111 in the maintenance database 140, the detection unit 113 may notify the determination unit 114 of the incident and the facility / equipment where the incident occurred. The determination unit 114 determines whether the incident is a compensable item by referring to the compensable item database 121.

[0025] The determination unit 114 refers to the maintenance management ticket 141 for the facility / equipment where the incident occurred and is marked as "maintenance target" to identify what kind of maintenance has been performed on the insured facility / equipment, and determines whether the maintenance is appropriate. For example, if the determination unit 114 determines that the "regular maintenance" work corresponding to the facility / equipment has not been performed at the predetermined timing, it determines that appropriate maintenance has not been performed. In addition, if the determination unit 114 determines that the predicted probability of the occurrence of an incident in the facility / equipment is equal to or greater than a predetermined value, but the maintenance corresponding to the incident has not been performed, it determines that appropriate maintenance has not been performed.

[0026] The determination unit 114 confirms that the insurance payment claim is not false. For example, if the determination unit 114 determines that the maintenance management ticket 141 for the corresponding maintenance work is not in the maintenance database 140 despite the insurance payment claim, it determines that it is false. The determination unit 114 confirms that the predicted occurrence probability of an incident is equal to or less than a predetermined value and that it is a prediction error. For example, the determination unit 114 refers to the latest incident prediction data 131 and determines that it is a prediction error if the predicted value of the probability of an incident occurring in the facility / equipment is equal to or less than the predetermined value. In other words, a prediction error is, for example, a case where an incident that was predicted to have a low probability of occurrence (the occurrence probability is equal to or less than the predetermined value) occurs.

[0027] If the incident is an insurance compensation target, appropriate maintenance has been performed, the insurance payment claim is not false, and the occurrence of the incident is a prediction error, the determination unit 114 approves the insurance payment claim. If the incident is not an insurance compensation target, appropriate maintenance has not been performed, the insurance payment claim is false, or the occurrence of the incident is not a prediction error, the determination unit 114 rejects the insurance payment claim (performs a rejection process; see step S17 in FIG. 4 described later).

[0028] As described above, the insurance payment review device 100 provided in the insurance payment review system 10 receives an insurance payment claim for an incident and includes a determination unit 114 that approves the claim when the predicted occurrence probability of the incident is equal to or less than a predetermined value. Also, the determination unit 114 refers to the record of the maintenance work for the insurance target (see the maintenance database 140) and rejects the claim if the predetermined maintenance work for the insurance target has not been performed.

[0029] ≪Insurance Payment Review Process≫ FIG. 4 is a flowchart of the insurance payment review process according to the first embodiment. The insurance payment review process is started when the insurance payment review device 100 receives an insurance payment claim from the terminal 270. Also, when a maintenance management form 141 for maintenance corresponding to the incident is received, the detection unit 113 detects this and notifies the determination unit 114. The determination unit 114 starts the insurance payment review process as if it has received the insurance payment claim.

[0030] In step S11, the determination unit 114 determines whether the facilities / devices included in the insurance payment claim and the incidents that occurred to the facilities / devices are eligible for compensation. If the determination unit 114 determines that they are eligible for compensation (step S11 → YES), it proceeds to step S12; if not (step S11 → NO), it proceeds to step S17. In step S12, the determination unit 114 determines whether the maintenance of the facilities / devices is appropriate. If it is appropriate (step S12 → YES), it proceeds to step S13; if not (step S12 → NO), it proceeds to step S17.

[0031] In step S13, the determination unit 114 determines whether the insurance payment claim is false. If it is not false (step S13 → NO), it proceeds to step S14; if it is false (step S13 → YES), it proceeds to step S17. In step S14, the determination unit 114 determines whether the prediction of the occurrence of the incident is incorrect. If the prediction is incorrect (step S14 → YES), it proceeds to step S15; if the prediction is not incorrect (step S14 → NO), it proceeds to step S17.

[0032] In step S15, the determination unit 114 controls the access rights to the incident prediction data 131 and the maintenance management ticket 141 related to the insurance payment claim. For example, when there is an insurance company that undertakes the insurance payment, the determination unit 114 changes the access rights so that the insurance company can access the incident prediction data 131 and the maintenance management ticket 141. Regarding the incident prediction data 131, not only the prediction probability at the time of the incident occurrence but also the prediction probability after the occurrence may be made accessible.

[0033] In step S16, the determination unit 114 notifies of payment approval. For example, when there is an insurance company that undertakes the insurance payment, the determination unit 114 notifies the insurance company that the payment of the insurance money has been approved. Also, when the insurance payment claim is received from the terminal 270, the determination unit 114 notifies the terminal 270 of the payment approval. In step S17, the determination unit 114 notifies of payment rejection. For example, when the determination unit 114 receives an insurance payment claim from the terminal 270, it notifies the terminal 270 of payment rejection.

[0034] ≪Features of Insurance Payment Review Device≫ The insurance payment review device 100 reviews to pay insurance for damages caused by an incident predicted to have a low occurrence probability due to maintenance. Since it becomes possible to compensate for damages due to prediction errors that are not covered by existing insurance, it becomes easier for the operator of the facility / equipment to perform maintenance work based on the prediction of incident occurrence.

[0035] ≪Modification Example: Distributed Ledger≫ In the above-described embodiment, the incident prediction data 131 is transmitted by the incident prediction device 210 to the insurance payment review device 100 and stored in the incident prediction database 130. Also, the maintenance management ticket 141 is transmitted by the maintenance management device 220 to the insurance payment review device 100 and stored in the maintenance database 140. Instead of the incident prediction data 131 and the maintenance management ticket 141 being individually transmitted and stored in the database, they may be shared among the incident prediction device 210, the maintenance management device 220, and the insurance payment review device 100 using distributed ledger technology (blockchain network).

[0036] FIG. 5 is an overall configuration diagram of an insurance payment review system 10A according to a modification example of the first embodiment. In the insurance payment review system 10A, the incident prediction device 210A, the maintenance management device 220A, and the insurance payment review device 100A are nodes of the blockchain network 290A and are connected via the blockchain network 290A. The incident prediction data and the maintenance management ticket are recorded and accessed in the distributed ledgers 190, 218, 228.

[0037] As described above, the determination unit 114 of the insurance payment review device 100A provided in the insurance payment review system 10A acquires the predicted occurrence probability by referring to the distributed ledger (distributed ledgers 190, 218, 228) in which the predicted occurrence probability calculated by the incident prediction device 210A that calculates the predicted occurrence probability of an incident is recorded. Also, the record of the maintenance work is recorded in the distributed ledger.

[0038] <<Second Embodiment>> In the insurance payment review device 100 in the first embodiment, when receiving an insurance payment claim or detecting maintenance work due to an incident, an insurance payment review is performed. If the review result is approval, for example, it is notified to the insurance company, and the insurance company pays the insurance money. A series of processes related to insurance, such as the conclusion of an insurance contract, the management of insurance contract contents, and the payment of insurance money, or some of the processes may be executed as a smart contract on a blockchain network. For example, incident prediction data and maintenance management slips are recorded in the blockchain network (distributed ledger), and when an insurance payment claim occurs or when maintenance work due to an incident is detected, the insurance payment review process is performed on the blockchain network, and if the review result is approval, the payment of the insurance money may also be executed as a smart contract on the blockchain network.

[0039] A smart contract is a contract, system, or mechanism in which the conclusion and performance of a contract are executed by a computer. In a smart contract, the procedures / processes and contract contents associated with the conclusion and performance of a contract are described / set as source code and data, and are executed as a program when executed. Note that this source code and data reflect the contract contents, and in some cases, the source code and data are also referred to as a smart contract. Also, in some cases, the program to be executed is called a smart contract. In the insurance payment review system in the second embodiment, the program for performing the procedure of the insurance payment review (refer to the insurance payment review process described in FIG. 4) is executed as a transaction on the blockchain network.

[0040] FIG. 6 is an overall configuration diagram of an insurance payment review system 10B according to the second embodiment. In the insurance payment review system 10B, an incident prediction device 210B, a maintenance management device 220B, an insurance management device 230B, and an insurance payment review device 100B are nodes of a blockchain network and are connected via the blockchain network 290B. Incident prediction data, maintenance management forms, and the results of insurance payment reviews are recorded in distributed ledgers 190, 218, 228, and 238. If the result of the insurance payment review by the insurance management device 230B is approval, the insurance management device 230B pays the insurance money according to the insurance contract.

[0041] FIG. 7 is an overall configuration diagram of an insurance payment review system 10C according to a modification of the second embodiment. When an insurance contract is concluded, the insurance management device 230C deploys a smart contract 298 reflecting the insurance contract on the blockchain network 290C.

[0042] The smart contract 298 includes the source code of a determination unit 114 that executes an insurance payment review process and data necessary for the insurance payment review process (refer to the compensation target database 121). The smart contract 298 may include the source code of a detection unit 113 that detects the occurrence of an incident by referring to a maintenance management form, the source code for accepting an insurance payment claim, the source code for paying the insurance money, and the data referred to by these source codes.

[0043] As described above, the smart contract 298 is a program for causing a computer to execute steps of accepting an insurance payment claim for an incident as a smart contract (as a mechanism) on the blockchain network 290C and approving the claim when the predicted occurrence probability of the incident is equal to or less than a predetermined value.

[0044] In addition, procedures / processes other than a series of procedures / processes related to insurance payment may be processed as smart contracts. For example, procedures such as conclusion of the insurance contract and payment of insurance premiums after the insurance contract details are determined may be processed using smart contracts. Thus, as an insurance payment review system, procedures from conclusion to performance of the insurance contract may be transactionally processed as smart contracts on a blockchain network. By executing the insurance payment review as a smart contract in this way, the transparency of the review can be ensured.

[0045] <<Application Example>> The equipment / devices in the above embodiment may be equipment / devices related to power supply. In this case, as an incident, for example, there is an accident caused by a tree contacting a power transmission line. For such an accident, the probability of occurrence of the incident can be calculated by predicting the growth of the tree and the contact time with the power transmission line. Another example of an incident is a power outage due to a breakdown in the power supply-demand balance. For example, based on power demand prediction, the probability of occurrence of such a power outage can be predicted. Maintenance of equipment / devices related to power supply includes regular maintenance, replacement of parts, maintenance of trees around the power transmission line, activation of emergency power, etc.

[0046] Note that there may be an agreement on incidents to be compensated, for example, compensating for a fire caused by contact between a power transmission line and a tree but not compensating for a fire caused by an earthquake. The agreed content is stored in the compensation target database 121, and it is determined whether it is in the agreement in step S11 shown in FIG. 4.

[0047] In the insurance payment review system 10 related to equipment / devices related to power supply as described above, the incident is an accident of the power transmission line, and the predicted probability of occurrence of the incident is based on the prediction of the contact time between the power transmission line and the tree. Also, the incident is a power outage, and the predicted probability of occurrence of the incident is based on power demand prediction.

[0048] <<Other Modification Examples>> Although some embodiments of the present invention have been described above, these embodiments are merely examples and do not limit the technical scope of the present invention. For example, although the incident prediction device 210 and the maintenance management device 220 are separate devices from the insurance payment review device 100, they may be a single device.

[0049] In the above-described embodiment, the insurance payment review process (see FIG. 4) is executed by the determination unit 114, but in some processes, human judgment may be included. For example, when determining whether the maintenance of the facility / equipment is appropriate in step S12, the determination unit 114 may display the relevant maintenance management form 141 and obtain and determine the result judged by a person. In addition, when receiving the maintenance management form 141 for maintenance corresponding to an incident and starting the insurance payment review process, the determination unit 114 may display the maintenance management form 141 and receive an instruction to start from a person and start the insurance payment review process.

[0050] The present invention can take various other embodiments, and furthermore, various changes such as omission and substitution can be made without departing from the gist of the present invention. These embodiments and their modifications are included in the scope and gist of the invention described in this specification and the like, and are also included in the invention described in the claims and the equivalent scope thereof.

Explanation of Reference Numerals

[0051] 10, 10A, 10B, 10C Insurance payment review system 100, 100A, 100B, 100C Insurance payment review device 111 Acquisition unit 112 Prediction accuracy calculation unit 113 Detection unit 114 Determination unit 130 Incident prediction database 140 Maintenance database 190, 218, 228, 238 Distributed ledger 290A, 290B, 290C Blockchain network 298 Smart Contract (Program)

Claims

1. An insurance payment review device which is a computer, comprising: Receiving a claim for insurance payment for an incident transmitted via a network; A determination unit configured to determine that the claim is to be approved when the predicted probability of occurrence of the incident, which is stored in a storage device provided in the insurance payment review device, is equal to or less than a predetermined value. An insurance payment review device.

2. The insurance payment review device is configured as a node constituting a blockchain network, The determination unit: Instead of the storage device, Referring to a distributed ledger which is a node constituting the blockchain network and in which the predicted probability of occurrence calculated by an incident prediction device that calculates the predicted probability of occurrence of the incident is recorded, to obtain the predicted probability of occurrence. The insurance payment review device according to claim 1.

3. The determination unit: Referring to a record of maintenance work for the insurance target stored in a storage device provided in the insurance payment review device, and performing a process of determining that the claim is to be rejected when there is no record of a predetermined maintenance work for the insurance target. The insurance payment review device according to claim 1.

4. Further comprising a detection unit that refers to a record of maintenance work for the insurance target stored in a storage device provided in the insurance payment review device and detects the occurrence of the incident based on the content of the record, The determination unit: Determining that the claim is to be approved when the predicted probability of occurrence of the incident is equal to or less than a predetermined value, assuming that the claim for insurance payment for the incident has been received when the detection unit detects the occurrence of the incident. The insurance payment review device according to claim 1.

5. The insurance payment review device is configured as a node constituting a blockchain network, The record of the maintenance work is recorded in the distributed ledger of the blockchain network instead of the storage device. The insurance payment review device according to claim 3 or 4.

6. Further comprising a prediction accuracy calculation unit that refers to a record of maintenance for the insurance target stored in a storage device provided in the insurance payment review device, calculates the occurrence frequency of the incident for the insurance target, and calculates the accuracy of the predicted probability of occurrence of the incident by comparing it with the predicted probability of occurrence of the incident. The insurance payment review device according to claim 1. An insurance payment review system that is a blockchain network including a plurality of nodes that are computers, wherein: the nodes receive a claim for insurance payment for an incident transmitted via a network, and perform a process of determining to approve the claim when a predicted occurrence probability of the incident recorded in a distributed ledger of the blockchain network is equal to or less than a predetermined value, and function as a computer including a determination unit that executes the process as a smart contract on the blockchain network Insurance payment review system. An insurance payment review method for an insurance payment review apparatus that is a computer, wherein: the insurance payment review apparatus performs a step of receiving a claim for insurance payment for an incident transmitted via a network, and performs a step of determining to approve the claim when a predicted occurrence probability of the incident stored in a storage device provided in the insurance payment review apparatus is equal to or less than a predetermined value Insurance payment review method.

Images