Information processing system and information processing method

Abstract

To provide an information processing system and an information processing method capable of appropriately transmitting and receiving information.SOLUTION: An information processing system includes a processor, and a storage device having association information having one or more combinations obtained by mutually associating a contractor, with first information showing life and death of the contractor and with second information showing at least the contract destination of a contract concluded by the contractor. The processor executes setting processing for setting an object person, extraction processing for extracting at least one of the first information and the second information, where the object person is associated as the contractor, as transmission information with reference to the association information, and transmission processing for transmitting the transmission information.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an information processing system and an information processing method.

Background Art

[0002] A technique in which a computer system that performs information cooperation between organizations executes a predetermined inter-organization procedure along a predetermined scenario triggered by a user's death notice has been conventionally known (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the case of the above prior art, for example, since the processing follows a scenario that has an event such as death as trigger information, insurance companies and other service providers wait for information passively. Also, because it is caused by an event, it is a single information cooperation. Therefore, it does not match the cases where insurance companies and other service providers actively collect information at their desired timing or search multiple times.

[0005] Furthermore, it is necessary to participate in a specific consortium to participate in the cooperation infrastructure system. For this reason, the high cost until service introduction, such as the need to provide some service from one's own company in a give-and-take manner and the cost required to support the cooperation infrastructure system, has become a problem.

[0006] The present invention has been made in view of such a background, and an object thereof is to provide an information processing system and an information processing method capable of appropriately transmitting and receiving information. [Means for solving the problem]

[0007] In one aspect, the present invention provides an information processing system comprising: a processing device; and a storage device having association information having one or more combinations of which a contractor, first information indicating whether the contractor is alive or dead, and second information indicating at least the contracting party of a contract concluded by the contractor are interrelated, wherein the processing device performs a setting process to set a target person; an extraction process to extract at least one of the first information and the second information associated with the target person as the contractor as transmission information by referring to the association information; and a transmission process to transmit the transmission information.

[0008] Another embodiment for solving the above problem is a method for causing an information processing system, which comprises a processing device and a storage device having association information having one or more combinations of first information indicating whether the contractor is alive or dead and second information indicating at least the contracting party of a contract concluded by the contractor, to execute a setting process for setting a target person, an extraction process for extracting at least one of the first information and the second information associated with the target person as the contractor as transmission information by referring to the association information, and a transmission process for transmitting the transmission information. [Effects of the Invention]

[0009] According to the above configuration, it is possible to provide an information processing system and information processing method that can appropriately send and receive information. [Brief explanation of the drawing]

[0010] [Figure 1] Overall conceptual diagram according to this embodiment [Figure 2] Conceptual diagram of an information processing device for sharing death information. [Figure 3] Hardware configuration diagram of an information processing device [Figure 4] Example diagram of a subscriber information file [Figure 5] Example of a death certificate information file [Figure 6]Example diagram of the information file of the deceased contractor [Figure 7] Example diagram of the API for querying the information of the deceased contractor [Figure 8] Example diagram of the death notice master information [Figure 9] Example diagram of the contractor master information [Figure 10] Example diagram of the business operator master information [Figure 11] Example diagram of the local government master information [Figure 12] Example diagram of the information related to the contractor's contract [Figure 13] Example diagram of the information related to the death notice and the contractor [Figure 14] Diagram showing the flowchart of the contractor information collection process [Figure 15] Diagram showing the flowchart of the death notice information collection process [Figure 16] Diagram showing the flowchart of the information linkage process of the deceased contractor [Figure 17] Diagram showing the flowchart of the process for querying the information of the deceased<​​​​​​​​​​​​​​​​​​​​​​​​Figure 1 shows the configuration of an information processing system 100 according to one embodiment of the present invention. The information processing system 100 includes an information processing device 1, a local government server 2 managed by a municipality or other local government, a business operator server 3 managed by various businesses such as life insurance companies and credit card companies, and a death notification information input terminal 6. The information processing device 1, the local government server 2, the business operator server 3, and the death notification information input terminal 6 are connected to each other via a communication network so that they can send and receive data from one another.

[0013] The information processing system 100 may include multiple local government servers 2, multiple business server 3, and multiple death notification information input terminals 6. Specific examples of business server 3 include an insurance company server 3A and other service provider servers 3B.

