JP7768345B2 - Health management support device, system, method and program - Google Patents

Description

This disclosure relates to health management support devices, systems, methods, and programs.

In recent years, it has become increasingly important to manage the health of workers while taking into account their working environment. Patent Document 1 discloses technology for calculating arrival and departure times from authentication results. Patent Document 2 discloses technology for calculating seated time from information collected from a wearable device, and for issuing health management recommendations if seated time exceeds a threshold.

Japanese Patent Application Laid-Open No. 2021-089638 Japanese Patent Application Laid-Open No. 2017-170066

Here, managing a person's health condition requires collecting and analyzing various types of information. However, collecting and analyzing various types of information to identify stress factors when an abnormality occurs in a person's health condition is cumbersome, and there is a problem in that it is often difficult to identify the cause.

In view of the above-mentioned problems, the purpose of this disclosure is to provide a health management support device, system, method, and program for supporting health management by collecting and analyzing various types of information to manage health status.

The health management support device according to the present disclosure comprises:
a first acquisition means for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquiring means for acquiring authentication history information including a personal authentication result and an authentication location of the first user;
a derivation means for deriving factor-related information relating to factors that have influenced the health state of the first user based on the basic health information and the authentication history information;
Equipped with.

The health management support system according to the present disclosure includes:
an authentication terminal for performing personal authentication of a user;
a health management support device;
The health management support device includes:
a first acquisition means for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquiring means for acquiring authentication history information including a result of personal authentication of the first user by the authentication terminal and an authentication location;
a derivation means for deriving factor-related information relating to factors that have influenced the health state of the first user based on the basic health information and the authentication history information;
Equipped with.

The health management support method according to the present disclosure includes:
The computer
Acquire basic health information of the first user measured by a measurement terminal worn by the first user;
acquiring authentication history information including a personal authentication result and an authentication location of the first user;
Based on the basic health information and the authentication history information, factor-related information regarding factors that have influenced the health state of the first user is derived.

The health management support program disclosed herein includes:
a first acquisition process for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquisition process for acquiring authentication history information including a personal authentication result and an authentication location of the first user;
a derivation process for deriving factor-related information relating to factors that have affected the health state of the first user based on the basic health information and the authentication history information;
to be executed by the computer.

This disclosure provides a health management support device, system, method, and program for collecting and analyzing various types of information to manage health status and assist in health management.

1 is a block diagram showing a configuration of a health management support device according to a first embodiment. 1 is a flowchart showing the flow of a health management support method according to the first embodiment. FIG. 10 is a block diagram showing the configuration of a health management support system according to a second embodiment. FIG. 10 is a block diagram showing the configuration of an authentication device according to a second embodiment. FIG. 10 is a block diagram showing the configuration of a health management support device according to a second embodiment. 10 is a flowchart showing the flow of a user information registration process according to the second embodiment. 10 is a flowchart showing the flow of a face information registration process performed by the authentication device according to the second embodiment. FIG. 10 is a sequence diagram showing the flow of a process for registering basic health information according to the second embodiment. FIG. 11 is a sequence diagram showing the flow of a registration process of authentication history information according to the second embodiment. 10 is a flowchart showing the flow of face authentication processing by the authentication device according to the second embodiment. 10 is a flowchart showing the flow of an analysis process according to the second embodiment. FIG. 10 is a diagram for explaining the concept of specific example 2-1 according to the second embodiment. FIG. 10 is a diagram for explaining the concept of specific example 2-2 according to the second embodiment. FIG. 10 is a diagram for explaining the concept of specific example 2-3 according to the second embodiment. FIG. 10 is a diagram for explaining the concept of specific example 2-4 according to the second embodiment. FIG. 10 is a diagram for explaining the concept of specific example 2-5 according to the second embodiment. FIG. 10 is a diagram for explaining the concept of specific example 2-6 according to the second embodiment.

Embodiments of the present disclosure will now be described in detail with reference to the drawings. In each drawing, identical or corresponding elements are designated by the same reference numerals, and duplicate descriptions will be omitted as necessary for clarity.

<Embodiment 1>
FIG. 1 is a block diagram showing the configuration of a health management support device 1 according to the first embodiment. The health management support device 1 is an information processing device for supporting the health management of a predetermined user. Here, it is assumed that a first user, who is the predetermined user, wears a measurement terminal capable of measuring basic health information from the body. The measurement terminal then transmits basic health information such as measurement values to the health management support device 1 periodically, at predetermined timing, or in response to a request from the health management support device 1. Here, the basic health information includes the user's skin temperature, pulse rate, number of steps, amount of conversation, sleep time, etc.

The first user also performs personal authentication to verify their identity (identify their identity) using the authentication terminal. Here, personal authentication includes biometric authentication such as facial recognition, and authentication for verifying their identity using electronic identification information. If the authentication terminal is successful in personal authentication of the first user, it transmits authentication history information including the personal authentication result (identification information of the first user and the time of authentication) and the authentication location (information indicating the installation location of the authentication terminal, etc.) to the health management support device 1. The authentication terminal may also register the authentication history information in the health management support device 1 or another storage device.

The health management support device 1 comprises a first acquisition unit 11, a second acquisition unit 12, and a derivation unit 13. The first acquisition unit 11 acquires basic health information of the first user measured by a measurement terminal worn by the first user. The second acquisition unit 12 acquires authentication history information including the first user's personal authentication result and authentication location. The derivation unit 13 derives factor-related information regarding factors that have affected the first user's health condition based on the basic health information and authentication history information.

Figure 2 is a flowchart showing the flow of the health management support method according to the first embodiment. First, the first acquisition unit 11 acquires basic health information of the first user measured by a measurement terminal worn by the first user (S11). Next, the second acquisition unit 12 acquires authentication history information including the personal authentication result and authentication location of the first user (S12). Then, the derivation unit 13 derives factor-related information relating to factors that have affected the health condition of the first user based on the basic health information and the authentication history information (S13).

In this way, in this embodiment 1, the first user's basic health information and authentication history information are collected, and by comprehensively considering these, factors that have affected the health condition and information that can contribute to the analysis of those factors can be derived as factor-related information. Therefore, the administrator who manages the first user's health can easily understand the factors that have affected the first user's health condition using the factor-related information. Alternatively, the administrator can use the factor-related information to easily perform various analyses and formulate health management indicators from the analysis results. In other words, health management can be supported by collecting and analyzing various types of information to manage the health condition.

