JP2018185611A - Information management system and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To fairly and reliably disclose message contents of a deceased to a plurality of persons having connection to him or her.SOLUTION: A management server 10 comprises a database 12 in which message contents to be disclosed to specific persons having connection to a user, and a plurality of persons having connection to the user to whom the message contents are to be disclosed are stored in association with an account of the user. Upon receipt of a death notice reporting the death of the user, the management server 10 transmits a confirmation notice for requesting confirmation of the death of the user, to each of user terminals 30 of the persons having connection to the user, which are associated with the account of the user. Then, on the condition that a response indicating confirmation of the death of the user has been accepted from all the persons having connection to the user, to whom the confirmation notice has been transmitted, the management server 10 can disclose message contents of disclosed information associated with the account to each of the user terminals 30 of the plurality of persons having connection to the user.SELECTED DRAWING: Figure 1

Description

  The present disclosure relates to an information management system for disclosing a message stored by a deceased person before life to a specific related person, and a program used in the information management system.

  In Patent Document 1, a deceased person records information about himself / her / relatives / acquaintances before his life, and the death person's death is used as a trigger to transmit the information recorded by the deceased person to a limited range desired by the deceased person. It describes the personal information management system.

JP 2012-168664 A

  The information handled in the personal information management system as described above may include, for example, information on interests among related persons such as information on inheritance of heritage. For this reason, when the deceased's message is disclosed to a related person, it is important to take care not to cause trouble among a plurality of related persons. For example, some relatives who know the death of the deceased earlier than other relatives need to devise measures to prevent the act of obtaining the deceased's message and running away from other relatives. It is done. This indication is made in order to solve such a subject.

An information management system according to an aspect of the present disclosure includes a database, a death reception unit, a confirmation notification unit, an answer reception unit, and a disclosure control unit.
The database is configured to store account information that is information related to an account set for the user. Further, the database is configured to store disclosure information including at least message content to be disclosed to a specific related person related to the user in association with the account information of the user. In addition, the database includes related person information including information that can specify the contact information of each of a plurality of related persons who are targets of disclosing the message content of the disclosed information associated with the account information of the user. It is configured to store in association with each other.

  The death reception unit is configured to receive a death notice indicating that the user has died. On the condition that the confirmation notification unit has received the death notification, the contact information of each of the related persons identified from the related person information associated with the account information of the user corresponding to the death notification, A confirmation notification requesting confirmation of the user's death is transmitted.

  The answer receiving unit is configured to receive answers from a plurality of related persons to whom the confirmation notification is transmitted by the confirmation notifying unit. On the condition that the disclosure control unit has received a reply that the user's death has been accepted from all of the plurality of related persons to whom the confirmation notification has been transmitted, the account information is sent to the contact information of each of the plurality of related persons. The message content of the disclosure information associated with is configured to be disclosed.

  According to the information management system described above, the contents of the message are disclosed on the condition that all of the related persons associated with the user's account have agreed that the user has died. That is, at the stage where only some of the designated related persons agree to the death of the user, the message content of the user is not disclosed to any of the related persons. As a result, the contents of the user's message can be surely disclosed to all the related persons, and troubles such that some of the related persons run away from other related persons can be prevented.

  Further, the information management system of the present disclosure may be configured as follows. That is, the database is configured to be able to store account information regarding a plurality of accounts for a single user. Further, the database is configured so that disclosure information and related person information regarding a plurality of related persons can be individually associated with each other and stored for a plurality of pieces of account information regarding a single user. The confirmation notification unit confirms the death of the user with respect to the contact information of each of the related persons identified from the related person information associated with the plurality of account information of the user corresponding to the death notification. It is configured to send the requested confirmation notification.

  Then, the disclosure control unit is configured to be able to disclose the message content for each of the plurality of account information as follows. That is, on the condition that a response indicating that the user's death has been accepted is received from all of the plurality of related persons associated with one account information, the account information is sent to the contact information of each of the plurality of related persons. The message content of the disclosure information associated with is enabled to be disclosed.

  For example, there are various degrees of relationship between various persons who can be designated as relatives, such as family members, relatives, friends / acquaintances, lawyers, and property organizers, and the deceased depending on the degree of the relationship. The content of the message contents that he wants to convey may be different. Therefore, by allowing one user to have a plurality of accounts, it is possible to register a plurality of related persons and message contents to be transmitted to the related persons for each account. By doing so, it is possible to perform various operations such as grouping related persons for each account and changing the contents of the message contents disclosed for each group.

  Further, the information management system of the present disclosure may be configured as follows. That is, the disclosure information in the database further includes date information indicating the date on which the message content should be disclosed after the user's death. The disclosure control unit is configured to be able to disclose the message content of the disclosure information when the date indicated by the date information included in the disclosure information has arrived. According to such a configuration, for example, various operations such as disclosing message contents corresponding to each node to related persons at the timing of each year such as annual death are possible.

  Further, the information management system of the present disclosure may be configured as follows. That is, the information processing apparatus further includes a confirmation information receiving unit that receives input of death confirmation information that is information for confirming the death of the user based on the authority of the administrator. When the death control information is received, the disclosure control unit sends the user's message to the contact information of each of the plurality of related persons regardless of whether there is a response from the plurality of related persons to whom the confirmation notification is transmitted. The content is configured to be disclosed. According to such a mechanism, in the situation where it is difficult for the relatives to acknowledge the death of the user due to some unforeseen circumstances, the message content is exceptionally disclosed to the relatives based on the administrator's authority. Can do.

  Further, the information management system of the present disclosure may be configured as follows. That is, the related person corresponding to the related person information associated with the account information of the user is another user whose account information is registered in the database. According to such a configuration, it is possible to realize an information management system capable of managing information related to a user who wants to entrust a message content to a related person and information related to a related person who should receive the message content.

  Further, the information management system of the present disclosure may be configured as follows. That is, a biological signal measured by a wearable terminal that is mounted on a user's body and configured to measure and transmit the user's biological signal to the outside is acquired, and the user's life and death is determined based on the acquired biological signal. The apparatus further includes a determination unit configured to determine the state. And the death reception part is comprised so that the determination result by the determination part may be acquired as a death notification.

  By using a wearable terminal attached to the user's body, the user's biological signal can be constantly observed. Then, by using a biological signal that can always be watched by the wearable terminal, the user's life / death state can be determined promptly and a notification can be quickly transmitted to the related person.

  As a user interface for a user who uses the information management system according to the present disclosure and a related person, for example, a communication terminal such as a smartphone or a tablet computer may be used. Specifically, the following program may be mounted on these communication terminals. The program is a program that causes a computer to execute an account registration procedure, a related person registration procedure, a disclosure information registration procedure, a reception procedure, a transmission procedure, and an output procedure.

  The account registration procedure is a procedure for registering input account information in the information processing system. The related person registration procedure is a procedure for registering the input related person information in the information processing system in association with the account information. The disclosure information registration procedure is a procedure for registering the input disclosure information in association with the account information in the information processing system. The reception procedure is a procedure for receiving a confirmation notification transmitted from the information processing system. The transmission procedure is a procedure for transmitting, to the information processing system, an answer indicating that the user has been killed on the condition that the user indicated by the received confirmation notice has been accepted as a result of accepting an operation that acknowledges that the user has died. . The output procedure is a procedure for accessing the message content of the disclosed information that can be disclosed by the information processing system and outputting the content of the message content.

  According to the program configured as described above, it is possible to realize a user interface for both the user and the related person in the information management system of the present disclosure.