[0014] The death notification information input terminal 6 is a terminal that receives information input from the person filing the death notification and outputs it as a death notification form (pre-printed death notification) that can be submitted to the local government. The death notification information input terminal 6 also has a function to transmit information related to the death notification to the information processing device 1.

[0015] The communication network connecting each device is either wireless or wired, such as the Internet, WAN (Wide Area Network), LAN (Local Area Network), or public These include public communication networks, dedicated lines, etc.

[0016] Although the information processing system 100 according to this embodiment is composed of the above-mentioned multiple devices, the present invention does not limit the number of these devices. Therefore, the information processing system 100 can be composed of one or more devices as long as they have the following functions. It is possible.

[0017] As shown in Figure 2, the information processing device 1 communicates with the death notification information input terminal 6, the local government server 2, and the business server 3, and is a device that processes information concerning policyholders of insurance and other businesses, as well as policyholders or customers of various services such as credit cards (these may be simply referred to as "policyholders" below). The specific information contained includes information on insurance policyholders, death notification information of policyholders, information on deceased policyholders, and information related to inquiry processing.

[0018] Figure 3 shows an example of the configuration of the information processing device 1. As shown in the figure, the information processing device 1 includes a CPU 101, memory 102, hard disk 103, database 104, and network card 106. These are connected to each other via communication means such as a bus.

[0019] Furthermore, the information processing device 1 does not necessarily have to be entirely implemented in hardware; all or part of its configuration may be implemented using virtual resources, such as a cloud server in a cloud system.

[0020] CPU101 is configured using a Central Processing Unit. The functions of the information processing device 1 are realized by reading and executing programs stored in Mori 102, hard disk 103, or database 104.

[0021] The memory 102, the hard disk 103, and the database 104 are all devices for storing programs and data.

[0022] The devices that make up memory 102 include ROM (Read Only Memory), RAM (Random Access Memory), non-volatile semiconductor memory (NVRAM (Non-Volatile RAM)), SSD (Solid State Drive), various non-volatile memory such as SD memory cards, optical storage devices (CD (Compact Disc), DVD (Digital Versatile Disc), etc.), and storage areas of cloud servers.

[0023] Specific examples of devices that make up database 104 include non-volatile semiconductor memory (NVRAM (Non-Volatile RAM)), SSD (Solid State Drive), SD memory card, etc. Non-volatile memory (NVRAM), hard disk drives, optical memory These include storage devices (such as CDs (Compact Discs) and DVDs (Digital Versatile Discs)), and the storage areas of cloud servers.

[0024] Memory 102 stores the deceased policyholder information inquiry API 21. Hard disk 103 stores the policyholder information file 31, the death notification information file 32, and the deceased policyholder information file 33. Database 104 stores the death notification master information 41, the policyholder master information 42, the business master information 43, the local government master information 44, the policyholder contract-related information 45, and the death notification policyholder-related information 46.

[0025] Note that the storage locations for this information, data, programs, etc., are merely examples and may be stored in either the hard disk 103 or the database 104.

[0026] The network card 106 is a wired or wireless communication interface that enables communication with other devices via the communication network 5, and is, for example, a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, etc.

[0027] An example of a subscriber information file 31 is shown in Figures 2 and 4. The subscriber information file 31 is a file transmitted from the business server 3 to the information processing device 1 as a representation of subscriber information (Figure 2). The subscriber information file 31 contains information on multiple subscribers, and for each subscriber, the following information is stored in association with the subscriber: name, date of birth, address, My Number, business code, business name, business management number, registration date, and whether or not there is a contract agreement. The business code and business management number are unique identifiers assigned to the business, respectively. The presence or absence of a contract disclosure agreement indicates whether or not the subscriber has agreed to the disclosure of contract information to bereaved family members, etc.

[0028] An example of a death notification information file 32 is shown in Figures 2 and 5. The death notification information file 32 is a file transmitted from the local government server 2 to the information processing device 1 as a file containing information related to death notifications (Figure 2). The death notification information file 32 is a file that contains information about the contractor for whom a death notification has been submitted, and for each contractor, the name, date of birth, address, My Number, local government code and name of the local government to which the contractor belongs, and registration date are mainly associated and stored.

