JP5252343B2 - Health guidance support system - Google Patents

Description

  The present invention relates to a system for supporting health guidance, and more particularly to a system for improving metabolic syndrome and the like caused by lifestyle habits.

In recent years, visceral fat obesity (metabolic syndrome) has attracted attention as one of lifestyle-related diseases. Metabolic syndrome refers to a condition that exceeds the standard of visceral fat area ≧ 100 cm ² (in the case of abdominal circumference, male ≧ 85 cm, female ≧ 90 cm) and has two or more risks of blood lipid, blood pressure, or blood glucose level. It is said that the risk of arteriosclerosis and heart disease or cerebrovascular disease is increased.

  In a medical examination facility or the like, if a medical examinee is diagnosed with metabolic syndrome or obesity, a doctor, a public health nurse, or the like instructs weight reduction. In particular, for the examiner (doctor or public health nurse) who has determined that strong intervention guidance is necessary, set a target weight that matches the weight of the examinee and improve the lifestyle that should be improved toward the target weight The weight loss program proposed as an item may be implemented. In this case, the leader calculates the number of calories to reach the target weight of the examinee (participant in weight loss), and proposes and presents life improvement items related to diet and exercise necessary to reduce the target weight. Will do. Then, the weight loss participant reports the execution status of the presented life improvement items and the change in the weight to the instructor to reduce the weight to the target weight.

Such techniques for weight loss include presenting target values for energy intake and energy consumption according to the target weight, dietary status, and exercise status of participants who are losing weight, as well as dietary restrictions and exercise to meet those target values. A technique for presenting a menu such as a method is known (for example, Patent Document 1).
JP 2004-227522 A

  However, a method in which the instructor sets the target weight of the weight loss participant, calculates the number of calories to reach this target weight, and presents the health improvement items necessary for realizing the target weight by the public health nurse Therefore, it is necessary for the instructor to grasp some life improvement items and the calorie consumption of each life improvement item in advance, and to decide which life improvement item to perform according to the individual, and to adjust the load of that item. The teacher's workload was heavy.

  The instructor takes time to communicate between the instructor and the weight-loss participant in order to set up life improvement items so that the participant's individual life patterns and personal preferences can be met and to facilitate weight loss. There was a need to do. Participants in weight loss interact with the instructor to set up life improvement items, but the improvement items will be selected from the (limited) life improvement items prepared by the instructor, which is not necessarily a dieting method suitable for the individual. There was a case.

  Furthermore, when collecting many life improvement items in advance and setting improvement items suitable for participants from those life improvement items, it is not easy to set life improvement items suitable for individual participants. There was a problem that it took time and effort.

  Moreover, in the case of the said patent document 1, although the estimated weight can be made into a target weight from the change of a eating habit or an exercise habit, there existed a problem that it was difficult to specify a specific life improvement item.

  Therefore, the present invention aims to provide a health guidance support system that efficiently implements uniform health guidance for a large number of health guidance subjects, and in particular, a participant among a number of life improvement items. The purpose is to provide life improvement items that are suitable for.