The figure showing the whole structure of an information management system. The figure showing the logical structure of a "users" table. The figure showing the logical structure of an "accounts" table. The figure showing the logical structure of a "bereaves" table. The figure showing the logical structure of a "messages" table. The figure showing the logical structure of a "movie_messages" table. The figure showing the list of functions of a pre-organization application. The figure showing an example of the process performed in an information management system. The figure showing the modification of the process performed in an information management system. The figure showing the example of a screen display in a pre-organization application. The figure showing the example of a screen display in a pre-organization application.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In addition, this indication is not limited to the following embodiment, It is possible to implement in various aspects.
[Description of information management system configuration]
The configuration of the information management system of the embodiment will be described with reference to FIG. As illustrated in FIG. 1, the information management system includes a management server 10 connected to a network 100 that is a wide area network such as the Internet.

  The management server 10 is a server computer that executes various processes related to a service that manages information related to pre-arrangement of registered users. Hereinafter, this service is referred to as a pre-organization service. The management server 10 is mainly composed of a CPU, RAM, ROM, auxiliary storage device, input / output interface and the like (not shown). The function of the management server 10 is realized by the CPU executing a program stored in a non-transitional physical storage medium such as a ROM or a semiconductor memory. The management server 10 includes a control unit 11 and a database 12 as a functional configuration.

  The control unit 11 has a function of providing various types of information in response to a request from a dedicated application for a pre-organization service (hereinafter referred to as a pre-organization application) that operates on the user terminal 30 connected to the network 100. . Communication between the user terminal 30 connected to the network 100 and the management server 10 is performed in a state where data exchange is encrypted by a well-known HTTPS (Hypertext Transfer Protocol Secure) mechanism. In addition, the control unit 11 has a function of managing a database in which information related to registered users is stored, and executing a service such as providing information corresponding to each user based on the stored information. As a function for managing the database 12, a known relational database management system such as PostgreSQL (registered trademark) is installed in the control unit 11.

  The database 12 is a database for storing various types of information related to users who have the authority to use the pre-organization service. The database 12 stores a table in which data groups related to users are grouped in a table format for each information type. Tables stored in the database 12 include a table of information relating to user definitions, a table of information relating to user accounts, a table of information relating to related persons associated with user accounts, a table of information relating to message contents, and the like. It is. In these tables, information defining the relationship between the data of each table is also recorded. Here, detailed contents of main tables stored in the database 12 will be described with reference to FIGS.

<<"users" table >>
The “users” table illustrated in FIG. 2 is a table in which information relating to definitions of users registered as members of the pre-organization service is recorded. As illustrated in FIG. 2, the “users” table has attributes # 1 to # 5 including “id”, “push_id”, “os”, “created_at”, and “updated_at”. In the “users” table, a set of values (hereinafter also referred to as records) corresponding to the attributes # 1 to # 5 is recorded for each user. Each attribute defines a type that represents a possible range of values. The contents of each attribute in the “users” table illustrated in FIG. 2 are as follows.

  “Id” is an attribute representing a unique identifier for identifying a user, and a recorded value is an integer type. The attribute “id” is a primary key in the “users” table, and is used to specify the record of the user.

  “Push_id” is an attribute representing unique identification information corresponding to the user terminal 30 used when performing push notification to the user terminal 30 corresponding to the user. The value recorded in the attribute of “push_id” is a character varying type.

  “Os” is an attribute representing the type of operating system (ie, OS) installed in the user terminal 30 corresponding to the user, and the recorded value is a character varying type. In the present embodiment, for example, iOS (registered trademark), Android (registered trademark), or the like is assumed as an OS installed in the user terminal 30.

  “Created_at” is an attribute representing the date and time when the record related to the user is created in the “users” table, and the recorded value is a timestamp without time zone type. “Updated_at” is an attribute indicating the date and time when the record related to the user is updated, and the recorded value is a timestamp without time zone type.