[0029] An example of a deceased policyholder information file 33 is shown in Figures 2 and 6. The deceased policyholder information file 33 is a file transmitted from the information processing device 1 to the information processing device 1 as a file containing information about a deceased policyholder (Figure 2). The deceased policyholder information file 33 is a file that contains information about policyholders for whom a death notification has been submitted, and for each policyholder, the following information is mainly associated and stored: name, date of birth, address, My Number, business code of the contracting company, business name, business management number, and date of death. In addition to or instead of the My Number, a social security (insurance) number, a driver's license or passport number, or an identifier issued by the system itself may be used.

[0030] Figures 2 and 7 illustrate the functions of the Deceased Policyholder Information Inquiry API 21. The Deceased Policyholder Information Inquiry API 21 has the function of receiving inquiries (requests) for policyholder information from external servers, and the function of creating and sending answers (responses) to those inquiries.

[0031] Devices such as the operator server 3 can use the deceased policyholder inquiry information 211 to request the information processing device 1 to transmit information about a specific policyholder. As will be described in detail later, the deceased policyholder information inquiry API 21 creates deceased policyholder inquiry response information 212 based on the information contained in the deceased policyholder inquiry information 211 and transmits it to the operator server 3.

[0032] An example of the death notification master information 41 is shown in Figure 8. The death notification master information 41 is information about multiple policyholders for whom a death notification has been submitted or whose death has been confirmed. It is stored in association with a unique serial number (master serial number) assigned to each death notification, the name of the policyholder related to the death notification, date of birth, address, My Number, name of the local government and local government, and date of death.

[0033] An example of the contract holder master information 42 is shown in Figure 9. The contract holder master information 42 contains information about multiple contract holders for whom a death notification has been submitted or whose death has been confirmed. For each contract holder, a unique serial number (master serial number) assigned to that contract holder, the contract holder's name, date of birth, address, My Number, date of death, and whether or not there was an agreement to disclose the contract are associated and stored.

[0034] An example of the business master information 43 is shown in Figure 10. The business master information 43 is information about businesses, and for each business, the business code, business name, business type, and individual interface settings are associated and stored. The individual interface settings define the functions that can be used in the information processing system 100 and are set for each business.

[0035] An example of the local government master information 44 is shown in Figure 11. The local government master information 44 concerns the business operator. This information is stored with a unique local government code and local government name associated with each local government. Local government master information 44 is used to identify the local government name by referring to the local government code. For example, by referring to local government master information 44 using the local government code from death notification master information 41, it is possible to identify the local government to which the contract holder belongs.

[0036] An example of Contractor Contract-Related Information 45 is shown in Figure 12. Contractor Contract-Related Information 45 contains information about the content of contracts concluded by the contractor and the business operator to which the contract is made. For each contractor, Contractor Contract-Related Information 45 is stored with associated information such as the contractor master serial number, the business operator code of the business operator with which the contractor has a contract, the business operator management number assigned to each contract, and the registration date (contract date). By referring to Contractor Contract-Related Information 45, it is possible to refer to a list of contracts concluded by the contractor.

[0037] An example of the Death Notification Policyholder Related Information 46 is shown in Figure 13. The Death Notification Policyholder Related Information 46 is information about policyholders for whom a death notification has been submitted, and is stored associated with each death notification, i.e., each policyholder, including the death notification master serial number, policyholder master serial number, etc.

[0038] In the Death Notification Contractor-Related Information 46, if a contract holder had contractual relationships with multiple businesses, multiple contract holder master serial numbers are registered, associated with a single death notification. Therefore, by referring to the Death Notification Contractor-Related Information 46, it is possible to extract a list of businesses that had contractual relationships with the contract holder for whom the death notification was submitted. By referring to the Death Notification Contractor-Related Information 46, it is possible to refer to a list of contracts concluded by the deceased contract holder and their corresponding death notification master serial numbers.

[0039] <Processing> The processes performed in the information processing system 100 are described below. In the following processes, the information processing device 1 executes a program or API stored in either the memory 102, the hard disk 103, or the database 104, by having the CPU 101 activate it. In the following, processes executed by the CPU 101 may also be described as being executed by the "information processing device 1" or the "death contract holder information inquiry API 21".