The health management support device 1 includes a processor, memory, and storage device, which are not shown in the figure. The storage device stores a computer program that implements the processing of the health management support method according to this embodiment. The processor then loads the computer program from the storage device into the memory and executes the computer program. This allows the processor to realize the functions of the first acquisition unit 11, the second acquisition unit 12, and the derivation unit 13.

Alternatively, each component of the health management support device 1 may be realized by dedicated hardware. Furthermore, some or all of the components of each device may be realized by general-purpose or dedicated circuits, processors, etc., or a combination of these. These may be configured by a single chip, or by multiple chips connected via a bus. Some or all of the components of each device may be realized by a combination of the above-mentioned circuits, etc., and programs. Furthermore, processors that can be used include CPUs (Central Processing Units), GPUs (Graphics Processing Units), FPGAs (Field-Programmable Gate Arrays), quantum processors (quantum computer control chips), etc.

Furthermore, when some or all of the components of the health management support device 1 are realized by multiple information processing devices, circuits, etc., the multiple information processing devices, circuits, etc. may be centrally or decentralized. For example, the information processing devices, circuits, etc. may be realized as a client-server system, cloud computing system, etc., in which each is connected via a communications network. Furthermore, the functions of the health management support device 1 may be provided in SaaS (Software as a Service) format.

<Embodiment 2>
The second embodiment is a specific example of the first embodiment described above. The second embodiment illustrates an example of a health management support system for supporting the health management of members (users) of an organization such as a company. FIG. 3 is a block diagram showing the configuration of a health management support system 1000 according to the second embodiment. A facility 200 is a building that serves as a base for activities, work, tasks, breaks, etc. within the organization. The facility 200 has various areas 210, 220, etc., and authentication terminals 120-1, 120-2, etc. are installed in each area. It is assumed that within the facility 200, there are users U1 to U3 who are the targets of health management, and an administrator UA who manages the health of users U1, etc. It is assumed that users U1, etc. and administrator UA may spend time outside the facility 200, for example, at home, outside of their organizational activity hours. Alternatively, there may be multiple facilities 200, and each user, etc. may be located at multiple different locations. The facility 200 may also be the home of each user, etc.

The health management support system 1000 comprises measurement terminals 110-1 to 110-3, authentication terminals 120-1 and 120-2, a management terminal 300, an authentication device 400, and a health management support device 500. Each of the measurement terminals 110-1, etc., authentication terminals 120-1, etc., the management terminal 300, the authentication device 400, and the health management support device 500 is communicably connected via a network N. Here, the network N is a wired or wireless communication line or communication network, such as a LAN (Local Area Network), the Internet, a wireless communication network, a mobile phone network, etc. Furthermore, the network N can use any type of communication protocol.

Let us assume that user U1 is wearing measurement terminal 110-1, user U2 is wearing measurement terminal 110-2, and users U1 and U2 are staying within area 210. Let us also assume that user U3 is wearing measurement terminal 110-3 and is staying within area 220. Note that the area in which each user is staying is merely an example at a certain point in time. Here, measurement terminals 110-1 to 110-3 have equivalent functions, and may be collectively referred to below as "measurement terminal 110." Furthermore, users U1 to U3 are members of the above-mentioned organization, for example, workers or employees working for a company. Below, users U1 to U3 may be collectively referred to as "user U." Furthermore, user U may include administrator UA.

The measurement terminal 110 is a wearable device worn on the body of the user U. The measurement terminal 110 measures measurement information, which is information indicating the physical health status of the user U wearing the device, as basic health information. The measurement terminal 110 also transmits a basic health information registration request, including the measurement terminal ID, measurement time, and measurement information, to the health management support device 500. The measurement terminal 110 may be equipped with a microphone. In this case, the measurement terminal 110 may detect the volume of sound picked up by the microphone and calculate the picked-up time as the conversation time. Alternatively, the measurement terminal 110 may determine from the picked-up sound whether it is the wearer's own voice or the voice of another person (such as a conversation partner), and separately tally the conversation time when the wearer is speaking and the conversation time when the other person is speaking. Alternatively, the measurement terminal 110 may measure the above-mentioned basic health information using known technology.

Authentication terminal 120-1 is installed in area 210, and authentication terminal 120-2 is installed in area 220. Here, authentication terminals 120-1 and 120-2 have equivalent functions, and hereinafter they may be collectively referred to as "authentication terminal 120."

In this example, the authentication terminal 120 performs facial authentication as personal authentication. The authentication terminal 120 captures an image of an area including the user's face using a built-in or connected camera, and transmits a facial authentication request including the captured facial image and the authentication terminal ID to the authentication device 400 or health management support device 500 via network N. The facial authentication request may also include time information such as the time of capture or transmission. The facial authentication request may also include location information indicating the installation location of the authentication terminal 120.

The authentication terminal 120 may be a user terminal operated by the user U. The user terminal may transmit a facial recognition request, including an image of the user captured by a built-in or connected camera and the user terminal's location information, to the authentication device 400 or the health management support device 500 via the network N. The user terminal may also be a mobile terminal carried by the user U. The user terminal may also perform a process to register the user's facial image (facial feature information) in the authentication device 400 in advance. For example, the user terminal transmits a registration request for user information, including a facial image, personal information, and the measurement terminal ID of the measurement terminal being worn, to the health management support device 500. In this case, the health management support device 500 registers the user's facial information in the authentication device 400.

The authentication device 400 is an information processing device that manages users' facial feature information and performs facial authentication. In response to a facial authentication request received from an external device, the authentication device 400 compares the facial image or facial feature information included in the request with the facial feature information of each user and returns the comparison result (authentication result) to the requestor.

Figure 4 is a block diagram showing the configuration of an authentication device 400 according to embodiment 2. The authentication device 400 comprises a face information database (DB) 410, a face detection unit 420, a feature point extraction unit 430, a registration unit 440, and an authentication unit 450. The face information DB 410 stores a user ID 411 and facial feature information 412 for that user ID in association with each other. The facial feature information 412 is a collection of feature points extracted from a facial image. The authentication device 400 may delete the facial feature information 412 in the face information DB 410 in response to a request from a user or the like corresponding to the facial feature information 412. Alternatively, the authentication device 400 may delete the facial feature information 412 after a certain period of time has elapsed since registration.