<<"accounts" table >>
The “accounts” table illustrated in FIG. 3 is a table in which information related to accounts set for each user registered in the above-described “users” table is recorded. In the present embodiment, at least one account can be set for one user.

  As illustrated in FIG. 3, the “accounts” table includes “id”, “user_id”, “created_at”, “updated_at”, “user_type”, “name”, “tel”, “prefecture_id”, “postcode”, It has attributes # 1 to # 15 consisting of “address1”, “address2”, “email”, “encrypted_password”, “reset_password_token”, and “passed_date”. In the “accounts” table, a set of values (that is, records) corresponding to the attributes # 1 to # 15 is recorded for each account. Each attribute defines a type that represents a possible range of values. The contents of each attribute in the “accounts” table illustrated in FIG. 3 are as follows.

  “Id” is an attribute representing a unique identifier for identifying an account set for a user, and a recorded value is an integer type. The attribute “id” is a primary key in the “accounts” table, and is used to specify the record of the account.

  “User_id” is an attribute representing an identifier of a user associated with the account, and a recorded value is an integer type. In the “user_id” attribute, a value common to the “id” attribute of the user in the “users” table (see FIG. 2) is recorded as an identifier of the user associated with the account. As a result, it is possible to specify the correspondence between the user registered in the “users” table and the account registered in the “accounts” table. In the “accounts” table, by providing a plurality of records in which a common user identifier is recorded in the “user_id” attribute, a plurality of accounts can be set for one user.

  “Created_at” is an attribute representing the date and time when the record related to the account is created in the “accounts” table, and the recorded value is a timestamp without time zone type. “Updated_at” is an attribute representing the date and time when the record related to the account is updated, and the recorded value is a timestamp without time zone type.

  “User_type” is an attribute representing the type of user in the account, and the recorded value is an integer type. In this “user_type” attribute, for example, a general user is recorded as 0, a property organizer is set as 1, a lawyer is set as 2, an advisor is set as 3, and a predetermined numerical value corresponding to the user type is recorded.

  “Name” is an attribute representing the name of the user in the account, and the recorded value is of the character varying type. The name recorded in the attribute “name” is displayed on the user terminal 30 as a name representing the account. “Tel” is an attribute representing a telephone number as a contact information of the user in the account, and a recorded value is a character varying type.

  “Prefecture_id” is an attribute representing a code for identifying the prefecture to which the user's address in the account belongs, and the recorded value is an integer type. “Postcode” is an attribute representing a postal code corresponding to the user's address in the account, and the recorded value is of a character varying type. “Address1” is an attribute representing the upper hierarchy of the user's address in the account, and the recorded value is a character varying type. “Address2” is an attribute representing the lower hierarchy of the user's address in the account, and the recorded value is a character varying type. “Email” is an attribute representing an e-mail address as a contact of a user in the account, and a recorded value is a character varying type.

  “Encrypted_password” is an attribute representing an encrypted password used for authentication for logging in to the account, and a recorded value is a character varying type. “Reset_password_token” is an attribute representing a token used for authentication when resetting a password set in the account, and a recorded value is a character varying type.

  “Passed_date” is an attribute indicating the date on which the user corresponding to the account died, and the recorded value is a datetime type. In the attribute “passed_date”, NULL is recorded as an initial value, and when the management server 10 determines the death of the user based on the notification from the outside, the date of the death is recorded.

"Bereaves" table
The “bereaves” table illustrated in FIG. 4 is a table in which information on relatives associated with the user's account is recorded. Here, the relative is a concept including a person having a specific relationship with the user, such as a family member, a relative, a friend, an acquaintance, a lawyer, or a property organizer. The relatives associated with the user's account in the “bereaves” table are persons who are to be disclosed after the user dies the message contents recorded in advance by the user.

  In the present embodiment, the relatives associated with the user's account are other users whose accounts are registered in the database 12. Further, at least two or more related persons' accounts are associated with one account. Further, when a plurality of accounts are set for one user, it is possible to associate the account of the relative with each account.

  As illustrated in FIG. 4, the “bereaves” table has attributes # 1 to # 5 including “id”, “account_id”, “account_target_id”, “created_at”, and “updated_at”. In the “bereaves” table, a set of values (that is, records) corresponding to the attributes # 1 to # 5 is recorded for each of the related persons associated with each account. Each attribute defines a type that represents a possible range of values. The contents of each attribute in the “bereaves” table illustrated in FIG. 4 are as follows.

  “Id” is an attribute representing a unique identifier for identifying a record of a relative associated with an account, and a recorded value is an integer type. The attribute of “id” is a primary key in the “bereaves” table.

  “Account_id” is an attribute representing the account of the user who has designated the relative, and the recorded value is an integer type. In the “account_id” attribute, a value common to the “id” attribute of the account in the “accounts” table (see FIG. 3) is recorded. As a result, the correspondence between the user account registered in the “accounts” table and the record recorded in the “bereaves” table can be specified. Also, in the “bereaves” table, by providing a plurality of records that record common account identifiers in the “account_id” attribute, a plurality of related persons can be set for one account.

  “Account_target_id” is an attribute representing a relative's account associated with the account indicated by the “account_id” attribute, and the recorded value is an integer type. In the “account_target_id” attribute, a value common to the “id” attribute of the account in the “accounts” table (see FIG. 3) is recorded. As a result, it is possible to identify the correspondence between the account of the relative registered in the “accounts” table and the record recorded in the “bereaves” table.

  “Created_at” is an attribute representing the date and time when the record was created in the “bereaves” table, and the recorded value is a timestamp without time zone type. “Updated_at” is an attribute indicating the date and time when the record is updated, and the recorded value is a timestamp without time zone type.

<<"messages" table >>
The “messages” table illustrated in FIG. 5 is a message content that is disclosed to a related person associated with the user's account, and records information related to the message content including text information such as a document. It is. In the present embodiment, at least one message content can be set for one account.

  As illustrated in FIG. 5, the “messages” table has attributes # 1 to # 6 including “id”, “account_id”, “message”, “day_of_publish”, “created_at”, and “updated_at”. In this “messages” table, a set of values (that is, records) corresponding to the attributes # 1 to # 6 is recorded for each message content. Each attribute defines a type that represents a possible range of values. The contents of each attribute in the “messages” table illustrated in FIG. 5 are as follows.

  “Id” is an attribute representing a unique identifier for identifying the message content corresponding to the user's account, and the recorded value is an integer type. The attribute of “id” is a primary key in the “messages” table, and is used to specify the record of the message content.

  “Account_id” is an attribute representing the account of the user who prepared the message content, and the recorded value is an integer type. In the “account_id” attribute, a value common to the “id” attribute of the account in the “accounts” table (see FIG. 3) is recorded. Thereby, it is possible to specify the correspondence between the user account registered in the “accounts” table and the record recorded in the “messages” table. In the “messages” table, by providing a plurality of records in which the common account identifier is recorded in the “account_id” attribute, a plurality of message contents can be associated with one account.

  “Message” is an attribute representing character information such as a document constituting the message content, and a recorded value is a text type. “Day_of_publish” is an attribute that represents the date on which the message content is disclosed, and the recorded value is an integer type. The value recorded in the attribute “day_of_publish” is, for example, a value representing the number of days from the date of death of the user to the date of disclosure.

  “Created_at” is an attribute indicating the date and time when the record is created in the “messages” table, and the recorded value is a timestamp without time zone type. “Updated_at” is an attribute representing the date and time when the record is updated, and the value to be recorded is a timestamp without time zone type value.