[0040] (Collection and processing of subscriber information) The customer information collection process in the information processing system 100 will be explained using Figure 14. The customer information collection process is the process by which the information processing device 1 collects information about customers who have contracted with service providers, including insurance companies (hereinafter simply referred to as "service providers").

[0041] When a customer applies for a contract (S1) and the service provider accepts the application (S2), the service provider proposes a contract regarding the provision of information upon death (S3). If the customer agrees and the contract is concluded (S4, S5), the service provider stores the customer information in the customer information file 31 and transmits it to the information processing device 1 (S6).

[0042] When the information processing device 1 receives subscriber information (S7), it registers and updates subscriber master information 42 and subscriber contract-related information 45 (S8, S9). As a result, the subscriber information held in the subscriber information file 31 is written to and saved in the subscriber master information 42 and subscriber contract-related information 45 (S9).

[0043] (Collection and processing of death certificate information) The process that is executed after the death of the contract holder will be explained using Figure 15.

[0044] When a contract holder dies, the notifier submits a death notification to the local government (S11). Upon receiving the death notification (S12), the local government stores the death notification information in the death notification information file 32 and transmits it to the information processing device 1 via the local government server 2 (S13).

[0045] When the information processing device 1 receives the death notification information file 32, i.e., the death notification information (S14), it checks whether there are any deficiencies in the contents of the death notification information (S15).

[0046] If there are any deficiencies (S15: Yes), the information processing device 1 notifies the local government server 2 of the deficiencies and their specific details (S16). The notification is delivered to the notifier via the local government server 2 (S17). The notifier resubmits the death notification to the local government server 2, taking into account the details of the deficiencies (S18A, S18B, S12).

[0047] If there are no deficiencies (S15: None), the information processing device 1 writes the contents of the death notification information held in the death notification information file 32 to the death notification master information 41 and the contractor master information 42, registers and updates them (S19A, S19B).

[0048] During registration and renewal (S19A, S19B), the information processing device 1 identifies the contract holder using identifiers such as the name, address, and My Number of the person whose death notification has been submitted, based on the contents of the death notification information file 32. The information processing device 1 accesses the death notification master information 41 and the contract holder master information 42 and writes the date of death for the identified contract holder.

[0049] Furthermore, the information processing device 1 registers and updates the contents of the death notification information in the death notification contract holder related information 46 (S20). Specifically, the information processing device 1 reads the death notification master information 41 and the contract holder master information 42, extracts the death notification master serial number and the contract holder master serial number of the contract holder for whom a death notification has been filed, associates these two types of serial numbers, and writes them to the death notification contract holder related information 46.

[0050] (Information sharing process for deceased policyholders) The information processing device 1 can communicate information about a deceased policyholder to the service provider at predetermined intervals. This process of sharing information about deceased policyholders will be explained using Figure 16.

[0051] First, in step S31, the information processing device 1 extracts information on deceased policyholders. The information processing device 1 reads the death notification policyholder-related information 46 and extracts the death notification master serial number and policyholder master serial number for each policyholder. Furthermore, the information processing device 1 reads the death notification master information 41 and policyholder master information 42 and reads the name, address, date of death, My Number, etc., of the policyholder associated with the extracted death notification master serial number and policyholder master serial number.

[0052] The information processing device 1 checks whether there are any items to be extracted from the information read in step S31 (S32). The presence or absence of items to be extracted can be determined by various conditions, but for example, it can be determined by checking whether there are any business operators to whom death notifications have been filed or who have died within a certain period.

[0053] If there are subscribers to be extracted (S32: Yes), the information processing device 1 compiles information for each business operator, including subscribers for whom a death notification was filed (or who died) within a certain period, along with their date of death, address, My Number, etc., based on the information obtained in step S31, as deceased subscriber information.

[0054] The compiled deceased policyholder information is sent to the service provider server 3 as, for example, a deceased policyholder information file 33 (Figure 6) (S33), and is received by the service provider server 3 (S34).

[0055] A business that receives information about a deceased policyholder via the business server 3 can take various actions using the information. For example, a business can perform a match with its own contract information (S 35) Determine whether a contract exists between the contractor and the other party (S36).

[0056] If a contract exists between the service provider and the customer (S36: Yes), the service provider shall carry out the procedures upon death based on the terms of the contract agreed upon with the customer (S37).

