JP2021009499A - Heir relationship explanatory diagram creation support system, heir relationship explanatory diagram creation support method, and program - Google Patents

Abstract

To provide an heir relationship explanatory diagram creation support system that reduces labor of creating a highly accurate heir relationship explanatory diagram relative to a predetermined person such as a client.SOLUTION: Family register data related to a predetermined person is acquired. Then, lack of the family register data regarding the predetermined person is checked. In addition, when enough family register data is not available, insufficiency information indicating that enough family register data is not available is output.SELECTED DRAWING: Figure 1

Description

The present invention relates to an heir relationship explanatory diagram creation support system, an heir relationship explanatory diagram creation support method, and a program.

A trust bank that carries out business related to inheritance of the deceased's heritage, etc. may create an heir relationship explanatory diagram showing the relationship of heirs based on a predetermined person such as a client or the deceased in the business. Patent Document 1 discloses a technique for creating a diagram showing the relationship between heirs.

Japanese Patent No. 6490258

It is desirable that the heir relationship explanatory diagram includes all heirs. However, due to the lack of information such as documents submitted by the client regarding inheritance, it takes time and effort to create a highly accurate heir relationship explanatory diagram.

Therefore, an object of the present invention is to provide an heir relationship explanatory diagram creation support system, an heir relationship explanatory diagram creation support method, and a program that solve the above-mentioned problems.

According to the first aspect of the invention, the heir relationship explanatory diagram creation support system includes a family register data acquisition unit that acquires family register data relating to a predetermined person, a check unit that checks for a shortage of the family register data relating to the predetermined person, and a check unit. It is characterized by including a shortage information output unit that outputs shortage information indicating that the family register data is not complete when the family register data is not complete.

According to the second aspect of the invention, the method for supporting the creation of an explanatory diagram of the heir relationship acquires the family register data relating to the predetermined person, checks for the lack of the family register data relating to the predetermined person, and does not have the family register data. In addition, it is characterized by outputting insufficient information indicating that the data are not complete.

According to the third aspect of the invention, the program checks the computer of the heir relationship explanatory diagram creation support system for the family register data acquisition means for acquiring the family register data for the predetermined person and the lack of the family register data for the predetermined person. It is characterized in that it functions as a checking means and a lack information output means for outputting lack information indicating that the family register data is not available when the family register data is not available.

According to the present invention, it is possible to reduce the labor and time for creating a highly accurate heir relationship explanatory diagram based on a predetermined person such as a client.

It is a figure which shows the structure of the heir relationship explanatory diagram creation support system by this embodiment. It is a hardware configuration diagram of the creation support device by this embodiment. It is a functional block diagram of the creation support device by this embodiment. It is a figure which shows the processing flow of the creation support apparatus by this embodiment. It is a figure which shows the data example of the family register data integration list data by this embodiment. It is the first figure which shows the output example of the lack information by this embodiment. It is a second figure which shows the output example of the lack information by this embodiment. It is a figure which shows the example of the heir table by this embodiment. It is a figure which shows the example of the correlation explanatory diagram by this embodiment. It is a figure which shows the minimum structure of the heir relationship explanatory diagram creation support system by this embodiment. It is a figure which shows the processing flow by the heir relationship explanatory diagram creation support system of the minimum configuration by this embodiment.

Hereinafter, the heir relationship explanatory diagram creation support system according to the embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing a configuration of an heir relationship explanatory diagram creation support system according to the same embodiment.
The heir relationship explanatory diagram creation support system 100 is configured by connecting the creation support device 1 for creating an heir relationship explanatory diagram to a communication network. The creation support device 1 communicates with the terminal 2. The creation support device 1 may communicate with the family register management device 3 via an external network 101 such as the Internet. The family register management device 3 is a device that manages family register data managed by each local government or the like. Although only one family register management device 3 is shown in FIG. 1, the creation support device 1 may be connected to a plurality of family register management devices 3 managed by each local government by communication. The heir relationship explanatory diagram creation support system 100 composed of the creation support device 1 and the terminal 2 is managed by an heir relationship diagram creation support company such as a trust bank, for example.

FIG. 2 is a hardware configuration diagram of the creation support device.
As shown in FIG. 2, the creation support device 1 includes hardware such as a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a database 104, and a communication module 105. It is a computer. The terminal 2 and the family register management device 3 are also computers having the same hardware configuration.