<<"movie_messages" table >>
The “movie_messages” table illustrated in FIG. 6 is a message content disclosed to a related person associated with the user's account, and information related to the message content including image information such as a moving image or a still image is recorded. It is a table to be. In the present embodiment, at least one message content can be set for one account.

  As illustrated in FIG. 6, the “movie_messages” table has attributes # 1 to # 6 including “id”, “account_id”, “path”, “day_of_publish”, “created_at”, and “updated_at”. In the “movie_messages” table, a set of values (that is, records) corresponding to the attributes # 1 to # 6 is recorded for each message content. Each attribute defines a type that represents a possible range of values. The contents of each attribute in the “movie_messages” table illustrated in FIG. 6 are as follows.

  “Id” is an attribute representing a unique identifier for identifying the message content corresponding to the user's account, and the recorded value is an integer type. The attribute of “id” is a primary key in the “movie_messages” table, and is used to specify the record of the message content.

  “Account_id” is an attribute representing the account of the user who prepared the message content, and the recorded value is an integer type. In the “account_id” attribute, a value common to the “id” attribute of the account in the “accounts” table (see FIG. 3) is recorded. Thereby, it is possible to specify the correspondence between the user account registered in the “accounts” table and the record recorded in the “movie_messages” table. Also, in the “movie_messages” table, by providing a plurality of records in which the common account identifier is recorded in the “account_id” attribute, a plurality of message contents can be associated with one account.

  “Path” is an attribute representing the location (namely, path) in the database 12 of an image file such as a moving image or a still image constituting the message content, and a recorded value is a character varying type. “Day_of_publish” is an attribute that represents the date on which the message content is disclosed, and the recorded value is an integer type. The value recorded in the attribute “day_of_publish” is, for example, a value representing the number of days from the date of death of the user to the date of disclosure.

  “Created_at” is an attribute representing the date and time when the record is created in the “movie_messages” table, and the recorded value is a timestamp without time zone type. “Updated_at” is an attribute indicating the date and time when the record is updated, and the recorded value is a timestamp without time zone type.

  Returning to the description of FIG. The administrator terminal 20 is an administrator terminal device that is used by being connected to the management server 10, and includes an input device such as a keyboard and an output display. The administrator terminal 20 has a function of giving an instruction to the management server 10 based on the authority of the administrator who operates the information management system.

  The user terminal 30 is a portable information terminal having a function as a user interface for the user to use the pre-organization service. The user terminal 30 is embodied by a high-function mobile phone such as a so-called smartphone, a tablet computer, or the like, and is connected to the network 100 using mobile data communication or wireless LAN communication.

  The user terminal 30 is mainly configured by a CPU, RAM, ROM, semiconductor memory such as a flash memory (not shown), an input / output interface, a wireless communication device, and the like. As an input / output device with which user terminal 30 is provided, a liquid crystal display, a speaker, a microphone, a touch panel, a fingerprint sensor, etc. are illustrated, for example. The function of the user terminal 30 is realized when the CPU executes a program stored in a non-transitional tangible storage medium such as a ROM or a semiconductor memory.

  The user terminal 30 is installed with a living arrangement application that provides a user interface function for using the living arrangement service. The user terminal 30 exchanges information with the management server 10 through the pre-organization application, transmits information input from the user to the management server 10, and presents various information based on the information received from the management server 10. To do.

Here, specific examples of main functions provided by the pre-organization application running on the user terminal 30 will be described with reference to FIG.
As illustrated in FIG. 7, the pre-organization application has functions for general users such as “register user”, “set / add account”, “post on bulletin board”, “disclose message content” `` Set a relative you want to do '', `` Create and save an ending note '', `` Create and save a message '', `` Contact a professional qualifier '', `` View information '', `` Register as a paid member '' And the like. In addition, functions such as "write column" and "comment on bulletin board" are further provided as functions for professional qualification contractors such as lawyers, estate organizers, and advisors. In addition, the function for general users can be utilized also about the user who corresponds to a professional qualified trader.

