WO2020250375A1 - Control method, control program, information processing device, and information processing system - Google Patents

Abstract

In this control method executed by an information processing device, upon detecting that receipt information relating to a patient has been stored in a block chain, a computer executes a process to transmit the patient's receipt information to an address corresponding to the patient prior to being transmitted to an address corresponding to an insurance company with which the patient has a contract, thereby making it possible to control whether the receipt information is to be charged to the insurance company.

Description

Control methods, control programs, information processing devices and information processing systems

The present invention relates to a control method, a control program, an information processing device, and an information processing system.

For insurance contracted with an insurance company, such as life insurance and medical insurance, the insurance company pays benefits to the insured when the insured is in the state (medical condition, etc.) specified in the contract. ..

In order for the insured to receive the benefits, the insured must contact the insurance company and perform procedures such as application. Such a procedure may require a large number of documents such as a medical certificate by a doctor, which imposes a heavy burden on the insured.

International Publication No. 2018/225428 International Publication No. 2018/12297 Japanese Patent No. 6245782

Therefore, if the receipt information submitted by the medical institution to the health insurance association is automatically transferred to the insurance company, and the insurance company can determine whether or not the person is eligible for the payment of benefits based on the receipt information, it will be covered. It is thought that the burden on the insurer can be reduced.

However, there is a possibility that the receipt information is irrelevant to the contract regarding the payment of benefits and also contains sensitive information. As a result, information on medical conditions that the insured does not want others to know may be leaked to the insurance company.

Therefore, on one aspect, it is an object of the present invention to make it possible to control whether or not the receipt information is subject to a claim to an insurance company.

In one aspect, when the control method executed in the information processing device detects that the patient's receipt information is stored in the blockchain, the patient's receipt information is sent to the destination according to the insurance company contracted by the patient. The computer performs the process of sending to the destination according to the patient before sending to.

As one aspect, it is possible to control whether or not the receipt information is subject to a claim to the insurance company.

It is a figure which shows the structural example of the information processing system in embodiment of this invention. It is a figure which shows the hardware configuration example of each node of the blockchain 10 in embodiment of this invention. It is a figure which shows the functional structure example of the information processing system in embodiment of this invention. It is a figure for demonstrating the registration process of account information. It is a figure for demonstrating the registration process of a matching condition. It is a figure for demonstrating the process which a medical institution terminal 40 executes after the medical treatment of the insured person a. It is a sequence diagram for demonstrating an example of the processing procedure executed in response to the input of the receipt information to the health insurance terminal 50. It is a figure which shows the state of the registration process of the insured person ID and the receipt information in a blockchain 10. It is a figure which shows the state of the determination process of a matching condition. It is a figure which shows the state of the transmission processing of the receipt information to an insurance company. It is a figure which shows the state of the confirmation process of the validity of the receipt information from an insured person. It is a figure for demonstrating the security of the receipt information stored in the blockchain 10.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a configuration example of an information processing system according to an embodiment of the present invention. In FIG. 1, the information processing system 1 includes an insured person terminal 20, a medical institution terminal 40, a health insurance terminal 50, an insurance company terminal 30, a blockchain 10, and the like. The blockchain 10 can communicate with the insured person terminal 20, the insurance company terminal 30, and the health insurance terminal 50 via a network such as the Internet. Further, the insured terminal 20 can communicate with the insurance company terminal 30 via a network such as the Internet. Further, the health insurance terminal 50 can communicate with the medical institution terminal 40 via a network such as the Internet.

The insured terminal 20 is provided by an insured person (hereinafter referred to as "insured person a") who has a contract for insurance provided by a certain insurance company (hereinafter referred to as "insurance company A"). It is a terminal to use. For example, a PC, a smartphone, a tablet terminal, or the like may be used as the insured terminal 20.

The medical institution terminal 40 is one or more computers used at the medical institution (hereinafter referred to as "medical institution B") to which the insured person a goes to the hospital.

The health insurance terminal 50 is one or more computers used by the health insurance association.

The insurance company terminal 30 is one or more computers used by the insurance company A.

The insured terminal 20 of the insured person other than the insured person a and the insurance company terminal 30 other than the insurance company A may be included in the information processing system.