The face detection unit 420 detects a facial area included in a registration image for registering facial information and outputs the detected area to the feature point extraction unit 430. The feature point extraction unit 430 extracts feature points from the facial area detected by the face detection unit 420 and outputs facial feature information to the registration unit 440. The feature point extraction unit 430 also extracts feature points included in a facial image received from a health management support device 500 or the like and outputs the facial feature information to the authentication unit 450.

When registering facial feature information, the registration unit 440 issues a new user ID 411. The registration unit 440 associates the issued user ID 411 with facial feature information 412 extracted from the registration image and registers the associated user ID 411 in the facial information DB 410. The authentication unit 450 performs facial authentication using the facial feature information 412. Specifically, the authentication unit 450 compares the facial feature information extracted from the facial image with the facial feature information 412 in the facial information DB 410. If the comparison is successful, the authentication unit 450 identifies the user ID 411 associated with the compared facial feature information 412. The authentication unit 450 returns a match of the facial feature information to the requester as the facial authentication result. The match of the facial feature information corresponds to the success or failure of authentication. Note that a match of the facial feature information (match present) refers to a match level equal to or greater than a threshold. Furthermore, if facial authentication is successful, the facial authentication result includes the identified user ID.

Returning to FIG. 3, the description will continue.
Health management support device 500 is an example of the above-mentioned health management support device 1. Health management support device 500 is an information processing device that derives factor-related information relating to factors that have affected the health condition of a specific user based on basic health information and authentication history information, and outputs the information to management terminal 300 or the like. Health management support device 500 may be configured redundantly across multiple servers, and each functional block may be implemented by multiple computers.

Figure 5 is a block diagram showing the configuration of a health management support device 500 according to this embodiment 2. The health management support device 500 comprises a storage unit 510, a memory 520, a communication unit 530, and a control unit 540. The storage unit 510 is an example of a storage device such as a hard disk or flash memory. The storage unit 510 stores a program 511, user information 512, authentication terminal information 513, basic health information 514, and authentication history information 515. The program 511 is a computer program (health management support program) that implements health management support processes, etc., including user information registration processing, basic health information registration processing, authentication history information registration processing, and analysis processing according to this embodiment 2.

User information 512 is information for managing users who are subjects or related parties to health management. User information 512 is information that associates a user ID 5121, personal information 5122, and a measurement terminal ID 5123. User ID 5121 is user identification information. User ID 5121 is information that is identical to or uniquely corresponds to user ID 411, which is managed in association with facial feature information 412 in the face information DB 410 of the authentication device 400. Therefore, user information 512 can be said to be information that is associated with the user's registered feature information (biometric information, identity authentication information, identity identification information, etc.) via the user ID 5121. Personal information 5122 includes name, age, gender, address, payment information, medical history, medical examination history, health checkup history, etc. Payment information includes credit card information and bank debit account information, etc. Measurement terminal ID 5123 is identification information for the measurement terminal 110 worn by the user.

The authentication terminal information 513 is information for managing the authentication terminal 120. The authentication terminal information 513 is information that associates an authentication terminal ID 5131 with an installation location 5132. The authentication terminal ID 5131 is identification information for the authentication terminal 120. The authentication terminal ID 5131 is information that is set in advance in each authentication terminal 120 and is included in and transmitted in a facial authentication request. The installation location 5132 is information that indicates the installation location of the authentication terminal 120, for example, information that can identify an area, room, etc. Alternatively, the installation location 5132 may be location information. Therefore, the authentication terminal ID 5131 can be said to be information that can identify the associated installation location 5132, i.e., the authentication location.

The basic health information 514 is information for managing measurement information measured by the measurement terminal 110 worn by the user U. The basic health information 514 is information that associates a user ID 5141, a measurement time 5142, and measurement information 5143. The user ID 5141 is user identification information and is identical to or uniquely corresponds to the user ID 5121 described above. The measurement time 5142 is time information indicating the time when the measurement information 5143 was measured by the measurement terminal 110. The measurement information 5143 is measurement values, etc. measured by the user U who is wearing the measurement terminal 110. The measurement information 5143 is, for example, the user U's skin temperature, pulse rate, number of steps, amount of conversation, sleep time, etc., as described above, but is not limited to these. Furthermore, there may be one or more types of measurement information 5143 per user. Conversely, the measurement information 5143 may include multiple types of measurement values, etc., per user. Furthermore, the types of measurement values may differ for each user.

The authentication history information 515 is information for managing the authentication history when user U is authenticated by the authentication terminal 120. The authentication history information 515 is information that associates a user ID 5151, an authentication time 5152, and an authentication location 5153. The user ID 5151 is identification information of a user who has succeeded in face authentication, as described below, and is information that is identical to or uniquely corresponds to the user ID 5121 described above. The authentication time 5152 is time information such as the shooting time or transmission time included in the face authentication request described above, or the time when authentication was successful through the face authentication process described below. The authentication location 5153 is information that indicates the installation location 5132 of the authentication terminal 120 when authentication was successful. The authentication location 5153 may be location information.

The memory unit 510 is required to store at least the program 511. Therefore, some or all of the user information 512, authentication terminal information 513, basic health information 514, and authentication history information 515 may be stored in an external storage device connected to the health management support device 500.

Memory 520 is a volatile storage device such as RAM (Random Access Memory) and is a storage area for temporarily storing information when control unit 540 is operating. Communication unit 530 is a communication interface with network N.

The control unit 540 is a processor, or control device, that controls each component of the health management support device 500. The control unit 540 loads the program 511 from the storage unit 510 into the memory 520 and executes the program 511. As a result, the control unit 540 realizes the functions of the acquisition unit 541, registration unit 542, derivation unit 543, and output unit 544.

The acquisition unit 541 is an example of the first acquisition unit 11 and second acquisition unit 12 described above. The acquisition unit 541 acquires a registration request for the above-mentioned user information from the above-mentioned user terminal, etc. The acquisition unit 541 also acquires a basic health information registration request from the measurement terminal 110. The acquisition unit 541 also acquires a face authentication request from the authentication terminal 120.

The registration unit 542 performs registration processing in response to a user information registration request. Specifically, the registration unit 542 registers facial feature information for the facial image included in the user information registration request in the authentication device 400 and obtains the user ID issued at the time of registration. The registration unit 542 then associates the user ID with the personal information and measurement terminal ID included in the registration request to generate user information 512 and registers it in the storage unit 510.

The registration unit 542 also performs a process for registering basic health information in response to a basic health information registration request. Specifically, the registration unit 542 identifies the user ID 5121 associated with the measurement terminal ID 5123 included in the basic health information registration request from the user information 512. The registration unit 542 then associates the identified user ID 5141 with the measurement time 5142 and measurement information 5143 included in the basic health information registration request to generate basic health information 514 and registers it in the memory unit 510.

