A health management system

Abstract

The present application relates to the technical field of health management, and particularly relates to a health management system, comprising a user terminal, a wearable monitoring terminal, a drinking water monitoring terminal, a meal information collection terminal, a nutrition auditing terminal, a meal supply terminal and a cloud management platform. The wearable monitoring terminal is used for collecting physiological monitoring data such as heart rate, blood pressure, blood glucose and exercise electrocardiogram of the user at regular time intervals; the drinking water monitoring terminal is used for collecting the drinking water amount and drinking water time of the user, and reminding when the drinking water does not reach the stage target; and the meal information collection terminal is used for collecting a meal identification code on the meal package to obtain the meal material type, calorie, serving size, meal times and allergen information of the meal. The present application can realize closed-loop management of physiological monitoring, drinking water management, meal identification, nutrition auditing, meal supply and cloud report, and improve the automation degree and data continuity of health management.

Description

Technical Field

[0001] This invention relates to the field of health management, and more specifically to a health management system. Background Technology

[0002] With the development of mobile internet, wearable devices, smart home terminals, and cloud data processing technologies, personal health management is gradually shifting from a single manual recording method to multi-terminal collaboration, data analysis, and long-term tracking management. Existing health management methods typically include functions such as exercise recording, calorie recording, water intake reminders, heart rate monitoring, and weight recording. However, these functions are mostly scattered across different devices or applications, lacking effective data linkage between them. As a result, although users can obtain exercise data, water intake data, or dietary data separately, it is difficult to form a continuous, complete, and traceable health management loop.

[0003] In terms of diet management, existing systems mostly rely on simply recording food names, calories, or nutritional components. This typically depends on manual input or estimation via photos, making the data entry process cumbersome and resulting in poor data accuracy and consistency. Especially in diet management scenarios centered on food diversity, users not only need to record daily calorie intake but also need to statistically analyze the types, repetition, and categorization of different foods over a certain period. Manual statistical analysis is difficult and prone to errors such as omissions, duplicate calculations, or inability to determine the balance of food intake. Therefore, existing diet management systems struggle to establish a closed-loop technology for automatically identifying, deduplicating, identifying gaps, and supplementing food intake across multiple food intake targets.

[0004] In terms of physiological data monitoring, although existing wearable devices such as smartwatches and wristbands can collect heart rate, blood pressure, blood sugar, exercise ECG or exercise data, in most cases they are only used as standalone data display tools. The collected data is not effectively correlated with the user's daily food intake, water intake, basal metabolism, exercise consumption and physical examination records, making it difficult for physiological monitoring data to be used in dietary plan adjustment, calorie balance calculation and long-term health change analysis, thus limiting the value of its data utilization.

[0005] In terms of hydration management, existing smart water bottles or hydration reminder devices typically only provide simple timed reminders or record whether a user has drunk water. They cannot dynamically calculate hydration goals based on factors such as the user's height, weight, activity level, and daily hydration intake, nor can they link with user terminals and cloud platforms to record hydration levels. For users who need to consume high-fiber, diverse foods, insufficient water intake can easily affect the effectiveness of dietary management, and current technologies struggle to incorporate hydration monitoring results into a comprehensive health management evaluation system.

[0006] Furthermore, existing meal delivery services are mostly concentrated on regular ordering, calorie-based meals, weight-loss meals, or nutritional meal delivery. There is a lack of a unified data interface between meal production, nutritionist review, matching of user allergy information, calorie input, ingredient diversity statistics, and cloud report generation. Even if meals are manually designed by nutritionists, users still need to manually record ingredients and calories after consumption. The lack of a unified information transmission path based on meal identification codes between the central factory production end, nutrition review end, user terminal, and cloud management platform makes it difficult to accurately and automatically incorporate meal data into users' health management records.

[0007] Meanwhile, existing health management systems lack sufficient support for long-term management, typically only providing short-term weight changes, exercise data, or calorie records. They lack monthly, semi-annual, annual, and multi-year health change reports, as well as regular check-up reminders and check-up result archiving functions. For users who need to continuously manage their weight, diet, or lifestyle, there is a lack of a comprehensive technology platform that can simultaneously connect to smartwatches, smart kettles, meal QR codes, nutritionist review, central factory catering, and long-term cloud storage.

[0008] Therefore, there is an urgent need to provide a health management system that, through the collaborative connection between user terminals, wearable monitoring terminals, drinking water monitoring terminals, meal information collection terminals, nutrition review terminals, meal supply terminals, and cloud management platforms, can achieve unified collection, calculation, review, storage, and feedback of physiological data, drinking water data, meal data, food diversity data, calorie balance data, and physical examination data. This would solve the problems of data dispersion, cumbersome manual recording, disconnect between meal review and actual intake, difficulty in statistical analysis of food diversity, and difficulty in tracking long-term health changes in existing health management methods. Summary of the Invention

[0009] To address the aforementioned problems, this invention provides a health management system that effectively overcomes the shortcomings of existing technologies.

