Insurance payment system, information processing method, and program

Abstract

To allow a user to easily know a possibility to pay an insurance claim.SOLUTION: An insurance payment system according to one aspect of the present technology acquires identification information associated with a My Number (the Social Security and Tax Number) of an insured person and medical information representing details of treatment performed on the insured person, and reads out information relating to payment criteria of an insurance which the insured person subscribes to, based on one or more insurance subscription numbers associated with the identification information. The insurance payment system determines whether or not there is a possibility to pay an insurance claim based on the medical information and the payment criteria, and sends a notice to a recipient associated with the identification information that there is the possibility to pay the insurance claim if it is determined that there is the possibility to pay the insurance claim. This technology can be applied to a system used by insurance subscribers and insurance companies.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present technology particularly relates to an insurance payment system, an information processing method, and a program that enable a user to easily know that an insurance payment is possible.

Background Art

[0002] In order to receive insurance benefits for life insurance or medical insurance, it is necessary for the insured or a relative of the insured to submit an application indicating that the insurance is to be applied to the insurance company.

[0003] For example, when applying for insurance coverage, the applicant fills in a template of an application form prepared in advance by the insurance company to create an application form, and submits the application form and supporting documents (e.g., a certificate from a medical institution) to the insurance company. The insurance company conducts a review based on the documents submitted by the insured and pays the insurance benefit after confirming that the reason for payment of the insurance benefit is met.

[0004] The insurance company expends a great deal of effort to prevent payment omissions. Therefore, various systems have been proposed as systems for preventing payment omissions (Patent Document 1).

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] Insurance benefit payment applications are often made immediately after an unfortunate event occurs to the insured or a relative of the insured. An application in such a state may be physically or mentally difficult.

[0007] This technology was developed in light of these circumstances, and aims to make it easy for users to know if they are eligible for insurance payment. [Means for solving the problem]

[0008] One aspect of this technology is an insurance payment system, which includes an acquisition unit that acquires identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person; a reading unit that reads out information regarding the payment criteria of the insurance to which the insured person subscribes based on one or more insurance subscription numbers linked to the identification information; a determination unit that determines whether or not there is a possibility of insurance payment based on the medical information and the payment criteria; and a recommendation unit that, if it is determined that there is a possibility of insurance payment, sends a notification to a first destination linked to the identification information that there is a possibility of insurance payment.