FIG. 3 is a functional block diagram of the creation support device.
The creation support device 1 is activated when the power is turned on, and executes a creation support program for the heir relationship explanatory diagram stored in advance. As a result, the creation support device 1 has at least a control unit 11, a family register data acquisition unit 12, a list data generation unit 13, a check unit 14, a shortage information output unit 15, a data table generation unit 16, and an heir relationship explanatory diagram generation unit 17. , Each function of the interface unit 18 is exhibited.

The control unit 11 controls other functional units.
The family register data acquisition unit 12 acquires family register data related to a predetermined person such as a deceased person or a client. The family register data acquisition unit 12 may acquire the family register data from the family register management device 3 via the external network 101. The family register data acquisition unit 12 may acquire the family register data acquired from the client via the terminal 2 or the user interface.

The list data generation unit 13 generates the family register data integrated list data in which the family register data is integrated.
The check unit 14 lacks other family register data including other inheritance target persons other than the inheritance target person included in the family register data based on the predetermined attribute information of the person included in the family register data regarding the predetermined person such as the deceased person and the client. Check. In the present embodiment, the predetermined attribute information is the information on the removal of registration included in the family register data.
The shortage information output unit 15 outputs the shortage information when there is a shortage of family register data.

The data table generation unit 16 generates a relationship data table showing the relationship of the persons included in the family register data based on the family register data. More specifically, the data table generation unit 16 generates a relationship data table showing the relationship of the persons included in the family register data based on the relationship of the family register data.

The heir relationship explanatory diagram generation unit 17 generates and outputs an heir relationship explanatory diagram based on the relationship relationship included in the relationship data table.
The interface unit 18 has a function of a web server and inputs / outputs information to / from the terminal 2.

FIG. 4 is a diagram showing a processing flow of the creation support device.
Next, the processing flow of the creation support device will be described step by step.
The person in charge of the creation support company receives a request from the client to create an explanatory diagram of the heir relationship. The person in charge receives a copy of the family register including the client and the deceased from the client. The family register contains information on the client's or deceased's name, registered domicile, date of birth, birthplace, birth reporter, parents or adoptive parents' names, marriage history, divorce history, and enrolled persons (children, spouse, etc.) Family register information such as name, date of birth, names of parents and adoptive parents, spouse classification) is included. The person in charge may receive from the client a copy of the family register of the deceased person and the person who is expected to be the heir if the client is deceased. The person in charge scans one or more family register copies received with a scanner or the like and generates family register data including the information described in the family register copy for each family register copy. As an example, the family register data is data in which family register information such as the assigned number, name, relationship, and date of birth is associated with each registered person included in a copy of the family register. The person in charge performs an operation of storing one or more family register data in the terminal 2.

The person in charge connects the terminal 2 to the creation support device 1 by communication. When the terminal 2 is connected by communication, the interface unit 18 of the creation support device 1 transmits the creation support web page of the heir relationship explanatory diagram to the terminal 2 (step S101). The terminal 2 receives the creation support web page from the creation support device 1. The terminal 2 outputs a creation support web page to the monitor. On the creation support web page, information on the base person such as the name of the requester, an input field for information about the requester such as contact information, a selection field for family register data, and the name of the person who will be the base point (person) based on the heir relationship explanatory diagram. Input fields etc. are displayed. The person in charge inputs information in each input field using the creation support web page, and selects the family register data recorded in the terminal 2. A creation start button is displayed on the creation support web page. The person in charge performs an operation of pressing the creation start button. Then, the terminal 2 transmits the information input to the creation support web page and the creation start information including the selected family register data to the creation support device 1.

The interface unit 18 of the creation support device 1 acquires the creation start information (step S102). The interface unit 18 records the requester information, the base point person information, and the family register data included in the creation start information in the database 104 in association with the management number newly issued for the request. The person in charge may record the family register copy scan data generated by scanning the family register copy on the terminal 2 and operate the terminal 2 to transmit the family register copy scan data to the creation support device 1. In this case, the interface unit 18 of the creation support device 1 receives the family register copy scan data from the terminal 2 after transmitting the creation support web page to the terminal 2, and performs OCR processing on the family register copy scan data to obtain the family register data. It may be generated. Further, the interface unit 18 of the creation support device 1 may generate structured family register data as a result of OCR processing of the family register copy scan data, and transmit a web page capable of confirming and correcting the error of the family register data to the terminal 2. Good. As a result, the person in charge confirms the contents of the family register data using the terminal 2, and operates the terminal 2 to send the corrected data to the creation support device 1, and the creation support device 1 corrects the data. The family register data may be recorded in the database 104. The interface unit 18 outputs a list data generation instruction including a control number to the list data generation unit 13.