The registration unit 542 also performs a process of registering authentication history information in response to a facial authentication request. Specifically, the registration unit 542 extracts a person's facial area as a facial image from the facial image included in the facial authentication request, and transmits the facial authentication request including the facial image to the authentication device 400. The registration unit 542 then receives the facial authentication result from the authentication device 400. The registration unit 542 also identifies the installation location 5132 associated with the authentication terminal ID 5131 included in the facial authentication request from the authentication terminal information 513. If the facial authentication result indicates successful authentication, the registration unit 542 generates authentication history information 515 by associating the user ID 5151, authentication time 5152, and authentication location 5153 included in the facial authentication result, and registers the information in the storage unit 510.

The derivation unit 543 is an example of the derivation unit 13 described above. The derivation unit 543 performs the analysis process described above. The derivation unit 543 derives factor-related information regarding factors that affected the health condition of a specific user based on the basic health information 514 and the authentication history information 515. Here, the factor-related information is information that is a candidate for the factors that affected the health condition of a specific user. For example, the factor-related information may be the time of day, location, other users, lifestyle rhythm, work situation, etc. that may have affected the health condition of the specific user. Alternatively, the factor-related information may be other users who can contribute to the analysis of the factors that affected the health condition of the specific user. Alternatively, the factor-related information may be countermeasures against the factors, such as improvement proposals.

Specifically, the derivation unit 543 derives factor-related information based on the authentication location 5153 corresponding to a specific authentication time 5152 included in the authentication history information 515, and the basic health information 514 corresponding to the specific authentication time 5152. This can assist in analyzing factors based on the correlation between the location where a specific user stayed at a specific time and the basic health information at that time. In particular, the derivation unit 543 may derive factor-related information from the authentication history information 515 based on the changes in the authentication location 5153 for each authentication time 5152 and the changes in the basic health information 514 for each authentication time 5152. This can assist in analyzing factors based on the correlation between the changes in the location of stay and movement routes (traffic lines) of a specific user over a certain period of time and trends in changes in physical condition.

The derivation unit 543 may also derive time periods or locations that may have affected the health status of a particular user as factor-related information. This makes it easier to identify the factors.

The derivation unit 543 may also calculate time information related to the work of a specific user from the authentication history information 515, and derive factor-related information based on the calculated time information and trends in the basic health information 514. Here, work-related time information refers to arrival time, working hours, overtime hours, or private time outside of working hours, etc. This makes it easier to determine whether a factor is affected by work, such as whether it occurs during working hours or outside of working hours, or the amount of overtime.

The derivation unit 543 may also derive the first user's behavior as factor-related information. Here, behavior refers to collaborative work (meetings, conversations) conducted by multiple people, individual work, smoking, behavior outside of work hours (sleeping, eating), etc. This makes it easier to analyze the factors.

The derivation unit 543 may also identify a time period in which the basic health information 514 satisfies a predetermined condition, and derive factor-related information based on the authentication history information 515 corresponding to the identified time period. This makes it possible to identify, for example, the places where the user stayed during a time period in which the user's health condition was relatively poor, or the people associated with that time period, making it easier to analyze the factors.

It is also desirable for the derivation unit 543 to derive factor-related information by taking into account the authentication history information 515 of multiple second users. This makes it possible to identify candidates who may have affected the health condition of a particular user or who may be aware of the circumstances, making it easier to analyze the factors.

The derivation unit 543 may also derive, from among multiple second users, users who may have influenced the health condition of the first user as factor-related information. This makes it possible to identify candidates for people who may have influenced the health condition of a specific user, making it easier to analyze the factors.

Furthermore, the derivation unit 543 may derive, from among multiple second users, users who can contribute to the analysis of factors as factor-related information. This makes it possible to identify candidates who may know the circumstances surrounding a change in a specific user's health condition, making it easier to analyze the factors by interviewing those people, for example.

Furthermore, the derivation unit 543 may derive countermeasures for the causes as cause-related information. This makes it easier to consider measures to improve the health condition of a specific user.

The output unit 544 outputs the factor-related information derived by the derivation unit 543 to the outside. For example, the output unit 544 transmits the factor-related information to the management terminal 300 via the network N. For example, if the factor-related information is an analysis result, the administrator UA can view the factor-related information (analysis result) displayed on the management terminal 300 to understand factors that may have affected the user's health condition. Furthermore, if the factor-related information is information that can contribute to the analysis of factors, the administrator UA can easily analyze factors that may have affected the health condition of a specific user by taking into account the factor-related information displayed on the management terminal 300. Furthermore, if the factor-related information is a countermeasure for the factor, the administrator UA can easily consider measures to improve the health condition of a specific user by taking into account the factor-related information displayed on the management terminal 300.

Figure 6 is a flowchart showing the flow of the user information registration process according to this embodiment 2. First, the user terminal accepts input of personal information and a measurement terminal ID from the user U, and captures an image of the user U's face using a camera. The user terminal then transmits a request to register user information, including the user U's facial image, personal information, and measurement terminal ID, to the health management support device 500 via the network N. In response, the health management support device 500 receives the user information registration request from the user terminal via the network N (S21).

Next, the health management support device 500 extracts a facial image from the received registration request. The health management support device 500 then transmits a facial information registration request including the extracted facial image to the authentication device 400 via the network N (S22). In response, the authentication device 400 performs facial information registration processing.

Figure 7 is a flowchart showing the flow of face information registration processing by the authentication device 400 according to the second embodiment. First, the authentication device 400 receives a face information registration request (S201). For example, the authentication device 400 receives the face information registration request from the health management support device 500 via the network N. Next, the face detection unit 420 detects a face area from the face image included in the face information registration request (S202). Then, the feature point extraction unit 430 extracts feature points (facial feature information) from the face area detected in step S202 (S203). Then, the registration unit 440 issues a user ID 411 (S204). Then, the registration unit 440 associates the extracted facial feature information 412 with the issued user ID 411 and registers them in the face information DB 410 (S205). Thereafter, the registration unit 440 returns the issued user ID 411 to the requestor (e.g., the health management support device 500) (S206). The authentication device 400 may perform the face information registration process in response to a face information registration request received from an arbitrary information registration terminal. For example, the information registration terminal is an information processing device such as a personal computer, a smartphone, or a tablet terminal.