The present invention provides a health guidance support system for implementing the healthcare for participants directed by the leader, a processor for arithmetic processing, a memory coupled to the processor, the interface connected to said processor, and a weight loss record database implementation and loss situation of loss menu for each participant is stored, the processor receives information of the first participant, and registers the information of the first participant said accepted The weight reduction menu executed by the second participant who has achieved the target weight within the predetermined weight loss period is extracted from the weight reduction menu implementation status of the weight loss recording database, and the extracted weight reduction menu is prioritized in descending order of appearance frequency. assigned a rank in the weight loss menus, the and weight loss menu, based on the first information of participants the registration, the first Select weight loss menu suitable for pressurized's in the order of the priorities, the present selected reduced menu the first participant, the first information of the participants, the first participant , A result of an inquiry to the first participant, and a category of a weight loss menu determined based on the inquiry result.

  According to the present invention, uniform health guidance can be efficiently implemented for a large number of health guidance subjects. In addition, since guidance can be focused on those who particularly need guidance, variations in guidance content by the leader can be suppressed. Furthermore, life improvement items suitable for individual participants can be easily provided from among many life improvement items, and the labor of the instructor can be reduced.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a block diagram showing a configuration of a health guidance support system according to an embodiment of the present invention.

  The health guidance support system according to the embodiment of the present invention includes an administrator terminal device 100, a leader terminal device 200, a participant terminal device 300, and a server 400. The administrator terminal device 100, the leader terminal device 200, the participant terminal device 300, and the server 400 are connected via a network 500.

  The administrator terminal device 100, the leader terminal device 200, and the participant terminal device 300 are computers each including a processor, a memory, a communication interface, and a user interface. Note that these terminal devices may be portable terminal devices such as a PDA or a mobile phone on which an application program (for example, a web browser) operates.

  The server 400 is a computer including a processor, a memory, a storage device, and a communication interface. The server 400 includes initial preparation processing means M1, participation preparation processing means M2, participant data input / browsing processing means M3, intervention guidance processing means M4, event processing means M5, and PDA data registration means M6. Each of these functions is provided by a program stored in the memory.

  The storage device of the server 400 includes a leader management database D1, a fixed phrase database D2, a regular event database D3, a participant management database D4, a weight loss record database D5, a guidance record database D6, an inquiry result database D7, and an individual program database D8. A meal calorie database D9, an exercise calorie database D10, a parameter setting database D11, an individual weight loss target database D12, and an inquiry information database D13 are stored.

  The leader management database D1 stores information such as a leader's identifier, password, and name.

  The fixed phrase database D2 stores information on fixed phrases used in health guidance by the health guidance support system of the present embodiment.

  The regular event database D3 stores information on regular events in health guidance by the health guidance support system of the present embodiment. The events registered in the regular event database D3 are set in advance when the health guidance support system of this embodiment is started up. As a regular event, creation of an e-mail and transmission of an alert are set every predetermined period from the start of weight reduction by a weight loss participant, and an identifier of a sentence to be transmitted is set in advance for each event.

  The fixed phrase database D2 stores sentences or phrases for each sentence identifier set in the regular event database D3.

  As shown in FIG. 21, the participant management database D4 stores participant information in health guidance by the health guidance support system of the present embodiment.

  The weight loss record database D5 stores information on the weight loss of the health guidance participants by the health guidance support system of the present embodiment. For example, the weight loss recording database D5 stores the weight loss participant identifier, weight, and measurement date and time.

  The guidance record database D6 stores information on the history of health guidance by the health guidance support system of the present embodiment. For example, the guidance record database D6 stores the identifier of the leader who gave the health guidance, the identifier of the quantity participant, the record of the health guidance given to the weight loss participant, and the date and time of occurrence.

  As shown in FIG. 23, the inquiry result database D7 stores information obtained by inquiry to the health guidance participants by the health guidance support system of the present embodiment.

  As shown in FIG. 24, the individual program database D8 stores life improvement items executed by the health guidance participants by the health guidance support system of the present embodiment.

  As shown in FIG. 26, the meal calorie database D9 stores information on life improvement items related to meals used for health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 27, the exercise calorie database D10 stores information on life improvement items related to exercise used for health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 25, the parameter setting database D11 stores information on parameters used for health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 34, the individual weight loss target database D12 stores information on weight loss targets of health guidance participants by the health guidance support system of the present embodiment.

  As shown in FIG. 22, the inquiry information database D13 stores information to be interviewed to participants of health guidance by the health guidance support system of the present embodiment.

  FIG. 2 is a flowchart illustrating an outline of processing by the health guidance support system according to the embodiment of this invention.

  First, input of own information by a health guidance participant by the health guidance support system of the present embodiment is accepted. The entered participant information (name, height, weight, identifier, responsible instructor, etc.) is registered in the participant management database D4 (M22, see FIG. 10).

  Next, the server 400 extracts the inquiry information corresponding to the input participant information from the inquiry information database D13, and sends the extracted inquiry information to the participant terminal device 300. At the same time, the target weight is calculated from the weight input by the participant and registered in the individual weight loss target database D12. There is a form that the system side decides within the range where the safety of weight loss is maintained, such as “Target weight is reduced by 5% of the current weight”, and the target weight input by the participant is provided, and the input is accepted and registered in the database There is also a form to do. Next, the participant terminal device 300 receives an input of an answer to the inquiry information. The answer to the inputted inquiry is registered in the inquiry result database D7 (M22, see FIG. 10).

  Next, the server 400 refers to the participant information registered in the participant management database D4 and the answer to the inquiry registered in the inquiry result database D7, and selects a meal menu suitable for the participant from the meal calorie database. The exercise menu selected from D9 is selected from the exercise calorie database D10, and the selected meal menu and exercise menu are transmitted to the participant terminal device 300 as a recommended menu.

  In the meal menu stored in the meal calorie database D9 and the exercise menu stored in the exercise calorie database D10, the amount of exercise and the amount of meal (amount to reduce meals) are set for each predetermined calorie (for example, 100 kcal). Has been. In addition, even in the same exercise, the calorie consumption varies depending on the physical characteristics of the participant, for example, the weight, so the exercise amount for each predetermined calorie consumption is calculated with reference to the participant information registered in the participant management database D4. Is done.

  The participant terminal device 300 presents the transmitted meal menu and exercise menu to the participant as a weight reduction menu. Further, the participant terminal device 300 accepts selection of a meal menu and an exercise menu by the participant. The selected meal menu and the selected exercise menu determine the participant's weight loss program. The selected meal menu and exercise menu are registered in the individual program database D8 (M22, see FIG. 10).

  Next, the participant terminal device 300 accepts input of the participant's daily data (weight, weight loss menu execution state). The input data is registered in the weight loss recording database D5 (M3, see FIG. 5).

  Next, the server 400 determines whether the data registered in the weight loss recording database D5 matches the event registered in the regular event database D3 at a predetermined timing (for example, repeatedly every predetermined period). (M42). The data determination result is registered in the instruction record database D6.

  The events registered in the regular event database D3 are set in advance when the health guidance support system of this embodiment is started up. The regular event can be edited using a regular event editing process (M53, see FIG. 17). Select a registered event, change the timing to generate an event (such as a data change of a weight loss participant), change the event content, or create a new event timing or event content And registered in the regular event database D3.

  Next, the server 400 extracts, from the instruction record database D6, a determination result that determines whether or not to generate an event based on data such as body weight input by the participant, and the extracted determination result is transmitted to the instructor terminal device 200. Send. The leader terminal device 200 displays the received determination result (M4, see FIG. 16).

  Next, the instructor performs instruction determined to be performed based on the displayed determination result. Execution of this guidance can also be performed by means such as e-mail using the health guidance support system of the present embodiment, without the leader using the health guidance support system of the present embodiment, It can also be done by means such as telephone.

  And the leader terminal device 200 receives the instruction | indication of the instruction | indication of the instruction | indication which the instruction | indication which the instructor determined to perform, and produces | generates the record of instruction | indication from the instruction | indication of execution of the instruction | indication input. Moreover, the leader terminal device 200 accepts an input of a record of guidance given by the leader (M4). These generated and input instruction records are registered in the instruction record database D6.

  FIG. 21 is an explanatory diagram showing the configuration of the participant management database D4 of the present embodiment.

  The participant management database D4 is a database in which information of persons who participate in health guidance by the health guidance support system of the present embodiment is registered. The participant management database D4 includes a participant identifier D401, name D402, gender D403, date of birth D404, email address D405, leader identifier D406, password D407, height D408, and weight D409.

  A unique identifier for identifying the participant is registered in the identifier D401. The participant identifier D401 is used to identify the participant data in the health guidance support system of the present embodiment. The participant identifier D401 is used together with the password D405 when the participant accesses the health guidance support system of the present embodiment.

  The name of the participant is registered in the name D402, the gender of the participant in the sex D403, the date of birth of the participant in the date of birth D404, and the email address of the participant in the email address D405.

  A unique identifier for identifying a leader in charge of the participant is registered in the leader identifier D406. In the password D407, a password that is collated when the participant accesses the health guidance support system of the present embodiment is registered. In the height D408 and the weight D409, the height and weight at the start of the instruction of the participant are registered.

  FIG. 22 is an explanatory diagram showing a configuration of the inquiry information database D13 of the present embodiment.

  The inquiry information database D13 is a database in which the contents of the inquiry to be inquired by the participants at the start of health guidance by the health guidance support system of the present embodiment are registered. The inquiry information database D13 includes an inquiry identifier D1301, an inquiry category D1305, a meal category D1302, an exercise menu category D1303, an inquiry content D1306, and an improvement content D1037.

  The inquiry identifier D1301 is a unique identifier for identifying the contents of the inquiry. The inquiry category D1305 indicates the subject of the inquiry. For example, “1” indicates food intake, “2” indicates exercise amount, “3” indicates eating behavior, and “4” indicates If present, it shows exercise behavior.

  The meal category D1302 and the exercise menu category D1303 are codes for classifying the contents of the inquiry category D1305. For example, “1” is an inquiry related to staple foods, “2” is an inquiry about fruits, “3” is an inquiry about snacks, and “9” is an inquiry not related to meals. Registered in For this meal category D1302, an identifier common to the meal category D902 of the meal calorie database D9 is used.

  In the exercise menu category D1303, “1” is registered for an inquiry related to walking / running, “2” is registered for an inquiry related to sports, and “9” is registered for an inquiry not related to exercise. An identifier common to the exercise category D1002 of the exercise calorie database D10 is used for the exercise menu category D1303.

  FIG. 23 is an explanatory diagram showing the configuration of the inquiry result database D7 of the present embodiment.

  The inquiry result database D7 is a database in which participants' answers to the inquiry contents are registered. The interview result database D7 includes a participant identifier D701, an interview identifier D702, an interview answer D703, an improvement implementation questionnaire D704, and an improvement implementation target D705.

  In the participant identifier D701, the identifier of the participant who answered the inquiry is registered, and an identifier common to the identifier D401 of the participant management database D4 is used. In the interview identifier D702, the identifier of the interview answered by the participant is registered, and an identifier common to the interview identifier D1301 in the interview information database D13 is used.

  In the inquiry D 703, the contents of the answer to the inquiry are registered. For example, if the answer content is “Yes”, “1” is registered in the question answer D 703, and if the answer content is “No”, “2” is registered.

  The improvement execution questionnaire D704 stores the degree to which the contents of the inquiry ID can be used as a life improvement item. For example, if it is “0”, it indicates that the questionnaire has not been executed. If it is, it indicates that it is not desired to be a life improvement item, “2” indicates that it cannot be implemented as a life improvement item, and “5” indicates that it can be implemented.

  In the improvement implementation target D705, a flag indicating whether or not to make the contents of the inquiry a weight reduction target is registered. For example, if the response content is “target”, “1” is registered in the improvement implementation target D705, and if the response content is “not target”, “2” is registered.

  FIG. 34 is an explanatory diagram showing the configuration of the individual weight loss target database D12 of the present embodiment.

  The individual weight loss target database D12 is a database in which a weight loss target set by a participant in health guidance by the health guidance support system of the present embodiment is registered. The individual weight loss target database D12 includes a participant identifier D1201, a weight loss target registration date D1202, a start date D1203, a target weight D1204, and a weight loss period D1205.

  In the participant identifier D1201, the identifier of the participant who has set the weight reduction target is registered, and an identifier common to the identifier D401 of the participant management database D4 is used. The date of registration of the weight loss target is registered in the registration date D1202 of the weight loss target.

  In the start date D1203, the start date of the weight loss target is registered. The target weight set by the participant is registered in the target weight D1204. In the weight loss period D1205, a target for a period until reaching the set target weight is registered.

  FIG. 24 is an explanatory diagram showing the configuration of the individual program database D8 of the present embodiment.

  The individual program database D8 is a database in which a weight reduction menu set by a participant in health guidance by the health guidance support system of the present embodiment is registered. The individual program database D8 includes a participant identifier D801, a program registration date D802, a serial number D803, a life improvement item meal menu identifier D804, a life improvement item exercise menu identifier D805, an improvement item increase / decrease amount D806, and Includes improvement item increase / decrease D807.

  In the participant identifier D801, the identifier of the participant who set the action goal is registered, and an identifier common to the identifier D401 of the participant management database D4 is used. The date of registration of this improvement item is registered in the program registration date D802.

  The serial number D803 stores a serial number for each participant in the weight reduction menu selected by the participant. The weight reduction menu selected by the participant is managed by the serial number D803. For example, when the same weight reduction menu is selected by the same participant, the number of the same weight reduction menu selected is assigned.

  In the improvement item meal menu identifier D804, an identifier for uniquely identifying the meal weight reduction menu selected by the participant is registered, and an identifier common to the identifier D901 of the meal calorie database D9 is used.

  In the improvement item exercise menu identifier D805, an identifier for uniquely identifying the exercise weight loss menu selected by the participant is registered, and an identifier common to the identifier D1001 of the exercise calorie database D10 is used.

  The weight reduction menu is a menu for reducing the amount of food in the meal menu and increasing the amount of exercise in the exercise menu, but the increase / decrease for each menu can be changed. For example, depending on the combination of weight reduction menus selected, the high-calorie (low meal amount corresponding to 100 kcal) meal menu is reduced by X, and the low-calorie (high meal equivalent of 100 kcal meal) menu is increased by Y. . At this time, by setting X> Y, it is possible to create a weight loss program that reduces calories in total. In order to express such a combination in the weight reduction menu, the number of improvement items increased / decreased D806 is registered in the improvement item increase / decrease amount D806. For example, if the improvement item is decreased, the decreased number of sheets is registered in the increase / decrease amount D806, and if the improvement item is increased, the value of the increased number of sheets is registered in the increase / decrease amount D806.

  In the improvement item increase / decrease D807, the increase / decrease in improvement items is registered. For example, if the improvement item is decreasing, “1” is registered in the increase / decrease D807, and if the improvement item is increasing, the increase / decrease D8057 “2” is registered.

  FIG. 26 is an explanatory diagram showing the configuration of the meal calorie database D9 of the present embodiment.

  The meal calorie database D9 is a database in which a meal menu presented as a weight reduction menu to participants is registered. As described above, in the meal menu stored in the meal calorie database D9, the type of meal and the amount of meal (amount to reduce meals) are set for each predetermined calorie (for example, 100 kcal).

  The meal calorie database D9 stores a meal menu identifier D901, a meal menu category D902, a meal priority D904, a meal menu name D903, a meal menu unit D905, and a meal menu unit calorie D906.

  In the meal menu identifier D901, an identifier for uniquely identifying a meal whose amount is to be reduced is registered. In the meal menu category D902, the type of meal whose amount is to be reduced is registered. For example, “1” if the meal type is a staple food, “2” if the meal type is fruit, “3” if the meal type is snack, and “9” if the meal type is not related to the meal. "Is registered in the category D902. In the meal menu name D903, the meal and amount to be reduced in this meal menu are registered. The meal priority order D904 stores the priority order for presenting the meal menu to the participants. This priority order is set in processing M17 (FIG. 19) described later, and the smaller the value, the higher the priority order. In the meal menu unit D905, a unit to be taken is stored for the contents of the meal menu name D903. For example, the weight “g” and the number of meals to be ingested are stored. In the meal menu unit calorie D906, the amount of meal heat set in the meal menu name D905 is stored. In this embodiment, 100 kcal is set in the meal menu unit calorie D906.

  FIG. 27 is an explanatory diagram showing the configuration of the exercise calorie database D10 of the present embodiment.

  The exercise calorie database D10 is a database in which exercise menus presented as a weight reduction menu to participants are registered. As described above, in the exercise menu stored in the exercise calorie database D10, an exercise amount is set for each predetermined calorie (for example, 100 kcal).

  The exercise calorie database D10 includes an exercise menu identifier D1001, exercise menu category D1002, exercise priority D1004, exercise menu name D1003, exercise menu unit D1005, exercise menu base weight (male) D1006, 100 kcal consumption time (male), exercise menu. 100kcal consumption time (male) D1007, exercise menu base weight (female) D1008 and 100kcal consumption time (female) D1009.

  In the exercise menu identifier D1001, an identifier for uniquely identifying the exercise to be performed by the participant is registered. In the exercise menu category D1002, the type of exercise to be performed by the participant is registered. For example, “1” is registered in the category D1002 if the exercise is walking or running, “2” if the exercise is sport, and “9” if it is not related to the exercise.

  In the exercise priority order D1004, a priority order for presenting an exercise menu to a participant is stored. This priority order is set in process M17 described later, and the smaller the value, the higher the priority order.

In the exercise menu name D1003, the type of exercise to be performed in this exercise menu is registered. In the exercise menu base weight (male) D1006, the weight (in kg) of a man serving as a reference for the exercise time registered in the exercise menu 100 kcal consumption time (male) D1007 is registered. The exercise menu 100 kcal consumption time (male) D1007 includes the time (minutes) required to consume 100 kcal when the exercise menu D name 1003 is performed with the exercise menu base weight (male) D1006, which is the male standard weight. Unit) is registered. This is because the calorie consumption varies depending on the weight of the participant even in the same exercise, and the exercise menu base weight (male) D1006 is used to calculate an appropriate amount of exercise based on the weight of the participant. Specifically, in order for a person with a weight of Wkg to consume 100 kcal, exercise for the time calculated by the following equation is required.
Exercise time = standard time x standard weight / W
For example, if an exercise with a weight of 80 kg requires an exercise of 30 minutes to consume 100 kcal, an exercise of 60 minutes is necessary for a 40 kg participant to consume 100 kcal. It takes 24 minutes of exercise to consume.

  Exercise menu base weight (female) D1008 and exercise menu 100kcal consumption time (female) D1009 are the above-mentioned male reference weight and exercise time base exercise weight (male) D1006 and exercise menu 100kcal consumption time (male) D1007. Similarly, a value in which a female standard weight and a standard exercise time are set for the exercise menu name D1003 is stored.

  FIG. 35 is an explanatory diagram showing the configuration of the weight loss recording database D5 of the present embodiment.

  The weight loss recording database D5 is a database in which the implementation status of the weight loss menu selected by the participant is registered. The weight loss recording database D5 includes a participant identifier D501, date D502, weight D503, serial number 1 implementation status D504, serial number 2 implementation status D505, serial number 3 implementation status D506, and serial number 4 implementation status D507. included.

  In the participant identifier D501, the identifier of the participant who should perform this weight reduction menu is registered, and an identifier common to the identifier D401 of the participant management database D4 is used. On the date D502, the date on which this weight reduction menu was implemented or not implemented is registered. In the body weight D803, the body weight of the participant on the day indicated by the date D502 is registered.

  In the serial number 1 implementation status D504, the serial number 2 implementation status D505, the serial number 3 implementation status D506, and the serial number 4 implementation status D507, the implementation status of the weight reduction menu indicated by each serial number is registered. The serial number used in the weight loss recording database D5 is the same as the serial number registered in the serial number D803 of the individual-specific program database D8.

  In the implementation status of the weight loss menu, the implementation status of the weight loss menu indicated by this serial number is registered. For example, “1” is registered in the implementation status of each weight reduction menu if the weight reduction menu indicated by the serial number is implemented, and “2” if the weight reduction menu is not implemented.

  FIG. 36 is an explanatory diagram showing the configuration of the regular event database D3 of the present embodiment.

  The regular event database D3 is a database that stores events that are determined to require guidance based on the state of the participant (the implementation status of the weight loss menu, the change in weight, the response status of the participant, etc.). The regular event database D3 includes an event identifier D301, a timing D302, a condition D303, an event content D304, a participant mail wording identifier D305, and a leader wording identifier D306.

  In the event identifier D301, an identifier for uniquely identifying an event is registered. In the timing D302, a time condition determined to be an event is registered. In the case of an event that does not define a temporal condition (an event that occurs any time if the condition D303 is satisfied), “anytime” is registered in the timing D302.

  In the condition D303, a condition for issuing an event (other than the time condition) is registered. “Intervention determination OK” in the condition D303 indicates an event to be executed when “intervention determination OK” is output in the intervention determination processing means M48 and the flowchart of FIG.

  In the event content D304, an action to be performed for this event is registered. That is, when the conditions registered in the timing D302 and the condition D303 are satisfied, the guidance registered in the event content D304 is performed.

  In the participant mail wording identifier D305, the wording identifier used as the text of the mail sent to the participant among the words registered in the text D203 of the standard wording database D2 is registered. Of the words registered in the body text D203 of the fixed phrase database D2, the identifier of the word used when displaying the result of the event check for the leader is registered in the identifier D306 of the leader wording.