The outline of each function described above is as follows.
(1) The “register user” function is a function for registering a user in the information management system at an early stage of using the pre-organization service through the pre-organization application. For example, the pre-organization application executes a procedure for setting authentication information for the user to log in to the pre-organization application. As authentication information, for example, it is conceivable to use a password or biometric information (fingerprint, vein, retina, etc.).

  In addition, the pre-organization application transmits information necessary for registering information regarding the new user and the user terminal 30 used by the user to the management server 10 to the management server 10. The information transmitted here includes, for example, device information including information indicating the type of OS of the user terminal 30, unique identification information necessary for performing push notification to the user terminal 30, and the like.

  The control unit 11 of the management server 10 creates a new record for the new user in the “users” table (see FIG. 2) of the database 12 based on the information about the new user and the user terminal 30 received from the pre-organization application. To do.

  (2) The “setting / adding account” function is a function for setting an account for a registered user. Specifically, the pre-organization application displays a GUI for receiving input of various information necessary for setting an account from the user, and transmits information input from the user to the management server 10 in accordance with the GUI. The information transmitted here includes, for example, the name of the user used in the account, the user type, the telephone number, the postal code, the address, the e-mail address, the password for accessing the account, and the password reset. Information such as tokens.

  The control unit 11 of the management server 10 newly creates a record related to the new account in the “accounts” table (see FIG. 3) of the database 12 based on the information regarding the account setting received from the pre-organization application. In the record relating to this account, the id of the corresponding user is recorded. As a result, the user registered in the “users” table is associated with the new account registered in the “accounts” table.

  (3) The “post to bulletin board” function is a function to post an article input by the user to an electronic bulletin board operated as part of the pre-organization service by the management server 10. An electronic bulletin board is a network environment in which articles can be written, comments about articles can be written, and such information can be browsed.

  (4) The function of “setting a relative who wants to disclose message contents” is a function for setting, for each account, a related person whose message contents prepared by the user are to be disclosed. Specifically, the pre-organization application displays a GUI for accepting input of information for identifying a relative associated with the account while logged in to the account, and follows the GUI. Information input from the user is transmitted to the management server 10. As information for specifying a related person, for example, an e-mail address registered in the account of the related person may be used. In the present embodiment, in order to be able to disclose the message content to a related person, it is a requirement to register two or more related persons per account.

  The control unit 11 of the management server 10 newly creates a record related to the new related person in the “bereaves” table (see FIG. 4) based on the information related to the setting of the related person received from the pre-organization application. Specifically, the control unit 11 specifies the account of the user corresponding to the related person from the “accounts” table of the database 12 based on the e-mail address of the related person received from the pre-organization application. Then, the control unit 11 newly adds a record including “account_id” representing the account of the user who designated the relative and “account_target_id” representing the account of the designated relative to the “bereaves” table. As a result, the account of the user who designates the related person from the accounts registered in the “accounts” table is associated with the account of the related person.

  (5) The function of “creating / saving an ending note” is a function of creating and saving an “ending note”, which is one form of message content that the user wants to disclose to a relative, for each account. Here, the ending note is information in which items to be conveyed to the relatives are gathered along items prepared in advance.

  The items that can be recorded in the ending notes include, for example, self-introduction, personal history, etc., list of relatives, friends, acquaintances, property / insurance / pension etc., pets, graves and funerals. These include things you want to request, PIN numbers for various services, and wills.

  The pre-organization application displays a GUI including input items for inputting information in accordance with the item of the ending note in a state where the account is logged in, and the information input from the user according to the GUI is displayed on the management server 10. Send to. The control unit 11 of the management server 10 newly creates a record related to the new message content in the “message” table (see FIG. 5) based on the information representing the content of the ending note received from the pre-organization application. In the record related to the message content, “account_id” indicating the account of the corresponding user is recorded. Thereby, the account registered in the “accounts” table is associated with the new message content registered in the “message” table.

  (6) The “create / save a message” function is a function that creates and saves a “message”, which is one form of message content that the user wants to disclose to a relative, for each account. The message here is information such as a document in which a matter to be transmitted to a relative is freely described without providing a specific theme or item, or a moving image / still image taken by the user.

  The pre-organization application displays a GUI for accepting input of character information constituting the message in a state where the account is logged in, and transmits information input from the user to the management server 10 in accordance with the GUI. Alternatively, the pre-organization application activates a camera and a microphone provided in the user terminal 30 to capture a moving image or a still image of the user, and transmits the captured image file to the management server 10 as a message.

  In addition, the pre-organization application receives an input of a date on which a document message or an image message should be disclosed from the user, and transmits information representing the input date to the management server 10 together with the message. In addition, as a thing which can be designated as a date which should disclose a message, the day of milestones, such as an annual death, is raised, for example. In addition, for a message that should be disclosed promptly after the user's death, there is no need to specify a date.

  The control unit 11 of the management server 10 newly creates a record regarding new message contents in the “messages” table (see FIG. 5) or “move_messages” (see FIG. 6) based on the message information received from the pre-organization application. To do. In the record related to the message content, “account_id” indicating the account of the corresponding user is recorded. Thereby, the account registered in the “accounts” table is associated with the new message content registered in the “message” table or the “move_messages” table.

  (7) The function of “contacting a professionally qualified company” is a function for notifying a specific user's account registered as a professionally qualified company such as a lawyer, a property organizer, an advisor, or the like.

  (8) The “browse information” function is a browsing function for displaying various contents provided from the management server 10 on a display. For example, the pre-organization application acquires content data such as an electronic bulletin board, a column posted by a professional qualification contractor, an ending note or a message of a deceased user from the management server 10 and displays it.

  The contents of messages such as the ending notes and messages of the deceased user are managed on the condition that after the user's death, a predetermined confirmation procedure was performed by a plurality of related persons associated with the user's account. Disclosed by server 10. Details of this series of procedures will be described later.

  (9) The “register as a paying member” function is a function for registering a user to a paying member who is given a privilege by paying a predetermined membership fee. For example, among the functions for creating message contents, the function for creating and saving ending notes is a service limited to paid members, and the function for creating and saving messages regardless of whether or not a paid member is registered. One example is to make it available.

  (10) The “write column” function is a function provided for a user who is registered as a professional qualified contractor. This function is a function for publishing articles for general users created by professional qualification contractors.

  (11) The “comment on the bulletin board” function is a function provided for users registered as professional qualified contractors. This function is a function for posting a comment (ie, less) to an article posted on an electronic bulletin board by a general user.