[0057] If there are no items to extract in step S32 (S32: None), no information will be sent to the service provider server 3. Also, if there is no contract in step S36 (S36: None), the death processing will not be performed.

[0058] By performing the above-mentioned processes regularly, such as once a day, once a month, or once a quarter, businesses can easily obtain information about deceased policyholders and ensure that the necessary actions are carried out.

[0059] (Inquiry process for information on deceased policyholders) The information processing system 100 can also respond to inquiries from businesses. The following explains the process of inquiring about deceased policyholder information using Figure 17.

[0060] The service provider uses the service provider server 3 to extract the subscribers whose information they wish to obtain (S41, S42). If there are subscribers whose information needs to be queried (S42: Yes), the service provider server 3 calls the deceased subscriber information query API 21 of the information processing device 1 (S43).

[0061] At that time, the service provider server 3 uses identifiers such as the name, address, and My Number of the target contract holder to identify the contract holder whose information is being inquired about, and sends this information as deceased contract holder inquiry information 211 to the deceased contract holder information inquiry API 21.

[0062] The deceased policyholder information inquiry API 21 responds to inquiries from the business server 3 and performs a death determination for the target policyholder (S44). The death determination can be performed by various methods, but for example, it is performed by referring to the policyholder master information 42 or the death notification master information 41. For example, when the policyholder master information 42 is used, the target policyholder is identified using My Number, identifier, policyholder name, address, etc., and the death determination is performed by checking whether the death date associated with that policyholder is registered.

[0063] If the registration of the date of death is confirmed (S45: Yes), the information processing device 1 responds that the inquired contract holder is deceased (S46A). If the registration of the date of death is not confirmed (S45: No), the deceased contract holder information inquiry API 21 responds that the inquired contract holder is alive (S46B). The response is sent as deceased contract holder inquiry response information 212 (Figure 7). In this case, the recipient is set to the business operator that made the inquiry.

[0064] When the operator server 3 receives the response (S47), it refers to the deceased policyholder inquiry response information 212 to determine whether or not there is information about the death of the inquired policyholder (S48).

[0065] If there is information about a death (S48: Yes), the service provider will carry out the necessary procedures upon death based on the terms of the contract agreed upon with the customer (S49).

[0066] (Processing of linking information on unregistered deceased persons) The information processing system 100 can also provide information about unregistered deceased persons to businesses. The process of linking unregistered deceased person information will be explained below using Figure 18.

[0067] The person who reports the death submits a death notification to the local government (S51). The local government then... Upon receiving the notification (S52), the death notification information is stored in the death notification information file 32 and transmitted to the information processing device 1 via the local government server 2 (S53).

[0068] In step S54, the information processing device 1 receives the death notification information (S54) and updates the death notification master information 41 by writing the contents of the death notification information to it (S55). The specific details of this process are the same as in step S19A.

[0069] If the deceased person whose death is reported is not registered in the contract holder master information 42 (S56: None), the information processing device 1 sends information indicating that the deceased person is an unregistered deceased contract holder (unregistered deceased contract holder information) to the business server 3 (S57). At that time, the unregistered deceased contract holder information is sent in the same format as, for example, the deceased contract holder information file 33.

[0070] The service provider can receive information on unregistered deceased policyholders via the service provider server 3 (S58) and consider their relevance to the business and the provision of services after death. They can also consider the possibility that the information may be unregistered due to some error or mistake, and refer to the contract status within the service provider.

[0071] In Figure 18, if the deceased person in the death notification is registered in the contract master information 42 (S56: Yes), the process of linking unregistered deceased person information is completed. After that, the information processing device 1 may execute both or either of the processes S19B and S20 in Figure 15.

[0072] (Disclosure of contract status information to bereaved family members) The information processing system 100 can also respond to requests for information disclosure from bereaved families. The process of disclosing contract information to bereaved families is explained below using Figure 19.

[0073] When a request for disclosure of information regarding the existence of a contract for a certain person (the person being requested) is sent by a bereaved family member or the like (S61), the information processing device 1 receives the request (S62). The information processing device 1 checks whether the person being requested, the contractor, is still alive (S63). This check can be performed, for example, by the information processing device 1 referring to the contractor master information 42 or the death notification master information 41, similar to the process in step S44.