Among the conditions registered in the condition D303, the X day target is the body weight that should be reached on the X day in order to achieve the target at the end of the weight loss period, and is calculated by the following equation.
Start weight-((start weight-target weight) x X / weight loss period)
For example, the 10th day target weight of a participant who has the goal of losing 80 kg weight at the start to 3.5 kg in 90 days is:
80-((80-76.5) × 10/90) = 79.611 [kg]
The target weight on the 20th day is
80-((80-76.5) × 20/90) = 79.222 [kg]
It becomes.

  In the regular event database D3, the implementation rate of the weight reduction menu can be set in the condition D303. As a result, the system determines whether or not the weight reduction menu selected by the participant has been implemented, so that it is possible to propose a change in the weight reduction menu if it has not been implemented. Accordingly, it is possible to provide appropriate and uniform guidance according to the weight loss process of the participant while suppressing variation in judgment by the leader.

  FIG. 37 is an explanatory diagram showing a configuration of the fixed phrase database D2 of the present embodiment.

  The fixed phrase database D2 is a database in which the contents of health guidance (for example, e-mail transmitted to participants) performed by the health guidance support system of the present embodiment are registered. The fixed phrase database D2 includes a phrase identifier D201, a title D202, and a text D203.

  In the word identifier D201, an identifier for uniquely identifying a word used for health guidance is registered. In the title D202, a word used as a title of an email transmitted to the participant is registered.

  In the text D203, words used for health guidance are registered. The wording used for the health guidance registered in the text D203 includes the wording used as the text of the email sent to the participants (the one whose identifier begins with "P"), The wording used when displaying the result of the event check (the one whose identifier starts with “S”) is included, and both are classified so as to be distinguishable by the identifier D201.

  FIG. 25 is an explanatory diagram showing the configuration of the parameter setting database D11 of the present embodiment.

  The parameter setting database D11 of the present embodiment is used to determine the priority order of the weight loss menu presented by the health guidance support system of the present embodiment. The parameter setting database D11 includes an identifier D1101, a setting item D1102, and setting contents D1103.

  An identifier for uniquely identifying the set parameter is registered in the identifier D1101. In the setting item D1102, the definition of the setting content is registered. For example, “[1: Meal / 2: Exercise] + [Category] + [1: Priority / 2: Random]” shown in FIG. 25 indicates whether the first digit of the setting content is meal or exercise. The digit indicates the menu category, and the third digit indicates whether it is in priority order or random. Specifically, if the setting content D1103 is “111”, it indicates that the meal menu of meal, category = 1 (meal category “1” indicates “main meal”) is presented in priority order.

  In the setting content D1103, a parameter for determining whether to present the weight reduction menu in the order of priority or in a random order is registered. FIG. 38 is an explanatory diagram showing the configuration of the instruction record database D6 of the present embodiment.

  The instruction record database D6 of the present embodiment is a database in which the history of health guidance implemented (or to be implemented) by the health guidance support system of the present embodiment is registered. The instruction record database D6 includes an instruction record identifier D601, a target participant identifier D602, an execution instructor identifier D603, an execution date and time D604, a type D605, a related event identifier D606, an event occurrence date and time D607, an instruction content D608, and an e-mail title. D609, mail text D610, status D611, and check result display flag D612.

  In the instruction record identifier D601, an identifier for uniquely identifying the record of the implemented health instruction is registered. The identifier of the participant for whom this health guidance has been implemented is registered in the identifier D602 of the target participant, and an identifier common to the identifier D401 of the participant management database D4 is used.

  The identifier of the instructor D603 is registered with the identifier of the instructor who has performed this health instruction, and the same identifier as the identifier D406 of the participant management database D4 is used. In addition, when the identifier D603 of an implementation leader is NULL, it indicates that this health guidance support system is a health guidance automatically implemented.

  In the implementation date D604, the date and time when the health guidance was implemented are registered. Specifically, the date and time when the e-mail created by this health guidance support system was sent, the date and time when the e-mail manually entered by the instructor, or the date and time when the interview with the participant was conducted, etc. are registered. Is done.

  The type of health guidance that has been implemented is registered in the type D605. For example, “1” is defined if health guidance is provided by e-mail, “2” if health guidance is provided by telephone, and “3” if health guidance is provided by interview. If the health guidance is provided by no method, “9” is registered in the type D605.

  The identifier of the event that triggered the health guidance is registered in the related event identifier D606, and an identifier common to the event identifier D301 of the regular event database D3 is used.

  In the event occurrence date / time D607, the event occurrence date / time that triggered the health guidance is registered. Specifically, the date and time when the occurred event was registered in the instruction record database D6 by the event check process (M42) is registered.

  In the guidance content D608, a method in which this health guidance is implemented is registered.

  The title of the email used for this health guidance is registered in the email title D609, and the text of the email used for this health guidance is registered in the email body D610. If the health guidance is not performed by e-mail, no data is registered in the mail title D609 and the mail text D610.

  The state of health guidance is registered in the state D611. For example, “1” if this health guidance has not yet been implemented, “2” if this health guidance has already been implemented, and “3” if it is judged by the instructor that this health guidance will not be implemented. "Is registered in the state D611.

  Registered in the check result display flag D612 is a flag for designating whether to display the event check result on the instructor's screen or not. Specifically, “1” is displayed when the event check result is displayed on the instructor screen, and “2” is displayed when the event check result is not required to be displayed on the instructor screen. Registered in D612.

  FIG. 3 is a block diagram showing functional elements of the initial preparation processing means M1 of the present embodiment.

  The initial preparation process is executed in the server 400 when the health guidance support system according to the present embodiment is activated or when the health guidance support system according to the present embodiment is activated.

  In the initial preparation process, first, the server-side management means M10 starts an administrator authentication process, and authenticates access from the administrator terminal device 100 to the health guidance support system (M11).

  After successful authentication, the administrator terminal device 100 accesses the information registration processing unit M12, the basic setting processing unit M13, the mail service processing unit M14, and the weight loss recording data extraction unit M15.

  The information registration processing means M12 is a database management system that controls input / output of data to / from the database.

  The basic setting processing means M13 is divided into parameter setting processing means M16, priority order processing means M17, and user management means M18. The parameter setting processing means M16 registers a parameter for performing a condition determination described later in the parameter setting database D11. The priority processing means M17 sets or changes the priority of the meal menu and exercise menu presented to the participant, and registers it in the parameter setting database D11. The user management means M18 manages information of users (administrators, leaders, and participants) of the health guidance support system of the present embodiment using the leader management database D1 and the participant management database D4.

  The mail service processing means M14 controls event detection and e-mail reception based on the data of the regular event database D3.

  The weight loss recording data extraction means M15 reads information registered in the weight loss recording database D5 based on the information input by the participant, and provides it to the participant terminal device 300.

  FIG. 4 is a block diagram showing functional elements of the participation preparation processing means M2 of the present embodiment.

  The participation preparation process is a process of registering a participant who receives health guidance by the health guidance support system of the present embodiment from the leader terminal device 200.

  In the participation preparation process, first, the server-side management means is activated to prepare for various processes (M20). Next, a leader authentication process is activated to authenticate access to the health guidance support system from the leader terminal device 200 (M21).

  Thereafter, the participant process registration process is started, and the participant information (identifier: D401, name: D402 to weight: D409, etc.) is registered in the participant management database D4 of the server 400 (M22). Through the above processing, information on the participants who receive health guidance from the leader terminal device 200 is registered in the participant management database D4.

  FIG. 5 is a block diagram showing functional elements of the participant data input / browsing processing means M3 of the present embodiment. Participant data input / browsing processing means M3 is started when a participant or the like requests access to the weight loss recording database D5 of the server 400 via the participant terminal device 300.

  When the server 400 receives an access request for the weight loss recording database D5 from the participant terminal device 300 (or the leader terminal device 200) to the server 400, the server-side management unit M30 activates the participant authentication processing unit M31. The participant authentication processing means M31 of the server 400 is based on the information included in the access request and the information such as the ID and password D407 registered in the participant management database D4. Authenticate. When the authentication is completed, the server 400 specifies the identifier of the participant from the ID and password at the time of authentication, reads the participant data from the weight loss record database D5, and causes the participant terminal device 300 to display the data (individual weight loss record display). Means M32).

  In the participant terminal apparatus 300, the date, weight, and the implemented weight reduction menu (identifier) are input to the date D502, weight D503, and serial numbers D504 to D507, respectively, in the weight loss recording database D5 shown in FIG. Processing means M33). The server 400 writes the input received from the participant terminal device 300 in the weight loss recording database D5 (data registration processing means M34).

  FIG. 6 is a block diagram showing functional elements of the intervention guidance processing means M4 of the present embodiment.

  The intervention guidance process is a process of performing health guidance by the health guidance support system of the present embodiment.

  In the intervention guidance process, first, the server side management unit activates the event check processing unit (M42), and detects the occurrence of an event that requires action on the participant. Then, an intervention determination process (see FIG. 15) is activated to determine whether intervention (action) is necessary for the detected event (M48). The event processing result is registered in the instruction record database D6. Next, the server-side management means activates the leader authentication process, and authenticates access from the leader terminal device 200 to the health guidance support system (M41). Further, the event check result display processing means M43 (see FIG. 13) is activated, and the detected event is displayed on the instructor terminal device 200. The leader looks at the event check result display screen and determines the contents of health guidance for the detected event. Further, depending on the event, the mail transmission means is activated and an electronic mail is transmitted automatically or based on the instruction of the instructor (M47).

  Further, after the authentication is successful, a participant list display process (see FIG. 14) is activated, and a list of participants is displayed on the leader terminal device 200 (M44). The instructor can check the status of each participant by looking at the event check result display screen.

  Also, after successful authentication, the guidance record registration process is started, the guidance content registration screen is displayed on the leader terminal device 200, and the guidance content input from the leader (recording health guidance by telephone or fax) is accepted ( M46).

  Further, after the authentication is successful, the individual weight loss record display processing is started, the weight loss record of the participant is read from the weight loss record database D5, the individual weight loss record is displayed, and the status of each participant can be confirmed ( M45).

  FIG. 7 is a block diagram showing functional elements of the event processing means M5 of the present embodiment.

  The event processing means M5 is activated when the manager requests access to the regular event database D3 or the fixed phrase database D2 of the server 400 via the manager terminal device 100 (or the leader terminal device 200). To do.

  When the server 400 receives an access request from the administrator terminal device 100 (or the leader terminal device 200) for editing a regular event or editing a fixed phrase used for e-mail, the server-side management unit M50 of the server 400 The leader authentication processing means M51 is activated. The leader authentication processing means M51 verifies access by comparing information (for example, identifier and password) included in the access request with information registered in the leader management database D1.

  When the authentication is completed, the server 400 activates the fixed phrase editing processing means M52 if the access request is editing a fixed phrase, and starts the periodic event editing processing means M53 if the access request is a periodic event editing.

  The fixed phrase editing processing means M52 reads the phrase identifier D201, the title D202, and the body text D203 from the fixed phrase database D2, and transmits the read data to the administrator terminal device 100. The administrator terminal device 100 displays the content of the received fixed phrase database D2. Data input by the administrator is transmitted to the fixed phrase editing processing means M52 of the server 400. The fixed phrase editing processing means M52 registers the information received from the administrator terminal device 100 in the fixed phrase database D2.

  The periodic event editing processing means M53 reads the timing D302, the condition D303, the event contents D304, the mail wording identifier D305 and the instructor wording identifier D306 from the periodic event database D3, and transmits the read data to the administrator terminal device 100. To do. The administrator terminal device 100 displays the contents of the received periodic event database D3. Data input by the administrator is transmitted to the periodic event editing processing means M53 of the server 400. The periodic event editing processing means M53 registers the information received from the administrator terminal device 100 in the periodic event database D3.

  FIG. 16 is a flowchart of processing by the fixed phrase editing processing means M52 shown in FIG.

  The fixed phrase editing process is started when the server 400 receives a fixed phrase editing request from the administrator terminal device 100 (or the leader terminal device 200).

  First, the fixed phrase editing processing means M52 of the server 400 determines whether the fixed phrase editing request received from the administrator terminal device 100 is a fixed phrase edit request addressed to the participant or a fixed phrase edit request addressed to the instructor. It is determined whether it exists (M5201). As a result of the determination, if the edit request for the fixed phrase is a request for editing the fixed phrase addressed to the participant, the record whose sentence identifier D201 in the fixed phrase database D2 starts with “P” is selected, and the data of the selected record is selected. It transmits to the administrator terminal device 100 (M5202). Then, the fixed phrase editing processing means M52 sets the category of the fixed phrase addressed to the participant to “P” (M5203), and proceeds to step M5206.

  On the other hand, if the result of determination in step M5201 is that the request for editing the fixed phrase is a request for editing the fixed phrase addressed to the instructor, the record whose phrase ID (D201) in the fixed phrase database D2 starts with “S” is selected and selected. The data of the recorded record is transmitted to the administrator terminal device 100 (M5204). Then, the fixed phrase editing processing means M52 sets the category of the fixed phrase addressed to the instructor to “P” (M5205), and proceeds to step M5206.

  Next, the server 400 inquires whether to select a fixed phrase already registered in the fixed phrase database D2 (M5206). If a registered fixed phrase is selected as a response from the administrator terminal device 100 to this inquiry, the process proceeds to step M5209. If a registered fixed phrase is not selected, the process proceeds to step M5207 to newly register a fixed phrase. move on.

  In the case of new registration, the administrator terminal device 100 accepts input of a title and text, and sends the accepted information to the server 400 (M5207). Thereafter, the server 400 generates a serial number, adds the generated serial number to the category set in step M5203 or M5205, and generates a word identifier. Then, a new record is added to the fixed phrase database D2, and the identifier of the generated phrase is registered. Then, the server 400 registers the title and text received from the administrator terminal device 100 in the title D202 and text D203 of the fixed phrase database D2, respectively (M5208).

  On the other hand, in step M5206, when a registered fixed phrase is selected, the administrator terminal apparatus 100 is inquired whether or not to delete the registered fixed phrase. If the response from the administrator terminal device 100 to this inquiry is “delete”, the process proceeds to step M5213, and if the response is not “delete”, the process proceeds to step M5210 (M5209).

  In step M5210, the data of the selected fixed phrase is read from the fixed phrase database D2, and the read data is displayed on the administrator terminal device 100. The administrator terminal device 100 accepts changes to the title D202 and the text D203. Then, the identifier D201 of the wording is added to the changed title D202 and body D203, and transmitted to the server 400 (M5210).

  The server 400 determines whether to update the data received from the administrator terminal device 100 with the same identifier or to newly register with another identifier (M5211).

  If the result of this determination is new registration, a new word identifier and record are generated, and the word identifier D201, title D202 and text D203 are registered in a new record in the fixed phrase database D2 (M5208). On the other hand, if the determination result is a change, the edited title D202 and text D203 are registered in the record of the wording identifier D201, and the standard wording database D2 is updated (M5212).

  When deleting a fixed phrase, the record of the identifier of the selected phrase is deleted from the fixed phrase database D2 (M5213).

  Through the above processing, the administrator (or the instructor) can edit the fixed phrase database D2, and can create or update a desired message by classifying it into the instructor and the participants.

  FIG. 17 is a flowchart of processing by the periodic event editing processing means M53 shown in FIG.

  The periodic event editing process is started when the server 400 receives a request for editing a fixed phrase from the administrator terminal device 100 (or the leader terminal device 200).

  First, the periodic event editing processing means M53 of the server 400 is designated if the periodic event already registered in the periodic event database D3 is designated in the periodic event editing request received from the administrator terminal device 100. Proceed to step M5304 to update or delete the periodic event. On the other hand, if the registered regular event is not designated, the process proceeds to step M5302 to register the regular event for new registration.

  In the case of new registration, the administrator terminal device 100 receives input of timing, event contents, and conditions, and sends the received information to the server 400 (M5302). Next, the server 400 generates a serial number, and determines the event identifier from the generated serial number. Then, a new record is added to the periodic event database D3, and an event identifier D301 is registered (M5303). Then, the timing, event contents, and conditions received by the server 400 from the administrator terminal device 100 are registered in the timing D302, condition D303, and event contents D304 of the regular event database D3, respectively.

  On the other hand, if a registered regular event is specified in step M5301, the administrator terminal device 100 is inquired whether to delete the registered regular event. If the response to the inquiry is “delete”, the process proceeds to step M5308, and if the response is not “delete”, the process proceeds to step M5305 (M5304).

  In step M5305, the data of the designated regular event is read from the regular event database D3, and the read data is displayed on the administrator terminal device 100. The administrator terminal device 100 accepts changes in the timing D302, the condition D303, and the event content D304. Then, the event identifier D201 is added to the changed timing D302, condition D303, and event content D304, and the result is transmitted to the server 400 (M5305).

  The server 400 determines whether to update the data received from the administrator terminal device 100 with the same identifier or newly register with another identifier (M5306).

  If the result of this determination is new registration, a new event ID and record are generated, and the event identifier D301, timing D302, condition D303, and event content D304 are registered in the new record of the periodic event database D3. On the other hand, if the determination result is a change, the edited timing D302, condition D303, and event content D304 are written in the record of the event identifier D301 to update the periodic event database D3.

  When deleting a periodic event, the record of the event D identifier 301 designated from the instructor terminal device 200 is deleted in step M5308.

  Through the above processing, the instructor (or manager) can edit the regular event database D3 with the instructor terminal device 200 to arbitrarily set conditions and timing for transmitting or creating a desired message.

  FIG. 8 is a block diagram showing functional elements of the mail service processing means M14 of the present embodiment. The mail service processing means M <b> 14 is activated based on a request from the administrator terminal device 100 in order to control transmission / reception of electronic mail between the leader terminal device 200 or the participant terminal device 300 and the server 400.

  When the server 400 receives an access request for the mail service processing means M14 from the administrator terminal device 100, the access request starts activation of receiving mail (or issuing an event), stopping mail service (or issuing an event), or issuing an event. It is determined which is (M141). If the determination result is that the mail service is activated, the server 400 accepts input of the mail reception interval and event issue interval, and stores the input mail reception interval and event issue interval (M142). Next, the server 400 starts mail reception or event issuance (event check processing means M43) based on the set mail reception interval and event issuance interval (M143).

  On the other hand, when the server 400 accepts the stop of the mail service in M141, the server 400 stops receiving mail or issuing an event (event check processing means M43) (M144). If the access request from the administrator terminal device 100 is an immediate issue of an event in M141, the server 400 issues an immediate event regardless of the set mail reception interval and event issue interval (event check processing) Means M43) (M145).

  With the above processing, the server 400 controls the start and end of mail reception and event issuance (event check processing means M43 for managing mail transmission).

  FIG. 9 is a flowchart of processing by the priority order setting processing means M17 of this embodiment. The server 400 inquires of the leader terminal device 200 (or the administrator terminal device 100) about a category for setting or changing the priority order. The instructor terminal device 200 selects either the meal menu or the exercise menu, further selects the meal menu category D902 of the meal calorie database D9 or the exercise menu category D1002 of the exercise calorie database D10, and responds to the server 400 (M171). ).

  The server 400 receives a response from the instructor terminal device 200, and acquires a meal or exercise database and a category of the meal or exercise menu for setting priority from the response. The server 400 receives the priority order from the instructor terminal device 200 for the menu belonging to the category of the acquired type of database (M172). For example, when the meal calorie database D9 is selected as the database for setting the priority in the instructor terminal device 200, and “7” of the meal menu category D902 is selected as the category, the server 400 sets the “main dish” of the meal calorie database D9. The meal menu name D903 and the priority order D904 are provided to the instructor terminal device 200, and an input to the meal priority order D904 is received.

  When the input of the priority order is completed, the server 400 inquires of the leader terminal device 200 whether or not to reflect the received priority order in the database (M173). If there is a response “YES” from the instructor terminal device 200 in response to this inquiry, the server 400 reflects the priority input in the above M172 in the database (M174). On the other hand, if there is a “NO” response from the instructor terminal device 200 to the inquiry, the server 400 discards the priority input in M172 and ends.

  Through the above processing, the menu priorities of the meal calorie database D9 and the exercise calorie database D10 can be arbitrarily set or changed by the instructor for each category of the database, and participants' habits, thoughts, age, gender Or the priority of a meal menu or an exercise menu can be set according to the implementation condition of a meal menu or an exercise menu (weight reduction menu).

  In M172, an example in which a leader or the like inputs priority is shown. However, the server 400 sets a plurality of priority setting patterns, selects a pattern from the leader terminal device 200 or the like, and selects the server 400. May be ranked according to the pattern. For example, the exercise menu of the exercise calorie database D10 includes a setting pattern in which the server 400 ranks the exercises in ascending order of exercise time. Further, the server 400 may rank the meal calorie database D9 and the exercise calorie database D10 in descending order of the weight loss effect from the past weight loss recording database D5. For example, the server 400 extracts the identifier of the participant who has achieved the target weight D1204 within the weight loss period D1205 of the individual weight loss target database D12 from the weight loss recording database D9, and performs the weight loss menu (exercise menu) performed by the extracted participant. Or the meal menu) may be extracted from the serial numbers D504 to D507, and the priority order may be assigned in the order of the extracted appearance frequency. Alternatively, the server 400 extracts the weight reduction menu executed from the serial numbers D504 to D507 of the weight loss recording database D9, obtains the implementation rate of each menu for each category of the weight reduction menu, and ranks the weight reduction menu in descending order of the implementation rate. May be assigned.

  Here, as the implementation rate of the weight loss menu, the serial number 803 corresponding to the meal menu identifier D804 or the life improvement item exercise menu identifier D805 of the individual program database D8 shown in FIG. 24 is acquired. Then, in the weight loss recording database D5 shown in FIG. 35, the number of appearances in which the values of the serial numbers D504 to D507 that match the acquired serial number D803 are already executed is acquired, and the number of records of the identifier D501 of the participant is reduced. A value obtained from D5 and obtained by dividing the number of appearances by the number of records is the implementation rate of the weight reduction menu set in the individual program database D8. By determining the implementation rate for each meal menu identifier D804 or the lifestyle improvement item exercise menu identifier D805 in the individual program database D8, the implementation rate for each weight reduction menu set by the participant can be determined.

  Furthermore, after the priority order of the weight reduction menu is assigned by the server 400 in the predetermined pattern as described above, the priority order assigned to the weight reduction menu from the leader terminal device 200 or the like may be corrected.

  FIG. 10 is a flowchart of processing by the participant registration processing means M22 of the present embodiment.

  In the participant registration process, first, the leader terminal device 200 accepts input of basic information, measurement information, and system information of a participant. At this time, a participant registration screen is displayed on the leader terminal device 200, and the leader inputs necessary items (221). Information input to the leader terminal device 200 is transmitted to the server 400 and registered in the participant management database D4 (222).

  Next, the server 400 reads out the inquiry information from the inquiry information database D12 and transmits it to the participant terminal apparatus 300. Note that the contents of the interview to be read may be selected based on the participant information input in step 222. For example, the contents of the interview can be selected based on the gender of the participant, the current weight, and the like.

  The participant terminal device 300 displays the received inquiry information (223). Participant terminal device 300 receives an input of an answer to the inquiry. At this time, an inquiry answer input screen is displayed on the participant terminal device 300, and the participant inputs an answer to the inquiry (224). The answer input to the participant terminal device 300 is transmitted to the server 400 and registered in the inquiry result database D7 (225).

  If the weight reduction menu is set without receiving an inquiry, the process proceeds to step 226 without executing the processes in steps 223 to 225.

  Next, the server 400 sends information necessary for setting the weight loss program to the participant terminal device 300. At this time, an individual program setting screen (see FIG. 28) is displayed on the participant terminal device 300, and the participant inputs information necessary for creating a weight loss program (target weight, weight loss start date and weight loss implementation period). . The information input to the participant terminal device 300 is transmitted to the server 400 and registered in the individual weight loss target database D12 (226).

  The server 400 calculates a calorie target to be reduced per day from the set information, and sends the calculated target calorie to the participant terminal device 300. The participant terminal device 300 displays the target calorie transmitted from the server 400 on the individual program setting screen (227).

  Furthermore, the server 400 refers to the information registered in the inquiry result database D7, and extracts items to be selected as the weight loss menu from the meal calorie database D9 and the exercise calorie database D10. Then, the server 400 sends the extracted meal menu and exercise menu to the participant terminal device 300. The participant terminal device 300 displays the weight loss menu (meal menu and exercise menu) transmitted from the server on the individual program setting screen (228).

  The participant terminal device 300 accepts the selection of the weight reduction menu (229). At this time, the participant may select a plurality of the same menus. The selected weight loss menu is transmitted to the server 400 and registered in the individual program database D8 (230).

  The server 400 calculates the target calorie and extracts the weight loss menu to be presented. In step 226, the participant terminal device 300 does not send the information necessary for creating the weight loss program to the server 400 in step 226. Calculation of the target calorie and extraction of the presented weight loss menu may be performed. In this case, in step 230, information is registered in the individual weight loss target database.

  FIG. 39 is an explanatory diagram showing an example of an individual program registration screen provided by the server 400 to the participant terminal device 300.

  The individual program setting screen is displayed on the display or the like of the participant terminal device 300, and the participant uses this screen to set the weight reduction menu.

  The start weight is displayed on the individual program setting screen. In addition, the individual program setting screen is provided with input fields for a target weight, a weight reduction start date, and a weight reduction implementation period. The individual program setting screen is provided with display fields for weight after weight loss and calories per day to be reduced. In addition, on the individual program setting screen, a weight reduction menu (meal menu and exercise menu) is displayed in a card format, an operation button for displaying a recommended weight reduction menu, and a display field for the selected weight reduction menu. Provided.

  As shown in FIG. 39, at the time of initial display, the starting weight input in the participant registration (221 in FIG. 10) is displayed.

  Thereafter, when the participant inputs the target weight, the weight reduction start date, and the weight reduction implementation period, the weight after weight loss and the daily calories to be reduced are calculated, and the calculation result is displayed.

  Further, a weight reduction menu is displayed on the card CD (lower right of FIG. 39, meal and exercise column). In this weight loss menu, one card CD is set to a predetermined calorie (for example, 100 kcal). This weight loss menu is displayed separately for meals and exercises, and further, meals are classified into staple foods, fruits, snacks, etc., and exercises are classified into walks / runs, sports, etc. and displayed.

  Further, since the calorie consumption changes depending on the weight of the participant, an exercise menu of exercise time according to the exercise time calculated based on the weight of the participant is displayed. In this way, since the weight loss menu in which the exercise time is calculated based on the participant's weight is presented to the participant, there is no need to calculate the exercise time according to the individual weight as in the past, and the work of the instructor Can be reduced.

  The participant selects the displayed weight loss menu with reference to the calculated daily calories to be reduced.

  When the participant selects the weight loss menu, as shown in FIG. 39, a list of the selected weight loss menus is displayed in a predetermined display field, calories that are reduced by the selected card are calculated, and the calculated calories are displayed. Is done.

  The weight loss menu has one card set to a predetermined calorie, so that no matter what weight loss menu the participant chooses, if the same number of weight loss menus are selected, the desired weight loss goal will be achieved Can do.

  In the initial state, the weight reduction menu list is set so that the meal amount is reduced in the meal menu and the exercise amount is increased in the exercise menu, but the increase / decrease for each menu can be changed. For example, depending on the combination of weight reduction menus selected, the high-calorie (low meal amount corresponding to 100 kcal) meal menu is reduced by X, and the low-calorie (high meal equivalent of 100 kcal meal) menu is increased by Y. . At this time, by setting X> Y, it is possible to create a weight loss program that reduces calories in total, and the range of options for the user can be expanded.

  Also, if you are unsure of the weight loss menu selection, you can configure a weight loss program that suits your individual by selecting the recommended menu button and based on the previously entered interview results (225 in FIG. 10). it can. Since the weight loss menu is preferentially displayed from the category that the participant himself / herself indicates as a goal, the card that can be executed by the participant can be easily selected. Editing of the recommended program can also be performed using the card CD (lower right of FIG. 39, meal and exercise column).

  Finally, by operating the “OK” button, the input information is transmitted to the server 400 and registered in the individual program database D8.

  FIG. 11 shows a time chart of the selection of the weight reduction menu (steps 226 to 230) shown in FIG.

  The participant terminal apparatus 300 requests the server 400 for the individual program registration screen shown in FIG. 28 (1101). The server 400 authenticates the participant who uses the participant terminal device 300 as described above, and specifies the identifier of the participant, and then outputs an individual program registration screen corresponding to the authenticated participant (1102). ).

  In the participant terminal device 300, the participant inputs a target weight, a weight reduction start date, and a weight reduction period on the individual program registration screen displayed on the display or the like (1103).

  When the server 400 receives the target weight, the weight reduction start date, and the weight reduction execution period from the participant terminal device 300, the server 400 achieves the target weight within the weight reduction execution period from the weight registered in the participant management database D4 in advance. Then, the target weight reduction calorie number per day is calculated and output to the individual program registration screen (1104). In the example of FIG. 28, it is necessary to reduce 311.1 kcal per day. Next, the server 400 outputs the weight loss menu card CD to the individual program registration screen according to the priority order for each of the meal menu and the exercise menu based on the target weight loss per day. The presentation of the card CD of the weight reduction menu is based on the result of the inquiry conducted in advance, and the server 400 extracts and outputs the menu with the highest priority from the categories that the participant himself / herself has indicated as the weight reduction target. For example, when the participant selects “7” in the meal menu category D902 and selects “3” in the exercise menu category D1002 as an answer to the inquiry, the server 400 sets the meal menu category D902 in the meal calorie database D9 to “7”. ”Outputs the meal menu name D903 to the individual program registration screen in ascending order of the meal priority order D904, and the exercise menu name D1003 in the ascending order of the exercise priority order D1004 when the exercise menu category D1002 of the exercise calorie database D10 is“ 3 ”. Output to another program registration screen.

  In the example of the individual program registration screen of FIG. 28, the meal menu and the exercise menu can each display six card CDs, and therefore the server 400 displays the top six meal menus in the priority order D904 from the meal calorie database D9. The name D903 is output, and the top six exercise menu names D1003 of the exercise priority order D1004 are output from the exercise calorie database D10.

  Further, the menu names D903 and D1003 having the highest priority D904 and D1004 of the meal menu and exercise menu are output as “weekday improvement items” in FIG.

  A participant who operates the participant terminal device 300 selects a card CD of 100 kcal from the meal menu or the exercise menu so as to be equal to or more than the target weight loss per day output on the individual program registration screen (1106). ). This selection is performed by clicking a check box provided at the upper left of each card CD, and the server 400 calculates the total amount of heat of the selected card CD to obtain the “current energy difference” in FIG. Output. Then, after selecting the number of card CDs necessary for the target number of calories to be reduced per day, the participant presses the “OK” button shown in FIG. 28 on the participant terminal device 300 (1107). When the determination button is pressed, the server 400 sets the weight loss menu identifier (meal menu identifier D901 or exercise menu identifier D1001) selected by the participant terminal device 300, the target weight, the weight loss start date, and the weight loss implementation period for each individual program. Register in the database D8 (1108, 1109).

  As described above, since the server 400 presents the meal menu and exercise menu with high priority from the category of the weight reduction menu that the participant has answered as the target in the answer to the inquiry, the weight reduction menu that is easy for the participant to display is displayed. Can do. For this reason, a participant can determine a weight loss menu without an instructor intervening.

  FIG. 12 is a flowchart of processing by the event check processing means M42 of this embodiment.

  The event check process is a process for determining whether data input by a participant matches a predetermined condition and extracting an event.

  In the event check process, first, information on all periodic events to be extracted is acquired from the periodic event database D3 (4201).

  Thereafter, the processing of loop 1 in steps 4202 to 4215 is entered. That is, in step 4202, after the counter 1 (Count 1) = 1 is initialized, the process of loop 1 up to step 4215 is repeatedly executed while the value of the counter 1 is equal to or less than the number of extracted periodic events.

  In the loop 1, information on all participants is acquired from the participant management database D4 (4203).

  Thereafter, the processing of loop 2 in steps 4204 to 4213 is entered. That is, in step 4204, after the counter 2 (Count2) = 1 is initialized, the process of loop 2 up to step 4213 is repeatedly executed while the value of the counter 2 is equal to or less than the number of participants from which the participant data has been acquired. To do.

  In the loop 2, the timing D302 acquired from the regular event database D3 is compared with the number of days elapsed and / or the weight loss period from the weight reduction start date of the participant. Then, a participant whose timing condition matches is identified (4205).

  Thereafter, it is determined whether or not the detection condition D303 of the periodic event in which the participant is specified is “none” (4206). As a result, if the detection condition D303 for the periodic event is “none”, the event is detected without attaching any conditions other than the timing, so the mail corresponding to the identifier registered in the identifier D305 of the participant mail wording The text is read from the fixed phrase database D2, and a sentence to be notified to the participant is created. At this time, a keyword (for example, name) included in the read word is replaced so as to be suitable for the participant (4207).

  On the other hand, if the periodic event detection condition D303 is not “None”, the periodic event detection condition D303 is compared with the participant's weight loss target to determine whether or not the leader needs to intervene (4208). Proceed to, and based on the result of the intervention determination, create a sentence to be notified to the participants.

  Next, the fact that a periodic event has been detected is registered in the instruction record database D6 (4209). At this time, “1” (indicating that the health guidance is not yet implemented) is registered in the state D611 of the guidance record database D6.

  Next, it is determined whether or not the event content D304 of the periodic event database D3 is “automatic mail transmission” (4210). As a result, if the event content D304 is “automatic mail transmission”, the mail addressed to the participant is transmitted (4211), and “2” (indicating that health guidance has already been implemented) is registered in the state D611. Is done. Thereafter, the process proceeds to step 4213 to exit from the loop 2.

  On the other hand, if the event content D304 is “automatic mail transmission”, the health guidance is performed after the judgment by the instructor, so that the process proceeds to step 4212 and the counter 2 is incremented to process the next participant ( 4212). If the value of the counter 2 exceeds the number of participants from which the participant data has been acquired, the event check processing has been completed for all the participants, so the process proceeds to step 4214 and the loop 2 is exited. On the other hand, if the value of the counter 2 is equal to or less than the number of participants from which the participant data has been acquired, there is a participant who has not finished the event check process, and the process returns to step 4204.

  In step 4214, the counter 1 is incremented to process the next periodic event. If the value of the counter 1 exceeds the number of extracted periodic events, the event check process is completed for all the regular events, and the event check process is terminated. On the other hand, if the number of the periodic events from which the value of the counter 1 is extracted is equal to or smaller than the above, there is a periodic event for which the event check process has not been completed, and the process returns to step 4202.

  With the above processing, it is possible to automatically determine whether or not the weight loss of the participant is proceeding as scheduled by an event for checking the weight loss status of the participant every predetermined period. In addition, with regard to the implementation status of the weight reduction menu, it is possible to automatically determine whether or not the participant is steadily executing the weight reduction menu based on an event that determines that the preset weight reduction menu implementation rate has fallen below a predetermined threshold. .

  FIG. 13 is a flowchart of the processing by the event check result display processing means M43 of this embodiment.

  The event check result display process is a process of displaying the detected event on the leader terminal device 200 and changing the state of the event.

  In the event check result display process, first, event data for which the check result display flag of the instruction record database D6 is “1” is acquired from the instruction record database D6, and the acquired data is transmitted to the instructor terminal device 200 (431). ).

  When receiving the data, the leader terminal device 200 displays the event data (432). The contents of the event displayed on the event check result display screen (not shown) are as follows by referring to the fixed phrase database D2 using the instructor wording identifier D306 registered in the periodic event database d3 of the detected event. The content to be displayed on the event check result display screen is acquired from D203.

  At this time, the check result display flag D612 can be changed by changing the display state between “not yet” and “done”. At this stage, the change of the check result display flag D612 is not registered in the instruction record database D6. Thus, since the display state of the event can be changed, an event that requires an action by the instructor can be selected and displayed.

  Thereafter, it is determined whether or not the “Done Delete” button has been operated (434). If the operation of the “Done Delete” button is detected, the event whose display state has been changed to “not yet” is deleted from the screen. Then, the changed check result display flag is registered in the instruction record database D6 (435).

  FIG. 14 is a flowchart of processing by the participant list display processing means M44 of this embodiment.

  The participant list display process is a process for displaying participant information on the leader terminal device 200.

  In the participant list display process, first, the name, sex, age, elapsed days, weight, etc. of the participant in charge of the instructor are acquired from the weight loss recording database D5 (441). Thereafter, a record of the intervention guidance of the participant is acquired from the guidance record database D6 (442). Thereafter, the participants are sorted according to preset priorities (date, elapsed days, goal achievement status, etc.) and displayed in a list format (443).

  FIG. 15 is a flowchart of intervention determination processing 4208 by the intervention determination processing means M48 of the present embodiment.

  The intervention determination process 4208 is a process for determining whether or not an event having the same detection timing matches the detection condition.

  In the intervention determination process 4208, first, the number of improvement implementation items of the participant is acquired from the individual-specific program database D8 (481).

  Next, the current weight D503 registered in the weight loss recording database D5 is subtracted from the starting weight D409 registered in the participant management database D4, and the current weight loss (at the time of intervention determination) is calculated (482).

  Then, the value obtained by dividing the weight loss by the number of improvement items is compared with the parameter set in the parameter setting database D11 (483). As a result, if the value obtained by dividing the weight loss by the number of improvement items is equal to or less than the preset parameter, the intervention determination is determined to be “OK” (484).

  FIG. 18 is a flowchart showing detailed processing of the weight reduction menu display processing in step 228 among the processing by the participant registration processing means M22 shown in FIG.

  First, the server 400 determines whether or not the participant terminal device 300 has selected a recommended weight reduction menu (“Recommended Menu” button in FIG. 31) (2401). If the participant selects the recommended menu, the process proceeds to step 2402. On the other hand, if the participant does not select the recommended menu, the meal menu displayed on the individual program registration screen of FIG. 28 or FIG. The weight reduction menu is selected from the exercise menu (2410).

  In step 2402, the parameter set in the parameter setting database D11 is acquired.

  Next, according to the priority order indicated by the parameter acquired from the parameter setting database D11, a meal menu is acquired from the meal calorie database D9 (2403), and an exercise menu is acquired from the exercise calorie database D10 in order of priority (2404).

  Next, an identifier D701 of an inquiry that is indicated as “target” in the improvement implementation target D705 is extracted from the inquiry result database D7 (2405). Thereafter, the server 400 refers to the interview identifier D1301 of the interview information database D13 with the interview identifier D701, and acquires the interview category targeted by the participant from the meal menu category D1302 and the exercise menu category D1303 of the interview information database D13. (2406).