[Explanation of processing related to disclosure of message content]
When the registered user dies, the management server 10 refers to the sequence diagram of FIG. 8 for the processing procedure for disclosing the message contents to the relatives associated with the account of the user (hereinafter referred to as the deceased). While explaining. In the case of FIG. 8, when the user dies (step S0), it is assumed that at least one of the relatives associated with the deceased account is informed of the deceased death by some method. In addition, it is assumed that the deceased's death certificate has been submitted by the surviving family to the management department of the pre-organization service.

  In step S <b> 100, the death notice regarding the deceased is transmitted to the management server 10 through the pre-organization application from the user terminal 30 of the relative who knows the death of the deceased. The transmission of the death notice is executed based on the operation instructions of the relatives in the pre-organization application. This death notice includes information identifying the deceased account.

  In step S <b> 102, the control unit 11 of the management server 10 confirms the death of the deceased with respect to the user terminals 30 of all the related persons associated with the account corresponding to the death notification received from the user terminal 30. Send the confirmation notification you want. Specifically, the control unit 11 is associated with the deceased account based on the relationship between users associated with each other in the “users” table, “accounts” table, and “bereaves” table of the database 12. Extract the relatives who are. And the control part 11 transmits the confirmation notification which asks for confirmation of the deceased's death by the push notification for the user terminal 30 corresponding to the extracted relative. Alternatively, a confirmation notification may be transmitted by e-mail to the e-mail address corresponding to the extracted relative. When a plurality of accounts are set for the deceased, the control unit 11 transmits a confirmation notification to the relatives associated with all the accounts.

  In step S <b> 104, each user terminal 30 that has received the confirmation notification from the management server 10 transmits a reply that acknowledges death to the management server 10 on the condition that the related person has performed an input operation that acknowledges the death of the deceased. This answer includes information representing the account of the sender's relative. In step S <b> 106, the control unit 11 of the management server 10 receives responses transmitted from the user terminals 30 of a plurality of related persons.

  In step S <b> 108, the control unit 11 determines whether or not an answer permitting death has been received from all the related persons associated with the deceased account. When a plurality of accounts are set for the deceased, the control unit 11 makes a determination for each individual account. In other words, the control unit 11 makes an affirmative determination on the account on the condition that a reply confirming death is received from all the related persons associated with one account.

  If an affirmative determination is made in step S108, the control unit 11 proceeds to step S100. In step S110, the control unit 11 determines the death of the deceased for the account for which a positive determination is made. Specifically, the control unit 11 records the date of death in the attribute “passed_date” of the deceased account in the “accounts” table of the database 12. In the next step S112, the control unit 11 sends a message for which all of the related persons associated with the account for which death has been confirmed has no disclosure date among the message contents corresponding to the account. Disclose the contents.

  Specifically, the control unit 11 extracts a list of message contents such as ending notes and messages disclosed from the “messages” table and the “move_messages” table of the database 12. And the control part 11 notifies the list of message contents, such as an ending note and a message to disclose, to the user terminal 30 of the relative who becomes the object of disclosure. Accordingly, the message content data to be browsed can be acquired from the management server 10 based on the list of message content notified from the management server 10 at the user terminal 30 of the relative.

  On the other hand, among the message contents corresponding to the account whose death has been confirmed, the control unit 11 performs the following for the message contents for which the date of disclosure is set. That is, in step S114, the control unit 11 determines whether or not the current date has passed the date corresponding to the date of disclosure of the message content. When the date corresponding to the date of disclosure of the message content has passed, the control unit 11 proceeds to step S116. In step S116, the contents of the message whose disclosure date has passed are disclosed.

  In step S118, the related person's user terminal 30 acquires the message content data disclosed in the management server 10, displays it on the display, and allows the related person to view the data. Specifically, the user terminal 30 acquires message content data from the management server based on the list of message content notified from the management server 10. In response to the acquisition request from the user terminal 30, the management server 10 transmits the disclosed message content data to the requesting user terminal 30. And the user terminal 30 displays character information, a moving image, a still image, etc. based on the acquired message content data.

  On the other hand, in the management department that has received the deceased death certificate, in step S120, the manager confirms the fact of the deceased death by a predetermined procedure. Then, the administrator understood that it was difficult to send a reply that acknowledged the death of the deceased due to some unavoidable circumstances for any of the relatives associated with the deceased account. If you do: It is an exceptional measure taken to avoid situations where the deceased's message content is not disclosed permanently.

  That is, in step S122, the administrator performs an input operation for confirming the death of the account of the deceased corresponding to the deceased who cannot answer from the administrator terminal 20 to the management server 10. In step S110, the control unit 11 of the management server 10 that has accepted the input operation for determining the death from the administrator terminal 20 in step S122 determines the death of the deceased for the account, and proceeds to the processes in and after S112.

[Variation of processing related to disclosure of message content]
A modification of the process illustrated in FIG. 8 will be described with reference to FIG. In the case of FIG. 8 described above, the case where the death notice is transmitted to the management server 10 from the user terminal 30 of the relative who is informed of the death of the deceased in step S100 has been described. On the other hand, the example of FIG. 9 employs a configuration in which the management server 10 determines a user's life / death state based on a user's biological signal measured by a wearable terminal attached to the user's body. The case is different.

  The wearable terminal includes a sensor that measures a biological signal representing a wearer's heart rate, blood pressure, body temperature, and the like, and a communication device that performs wireless communication with an external communication device (for example, the user terminal 30). The biometric signal of the wearer is configured to be transmitted to an external communication device. The external communication device transmits to the management server 10 user biometric information including the biometric signal received from the wearable terminal and the identification information of the user wearing the wearable terminal. The wearable terminal preferably has a shape such as a ring or a bracelet that can be worn in a manner that is less uncomfortable for the wearer, and is operated by a built-in power source or a wirelessly supplied power source.

  As illustrated in FIG. 9, in step S <b> 101, the control unit 11 of the management server 10 determines whether the user is alive or dead based on the received user biometric information data. Specifically, the control unit 11 compares the biometric signal included in the user biometric information with given reference data serving as a determination criterion for the life / death state, and determines the user's life / death state based on the comparison result.

  When it determines with the user having died in step S101, the control part 11 progresses to step S102. In step S <b> 102, the control unit 11 transmits a confirmation notification requesting confirmation of the death of the deceased to the user terminals 30 of all the related persons associated with the deceased account. Since the procedure after step S102 is the same as that of the example of FIG. 8, description is abbreviate | omitted.