[0010] The present invention is achieved through the following technical solution: a health management system, including a user terminal, a wearable monitoring terminal, a drinking water monitoring terminal, a meal information collection terminal, a nutrition review terminal, a meal supply terminal, and a cloud management platform; The wearable monitoring terminal is communicatively connected to the user terminal and is used to collect the user's physiological monitoring data according to a preset collection cycle, and transmit the physiological monitoring data to the user terminal. The physiological monitoring data includes one or more of heart rate data, blood pressure data, blood glucose data, and exercise electrocardiogram data. The drinking water monitoring terminal is communicatively connected to the user terminal and is used to collect the user's water consumption and drinking time, and generate a drinking water reminder message when the user's cumulative water consumption within a preset time period does not reach the stage drinking water target. The food information collection terminal is used to collect the food identification code on the food packaging, and obtain the corresponding food ingredient type, ingredient quantity, food calories, food portion size, meal time information and allergen information based on the food identification code; The user terminal is used to store basic user information, medical history information, food sensitivity information and drug allergy information, and to generate user health management results based on the user's height, weight, activity status, physiological monitoring data, water intake data and meal data; The nutrition review platform is used by nutritionists to review meal plans based on user basic information, medical history, food sensitivity information, drug allergy information, target calorie intake, and food diversity goals. The food supply end is used to generate food production information and food identification codes based on the approved food plan, and to configure the food identification codes on the food packaging; The cloud management platform is used to receive and store user information, physiological monitoring data, drinking water data, food intake data, physical examination data and health management results uploaded by the user terminal, and generate periodic health change reports.

[0011] As a preferred technical solution, the wearable monitoring terminal includes a physiological sensing unit, a timed acquisition unit, a data caching unit, a wireless transmission unit, and a display unit. The timed acquisition unit is used to control the physiological sensing unit to collect heart rate data, blood pressure data, blood glucose data, and exercise electrocardiogram data at fixed time intervals. The data caching unit is used to bind and store each collected physiological monitoring data with the acquisition time. The wireless transmission unit is used to send the physiological monitoring data bound with the acquisition time to the user terminal. The display unit is used to display the physiological monitoring data or the interim monitoring results in the data caching unit.

[0012] As a preferred technical solution, the drinking water monitoring terminal includes a container body, a drinking water volume detection unit, a drinking water time recording unit, a drinking water target comparison unit, an alert unit, and a communication unit. The drinking water volume detection unit is used to detect the amount of water consumed by the user each time. The drinking water time recording unit is used to record the user's drinking time. The drinking water target comparison unit is used to compare the cumulative drinking water volume within a preset time period with the stage drinking water target. When the cumulative drinking water volume is lower than the stage drinking water target, the alert unit generates an audio alert, a vibration alert, or a light alert. The communication unit sends the drinking water data and alert records to the user terminal.

[0013] As a preferred technical solution, the user terminal includes a user data management module, a target calculation module, a meal allocation module, and a weight update module. The user data management module is used to store user member information, height, weight, activity status, medical history, food sensitivity information, and drug allergy information. The target calculation module is used to calculate the daily target water intake, daily target calorie intake, and basal metabolic rate based on the user's height, weight, and activity status. The meal allocation module is used to allocate the daily target calorie intake proportionally to breakfast, lunch, and dinner. The weight update module is used to prompt the user to update their weight data at a preset period and recalculate the daily target water intake, daily target calorie intake, and basal metabolic rate based on the updated weight data.

[0014] As a preferred technical solution, the user terminal further includes a food diversity management module. The food diversity management module includes a food reading unit, a food deduplication unit, a periodic statistics unit, and an output gap prompt unit. The food reading unit is used to read the food list in the meal according to the meal identification code. The food deduplication unit is used to deduplicate foods that are repeatedly consumed within the same statistical period. The periodic statistics unit is used to count the number of different foods that the user has consumed within the statistical period. The output gap prompt unit is used to generate a food replenishment prompt when the number of different foods is lower than a preset food diversity target.

[0015] As a preferred technical solution, the preset food diversity target is to consume no less than 30 different foods daily or weekly. The periodic statistics unit is also used to classify and count the foods according to grains, vegetables, fruits, beans, nuts and seeds, mushrooms, spices and proteins, and generate a food structure balance prompt based on the intake of different categories of foods. The output gap prompt unit is also used to output corresponding food supplementation suggestions based on the food structure balance prompt.

[0016] As a preferred technical solution, the user terminal further includes a calorie balance calculation module and a health result generation module. The calorie balance calculation module includes a calorie intake accumulation unit, an exercise expenditure calculation unit, a basal metabolic rate calculation unit, and a result determination unit. The calorie intake accumulation unit is used to accumulate the user's daily calorie intake based on the meal identification code. The exercise expenditure calculation unit is used to calculate the exercise expenditure based on the user's weight, heart rate data, and exercise time. The basal metabolic rate calculation unit is used to calculate the basal metabolic rate based on the user's height, weight, and activity level. The result determination unit is used to generate a weight management evaluation result based on the daily calorie intake, basal metabolic rate, and exercise expenditure. The health result generation module is used to write the weight management evaluation result into a daily health management record table.

[0017] As a preferred technical solution, the nutrition review unit includes a user risk reading unit, a meal plan receiving unit, an allergy conflict detection unit, a calorie review unit, and an identification code confirmation unit. The user risk reading unit is used to read the user's medical history information, food sensitivity information, and drug allergy information. The meal plan receiving unit is used to receive user data, target calorie intake, and food diversity targets sent by the user terminal. The allergy conflict detection unit is used to determine whether the ingredients in the meal plan conflict with the user's food sensitivity information or drug allergy information. The calorie review unit is used to determine whether the calorie content of the meal plan matches the user's target calorie intake and meal distribution results. The identification code confirmation unit is used to generate or confirm the meal identification code after the meal plan is approved.

[0018] As a preferred technical solution, the food supply unit includes a menu cycle management unit, an order management unit, a central factory production unit, and a delivery management unit. The menu cycle management unit is used to generate a cycle menu according to a preset number of days and control the repetition rate of ingredients within the same menu cycle to be lower than a preset repetition threshold. The order management unit is used to manage users' weekly, monthly, quarterly, semi-annual, annual, or multi-year orders. The central factory production unit is used to generate food production tasks based on the food plan approved by the nutrition review unit and generate food packaging with the food identification code. The delivery management unit is used to record the food's freezing status, delivery status, and delivery status.