Menus that belong to the category that matches the items targeted as the improvement implementation target D705 from the acquired meal menu category D1302 and exercise menu category D1303 are acquired from the meal calorie database D9 and the exercise calorie database D10 in order of priority D904 and D1004. (2407). The above step 2407 is repeated until the value obtained by multiplying the number of acquired menus by 100 kcal is equal to or greater than the target number of weight loss per day (2408). If the value obtained by multiplying the number of acquired menus by 100 kcal is equal to or greater than the target number of weight loss per day, the server 400 sets the acquired meal menu name D903 and exercise menu name D1003 in the order of priority D904 and D1004. It is transmitted to the participant terminal device 300 and displayed on the individual program registration screen (FIG. 28) (2409). Then, the process proceeds to step 2410 to wait for a menu to be selected from the individual program registration screen (2410).
In step 2407 above, the menu acquisition category may be referred to alternately in the meal calorie database D9 and the exercise calorie database D10. Moreover, you may make it refer to a category in the order with the high possibility of the implementation implementation questionnaire of an inquiry item.

  With the above processing, when there are many meal and exercise weight loss menus, it is possible to refer to answers to the inquiry information and present weight loss menus suitable for the participants according to preset priorities. In the flowchart of FIG. 18, the determination process is performed in step 2401, but step 2402 and subsequent steps may be executed when the “recommended menu” button in FIG. 31 is clicked. In particular, by extracting the weight loss menu from the meal calorie database D9 and the exercise calorie database D10 in descending order of the priority rankings D904 and D1004, the priority ranking D904 is reached until the total number of calories in the weight loss menu reaches a predetermined value. Thus, it is possible to extract a weight reduction menu having a high D1004, and the weight reduction menus to be presented to the participant terminal device 300 are arranged in descending order of priority set in advance. Thereby, the weight reduction menu suitable for each participant can be easily provided from a large number of weight reduction menus (meal menu and exercise menu), and the labor of the instructor can be reduced.

  The weight reduction menu may be output to the participant terminal device 300 in the order of priority D904 and D1004, and may be sorted by the server 400 or may be sorted by the participant terminal device 300.

  FIG. 19 is a time chart showing a processing procedure for displaying the weight reduction menu shown in FIG.

  First, the participant terminal device 300 selects a recommended menu from the individual program registration screen and transmits it to the server 400 (1901).

  The server 400 receives the selection of the recommended menu from the participant terminal device 300, and acquires the parameters set in the parameter setting database D11 (1902).

  Next, the parameter setting database D11 acquires a parameter related to the recommended menu and responds to the server 400 (1903). The server 400 analyzes the parameters of the recommended menu acquired from the parameter setting database D11, and determines whether the recommended menus are displayed in order of priority or in random order (1904). Hereinafter, description will be given in the order of priority.

  Next, the server 400 acquires a meal menu from the meal calorie database D9 according to the priority order indicated by the parameters acquired from the parameter setting database D11 (1905, 1906), and acquires an exercise menu from the exercise calorie database D10 according to the priority order. (1907, 1908).

  Next, the server 400 extracts the identifier D701 of the inquiry that is indicated as “target” in the improvement implementation target D705 in the inquiry result database D7 (1909). The inquiry database D7 returns an inquiry identifier D701 in response to the inquiry from the server 400 (1910).

  The server 400 then inquires of the inquiry information database D13 about the inquiry category (meal menu category D1302 and exercise menu category D1303) of the identifier D701 extracted from the inquiry result database D7 (1911). The inquiry information database D13 specifies the meal menu category D1302 and the exercise menu category D1303 corresponding to the inquiry identifier D701 and responds to the inquiry from the server 400 (1912).

  The server 400 selects a menu belonging to a category that matches the item targeted as the improvement implementation target D705 from the specified meal menu category D1302 and exercise menu category D1303, from the meal calorie database D9 and the exercise calorie database D10, the priority order D904, Obtained in the order of D1004 (1913).

  As shown in step 2408 of FIG. 18, the server 400 repeats the process of step 1913 until the total amount of heat of the acquired menu becomes equal to or more than the target number of calories reduced per day (1914). When the total amount of heat of the acquired menu becomes equal to or greater than the target number of calories reduced per day, the server 400 ends the acquisition of the menu (1914).

  Then, the server 400 transmits the menu name acquired up to step 1914 to the participant terminal device 300 as a weight reduction menu (1915), and the participant terminal device 300 displays the weight reduction menu candidates on the individual program registration screen. The participant performs the selection (1916).

  FIG. 20 is a flowchart showing a modification example of the weight reduction menu display process performed in the weight loss menu display in step 228 of FIG. 10 and the weight loss menu display in step 2409 of FIG. In this example, regarding the exercise menu, an appropriate exercise time according to the weight of the participant is presented.

  First, the server 400 determines whether or not the exercise menu is included in the weight loss menu (card) to be displayed. If the exercise menu is included, the process proceeds to step 24902, and if only the meal menu, the process proceeds to step 24911. When both the exercise menu and the meal menu are included, step 24902 and the subsequent steps and step 24911 may be executed once.

  In step 24902, the server 400 acquires the weight and sex of the participant from the participant management database D4. Based on the exercise menu identifier D1001 to be displayed from the exercise calorie database D10, exercise menu base weight (male) D1006, exercise menu 100kcal consumption time (male) D1007, exercise menu base weight (female) D1008, exercise menu 100kcal Consumption time (female) D1009 is acquired.