[Example of Screen Display on User Terminal 30]
Next, a screen display example of the pre-organization application on the user terminal 30 will be described with reference to FIGS. 10 and 11.

  FIG. 10 is a screen display example in a series of procedures from the start of the pre-organization application to account registration and relative setting. First, (1) in FIG. 10 is a screen display example immediately after the start of the pre-organization application. On the screen immediately after startup, for example, a button for starting fingerprint authentication for logging into the pre-organization application is provided. When this button is pressed on the touch panel, the screen shifts to a user authentication screen illustrated in (2) of FIG.

  (2) of FIG. 10 is an example of a user authentication screen for accepting fingerprint authentication for the user to log in to the pre-organization application. On this user authentication screen, the user login is established on the condition that the user's fingerprint read by the fingerprint sensor matches the pre-registered fingerprint.

  After the user login is established, if no account is registered for the user, the screen shifts to an account registration screen illustrated in (3) of FIG. As illustrated in FIG. 10 (3), the account registration screen is provided with an input form for inputting various information necessary for registering an account. After the user inputs necessary information according to the input form, when the “Register” button is pressed, the input information is transmitted from the user terminal 30 to the management server 10, and the account of the user is registered in the management server 10. The

  On the other hand, when an account has already been registered for the user after the login of the user is established, or when an account has been registered on the account registration screen of (3) in FIG. 10, the example is illustrated in (4) of FIG. Move to the account selection screen. As illustrated in (4) of FIG. 10, a list of registered accounts is displayed on the account selection screen. When one account to be signed in is selected from the list of accounts displayed on this account selection screen and the “OK” button is pressed, the screen shifts to the account authentication screen illustrated in (5) of FIG. To do.

  As illustrated in (5) of FIG. 10, the account authentication screen is provided with an input form for inputting a password for logging in to the selected account. On this account authentication screen, login to the account is established on condition that the password entered in the input form matches the password registered in advance in association with the account. After the login to the account is established, the screen shifts to an account screen illustrated in (6) of FIG.

  As illustrated in FIG. 10 (6), the account screen displays a list of functions available to the user in the logged-in account. When the “account management” button is pressed from the list of functions displayed on the account screen, the screen shifts to the account management screen illustrated in (7) of FIG.

  As illustrated in (7) of FIG. 10, the account management screen displays a list of functions for performing management related to the logged-in account. When the “related party setting” button is pressed from the list of functions displayed on the account management screen, the screen shifts to the related party setting screen illustrated in (8) of FIG.

  As illustrated in (8) of FIG. 10, the related person setting screen is for specifying a plurality of related persons who are to be disclosed messages when a user corresponding to the logged-in account dies. An input form is provided. In the case of (8) in FIG. 10, the account can be designated as a relative by entering the mail address registered in the account of another user in the input form. In the case of (8) in FIG. 10, it is possible to input the mail addresses of two related persons, but a configuration in which more than two related persons can be designated may be used.

  When the “input” button is pressed after the user inputs the mail address of the relative according to the input form, the input information is transmitted from the user terminal 30 to the management server 10. The management server 10 extracts a related person account corresponding to the received e-mail address from the accounts registered in the database 12, and corresponds the extracted related person account to the account designated as the related person. At the same time, it is registered in the database 12.

  Next, FIG. 11 is an image display example in a series of procedures from transmission of a death notice, transmission of a reply that acknowledges death, and browsing of message contents. Note that the image display example in FIG. 11 assumes a screen display example on the account side designated by the relative from the account “acc3” in which the relative is registered in the example of FIG.

  (1) in FIG. 11 is a list of accounts of other users (hereinafter referred to as designated accounts) who designate the logged-in account as a relative. In the case of (1) in FIG. 11, the account “acc3” is displayed in the list of designated accounts, and a “notify” button is provided. The “notify” button is an icon for executing a function of notifying the management server 10 of the first report when the user corresponding to the designated account dies. When the “notify” button displayed on the nominated account list screen is pressed, the screen shifts to a death notification screen illustrated in (2) of FIG.

  As illustrated in (2) of FIG. 11, the death notification screen is provided with an input form for inputting the date when the corresponding user died in the account “acc3”. After the user inputs the date of death of the designated user according to the input form, when a “decision” button is pressed, a death notification including information on the input date is transmitted from the user terminal 30 to the management server 10. It has become. When the management server 10 receives the death notice regarding the account “acc3”, the management server 10 reports the death of the account “acc3” to the accounts of the relatives associated with all the accounts of the user corresponding to the account “acc3”. Send a confirmation notification requesting confirmation.

  In each user terminal 30 that has received the confirmation notification from the management server 10, as illustrated in (3) of FIG. 11, “There is a notification” on the account screen that is a relative of the account “acc3”. Display is made. When the “There is a notification” button is pressed on this account screen, the screen shifts to a notification screen exemplified in (4) of FIG.

  As illustrated in (4) of FIG. 11, a list of accounts corresponding to the confirmation notification received from the management server 10 is displayed on the notification screen. When the user selects an account for proceeding from the list of accounts displayed on the notification screen, the screen shifts to an answer transmission screen illustrated in (5) of FIG.

  As illustrated in (5) of FIG. 11, the reply transmission screen is provided with a “notify” button for replying that the death of the account “acc3” is acknowledged together with a sentence informing the death of the account “acc3”. When the “acknowledge” button is pressed on this answer transmission screen, an answer that acknowledges death is transmitted from the user terminal 30 to the management server 10. The management server 10 waits for responses from the accounts of all the related persons who have transmitted the confirmation notification regarding the account “acc3”.

  While the management server 10 is waiting for an answer from another related person, as shown in (6) of FIG. 10, the “accounting” display is displayed together with the display of the account “acc3” on the nominated account list screen. Is provided. At this time, the message content related to the account “acc3” cannot be viewed on the user terminal 30 of each related person. After that, when answers from all the related persons associated with the account “acc3” are obtained, the management server 10 discloses the message contents of the account “acc3” to the corresponding related accounts of the related persons. .

  As a result, as illustrated in (7) of FIG. 10, an “information browsing” button is provided together with the display of the account “acc3” on the nominated account list screen in the account of the relative. When this “information browsing” button is pressed, the message content list screen illustrated in (8) of FIG. 10 is displayed.

  As illustrated in (8) of FIG. 10, the message content list screen displays a list of message content items of the account “acc3”. On this message content list screen, the message content corresponding to the selected item can be browsed by selecting the item that the user wants to browse. For example, when the “view message” item is selected on the message content list screen illustrated in (8) of FIG. 10, the process proceeds to the message list screen illustrated in (9) of FIG. 10.

  As illustrated in (9) of FIG. 10, a list of messages already disclosed by the management server 10 is displayed on the message list screen. On this message list screen, when a user selects a message to be viewed, character information and an image of the selected message are displayed. However, in addition to the message displayed on the message list screen, for example, if there is a message with the date of disclosure of 7th disappointment and it has not reached 7th disappointment at present, that message is displayed on the message list screen. It cannot be viewed.

[effect]
The information management system according to the embodiment has the following effects.
The contents of the message are disclosed on the condition that all of the related persons associated with the user's account have agreed that the user has died. That is, at the stage where only some of the designated related persons agree to the death of the user, the message content of the user is not disclosed to any of the related persons. As a result, the contents of the user's message can be reliably disclosed to all the related persons, and troubles such that some of the related persons run away from other related persons can be prevented.

  One user can have a plurality of accounts, and for each account, a plurality of related persons and contents of messages to be transmitted to the related persons can be registered. As a result, for various persons designated as related persons, various operations such as grouping related persons for each account according to the degree of relationship with the user, and changing the contents of the message content disclosed for each group. It becomes possible.

  A disclosure date can be set for the message content. As a result, for example, various operations such as disclosing message contents corresponding to each section to the relatives at the timing of each section such as annual death are possible.

  An instruction for confirming the death of the user can be input from the administrator terminal 20. As a result, in a situation where it is difficult for the related person to give a reply that acknowledges the user's death due to some unforeseen circumstances, the message content can be exceptionally disclosed to the related person based on the authority of the administrator.

  A user who wants to transmit a message content to a related person and a user who views the message content of the deceased as a related person are both managed as users having an account in the pre-organization service. Accordingly, it is possible to realize an information management system capable of managing information related to a user who wants to entrust a message content to a related person and information related to a related person who should receive the message content.

  By constantly observing the biological signal measured by the wearable terminal worn on the user's body, the user's life / death state can be determined promptly and a notification can be promptly transmitted to the related person.