[0019] As a preferred technical solution, the cloud management platform includes a cloud account management unit, a health data storage unit, a physical examination reminder unit, a report generation unit, and a permission management unit. The cloud account management unit is used to establish cloud storage accounts for users. The health data storage unit is used to store users' daily physiological monitoring data, water intake data, meal intake data, weight management evaluation results, and physical examination data. The physical examination reminder unit is used to generate physical examination reminder information according to a preset cycle and send the physical examination reminder information to the user terminal. The report generation unit is used to generate monthly, semi-annual, annual, two-year, and three-year reports based on the stored health data. The permission management unit is used to configure different data access permissions according to the identities of users, customer service, nutritionists, and managers.

[0020] The beneficial effects of this invention are as follows: By setting up user terminals, wearable monitoring terminals, drinking water monitoring terminals, meal information collection terminals, nutrition review terminals, meal supply terminals, and a cloud management platform, this invention establishes a unified system architecture for physiological monitoring, drinking water recording, meal identification, nutrition review, meal production, delivery recording, and cloud report generation. Compared with existing methods of recording with a single app or monitoring with a single smart device, this invention can centrally process and correlate data collected from multiple terminals. This eliminates the reliance on scattered manual recording for daily health management results, instead forming a cohesive whole from multi-source data, thus improving the continuity, accuracy, and automation of the health management process.

[0021] This invention uses a wearable monitoring terminal to periodically collect physiological monitoring data such as heart rate, blood pressure, blood glucose, and exercise electrocardiogram, and transmits this data to the user terminal via a wireless transmission unit. This allows the physiological data to be correlated with the user's diet, water intake, and exercise in chronological order. This structure not only enables the periodic collection and caching of physiological monitoring data but also avoids omissions caused by users manually recording physiological indicators, providing a more stable data source for subsequent calorie balance calculations and health result generation.

[0022] This invention collects users' water consumption and drinking time through a water monitoring terminal. A water consumption target comparison unit then determines whether the cumulative water consumption within a preset time period has reached the stage's water consumption target. If the target is not met, an alert unit generates an audible, vibration, or visual reminder. Therefore, water consumption management is no longer a simple timed reminder, but rather a judgment based on actual water consumption and stage targets. This allows for more accurate encouragement of users to complete their daily water consumption goals, and the water consumption data is sent to the user's terminal for health management recording, enhancing the linkage between water consumption monitoring and overall health management.

[0023] This invention collects meal identification codes from meal packaging via a meal information collection terminal, allowing users to directly access information such as ingredient types, quantities, calories, portion size, meal frequency, and allergens when consuming the meal. This eliminates the need for users to manually input ingredient and calorie information item by item. The meal identification code connects data from the meal production end, the nutrition verification end, and the user's terminal, providing a traceable data foundation for meals from verification, production, and distribution to user intake records, thus improving the accuracy and convenience of meal data entry.

[0024] This invention, by setting up a food diversity management module and further incorporating a food reading unit, a food deduplication unit, a periodic statistics unit, and a gap-finding prompt unit, can automatically read, deduplicate, and count the quantity of food consumed within the same statistical period. When a user fails to meet the goal of consuming at least 30 different foods daily or weekly, the system can automatically output a prompt to replenish the food. This design transforms traditional food diversity management, which relies on manual memory and statistics, into a calculable, recordable, and prompt-based technical process, improving the feasibility of diversified diet management.

[0025] This invention categorizes food ingredients into grains, vegetables, fruits, legumes, nuts and seeds, fungi, spices, and proteins. This allows the system to not only track the total quantity of each ingredient but also assess the balance of the food composition and generate supplementary recommendations based on the intake of different categories. Consequently, the system avoids the problem of users achieving their food quantity goals but with an overly singular food category, enabling more precise management of food diversity.

[0026] This invention uses a calorie balance calculation module to comprehensively calculate calorie intake, calorie expenditure through exercise, and basal metabolic rate. A health results generation module then generates a daily health management record, allowing users to intuitively understand the relationship between daily intake and expenditure. Because calorie intake is derived from meal identification codes, exercise expenditure data is calculated based on user weight, heart rate, and exercise time, and basal metabolic rate data is calculated based on height, weight, and activity level, the results are more consistent and valuable for reference compared to manual estimation.

[0027] This invention, through a target calculation module, a meal allocation module, and a weight update module, enables the system to calculate daily target water intake, daily target calorie intake, and basal metabolic rate based on the user's height, weight, and activity level, and allocate these parameters proportionally according to breakfast, lunch, and dinner. By periodically prompting users to update their weight data, the system can recalculate corresponding targets based on changes in the user's body parameters, avoiding the deviation of management results from reality caused by long-term use of fixed targets, and improving the dynamic adaptability of the health management plan.

[0028] This invention reads users' medical history, food allergy information, and drug allergy information through a nutrition review system, and performs allergy conflict detection and calorie verification on meal plans. This allows for risk matching and calorie verification of meal plans before meal delivery. Therefore, meal plans are no longer generated solely based on general calorie standards, but are reviewed in conjunction with individual user information, reducing the possibility of conflicts between meals and users' food allergy or drug allergy information, and improving the match between meal plans and users' target calorie intake.

[0029] This invention achieves end-to-end management of meal plans, from menu circulation and order management to central factory production, frozen delivery, and delivery status recording, through a menu cycle management unit, order management unit, central factory production unit, and delivery management unit at the meal supply end. The central factory production unit can generate meal production tasks based on the approved meal plan and produce meal packaging with meal identification codes, establishing a unified data entry point between the meal supply end and user intake records, facilitating automatic entry of meal information by user terminals and subsequent statistical analysis.