Next, steps 24904 to 24909 loop until the number of exercise menus to be displayed. First, the number of calories consumed by the participant per minute per kilogram of body weight is calculated as calorie kg / min (calorie consumption per minute per kilogram of body weight) (24905). In this calculation, since the calorie consumption of each exercise menu is 100 kcal, the gender of the target participant is determined, and if it is a male, the weight of the participant is determined based on the exercise menu base weight (male) D1006 and the exercise menu. From 100kcal consumption time (male) D1007, calorie kg / min by the following formula,
Calorie kg / min = 100 / (Exercise menu base weight (male) x exercise menu 100kcal consumption time (male))
Calculate from. When the participant is a woman, the exercise menu base weight (female) D1008 and the exercise menu 100 kcal consumption time (female) D1009 may be used.

Next, the server 400 calculates calorie consumption by weight (24906). The calorie consumption by body weight is the weight multiplied by the calorie kg / min.
Determined from the weight of the participant x calories consumed per minute per kg of body weight.

Next, based on the calorie consumption by weight, when the exercise menu currently focused on is performed with the weight of the participant, the exercise time required to consume 100 kcal is calculated as the exercise time by weight ( 24907). Exercise time by weight
It can be calculated from 100 / calorie consumption calorie.

  By the above, the exercise time according to body weight according to the sex and weight of a participant can be calculated | required about one exercise menu.

  In steps 24908 and 27909, the exercise time by weight is obtained for all exercise menus to be displayed, and stored in the storage device or memory of the server 400. Then, the exercise time by weight and the exercise menu name obtained for all exercise menus are transmitted to the participant terminal device 300.

  On the other hand, when the weight loss menu to be displayed is a meal menu, the meal menu name D903 may be acquired from the meal calorie database D9 and transmitted to the participant terminal device 300 as described above.

  As described above, it is possible to display the exercise menu execution time according to the gender and weight of the participant.

  FIG. 29 is a flowchart showing an example of processing for displaying either the weekday recommended menu or the holiday recommended menu as the exercise menu, showing a modification of FIG. As shown in FIG. 28, the weight reduction menu displayed on the individual program registration screen displays different contents for the weekday recommended menu and the holiday recommended menu. In the example of FIG. 28, buttons for “recommended menu for weekdays” and “recommended menu for holidays” are provided. Different programs (card CD) may be selected for weekdays and holidays.

  Pressing the "Weekday recommended menu" will display programs that are suitable for individuals from programs that can be played even on days when there is no time such as weekdays. When the “Holiday Recommendation Menu” is pressed, programs suitable for individuals are displayed from programs that can be performed when there is time on holidays and holidays.