Returning to FIG. 6, the description will continue.
The health management support device 500 receives the face information registration result (user ID) from the authentication device 400 via the network N (S23). The health management support device 500 then extracts the personal information and the measurement terminal ID from the registration request received in step S21. The health management support device 500 then registers the user information 512, which associates the received user ID 5121, personal information 5122, and measurement terminal ID 5123, in the storage unit 510 (S24).

Figure 8 is a sequence diagram showing the flow of the basic health information registration process according to this embodiment 2. First, the measurement terminal 110 measures physical measurement information from the wearer, user U (S301). Then, the measurement terminal 110 transmits a basic health information registration request, including the measurement terminal ID, measurement time, and measurement information, to the health management support device 500 via the network N (S302). In response, the health management support device 500 receives the basic health information registration request from the measurement terminal 110 via the network N.

Next, the health management support device 500 extracts the measurement terminal ID from the received basic health information registration request. The health management support device 500 then identifies the user ID 5121 associated with the extracted measurement terminal ID 5123 from the user information 512 (S303). The health management support device 500 then associates the identified user ID 5141 with the measurement time 5142 and measurement information 5143 included in the basic health information registration request and registers them in the storage unit 510 as basic health information 514 (S304). The basic health information registration process is executed periodically, at a specified timing, or in response to a request from the health management support device 500. Therefore, multiple pieces of basic health information 514 are stored in the health management support device 500 or an external storage device for each user U1, etc.

Figure 9 is a sequence diagram showing the flow of the authentication history information registration process according to this embodiment 2. Here, we will explain the case of registering authentication history information for user U1 staying in area 210. First, authentication terminal 120-1 photographs the face of user U1 (S311). Then, authentication terminal 120-1 transmits an authentication request including the facial image of user U1 photographed in step S311 and the authentication terminal ID of authentication terminal 120-1 to health management support device 500 via network N (S312). In response, health management support device 500 receives the authentication request from authentication terminal 120-1 via network N, and transmits a facial authentication request including the facial image included in the authentication request to authentication device 400 via network N (S313). In response, authentication device 400 performs facial authentication processing (S314).

Figure 10 is a flowchart showing the flow of facial recognition processing by the authentication device 400 according to the second embodiment. First, the authentication device 400 receives a facial recognition request from the health management support device 500 via the network N (S211). Next, the authentication device 400 extracts facial feature information from the facial image included in the facial recognition request, similar to steps S202 and S203 described above. Then, the authentication unit 450 of the authentication device 400 compares the facial feature information extracted from the facial image included in the facial recognition request with the facial feature information 412 in the facial information DB 410 (S212) and calculates the degree of match. Then, the authentication unit 450 determines whether the degree of match is equal to or greater than a threshold (S213). If the facial feature information matches, that is, if the degree of match of the facial feature information is equal to or greater than the threshold, the authentication unit 450 identifies the user ID 411 associated with the facial feature information 412 (S214). Then, authentication unit 450 returns the face authentication result, including the fact that face authentication was successful and the identified user ID 411, to health management support device 500 via network N (S215). If the degree of match is less than the threshold in step S213, authentication unit 450 returns the face authentication result, including the fact that face authentication was unsuccessful, to health management support device 500 via network N (S216).

Returning to FIG. 9, the description will continue.
Health management support device 500 receives the face authentication result from authentication device 400 via network N. Health management support device 500 then determines whether face authentication was successful. Specifically, health management support device 500 references the face authentication result, and determines that face authentication was successful if the face authentication result includes a user ID. If it is determined that face authentication was unsuccessful, health management support device 500 may return a message to authentication terminal 120-1 via network N indicating that the user failed face authentication.

Here, we will continue the explanation assuming that the facial authentication result includes a message indicating successful facial authentication and the user ID of user U1. The health management support device 500 identifies the installation location 5132 associated with the authentication terminal ID 5131 included in the facial authentication request received from authentication terminal 120-1 from the authentication terminal information 513 (S316). The health management support device 500 then associates the user ID 5151, authentication time 5152, and authentication location 5153 included in the facial authentication result and registers them in the memory unit 510 as authentication history information 515 (S317).

Figure 11 is a flowchart showing the flow of the analysis process according to the second embodiment. First, the management terminal 300 accepts the designation of the user to be analyzed from the administrator UA and transmits the designation of the user to be analyzed to the health management support device 500 via the network N. In response, the health management support device 500 accepts the designation of the user to be analyzed from the management terminal 300 via the network N (S321). The health management support device 500 then analyzes the basic health information 514 and authentication history information 515 corresponding to the designated user and derives factor-related information (S322). The health management support device 500 then outputs the factor-related information to the management terminal 300 via the network N (S323). In response, the management terminal 300 displays the received factor-related information on the screen. This makes it easier for the administrator UA to consider health management indicators in the organization.

Next, a specific example of this embodiment will be described. In the following description, it is assumed that the user subject to health management is user U1, and that when user U1's health condition becomes abnormal, administrator UA uses the health management support device 500 to analyze the cause.

<Specific Example 2-1>
This example describes a case in which candidate locations and time periods that may have affected the health status are derived as factor-related information. In this case, the measurement information 5143 of the basic health information 514 is skin temperature and pulse rate. The derivation unit 543 then identifies the user U1's movement path from the transition of the authentication location 5153 for each authentication time 5152 associated with the user U1's user ID 5151 in the authentication history information 515. For example, the derivation unit 543 may identify the user U1's movement path, such as the time spent at each location, travel routes between areas and other locations, and waypoints on the travel route, based on the authentication locations for each authentication time. Next, the derivation unit 543 determines the characteristics and attributes of the locations from the identified movement path and analyzes the trends of each location and waypoint. For example, the derivation unit 543 may determine a rest area, a smoking area, a conference room, or outside the facility 200 (e.g., the user U1's home) as the attribute of the location of stay. The derivation unit 543 may also analyze the frequency of stays or stops at places of stay and waypoints. Next, the derivation unit 543 identifies the measurement information 5143 for user U1 for each of the identified time periods from the basic health information 514, and identifies time periods or places of stay where the identified measurement information 5143 is equal to or greater than a predetermined value. The derivation unit 543 then derives the identified time periods or places of stay, or places of stay where the frequency of use is high or the length of stay is long, as factor-related information. The output unit 544 then outputs the derived factor-related information and the measurement information for the identified time period to the management terminal 300. As a result, if user U1's health condition is abnormal, the administrator UA can analyze the cause of the abnormality in user U1's health condition using clues such as places and time periods that may have affected user U1's health condition. Figure 12 is a diagram for explaining the concept of specific example 2-1 according to the second embodiment.