[0030] This invention stores users' daily physiological monitoring data, water intake data, meal intake data, weight management evaluation results, and physical examination data through a cloud management platform, and generates monthly, semi-annual, annual, two-year, and three-year reports, enabling users' health management data to form a long-term continuous record. Compared with existing health management tools that only provide short-term records, this invention can support longer-term data tracking, report generation, and trend observation, which is beneficial for users, nutritionists, or managers to adjust health management plans based on long-term data.

[0031] This invention generates health check reminders according to a preset cycle through a health check reminder unit, and links and stores the health check results with daily physiological monitoring data, water intake data, meal intake data, and health management results, forming a data closed loop between daily health management and periodic health checkups. Therefore, the system avoids relying solely on daily self-test data for judgment and can also incorporate hospital health checkup results into long-term health change records, improving the completeness of the health management process.

[0032] This invention uses a permission management unit to configure different data access permissions based on the identities of users, customer service representatives, nutritionists, and administrators. This ensures that different roles can only access data content corresponding to their responsibilities, improving the security and standardization of user data management while meeting the collaborative needs of health management services. Furthermore, enabling customer service representatives and nutritionists to collaboratively view abnormal records, food shortage records, insufficient hydration records, or report results also enhances the system's service responsiveness. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] Figure 1 This is a schematic diagram of the overall architecture of the health management system of the present invention; Figure 2 This is a structural block diagram of the wearable monitoring terminal of the present invention; Figure 3 This is a structural block diagram of the drinking water monitoring terminal of the present invention; Figure 4 This is a functional block diagram of the user terminal of the present invention; Figure 5 This is a schematic diagram of the food diversity management and heat balance calculation process of the present invention; Figure 6 This is a schematic diagram illustrating the collaboration between the nutrition review end and the meal supply end of the present invention. Figure 7 This is a block diagram of the cloud management platform of the present invention. Detailed Implementation

[0035] All features disclosed in this specification, or all steps in all disclosed methods or processes, may be combined in any way, except for mutually exclusive features and / or steps.

[0036] Any feature disclosed in this specification (including any appended claims, abstract, and drawings) may be replaced by other equivalent or similar features for a similar purpose, unless specifically stated otherwise. That is, unless specifically stated otherwise, each feature is merely one example of a series of equivalent or similar features.

[0037] See Figures 1 to 7 This embodiment provides a health management system 100, which is used to uniformly collect, calculate, review, store, and provide feedback on users' physiological monitoring data, drinking water data, food intake data, food diversity data, nutritional review data, meal supply data, and long-term health change data. The health management system 100 includes a user terminal 110, a wearable monitoring terminal 120, a drinking water monitoring terminal 130, a meal information collection terminal 140, a nutritional review terminal 150, a meal supply terminal 160, and a cloud management platform 170. User terminal 110 can be a smartphone, tablet, or other mobile terminal with data processing, communication connection, barcode scanning and information display functions. Wearable monitoring terminal 120 can be a smartwatch, smart bracelet, or other wearable health monitoring device. Drinking water monitoring terminal 130 can be a smart kettle, smart cup, or drinking water container with drinking water detection function. Meal information collection terminal 140 can be a barcode scanning module, camera recognition module, or independent barcode scanning device installed in user terminal 110. Nutrition review terminal 150 can be a management terminal or review system used by nutritionists. Meal supply terminal 160 can be a central factory, store, distribution terminal, or meal production management system. Cloud management platform 170 can be a server, cloud database, or cloud health management system.

[0038] In practical use, users first establish a personal account through user terminal 110 and enter basic user information, which may include name, age, gender, height, weight, activity status, membership information, medical history, food sensitivity information, and drug allergy information. User terminal 110 uses the above information as the basis for subsequent target calculations, meal review, allergy conflict assessment, food diversity statistics, and health result generation. User terminal 110 can also remind users to update their weight data according to a preset cycle, such as reminding users to update their weight monthly, so that the system can recalculate daily target water intake, daily target calorie intake, and basal metabolic rate based on changes in the user's body parameters, avoiding inaccurate health management results due to long-term use of fixed parameters.

[0039] The wearable monitoring terminal 120 is communicatively connected to the user terminal 110, and data transmission between them can be achieved via Bluetooth, Wi-Fi, cellular network, or other short-range wireless communication methods. The wearable monitoring terminal 120 collects the user's physiological monitoring data according to a preset collection cycle and transmits the collected physiological monitoring data to the user terminal 110. The physiological monitoring data may include one or more of the following: heart rate data, blood pressure data, blood glucose data, and exercise electrocardiogram data; it may also further include auxiliary health data such as sleep data, step count data, exercise duration data, and blood oxygen data. The preset collection cycle can be set according to actual needs, such as collecting data every 30 minutes, or the collection frequency can be automatically adjusted according to the user's exercise status, rest status, or abnormal status.

[0040] See Figure 2 The wearable monitoring terminal 120 includes a physiological sensing unit 121, a timed acquisition unit 122, a data buffer unit 123, a wireless transmission unit 124, and a display unit 125. The physiological sensing unit 121 collects the user's heart rate, blood pressure, blood glucose, and exercise electrocardiogram (ECG) data. The timed acquisition unit 122 is connected to the physiological sensing unit 121 and controls the physiological sensing unit 121 to collect data at fixed time intervals, triggering the physiological sensing unit 121 to perform one or more samplings when a preset acquisition time point is reached. The data buffer unit 123 receives and temporarily stores each collected physiological monitoring data, and binds the physiological monitoring data with the acquisition time, device number, user identity information, or acquisition status to form a monitoring record with a time identifier. The wireless transmission unit 124 is connected to the data buffer unit 123 and sends the physiological monitoring data bound to the acquisition time to the user terminal 110. The display unit 125 is used to display real-time heart rate, blood pressure, blood sugar, exercise ECG status or interim monitoring results locally on the wearable monitoring terminal 120, so that users can directly view their current physical status.