When the list data generation unit 13 acquires the list data generation instruction, the list data generation unit 13 acquires the management number included in the instruction. The list data generation unit 13 acquires one or more family register data recorded in the database 104 in association with the management number. The list data generation unit 13 generates family register data integrated list data including all registered persons included in one or a plurality of family register data (step S103).

FIG. 5 is a diagram showing a data example of family register data integration list data.
As shown in this figure, the family register data integrated list data includes the identification number (# 1, # 2, # 3, ...) of each family register linked to the management number of the family register data, the name of the person, and the year of birth. It is the data associated with each information described in the family register data such as the date, the relationship based on the base person, the status including information such as removal of registration, and the registered domicile. Here, one person may be recorded in multiple family register data. For example, the family register data in which the client is included as the first person includes the information of the client's father. If the client wishes to create an explanatory diagram of the heir relationship based on the deceased father, the client may hand over a copy of the family register of the deceased father to the person in charge. In this case, the family register data generated based on the copy of the family register of the father includes the father as the first person. In such a case, for example, the family register copy in which the client is the first person and the family register copy in which the father of the request form is the first person include information on the father of the client who is the same person. In this case, the family register data integrated list data generated by using each family register data corresponding to the family register copy includes two pieces of information about the client's father. The list data generation unit 13 associates the family register data integration list data with the management number and records it in the database 104.

When the list data generation unit 13 generates the family register data integrated list data, the list data generation unit 13 instructs the check unit 14 to check the lack of the family register data. The instruction includes a control number. The check unit 14 acquires one or more family register data recorded in the database 104 in association with the management number. Based on the information included in the acquired family register data, the check unit 14 determines whether family register data including another person who can be an heir candidate necessary for creating the heir relationship explanatory diagram is required (step S104).

Specifically, the check unit 14 specifies the family register data a including the base person as a registered person.
When the child of the base point person included in the family register data a is removed from the register, the check unit 14 determines whether the family register data b including the child is included in the acquired family register data. If the family register data b does not exist, the check unit 14 determines the family register data b as the acquisition target. The family register data b is family register data including the child of the base point person, and the child of the base point person is an example of the acquisition target person.

If there is no information on the child of the base point person included in the family register data a, the check unit 14 sets one of the parents of the base point person (second-ranked heir) included in the family register data a as the first person. It is determined whether or not the family register data c to be used is included in the acquired family register data. If there is no family register data c, the check unit 14 determines that the family register data c is to be acquired. The family register data c is family register data including the parents of the base point person, and the parents of the base point person is an example of the acquisition target person.

Further, when the check unit 14 has the family register data c and the relative heir who is the second rank of the base point person is removed from the family register, the person included in the family register data c (for example, among the brothers of the base point person). It is determined whether or not the family register data d including the person who was removed from the family register due to marriage among the third-ranked relatives such as the person who was removed from the family register due to marriage is included in the acquired family register data. If there is no family register data d, the check unit 14 determines that the family register data is to be acquired. The family register data d is family register data including the siblings of the base point person, and the siblings of the base point person are an example of the acquisition target person.

Further, the check unit 14 is in the case where there is family register data d, and the third-ranked blood relative heir is removed from the register due to death or the like, and the person has a child, and the child (base point) included in the family register data d. When a person's nephew or niece) is removed from the register due to marriage, it is determined whether the family register data e including the child is included in the acquired family register data. If there is no family register data e, the check unit 14 determines that the family register data is to be acquired. The family register data e is family register data including the children of the siblings of the base point person, and the children of the siblings of the base point person are the acquisition target persons.

The check unit 14 may determine whether other family register data including a person who can be a candidate for heir is required by another method. Possible heir candidates are the spouse of the base person and those included in his or her relatives. When the check unit 14 identifies in the family register data that a person who has been removed from the family register has been removed due to death, the check unit 14 does not determine that person as the target for acquiring the family register data. The process of the check unit 14 described above is based on the predetermined attribute information of the person included in the family register data regarding the predetermined person (base point person), and the other family register data including the inheritance target person other than the inheritance target person included in the family register data. This is one aspect of the process of checking for the lack of Further, the process of the check unit 14 described above is one aspect of a process of checking whether the family register data relating to a predetermined person has all the information of the person including the inheritance target person.

The check unit 14 gives an insufficient information output instruction including information (name, date of birth, registered domicile, address, etc.) of the person to be acquired and a management number included in the family register data specified as the acquisition target, and the insufficient information output unit 15 Output to. The shortage information output unit 15 generates shortage information indicating the information of the acquisition target person and the management number (step S105). The shortage information output unit 15 records the shortage information in the database 104. The shortage information output unit 15 may output the shortage information to the terminal 2 used by the person in charge. The shortage information output unit 15 instructs the interface unit 18 to output a web page of the shortage information. Then, the interface unit 18 generates a web page indicating the lack information and transmits it to the terminal 2. The terminal 2 displays a web page of missing information on the monitor. As a result, the person in charge can confirm the presence or absence of the family register information including the missing person to be acquired with respect to the request for creating the heir relationship explanatory diagram indicated by the management number based on the lack information. The person in charge requests the client to submit a copy of the family register including the missing person to be acquired regarding the request to create the heir relationship explanatory diagram.

FIG. 6 is a first diagram showing an output example of insufficient information.
The interface unit 18 displays a web page as shown in FIG. 6 in which each person included in the family register data specified as an acquisition target is displayed, and only the information of the acquisition target person among those persons is displayed in a highlighted manner. It may be generated and transmitted to the terminal 2.

FIG. 7 is a second diagram showing an output example of insufficient information.
As shown in FIG. 7, the interface unit 18 displays each person included in the family register data specified as the acquisition target in a tree diagram based on the base point person, and information on the acquisition target person among those persons. A web page displayed only in the highlighted manner may be generated and transmitted to the terminal 2.

The creation support device 1 may automatically acquire the information of the family register copy based on the lack information. In this case, the lack information output unit 15 outputs a family register information acquisition instruction including the lack information to the family register data acquisition unit 12. The family register data acquisition unit 12 identifies the local government to which the family register copy is requested to be acquired based on the registered domicile of the person to be acquired included in the insufficient information (step S106). The family register data acquisition unit 12 acquires the transmission destination (network address, etc.) of the family register management device 3 recorded in the database 104 in association with the information of the registered domicile. The family register data acquisition unit 12 transmits a family register copy acquisition request including information on the person to be acquired to the family register management device 3 of the acquisition destination (step S107).

The family register management device 3 of the destination specifies the information (name, date of birth, registered domicile, etc.) of the person to be acquired included in the family register copy acquisition request. The family register management device 3 acquires the data of the family register copy previously recorded in the database 104 in association with the information of the person to be acquired. The family register management device 3 generates reply data including the acquired family register copy data of the acquisition target person and the management number, and transmits the reply data to the creation support device 1.

The family register data acquisition unit 12 of the creation support device 1 acquires the data of the family register copy included in the reply data and the management number. The family register data acquisition unit 12 acquires reply data for each acquisition target person from each family register management device 3. The family register data acquisition unit 12 outputs a list data update instruction including the data of the family register copy and the management number to the list data generation unit 13. The list data generation unit 13 generates family register data including the information of the family register copy based on the family register copy data, associates it with the management number, and records it in the database 104.

Further, the list data generation unit 13 reads the family registration data integration list data recorded in the database 104 in association with the management number, and combines the newly generated family registration data with the family registration data integration list data to integrate the family registration data. The list data is updated (step S108). The list data generation unit 13 rewrites the family register data integration list data recorded in the database 104 in association with the management number with the updated family register data integration list data. The family register data integration list data is updated based on the data of the family register copy of the person to be acquired.

Similarly, when the person in charge receives a copy of the family register of the person to be acquired from the client, the list data generation unit 13 acquires the family register data generated and transmitted by the terminal 2 based on the copy of the family register. The list data generation unit 13 updates the family register data integrated list data based on the newly acquired family register data.

When the family register data of the person to be acquired is recorded in the database 104 by the interface unit 18, the check unit 14 can be another candidate for heirs necessary for creating an explanatory diagram of the heir relationship using the family register data. The process of determining whether family register data including a person is required may be repeated. The check unit 14 determines that the family register data including other persons who can be candidates for heirs necessary for creating the heir relationship explanatory diagram is not necessary, or receives an instruction from the administrator to end the acquisition of the family register data. In this case, the data table generation unit 16 is instructed to generate the heir table based on the family register data integrated list data. The instruction includes a control number.

The data table generation unit 16 specifies the control number based on the instruction for generating the heir table. The data table generation unit 16 acquires the family register data integration list data recorded in the database 104 in association with the management number. The data table generation unit 16 identifies the same person whose information is duplicated in a plurality of family register data among the persons included in the family register data integration list data. For example, the data table generation unit 16 identifies a person when a plurality of sets of information having the same combination of name and date of birth are included. The data table generation unit 16 generates an heir table (FIG. 8) in which the information of the specified person is put together (step S109). The data table generation unit 16 associates the heir table with the management number and records it in the database 104. Further, when the data table generation unit 16 generates the heir table, the data table generation unit 16 outputs a creation instruction to the heir relationship explanatory diagram generation unit 17. The creation instruction includes a control number. The generation of the heir table is one aspect of the process of generating the relationship data table showing the relationship of the persons included in the family register data based on the relationship of the family register data by the data table generation unit 16.

The heir relationship explanatory diagram generation unit 17 acquires the heir table from the database 104 based on the control number included in the creation instruction. The heir relationship explanatory diagram generation unit 17 is an inheritance in which the parent-child relationship, sibling relationship, and marital relationship are represented by a tree structure based on the person who is the base person based on the attributes of each person included in the heir table. A human relationship explanatory diagram (FIG. 9) is generated (step S110). The heir relationship explanatory diagram generation unit 17 records the data of the heir relationship explanatory diagram in the database 104 in association with the management number. Further, the heir relationship explanatory diagram generation unit 17 transmits information indicating the completion of creation of the heir relationship explanatory diagram to the terminal 2 (step S111). When there is a shortage of family register data, the process of the above-mentioned heir relationship explanatory diagram generation unit 17 further includes information on other inheritance targets included in other family register data acquired based on the shortage. This is one aspect of the process of generating an explanatory diagram.

The terminal 2 outputs information indicating the completion of the creation of the heir relationship explanatory diagram to the monitor. The information may include a control number, the client's name and contact information. The person in charge connects the terminal 2 to the creation support device 1 by communication. When the terminal 2 is connected to the communication, the interface unit 18 of the creation support device 1 transmits the creation support web page of the heir relationship explanatory diagram to the terminal 2. The terminal 2 receives the creation support web page from the creation support device 1. The terminal 2 outputs a creation support web page to the monitor. The creation support web page includes an input field for the management number and a button for displaying the heir relationship explanatory diagram. The person in charge inputs the management number in the input field and presses the display button of the heir relationship explanatory diagram. The terminal 2 transmits a display request of the heir relationship explanatory diagram including the management number to the creation support device 1.

The interface unit 18 of the creation support device 1 acquires a request for displaying the heir relationship explanatory diagram. The interface unit 18 acquires a control number from the display request. The interface unit 18 transmits the data of the heir relationship explanatory diagram recorded in the database 104 in association with the management number to the terminal 2. The terminal 2 receives the data of the heir relationship explanatory diagram. Then, the terminal 2 outputs the heir relationship explanatory diagram to the monitor. The person in charge contacts the client and provides a printout of the heir relationship explanatory diagram.

According to the above processing, the creation support device 1 can create an heir relationship explanatory diagram based on the family register copy provided by the client. By the processing of the check unit 14 of the creation support device 1, it is possible to automatically determine the necessity of acquiring a copy of the family register including the person to be acquired, which is insufficient for creating the heir relationship explanatory diagram, so that the client or the deceased It is possible to create a highly accurate heir relationship explanatory diagram based on the base person (predetermined person) such as, and to reduce the labor for creating the diagram. Further, by the processing of the family register data acquisition unit 12, it is possible to acquire the data of the family register copy of the person to be acquired, which is insufficient for creating the heir relationship explanatory diagram, so that the work of manually acquiring the family register copy is simplified. , It is possible to reduce the labor of creating the heir relationship explanatory diagram.

FIG. 8 is a diagram showing an example of an heir table.
The heir table is composed of information such as each heir's name, date of birth, relationship, status, death flag, legal heir flag, and legal heir ratio based on the base person (person). In this way, the data table generation unit 16 generates an heir table in which status information such as removal from the family register and a death flag indicating whether or not the person is dead are linked to each person based on the information contained in the family register data. You can. Further, as shown in FIG. 8, the data table generation unit 16 determines the information of the legal heir flag indicating whether or not it is a legal heir by using an heir determination algorithm, and creates an heir table linked to each person. May be generated. Further, as shown in FIG. 8, the data table generation unit 16 may generate an heir table associated with each person by determining the value of the legal inheritance ratio by using the inheritance ratio algorithm. Further, the data table generation unit 16 may generate an heir table in which each person is sorted in the order of legal inheritance.

FIG. 9 is a diagram showing an example of an explanatory diagram of the correlation person relationship.
The heir relationship explanatory diagram is a diagram showing a parent-child relationship, a sibling relationship, and a marital relationship in a tree structure based on the person who is the base person, using all the persons included in the heir table.

FIG. 10 is a diagram showing the minimum configuration of the heir relationship explanatory diagram creation support system.
FIG. 11 is a diagram showing a processing flow by the heir relationship explanatory diagram creation support system having the minimum configuration.
The heir relationship explanatory diagram creation support system may include at least a family register data acquisition unit 12, a check unit 14, and a lack information output unit 15.
The family register data acquisition unit 12 acquires family register data related to a predetermined person (step S801).
The check unit 14 checks for a lack of family register data regarding a predetermined person (step S802).
When the family register data is not available, the lack information output unit 15 outputs the lack information indicating that the family register data is not available (step S803).

Each of the above devices has a computer system inside. The process of each process described above is stored in a computer-readable recording medium in the form of a program, and the process is performed by the computer reading and executing this program. Here, the computer-readable recording medium refers to a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like. Further, this computer program may be distributed to a computer via a communication line, and the computer receiving the distribution may execute the program.

Further, the above program may be for realizing a part of the above-mentioned functions. Further, a so-called difference file (difference program) may be used, which can realize the above-mentioned functions in combination with a program already recorded in the computer system.

1 ... Creation support device 2 ... Terminal 3 ... Family register management device 11 ... Control unit 12 ... Family register data acquisition unit 13 ... Data table generation unit 14 ... Check unit 15 ...・ Insufficient information output unit 16 ・ ・ ・ Heir relationship explanatory diagram generation unit 17 ・ ・ ・ Interface unit

Claims (10)

The family register data acquisition department that acquires family register data related to a predetermined person,
A check unit that checks for the lack of family register data related to the predetermined person,
When the family register data is not available, the missing information output unit that outputs missing information indicating that the family register data is not available,
Heir relationship explanatory diagram creation support system equipped with. The check unit checks the lack of other family register data including other inheritance target persons included in the family register data based on the predetermined attribute information of the person included in the family register data regarding the predetermined person. ,
The heir relationship explanatory diagram creation support system according to claim 1. The check unit is the heir relationship explanatory diagram creation support system according to claim 1, which checks whether the family register data regarding the predetermined person has all the information of the person including the inheritance target person. When the predetermined attribute information included in the family register data indicates at least information on removal from the family register, the check unit lacks other family register data including other inheritance target persons other than the inheritance target person included in the family register data. The heir relationship explanatory diagram creation support system according to claim 2, which determines that the data is being used. It is provided with a data table generation unit that generates a relationship data table showing the relationship of persons included in the family register data based on the family register data.
Any of claims 1 to 4, wherein the data table generation unit includes a relationship data table showing the relationship of persons included in the family register data based on the relationship of the family register data. The heir relationship explanatory diagram creation support system described in paragraph 1. An heir relationship explanatory diagram generation unit that generates and outputs an heir relationship explanatory diagram based on the relationship relationship,
The heir relationship explanatory diagram creation support system according to claim 5. When there is a shortage of the family register data, the heir relationship explanatory diagram generation unit generates the heir relationship explanatory diagram further including information on other inheritance targets included in the family register data acquired based on the shortage. The heir relationship explanatory diagram creation support system according to claim 6. The lack information output unit identifies the real address of the person to be acquired, which is the person specified based on the predetermined attribute information among the persons included in the family register data regarding the predetermined person, and the family register management device corresponding to the real place. The heir relationship explanatory diagram creation support system according to claim 7, which sends a family register copy acquisition request including information on the person to be acquired to. Obtain family register data for a given person and
Check for the lack of family register data related to the predetermined person,
A method for supporting the creation of an explanatory diagram of heir relationships, which outputs insufficient information indicating that the family register data is not available when the family register data is not available. The computer of the heir relationship explanatory diagram creation support system,
Family register data acquisition means for acquiring family register data related to a predetermined person,
Checking means for checking the lack of family register data for the predetermined person,
Insufficient information output means for outputting insufficient information indicating that the family register data is not available when the family register data is not available.
A program that functions as.

Images