JP7499639B2 - Inquiry support device and inquiry support method - Google Patents

Description

The present invention relates to an inquiry support device and an inquiry support method.

In order to sort out the assets (including liabilities) of the deceased, surviving family members will make inquiries to financial institutions etc. that they think might have had the deceased's account or various contracts. However, if the deceased did not leave behind bankbooks, cash cards, contracts etc., and the surviving family members have no idea what they might have, the current situation is that the surviving family members will make inquiries one by one to possible financial institutions etc.

In addition, regarding the services that the User has contracted or is currently using, the User's own pre-set/
As a conventional technology for aggregating information upon request, for example, an account aggregation system (see Patent Document 1) has been proposed that includes an account information registration unit that receives account information for accessing an institution that provides transaction information from a user terminal and registers it in an account information storage unit, a transaction information acquisition unit that acquires transaction information from the institution based on the account information, a transaction information providing unit that provides the acquired transaction information to the user terminal, a correspondence relationship storage unit that stores keywords indicating transaction contents that may be included in the transaction information and correspondence relationship information indicating a correspondence relationship with other institutions that provide the transaction information, an institution identification unit that identifies the other institutions that provide the transaction information and have no account information registered in the account information storage unit based on the keywords included in the acquired transaction information and the correspondence relationship information, and a recommendation information providing unit that provides the user terminal with recommendation information recommending the registration of account information of the other identified institutions.

JP 2018-077730 A

However, account aggregation services such as those in the above-mentioned conventional technology require the deceased person to inquire about their own accounts, and do not allow surviving family members to check the accounts held by the deceased.

On the other hand, when bereaved family members visit a financial institution to inquire about the accounts held by the deceased, the financial institution must verify the legitimacy of the heirs. However, the number of personnel required for such work at financial institutions is not negligible in terms of costs, and the financial institution feels a heavy burden.

Moreover, in the financial industry as a whole, each financial institution is currently carrying out the same procedures for the same deceased person from the same family member. In other words, each financial institution is carrying out the same or similar procedures for the same deceased person and obtaining the same results, which is a huge waste.

Therefore, an object of the present invention is to provide a technique for making the process of confirming asset information of a deceased person more efficient among the relevant parties and reducing costs.

The inquiry support device of the present invention, which solves the above-mentioned problem, is characterized by including a communication device that communicates with each financial institution system via a network, and a calculation device that executes the following processes: a process of communicating with the financial institution system of the specified financial institution to receive success information of an heir identification determination based on the deceased's family register information and an account inquiry request for the deceased when an account inquiry task for the deceased occurs at a specified financial institution, the process of sending the received success information and account inquiry request to each of the other financial institution systems other than the specified financial institution among the various financial institution systems, and obtaining the results of the account inquiry process for the deceased that was executed in each of the other financial institution systems with the success information as a prerequisite, and the process of returning the results obtained from each of the other financial institution systems to the financial institution system of the financial institution.

In addition, the inquiry support method of the present invention is characterized in that an information processing device is equipped with a communication device that communicates with each financial institution system via a network, and executes the following processes: a process of communicating with the financial institution system of the specified financial institution to receive success information of an heir identification determination based on the family register information of the deceased and an account inquiry request for the deceased when an account inquiry operation for the deceased occurs at a specified financial institution, the process of sending the received success information and account inquiry request to each of the other financial institution systems other than the specified financial institution among the various financial institution systems, and obtaining the results of the account inquiry process for the deceased that was executed in each of the other financial institution systems with the success information as a prerequisite; and a process of returning the results obtained from each of the other financial institution systems to the financial institution system of the financial institution.

According to the present invention, it is possible to streamline the process of confirming the asset information of a deceased person among the relevant parties and reduce costs.

FIG. 1 is a diagram showing an inventive concept including a query support device according to an embodiment of the present invention. 1 is a diagram illustrating an example of a network configuration including a query support device according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a hardware configuration of the query support device according to the present embodiment. FIG. 1 is a diagram showing an example of a flow of a query support method according to an embodiment of the present invention. 5 is a diagram showing an example of a data structure of a query request file according to the present embodiment. FIG. 4 is a diagram showing an example of the configuration of query request management data according to the embodiment; FIG. FIG. 4 is a diagram illustrating an example of a configuration of communication destination management data according to the present embodiment. 11 is a diagram illustrating an example of a data structure of a query result file according to the embodiment. FIG. 4 is a diagram showing an example of the configuration of query request management data according to the embodiment; FIG. FIG. 2 is a diagram showing an example of a flow of a query support method according to the present embodiment. A figure showing an example of the data structure of a funeral intermediation request file in this embodiment. 13 is a diagram showing an example of the data structure of a funeral response result file in this embodiment. FIG. FIG. 4 is a diagram showing an example of the configuration of intermediary reception management data according to the embodiment;