[0041] The drinking water monitoring terminal 130 is communicatively connected to the user terminal 110 to collect the user's water consumption and drinking time. It generates a drinking reminder message when the user's cumulative water consumption within a preset time period fails to reach the stage's drinking target. The drinking water monitoring terminal 130 can determine whether the user has engaged in drinking behavior through methods such as weight sensing, liquid level detection, flow rate detection, tilt angle detection, or lid opening detection, and calculates the amount of water consumed each time based on changes in the weight or level of the liquid in the container before and after drinking. The drinking water monitoring terminal 130 can upload drinking water data to the user terminal 110 at fixed time intervals, such as every 30 minutes, or it can upload drinking water data immediately after each drinking behavior.

[0042] See Figure 3 The drinking water monitoring terminal 130 includes a container body 131, a drinking water volume detection unit 132, a drinking water time recording unit 133, a drinking water target comparison unit 134, an alert unit 135, and a communication unit 136. The container body 131 is used to hold drinking water or other beverages. The drinking water volume detection unit 132 is mounted on or connected to the container body 131 and is used to detect the amount of water consumed each time. The drinking water time recording unit 133 records the time of each drinking action by the user and forms a drinking water time sequence. The drinking water target comparison unit 134 is connected to both the drinking water volume detection unit 132 and the drinking water time recording unit 133, and is used to compare the cumulative drinking water volume within a preset time period with a stage drinking water target. When the user's cumulative drinking water volume within the preset time period is lower than the stage drinking water target, the alert unit 135 generates an audible alert, a vibration alert, or a light alert to remind the user to replenish water in time. The communication unit 136 is used to send drinking water data and reminder records to the user terminal 110, so that the user terminal 110 can accumulate and record the user's daily drinking water status and make a judgment.

[0043] User terminal 110, as the local data processing core of the health management system 100, receives physiological monitoring data uploaded by wearable monitoring terminal 120, drinking water data uploaded by drinking water monitoring terminal 130, and meal data collected by meal information collection terminal 140, and generates user health management results based on the above data. (See also...) Figure 4 The user terminal 110 includes a user data management module 111, a target calculation module 112, a meal allocation module 113, a weight update module 114, a food diversity management module 115, a calorie balance calculation module 116, a health result generation module 117, a physical examination reminder module 118, and a data synchronization module 119.

[0044] The user data management module 111 stores user member information, height, weight, activity status, medical history, food sensitivity information, and drug allergy information. The activity status can include sedentary, light, moderate, and high-intensity activity levels, and can also be automatically determined based on the user's daily steps, exercise duration, or work type. The target calculation module 112, connected to the user data management module 111, calculates the daily target water intake, daily target calorie intake, and basal metabolic rate based on the user's height, weight, and activity status. The meal allocation module 113, connected to the target calculation module 112, distributes the daily target calorie intake proportionally to breakfast, lunch, and dinner, for example, 30% for breakfast, 40% for lunch, and 30% for dinner. This can also be adjusted based on the user's sleep habits, exercise time, or a nutritionist's plan. The weight update module 114 prompts the user to update their weight data at preset intervals and sends the updated weight data to the target calculation module 112, causing the target calculation module 112 to recalculate the daily target water intake, daily target calorie intake, and basal metabolic rate.

[0045] The meal information collection terminal 140 is used to collect the meal identification code 165 on the meal packaging. The meal identification code 165 can be a QR code, barcode, RFID tag, or other identifiable data tag. The meal identification code 165 can contain the meal number, meal type, ingredient list, ingredient quantity, meal calories, meal portion size, allergen information, nutritionist review mark, production batch information, freezing status information, and delivery status information. Before or after eating the meal, the user scans the meal identification code 165 through the meal information collection terminal 140. The user terminal 110 can then obtain the corresponding meal's ingredient types, ingredient quantities, meal calories, meal portion size, meal information, and allergen information based on the meal identification code 165, and write the above information into the corresponding user's meal intake record.

[0046] The food diversity management module 115 is used to statistically analyze the different foods consumed by a user within a preset statistical period, based on the food list corresponding to the meal identification code 165. (See also...) Figure 5The food diversity management module 115 includes a food reading unit 1151, a food deduplication unit 1152, a periodic statistics unit 1153, and an output gap prompt unit 1154. The food reading unit 1151 reads the food list from the meal based on the meal identification code 165 and writes the name, category, and number of each food ingredient into the user's daily or weekly food record. The food deduplication unit 1152 deduplicates foods repeatedly consumed within the same statistical period, preventing the same food ingredient from being counted as multiple food categories when it appears repeatedly in different meals. The periodic statistics unit 1153 counts the number of different foods consumed by the user within the statistical period and determines whether the quantity of different foods meets the preset food diversity target. The output gap prompt unit 1154 generates a food replenishment prompt when the quantity of different foods is lower than the preset food diversity target, enabling the user, nutritionist, or meal supplier 160 to replenish the corresponding food ingredients based on the gap prompt.