<Specific example 2-2>
This example describes a case in which candidate individuals who may have affected the health status are derived as factor-related information. In this case, the measurement information 5143 in the basic health information 514 is the pulse rate. The derivation unit 543 then identifies, from the basic health information 514, a time period during which the pulse rate of user U1 remained above a predetermined value for a certain period of time or longer. The derivation unit 543 then references the authentication history information 515 to identify user U2 who was in the same location (e.g., a conference room) as user U1 during the identified time period. Note that even if user U1 and user U2 are in different authentication locations 5153, the derivation unit 543 may identify users who participated in the same remote conference based on the remote conference history or the like as users who performed collaborative work (such as a conference) with user U1 during the identified time period. In other words, the derivation unit 543 identifies user U2 who at least had contact with user U1 in some kind of work. The derivation unit 543 may then derive the degree of possibility that user U2 influenced user U1's health condition from the date, time, and number of contacts and user U1's pulse rate at that time. The derivation unit 543 then identifies user U2 whose degree is equal to or greater than a predetermined value as factor-related information. The output unit 544 then outputs the derived factor-related information and measurement information for the identified time period to the management terminal 300. This allows the administrator UA to analyze the cause of the abnormality in user U1's health condition by identifying user U2 as a candidate for someone who may have influenced user U1's health condition. For example, this can assist in analyzing the possibility of a stress factor, such as user U2 being user U1's boss. Figure 13 is a diagram for explaining the concept of specific example 2-2 according to the second embodiment.

<Specific example 2-3>
This example describes the case where candidate individuals who can contribute to the analysis of factors affecting the health condition are derived as factor-related information. In this case, the measurement information 5143 of the basic health information 514 is the amount of conversation. The derivation unit 543 then identifies user U3, who had contact with user U1 during some task, as in Specific Example 2-2 described above. Alternatively, the derivation unit 543 may calculate the speech time of user U1 and the speech time of other users from the measurement information 5143 of user U1, and calculate the speech time of user U3 and the speech time of other users from the measurement information 5143 of user U2. In this case, the derivation unit 543 may identify user U3 based on the degree of agreement between the time periods of the speech times. The derivation unit 543 then determines, from the basic health information 514, whether the amount of conversation between users U1 and U3 was equal to or greater than a predetermined time during the time period when they had contact. The derivation unit 543 derives user U3, who had a conversation amount equal to or greater than the predetermined time period, as a person who can contribute to the analysis of factors affecting user U1's health condition . As a result, the administrator UA can select user U2 as a candidate for a person to interview about the circumstances of user U1's deteriorating health. For example, even if user U3 has no business relationship with user U1, he or she can derive a close person who is not apparent from the organizational structure, such as someone with whom he or she often talks at rest areas, as an interview candidate. The administrator UA can also use such relationships outside the organization as a clue to analyze the factors that have affected user U1's health condition. Figure 14 is a diagram for explaining the concept of specific example 2-3 according to the second embodiment.

<Specific example 2-4>
This example describes a case in which lifestyle rhythms and work conditions that may have affected user U1's health status are derived as factor-related information. In this case, the measurement information 5143 in the basic health information 514 includes the number of steps and sleep time. The derivation unit 543 then identifies user U1's work hours and movement paths based on the transition of authentication locations 5153 for each authentication time 5152 associated with user U1's user ID 5151 in the authentication history information 515. Here, work hours may include a breakdown of time spent at the office (working hours) and meeting time. The derivation unit 543 then analyzes the causes of user U1's poor health status based on the identified work hours and movement paths and the number of steps and sleep time in user U1's basic health information 514. For example, the derivation unit 543 may derive factors such as lack of exercise when the number of steps is below a predetermined value, lack of sleep when the average sleep time over a certain period is below a predetermined time, or long working hours or overtime hours when fatigue is long. This makes it easier for the administrator UA to analyze the possible causes of the user U1's poor health based on factors such as daily routine, work situation, etc. Fig. 15 is a diagram for explaining the concept of specific example 2-4 according to the second embodiment.

<Specific example 2-5>
This example describes a case in which lifestyle habits outside of work hours that may have affected the health status are derived as factor-related information. In this case, the measurement information 5143 in the basic health information 514 includes pulse rate and sleep time. The derivation unit 543 then identifies user U1's work hours and movement path, as in specific example 2-4 above. In particular, the derivation unit 543 may determine whether user U1's stay in a specific area is longer than a predetermined time. The derivation unit 543 then analyzes the causes of user U1's poor health status based on the identified work hours and movement path and the pulse rate and sleep time in user U1's basic health information 514. For example, the derivation unit 543 may derive, as factor-related information, issues outside of work hours when sleep time is short and time at the office is also short, a disrupted life cycle after leaving work, when time at the office is short and time spent in a smoking area is long, smoking is excessive, or a pulse rate after leaving work is greater than a predetermined value. Alternatively, the derivation unit 543 may derive, as factor-related information, the degree of possibility that work content is having an influence, or the fact that work hours have a low relevance to factors and private time has a high relevance to factors, etc. This makes it easier for the administrator UA to analyze the possibility of the cause of user U1's poor health based on the degree of influence of work hours, lifestyle habits, etc. Figure 16 is a diagram for explaining the concept of specific example 2-5 according to the second embodiment.

<Specific example 2-6>
In this example, assume that user U1 is an employee who requires special consideration for work, such as pregnancy. A case will be described in which countermeasures for factors that may have affected the user U1's health status are derived as factor-related information. In this case, the measurement information 5143 in the basic health information 514 includes skin temperature, pulse rate, number of steps, and sleep time. The derivation unit 543 then identifies user U1's work hours and movement path, as in Specific Example 2-4 above. The derivation unit 543 then determines whether the workplace (organization) or work significantly impacts user U1's health status based on the identified work hours and movement path and the skin temperature, pulse rate, number of steps, and sleep time in user U1's basic health information 514. For example, if the pulse rate or number of steps during work hours is equal to or greater than a predetermined value, the derivation unit 543 determines that user U1's physical load at work is high. Furthermore, if the sleep time and work hours vary significantly from day to day, the derivation unit 543 determines that user U1's daily rhythm is disrupted. If the workplace or the like has a significant impact on user U1's health condition, the derivation unit 543 determines that the cause is the workplace or the like not providing appropriate consideration to user U1. Therefore, the derivation unit 543 derives countermeasures (improvement proposals) such as transferring user U1's work to desk work or reviewing shifts as cause-related information. This makes it easier for the administrator UA to propose appropriate countermeasures to employees or superiors who require special consideration in their work. Figure 17 is a diagram for explaining the concept of specific example 2-6 according to the second embodiment.