[0074] If the contractor is alive (S63: alive), the information processing device 1 does not disclose the information and terminates the process. On the other hand, if the contractor is deceased (S63: deceased), the information processing device checks whether the contractor has consented to the disclosure of the information by referring to the contractor master information 42 (S64).

[0075] There are various routes and methods for specifically confirming the agreement, but one example is to refer to the death notification master information 41. In this case, the information processing device 1 refers to the death notification master information 41 to identify the contractor associated with the information such as the name, address, and identifier of the person concerned, and collects the death notification master serial number of that contractor. Furthermore, the information processing device 1 refers to the death notification contractor-related information 46 to obtain the contractor master serial number associated with the collected death notification master serial number. Next, the information processing device 1 refers to the contractor master information 42 and reads the information associated with the obtained contractor master serial number, thereby confirming whether an agreement exists for each contract.

[0076] If there is no agreement, the information will not be disclosed (S64: No agreement). On the other hand, if the contractor agrees (S64: Agreement given), the information processing device 1 extracts information on whether the target person has a contract (S65). The information on whether the contract exists includes the name of the contracting company, the contract date, the content of the contract, the registration date (contract date), etc. This information can be extracted by referring to the contractor contract-related information 45 and the contractor master information 42 and reading the information associated with the target person. ru.

[0077] Information regarding the existence of contracts can also be extracted by referring to files 31-33 and information 41-46 to check whether there is a business associated with the subject. If no associated business exists, it can be concluded that no contracts were made by the subject, and if a business exists, it can be concluded that some kind of contract exists.

[0078] The information processing device 1 can compile information regarding the existence of a contract for the requested contractor into a format such as a deceased contractor information file 33 and transmit it (S66, S67). The bereaved family can obtain information about the contract by receiving the file (S68).

[0079] In each of the above processes, the information processing system 100 refers to file 31, death notification information file 32, and death contract holder information file 33, death notification master information 41, contract holder master information 42, business operator master information 43, local government master information 44, contract holder information 45, and death notification contract holder related information 46 to identify or extract the target contract holder, business operator, or local government, and further extracts information such as the circumstances of death, whether an agreement was reached, and contract details appropriately.

[0080] As described above, files 31-33 and information 41-46 function as associated information, possessing multiple combinations of associations between various types of information. In the information processing system 100, the associated information is referenced to identify contractors and businesses, and to perform appropriate processing and extraction / acquisition of appropriate information.

[0081] The methods of using and referencing files 31-33 and information 41-46 in the above embodiment are examples only. The files and information used to extract the desired information are not limited to those described above. For example, in steps S61-S68, information regarding the existence of a contract may be extracted by referencing file 31-33.

[0082] (Collection and processing of death certificate information) After the contract holder dies, the death notification information input terminal 6 may intervene to execute the process. This will be explained using Figure 20.

[0083] When a policyholder dies, the person who notifies the policyholder of the death (hereinafter also referred to as the notifier) ​​enters the death notification information into the death notification input terminal 6 (S71). The death notification input terminal 6 checks the input content (S72), and if there are any deficiencies or omissions (S73: Yes), it returns to step S71 and requests re-entry.

[0084] If there are no errors in the information entered by the notifier (S73: None), the death notification input terminal 6 outputs a pre-printed death notification form (S74). The pre-printed death notification form is a document equivalent to a draft of the death notification form to be submitted to the local government, and is filled in with the entered death notification information, such as the deceased's address and name.

[0085] The notifier adds the necessary information to the pre-printed death notification form (S75) and submits the death notification form to the local government (S76). Submission may also be made to local government server 2.

[0086] The local government or local government server 2 receives the death notification (S77), and then notifies the death notification information input terminal 6 that the death notification has been approved (S78).

[0087] When the death notification information input terminal 6 receives information that it has been approved (S79), the death notification information is sent to the information processing device 1 in the format of a death notification information file 32 (S80).

[0088] When the information processing device 1 receives death notification information (S80A), it writes the contents of the death notification information stored in the death notification information file 32 to the death notification master information 41 and the contract holder master information 42, registers and updates them (S80B, S80C).

[0089] During registration and renewal (S80B, S80C), the information processing device 1 identifies the contract holder using identifiers such as the name, address, and My Number of the person whose death notification has been submitted, based on the contents of the death notification information file 32. The information processing device 1 accesses the death notification master information 41 and the contract holder master information 42 and writes the date of death for the identified contract holder.