Mainly, the program that changes recommendations on weekdays / holidays is an exercise program (or a meal program)
.

  In the following example, processing when the “weekday recommended menu” shown in FIG. 28 is selected will be described.

  First, the server 400 determines whether or not the participant terminal device 300 has selected the “weekday recommended menu” (2901). If the participant selects “Weekday recommended menu”, the process proceeds to step 2902. On the other hand, if the participant does not select “Weekday recommended menu”, the program is displayed on the individual program registration screen of FIG. The weight loss menu is selected from the meal menu and exercise menu (2913).

  In step 2902, the server 400 acquires the parameters set in the parameter setting database D11.

  Next, according to the priority order indicated by the parameters acquired from the parameter setting database D11, a meal menu is acquired from the meal calorie database D9 (2903), and an exercise menu is acquired from the exercise calorie database D10 in order of priority (2904).

  Here, in the exercise calorie database D10, a flag for identifying the weekday recommended menu and the holiday recommended menu is set in the content shown in FIG. 27, and the weekday / holiday category D1010 is set in advance as shown in FIG. Set it. In the example of FIG. 30, a weekday / holiday category D1010 value of “0” indicates a weekday recommended menu, and “1” indicates a holiday recommended menu.

  In step 2904, an exercise menu is acquired from a record in which the weekday / holiday category D1010 is “0”.

  Next, the server 400 extracts from the inquiry result database D7 the inquiry identifier D701 that is indicated as “target” in the improvement implementation target D705. Thereafter, the server 400 refers to the interview identifier D1301 of the interview information database D13 with the interview identifier D701, and acquires the interview category targeted by the participant from the meal menu category D1302 and the exercise menu category D1303 of the interview information database D13. (2905).

  Next, in steps 2906 to 2911, the total number of meal menu categories D1302 and exercise menu categories D1303 acquired in step 2905 is set as the improvement target number, and the number of loops (value of variable Count) reaches the improvement target number or The loop is repeated until the number of calories in the weight loss menu acquired in the loop is equal to or greater than the target number of weight loss per day obtained in step 1104 in FIG.

  In step 2907, the menus belonging to the category that matches the item targeted as the improvement implementation target D705 from the acquired meal menu category D1302 and exercise menu category D1303 are assigned priority levels D904 and D1004 from the meal calorie database D9 and exercise calorie database D10. Get in order.

  In step 2908, 100 kcal is added to the variable CalCnt every time a weight loss menu is acquired from either the meal calorie database D9 or the exercise calorie database D10.

  In step 2909, if the value of the variable CalCnt is equal to or more than the target number of calories reduced per day obtained in step 1104, the loop is terminated and the routine proceeds to step 2911. On the other hand, if the value of the variable CalCnt is less than the target weight reduction calorie number per day, in step 2910, 1 is added to the value of the variable Count for counting the total number of weight loss menus, and then the process returns to step 2906 to loop. repeat.

  When the loop of steps 2906 to 2911 is completed, the contents of the category weight reduction menu (meal menu name D903, exercise menu name D1003 and the amount or time) that the participant sets as the improvement target number are the meal calorie database D9 and the exercise calorie database D10. Extracted from

  In step 2912, the server 400 transmits the extracted weight loss menu to the participant terminal device 300 in the order of priority D904 and D1004, and the participant terminal device 300 can select a weight loss menu suitable for weekday exercise. Yes (2913).

  In the above description, the processing when the “Weekday recommended menu” is selected is shown. However, when the “Holiday recommended menu” is selected, in the above step 2904, the weekday / holiday category D1010 is “1”. You can get an exercise menu from.

  Through the above processing, a predetermined weight loss can be effectively performed while changing the exercise menu performed on weekdays and the row exercise menu on holidays.

  In the flowchart of FIG. 29, the determination process is performed in step 2901. However, when the “weekday recommended menu” button in FIG. 28 is clicked, step 2902 and subsequent steps may be executed.

  FIG. 31 is a screen in which a “recommended menu” button is set in place of the weekday recommended menu and holiday recommended menu on the individual program registration screen shown in FIG. 28, and a check box for selecting the recommended menu is added. It is. Others are the same as those in FIG. The recommended menu display column shows an increase in walking and a reduction in canned beer as improvement items on weekdays. In the recommended menu display field, for each improvement item (weight reduction menu), a check box CX is provided that allows the participant to cancel the recommended menu item.

  The check box CX can be written or canceled by the participant terminal device 300. When the check box CX is incorporated as a weight reduction program performed by the participant, the check is written. If the check box CX is not checked, the server 400 can determine that the recommended menu has been rejected.

  FIG. 32 is a flowchart showing an example of processing for displaying a weight reduction menu on the individual program registration screen shown in FIG.

  First, the server 400 outputs a “recommended menu” to the individual program registration screen shown in FIG. 31 by the participant terminal device 300 (3201). Next, the notification that the check box CX is released is received from the participant terminal device 300. Then, it is determined whether or not the participant has selected the “recommended menu” on the participant terminal device 300 (3203). If “recommended menu” is selected, the process proceeds to step 3204. On the other hand, if the participant does not select “recommended menu”, the meal menu displayed on the individual program registration screen of FIG. A weight reduction menu is selected from the exercise menu (3216).

  In step 3204, the server 400 acquires the parameters set in the parameter setting database D11.

  Next, according to the priority order indicated by the parameters acquired from the parameter setting database D11, a meal menu is acquired from the meal calorie database D9 (3205), and an exercise menu is acquired from the exercise calorie database D10 in order of priority (3206).

  Next, the server 400 extracts from the inquiry result database D7 the inquiry identifier D701 that is indicated as “target” in the improvement implementation target D705. Thereafter, the server 400 refers to the interview identifier D1301 of the interview information database D13 with the interview identifier D701, and acquires the interview category targeted by the participant from the meal menu category D1302 and the exercise menu category D1303 of the interview information database D13. (3207).

  Next, the server 400 excludes the category of the recommended menu in which the check box CX is unchecked in the step 3202 from the categories acquired in the step 3208.

  Next, in steps 3209 to 3214, the total number of meal menu categories D1302 and exercise menu categories D1303 obtained in step 3205 is set as the improvement target number, and the number of loops (value of variable Count) reaches the improvement target number or The loop is repeated until the number of calories in the weight loss menu acquired in the loop is equal to or greater than the target number of weight loss per day obtained in step 1104 in FIG.

  In step 3210, the menus belonging to the category that matches the item targeted as the improvement implementation target D705 from the acquired meal menu category D1302 and exercise menu category D1303 are assigned priority levels D904 and D1004 from the meal calorie database D9 and exercise calorie database D10. Get in order.

  In step 3211, 100 kcal is added to the variable CalCnt every time a weight loss menu is acquired from either the meal calorie database D9 or the exercise calorie database D10.

  In step 3212, if the value of the variable CalCnt is equal to or greater than the target weight loss per day calculated in step 1104, the loop ends and the process proceeds to step 3214. On the other hand, when the value of the variable CalCnt is less than the target weight reduction calorie number per day, in step 3213, 1 is added to the value of the variable Count for counting the total number of weight reduction menus, and then the process returns to step 3209 to execute the loop. repeat.

  When the loop of the above steps 3209 to 3214 is completed, the contents of the weight reduction menu (meal menu name D903, exercise menu name D1003 and amount or time) of the category that the participant sets as the improvement target number are the meal calorie database D9 and the exercise calorie database D10. Extracted from

  In step 3215, the server 400 transmits the extracted weight loss menu to the participant terminal device 300 in the order of priority D904 and D1004, and the participant terminal device 300 can select a weight loss menu suitable for weekday exercise. (3216).

  The categories excluded by the participant from the recommended menu by the above processing are excluded from the weight reduction menu, so that the weight reduction menu according to the participant's habits and preferences can be displayed.

  FIG. 33 is a flowchart showing another example of processing for displaying a weight reduction menu on the individual program registration screen shown in FIG.

  The process of FIG. 33 shows the process of presenting the recommended menu again when changing the weight loss menu to be registered when the implementation rate of the weight loss menu is poor.

  As a person who changes the weight loss menu, the target review time is set in advance every arbitrary number of days, and the participant can not clear the target weight of the day continuously any number of times during the target review time (Or if a continuous weight loss menu is not being implemented), the server 400 sends an alert email regarding the participant to the instructor in charge. When the instructor receives the alert mail, the instructor transmits a weight change menu change (or addition) mail to the corresponding participant and enters the weight loss menu change procedure.

  When changing the weight reduction menu in the middle of weight reduction, the weight loss menu with a poor implementation rate belongs to a category other than the category to which the weight reduction menu with a low implementation rate belongs, so that the weight loss menu with a poor implementation rate is changed among the registered weight reduction menus of participants. Present a recommended menu. This weight reduction menu presentation process will be described below.

  First, the participant terminal device 300 receives an e-mail that encourages a change in the weight reduction menu (3401). The participant terminal device 300 accesses the server 400 using the participant identifier (3402). The server 400 uses the identifier of the participant who received the access, the identifier of the weight loss menu stored in the serial number D504 to D507 of the weight loss recording database D5 of the participant, and the life improvement item stored in the individual program database D8. The meal menu identifier D804 and the lifestyle improvement item exercise menu identifier D805 are compared to determine the implementation rate of the weight loss menu as described above. Then, the server 400 performs less than the threshold set in advance in the life improvement item meal menu identifier D804 or the exercise menu identifier D805 of the life improvement item set in the personalized program database D8 for execution by the participant Are extracted (3403).

  Next, the server 400 determines whether or not the participant terminal device 300 has selected the “recommended menu” on the individual program registration screen shown in FIG. 31 (3404). If the “recommended menu” is selected, the process proceeds to step 3405. On the other hand, if the participant does not select the “recommended menu”, the meal menu displayed on the individual program registration screen of FIG. A weight reduction menu is selected from the exercise menu (3417).

  In step 3405, the server 400 acquires the parameters set in the parameter setting database D11.

  Next, according to the priority order indicated by the parameter acquired from the parameter setting database D11, a meal menu is acquired from the meal calorie database D9 (3406), and an exercise menu is acquired from the exercise calorie database D10 in order of priority (3407).

  Next, the server 400 extracts from the inquiry result database D7 the inquiry identifier D701 that is indicated as “target” in the improvement implementation target D705. Thereafter, the server 400 refers to the interview identifier D1301 of the interview information database D13 with the interview identifier D701, and acquires the interview category targeted by the participant from the meal menu category D1302 and the exercise menu category D1303 of the interview information database D13. (3408).

  Next, the server 400 excludes the category that has become less than the threshold value in step 3403 from the categories acquired in step 3408. In other words, the server 400 excludes the category of the weight reduction menu whose participation rate of participants is lower than the threshold.

  Next, in steps 3410 to 3415, the total number of meal menu categories D1302 and exercise menu categories D1303 acquired in step 3405 is set as the improvement target number, and the loop count (value of variable Count) reaches the improvement target number, or The loop is repeated until the number of calories in the weight loss menu acquired in the loop is equal to or greater than the target number of weight loss per day obtained in step 1104 in FIG.

  In step 3411, the menus belonging to the category that matches the item targeted as the improvement execution target D705 from the acquired meal menu category D1302 and exercise menu category D1303 are assigned priority levels D904 and D1004 from the meal calorie database D9 and exercise calorie database D10. Get in order.

  In step 3412, 100 kcal is added to the variable CalCnt every time a weight loss menu is acquired from either the meal calorie database D9 or the exercise calorie database D10.

  In step 3413, if the value of the variable CalCnt is equal to or greater than the target weight reduction calorie per day obtained in step 1104, the loop is terminated and the routine proceeds to step 3415. On the other hand, if the value of the variable CalCnt is less than the target weight reduction calorie number per day, in step 3414, 1 is added to the value of the variable Count for counting the total number of weight loss menus, and then the process returns to step 3410 to execute the loop. repeat.

  When the loop of steps 3410 to 3415 is completed, the contents of the category weight reduction menu (meal menu name D903, exercise menu name D1003, amount or time) that the participant sets as the improvement target number are the meal calorie database D9 and the exercise calorie database D10. Extracted from

  In step 3416, the server 400 transmits the extracted weight loss menu to the participant terminal device 300 in the order of priority D904 and D1004, and the participant terminal device 300 can select a weight loss menu suitable for weekday exercise. (3417).

  As a result of the processing as described above, the category whose participation rate of the participant is less than the threshold is excluded from the recommended menu, and therefore a weight reduction menu corresponding to the implementation status of the participant can be displayed.

  In the above embodiment, the server side management means M10 to M50 may be configured by the same management means.