The blockchain 10 is a decentralized network (blockchain 10) including a plurality of nodes that store the receipt information of the insured person a. Each node is one or more computers (information processing devices), and includes a ledger 15 (distributed ledger) for storing the receipt information as a management target in the blockchain 10, and also receives the receipt information to the insurance company terminal 30. Controls whether or not the information can be transmitted. The receipt information refers to information indicating items to be described in the medical fee statement. For example, personal information such as patient name, gender and date of birth, patient health insurance enrollment information, medical institution name of claimant, clinical department, disease name, injection, treatment, surgery, examination, diagnostic imaging performed in the medical treatment month. , Rehabilitation, scores of medicines prescribed in the month of medical treatment, etc. are included in the receipt information. The receipt information may include items described in the dispensing fee statement and items described in the statement of nursing care expenses.

FIG. 2 is a diagram showing a hardware configuration example of each node of the blockchain 10 according to the embodiment of the present invention. As shown in FIG. 2, each node has a drive device 100, an auxiliary storage device 102, a memory device 103, a CPU 104, an interface device 105, and the like, which are connected to each other by a bus B.

The program that realizes the processing at the node is provided by the recording medium 101. When the recording medium 101 on which the program is recorded is set in the drive device 100, the program is installed in the auxiliary storage device 102 from the recording medium 101 via the drive device 100. However, the program does not necessarily have to be installed from the recording medium 101, and may be downloaded from another computer via the network. The auxiliary storage device 102 stores the installed program and also stores necessary files, data, and the like.

The memory device 103 reads and stores the program from the auxiliary storage device 102 when the program is instructed to start. The CPU 104 executes a function related to the node according to a program stored in the memory device 103. The interface device 105 is used as an interface for connecting to a network.

An example of the recording medium 101 is a portable recording medium such as a CD-ROM, a DVD disc, or a USB memory. Further, as an example of the auxiliary storage device 102, an HDD (Hard Disk Drive), a flash memory, or the like can be mentioned. Both the recording medium 101 and the auxiliary storage device 102 correspond to computer-readable recording media.

FIG. 3 is a diagram showing a functional configuration example of the information processing system according to the embodiment of the present invention. In FIG. 3, the medical institution terminal 40 has a medical institution processing unit 41. The medical institution processing unit 41 is realized by processing one or more programs installed in the medical institution terminal 40 to be executed by the CPU of the medical institution terminal 40. The medical institution processing unit 41 transmits the receipt information of each insured person regarding the medical practice (medical treatment, etc.) performed in the cycle to the health insurance terminal 50 at a regular cycle such as every month.

The health insurance terminal 50 has a health insurance processing unit 51. The health insurance processing unit 51 is realized by processing one or more programs installed in the health insurance terminal 50 to be executed by the CPU of the health insurance terminal 50. The health insurance processing unit 51 associates each receipt information transmitted from the medical institution processing unit 41 with the patient (insured person) identification information (hereinafter, referred to as “insured person ID”) related to each receipt information. Send to blockchain 10.

Each node of the blockchain 10 has a receipt information receiving unit 11, a condition determination unit 12, a receipt information notification unit 13, an inquiry response unit 14, and the like. Each of these parts is realized by a process of causing the CPU 104 to execute one or more programs installed on each node. Each node also uses the ledger 15. The ledger 15 can be realized by using, for example, an auxiliary storage device 102, a storage device that can be connected to each node via a network, or the like.

The receipt information receiving unit 11 receives the receipt information and the insured person ID transmitted from the health insurance processing unit 51, and stores the received receipt information and the insured person ID in the ledger 15 in association with each other.

The condition determination unit 12 determines whether or not the receipt information stored in the ledger 15 matches the matching condition. The matching condition is a condition for the receipt information registered in advance by each insurance company.

When the receipt information notification unit 13 detects that the receipt information that matches the matching condition is stored in the ledger 15, the receipt information notification unit 13 receives the address according to the patient (insured person a) related to the receipt information (insured in the present embodiment). Send to the person terminal 20).

The inquiry response unit 14 acquires the receipt information requested from the insurance company terminal 30 from the ledger 15 and transmits it to the insurance company terminal 30.

The ledger 15 is a distributed ledger of the blockchain 10 that stores receipt information and the like.

The insured terminal 20 has a client unit 21. The client unit 21 is realized by a process of causing the CPU of the insured terminal 20 to execute one or more programs installed on the insured terminal 20. When the client unit 21 receives the receipt information transmitted from the receipt information notification unit 13 of the blockchain 10, the client unit 21 outputs the receipt information in a state in which the insured person a can confirm it. When the client unit 21 determines the operation to send the receipt information to the insurance company A and accepts the operation to send the receipt information to the insurance company A, the client unit 21 sends the receipt information to the destination according to the insurance company A ( In this embodiment, transmission is performed to the insurance company terminal 30).