[0009] In one aspect of this technology, identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person are acquired, and information regarding the payment criteria of the insurance the insured person is enrolled in is read based on one or more insurance enrollment numbers linked to the identification information. Furthermore, it is determined whether or not there is a possibility of insurance payment based on the medical information and the payment criteria, and if it is determined that there is a possibility of insurance payment, a notification of the possibility of insurance payment is sent to the recipient linked to the identification information. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example of a user of an insurance payment platform realized by an information processing system according to one embodiment of this technology. [Figure 2] This diagram shows the overall flow of information provision by the insurance payment platform. [Figure 3] This diagram shows an example of interaction between an insurance company and a user. [Figure 4] This diagram shows the relationship between My Number (Japan's social security number) and insurance enrollment number. [Figure 5] It is a diagram showing the flow of pre - preparation. [Figure 6] It is a diagram showing an example of subscriber management information. [Figure 7] It is a diagram showing the flow of processing from when a user visits a medical institution until the eligibility information for health insurance is confirmed. [Figure 8] It is a diagram showing an example of a consent confirmation screen. [Figure 9] It is a diagram showing an example of eligibility information provided to a medical institution. [Figure 10] It is a diagram showing the flow of processing from when eligibility information is confirmed until an insurance payment recommendation is sent. [Figure 11] It is a diagram showing an example of an insurance payment recommendation. [Figure 12] It is a diagram showing an example of a confirmation of intention screen. [Figure 13] It is a block diagram showing an example of the configuration of a PF management server. [Figure 14] It is a block diagram showing an example of the functional configuration of a PF management server. [Figure 15] It is a flowchart for explaining the processing of a PF management server. [Figure 16] It is a diagram showing an example of a blockchain database. [Figure 17] It is a diagram showing an example of transaction data. [Figure 18] It is a diagram showing an example of transaction data. [Figure 19] It is a diagram showing an example of an inference model.

Modes for Carrying Out the Invention

[0011] Hereinafter, the modes for carrying out the present technology will be described. The description will be made in the following order. [[ID=5……]] 2. Pre - preparation 3. Flow of the overall processing 4. Configuration and operation of the PF management server 5. Variants​

[0012] <Regarding the Insurance Payment Platform> FIG. 1 is a diagram showing an example of users of an insurance payment platform realized by an information processing system according to an embodiment of the present technology.

[0013] As shown in FIG. 1, medical institutions, insurance companies, and users become the main users of the insurance payment platform. In the example of FIG. 1, two medical institutions and two insurance companies are shown respectively, but more medical institutions and insurance companies become users of the insurance payment platform.

[0014] A medical institution is a hospital, clinic, nursing home for the elderly, pharmacy that dispenses drugs, or other facility that provides medical care as defined by laws related to medicine. A medical institution is, for example, an institution corresponding to insurance medical treatment using health insurance defined by the Health Insurance Law.

[0015] An insurance company is a company that sells insurance products including contracts that pay insurance money when the insured person receives medical treatment, such as life insurance, medical insurance, and fire insurance. In the following, examples of insurance products for insurance medical treatment will be described, but free medical treatment may also be targeted.

[0016] As shown at the bottom of FIG. 1, a user is a subscriber of insurance sold by an insurance company. The user becomes the insured person with respect to the insurance company that is the insurer. Also, when the user receives medical treatment at a medical institution, the user becomes a patient. Appropriately, the user may be simply described as the user, or as an insurance subscriber. Also, the user may be described as the insured person, or as the patient.

[0017] The insurance payment platform is a system that provides various services, such as presenting insurance-related information to the user and the insurance company when the user receives insurance medical treatment as a patient.

[0018] FIG. 2 is a diagram showing the overall flow of information provided by the insurance payment platform.

[0019] The various functions of the insurance payment platform are implemented by the PF (Platform) Management Server 1, which is an information processing device on the Internet. The PF Management Server 1 is composed of a single computer or multiple computers working together.

[0020] The following describes the processes required to implement the functions of the insurance payment platform, as processes performed by PF Management Server 1. The processing for medical institutions and insurance companies is basically handled by their respective business management systems.

[0021] PF Management Server 1 has an Insurance Subscriber DB2, which is a database of subscriber management information containing information about insurance subscribers. Subscriber management information includes information about the insurance each user is enrolled in, each user's My Number, and the recipient of notifications from the insurance payment platform. My Number is a social security and tax number established by a government agency. The following explains an example using My Number. Note that if a health insurance card is linked to or functions as a health insurance card and has an identifier set for each individual, that identifier may be used instead of My Number.

[0022] As shown by arrow A1, the user visits a medical institution and presents their My Number Card at the reception desk. A card reader for reading My Number Cards is installed at the reception desk of the medical institution. By registering using the My Number Card, the user can receive insured medical treatment. Alternatively, a device with equivalent functionality to the My Number Card may be used. For example, an application with a My Number set up may be used.

[0023] In other words, the insurance payment platform is a system that assumes health insurance cards are linked to My Number (Japan's social security and tax number). Users will need to register using their My Number card instead of their health insurance card before receiving medical treatment.

[0024] After presenting your My Number Card, your health insurance eligibility information will be verified. Details of this process will be described later.

[0025] When a medical consultation is completed, medical information is created at the medical institution. Medical information includes information that describes the content of the medical treatment, such as a medical claim form (receipt) or a medical receipt. Below, we will explain medical information using a medical claim form as an example. A medical claim form is a detailed statement that describes the treatments performed on a patient, etc., so that the medical institution can claim medical expenses from the health insurance association. Medical claim forms are generated as electronic information on the medical institution's terminal. When using medical claim forms, the target is insured medical treatment, but private medical treatment may also be included using other medical information. For example, the medical institution may use information generated by entering the details of medical treatment, including both insured and private medical treatment, into a format that allows for the entry of medical treatment details, as medical information. In this case, the details of insured medical treatment may be automatically entered based on the medical claim form.

[0026] As shown by arrow A2, the medical institution provides the claim form to the PF management server 1. As will be described later, the provision of the claim form to the insurance payment platform is performed only if the user has consented to the provision of the claim form.

[0027] PF Management Server 1 refers to subscriber management information stored in Insurance Subscriber DB 2 to identify the insurance policy the user is enrolled in. Based on the medical claim and the payment criteria of the insurance policy the user is enrolled in, PF Management Server 1 determines whether or not there is a possibility of insurance payment.

[0028] If the PF management server 1 determines that there is a possibility of insurance payment, it sends a notification to the user, as shown by arrow A3. The notification to the user is sent using various means, such as email or SNS messages.

[0029] Hereafter, any notification that there is a possibility of insurance payment will be referred to as an "insurance claim recommendation," meaning a notification that encourages the user to receive the insurance payment.

[0030] Furthermore, if the user has agreed to provide the claim to the insurance company, which is the insurer, the PF management server 1 will provide the claim and share it with the insurance company, as shown by arrow A4.

[0031] Insurance companies that share claims with the insurance payment platform verify whether the determination that there is a possibility of insurance payment is correct by comparing the content of the claim with the content of the insurance policy the user has. If the determination that there is a possibility of insurance payment is correct, the insurance company will contact the user and provide information on necessary documents, as shown by arrow A4 in Figure 3.

[0032] Once the insurance company is able to pay the insurance claim, such as after receiving the necessary documents from the user, it will pay the insurance claim to the user as shown by arrow A5.

[0033] Thus, in the insurance payment platform, the process of paying insurance benefits when a user receives insured medical treatment is triggered by a notification from the insurance payment platform (PF management server 1).

[0034] The traditional process for insured individuals to receive insurance payments for medical treatment covered by insurance is as follows: After receiving medical treatment, policyholders should recall the details of their life insurance, medical insurance, and fire insurance (group credit life insurance) policies and determine whether they are eligible to receive insurance benefits for their illness (diagnosis) as stated in the medical certificate issued by the medical institution. If they determine that they are eligible to receive insurance benefits, the policyholder should contact their insurance company. The insurance company will explain the required documents to the policyholder and conduct a review based on the documents submitted by the policyholder (such as medical certificates). The insurance company will pay the insurance benefit if the policyholder's illness qualifies as a cause for payment.

[0035] Thus, in the conventional process of paying out insurance claims for voluntary insurance, the insurance company cannot know the condition of the insured person unless the insured person takes action.

[0036] Furthermore, when policyholders need to file a claim with their insurance company, it is often after suffering a serious illness or undergoing surgery, making it difficult for them to even consider filing a claim.

[0037] As mentioned above, because the process of receiving insurance payments for medical treatment is triggered by a notification from the insurance payment platform, users can easily find out if they are eligible for insurance payments, even if they are not familiar with the details of their insurance policy. Users can prevent missing out on insurance payment claims without having to file a claim themselves.

[0038] Furthermore, insurance companies can contact users and begin discussions regarding insurance payments without waiting for them to submit an insurance claim application. This allows insurance companies to prevent missed insurance payments.

[0039] <Preparation> In order for users to receive insurance payout recommendations, their My Number (social security number) and insurance policy number must be linked, as shown in Figure 4.

[0040] An insurance policy number is an identification number for policyholders issued by the insurance payment platform. Each user is issued an insurance policy number.

[0041] The process of linking My Number (social security number) with insurance enrollment number is carried out as a preliminary step.

[0042] Figure 5 shows the flow of the preparation process.

[0043] As indicated by arrow A11, an insurance enrollment number is issued to the user. The insurance enrollment number is issued, for example, by the PF management server 1 when the user registers as a user of the insurance payment platform.

[0044] When a user who has received an insurance subscription number subscribes to optional insurance such as life insurance or medical insurance sold by an insurance company, they notify the insurance company of their user information to the insurance payment platform via the insurance company, as shown by arrow A12.

[0045] User information includes user ID, password, name, My Number (social security number), recipient, and insurance ID.

[0046] A User ID is an identification piece of information set, for example, when registering a user on an insurance payment platform. The User ID is a different identification piece of information from the insurance enrollment number mentioned above.

[0047] The password is used to access the insurance payment platform services. A website is provided for accessing the insurance payment platform services. Users can access the insurance payment platform services by logging in to the website using their user ID and password.

[0048] The name is the user's name.

[0049] My Number is the user's My Number.

[0050] The recipient is the destination for notifications from the insurance payment platform, such as insurance claim recommendation notifications. For example, the user's email address is set as the recipient. The recipient of notifications such as insurance claim recommendation notifications is registered by the user.

[0051] The insurance ID is the identification information for the insurance policy a user has purchased. Each insurance product from each insurance company is assigned a unique ID.

[0052] Based on the user information including the above information, the PF management server 1 registers subscriber management information in the insurance subscriber DB2, as shown by arrow A13.

[0053] Figure 6 shows an example of subscriber management information.

[0054] As shown in Figure 6, subscriber management information consists of the user ID, password, name, My Number, recipient, and insurance ID provided as user information, along with the insurance enrollment number.

[0055] The insurance enrollment number is the insurance enrollment number issued to the user. The insurance enrollment number issued to the user is identified based on the user ID, etc., and included in the enrollment information. Once the enrollment information is registered, the My Number and the insurance enrollment number become linked on the insurance payment platform.

[0056] In the example shown in Figure 6, Insurance ID-1, Insurance ID-2, and Insurance ID-3 are shown as insurance IDs for the insurance policies that the user subscribes to. For example, each time a user subscribes to a new insurance policy, an additional insurance ID is added and registered.

[0057] Thus, in the insurance payment platform, not only are My Number and insurance policy numbers linked, but various identification information such as My Number and insurance policy numbers are also linked to the user ID. It is also possible to link not just one insurance policy number to a single user ID, but multiple insurance policy numbers.

[0058] PF Management Server 1 manages the contact information (notification recipients) for each insurance company and the insurance ID information sold by each insurance company. By associating an insurance ID with a user ID, the notification recipients for each insurance company are also associated with the user ID.

[0059] When subscriber management information is registered, as shown by arrow A14 in Figure 5, the PF management server 1 requests the eligibility verification agency to register the My Number and insurance membership number in association. The request to the eligibility verification agency is made by sending information to the eligibility verification agency's system requesting that a specific insurance membership number be registered in association with a specific My Number user.

[0060] The eligibility verification body's system verifies the My Number in response to a request from PF management server 1 and stores the insurance enrollment number on a server managed by the eligibility verification body. On the server managed by the eligibility verification body, the insurance enrollment number is stored linked to the My Number.

[0061] Through the preparatory processes described above, the insurance enrollment number will be linked to the My Number at both the insurance payment platform and the eligibility verification body.

[0062] Furthermore, the insurer membership number can be any type of identification information as long as it is an ID that can identify the user. Identification information linked to the insurer membership number may be generated, and this generated identification information may be stored on the eligibility verification body's server in place of the insurer membership number.

[0063] It would be acceptable to replace the My Number itself with the insurance enrollment number.

[0064] <Overall processing flow> Here, we will explain the processing flow of each device until the user receives the insurance claim recommendation.

[0065] The entire process leading up to a user receiving an insurance claim recommendation can be broadly divided into two parts: the process from when the user visits a medical institution until their health insurance eligibility information is verified, and the process from when the eligibility information is verified until the insurance claim recommendation is sent.

[0066] Figure 7 shows the process flow from when a user visits a medical institution to when their health insurance eligibility information is verified. A medical institution is, for example, a medical facility or pharmacy that can provide medical treatment.

[0067] When a user visits a medical institution as a patient due to illness or other reasons, they have their My Number Card read by the card reader 11, as shown by arrow A21. A card reader 11 that reads the information stored on the IC chip of the My Number Card is installed at the reception desk of the medical institution.

[0068] When presenting a My Number Card, consent is confirmed regarding the provision of medical claim data to the insurance payment platform. This consent confirmation is performed, for example, using a consent confirmation screen displayed on the display of the card reader 11.

[0069] Figure 8 shows an example of a consent confirmation screen.

[0070] As shown in Figure 8, the consent confirmation screen displays a message asking the user whether they consent to providing the medical claim to the insurance payment platform. Below the message, there are buttons to press to consent and buttons to press to disagree. The card reader 11's display may be, for example, a touch panel.

[0071] The user views this consent confirmation screen and selects whether or not they consent to providing the medical claim to the insurance payment platform. If the user consents to providing the medical claim, consent information is generated and stored in the card reader 11. A timestamp is added to the consent information.

[0072] At the time of registration at a medical institution, consent information may be generated if consent is obtained using a registration device. For example, a device other than the card reader 11, such as a tablet terminal, may be used as the registration device.

[0073] If consent is obtained from the patient or their family, that information may be entered into the medical institution's PC, and the consent information may be generated on the medical institution's PC. In this case, confirmation of the patient's or their family's consent will be done using a paper consent form.

[0074] Medical institutions may use a reception device or paper instead of My Number cards for registration. In this case, the card reader 11 becomes a device for verifying the validity of the electronic certificate stored on the My Number card.

[0075] The card reader 11, having read the electronic certificate from the My Number Card, transmits the electronic certificate to the online eligibility verification system 13 (the online eligibility verification system of the Payment Fund and the National Health Insurance Association) managed by the eligibility verification body, as shown by arrow A22, and requests eligibility information. If the user has consented to providing the medical claim to the insurance payment platform, eligibility information with the insurance enrollment number is requested from the online eligibility verification system 13.

[0076] Furthermore, online eligibility verification utilizes a system that centrally manages the eligibility information of all citizens, and is a mechanism that allows for online verification of the details of a patient's health insurance plan based on their My Number Card.

[0077] The online eligibility verification system 13 queries the public personal authentication service (not shown) managed by the Local Government Information Systems Organization for the validity of the electronic certificate. If the electronic certificate is invalid, the online eligibility verification system sends information to the medical institution's business terminal 12 indicating that the electronic certificate is invalid and that eligibility information cannot be obtained.

[0078] On the other hand, if the electronic certificate is valid, the online credential verification system 13 reads the credential information linked to the electronic certificate (credential information linked to the My Number linked to the electronic certificate) from the intermediate server 14, as shown by arrow A23. The intermediate server 14 is a server that manages the My Numbers of all citizens and various other information, including credential information.

[0079] The online eligibility verification system 13 adds the insurance enrollment number to the eligibility information read from the intermediate server 14 and transmits it to the medical institution's business terminal 12, as shown by arrow A24.

[0080] Figure 9 shows an example of eligibility information provided to a medical institution.

[0081] As shown in Figure 9, eligibility information includes name, gender, date of birth, insurer name, insured person symbol number (health insurance), acquisition and loss information, and insurance enrollment number.

[0082] The insurance enrollment number attached to the eligibility information is the insurance enrollment number that was linked to the My Number and managed by the eligibility verification body through a pre-preparation process (Figure 5).

[0083] Alternatively, the insurance enrollment number may be obtained not when acquiring eligibility information, but when the medical institution makes an inquiry. For example, if the insurance enrollment number is linked to the My Number and managed in the My Number Portal, an inquiry can be made from the medical institution's work terminal 12 to the My Number Portal (the system that manages the My Number Portal), and the insurance enrollment number can be obtained in response to that inquiry.

[0084] As shown in Figure 7, the business terminal 12, which has acquired an insurance enrollment number with attached eligibility information, stores the eligibility information and patient ID in a linked manner. The patient ID is patient identification information issued by the medical institution.

[0085] The above process takes place when the user presents their My Number Card to the card reader 11 at the medical institution's reception desk. After the registration process, including the presentation of the My Number Card, is complete, the user will receive a medical examination. Treatment, medication, drug provision, hospitalization, etc., may be provided in lieu of or in conjunction with the medical examination.

[0086] Figure 10 shows the process flow from verifying eligibility information to sending insurance claim recommendations.

[0087] Once the examination of the patient (user) is complete, the medical institution's operational terminal 12 creates a medical claim form (medical fee statement) by recording the details of the treatment in the electronic medical record, as shown on the far left of Figure 10.

[0088] If the medical institution that accepts My Number Card payments is a pharmacy, a dispensing fee statement will be created as a claim form. Similarly, if home nursing care is provided using a My Number Card, a home nursing care expense statement will be created as a claim form. The user's treatment details recorded in the claim form will include at least one of the following: medical treatment, dispensing of medication, or nursing care.

[0089] If the user agrees to provide the medical claim to the insurance payment platform, the medical institution's business terminal 12 sends the medical claim to the PF management server 1, as shown by arrow A31.

[0090] For example, if the consent information includes information indicating that the user has consented to providing the claims, or if the eligibility information sent by the eligibility verification body includes the insurance enrollment number, the user will be deemed to have consented to providing the claims to the insurance payment platform.

[0091] As shown in the callout in Figure 10, the medical claim form transmitted by the business terminal 12 includes the insurance enrollment number provided by the eligibility verification body.

[0092] As shown by the bidirectional arrow A32, the PF management server 1 refers to the subscriber management information stored in the insurance subscriber DB2 and identifies the type of insurance the user has based on the insurance subscriber number. Here, subscriber management information containing the same insurance subscriber number as the insurance subscriber number included in the medical claim is read from the insurance subscriber DB2, and the type of insurance the user has is identified based on the insurance ID included in the subscriber management information.

[0093] PF management server 1 estimates the user's diagnosis based on the contents of the medical claim form. The medical claim form contains information such as points, but does not record the diagnosis. The diagnosis may be estimated using an inference model generated by machine learning. The inference model is generated by machine learning using combinations of medical claim form contents and diagnosis names as training data.

[0094] PF management server 1 determines whether or not insurance benefits can be paid by comparing the estimated disease name with the insurance payment criteria. The determination of whether or not insurance benefits can be paid is whether or not there is a possibility of insurance benefits being paid.

[0095] If the PF management server 1 determines that there is a possibility of insurance payment, it sends an insurance claim recommendation to the insured user, as shown by arrow A33. The insurance claim recommendation is sent, for example, by email. The recipient of the email is identified based on information (Figure 6) that was managed in the subscriber management information linked to the insurance subscription number.

[0096] Furthermore, it may be possible to manage multiple recipients by linking them to the insurance policy number. This would allow relatives of the insured person to be notified of the possibility of insurance payouts.

[0097] Figure 11 shows an example of an insurance claim recommendation using email.

[0098] As shown in Figure 11, the email body contains a message informing the recipient that they may be eligible to receive insurance benefits. The message also includes a URL to access if they wish to confirm their intention to receive the insurance benefits.

[0099] If a user views such an email on a device such as a smartphone and selects the URL, a web browser will launch and access the URL. The web browser will then display a confirmation screen. The display of insurance payout recommendations and the confirmation screen may also be handled by a dedicated application.

[0100] Figure 12 shows an example of a screen for confirming intent.

[0101] As shown in Figure 12, the confirmation screen displays a message asking whether the user wants to check with the insurance company to see if they are eligible to receive insurance benefits for medical treatment received at a medical institution.

[0102] A message will also appear asking whether you agree to share your medical claims with your insurance company. You will also be informed that sharing your claims will streamline communication with your insurance company.

[0103] If it is chosen to check with the insurance company, PF management server 1 notifies the insurance company that there is a possibility of insurance payment by sending the user's information to the insurance company.

[0104] Furthermore, if it is chosen to confirm with the insurance company and share the claim form, the PF management server 1 will send the claim form and notify the insurance company that there is a possibility of insurance payment, as shown by arrow A34 in Figure 10.

[0105] Upon receiving a notification from PF management server 1, the insurance company contacts the insured and verifies the necessary documents for receiving the insurance payment. The communication between the insurance company and the insured may also be conducted using the communication function provided on the insurance payment platform.

[0106] In this way, by using the insurance payment platform, insured individuals can receive notification of potential insurance payouts simply by visiting a medical institution. Even if insured individuals have multiple insurance policies, they do not need to compare their illness with the payment criteria of each insurance company.

[0107] On the other hand, insurance companies can easily confirm that an insurance claim payment has occurred.

[0108] The documents required to receive insurance benefits can vary depending on the insurance company. By using an insurance payment platform for initial confirmation of eligibility for insurance payments and communication with the insured by the insurance company for secondary confirmation, it becomes possible to process insurance payments without significantly changing the insurance company's workflow.

[0109] It is conceivable that the decision on whether or not to pay insurance claims could be made within the medical institution's reception system using the insured person's insurance enrollment number and medical claim form. However, in this case, the information in the reception system would need to be updated every time a new insurance policy is created, which is not practical.

[0110] Furthermore, because different insurance companies have different criteria for diagnosing illnesses, it is difficult for medical institutions to determine eligibility for insurance payments within their reception systems. Also, since a single user may have multiple insurance policies, determining eligibility for all policies takes considerable time.

[0111] By having the decision on whether or not to pay insurance claims made on the insurance payment platform, it becomes possible to easily determine whether or not there is a possibility of paying insurance claims without placing such a burden on medical institutions.

[0112] <Configuration and Operation of PF Management Server 1> · Configuration of PF Management Server 1 FIG. 13 is a block diagram showing a configuration example of PF Management Server 1.

[0113] As shown in FIG. 13, PF Management Server 1 is configured by a computer. PF Management Server 1 may also be configured by a plurality of computers. When PF Management Server 1 is configured by a plurality of computers, each computer cooperates to realize the various processes described above.

[0114] A CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, and a RAM (Random Access Memory) 103 are interconnected by a bus 104.

[0115] An input / output interface 105 is further connected to the bus 104. An input unit 106, an output unit 107, a storage unit 108, a communication unit 109, and a drive 110 are connected to the input / output interface 105.

[0116] The input unit 106 is composed of a keyboard, a mouse, etc. The output unit 107 is composed of a display, etc.

[0117] The storage unit 108 is composed of a hard disk, a non-volatile memory, etc. The storage unit 108 stores various information such as programs executed by the CPU 101.

[0118] The communication unit 109 is an interface to the Internet. For example, the communication unit 109 communicates with the business terminal 12 of a medical institution and receives the receipt transmitted from the business terminal 12. Also, the communication unit 109 communicates with the business terminal of an insurance company and transmits the receipt of a user who may receive insurance payment to the insurance company.

[0119] Drive 110 controls the writing of data to and reading of data from the removable media 111.

[0120] Figure 14 is a block diagram showing an example of the functional configuration of the PF management server 1. At least some of the functional units shown in Figure 14 are realized by the execution of a predetermined program by the CPU 101 shown in Figure 13.

[0121] As shown in Figure 14, an information processing unit 121 is implemented in the PF management server 1. The information processing unit 121 consists of an acquisition unit 131, a reading unit 132, a payment eligibility determination unit 133, a recommendation unit 134, and a transmission control unit 135.

[0122] The acquisition unit 131 controls the communication unit 109 to receive and acquire user information transmitted from the insurance company during the preparation phase. The user information acquired by the acquisition unit 131 is supplied to the insurance subscriber DB2 and stored as subscriber management information along with the insurance subscriber number.

[0123] Furthermore, the acquisition unit 131 communicates with the medical institution's business terminal 12. The acquisition unit 131 receives and acquires the medical claim forms transmitted from the business terminal 12. The medical claim forms acquired by the acquisition unit 131 are supplied to the payment eligibility determination unit 133 and the transmission control unit 135.

[0124] The user information acquired by the acquisition unit 131 includes identification information, including a user ID, linked to the My Number. The acquisition unit 131 functions as an acquisition unit that acquires identification information linked to the insured person's My Number and the insured person's medical claim form.

[0125] The reading unit 132 reads the user's subscriber management information from the insurance subscriber DB2 based on the insurance subscriber number included in the medical claim. The subscriber management information read by the reading unit 132 is supplied to the payment eligibility determination unit 133, the recommendation unit 134, and the transmission control unit 135.

[0126] Furthermore, the reading unit 132 reads information regarding the payment criteria for insurance claims for the insurance policy the user is subscribed to from the insurance subscriber DB2, based on the insurance ID included in the subscriber management information. The information regarding the payment criteria for insurance claims read by the reading unit 132 is supplied to the payment eligibility determination unit 133.

[0127] The reading unit 132 functions as a reading unit that reads information regarding the criteria for insurance payment based on the insurance subscription number linked to the identification information in the subscriber management information.

[0128] The policyholder DB2 also stores information regarding the payment criteria for each insurance policy. The policyholder DB2 may be built on the storage unit 108, or it may be built as an external database.

[0129] The payment eligibility determination unit 133 determines whether or not to pay insurance benefits by comparing the medical claim form supplied from the acquisition unit 131 with the insurance benefit payment criteria supplied from the reading unit 132. The payment eligibility determination is performed, for example, by estimating the user's illness and symptoms based on the medical claim form and comparing the estimated illness and other information with the insurance benefit payment criteria. Information representing the result of the insurance benefit payment eligibility determination is supplied to the recommendation unit 134 and the transmission control unit 135.

[0130] The recommendation unit 134 sends an insurance claim recommendation to the user if it determines that there is a possibility of insurance payment. The insurance claim recommendation is sent from the communication unit 109 according to the control of the recommendation unit 134. The destination of the insurance claim recommendation is the destination included in the subscriber management information.

[0131] Furthermore, if the recommendation unit 134 determines that there is no possibility of insurance payment, it sends a notification to the user indicating this.

[0132] If the transmission control unit 135 determines that there is a possibility of insurance payment, it controls the communication unit 109 and transmits information to the insurance company indicating this.

[0133] Furthermore, if the user has consented to providing the claim, the transmission control unit 135 transmits the claim supplied by the acquisition unit 131 to the insurance company. The transmission control unit 135 functions as a transmission unit that transmits the claim to the insurance company based on the user's consent as a response to the insurance claim recommendation.

[0134] • Operation of PF Management Server 1 Now, referring to the flowchart in Figure 15, we will explain the processing of the PF management server 1 having the above configuration.

[0135] In step S1, the acquisition unit 131 acquires the medical claim form transmitted from the medical institution's business terminal 12.

[0136] In step S2, the reading unit 132 reads the user's subscriber management information from the insurance subscriber DB2 based on the insurance subscriber number included in the medical claim. The reading unit 132 also reads information regarding the payment criteria of the insurance the user is subscribed to from the insurance subscriber DB2 based on the insurance ID included in the subscriber management information.

[0137] In step S3, the payment eligibility determination unit 133 determines whether or not to pay the insurance benefit by comparing the disease name estimated based on the medical claim with the insurance benefit payment criteria.

[0138] In step S4, the payment eligibility determination unit 133 determines whether or not there is a possibility of paying the insurance claim.

[0139] If it is determined in step S4 that there is a possibility of insurance payment, in step S5 the recommendation unit 134 sends an insurance payment recommendation, which is a notification that there is a possibility of insurance payment, to the registered user's recipient.

[0140] In step S6, the transmission control unit 135 sends a notification to the insurance company, along with the medical claim form, indicating that there is a possibility of insurance payment. The medical claim form is sent only if the user has given their consent.

[0141] After that, processing on PF Management Server 1 is completed. Similarly, if it is determined in step S4 that there is no possibility of insurance payment, the user will be notified of the lack of possibility of insurance payment as appropriate, and then processing will be completed.

[0142] <Variation> While the assessment of the likelihood of paying out insurance benefits for medical and life insurance is intended to be performed on the insurance payment platform, the assessment of the likelihood of paying out benefits for other types of voluntary insurance may also be performed on the insurance payment platform.

[0143] For example, it is possible to have the determination of the likelihood of paying out fire insurance and earthquake insurance claims performed on the insurance payment platform. In this case, the same processing described above, which is performed at medical institutions, would be carried out at police stations and local government offices.

[0144] The insurance payment platform may be configured to accept only information from registered institutions, such as specific medical institutions. In this case, each institution would be assigned an institution identification code. By performing authentication using the institution identification code on the insurance payment platform before sending or receiving claims, including insurance enrollment numbers, the risk of insurer enrollment numbers and claims being leaked externally can be reduced.

[0145] • Example using a blockchain database The assessment result regarding the likelihood of insurance payment may be stored in conjunction with information such as the insurance policy number and insurance ID.

[0146] Since fraudulent activities can occur during transactions related to insurance payouts, it is necessary to keep accurate records of all such transactions. Furthermore, insurance companies need to verify whether they have fulfilled all their payment obligations.

[0147] A blockchain database is used to store information regarding the determination of the likelihood of insurance payment. The blockchain database also stores information on whether or not the insurance payment has been completed.

[0148] Figure 16 shows an example of a blockchain database that stores judgment result information.

[0149] As shown in Figure 16, a consortium-type blockchain network 201 is used as the blockchain database. Blockchain network 201 is a P2P network composed of multiple nodes managed by multiple participants. A node is a device such as a server. A single node may consist of one device, or it may consist of multiple devices.

[0150] The blockchain network 201 can store various types of information from the PF management server 1 and the insurance company's server 202. For example, a separate server 202 is provided for each insurance company.

[0151] As described above, if the PF management server 1 determines that there is a possibility of insurance payment, it stores the determination result information, including the insurance enrollment number and insurance ID, in the blockchain network 201. Because this is highly sensitive personal information, it is preferable not to store the medical claim forms provided by medical institutions in the blockchain network 201.

[0152] When an insurance company receives notification from PF management server 1 that there is a possibility of paying an insurance claim, it also makes a determination itself as to whether or not payment is possible and communicates the result of that determination to the insurance payment platform. After communicating the result of the determination as to whether or not payment is possible to the insurance payment platform, server 202 stores in blockchain network 201 information indicating whether or not payment of the insurance claim has been completed for the insurance that was determined to have a possibility of payment.

[0153] Figure 17 shows an example of transaction data stored in the blockchain network 201 by the PF management server 1.

[0154] As shown in Figure 17, the transaction data generated by the PF management server 1 includes the electronic signature of the insurance payment platform, the public key of the insurance payment platform, the address of the insurance payment platform, the recipient address, the insurance policy number, the insurance ID, and information indicating whether or not a notification of the possibility of insurance payment has been sent to the insurance company.

[0155] The recipient address represents the recipient address used by the insurance payment platform for sending insurance claim recommendations. It is preferable that the insurance policy number be encrypted, such as through hashing.

[0156] For example, if transaction data containing the information shown in Figure 17 is stored in the blockchain network 201, information indicating this is sent to the insurance company by, for example, the transmission control unit 135. The information sent to the insurance company includes the insurance policy number.

[0157] Figure 18 shows an example of transaction data stored in the blockchain network 201 by the server 202.

[0158] As shown in Figure 18, the transaction data generated by server 202 includes the insurance company's digital signature, the insurance company's public key, the insurance company's address, the recipient address, the insurance policy number, the insurance ID, and information indicating whether or not the insurance payment has been completed.

[0159] The recipient address represents the recipient of the insurance claim. It is preferable that the insurance policy number be encrypted using hashing or similar methods.

[0160] Transactions that write such transaction data are stored in blocks that make up the blockchain network 201. Each block stores multiple transactions along with the hash value of the previous block.

[0161] By ensuring that neither the transaction data generated by PF management server 1 nor the transaction data generated by server 202 includes medical information, it becomes possible to protect users' personal information.

[0162] Examples of information managed in the insurance payment platform Information indicating whether the insurance payment has been completed may be sent from the insurance company to the insurance payment platform and stored on the insurance payment platform. The insurance payment platform manages the information sent from the insurance company so that users can check at any time whether the insurance payment has been made.

[0163] For example, by accessing the insurance payment platform, users could be able to view information such as which insurance policies they have, when insurance payouts for each policy are being made, and how much their monthly premiums are. Furthermore, this information could be linked to their My Number (Social Security Number) and, with the user's consent, published on the My Number Portal.

[0164] • Examples of determinations in insurance payment platforms While the system is designed to determine whether or not there is a possibility of paying insurance benefits, the payment eligibility determination unit 133 may also determine the details of the payment, such as the amount of the insurance benefits, in addition to determining whether or not there is a possibility of paying insurance benefits. For insurance that covers exchanges other than money, the payment eligibility determination unit 133 may also determine the details of the coverage.

[0165] If it is determined that there is a possibility of insurance payment, the recommendation unit 134 will send a notification that there is a possibility of insurance payment, along with information describing the details of the payment, to at least one of the user and the insurance company.

[0166] Other determinations besides whether or not there is a possibility of paying insurance benefits may be made on the insurance payment platform.

[0167] For example, the insurance payment platform may determine whether a user who is an insured person has fulfilled their disclosure obligations for insurance purposes. This determination may be based, for example, on at least one of the following: past health checkup results obtained from the My Number Portal, and medical information representing the details of medical treatments the user has received in the past.

[0168] The determination of whether or not an insurance policyholder has fulfilled their disclosure obligations is made at predetermined times, such as when the user applies for insurance with the insurance company or when determining whether or not an insurance claim can be paid. The determination of whether or not an insurance policyholder has fulfilled their disclosure obligations may also be made with the user's consent and at the request of the insurance company.

[0169] Various decisions, including the determination of whether or not insurance claims can be paid, may be made using inference models generated by machine learning.

[0170] Figure 19 shows an example of an inference model provided in the payment eligibility determination unit 133.

[0171] As shown in Figure 19, the payment eligibility determination unit 133 is equipped with a payment eligibility determination model 133A used to determine whether or not insurance benefits can be paid. The payment eligibility determination model 133A is an inference model composed of a neural network or the like, generated by machine learning based on a genetic algorithm. For example, the payment eligibility determination model 133A is generated by machine learning based on a set of training data that links medical claims, types of insurance, and the results of the determination of the likelihood of insurance benefit payment. Note that medical claims may be other medical information that indicates the content of medical treatment.

[0172] For the payment eligibility determination model 133A, the medical claim and the type of insurance are input, and a determination result is output regarding whether or not there is a possibility of insurance payment. By using the payment eligibility determination model 133A, it is possible to determine whether or not there is a possibility of insurance payment based on the medical claim and the type of insurance.

[0173] The payment eligibility determination unit 133 may perform an analysis of the validity of multiple claims submitted from the same medical institution. In this case, a statistical analysis of the multiple claims is performed, and the analysis result indicates whether or not the claims are valid.

[0174] For example, if a statistically significant number of similar claims are found among claims submitted by a particular medical institution compared to those submitted by other medical institutions, it may be determined that fraudulent activity is possible, and an alert will be sent to the administrator of the insurance payment platform.

[0175] Thus, it is also possible to give the payment eligibility determination unit 133 the function of an analysis unit that performs statistical analysis of multiple claims sent from the same medical institution.

[0176] The appropriateness of each medical institution's diagnostic and treatment practices may be statistically determined based on multiple claims. For example, appropriateness could be determined based on whether or not a medical institution is performing excessive or insufficient diagnoses or treatments compared to other medical institutions. This would allow insurance companies to investigate medical institutions that are performing more appropriate diagnoses and treatments and recommend appropriate medical institutions to their policyholders.

[0177] • If you receive medical treatment without presenting your health insurance card, or if you receive treatment on a private-pay basis. If a patient receives medical treatment without presenting their health insurance card, or if the treatment is not covered by insurance, the medical institution may issue a notification letter linked to the medical information entered by the medical institution and send the letter to the user. The notification letter is a format for submitting the medical information to the insurance payment platform, and may be, for example, an email or an online response form. For example, if a user receives treatment not covered by insurance at a medical institution, the medical institution accesses the insurance payment platform and enters the details of the treatment according to the prescribed format. The insurance payment platform generates medical information and an online response form based on the entered medical information and links the medical information and the notification letter to a temporarily generated ID. The medical institution sends the user a URL for the online response form or a code (for example, a QR code) to access the online response form. The user accesses the online response form, enters their My Number, and submits it. Alternatively, instead of entering the My Number, the user may enter a user ID and password for user authentication. The insurance payment platform stores the medical information linked to the entered My Number or user ID and performs the above-mentioned insurance payment possibility determination and recommendation processing. This makes it easy for users to know that they may be eligible for insurance coverage even if they receive medical treatment without presenting their health insurance card or if the treatment is not covered by insurance.

[0178] • About the program The series of processes described above can be executed by hardware or by software. When the series of processes are executed by software, the programs that make up the software are installed on a computer that is built into dedicated hardware, or on a general-purpose personal computer.

[0179] The program to be installed is provided by recording it on removable media 111, as shown in Figure 13, which consists of optical discs (CD-ROM (Compact Disc-Read Only Memory), DVD (Digital Versatile Disc), etc.) or semiconductor memory. Alternatively, it may be provided via wired or wireless transmission media such as a local area network, the internet, or digital broadcasting. The program can be pre-installed in ROM 102 or storage unit 108.

[0180] The programs executed by the computer may be programs that are processed chronologically in the order described herein, or they may be programs that are processed in parallel or at necessary times, such as when they are called.

[0181] In this specification, a system means a collection of multiple components (devices, modules (parts), etc.), regardless of whether all components are located in the same enclosure. Therefore, multiple devices housed in separate enclosures and connected via a network, and a single device containing multiple modules in one enclosure, are both considered systems.

[0182] Furthermore, the effects described herein are merely illustrative and not limiting, and other effects may also occur.

[0183] The embodiments of this technology are not limited to those described above, and various modifications are possible without departing from the spirit of this technology.

[0184] For example, this technology can be configured as cloud computing, where a single function is shared and processed collaboratively by multiple devices via a network.

[0185] Furthermore, each step described in the flowchart above can be performed by a single device, or it can be divided and performed by multiple devices.

[0186] Furthermore, if a single step includes multiple processes, those processes can be executed by a single device or shared among multiple devices.

[0187] • Examples of configuration combinations This technology can also be configured as follows:

[0188] (1) An acquisition unit that acquires identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person, A reading unit reads information regarding the payment criteria of the insurance policy the insured person is enrolled in, based on one or more insurance enrollment numbers linked to the aforementioned identification information. A determination unit that determines whether or not there is a possibility of insurance payment based on the medical information and the payment criteria, If it is determined that there is a possibility of insurance payment, the recommendation unit sends a notification of the possibility of insurance payment to the first recipient linked to the identification information. An insurance payment system equipped with the following features. (2) The treatment described in the aforementioned medical information includes at least one of the following: medical treatment covered by health insurance, dispensing of medication, and nursing care. The insurance payment system described in (1) above. (3) If the recommendation unit determines that there is no possibility of paying the insurance claim, it sends a notification to the first recipient stating that there is no possibility of paying the insurance claim. The insurance payment system described in (1) or (2) above. (4) The system further includes a transmission unit that transmits the medical information to a second destination linked to the identification information, based on the insured's response to a notification that there is a possibility of insurance payment. The insurance payment system described in any of (1) to (3) above. (5) When the transmission unit has stored data including the determination result of whether or not there is a possibility of insurance payment and the insurance subscription number in the blockchain database, it transmits the information including the insurance subscription number to the second recipient. The insurance payment system described in (4) above. (6) The determination unit further determines the details of the payment related to the insurance for which it has been determined that there is a possibility of insurance payment, The recommendation unit sends a notification of payment details to the insured or the insurance company. An insurance payment system as described in any of (1) to (5) above. (7) The determination unit determines whether the insured person has fulfilled their obligation to disclose information for insurance purposes, based on at least one of the insured person's past medical examination results and other medical information representing the content of medical treatment received by the insured person in the past. An insurance payment system as described in any of (1) to (6) above. (8) The determination unit determines whether or not there is a possibility of paying insurance benefits using an inference model generated by machine learning. An insurance payment system as described in any of (1) through (7) above. (9) The system further includes an analysis unit that performs statistical analysis based on multiple medical records issued by the same medical institution and outputs the results of the analysis to determine the validity of the content. An insurance payment system as described in any of (1) through (8) above. (10) The information processing device that manages the insurance payment system, The system acquires identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person. Based on one or more insurance subscription numbers linked to the aforementioned identification information, information regarding the payment criteria of the insurance policy the insured person is enrolled in is read. Whether or not there is a possibility of insurance payment is determined based on the aforementioned medical information and the aforementioned payment criteria. If it is determined that there is a possibility of insurance payment, a notification of the possibility of insurance payment will be sent to the recipient associated with the aforementioned identification information. Information processing methods. (11) On the computer, The system acquires identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person. Based on one or more insurance subscription numbers linked to the aforementioned identification information, information regarding the payment criteria of the insurance policy the insured person is enrolled in is read. Whether or not there is a possibility of insurance payment is determined based on the aforementioned medical information and the aforementioned payment criteria. If it is determined that there is a possibility of insurance payment, a notification of the possibility of insurance payment will be sent to the recipient associated with the aforementioned identification information. A program to execute a process. [Explanation of symbols]

[0189] 1 PF Management Server, 2 Insurance Subscriber Database, 11 Card Reader, 12 Business Terminal, 13 Online Eligibility Verification System, 14 Intermediate Server, 121 Information Processing Unit, 131 Acquisition Unit, 132 Reading Unit, 133 Payment Eligibility Determination Unit, 134 Recommendation Unit, 135 Transmission Control Unit

Claims

1. An acquisition unit that acquires identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person, which have been transmitted from the medical institution when the user has given consent to the provision of medical information by operating a consent confirmation screen displayed on the medical institution's terminal, A reading unit reads information regarding the payment criteria of the insurance policy the insured person is enrolled in, based on one or more insurance enrollment numbers linked to the aforementioned identification information. A determination unit that estimates the user's medical diagnosis based on the medical information and determines whether or not there is a possibility of insurance payment based on the user's medical diagnosis estimated based on the medical information and the payment criteria, If it is determined that there is a possibility of insurance payment, a notification of the possibility of insurance payment is sent to the device used by the insured, which is the first destination linked to the identification information, including information indicating the medical information to be provided and information of the insurance company to which the information will be provided. If the insured agrees to provide the medical information to the insurance company in response to the notification of the possibility of insurance payment, the communication unit transmits the medical information to the insurance company's system, which is the second destination linked to the identification information. An insurance payment system equipped with the following features.

2. The treatment described in the aforementioned medical information includes at least one of the following: medical treatment covered by health insurance, dispensing of medication, and nursing care. The insurance payment system according to claim 1.

3. If the communications unit determines that there is no possibility of paying the insurance claim, it sends a notification to the first recipient stating that there is no possibility of paying the insurance claim. The insurance payment system according to claim 1.

4. The communications unit transmits information to the insurance company's system indicating that there is a possibility of paying insurance benefits to the insured. The insurance payment system according to claim 1.

5. When the data including the determination result of whether or not there is a possibility of insurance payment and the insurance subscription number is stored in the blockchain database, the communications unit transmits the information including the insurance subscription number to the second recipient. The insurance payment system according to claim 4.

6. The determination unit further determines the details of the payment related to the insurance for which it has been determined that there is a possibility of insurance payment, The communications unit shall send a notification of payment details to the insured or the insurance company. The insurance payment system according to claim 1.

7. The determination unit determines whether the insured person has fulfilled their obligation to disclose information for insurance purposes, based on at least one of the insured person's past medical examination results and other medical information representing the content of medical treatment received by the insured person in the past. The insurance payment system according to claim 1.

8. The determination unit determines whether or not there is a possibility of paying insurance benefits using an inference model generated by machine learning. The insurance payment system according to claim 1.

9. The system further includes an analysis unit that performs statistical analysis based on multiple medical records issued by the same medical institution and outputs the results of the analysis to determine the validity of the content. The insurance payment system according to claim 1.

10. The information processing device that manages the insurance payment system, When a user consents to the provision of medical information by using a consent confirmation screen displayed on the medical institution's terminal, the medical institution transmits identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person. Based on one or more insurance subscription numbers linked to the aforementioned identification information, information regarding the payment criteria of the insurance policy the insured person is enrolled in is read. The system estimates the user's medical diagnosis based on the medical information and determines whether or not there is a possibility of paying insurance benefits based on the estimated medical diagnosis of the user and the payment criteria. If it is determined that there is a possibility of insurance payment, a notification of the possibility of insurance payment is sent to the device used by the insured, which is linked to the identification information, and includes information indicating the medical information to be provided and information of the insurance company to which the information will be provided. If the insured person agrees to provide the aforementioned medical information to the insurance company in response to notification that there is a possibility of insurance payment, the medical information will be transmitted to the insurance company's system, which is linked to the aforementioned identification information. Information processing methods.

11. On the computer, When a user consents to the provision of medical information by using a consent confirmation screen displayed on the medical institution's terminal, the medical institution transmits identification information linked to the insured person's My Number and medical information representing the details of the treatment received by the insured person. Based on one or more insurance subscription numbers linked to the aforementioned identification information, information regarding the payment criteria of the insurance policy the insured person is enrolled in is read. The system estimates the user's medical diagnosis based on the medical information and determines whether or not there is a possibility of paying insurance benefits based on the estimated medical diagnosis of the user and the payment criteria. If it is determined that there is a possibility of insurance payment, a notification of the possibility of insurance payment is sent to the device used by the insured, which is linked to the identification information, and includes information indicating the medical information to be provided and information of the insurance company to which the information will be provided. If the insured person agrees to provide the aforementioned medical information to the insurance company in response to notification that there is a possibility of insurance payment, the medical information will be transmitted to the insurance company's system, which is linked to the aforementioned identification information. A program to execute a process.

Images