It is a block diagram which shows the structure of the health guidance support system of embodiment of this invention. It is a flowchart which shows the outline | summary of the process by the health guidance support system of embodiment of this invention. It is a block diagram which shows the functional element of the initial stage preparation means of embodiment of this invention. It is a block diagram which shows the functional element of the participation preparation process means of embodiment of this invention. It is a block diagram which shows the functional element of the participant data input and browsing process means of embodiment of this invention. It is a block diagram which shows the functional element of the intervention guidance process means of embodiment of this invention. It is a block diagram which shows the functional element of the event processing means of this Embodiment. It is a flowchart of the process by the mail service process means of embodiment of this invention. It is a flowchart of the process by the priority order setting process means of this Embodiment. It is a flowchart of the process by the participant registration process means of embodiment of this invention. FIG. 11 shows a time chart of the weight reduction menu selection process shown in FIG. 10 according to the embodiment of the present invention. FIG. It is a flowchart of the process by the event check process means of embodiment of this invention. It is a flowchart of the process by the event check result display process means of embodiment of this invention. It is a flowchart of the process by the participant list display process means of embodiment of this invention. It is a flowchart of the process by the intervention determination process means of embodiment of this invention. It is a flowchart of the process by the fixed phrase edit process means of this Embodiment. It is a flowchart of the process by the regular event edit process means of this Embodiment. It is a flowchart which shows the detailed process of the display process of the weight reduction menu of step 228 among the processes of the participant registration process means shown in FIG. 10 of the embodiment of the present invention. It is a time chart of the display process of the weight loss menu of embodiment of this invention. It is a flowchart which shows the modification of the display process of the weight reduction menu of embodiment of this invention. It is explanatory drawing which shows the structure of the participant management database of embodiment of this invention. It is explanatory drawing which shows the structure of the inquiry information database of embodiment of this invention. It is explanatory drawing which shows the structure of the inquiry result database of embodiment of this invention. It is explanatory drawing which shows the structure of the program database classified by individual of embodiment of this invention. It is explanatory drawing which shows the structure of the parameter setting database of embodiment of this invention. It is explanatory drawing which shows the structure of the meal calorie database of embodiment of this invention. It is explanatory drawing which shows the structure of the exercise calorie database of embodiment of this invention. It is explanatory drawing of the weekday / holiday individual program registration screen of embodiment of this invention. It is a flowchart which shows the modification of the display process of the weight reduction menu of embodiment of this invention. It is explanatory drawing which shows the structure of the exercise calorie database of embodiment of this invention, and shows a modification. It is explanatory drawing of the program registration screen classified by individual of embodiment of this invention, and shows another example. It is a flowchart which shows the other modification of the display process of the weight reduction menu of embodiment of this invention. It is a flowchart which shows the further another modification of the display process of the weight reduction menu of embodiment of this invention. It is explanatory drawing which shows the structure of the individual weight loss target database of embodiment of this invention. It is explanatory drawing which shows the weight loss recording database structure of embodiment of this invention. It is explanatory drawing which shows the structure of the regular event database of embodiment of this invention. It is explanatory drawing which shows the structure of the fixed phrase database of embodiment of this invention. It is explanatory drawing which shows the structure of the instruction record database of embodiment of this invention. It is explanatory drawing of the program registration screen classified by individual of embodiment of this invention.