[0090] Furthermore, the information processing device 1 registers and updates the contents of the death notification information in the death notification contract holder related information 46 (S80D). Specifically, the information processing device 1 reads the death notification master information 41 and the contract holder master information 42, extracts the death notification master serial number and the contract holder master serial number of the contract holder for whom a death notification has been filed, associates these two types of serial numbers, and writes them to the death notification contract holder related information 46.

[0091] (Collection and processing of death certificate information) Figure 21 illustrates another example of a process involving the death notification information input terminal 6 after the death of the contract holder.

[0092] Steps S71 through S80B are the same as the process in Figure 20, and therefore the same step numbers are used, and the explanation is omitted.

[0093] If the deceased person whose death is reported is not registered in the contract holder master information 42 (S93: None), the information processing device 1 sends information indicating that the deceased person is an unregistered deceased contract holder (unregistered deceased contract holder information) to the business server 3 (S94). At that time, the unregistered deceased contract holder information is sent in the same format as, for example, the deceased contract holder information file 33.

[0094] The service provider can receive information on unregistered deceased policyholders via the service provider server 3 (S95) and consider their relevance to the business and the provision of services after death. They can also consider the possibility that the information may be unregistered due to some error or mistake, and refer to the contract status within the service provider.

[0095] In Figure 21, if the deceased person in the death notification is registered in the contract master information 42 (S93: Yes), the process of linking unregistered deceased person information is completed. After that, the information processing device 1 may execute both or either of the processes S80C and S80D in Figure 20.

[0096] <Effects> This specification clarifies at least the following:

[0097] (Aspect 1) The information processing device 1 includes a CPU 101 (corresponding to a processing device), a memory 102, a hard disk 103, and a database 104 (corresponding to a storage device) having associated information which has one or more combinations of a contractor, first information indicating whether the contractor is alive or dead, and second information indicating at least the contracting party of a contract concluded by the contractor. The CPU 101 may execute a setting process to set the target person (S31, S44, S56, S62), an extraction process to extract at least one of the first information and second information associated with the target person as a contractor as transmission information by referring to the associated information (S32, S45, S66), and a transmission process to transmit the information to the specified business operator (S33, S46A, 46B, S67).

[0098] By performing such processing, the information processing system 100 can, for example, appropriately send and receive information. Specifically, it can send information about subscribers in response to inquiries from businesses, send information about unregistered individuals, and send information to businesses periodically, such as monthly or daily reports. Therefore, it is not limited to sending information only on a one-off basis triggered by some event, but can also send information periodically or at appropriate intervals. Furthermore, it is possible to send and receive information without participating in a specific consortium.

[0099] If the business operator is an insurance company, the insurance company can carry out insurance payments, etc. If the business operator is a credit card company or a utility company such as an electricity company, it can quickly carry out processes such as suspending services, stopping payments, and canceling membership fees.

[0100] (Aspect 2) In this embodiment, the CPU 101 may further perform inquiry processing (S43, S61) to receive an inquiry regarding the subject, and may perform setting processing, extraction processing, and transmission processing in response to the inquiry.

[0101] By performing this processing, the information processing system 100 can respond quickly to inquiries from businesses and bereaved families and provide accurate answers.

[0102] (Aspect 3) In another embodiment, a business operator or the like may inquire about the life or death status of the subject (S43). In this case, the CPU 101 may transmit information indicating the life or death status of the subject (first information) to the business operator or the like that made the inquiry (S46A, S46B).

[0103] (Aspect 4) In this embodiment, the CPU 101 may further perform a process to confirm whether the person subject to the inquiry is deceased (S63) and a process to determine whether information disclosure is possible to the person who made the inquiry (S64), and if it is determined that the person subject is deceased and information disclosure is possible, it may perform a transmission process (S67).

[0104] In this case, there is no risk of information leakage due to false inquiries or the disclosure of information that is not authorized for disclosure.

[0105] (Aspect 5) In any of aspects 1 to 4, the CPU 101 may further perform a process (S57) to notify a predetermined person if it is not possible to extract second information associated with the subject as a contract holder in the extraction process (S56).