<About the inventive concept>
[0023] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. Fig. 1 is a diagram showing an inventive concept including a query support device 100 of the present embodiment, and Fig. 2 is a diagram showing an example of a network configuration including the query support device 100.

The inquiry support device 100 shown in Fig. 1 and Fig. 2 is a computer that aims to streamline the confirmation work of the deceased's asset information among the related parties and reduce costs. The surviving family members who have lost a family member or the like (deceased) can check the accounts held by the deceased at financial institutions, the services contracted with various businesses, etc.
It is necessary to check whether this is the case or not.

Therefore, such surviving family members will visit a bank or other financial institution (or access the financial institution's system via a terminal), present official documents such as a family register containing information about themselves and the deceased, and demonstrate that they are legitimate heirs, and make a request, for example, to check an account.

On the other hand, at the financial institution that has received the request, a designated person in charge checks the family register and other documents to confirm the legitimacy of the heir. The results of this check are input to the financial institution system 200, and are then sent from the financial institution system 200 to the inquiry support device 100 as an account inquiry request.

The inquiry support device 100 receives this account inquiry request, stores it in its own storage device, and also transmits it to the systems (A
The other financial institution systems 250 receive the request and make an inquiry to the API
) performs an account search using the information of the deceased person contained in the above-mentioned account inquiry request (e.g., name, address, date of birth, telephone number, My Number) as keys in an appropriate core system such as an accounting system that manages accounts, and returns the results to the inquiry support device 100.

The inquiry support device 100 thus collects the results about the deceased from each of the other financial institution systems 250, i.e., information on whether or not the deceased held an account, and compiles them in an appropriate format as inquiry results, which are returned to the financial institution system 200. On the other hand, the above-mentioned surviving family members are presented with the inquiry results obtained by the financial institution system 200, for example, via a teller or a specified person in charge at the financial institution, and can recognize whether the deceased held accounts at each financial institution, etc.

In other words, in many cases, the surviving family members do not fully understand the accounts held by the deceased, but even in such a situation, the system allows them to check the account information held efficiently and at low cost.
This will reduce the time it takes to identify the assets of the deceased and prevent any oversights from being identified.

On the other hand, from the financial institution's perspective, by distributing the information of a deceased person whose heirs have been confirmed at one financial institution to each of the other financial institutions and then consolidating the inquiry results from each of those other financial institutions, it is possible to reduce the burden of identifying the assets of the deceased person and to reduce the costs for the financial institutions that receive inquiries.

As mentioned above, the model is that the client pays a fee to the underwriter for each process based on an account inquiry request, which allows the client to recover the operational costs of using its own system to inquire about the presence or absence of an account in response to requests from other companies.

Financial institutions that receive inquiries can also reduce costs by sharing information on heirs confirmed by other financial institutions. In addition, by publishing account inquiry processing as their own API, they can secure fee income. In addition, early sharing of death information can be used to trigger account freezing and insurance payment operations, allowing financial institutions to fulfill their social responsibilities.

On the other hand, when the inquiry support device 100 receives a request for intermediation of funeral services from the financial institution system 200 in addition to the above-mentioned account inquiry request, it transmits the request for intermediation to the funeral service provider system 300. The operator of this funeral service provider system 300 is assumed to be an entity that has signed contracts in advance with each funeral-related business that is a general funeral business, operates a portal site for funeral services, and exists as a funeral service intermediary.

In this case, the funeral service provider system 300 performs contract mediation of funeral services between the funeral-related business that meets the contract conditions indicated in the mediation request and the surviving family of the deceased, and responds with the results to the inquiry support device 100. The funeral-related business that receives the funeral service mediation can efficiently secure potential customers with a high probability.

In addition, bereaved families can receive referrals from funeral-related businesses that match their requirements,
It will be possible to easily consult with specialists regarding the procedures necessary for funerals.
<Hardware Configuration>
The hardware configuration of the query support device 100 is as follows: Fig. 2 is a diagram showing an example of the hardware configuration of the query support device 100 of this embodiment.

In this case, the query support device 100 includes a storage device 101, a memory 103, a computing device 104,
and a communication device 105.

Of these, the storage device 101 is configured with an appropriate non-volatile storage element such as an SSD (Solid State Drive) or a hard disk drive.

In addition, memory 103 is composed of a volatile memory element such as RAM.

The arithmetic unit 104 also reads the program 102 stored in the storage device 101 from the memory 10
3 and executes it to perform overall control of the apparatus itself, as well as various judgments, calculations and control processes.

The communication device 105 is a network interface card that is connected to the network 1 and handles communication processing with other devices such as the financial institution system 200, other financial institution systems 250, and funeral service provider system 300.

In addition to the program 102 for implementing the functions required for the inquiry support device 100 of this embodiment, at least data such as an inquiry request file, an inquiry result file, a funeral intermediation request file, a funeral answer result file, communication destination management data, inquiry request management data, and intermediation reception management data are stored in the storage device 101. Details of these data will be described later.

In addition, the memory 103 is implemented with an account inquiry API.
is an API (Application Programming Interface) that is generally available to financial institutions.
The query support device 100 is similar to the gramming interface.
This is an API that provides a function for making an account inquiry request to each of the other financial institution systems 250 based on an account inquiry request received from the financial institution system 200.
<Inquiry support method: Cases between financial institutions>
The actual procedure of the query support method according to this embodiment will be described below with reference to the drawings. The various operations corresponding to the query support method described below are realized by a program that is read into a memory or the like and executed by the query support device 100. This program is composed of codes for performing the various operations described below.

4 is a diagram showing an example of a flow of the inquiry support method according to the present embodiment. Here, it is assumed that a surviving family member of a deceased person visits a certain financial institution, presents a certified copy of the family register containing information about the deceased person and the surviving family member, and makes a request to inquire about the account of the deceased person.

In this case, the heir verification work based on the above-mentioned family register is carried out by the department in charge of the heir verification work at the financial institution. In addition, the result of this work is registered in the financial institution system 200 of the financial institution.

The financial institution system 200 acquires the result of the heir verification (the result of the heir confirmation judgment) (s1
1), and it is determined whether the result indicates success or failure (s12).

If the above-mentioned judgment result shows that the above-mentioned surviving family member is not a legitimate heir (s12: NG
), the financial institution system 200 outputs the result, for example, to the teller terminal (or the surviving family member's terminal), and ends the process.

On the other hand, if the result of the above-mentioned judgment indicates that the above-mentioned surviving family member is a legitimate heir (s12:
OK), the financial institution system 200 creates the inquiry request file 130 (FIG. 5) (s1
3).

This inquiry request file 130 includes, for example, "counter reception information", which is information received from the surviving family members at the counter of the above-mentioned financial institution, "account inquiry information", which is information required when making an account inquiry request to another financial institution system 250 other than the above-mentioned financial institution system 200, and "management information" held in the inquiry support device 100 regarding the case in question.

Of these, "reception information" includes the financial institution that checked the family register, the reception date,
This includes information such as client category, client identification documents, client name, funeral referral request, and collection fee.

In addition, the "account inquiry information" includes information about the deceased that is required when inquiring about the deceased's accounts, such as the address, name (kana and kanji), date of birth, telephone number, and My Number. By including such information, inquiries can be made even if the authentication information, such as the user ID and password, linked to the account is unknown to the surviving family members.

The financial institution system 200 uses, for example, an account inquiry API published by the inquiry support device 100.
and executes an introduction request using the information in the introduction request file 130 as a key (s14).

On the other hand, the query support device 100 receives the query request and stores it in the query request management data 100.
26 (FIG. 16) (s15). In the example of FIG. 16, the result of the account inquiry of the deceased person at the financial institution that performed the above-mentioned verification of the heir of the surviving family (which is assumed to be included in the account inquiry request from the financial institution system 200) and management information of the inquiry request case are included.

Next, the inquiry support device 100 appropriately edits the content of the inquiry request described above in accordance with the rules of the API published by the other financial institution system 250 (s16), and transmits the inquiry request file (similar to FIG. 5) generated through this editing to each destination (account inquiry API published by the other financial institution system 250) indicated in the communication destination management data 125 (FIG. 7) (s17). The communication destination management data 125 is a table that specifies the URLs of the account inquiry API published by the financial institution system 200 and the other financial institution system 250.

Meanwhile, each of the other financial institution systems 250 that receives the inquiry request file 130 via the above-mentioned account inquiry API executes an account identification process based on the information of the deceased person indicated in the inquiry request file 130 in accordance with the regulations of the inquiry business (s18, s19).

Furthermore, each of the other financial institution systems 250 responds to the introduction assistance device 100 with the inquiry result, which is the result of s19 (s20).

On the other hand, the inquiry support device 100 acquires inquiry results from each other financial institution system 250 (s21), and determines whether inquiry results have been obtained from all other financial institution systems 250 (the destinations of the inquiry request file in s17) (s22).

If the result of the above determination is that there is another financial institution system 250 for which the inquiry result has not yet been obtained (s22: No), the inquiry support device 100 returns the process to s21.

On the other hand, if the result of the above determination is that the inquiry results have been obtained from all the other financial institution systems 250 (s22: Yes), the inquiry support device 100 consolidates the inquiry results and stores them in the inquiry result file 1.
31 (FIG. 8) is generated (s23).

8, this inquiry result file 131 contains financial institution inquiry result information in addition to the same configuration as the inquiry request file 130 (counter reception information, account inquiry information, management information). This financial institution inquiry result information is a list of the inquiry results obtained from the other financial institution systems 250 in s21 above, organized by financial institution.

At this time, the inquiry support device 100 sets the corresponding values of the inquiry results obtained in s21 or aggregated in s23 to the values of "Inquiry Result" and "Account Number" for each financial institution in the "Financial Institution Inquiry Information" column in the inquiry request management data 126.

Next, the inquiry support device 100 responds to the financial institution system 200 with the inquiry result file 131 generated in s23 (s24).

Meanwhile, the financial institution system 200 outputs the inquiry result file 131 obtained in response from the inquiry support device 100 to, for example, a teller terminal (or a terminal of the surviving family) (s25), and ends the process. The surviving family members can recognize the contents of this inquiry result file 131, ensure that they understand the assets of the deceased, and prevent oversight of inquiries.
<Inquiry support method: Funeral-related business case>
Next, a description will be given of a case where the bereaved family is considering using a funeral service and requests an intermediary for the service. FIG 10 is a diagram showing an example of a flow of the introduction support method of this embodiment.

Here, as in the above flow example, it is assumed that the family of the deceased visits a certain financial institution and makes a request for funeral mediation regarding the funeral of the deceased. In this case, the department in charge of the relevant business at the financial institution registers information based on the above funeral mediation request in the financial institution system 200 of the financial institution.

The financial institution system 200 creates a funeral intermediation request file 132 (FIG. 11) in response to the above-mentioned information registration (s31).

This funeral intermediation request file 132 includes, for example, "counter reception information," which is the information received from the bereaved family at the counter of the financial institution mentioned above, "client information," which is the information required when making a funeral intermediation request to the funeral business operator system 300, and "funeral intermediation business information" regarding the intermediation request destination for the case in the inquiry support device 100.

Of these, the "reception information" includes information such as the reception financial institution that received the funeral intermediation request from the bereaved family, the reception date, the client category, the client's name, funeral introduction request, and collection fees.

In addition, the "client information" includes information about the surviving family member who is the client, i.e., the heir, such as the client category, address, name (kana or kanji), date of birth, and telephone number.

The funeral intermediation information includes information such as the identification information of the funeral business operator who is the funeral intermediary, the reception number, the intermediation status, the contract information with the customer, the contract amount, the contract date, the contract fee, etc. However, at the time of s31, the information such as the contract information with the customer, the contract amount, the contract date, and the contract fee has not been set.

Next, the financial institution system 200, for example,
The API is called and a request for intermediation is made using the information in the funeral intermediation request file 132 as a key (s32). The API for intermediation in this case is an API (Application Programming Interface (API)) published in the introduction support device 100 and the funeral business operator system 300.
The API is an API that provides the inquiry support device 100 with a function of making a funeral intermediation request to the funeral service provider system 300 based on a funeral intermediation request received from the financial institution system 200.

Meanwhile, the inquiry support device 100 receives the above-mentioned funeral mediation request and registers it in the mediation reception management data 127 (FIG. 13) (s33). In the example of FIG. 13, the management information and mediation information of the funeral mediation request are included. At this point, the "contract status" in the mediation information is "undecided," and the fields for the contract date, contract contents, and contract fee are all blank.

Next, the inquiry support device 100 appropriately edits the contents of the funeral intermediation request in accordance with the rules of the API published by the funeral service provider system 300 (s34), and transmits the funeral intermediation request file 132 (similar to FIG. 11) created through this editing to each destination (intermediation API published by the funeral service provider system 300) indicated in the communication destination management data 125 (FIG. 7) (s35).
.

In addition, the communication destination management data 125 includes the URL of the account inquiry API, as well as the inquiry support device 1.
It is a table that specifies the URLs of the intermediation APIs published by the funeral service provider system 300 and the funeral service provider system 300.

Meanwhile, the funeral service provider system 300, which receives the funeral intermediation request file 132 via the above-mentioned intermediation API, executes the process of contract adjustment based on the information indicated in the funeral intermediation request file 132 in accordance with the regulations for funeral intermediation business (s36, s37).

Specifically, for example, the conditions specified by the bereaved family (included in the funeral intermediation request file 132)
A funeral-related business that matches the criteria is identified from a list of funeral-related businesses previously stored in a storage device, etc., and the contents of the funeral intermediation request file 132 are notified to the terminals, etc. of both the identified funeral-related business and the above-mentioned surviving family member, prompting them to enter into a contract.

At this time, a contract is made between the funeral-related business and the bereaved family, and the success or failure of the contract is notified to the funeral service provider system 300 from the terminal of the bereaved family or the funeral-related business. If the success or failure is that the contract has not been made, the process ends. On the other hand, if the success or failure is that the contract has been made, the funeral service provider system 300 appropriately edits the contract contents according to the format of the funeral response result file 133 shown in Figure 12 (s38).

In addition, the funeral service provider system 300 stores the funeral service answer result file 133 obtained by editing in s38.
The request is responded to the query support device 100 (s38).

On the other hand, the inquiry support device 100 receives the above-mentioned funeral service answer result file 133 from the funeral service business operator system 300 (s40), and based on the contents of the file, compiles the intermediation reception management data 127 (FIG. 2
7) Update the “Contract Status” to “Contract Completed” and set the contract date, contract details, and contract fee.

Although the best mode for carrying out the present invention has been specifically described above, the present invention is not limited to this, and various modifications are possible without departing from the spirit and scope of the present invention.

According to this embodiment, general users can reduce the time it takes to understand the assets of the deceased and prevent oversight of inquiries. In addition, general users can receive referrals from funeral-related businesses and can consult with specialist businesses regarding the procedures required for funerals.

On the other hand, the financial institution that receives the inquiry can reduce the cost of the operation by sharing the information on confirmed heirs with other financial institutions. Also, by releasing the function for responding to inquiries about the deceased's account information as its own API, it may be possible to secure fee income from other financial institutions. Furthermore, by sharing information on the death of a policyholder early between financial institutions, the death information can be used as a trigger for freezing the policyholder's account or for paying insurance claims. This is also important for financial institutions in fulfilling their social responsibilities. Also,
Funeral-related businesses will be able to secure highly likely potential customers.

In other words, it will be possible to streamline the process of confirming the deceased person's asset information among the relevant parties and reduce costs.

The description of this specification makes clear at least the following: That is, in the inquiry support device of this embodiment, the arithmetic device uses inquiry APIs disclosed by the inquiry support device, the financial institution system, and the other financial institution system when transmitting and receiving information between the financial institution system and the other financial institution system;
It is also possible to use the following.

This makes it possible to appropriately use APIs currently in operation for inquiry response work in financial institution systems and apply them to the inquiry support method of the present invention, making it possible to implement a more efficient inquiry support method at low cost, and ultimately making the process of confirming the asset information of the deceased more efficient among the parties involved, thereby further reducing costs.

In addition, in the inquiry support device of this embodiment, the communication device may be capable of communicating with a funeral service provider system, and the calculation device may further perform the following processes: receiving a funeral service mediation request from the financial institution system, in addition to the success information and the account inquiry request, and sending the mediation request to the funeral service provider system, and obtaining in the funeral service provider system the result of the funeral service contract mediation between a funeral service provider that matches the contract conditions indicated in the mediation request and the surviving family members of the deceased.

This makes it possible to easily identify and use funeral services that match desired conditions, even for those who do not normally have the opportunity to use them and are unlikely to be aware of suitable services.

In the inquiry support method of the present embodiment, when the information processing device transmits and receives information between the financial institution system and the other financial institution system, the inquiry support device, the financial institution system, and the other financial institution system use an inquiry API disclosed by each of the financial institution system and the other financial institution system.
It is also possible to use the following.

In addition, in the inquiry support method of this embodiment, the information processing device may be capable of communicating with a funeral service provider system via the communication device, and may further execute the following processes: receiving a funeral service mediation request from the financial institution system, in addition to the success information and the account inquiry request; sending the mediation request to the funeral service provider system; and obtaining in the funeral service provider system the results of the funeral service contract mediation between a funeral service provider that matches the contract conditions indicated in the mediation request and the surviving family members of the deceased.

1 Network 100 Inquiry support device 101 Storage device 102 Program 103 Memory 104 Arithmetic device 105 Communication device 125 Communication destination management data 126 Inquiry request management data 127 Mediation reception management data 130 Inquiry request file 131 Inquiry result file 132 Funeral mediation request file 133 Funeral response result file 200 Financial institution system 250 Other financial institution system 300 Funeral business operator system 400 Various business entity systems

Claims (6)

a communication device that communicates with each financial institution system via a network;
a computing device that executes the following processes: a process of receiving, by communicating with a financial institution system of a specified financial institution, success information of an heir identification determination based on the family register information of the deceased and an account inquiry request for the deceased, when an account inquiry operation for the deceased occurs at the specified financial institution; a process of sending the received success information and account inquiry request to each of the other financial institution systems other than the specified financial institution among the financial institution systems, and acquiring results of the account inquiry operation for the deceased that was executed at each of the other financial institution systems with the success information as a prerequisite; and a process of returning the results obtained from each of the other financial institution systems to the financial institution system of the financial institution;
13. A query support device comprising: The computing device includes:
When transmitting and receiving information between the financial institution system and the other financial institution system,
This inquiry support device utilizes inquiry APIs disclosed by the financial institution system and the other financial institution system,
2. The inquiry support device according to claim 1. The communication device is capable of communicating with a funeral service provider system,
The computing device further executes a process of receiving a funeral service intermediation request from the financial institution system in addition to the success information and the account inquiry request, and a process of transmitting the intermediation request to the funeral service provider system and acquiring, in the funeral service provider system, a result of the funeral service contract intermediation conducted between a funeral service provider that matches the contract conditions indicated in the intermediation request and the surviving family of the deceased.
2. The inquiry support device according to claim 1. An information processing device,
A communication device is provided for communicating with each financial institution system via a network,
a process of communicating with a financial institution system of a specified financial institution to receive success information of an heir identification determination based on the deceased's family register information and an account inquiry request for the deceased, when an account inquiry operation for the deceased occurs at the specified financial institution; a process of sending the received success information and account inquiry request to each of the other financial institution systems other than the specified financial institution among the financial institution systems, and obtaining results of the account inquiry operation for the deceased that was executed in each of the other financial institution systems with the success information as a prerequisite; and a process of returning the results obtained from each of the other financial institution systems to the financial institution system of the financial institution.
2. A method for assisting a query, comprising: The information processing device,
When transmitting and receiving information between the financial institution system and the other financial institution system,
Using the inquiry API disclosed by the inquiry support device, the financial institution system, and the other financial institution system,
5. The method of claim 4, wherein the query is a query. The information processing device,
The communication device is capable of communicating with a funeral service provider system,
A process of receiving from the financial institution system a funeral service mediation request in addition to the success information and the account inquiry request, and a process of sending the mediation request to the funeral service provider system and acquiring in the funeral service provider system a result of a funeral service contract mediation conducted between a funeral service provider that matches the contract conditions indicated in the mediation request and the surviving family of the deceased;
5. The method of claim 4, further comprising:

Images