[0047] In one specific implementation, the preset food diversity target is to consume no less than 30 different foods daily or weekly. The periodic statistics unit 1153 not only counts the total quantity of different foods, but also categorizes them into grains, vegetables, fruits, legumes, nuts and seeds, mushrooms, spices, and proteins, and generates a balanced food structure prompt based on the intake quantity of each category. For example, if a user consumes more vegetables and fruits but less grains, legumes, or nuts and seeds within a statistical period, the gap prompt unit 1154 can output supplementation suggestions for the corresponding categories based on the balanced food structure prompt, ensuring that the user's food diversity management focuses not only on quantity but also on the structure of food categories.

[0048] The calorie balance calculation module 116 generates weight management evaluation results based on data such as meal calories, physiological monitoring data, exercise time, and basal metabolic rate. The calorie balance calculation module 116 includes a calorie intake accumulation unit 1161, an exercise expenditure calculation unit 1162, a basal metabolic rate calculation unit 1163, and a result determination unit 1164. The calorie intake accumulation unit 1161 accumulates the user's daily calorie intake based on the meal identification code 165 and assigns the calories to breakfast, lunch, or dinner according to meal information. The exercise expenditure calculation unit 1162 calculates exercise expenditure based on the user's weight, heart rate data, and exercise time. Heart rate data can be obtained from the wearable monitoring terminal 120, and exercise time can be obtained from the user terminal 110 or the wearable monitoring terminal 120. The basal metabolic rate calculation unit 1163 calculates basal metabolic rate based on the user's height, weight, and activity level, and updates the basal metabolic rate synchronously after the weight update module 114 updates the user's weight. The result determination unit 1164 is used to generate weight management evaluation results based on daily calorie intake, basal metabolic rate, and exercise calorie expenditure, and send the calculation results to the health result generation module 117.

[0049] The health outcome generation module 117 integrates weight management evaluation results, hydration achievement results, food diversity achievement results, and physiological monitoring status to generate a daily health management record. In one embodiment, the health outcome generation module 117 calculates the daily calorie difference by subtracting basal metabolic rate and exercise expenditure from daily calorie intake, and generates the user's daily health management results by combining factors such as whether hydration, food diversity, and meal calorie distribution deviate from the target. When the calorie difference exceeds a preset threshold, the health outcome generation module 117 generates an over-consumption warning; when the calorie difference is below or equal to the preset threshold and both hydration and food diversity targets are met, the health outcome generation module 117 generates an achievement warning or a health management score. The above results can be displayed on the user terminal 110 or uploaded to the cloud management platform 170.

[0050] The nutrition review panel (150) is used by nutritionists to review meal plans based on user information, medical history, food sensitivities, drug allergies, target calorie intake, and food diversity goals. See also... Figure 6The nutrition review unit 150 includes a user risk reading unit 151, a meal plan receiving unit 152, an allergy conflict detection unit 153, a calorie review unit 154, and an identification code confirmation unit 155. The user risk reading unit 151 reads the user's medical history, food sensitivity information, and drug allergy information, enabling nutritionists or the system to understand the user's dietary risks. The meal plan receiving unit 152 receives user data, target calorie intake, and food diversity targets sent by the user terminal 110, and can also receive meal plans for review provided by the meal supply unit 160. The allergy conflict detection unit 153 determines whether the ingredients in the meal plan conflict with the user's food sensitivity information or drug allergy information. When a conflict is detected, the nutrition review unit 150 can generate a replacement suggestion or a correction prompt. The calorie review unit 154 determines whether the calorie content of the meal plan matches the user's target calorie intake and meal distribution results. The identification code confirmation unit 155 is used to generate or confirm the meal identification code 165 after the meal plan is approved, so that the approved meal plan can form a corresponding relationship with the subsequent meal production, packaging and user scanning and entry.

[0051] The food supply unit 160 generates food production information and a food identification code 165 based on the approved food plan, and configures the food identification code 165 on the food packaging. The food supply unit 160 includes a menu cycle management unit 161, an order management unit 162, a central factory production unit 163, and a delivery management unit 164. The menu cycle management unit 161 generates a cyclical menu according to a preset number of days, for example, generating food plans with a three-day menu cycle, and controls the repetition rate of ingredients within the same menu cycle to be below a preset repetition threshold, so that users can more easily achieve the goal of ingredient diversity during continuous multi-day food supply. The order management unit 162 manages users' weekly, monthly, quarterly, semi-annual, annual, or multi-year orders, and records user order cycles, delivery frequency, meal quantity, and service status. The central factory production unit 163 generates food production tasks based on the food plan approved by the nutrition review unit 150, and performs ingredient preparation, processing, packaging, freezing, or preservation according to the food production tasks. The central factory production unit 163 is also used to generate meal packaging with meal identification codes 165, so that each meal can be associated with the user, meal number, calories, ingredient list, and audit records through the meal identification code 165. The delivery management unit 164 is used to record the frozen status, delivery status, and delivery status of the meals, and synchronize the relevant status information to the user terminal 110 or the cloud management platform 170.

[0052] The cloud management platform 170 is used to receive and store user information, physiological monitoring data, drinking water data, meal intake data, physical examination data, and health management results uploaded by user terminals 110, and to generate periodic health change reports. See also Figure 7 The cloud management platform 170 includes a cloud account management unit 171, a health data storage unit 172, a physical examination reminder unit 173, a report generation unit 174, and a permission management unit 175. The cloud account management unit 171 is used to create cloud storage accounts for users and associate user terminals 110, wearable monitoring terminals 120, drinking water monitoring terminals 130, and user order information with the cloud accounts. The health data storage unit 172 is used to store users' daily physiological monitoring data, drinking water data, meal intake data, weight management evaluation results, and physical examination data, and categorizes and stores them according to time, data type, device source, and user identity. The physical examination reminder unit 173 is used to generate physical examination reminder information according to a preset cycle, such as once every six months, and send the physical examination reminder information to the user terminal 110. After completing a physical examination, the user can upload the examination results through the user terminal 110, and the health data storage unit 172 associates and stores the examination results with historical daily health data. The report generation unit 174 is used to generate monthly, semi-annual, annual, two-year, and three-year reports based on stored health data, enabling users, nutritionists, or authorized managers to view long-term health trends. The access control unit 175 is used to configure different data access permissions based on the identities of users, customer service representatives, nutritionists, and managers, preventing unauthorized personnel from viewing health data outside their authorized scope.