The insurance company terminal 30 has an insurance company processing unit 31. The insurance company processing unit 31 is realized by processing one or more programs installed in the insurance company terminal 30 to be executed by the CPU of the insurance company terminal 30. When the insurance company processing unit 31 receives the receipt information transmitted from the client unit 21, it receives the receipt information based on the comparison result between the received receipt information of the patient and the receipt information of the insured person a stored in the blockchain 10. It is determined whether or not the received receipt information has been tampered with.

In this embodiment, one insured person (insured person a), one medical institution (medical institution B), and one insurance company (insurance company A) will be described, but a plurality of insured persons. , Multiple medical institutions and multiple insurance companies may exist.

The processing procedure executed in the information processing system 1 will be described below. Before the operation of the information processing system 1, first, the insured person's account information is registered from the insured person's terminal 20 to the health insurance terminal 50 and the insurance company terminal 30.

FIG. 4 is a diagram for explaining the account information registration process. In FIG. 4, the overlapping insurance company public key PKc on the upper right of the client unit 21 has the public key of the insurance company A (hereinafter referred to as “insurance company public key PKc”) set in advance for the client unit 21. Indicates that it is (included). For example, the client unit 21 may be realized by a process in which an application program distributed from the insurance company A to each insured person is executed on the insured person terminal 20. In this case, the insurance company A may include the insurance company public key PKc for the application before distribution of the application.

First, the insured person a inputs the attribute information of the insured person a such as the name to the client unit 21 (S101). The input of the name and the like may be performed, for example, via the screen displayed on the insured terminal 20 by the client unit 21.