Here, we will explain one aspect of the problem and effect that this embodiment aims to solve. For example, even a wearable device alone can acquire GPS (Global Positioning System) information, but accuracy limits make it difficult to identify the exact location within a building. Furthermore, authentication history information can identify the location and time of a user's presence, making it possible to analyze work hours, overtime, and other factors. However, using basic health information and authentication history information alone makes it difficult to comprehensively analyze a user's exact location (e.g., room), relationships with others (amount of conversation), and relationships outside the organization (friends with whom they talk during breaks) when they are in a certain health state. Therefore, this embodiment derives factor-related information related to factors that may affect the user's health state by combining and comprehensively analyzing the basic health information and authentication history information for a specific user. For example, providing factor-related information to a company's health management department staff (e.g., administrator UA) makes it easier for the staff to formulate the company's health management index. In other words, a health management index specialized for the effects of the work environment can be provided. Furthermore, if an employee develops an abnormal health condition, it becomes easier to identify potential stressors, such as an increase in pulse rate when the employee is with a specific person. Furthermore, even if a person is not a stressor, by identifying someone who is often present during breaks, it is possible to create a list of people who should be interviewed, thereby providing further support for health management.

In particular, by analyzing this information together with the authentication history of other users, it is possible to identify people who were in the vicinity at the same time (bosses, colleagues, junior colleagues, friends, family), and people who collaborated (on tasks, meetings, etc.) in person (or remotely). This makes it easier to determine whether the stress factor is work-related or personal.

<Other embodiments>
The health management support device 500 according to the above-described embodiment may further include a third acquisition unit that acquires diet history information indicating the dietary history of the first user. In this case, the derivation unit may derive factor-related information taking the diet history information into account. This allows the administrator UA to analyze factors in more detail, develop more appropriate health management indices, and more easily propose more appropriate countermeasures.

The processing of the derivation unit described above may also use an AI (Artificial Intelligence) model that receives basic health information and authentication history information and outputs factor-related information for a specific user. In this case, the AI model may be machine-trained using a combination of basic health information, authentication history information, and factor-related information for a specific user as training data. The derivation unit may then use an AI model that has already been machine-trained.

While the above-described embodiments have been described as using facial recognition for personal authentication (identity verification, identity authentication, identity identification processing, etc.), other biometric authentication methods using biometric information may also be used. Other technologies using captured images of a person may be applied to biometric authentication and biometric information. For example, biometric information may be data (features) calculated from physical characteristics unique to an individual, such as fingerprints, voiceprints, veins, retinas, irises, or palm patterns. Furthermore, biometric authentication may involve extracting feature information indicating a person's physical characteristics from a captured image of a portion of the user's body, comparing the extracted feature information with pre-registered feature information, and determining that authentication is successful if the degree of match is greater than or equal to a threshold. For example, biometric authentication may be based on a person's external shape. In this case, the feature information may be information related to the person's external shape, such as information indicating characteristics such as body shape, height, and clothing. Furthermore, other types of personal authentication may be applied instead of biometric authentication, and biometric information may also be other types of personal authentication information. For example, the personal authentication information may include, but is not limited to, a user ID, a combination of ID and password, the contents of an identification card such as a My Number or a driver's license (identification number or password), an electronic certificate, code information, etc. The code information may be a two-dimensional code, for example, a QR code (registered trademark).

In the above-mentioned second embodiment, the authentication device 400 and the health management support device 500 are described as separate information processing devices, but they may be the same. For example, the health management support device 500 may further associate and register facial feature information with the user ID 5121 of the user information 512. In this case, the control unit 540 may further include the functions of the face detection unit 420, feature point extraction unit 430, registration unit 440, and authentication unit 450 in Figure 4.

In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

Note that this disclosure is not limited to the above-described embodiments and can be modified as appropriate without departing from the spirit of the disclosure. Furthermore, this disclosure may be implemented by combining the respective embodiments as appropriate.

Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes.
(Appendix A1)
a first acquisition means for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquiring means for acquiring authentication history information including a personal authentication result and an authentication location of the first user;
a derivation means for deriving factor-related information relating to factors that have affected the health state of the first user based on the basic health information and the authentication history information;
A health management support device comprising:
(Appendix A2)
The derivation means
The health management support device according to Appendix A1, wherein the factor-related information is derived based on an authentication location corresponding to a specific authentication time included in the authentication history information and the basic health information corresponding to the specific authentication time.
(Appendix A3)
The derivation means
The health management support device according to appendix A1 or A2, wherein the factor-related information is derived from the authentication history information based on a transition of authentication locations for each authentication time and a transition of the basic health information for each authentication time.
(Appendix A4)
The derivation means
The health management support device according to Appendix A3, further comprising: deriving, as the factor-related information, a time period or a place that may have affected the health state of the first user.
(Appendix A5)
The derivation means
Calculating time information related to the work of the first user from the authentication history information;
The health management support device according to appendix A1 or A2, wherein the factor-related information is derived based on the time information and a transition of the basic health information.
(Appendix A6)
The derivation means
The health management support device according to Appendix A5, wherein the health management support device derives a behavior of the first user as the factor-related information.
(Appendix A7)
The derivation means
Identifying a time period in which the basic health information satisfies a predetermined condition;
The health management support device according to any one of Appendix A1 to Appendix A6, wherein the factor-related information is derived based on the authentication history information corresponding to the identified time period.
(Appendix A8)
The health management support device according to any one of Appendix A1 to Appendix A7, wherein the derivation means derives the factor-related information by taking into account the authentication history information of a plurality of second users.
(Appendix A9)
The health management support device according to Appendix A8, wherein the deriving means derives, from among the plurality of second users, a user who may have influenced the health state of the first user as the factor-related information.
(Appendix A10)
The health management support device according to Appendix A8 or A9, wherein the deriving means derives, from among the plurality of second users, a user who can contribute to the analysis of the factor as the factor-related information.
(Appendix A11)
The health management support device according to any one of Appendix A1 to Appendix A10, wherein the derivation means derives a countermeasure for the cause as the cause-related information.
(Appendix A12)
The system further includes a third acquisition means for acquiring meal history information indicating a history of meal contents of the first user,
The health management support device according to any one of Appendix A1 to Appendix A11, wherein the derivation means derives the factor-related information by taking into account the diet history information.
(Appendix B1)
an authentication terminal for performing personal authentication of a user;
a health management support device;
The health management support device includes:
a first acquisition means for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquiring means for acquiring authentication history information including a result of personal authentication of the first user by the authentication terminal and an authentication location;
a derivation means for deriving factor-related information relating to factors that have affected the health state of the first user based on the basic health information and the authentication history information;
A health management support system equipped with:
(Appendix B2)
The derivation means
The health management support system according to Appendix B1, wherein the factor-related information is derived based on an authentication location corresponding to a specific authentication time included in the authentication history information and the basic health information corresponding to the specific authentication time.
(Appendix C1)
The computer
Acquire basic health information of the first user measured by a measurement terminal worn by the first user;
acquiring authentication history information including a personal authentication result and an authentication location of the first user;
deriving factor-related information relating to factors that have influenced the health state of the first user based on the basic health information and the authentication history information.
(Appendix D1)
a first acquisition process for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquisition process for acquiring authentication history information including a personal authentication result and an authentication location of the first user;
a derivation process for deriving factor-related information relating to factors that have affected the health state of the first user based on the basic health information and the authentication history information;
A non-transitory computer-readable medium storing a health management support program that causes a computer to execute the above.