[0053] The data synchronization module 119 is used to enable data upload and download between the user terminal 110 and the cloud management platform 170. The user terminal 110 can upload locally generated user information, physiological monitoring data, water intake data, meal intake data, weight management evaluation results, food diversity statistics, and physical examination data to the cloud management platform 170. The cloud management platform 170 can also send periodic health change reports, physical examination reminders, nutritionist review results, meal plan adjustment information, and customer service prompts to the user terminal 110. Through the data synchronization module 119, even if a user changes their user terminal 110, they can restore historical health data from the cloud management platform 170, improving the continuity of system use.

[0054] During the operation of the health management system 100, after the user enters basic information through the user terminal 110, the target calculation module 112 calculates the daily target water intake, daily target calorie intake, and basal metabolic rate based on the user's height, weight, and activity level. The meal allocation module 113 further allocates the daily target calorie intake to breakfast, lunch, and dinner. The wearable monitoring terminal 120 collects the user's heart rate, blood pressure, blood sugar, and exercise ECG data according to a preset collection cycle and sends the data to the user terminal 110. The water intake monitoring terminal 130 collects the user's water intake and drinking time in real time or periodically, and issues a reminder through the reminder unit 135 when the user fails to reach the stage water intake target, while simultaneously sending the water intake data to the user terminal 110. The meal supply terminal 160 produces meals according to the meal plan approved by the nutrition review terminal 150 and configures the meal identification code 165 on the meal packaging. When a user dinees, the meal information collection terminal 140 collects the meal identification code 165. The user terminal 110 reads the corresponding ingredient list, meal calories, and meal information. Then, the ingredient diversity management module 115 reads the ingredients, performs deduplication statistics, and provides gap prompts. The calorie balance calculation module 116 performs a comprehensive calculation of calorie intake, exercise-induced calorie expenditure, and basal metabolic rate. Finally, the health result generation module 117 generates the daily health management result.

[0055] The health management system 100 integrates smart wearable monitoring, drinking water monitoring, meal identification, nutritional review, central factory catering, cloud storage, and long-term report generation into a complete closed loop. Users can complete meal calorie input, ingredient diversity statistics, drinking water adequacy assessment, and health result recording without relying entirely on manual memory and recording. Nutritionists can review meal plans through the nutrition review terminal 150, combining user medical history, food sensitivity information, drug allergy information, and target calorie intake. The meal supply terminal 160 can produce and deliver meals based on the approved plans. The cloud management platform 170 can store users' long-term health data and generate reports, thereby improving the automation, data accuracy, and long-term traceability of the health management process.

[0056] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions conceived without inventive effort should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope defined in the claims.

Claims

1. A health management system (100), characterized in that, It includes a user terminal (110), a wearable monitoring terminal (120), a drinking water monitoring terminal (130), a meal information collection terminal (140), a nutrition review terminal (150), a meal supply terminal (160), and a cloud management platform (170). The wearable monitoring terminal (120) is communicatively connected to the user terminal (110) and is used to collect the user's physiological monitoring data according to a preset collection cycle, and transmit the physiological monitoring data to the user terminal (110). The physiological monitoring data includes one or more of heart rate data, blood pressure data, blood glucose data, and exercise electrocardiogram data. The drinking water monitoring terminal (130) is communicatively connected to the user terminal (110) and is used to collect the user's drinking water volume and drinking time, and generate drinking water reminder information when the user's cumulative drinking water volume within a preset time period does not reach the stage drinking water target; The meal information collection terminal (140) is used to collect the meal identification code (165) on the meal packaging, and obtain the corresponding meal's ingredient type, ingredient quantity, meal calories, meal portion, meal frequency information and allergen information based on the meal identification code (165); The user terminal (110) is used to store user basic information, medical history information, food sensitivity information and drug allergy information, and generate user health management results based on the user's height, weight, activity status, physiological monitoring data, water consumption data and meal data; The nutrition review terminal (150) is used by nutritionists to review meal plans based on user basic information, medical history information, food sensitivity information, drug allergy information, target calorie intake and food diversity goals. The food supply end (160) is used to generate food production information and food identification code (165) according to the approved food plan, and to configure the food identification code (165) on the food packaging; The cloud management platform (170) is used to receive and store user information, physiological monitoring data, drinking water data, food intake data, physical examination data and health management results uploaded by the user terminal (110), and generate periodic health change reports.

2. The health management system (100) according to claim 1, characterized in that, The wearable monitoring terminal (120) includes a physiological sensing unit (121), a timed acquisition unit (122), a data caching unit (123), a wireless transmission unit (124), and a display unit (125). The timed acquisition unit (122) is used to control the physiological sensing unit (121) to collect heart rate data, blood pressure data, blood glucose data, and exercise electrocardiogram data at fixed time intervals. The data caching unit (123) is used to bind and store each physiological monitoring data collected with the acquisition time. The wireless transmission unit (124) is used to send the physiological monitoring data bound with the acquisition time to the user terminal (110). The display unit (125) is used to display the physiological monitoring data or the phased monitoring results in the data caching unit (123).

