Health management device
The health management device uses machine learning to predict menstruation-related symptoms by integrating user-specific health data, overcoming limitations of previous methods that rely on general menstrual and weather data, offering precise symptom predictions.
Patent Information
- Application Number
- JP2020182898
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-10-30
- Publication Date
- 2024-11-07
- Estimated Expiration
- 2040-10-30
AI Technical Summary
Existing systems struggle to accurately predict symptoms associated with menstruation tailored to individual users by relying solely on menstrual cycles and weather data.
A health management device that includes a storage unit for life log data and a symptom prediction unit, utilizing machine learning to predict symptoms based on individual user data, including physical health metrics, menstrual information, basic constitution, and weather data.
Enables accurate prediction of symptoms related to menstruation by analyzing individual user data, providing precise onset dates, cycles, severity, and maximum severity days of peri-menstrual symptoms.
Smart Images

Figure 0007579111000001 
Figure 0007579111000002 
Figure 0007579111000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a health management device that predicts a user's health condition. [Background technology]
[0002] Patent Document 1 provides a comprehensive health management system that obtains information about a woman's menstrual start and physical discomfort from voice input, and also obtains weather data to calculate an individual's menstrual cycle, the probability that menstruation will start on that day, the probability of discomfort due to the menstrual cycle, and the individual's sensitivity to drops in air pressure, and issues advance warning of physical discomfort. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2018-195000 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, it has been difficult to make detailed predictions of each individual's menstrual symptoms simply by using an individual's menstrual cycle and meteorological data.
[0005] Therefore, in order to solve the above-mentioned problems, an object of the present invention is to provide a health management device that can accurately predict each symptom associated with a health condition, such as menstruation, for each individual user. [Means for solving the problem]
[0006] The health management device of the present invention comprises a memory unit that stores life log data, which is information that affects the physical health of multiple users, and a symptom prediction unit that predicts symptoms in the peripheral period of a user's health condition at a specified reference time based on the life log data.
[0007] With this configuration, it is possible to accurately and easily predict symptoms in the peripheral period of a user's health condition at a specified reference time based on the user's life log data. Effect of the Invention
[0008] According to the present invention, by using the life log data of each user, it is possible to accurately predict symptoms in the peripheral period of the user's health condition at a predetermined reference time. [Brief description of the drawings]
[0009] [Figure 1] 1 is a diagram illustrating a system configuration of a health management system according to the present disclosure. [Diagram 2] 2 is a block diagram showing a functional configuration of a measurement value transfer device 30. FIG. [Diagram 3] FIG. 2 is a block diagram showing the functional configuration of a physical condition registration device 40. [Figure 4] 2 is a block diagram showing the functional configuration of a basal constitution registration device 50. FIG. [Diagram 5] FIG. 2 is a block diagram showing the functional configuration of the menstrual information registration device 60. [Figure 6] 2 is a block diagram showing the functional configuration of a weather information acquisition device 70. FIG. [Figure 7] FIG. 2 is a block diagram showing the functional configuration of the data collection and analysis device 100. [Figure 8] 11 is a diagram showing a specific example of a database stored in the data storage function 120. FIG. [Figure 9] 4 is a flowchart showing a prediction model generation process in the data collection and analysis device 100. [Figure 10] 13 is a flowchart showing the process of generating an onset date prediction model by an onset date prediction model generating function 130. [Figure 11] 13 is a flowchart showing a process of predicting the onset date of any one symptom by the onset date prediction function 140. [Figure 12] 13 is a flowchart showing a process for generating an onset cycle prediction model. [Figure 13]FIG. 11 is a diagram for explaining a frequency analysis process. [Figure 14] 13 is a flowchart showing a process of predicting the onset cycle of a symptom by the onset cycle prediction function 145. [Figure 15] 13 is a flowchart showing a generation process of a severity prediction model by a severity prediction model generation function 150. [Figure 16] 13 is a flowchart showing a process of predicting the severity of a symptom by the severity prediction function 160. [Figure 17] 13 is a flowchart showing a maximum severity day prediction model generation process of the maximum severity day prediction model generation function 155. [Figure 18] 13 is a flowchart showing a process of predicting the day (maximum day) when the severity of one symptom will be maximum, performed by the maximum severity day prediction function 165. [Figure 19] 1 is a diagram illustrating an example of a hardware configuration of a data collection and analysis device 100 according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] The embodiments of the present disclosure will be described with reference to the accompanying drawings. Whenever possible, the same parts are designated by the same reference numerals and redundant description will be omitted.
[0011] FIG. 1 is a diagram showing the system configuration of a health management system in the present disclosure. As shown in FIG. 1, the health management system includes a measuring device 20, a measurement value transfer device 30, a physical condition registration device 40, a basic constitution registration device 50, a menstrual information registration device 60, a weather information acquisition device 70, and a data collection and analysis device 100 (health management device). The data collection and analysis device 100 collects and analyzes the life log data of the user from the measuring device 20, the physical condition registration device 40, the basic constitution registration device 50, the menstrual information registration device 60, and the weather information acquisition device 70. As will be described later, the life log data is data showing the physical health condition of each user and / or data affecting the health, and is information showing the daily life of the user. The life log data includes measurement values that are objective information of the user's body, physical condition data related to the user's physical condition, basic constitution data showing the user's basic constitution, the user's menstruation start date, menstrual data related to other symptoms, and other weather information. The weather data is information showing the weather related to the user's place of residence and affecting the user's health depending on the weather.
[0012] The measurement device 20 is a part that directly measures measured values, which are a type of life log data, from the user. In the present disclosure, the measurement device 20 includes at least one of a blood pressure meter, a weight scale, an activity meter, and a thermometer, and measures objective physical data of the user, such as blood pressure, weight, heart rate, calories burned, and body temperature.
[0013] The measurement value transfer device 30 is a device that transfers the measurement values, which are a type of life log data, measured by the measuring device 20 together with the date of measurement to the data collection and analysis device 100 via the network 90.
[0014] The health registration device 40 accepts user operation, receives the registration date (corresponding to the onset date) and health data, and stores them in the data collection and analysis device 100. The health data indicates the amount of sleep and whether or not medication was taken, but may also include other information such as the content or amount of food and satisfaction with sleep. In addition to the amount of sleep, it may also include satisfaction with sleep. The health data is information related to the user's lifestyle habits.
[0015] The basal constitution registration device 50 is a device that accepts user operations, receives basal constitution data, and registers it in the data collection and analysis device 100. The basal constitution data is information indicating age, BMI (Body Mass Index), birth history, medical history, etc. The basal constitution data is data indicating the user's medical history, information that is updated about once a year, and physical information that is generally unlikely to change significantly within a year.
[0016] The menstrual information registration device 60 is a device that accepts user operations, receives menstrual data, and registers it in the data collection and analysis device 100. The menstrual data is information (hereinafter referred to as symptom information) indicating the onset date of menstruation and various symptoms during the peri-menstrual period (a predetermined period before and after menstruation). The various symptoms are symptoms that occur in relation to the menstrual cycle, and indicate symptoms that occur during at least one of the follicular phase, ovulation phase, luteal phase, or menstrual phase. Specifically, the various symptoms indicate at least one of lower back pain, headache, abdominal pain, discomfort, irritability, the presence or absence of bleeding, breast swelling, the presence or absence of vaginal discharge, skin condition, or fatigue.
[0017] The weather information acquisition device 70 is a device that acquires weather data (temperature, weather, air pressure, humidity, etc.) for the area where the user lives from a weather database owned by the Meteorological Agency or the like.
[0018] The data collection and analysis device 100 stores data collected from each device, and generates prediction models for the onset date, onset end date, onset cycle, severity, and maximum severity date of peripheral symptoms by machine learning based on the data (any machine learning method can be used. For example, a classical linear model, a nonlinear model such as XGBoost or LightGBM, or deep learning such as DNN can be used.) Then, using these prediction models, it predicts the onset date, onset end date, onset cycle, severity, and maximum severity date of peripheral symptoms.
[0019] In the above description, life log data is accepted and registered through user operation, but this is not limited to this. The user may operate a user terminal to transmit various life log data from the user terminal to each device and register it.
[0020] These devices will be described below. Figure 2 is a block diagram showing the functional configuration of the measurement value transfer device 30. As shown in the figure, the measurement value transfer device 30 has a data acquisition function 31, a data transfer function 32, a measurement device authentication function 33, and a user authentication function .
[0021] The data acquisition function 31 is a function for acquiring the measurement values and the measurement dates measured by the measuring device 20.
[0022] The data transfer function 32 is a function for transferring the acquired measurement values and the measurement dates to the data collection and analysis device 100 .
[0023] The measuring device authentication function 33 is a function that performs authentication processing of the measuring device 20 when acquiring a measurement value from the measuring device 20. The authentication processing is a known authentication processing, for example, a processing of verifying identification information of the measuring device 20.
[0024] The user authentication function 34 is a function that performs authentication processing of the user when acquiring a measurement value from the measurement device 20. The authentication processing is a known authentication processing, for example, a processing of matching the user's identification information and the password.
[0025] 3 is a block diagram showing the functional configuration of the health registration device 40. The health registration device 40 includes a data registration function 41, a data transfer function 42, and a user authentication function 43.
[0026] The data registration function 41 includes a section for accepting user operations, and is a function for accepting physical condition data and the date of registration thereof in accordance with the operations.
[0027] The data transfer function 42 is a function for transferring physical condition data and the registration date to the data collection and analysis device 100 .
[0028] The user authentication function 43 is a function that performs authentication processing of the user when the data registration function 41 accepts physical condition data. The authentication processing is a known authentication processing, for example, a processing of verifying the user's identification information and password.
[0029] 4 is a block diagram showing the functional configuration of the basal constitution registration device 50. The basal constitution registration device 50 includes a data registration function 51 and a data transfer function 52.
[0030] The data registration function 51 includes a section for accepting user operations, and is a function for accepting basic constitution data and the date of registration thereof in accordance with the operations.
[0031] The data transfer function 52 is a function for transferring basic constitution data and the registration date to the data collection and analysis device 100 .
[0032] 5 is a block diagram showing the functional configuration of the menstrual information registration device 60. The menstrual information registration device 60 includes a data registration function 61 and a data transfer function 62.
[0033] The data registration function 61 includes a section for accepting user operations, and is a function for accepting menstrual data in accordance with the operations.
[0034] The data transfer function 52 is a function that transfers menstrual data to the data collection and analysis device 100 .
[0035] FIG. 6 is a block diagram showing the functional configuration of the weather information acquisition device 70. As shown in FIG.
[0036] The weather information acquisition device 70 includes a data acquisition function 71 and a data transfer function 72 .
[0037] The data acquisition function 71 is a function that periodically or when generating an estimation model in the data collection and analysis device 100, accesses the weather information database to acquire weather information corresponding to the user's location or residence and the registration date (or measurement date) of the above various information. The user's location or residence is information that is registered in advance, but may also be a location using GPS or the like.
[0038] The data transfer function 72 is a function for transferring meteorological information for each user to the data collection and analysis device 100 .
[0039] 7 is a block diagram showing the functional configuration of the data collection and analysis device 100. As shown in the figure, the data collection and analysis device 100 includes a data acquisition function 110, a data storage function 120, an onset date prediction model generation function 130, an onset cycle prediction model generation function 135, an onset date prediction function 140, an onset cycle prediction function 145, a severity prediction model generation function 150, a maximum severity day prediction model generation function 155, a severity prediction function 160, a maximum severity day prediction function 165, and a result notification function 170. The data collection and analysis device 100 has a plurality of prediction functions and a plurality of prediction model functions, but is not limited thereto. One or several prediction models that output the onset date, onset end date, onset cycle, severity, and maximum severity date for the life log data may be learned and used. In addition, in the description below, each prediction model generation function generates a respective prediction model (onset date prediction model, onset cycle prediction model, severity prediction model, maximum severity date prediction model) for all symptoms, but one or several prediction models that output a prediction value for each symptom may be generated.
[0040] The data acquisition function 110 is a function for acquiring various information from the measurement value transfer device 30, the physical condition registration device 40, the basic constitution registration device 50, the menstrual information registration device 60, and the weather information acquisition device .
[0041] The data storage function 120 is a function that stores various information acquired by the data acquisition function 110, and is a so-called storage unit. Fig. 8 is a diagram showing a specific example of a database stored by the data storage function 120. As shown in the diagram, measurement data, menstrual data, physical condition data, basic constitution data, and weather data are stored in association with each user ID. Each of these data is associated with a registration date (or measurement date).
[0042] The measurement data is information in which body temperature, weight, amount of activity (heart rate), etc. are associated with the registration date.
[0043] The physical condition data is information in which the sleep time and whether or not a medication was taken are associated with the registration date.
[0044] The menstrual data is the start date of menstruation, the end date of menstruation, or various perimenstrual symptoms and the registration date thereof. The various perimenstrual symptoms are at least one of the following: presence or absence or degree of abdominal pain, presence or absence or degree of headache, presence or absence or degree of lower back pain, presence or absence or degree of discomfort, presence or absence or degree of irritability, presence or absence or degree of bleeding, breast bloating or degree, presence or absence or amount of vaginal discharge, skin condition, and presence or absence or degree of fatigue.
[0045] The basic constitution data is information in which age, BMI, whether or not a person has given birth, etc. are associated with the registration date.
[0046] The weather data is information in which temperature, weather, humidity, and atmospheric pressure are associated with the registration date.
[0047] Although the data storage function 120 stores the above-mentioned various information only for user A in FIG. 8, the data storage function 120 actually stores the above-mentioned various information for all users other than user A.
[0048] The data extraction function 125 is a function that extracts various data stored in the data storage function 120 in order to generate each prediction model. For example, the data extraction function 125 extracts life log data of a user who has registered data for a predetermined period of time that is useful for generating a prediction model.
[0049] The onset date prediction model generation function 130 is a function that generates a prediction model (onset date prediction model) for predicting the onset date and onset end date during the perimenstrual period. This onset date prediction model generation function 130 generates an onset date prediction model for predicting the onset date and onset end date of perimenstrual symptoms using the measurement data, menstrual data, physical condition data, basic constitution data, and weather data extracted by the data extraction function 125 as feature quantities (explanatory variables) and the difference between the menstruation start date and onset date as the objective variable. Details will be described later. The onset date prediction model may output either the onset date or the onset end date.
[0050] The onset cycle prediction model generation function 135 is a function that generates a prediction model (onset cycle prediction model) for predicting onset cycles. This onset cycle prediction model generation function 135 generates an onset cycle prediction model for predicting the onset cycle of perimenstrual symptoms using the measurement data, menstrual data, physical condition data, basic constitution data, and weather data extracted by the data extraction function 125 as feature quantities (explanatory variables) and the cycle of onset days as a response variable. Details will be described later.
[0051] The onset date prediction function 140 stores the onset date prediction model generated by the onset date prediction model generation function 130, and uses this to predict the onset date and onset end date of each perimenstrual symptom. The onset date prediction function 140 predicts the onset date and onset end date of each perimenstrual symptom by inputting life log data such as the user's measurement value data, menstrual data, basic constitution data, and weather data at the time of prediction.
[0052] The onset cycle prediction function 145 is a function that stores the onset cycle prediction model generated by the onset cycle prediction model generation function 135 and predicts the onset cycle of each perimenstrual symptom using the model. The onset cycle prediction function 145 predicts the cycle of each perimenstrual symptom by inputting life log data such as the user's measurement value data, menstrual data, basic constitution data, and weather data at the time of prediction.
[0053] The severity prediction model generation function 150 is a function that generates a severity prediction model for predicting the severity of each symptom during the perimenstrual period. This severity prediction model generation function 150 generates a severity prediction model for predicting the maximum severity of perimenstrual symptoms using the measurement data, menstrual data, physical condition data, basic constitution data, and weather data extracted by the data extraction function 125 as feature quantities (explanatory variables) and the severity at which the symptom is at its maximum as the objective variable. Details will be described later.
[0054] The maximum severity day prediction model generation function 155 is a function that generates a maximum severity day prediction model for predicting the day when the severity of each symptom during the perimenstrual period will be at its maximum (maximum severity day). This maximum severity day prediction model generation function 155 uses the measurement data, menstrual data, physical condition data, basic constitution data, and weather data extracted by the data extraction function 125 as feature quantities (explanatory variables) and the day when the severity of the symptom will be at its maximum as the objective variable to generate a maximum severity day prediction model for predicting the day when the severity of the perimenstrual symptoms will be at their maximum. Details will be described later.
[0055] The severity prediction function 160 stores the severity prediction model generated by the severity prediction model generation function 150, and uses this to predict the severity of each symptom that occurs during the perimenstrual period.
[0056] The maximum severity day prediction function 165 stores the maximum severity day prediction model generated by the maximum severity day prediction model generation function 155, and uses this to predict the day on which the severity of each symptom occurring during the perimenstrual period will be at its maximum.
[0057] The result notification function 170 is a function that notifies the user of the onset date, end date of onset, onset cycle, severity, and the day when the severity is at its maximum (day of maximum severity) of each symptom that occurs around the menstrual period, as predicted using the onset date prediction model, cycle prediction model, severity prediction model, and maximum severity day prediction model.
[0058] The prediction model generation process is performed periodically or arbitrarily. The prediction process and notification process are performed periodically or when specified by the user.
[0059] Next, the operation of the data collection and analysis device 100 of the present disclosure will be described. Fig. 9 is a flowchart showing a prediction model generation process in the data collection and analysis device 100. The data acquisition function 110 acquires various data (life log data) from all or some of the devices, and the data storage function 120 stores the data (S100). The data storage function 120 detects and removes abnormal values and interpolates missing values from the stored life log data (S101).
[0060] The data extraction function 125 extracts users who have stored life log data a certain number of times or more in the past three months or more (S102). Note that this is not limited to three months, and may be a certain number of times or more in a predetermined period.
[0061] The onset date prediction model generation function 130 generates an onset date prediction model by utilizing the life log data stored in the data storage function 120 (S103). This onset date prediction model is generated for each symptom such as headache, abdominal pain, etc. that occurs during the perimenstrual period. The onset date prediction function 140 predicts the onset date and end date of the next and subsequent perimenstrual symptoms using the onset date prediction model (S104).
[0062] Furthermore, the onset cycle prediction model generation function 135 generates an onset cycle prediction model using the life log data (S105). This onset cycle prediction model is generated for each symptom such as headache, abdominal pain, etc. that occurs during the perimenstrual period. The onset cycle prediction function 145 predicts the onset cycle of perimenstrual symptoms from the next period onwards using the onset cycle prediction model (S106).
[0063] In addition, the severity prediction model generation function 150 generates a severity prediction model using the life log data stored in the data storage function 120 (S107). This severity prediction model is generated for each symptom. The severity prediction function 160 predicts the severity from the next time onwards using the severity prediction model (S108).
[0064] Furthermore, the maximum severity day prediction model generation function 155 generates a maximum severity day model using the life log data (S109). This maximum severity day prediction model is generated for each symptom. The maximum severity day prediction function 165 predicts the day on which the severity will be maximum from the next time onward using the maximum severity day prediction model (S110).
[0065] The result notification function 170 notifies the user of the onset date, onset end date, onset cycle, severity, and the day when the severity will be maximum for each symptom predicted by the onset date prediction function 140, the onset cycle prediction function 145, the severity prediction function 160, and the maximum severity day prediction function 165 (S111).
[0066] The prediction processes S104, S106, S108, and S110 are not limited to being executed after each prediction model is generated, and only the prediction processes may be executed at any timing.
[0067] Next, a detailed process of step S103 will be described. Fig. 10 is a flowchart showing a process of generating an onset date prediction model by the onset date prediction model generating function 130.
[0068] The onset date prediction model generation function 130 extracts the menstruation start date of each user based on the extracted menstruation data of each user. Then, it calculates the menstrual cycle of each user (S103-1). If there are three or more menstruation start dates, the average value is set as the menstrual cycle of the user.
[0069] The onset date prediction model generation function 130 performs a processing loop for each perimenstrual symptom (S103-2, S103-3). That is, the onset date prediction model generation function 130 extracts life log data of users who have developed the symptom for each symptom from the menstrual data stored in the data storage function 120 (S103-3). The symptoms are headache, abdominal pain, etc., and some users may develop both headache and abdominal pain, or may develop headache but not abdominal pain. In the present disclosure, life log data of users who have developed the symptom for each symptom, such as users who have developed headache and users who have developed abdominal pain, is collected. Therefore, the same life log data may be handled in duplicate. Note that the physical condition data in FIG. 8 is represented by the degree of the symptom. In the physical condition data, 0 is added when there is no symptom. Note that when the degree of a symptom is extremely low, the symptom may be treated as not being present.
[0070] The onset date prediction model generation function 130 calculates the difference in number of days D1 between the menstruation start date and the onset first day closest to the menstruation start date for each user (S103-4). The symptoms continue to occur, and the onset first day refers to the first day of the onset. The process here finds the day that the first day is closest to the menstruation start date.
[0071] The onset date prediction model generation function 130 uses physical condition data, basic constitution data, weather data, menstruation start date, and menstrual cycle as feature quantities (explanatory variables) and the difference in number of days D1 as a response variable, and generates an onset date prediction model for predicting the menstruation start date and the closest first day of onset of the symptom from the menstruation start date using any machine learning method. This onset date prediction model is a prediction model for predicting the onset date of the symptom determined in S103-2.
[0072] The onset date prediction model generation function 130 performs these processes for all symptoms (headache, stomachache, etc.) and generates onset date prediction models for all symptoms (S103-6). For convenience of explanation, the generation process of the onset date prediction model has been described with a focus on the onset date, but this onset date prediction model is similarly learned for the onset end date. That is, the onset date prediction model generation function 130 calculates the difference in number of days between the onset end date, which is paired with the onset first day, and the menstruation start date, and learns the onset date prediction model for the onset end date based on the difference in number of days.
[0073] Next, a prediction process using the onset date prediction model will be described. FIG. 11 is a flowchart showing a prediction process of the onset date of any one symptom by the onset date prediction function 140. The onset date prediction function 140 applies the life log data of one user to the onset date prediction model corresponding to one symptom to calculate a predicted value (S104-1). The onset date prediction function 140 converts the predicted value into an onset date (S104-2). This predicted value is the difference in number of days between the menstruation start date and the onset first day of the symptom closest to the menstruation start date. The onset date prediction function 140 predicts the next menstruation start date from the registered menstruation start date and the menstrual cycle calculated from the menstruation start date, and can use it to obtain the onset date of the symptom. The result notification function 170 notifies the one user of the predicted onset date of the symptom (S104-3). This is a notification process of the onset date for one symptom. These processes are repeated for all symptoms. The user may specify any symptom and have the onset date of only that symptom predicted.
[0074] Next, the process S105 will be described. Fig. 12 is a flowchart showing the process of generating an onset cycle prediction model. The onset cycle prediction model generation function 135 extracts the menstruation start date of each user based on the extracted menstrual data of each user. Then, the menstrual cycle of each user is calculated (S105-1). If there are three or more menstruation start dates, the average value is set as the menstrual cycle of the user.
[0075] The onset cycle prediction model generation function 135 runs a processing loop for each perimenstrual symptom (S105-2, S105-3). That is, the onset cycle prediction model generation function 135 extracts, for each symptom, life log data of users who have developed the symptom from the menstrual data stored in the data storage function 120 (S105-3). The symptoms are headache, abdominal pain, etc., and some users may develop both headache and abdominal pain, or may develop headache but not abdominal pain. Therefore, the life log data may be used in duplicate.
[0076] The onset cycle prediction model generation function 135 calculates the onset cycle Y of perimenstrual symptoms using frequency analysis or any regression analysis using the onset date of the target symptom (S105-4).
[0077] Here, the calculation process of the onset period Y will be described. Fig. 13 is a diagram for explaining the frequency analysis process. Frequency analysis is a method for deriving the periodicity of time series data and analyzing its characteristics. In the present disclosure, the horizontal axis (time axis) of the time series data is the number of days going back from the start date of menstruation, and the vertical axis (amplitude) is the registration rate for the entire symptom.
[0078] In FIG. 13, the dotted line is a graph of the registration rate of symptom a registered on days going back from the start date of menstruation. The registration rate is the ratio of the number of users who registered that they have developed symptom a to the total number of users, and is calculated for each day going back from the start date of menstruation. These values are connected to form graph G1, which is represented by a dotted line. Note that instead of the registration rate on the vertical axis, the severity of the symptom may be used. For example, users may be asked to enter numerical information on the severity of their headache or stomachache, and the average may be calculated.
[0079] The onset cycle prediction model generation function 135 performs frequency analysis on this dotted line graph G1, thereby making it possible to extract the fluctuation pattern (periodicity) shown by the solid line graph G2.
[0080] The onset cycle prediction model generation function 135 detects peaks in the amplitude of this solid line graph G2, and can calculate the number of days between the peaks, that is, the cycle Y of the symptom a. This symptom a is each symptom of the perimenstrual period, such as headache, abdominal pain, etc.
[0081] The onset cycle prediction model generation function 135 uses physical condition data, basic constitution data, weather data, menstruation start date, and menstrual cycle as feature quantities, and onset cycle Y as a response variable, and generates an onset cycle prediction model for predicting the onset cycle using any machine learning method. This onset cycle prediction model is a prediction model that predicts the onset cycle of the symptom determined in S105-2.
[0082] The onset cycle prediction model generation function 135 performs these processes for all symptoms (headache, stomachache, etc.) and generates onset cycle prediction models for all symptoms (S105-6).
[0083] Next, the prediction process using the onset cycle prediction model will be described. FIG. 14 is a flowchart showing the prediction process of the onset cycle of one symptom by the onset cycle prediction function 145. The onset cycle prediction function 145 applies the life log data of one user to the onset cycle prediction model corresponding to one symptom to predict the onset cycle of the one symptom (S106-1). The result notification function 170 notifies the one user of the onset cycle of the one symptom (S106-2). This is a notification process of the onset date for one symptom. These processes are repeated for all symptoms. Note that one user may specify an arbitrary symptom to predict the onset cycle, etc., of only that symptom.
[0084] Next, a detailed process of step S107 will be described. Fig. 15 is a flowchart showing a process of generating a severity prediction model by the severity prediction model generating function 150.
[0085] The severity prediction model generation function 150 extracts the menstruation start date of each user based on the extracted menstrual data of each user. Then, it calculates the menstrual cycle of each user (S107-1). If there are three or more menstruation start dates, the average value is set as the menstrual cycle of the user.
[0086] The severity prediction model generation function 150 performs a processing loop for each perimenstrual symptom (S107-2). That is, the onset date prediction model generation function 130 determines one perimenstrual symptom.
[0087] Then, the severity prediction model generation function 150 extracts the menstruation start date and the severity L of the symptom closest to the menstruation start date from the life log data of the user who has the perimenstrual symptom (S107-3). That is, the severity prediction model generation function 150 extracts the severity L of the day closest to the menstruation start date from among several onset dates at which the severity peaks. This is performed for the life log data of each user. For women who do not have the perimenstrual symptom, the severity is calculated as 0.
[0088] Then, the severity prediction model generation function 150 uses the physical condition data, basic constitution data, weather data, menstruation start date, and menstrual cycle as feature quantities (explanatory variables) and the severity L as a response variable, and generates a severity prediction model for predicting the menstruation start date and the severity L of the day closest to the menstruation start date among several days at which the severity peaks, using any machine learning method. This severity prediction model is a prediction model for predicting the severity of one symptom determined in S107-2.
[0089] The severity prediction model generation function 150 performs these processes for all symptoms (headache, stomachache, etc.) and generates severity prediction models for all symptoms (S107-5).
[0090] Next, the prediction process using the severity prediction model will be described. FIG. 16 is a flowchart showing the process of predicting the severity of one symptom by the severity prediction function 160. The severity prediction function 160 applies the life log data to the severity prediction model corresponding to one symptom to calculate the maximum severity (S108-1). The result notification function 170 notifies the user of the severity of the one symptom (S108-2). This is the notification process of the severity for one symptom. These processes are repeated for all symptoms. Note that the user may specify any symptom to have the severity of only that symptom predicted.
[0091] Next, a process for generating a maximum severity day prediction model for predicting the onset date at which the severity is at its maximum will be described. FIG. 17 is a flowchart showing the maximum severity day prediction model generation process of the maximum severity day prediction model generation function 155.
[0092] The severity maximum day prediction model generation function 155 extracts the menstruation start date of each user based on the extracted menstrual data of each user. Then, it calculates the menstrual cycle of each user (S109-1). If there are three or more menstruation start dates, the average of the dates is used as the menstrual cycle of the user.
[0093] The maximum severity day prediction model generation function 155 runs a processing loop for each perimenstrual symptom (S109-2, S109-3). That is, the maximum severity day prediction model generation function 155 extracts life log data of users who have developed each symptom from the menstrual data stored in the data storage function 120 (S109-3). The symptoms are headache, abdominal pain, etc., and some users may develop both headache and abdominal pain, or may develop headache but not abdominal pain.
[0094] The maximum severity day prediction model generation function 155 calculates, for each user, the difference in number of days D2 between the menstruation start date and the onset date with the maximum severity closest to the menstruation start date (S109-4).
[0095] The maximum severity day prediction model generation function 155 uses physical condition data, basic constitution data, weather data, menstruation start date, and menstrual cycle as feature quantities, and the difference in number of days D2 as a target variable, and generates an onset date prediction model for predicting the difference in number of days between the start of menstruation and the onset date when the severity of the symptom is at its maximum closest to the menstruation start date, using any machine learning method. This maximum severity day prediction model is a prediction model that predicts the day when the severity of the symptom determined in S109-2 is at its maximum.
[0096] The maximum severity day prediction model generation function 155 performs these processes for all symptoms (headache, stomachache, etc.) and generates maximum severity day prediction models for all symptoms (S109-6).
[0097] Next, a prediction process using the maximum severity day prediction model will be described. FIG. 18 is a flowchart showing a prediction process of the day (maximum severity day) when the severity of one symptom is maximum by the maximum severity day prediction function 165. The maximum severity day prediction function 165 applies the life log data of one user to the maximum severity day prediction model corresponding to one symptom to calculate a predicted value (S110-1). The maximum severity day prediction function 165 converts the predicted value into an onset date (S110-2). This predicted value is the difference between the menstruation start date and the day when the severity is maximum, which is closest to the menstruation start date. The maximum severity day prediction function 165 predicts the menstruation start date from the registered menstruation start date and the menstrual cycle calculated from the menstruation start date, and can use it to find the day when the severity of the symptom is maximum. The result notification function 170 notifies the user of the day when the severity of the symptom is maximum (S110-3). This is a notification process of the day when the severity of one symptom is maximum. These processes are repeated for all symptoms. Note that the user may specify an arbitrary symptom and have the system predict the day when the severity of only that symptom will be at its maximum.
[0098] Next, a description will be given of the effects of the data collection and analysis device 100 of the present disclosure. The data collection and analysis device 100 of the present disclosure includes a data storage function 120 that functions as a storage unit that stores life log data, which is information on the physical health condition and health effects of a user, and a prediction function that functions as a symptom prediction unit that predicts symptoms of a peripheral period of a certain reference time of a user's health condition based on the life log data.
[0099] The prediction function is at least one of the onset date prediction function 140 , the onset cycle prediction function 145 , the severity prediction function 160 , and the maximum severity date prediction function 165 .
[0100] With this configuration, it is possible to accurately and easily predict symptoms in a peripheral period of a user's health condition at a predetermined reference time based on the user's life log data. The life log data is information on the user's health condition and information that affects the health, for example, information on the body of an individual user or information that affects the body, so that it is possible to accurately predict symptoms in the peripheral period according to the user's characteristics. This life log data includes at least one of the user's blood pressure, weight, activity level, body temperature, sleep time, medication data (whether or not the user is taking medication), menstruation start date, and place of residence. By using this information on the body or information that affects the body, it is possible to predict symptoms in the peripheral period of a specific reference time of an individual user's health condition.
[0101] In addition, in the present disclosure, the periphery symptoms at a predetermined reference time of health status are periphery symptoms at the start of menstruation. Although the cycle of the menstrual start date, etc. does not vary much among individuals and is easy to understand, the symptoms in the periphery vary among individuals, and there is a demand to know them in advance.
[0102] In the present disclosure, symptoms that occur around the start of menstruation are considered to be abdominal pain, headache, back pain, discomfort, irritability, bleeding, breast bloating, vaginal discharge, rough skin, or fatigue. These symptoms vary from person to person, and their periodicity may not be clearly defined.
[0103] In the present disclosure, predictions can be made about these symptoms from the user's life log data.
[0104] The onset date prediction function 140 or onset cycle prediction function 145 predicts the onset date, onset end date, or onset cycle of a symptom from the user's life log data. The severity prediction function 160 or maximum severity day prediction function 165 predicts the severity of a symptom or the day when the severity is maximum from the user's life log data.
[0105] With this configuration, it is possible to predict the onset date, end date of onset, onset cycle, degree of severity, and date of maximum severity of abdominal pain, headache, etc. associated with menstruation from the life log data.
[0106] In the data collection and analysis device 100 of the present disclosure, each prediction function (onset date prediction function 140, onset cycle prediction function 145, severity prediction function 160, and maximum severity date prediction function 165) stores a prediction model learned using the user's life log data as explanatory variables and information on peripheral symptoms at a predetermined reference time of the user's health condition as objective variables. The peripheral symptoms here are respectively the onset date, onset end date, onset cycle, severity level, and maximum severity date as objective variables.
[0107] These prediction functions can input a user's life log data into a predictive model to predict information about the user's peri-menstrual symptoms at a given baseline time point, such as symptoms at the start of menstruation.
[0108] In the present disclosure, the onset date prediction model or the maximum severity date prediction model is trained using difference information between a reference time and a date and time related to symptoms as a response variable, i.e., the difference in number of days between the menstruation start date, which is the reference time, and the onset date, onset end date, or maximum severity date, which are dates and times related to symptoms, is trained using the response variable.
[0109] The onset date, end date, and date of maximum severity are correlated with the start date of menstruation, and by utilizing this, it is possible to predict the onset date and end date of each symptom.
[0110] Each prediction function (onset date prediction function 140, onset cycle prediction function 145, severity prediction function 160, and maximum severity date prediction function 165) stores multiple prediction models learned for each symptom. The prediction function selects a prediction model corresponding to the symptom from the multiple prediction models and makes a prediction. Providing a prediction model for each symptom enables accurate prediction.
[0111] The data collection and analysis device 100 of the present disclosure further includes a prediction model generation function that learns and generates a prediction model using the user's life log data as explanatory variables and information on symptoms in the peripheral phase at a predetermined reference time of the user's health condition (onset date, onset end date, onset cycle, severity, and maximum severity date) as objective variables. This prediction model generation function is at least one of an onset date prediction model generation function 130, an onset cycle prediction model generation function 135, a severity prediction model generation function 150, and a maximum severity date prediction model generation function 155.
[0112] The block diagrams used in the description of the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.
[0113] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, mapping, assignment, etc. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. In either case, as described above, there is no particular limitation on the method of realization.
[0114] For example, the data collection and analysis device 100 according to an embodiment of the present disclosure may function as a computer that performs processing of the health management method of the present disclosure. Fig. 19 is a diagram showing an example of a hardware configuration of the data collection and analysis device 100 according to an embodiment of the present disclosure. The above-mentioned data collection and analysis device 100 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.
[0115] In the following description, the term "apparatus" may be replaced with a circuit, a device, a unit, etc. The hardware configuration of the data collection and analysis apparatus 100 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.
[0116] Each function in the data collection and analysis device 100 is realized by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communications via a communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and the storage 1003.
[0117] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned data extraction function 125, onset date prediction model generation function 130, onset date prediction function 140, etc. may be realized by the processor 1001.
[0118] Moreover, the processor 1001 reads out a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to the read out programs. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the data extraction function 125, the onset date prediction model generation function 130, and the onset date prediction function 140 may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may be similarly realized. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via an electric communication line.
[0119] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc. The memory 1002 may be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), software modules, etc. that can be executed to implement a health management method according to an embodiment of the present disclosure.
[0120] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.
[0121] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned data acquisition function 110 may be realized by the communication device 1004.
[0122] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0123] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0124] The data collection and analysis device 100 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0125] The notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. In addition, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0126] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.
[0127] The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0128] Information, etc. may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Information may be input / output via multiple network nodes.
[0129] The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.
[0130] The determination may be based on a value represented by a single bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).
[0131] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).
[0132] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.
[0133] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0134] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.
[0135] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0136] In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0137] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0138] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.
[0139] The names used for the above-mentioned parameters are not limiting in any way. Moreover, the formulas using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.
[0140] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.
[0141] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0142] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0143] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.
[0144] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.
[0145] In this disclosure, where articles have been added due to translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0146] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different." [Explanation of symbols]
[0147] 20...measuring device, 30...measurement value transfer device, 40...physical condition registration device, 50...basic constitution registration device, 60...menstrual information registration device, 70...weather information acquisition device, 100...data collection and analysis device, 90...network, 31...data acquisition function, 32...data transfer function, 33...measuring device authentication function, 34...user authentication function, 41...data registration function, 42...data transfer function, 43...user authentication function, 51...data registration function, 52...data transfer function, 61...data registration recording function, 62...data transfer function, 71...data acquisition function, 72...data transfer function, 110...data acquisition function, 120...data storage function, 130...onset date prediction model generation function, 135...onset cycle prediction model generation function, 140...onset date prediction function, 145...onset cycle prediction function, 150...severity prediction model generation function, 155...maximum severity day prediction model generation function, 160...severity prediction function, 165...maximum severity day prediction function, 170...result notification function.
Claims
1. A storage unit that stores life log data indicating information indicating a menstrual state of a user's body or information affecting menstruation; a prediction model storage unit that stores a prediction model learned using the user's physical condition data, the user's basic constitution data, weather data, a predetermined reference time of the user's menstrual state, and the user's menstrual cycle as explanatory variables from among the user's life log data, and using the difference in number of days between the predetermined reference time of the menstrual state and the onset date of peripheral symptoms indicating a predetermined period before and after the predetermined reference time of the user's menstrual state as an objective variable; A symptom prediction unit that predicts an onset date of a peripheral symptom indicating a predetermined period before and after a predetermined reference time of a menstrual state of a user based on the prediction model; Equipped with The symptom prediction unit inputs the life log data of the one user into the prediction model and predicts an onset date of a peripheral symptom indicating a predetermined period before and after a predetermined reference time of the menstrual state of the one user. Health management device.
2. A storage unit that stores life log data indicating information indicating a menstrual state of a user's body or information affecting menstruation; a prediction model storage unit that stores a prediction model learned using the user's physical condition data, the user's basic constitution data, weather data, a predetermined reference time of the user's menstrual state, and the user's menstrual cycle as explanatory variables, and using the difference in number of days between the end date of the peripheral symptoms at the predetermined reference time of the user's menstrual state and the predetermined reference time of the menstrual state as a response variable, from among the user's life log data; A symptom prediction unit that predicts an end date of a peripheral symptom indicating a predetermined period before and after a predetermined reference time of a menstrual state of a user based on the prediction model; Equipped with The symptom prediction unit inputs the life log data of the one user into the prediction model and predicts an end date of a peripheral symptom indicating a predetermined period before and after a predetermined reference time of the menstrual state of the one user. Health management device.
3. A storage unit that stores life log data indicating information indicating a menstrual state of a user's body or information affecting menstruation; a prediction model storage unit that stores a prediction model learned using the user's physical condition data, the user's basic constitution data, weather data, a predetermined reference time of the user's menstrual state, and the user's menstrual cycle as explanatory variables and the onset cycle of symptoms in the peripheral period of the user's menstrual state at the predetermined reference time as a response variable, among the user's life log data; A symptom prediction unit that predicts an onset cycle of a peripheral symptom indicating a predetermined period before and after a predetermined reference time of a menstrual state of a user based on the prediction model; Equipped with The symptom prediction unit inputs the life log data of the one user into the prediction model and predicts an onset cycle of a peripheral symptom indicating a predetermined period before and after a predetermined reference time of the menstrual state of the one user. Health management device.
4. A storage unit that stores life log data indicating information indicating a menstrual state of a user's body or information affecting menstruation; a prediction model storage unit that stores a prediction model learned using explanatory variables including physical condition data of the user, basic constitution data of the user, weather data, a predetermined reference time of the menstrual state of the user, and the menstrual cycle of the user from among the life log data of the user, and a target variable including a difference in number of days between a predetermined reference time of the menstrual state of the user and the day closest to the reference time when the severity of symptoms is at its maximum; A symptom prediction unit that predicts a day when the severity of a peripheral symptom, which indicates a predetermined period before and after a predetermined reference time of a menstrual state of a user, will be maximum based on the prediction model; Equipped with The symptom prediction unit inputs the life log data of the one user into the prediction model and predicts a day when the severity of a peripheral symptom indicating a predetermined period before and after a predetermined reference time of the menstrual state of the one user will be maximum. Health management device.
Citation Information
Patent Citations
Life condition recorder apparatus and body information processing system
JP2006280762A
Body composition measuring instrument and method
JP2009005904A
Physical condition predicting system and program
JP2016081190A
Health management device, health management system, and health management method
JP2016131770A
Health prediction system and health prediction method
JP2016153978A