The client unit 21 responds to the input of the name and the like, and receives the insured person's ID, the insured person's public key (hereinafter referred to as "insured person's public key PKi"), and the private key (hereinafter, "" Insured person's private key SKi ") is generated. The client unit 21 transmits the insured person ID, the name, etc., and the insured person public key PKi to each of the health insurance terminal 50 and the insurance company terminal 30 (S102, S103).

Each of the health insurance terminal 50 and the insurance company terminal 30 stores the insured person ID, name, etc. and the insured person public key PKi in the storage device as the account information of the insured person a.

On the other hand, from the insurance company terminal 30, matching conditions are set in advance for the condition determination unit 12 of each node of the blockchain 10. The matching condition refers to a condition for detecting specific receipt information.

FIG. 5 is a diagram for explaining the registration process of the matching condition. For example, the insurance company processing unit 31 of the insurance company terminal 30 responds to the registration of the account information described in FIG. 4, and the matching condition for the receipt information of the insured person a related to the insured person ID included in the account information. Is registered in the condition determination unit 12 of any node of the blockchain 10. The matching condition may be registered as a smart contract (for example, Chaincode).

In the present embodiment, the receipt information corresponding to the insured person ID of the insured person a is registered as a matching condition. The matching condition is not information for determining whether or not the benefit is paid based on the receipt information, but for detecting that the receipt information of a specific insured person is registered in the blockchain 10. Because it is information. The matching conditions set in the condition determination unit 12 of a certain node are also automatically set for the condition determination unit 12 of each node in the blockchain 10.

When the matching condition is set, the condition determination unit 12 of each node determines whether or not the receipt information matches the matching condition each time the receipt information is registered in the blockchain 10.

After that, it is assumed that the insured person a receives medical treatment at the medical institution B. In this case, the process of FIG. 6 is executed at a predetermined timing after the medical treatment. FIG. 6 is a diagram for explaining a process executed by the medical institution terminal 40 after the medical treatment of the insured person a.

The medical institution processing unit 41 of the medical institution terminal 40 extracts medical records and the like in the cycle from the electronic medical record DB in the medical institution B at a periodic timing such as one month, and the medical records and the like are extracted based on the medical records and the like. Receipt information corresponding to the cycle (1 month) is generated for each patient, and the receipt information of each patient is transmitted to the health insurance terminal 50 (S121). If the insured person a is receiving medical treatment or the like in the cycle, the receipt information of the insured person a is also transmitted to the health insurance terminal 50.

When the receipt information transmitted from the medical institution processing unit 41 is received by the health insurance terminal 50, for example, the operator of the health insurance association processes the receipt information and the insured person ID with the health insurance processing unit 51. Input to unit 51 (S122). The insured person ID corresponding to the receipt information can be specified by collating the name and the like included in the receipt information with the name and the like in the account information registered in advance in the health insurance terminal 50.

Note that step S122 may be performed automatically instead of being manually performed by the operator. That is, the health insurance processing unit 51 receives the receipt information transmitted from the medical institution processing unit 41, and the health insurance processing unit 51 uses the insured person ID corresponding to the receipt information as the account information registered in the health insurance terminal 50. It may be specified based on.

The processing procedure after the input of the receipt information to the health insurance processing unit 51 (health insurance terminal 50) will be described with reference to a sequence diagram. FIG. 7 is a sequence diagram for explaining an example of a processing procedure executed in response to input of receipt information to the health insurance terminal 50.

Step S201 of FIG. 7 corresponds to step S122 of FIG. In response to step S201 (S122), the health insurance processing unit 51 uses the insured person public key PKi included in the account information including the input insured person ID among the account information registered in the health insurance terminal 50. It is used to encrypt the input receipt information (S202). Subsequently, the health insurance processing unit 51 transmits the insured person ID and the encrypted receipt information to the blockchain 10 (S203).

When the receipt information receiving unit 11 of each node of the blockchain 10 receives the insured person ID and the receipt information, the receipt information is recorded in the ledger 15 in association with the insured person ID (S204).

Note that FIG. 8 shows the state of the registration process of the insured person ID and the receipt information in the blockchain 10 in steps S202 to S204. In FIG. 8, for convenience, the registration process is shown for one node, but in the blockchain 10, the insured person ID and the receipt information registered in the node are stored in the ledger 15 of all the other nodes. It will be reflected.

Subsequently, the condition determination unit 12 of each node determines whether or not the receipt information newly stored in the ledger 15 matches the matching condition registered in advance (S205). In the present embodiment, the content of the matching condition is to notify the destination corresponding to the insured ID when the receipt information corresponding to the insured ID set in the matching condition is stored in the ledger 15. It is to do. Therefore, the condition determination unit 12 determines whether or not the insured person ID stored in the ledger 15 together with the receipt information matches the insured person ID set in the matching condition. If the insured ID stored in the ledger 15 does not meet any of the matching conditions, the subsequent processing is not executed. On the other hand, if the ID of the insured stored in the ledger 15 matches any of the matching conditions, the subsequent processing is executed. For example, the insured stored in the ledger 15 detects that the ID matches the matching condition related to the insured ID of the insured person a (that is, the receipt information of the insured person a is stored in the ledger 15). Then, the receipt information notification unit 13 is a notification destination corresponding to the receipt information (that is, a notification destination according to the insured person ID registered together with the receipt information) for the receipt information stored in the ledger 15. Notify (transmit) to the client unit 21 of the insured terminal 20 of the insured a (S206). Upon receiving the receipt information, the client unit 21 decrypts the receipt information with the insured person's private key SKi so that the insured person a can view the receipt information (S207). For example, the client unit 21 may save the file including the decrypted receipt information in the insured terminal 20 and send the name of the file to the e-mail address of the insured a, or the client unit 21 may be decrypted. The receipt information may be displayed.

Note that FIG. 9 shows the state of the matching condition determination process in steps S206 and S207.

By being notified of the receipt information, the insured a can confirm his / her receipt information that may be sent to the insurance company A in order to receive the benefit before sending it to the insurance company A. .. Therefore, the insured person a determines whether or not to allow or reject the transmission of the receipt information. For example, it is determined whether or not the receipt information does not include information that one does not want to disclose. The insured person a inputs the result of the determination (permission or rejection of transmission), for example, via the screen displayed by the client unit 21.

When the insured person a performs the input operation of the judgment result, the client unit 21 determines whether or not the operation to transmit the receipt information is accepted, and when the operation to not transmit is accepted, thereafter. Cancels the processing of. On the other hand, when the operation to transmit is accepted, the client unit 21 encrypts the receipt information using the insurance company public key PKc set in advance in the client unit 21 (S209). Subsequently, the client unit 21 transmits the insured person ID of the insured person a and the encrypted receipt information to the insurance company terminal 30 (S210). When the insurance company processing unit 31 of the insurance company terminal 30 receives the insured person ID and the receipt information, it corresponds to the insurance company public key PKc and uses the insurance company private key SKc held by the insurance company processing unit 31. The receipt information is decoded (S211).

Note that FIG. 10 shows the state of the process of transmitting the receipt information to the insurance company in steps S210 and S211.

Subsequently, steps S212 to S216 are executed in order for the insurance company processing unit 31 to confirm the validity of the decrypted receipt information (hereinafter, referred to as “target receipt information”).

In step S212, the insurance company processing unit 31 transmits a receipt information inquiry request to the blockchain 10 using the insured person ID received together with the target receipt information as a key. The inquiry response unit 14 of any node of the blockchain 10 stores the receipt information encrypted by the insured person public key PKi, which is stored in the ledger 15 in association with the insured person ID, in the ledger 15. Obtained from (S213). Subsequently, the inquiry response unit 14 transmits the receipt information (hereinafter, referred to as “registered receipt information”) to the insurance company processing unit 31 (S214).

When the insurance company processing unit 31 receives the registered receipt information, it encrypts the target receipt information with the insured person's public key PKi of the insured person a (S215). The insured person public key PKi of the insured person a can be obtained from the account information including the insured person ID received together with the target receipt information in step S210. Subsequently, the insurance company processing unit 31 compares the target receipt information encrypted with the insured person public key PKi of the insured person a with the registered receipt information (S216). Here, the registration receipt information is encrypted by the insured person's public key PKi. Therefore, if the plaintext target receipt information and the plaintext registration receipt information are the same, the encrypted information should also be the same. Therefore, the insurance company processing unit 31 determines that the target receipt information is valid if the encrypted target receipt information and the registered receipt information match, and if not, the target receipt information is invalid. Is determined. If the target receipt information is invalid, the subsequent processing will not be executed. The legitimacy of the target receipt information here is two conditions: (1) the target receipt information has not been tampered with, and (2) the target receipt information is the receipt information of the insured person a. Although it means that the condition is satisfied, it can be determined by step S216 whether or not these two conditions are satisfied. That is, when the encrypted target receipt information matches the registered receipt information stored in the blockchain 10, it is confirmed that the information has not been tampered with. Further, when the encrypted target receipt information matches the registered receipt information of the insured person a, it is confirmed that the target receipt information is the receipt information of the insured person a.

Note that FIG. 11 shows the state of the confirmation processing of the validity of the receipt information from the insured terminal 20 in steps S212 to S216.

If the target receipt information is valid, the insurance company processing unit 31 notifies, for example, the insured person ID of the insured person a and the target receipt information in plain text to the operator of the insurance company terminal 30 (S217). Notification of the insured person ID of the insured person a and the target receipt information in plain text may be performed by using a known means such as e-mail. In response to the notification, the insurance company A conducts an insurance examination based on the receipt information and the account information corresponding to the insured person ID (S218). If the examination is passed, the insurance company A will pay the insured person a a benefit.

As described above, according to the present embodiment, before the receipt information is presented to the insurance company, the insured is inquired whether or not the receipt information can be transmitted. Therefore, it is possible to control whether or not the receipt information is subject to a claim to the insurance company. As a result, it is possible to prevent the insurance company from being notified of information (such as chronic illness) that the insured person (patient) does not want to know.

In addition, the receipt information is encrypted by the insured person's public key PKi and stored in the blockchain 10. Therefore, in order to decrypt the receipt information, the insured person's private key PKs corresponding to the insured person's public key PKi are required, but it is basically insured to have the insured person's private key PKs. Limited to insurers. This means that the receipt information stored in the blockchain can be logically (substantially) deleted at the will of the insured. That is, if the insured wants to logically delete his / her past receipt information, he / she may destroy (delete) his / her insured private key PKs.

Further, when the receipt information stored in the blockchain 10 is transmitted to the insurance company terminal via the insured terminal, it is advantageous for the insured (for example, a large amount of benefit is paid). There is a possibility that the receipt information will be falsified. However, since the correct receipt information is stored in the blockchain 10 which is difficult to falsify, the insurance company can compare the receipt information from the insured terminal with the receipt information registered in the blockchain 10. , It is possible to easily detect whether or not the receipt information from the insured terminal has been tampered with. Therefore, in the present embodiment, it is possible to secure a high degree of falsification resistance in the management of the receipt information, and it is possible to reduce the possibility that the insurance company will be damaged by fraudulent claims.

Further, in the present embodiment, the information included in the matching condition is the insured person ID, and the payment condition of the benefit peculiar to each insurance company is not included. Therefore, even when the blockchain 10 is shared by a plurality of insurance companies, it is possible to avoid disclosure of the payment terms and the like of each insurance company to other insurance companies. In addition, matching conditions can be outside the scope of the effects of changes in payment conditions.

Further, since the collation target of the matching condition is the insured person ID and not the receipt information, the encrypted receipt information can be registered in the blockchain 10. As a result, for example, as shown in FIG. 12, what the administrator of the blockchain 10 can refer to is the encrypted receipt information. Therefore, even the administrator can hide the contents of the receipt information.

In the present embodiment, the insured person's private key SKi is an example of the first secret key. The insured public key PKi is an example of the first public key. The insured person terminal 20 is an example of the first terminal. The insurance company private key SKc is an example of a second private key. The insurance company private key PKc is an example of a second public key. The insurance company terminal 30 is an example of a second terminal. The insured person ID is an example of patient identification information. The receipt information notification unit 13 is an example of a transmission unit.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to such specific embodiments, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed.

1 Information processing system 10 Blockchain 11 Receipt information receiving unit 12 Condition judgment unit 13 Receipt information notification unit 14 Inquiry response unit 15 Ledger 20 Insured person terminal 21 Client unit 30 Insurance company terminal 31 Insurance company processing unit 40 Medical institution terminal 41 Medical Engine processing unit 50 Health insurance terminal 51 Health insurance processing unit 100 Drive device 101 Recording medium 102 Auxiliary storage device 103 Memory device 104 CPU
105 Interface device B bus

Claims (9)

1. In the control method executed in the information processing device
   When it is detected that the patient's receipt information is stored in the blockchain, the patient's receipt information is transmitted to the destination according to the patient before being transmitted to the destination according to the insurance company contracted by the patient.
   A control method characterized by a computer performing processing.
2. When the first terminal receives the receipt information of the patient transmitted to the destination corresponding to the patient, the first terminal transmits the received receipt information of the patient to the insurance company contracted by the patient. When it is determined whether or not the operation has been accepted and the operation to be transmitted to the insurance company is accepted, the receipt information of the patient is transmitted to the destination corresponding to the insurance company.
   The control method according to claim 1, wherein the control method is characterized by the above.
3. When the second terminal receives the patient's receipt information transmitted to the destination corresponding to the insurance company, the second terminal receives the received patient's receipt information and the patient's receipt information stored in the blockchain. Based on the result of comparison with the receipt information, it is determined whether or not the received receipt information of the patient has been tampered with.
   The control method according to claim 2, wherein the control method is characterized by the above.
4. The patient's receipt information is encrypted by a first public key corresponding to the first private key held by the patient, and the patient's receipt information transmitted to a destination corresponding to the patient is first. When the terminal receives it, the first terminal decrypts the received receipt information of the patient with the first private key and transmits the receipt information of the patient to the insurance company contracted by the patient. When it is determined whether or not the patient has been accepted and the operation to be transmitted to the insurance company is accepted, the patient's receipt information decrypted by the first private key is stored in the second secret held by the insurance company. It is encrypted with the second public key corresponding to the key and sent to the destination corresponding to the insurance company.
   The control method according to claim 1, wherein the control method is characterized by the above.
5. When the second terminal receives the receipt information of the patient transmitted to the destination corresponding to the insurance company, the second terminal decodes the received receipt information of the patient with the second private key, and the above-mentioned The patient's receipt information decrypted by the second private key is encrypted by the first public key, and the patient's receipt information encrypted by the first public key and the said patient's receipt information stored in the blockchain. Based on the comparison result with the patient's receipt information, it is determined whether or not the received patient's receipt information has been tampered with.
   The control method according to claim 4, wherein the control method is characterized by the above.
6. The patient's receipt information is stored in the blockchain in association with the patient's identification information.
   The information processing device detects that the receipt information of the patient is stored in the blockchain based on the identification information of the patient.
   The control method according to any one of claims 1 to 5, characterized in that.
7. When it is detected that the patient's receipt information is stored in the blockchain, the patient's receipt information is transmitted to the destination according to the patient before being transmitted to the destination according to the insurance company contracted by the patient.
   A control program characterized by having a computer execute processing.
8. When it is detected that the patient's receipt information is stored in the blockchain, the transmitter that transmits the patient's receipt information to the destination according to the patient before transmitting the receipt information to the destination according to the insurance company contracted by the patient. ,
   An information processing device characterized by having.
9. When it is detected that the patient's receipt information is stored in the blockchain, the transmitter that transmits the patient's receipt information to the destination according to the patient before transmitting the receipt information to the destination according to the insurance company contracted by the patient. ,
   An information processing system characterized by having.

Images