Explanation of symbols

100 administrator terminal device 200 leader terminal device 300 participant terminal device 400 server M1 initial preparation processing means M2 participation preparation processing means M3 participant data input / browsing processing means M4 intervention guidance processing means M5 event processing means M6 PDA data registration means D1 Instructor management database D2 Fixed phrase database D3 Periodic event database D4 Participant management database D5 Weight loss record database D6 Instruction record database D7 Questionnaire result database D8 Individual program database D9 Dietary calorie database D10 Exercise calorie database D11 Parameter setting database D12 Individual Weight loss target database D13 Interview information database

Claims (7)

A health guidance support system for implementing the health guidance to the participants by the instructions of the leaders,
A processor for performing arithmetic processing, a memory connected to the processor, an interface connected to the processor, and a weight loss recording database for storing the implementation status and the weight loss status of each participant's weight loss menu ,
The processor is
Accepts the information of the first participant to register the information of the first participant to the accepted,
The weight reduction menu implemented by the second participant who has achieved the target weight within the predetermined weight loss period is extracted from the weight reduction menu implementation status of the weight loss recording database, and the priority ranking is in descending order of the appearance frequency of the extracted weight loss menu. Assigned to the weight loss menu,
Wherein the weight loss menu, based on the first information of participants the registration, the first weight loss menu suitable for participants selected in order of the priority, the said selected reduced menu first To 1 participant,
The first information of the participants may transmit information for identifying the first participant, and results of interview to the first participant, the category of weight loss menu determined on the basis of the interview result Health guidance support system characterized by including. The processor is
Accepting the implementation status of the selected weight loss menu and the weight reduction status of the first participant, registering the accepted implementation status and weight loss status,
The health guidance support system according to claim 1, wherein it is determined whether or not at least one of the registered implementation status and weight loss status satisfies a predetermined condition, and the result of the determination is displayed. The health guidance support system includes:
A participant information database in which information for identifying the first participant is stored;
Results of interview to the first participant, and inquiry database categories weight loss menu first participant in response to the interview result is carried out is stored,
A weight-loss menu database presented to the first participant, the weight-loss menu database being preliminarily given priority and stored in a plurality of categories.
The processor is
The category executed by the first participant is acquired from the inquiry database, the weight reduction menu of the category that matches the acquired category is selected from the weight reduction menu database, and the selected weight reduction menu is extracted in the order of priority. The health guidance support system according to claim 1, wherein: The processor is
An implementation rate for each weight reduction menu of the first participant is calculated from the implementation status of the weight loss menu in the weight loss recording database, and a weight reduction menu with the implementation rate less than a predetermined threshold is extracted, and the extracted weight reduction menu acquires the category from the weight loss menu database, weight loss menu suitable for the first participant to select the order of the priority, claims, characterized in that excluding a category of the extracted reduced menu Item 4. The health guidance support system according to item 3 . The health guidance support system includes:
A participant information database in which information for identifying the first participant is stored;
A weight-loss menu database presented to the first participant, the weight-loss menu database being preliminarily given priority and stored in a plurality of categories.
Information of the first participant includes the weight of the first participant,
The weight loss menu database has an exercise menu including a reference weight and a reference exercise time according to the reference weight,
The processor is
When the exercise menu is included when presenting the selected weight loss menu to the first participant, a reference exercise time corresponding to the reference weight of the exercise menu is obtained from the weight loss menu database; The health guidance support system according to claim 1, wherein the exercise time corresponding to the weight of the first participant is calculated and presented. The health guidance support system includes:
A participant information database in which information for identifying the first participant is stored;
A weight-loss menu database presented to the first participant, the weight-loss menu database being preliminarily given priority and stored in a plurality of categories.
The processor is
Of Weight Loss menu presented to the first participant to detect weight loss menu that is not selected as reduced menu the first participant to implement, the category of the detected reduced menu from the weight loss menu database 2. The health guidance according to claim 1, wherein when the weight reduction menu obtained and selected for the first participant is selected in order of priority, the extracted weight loss menu category is excluded. Support system. A program that causes a health guidance support system that performs health guidance for participants according to instructions from a leader to execute the following procedures:
The health guidance support system includes a processor for performing arithmetic processing, a memory connected to the processor, an interface connected to the processor, and a weight loss record for storing a weight reduction menu implementation status and weight reduction status of each participant. With a database ,
The program is
And procedures for accepting the information of the first participant, to register the information of the first participant to the accepted,
Selecting a weight reduction menu suitable for the first participant based on the registered first participant information and presenting the selected weight loss menu to the first participant; Including
The first information of the participants may transmit information for identifying the first participant, and results of interview to the first participant, the category of weight loss menu determined on the basis of the interview result Including
The procedure for presenting the selected weight loss menu to the first participant comprises:
From the weight reduction menu implementation status in the weight loss record database, extract the weight loss menu implemented by the second participant who achieved the target weight within the prescribed weight loss period, and prioritize in descending order of appearance frequency of the extracted weight loss menu the assignment to the weight loss menu, based on the first participant information the registration, a program and selects the reduction menu suitable for the first participant in the order of the priority.