The present invention has been described above with reference to embodiments (and examples), but the present invention is not limited to the above embodiments (and examples). Various modifications that would be understood by a person skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

REFERENCE SIGNS LIST 1 health management support device 11 first acquisition unit 12 second acquisition unit 13 derivation unit 1000 health management support system N network U user U1 user U2 user U3 user UA administrator 200 facility 210 area 220 area 300 management terminal 110 measurement terminal 110-1 measurement terminal 110-2 measurement terminal 110-3 measurement terminal 120 authentication terminal 120-1 authentication terminal 120-2 authentication terminal 400 authentication device 410 face information DB
411 User ID
412 Facial feature information 420 Face detection unit 430 Feature point extraction unit 440 Registration unit 450 Authentication unit 500 Health management support device 510 Storage unit 511 Program 512 User information 5121 User ID
5122 Personal information 5123 Measurement terminal ID
513 Authentication terminal information 5131 Authentication terminal ID
5132 Installation location 514 Basic health information 5141 User ID
5142 Measurement time 5143 Measurement information 515 Authentication history information 5151 User ID
5152 Authentication time 5153 Authentication location 520 Memory 530 Communication unit 540 Control unit 541 Acquisition unit 542 Registration unit 543 Derivation unit 544 Output unit

Claims (15)

a first acquisition means for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquiring means for acquiring authentication history information including a personal authentication result and an authentication location of the first user related to biometric authentication by an authentication terminal installed in an area of the facility where the first user is present;
a derivation means for deriving factor-related information relating to factors that have influenced the health state of the first user based on the basic health information and the authentication history information;
Equipped with
The derivation means derives the factor-related information by taking into account the authentication history information of a plurality of second users.
Health management support device. The derivation means
The health management support device according to claim 1 , wherein the factor-related information is derived based on an authentication location corresponding to a specific authentication time included in the authentication history information and the basic health information corresponding to the specific authentication time. The derivation means
The health management support device according to claim 1 or 2, wherein the factor-related information is derived from the authentication history information based on a transition of authentication locations for each authentication time and a transition of the basic health information for each authentication time. The derivation means
The health management support device according to claim 3 , wherein a time period or a place that may have affected the health condition of the first user is derived as the factor-related information. The derivation means
Calculating time information related to the work of the first user from the authentication history information;
The health management support device according to claim 1 , wherein the factor-related information is derived based on the time information and a transition of the basic health information. The derivation means
The health management support device according to claim 5 , wherein the behavior of the first user is derived as the factor-related information. The derivation means
Identifying a time period in which the basic health information satisfies a predetermined condition;
The health management support device according to claim 1 , wherein the factor-related information is derived based on the authentication history information corresponding to the identified time period. The health management support device according to claim 1 , wherein the deriving means derives, from among the plurality of second users, a user who may have influenced the health state of the first user as the factor-related information. The health management support device according to claim 1 , wherein the deriving means derives, from among the plurality of second users, users who can contribute to the analysis of the factors as the factor-related information. The health management support device according to claim 1 , wherein the derivation means derives a countermeasure for the cause as the cause-related information. The system further includes a third acquisition means for acquiring meal history information indicating a history of meal contents of the first user,
The health management support device according to claim 1 , wherein the deriving means derives the factor-related information by taking into account the diet history information. an authentication terminal that is installed in an area of the facility where the user is located and performs personal authentication of the user using biometric authentication;
a health management support device;
The health management support device includes:
a first acquisition means for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquiring means for acquiring authentication history information including a result of personal authentication of the first user by the authentication terminal and an authentication location;
a derivation means for deriving factor-related information relating to factors that have influenced the health state of the first user based on the basic health information and the authentication history information;
Equipped with
The derivation means derives the factor-related information by taking into account the authentication history information of a plurality of second users.
Health management support system. The derivation means
The health management support system according to claim 12 , wherein the factor-related information is derived based on an authentication location corresponding to a specific authentication time included in the authentication history information and the basic health information corresponding to the specific authentication time. The computer
Acquire basic health information of the first user measured by a measurement terminal worn by the first user;
acquiring authentication history information including a personal authentication result and an authentication location of the first user relating to biometric authentication by an authentication terminal installed in an area of the facility where the first user is located;
deriving factor-related information relating to factors that have affected the health state of the first user based on the basic health information and the authentication history information;
In deriving the factor-related information, the factor-related information is derived by taking into account the authentication history information of a plurality of second users.
Health management support method. a first acquisition process for acquiring basic health information of a first user measured by a measurement terminal worn by the first user;
a second acquisition process for acquiring authentication history information including a personal authentication result and an authentication location of the first user related to biometric authentication performed by an authentication terminal installed in an area of the facility where the first user is present;
a derivation process for deriving factor-related information relating to factors that have affected the health state of the first user based on the basic health information and the authentication history information;
on the computer ,
The derivation process derives the factor-related information by taking into account the authentication history information of a plurality of second users.
Health management support program.