[Correspondence with configuration described in claims]
The correspondence between each configuration of the embodiment and the configuration described in the claims is as follows.
A process in which the control unit 11 of the management server 10 receives a death notification from the user terminal 30 corresponds to a process as a death accepting unit. The processing in step S102 executed by the control unit 11 of the management server 10 corresponds to processing as a confirmation notification unit. The process of step S106 executed by the control unit 11 of the management server 10 corresponds to a process as an answer receiving unit. A process in which the control unit 11 of the management server 10 receives an input of death confirmation from the administrator terminal 20 corresponds to a process as a confirmation information receiving unit. The processing of step S112 and step S114 executed by the control unit 11 of the management server 10 corresponds to processing as a disclosure control unit. The process of step S101 executed by the control unit 11 of the management server 10 corresponds to the process as the determination unit.

[Modification]
The functions of one component in each of the above embodiments may be shared by a plurality of components, or the functions of a plurality of components may be exhibited by one component. Moreover, you may abbreviate | omit a part of structure of each said embodiment. In addition, at least a part of the configuration of each of the above embodiments may be added to or replaced with the configuration of the other above embodiments. It should be noted that all aspects included in the technical idea specified from the words described in the claims are embodiments of the present disclosure.

  For example, in the above-described embodiment, a case has been described in which a relative who is the subject of disclosure of the message content of a deceased user is a user who has an account for the pre-arrangement service as with the user. Not only this but the structure which can set the person who is not registered as a user of the pre-organization service as a relative is also possible. In that case, it may be configured to send a confirmation notification requesting confirmation of the death of the deceased and a notification that the content of the message is disclosed to the e-mail of the person registered as a relative.

  In various forms such as a system having the above-described management server 10 as a configuration requirement, a program for causing a computer to function as the management server 10, a non-transitional actual recording medium such as a semiconductor memory storing the program, an information management method, etc. The present disclosure can also be realized.

  DESCRIPTION OF SYMBOLS 10 ... Management server, 11 ... Control part, 12 ... Database, 20 ... Manager terminal, 30 ... User terminal, 100 ... Network.

Claims (7)

Account information, which is information related to an account set for a user, is stored, and message disclosure information including at least a message content to be disclosed to a specific related person related to the user is included in the account information of the user. The associated information including information that can be stored in association with each other, and that can specify the contact information of each of the plurality of related persons who are to be disclosed the message contents of the disclosed information associated with the account information of the user. A database configured to be stored in association with the account information;
A death reception unit configured to receive a death notice indicating that the user has died,
On the condition that the death notice is received by the death reception unit, for the contact information of each of the related persons identified from the related person information associated with the account information of the user corresponding to the death notice, A confirmation notification unit configured to send a confirmation notification requesting confirmation of the user's death;
An answer accepting unit configured to accept answers from a plurality of related persons to whom the confirmation notice is transmitted by the confirmation notifying part;
On the condition that the reply accepting unit accepts a reply to acknowledge the death of the user from all of the plurality of related persons to whom the confirmation notification has been transmitted, for the contact information of each of the plurality of related persons, A disclosure control unit configured to enable disclosure of the message content of the disclosure information associated with the account information;
An information management system comprising: The database is configured to be able to store account information related to a plurality of accounts for a single user, and the related information about the disclosure information and related persons for each of the plurality of account information related to the single user. And can be stored individually associated with each other,
The confirmation notifying unit, on the condition that the death notice has been received, contacts each of a plurality of related persons identified from the related person information respectively associated with the plurality of account information of the user corresponding to the death notification. To send a confirmation notice requesting confirmation of the user ’s death,
The disclosure control unit, for each of the plurality of account information, on the condition that a response to acknowledge the death of the user from all of a plurality of relatives associated with one account information, It is configured to enable disclosure of the message content of the disclosure information associated with the account information for each contact of the relative.
The information management system according to claim 1. The disclosure information of the database further includes due date information indicating the due date on which the content of the message should be disclosed after the death of the user,
The disclosure control unit is configured to enable disclosure of the message content of the disclosure information when the date indicated by the date information included in the disclosure information has arrived.
The information management system according to claim 1 or 2. Based on the authority of the administrator in the information management system, further comprising a confirmation information receiving unit that accepts input of death confirmation information that is information for confirming the death of the user,
The disclosure control unit, when accepting death confirmation information by the confirmation information receiving unit, regardless of the presence or absence of responses from a plurality of related persons to whom the confirmation notification is transmitted, to the contact information of each of the plurality of related persons In contrast, the message content of the disclosure information associated with the user account information is configured to be disclosed,
The information management system according to any one of claims 1 to 3. The related person corresponding to the related person information associated with the account information of the user is another user whose account information is registered in the database.
The information management system according to any one of claims 1 to 4. Obtaining a biological signal measured by a wearable terminal attached to the user's body and configured to measure and transmit the user's biological signal to the outside, and based on the acquired biological signal, whether the user is alive or dead A determination unit configured to determine the state;
The death reception unit is configured to acquire the determination result by the determination unit as the death notification.
The information management system according to any one of claims 1 to 5. A program for causing a computer provided in a communication terminal used by the user and the relative in the information processing system according to any one of claims 1 to 6,
An account registration procedure for registering the input account information in the information processing system;
A related person registration procedure for registering the input related person information in the information processing system in association with the account information;
Disclosure information registration procedure for registering the input disclosure information in the information processing system in association with the account information;
A receiving procedure for receiving a confirmation notification transmitted from the information processing system;
A transmission procedure for transmitting to the information processing system an answer indicating that the user has been killed on the condition that the user indicated by the confirmation notice received in the reception procedure has accepted an operation that acknowledges that the user has died. When,
An output procedure for accessing the message content of the disclosure information that has been disclosed by the information processing system and outputting the content of the message content;
A program for causing the computer to execute.

Images