[0106] In the above case, the death can be notified regardless of whether a contract exists. Therefore, businesses and other parties can check whether there are any situations such as contracts not being registered due to errors.

[0107] (Pattern 6) In any of the Patterns 1 to 5, the policyholder is the person who entered into the life insurance contract, and the contracting party is the life insurance company.

[0108] In the above configuration, it becomes possible to carry out life insurance payment procedures accurately and promptly.

[0109] (Aspect 7) In any of aspects 1 to 6, the CPU 101 periodically performs setting processing, extraction processing, and transmission processing, thereby enabling accurate communication with the business operator in the form of monthly reports, daily reports, etc.

[0110] (Aspect 8) In any of aspects 1 to 7, the CPU 101 obtains information regarding the life or death status from the municipality to which the subject belonged.

[0111] By obtaining death information from local governments, it becomes possible to acquire information quickly and reliably.

[0112] (Aspect 9) In any of aspects 1 to 8, the CPU 101 obtains information regarding the life or death of the subject from the person who filed the death notification, without going through the local government.

[0113] By obtaining death information from the person who filed the death notification, it becomes possible to obtain information quickly and reliably.

[0114] In the above embodiment, the first information is not limited to information that directly indicates life or death, but also information that indirectly indicates it. However, this is also acceptable. For example, if the date of death is not recorded or the entry field is left blank, it can be understood as information indicating that the person is still alive. Furthermore, the second piece of information is not limited to information showing the details of the contract; it may also include information such as the name of the contracting company. Alternatively, it may simply be information that directly or indirectly indicates that the contracting company does not exist.

[0115] In the embodiment, "business operator" may include individuals as well as corporations. Similarly, "person" may include organizations such as corporations as well as individuals. [Explanation of symbols]

[0116] Information processing system 100 Information processing device 1 Local government server 2 Operator Server 3

Claims

1. Processing device and A storage device having associated information having one or more combinations of a contracting party, a first piece of information indicating whether the contracting party is alive or dead, and a second piece of information indicating at least one of the contracting parties to the contract concluded by the contracting party, The aforementioned processing apparatus is The process of setting the target person, An extraction process that, by referring to the associated information, extracts at least one of the first and second pieces of information associated with the subject as the subscriber as transmitted information, A transmission process for transmitting the aforementioned transmission information, In the extraction process, if the second information associated with the subject as the contractor cannot be extracted, a process is performed to notify a predetermined person. An information processing system that performs [this action].

2. The aforementioned processing apparatus is Further inquiry processing is performed to receive inquiries regarding the aforementioned subject, In response to the aforementioned inquiry, the setting process, the extraction process, and the transmission process are executed. The information processing system according to claim 1.

3. The aforementioned inquiry concerns the life or death status of the subject, The transmitted information includes the first information relating the subject to the contracting party, The information processing system according to claim 2.

4. The aforementioned processing apparatus is In response to the aforementioned inquiry process, A process to confirm whether the aforementioned subject is deceased, Further processing is performed to determine whether information disclosure is possible, If the aforementioned subject dies and it is determined that information disclosure is possible, the transmission process will be executed. The information processing system according to claim 2.

5. The aforementioned policyholder is the person who entered into the life insurance contract, The aforementioned contracting party is a life insurance company. The information processing system according to claim 1 or 2.

6. The aforementioned processing apparatus is The aforementioned setting process, extraction process, and transmission process are performed periodically. The information processing system according to claim 1 or 2.

7. The aforementioned processing apparatus is The first information is obtained from the municipality to which the aforementioned subject belonged. The information processing system according to claim 1 or 2.

8. The aforementioned processing apparatus is The first information is obtained from the person who filed the death certificate for the aforementioned subject, without going through the local government. The information processing system according to claim 1 or 2.

9. An information processing system comprising a processing device and a storage device having associated information having one or more combinations of which a contractor, first information indicating the life or death of the contractor, and second information indicating at least the contracting party of a contract concluded by the contractor are interrelated, The aforementioned processing device The process of setting the target person, An extraction process that, by referring to the associated information, extracts at least one of the first and second pieces of information associated with the subject as the subscriber as transmitted information, A transmission process for transmitting the aforementioned transmission information, In the extraction process, if the second information associated with the subject as the contractor cannot be extracted, a process is performed to notify a predetermined person. An information processing method that performs the following.

Images