3. The health management system (100) according to claim 1, characterized in that, The drinking water monitoring terminal (130) includes a container body (131), a drinking water volume detection unit (132), a drinking water time recording unit (133), a drinking water target comparison unit (134), a reminder unit (135), and a communication unit (136). The drinking water volume detection unit (132) is used to detect the amount of water consumed by the user each time. The drinking water time recording unit (133) is used to record the user's drinking time. The drinking water target comparison unit (134) is used to compare the cumulative drinking water volume within a preset time period with the stage drinking water target. When the cumulative drinking water volume is lower than the stage drinking water target, the reminder unit (135) generates a sound reminder, a vibration reminder, or a light reminder. The communication unit (136) sends the drinking water data and reminder records to the user terminal (110).

4. The health management system (100) according to claim 1, characterized in that, The user terminal (110) includes a user data management module (111), a target calculation module (112), a meal allocation module (113), and a weight update module (114). The user data management module (111) is used to store user member information, height, weight, activity status, medical history information, food sensitivity information, and drug allergy information. The target calculation module (112) is used to calculate the daily target water intake, daily target calorie intake, and basal metabolic rate based on the user's height, weight, and activity status. The meal allocation module (113) is used to allocate the daily target calorie intake according to the proportion of breakfast, lunch, and dinner. The weight update module (114) is used to prompt the user to update their weight data according to a preset period and recalculate the daily target water intake, daily target calorie intake, and basal metabolic rate based on the updated weight data.

5. The health management system (100) according to claim 1, characterized in that, The user terminal (110) also includes a food diversity management module (115), which includes a food reading unit (1151), a food deduplication unit (1152), a periodic statistics unit (1153), and an output gap prompt unit (1154). The food reading unit (1151) is used to read the food list in the meal according to the meal identification code (165). The food deduplication unit (1152) is used to deduplicate the food that is repeatedly consumed within the same statistical period. The periodic statistics unit (1153) is used to count the number of different food items that the user has consumed within the statistical period. The output gap prompt unit (1154) is used to generate a food replenishment prompt when the number of different food items is lower than the preset food diversity target.

6. The health management system (100) according to claim 5, characterized in that, The preset food diversity target is to consume no less than 30 different foods per day or per week. The periodic statistics unit (1153) is also used to classify and count the foods according to grains, vegetables, fruits, beans, nuts and seeds, mushrooms, spices and proteins, and generate food structure balance prompts based on the intake of different categories of foods. The output gap prompt unit (1154) is also used to output corresponding food supplementation suggestions based on the food structure balance prompts.

7. The health management system (100) according to claim 1, characterized in that, The user terminal (110) further includes a calorie balance calculation module (116) and a health result generation module (117). The calorie balance calculation module (116) includes a calorie intake accumulation unit (1161), an exercise consumption calculation unit (1162), a basal metabolic rate calculation unit (1163), and a result determination unit (1164). The calorie intake accumulation unit (1161) is used to accumulate the user's daily calorie intake according to the meal identification code (165). The exercise consumption calculation unit (1162) is used to calculate the exercise consumption calorie according to the user's weight, heart rate data, and exercise time. The basal metabolic rate calculation unit (1163) is used to calculate the basal metabolic rate according to the user's height, weight, and activity status. The result determination unit (1164) is used to generate a weight management evaluation result based on the daily calorie intake, basal metabolic rate, and exercise consumption. The health result generation module (117) is used to write the weight management evaluation result into the daily health management record table.

8. The health management system (100) according to claim 1, characterized in that, The nutrition review unit (150) includes a user risk reading unit (151), a meal plan receiving unit (152), an allergy conflict detection unit (153), a calorie review unit (154), and an identification code confirmation unit (155). The user risk reading unit (151) is used to read the user's medical history information, food sensitivity information, and drug allergy information. The meal plan receiving unit (152) is used to receive user data, target calorie intake, and food diversity targets sent by the user terminal (110). The allergy conflict detection unit (153) is used to determine whether the food in the meal plan conflicts with the user's food sensitivity information or drug allergy information. The calorie review unit (154) is used to determine whether the calorie content of the meal plan meets the user's target calorie intake and meal allocation results. The identification code confirmation unit (155) is used to generate or confirm the meal identification code (165) after the meal plan is approved.

9. The health management system (100) according to claim 1, characterized in that, The food supply unit (160) includes a menu cycle management unit (161), an order management unit (162), a central factory production unit (163), and a delivery management unit (164). The menu cycle management unit (161) is used to generate a cycle menu according to a preset number of days and control the repetition rate of ingredients within the same menu cycle to be lower than a preset repetition threshold. The order management unit (162) is used to manage users' weekly orders, monthly orders, quarterly orders, semi-annual orders, annual orders, or multi-year orders. The central factory production unit (163) is used to generate food production tasks based on the food plan approved by the nutrition review unit (150) and generate food packaging with the food identification code (165). The delivery management unit (164) is used to record the food freezing status, delivery status, and delivery status.

10. The health management system (100) according to claim 1, characterized in that, The cloud management platform (170) includes a cloud account management unit (171), a health data storage unit (172), a physical examination reminder unit (173), a report generation unit (174), and a permission management unit (175). The cloud account management unit (171) is used to establish cloud storage accounts for users. The health data storage unit (172) is used to store users' daily physiological monitoring data, water consumption data, meal intake data, weight management evaluation results, and physical examination data. The physical examination reminder unit (173) is used to generate physical examination reminder information according to a preset cycle and send the physical examination reminder information to the user terminal (110). The report generation unit (174) is used to generate monthly reports, semi-annual reports, annual reports, two-year reports, and three-year reports based on the stored health data. The permission management unit (175) is used to configure different data access permissions according to the identities of users, customer service, nutritionists, and managers.

Images