JP5318443B2 - Health guidance support system and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a health guidance support system for efficiently conducting uniform health guidance to a large number of health guidance target persons. <P>SOLUTION: This health guidance support system for conducting the health guidance to a user by an instruction of an instructor has: a processor performing arithmetic processing; a memory connected to the processor; and an interface connected to the processor. The processor receives information of a participant, registers the received information of the participant, selects a weight reduction menu fit for the participant based on the registered information of the participant, presents the selected weight reduction menu to the participant, receives an execution situation of the selected weight reduction menu and a situation of weight reduction of the participant, registers the received execution situation and weight reduction situation, decides whether at least one of the registered execution situation and weight reduction situation satisfies a prescribed condition or not, and displays a result of the decision. <P>COPYRIGHT: (C)2010,JPO&amp;INPIT

Description

  The present invention relates to a system for supporting health management, 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. The disease is said to increase the risk of arteriosclerosis, heart disease or cerebrovascular disease.

  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 examinee (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 instructor calculates the number of calories for reaching the target weight of the examinee, and plans and presents life improvement items regarding the dietary life and the amount of exercise necessary to reduce the weight to the target weight. Then, the execution status of the presented life improvement items and changes in weight are reported to the instructor, and the weight is reduced to the target weight.

Such techniques for weight loss include presenting target values for ingested energy and energy consumption according to the target weight, dietary status, and exercise status of the person performing weight loss, dietary restrictions to meet the target values, A technique for presenting a menu such as an exercise method is known (for example, see Patent Document 1).
JP 2004-227522 A

  However, in the method where the instructor sets the target weight of the examinee, calculates the number of calories to reach this target weight, and the public health nurse presents the life improvement items necessary to achieve the target weight, The instructor needs to know some life improvement items and the calorie consumption of each life improvement item in advance, and which life improvement item should be performed according to the individual, and the load of that item must be adjusted. The workload was heavy.

  The instructor spends time and dialogue between the instructor and the weight loss participant in order to set up life improvement items so that the individual's life pattern and personal preference are matched and the weight loss is easy to perform. There is a need to do. Participants in weight loss, such as the examinee, interact with the instructor to set items for improving their lives, but the improvement items are selected from the (limited) life improvement items prepared by the instructor, which is not necessarily a diet that suits the individual. In some cases, it was not the way.

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

  In addition, according to the technique described in Patent Document 1 described above, the predicted weight can be set as the target weight from changes in eating habits and exercise habits, but it is difficult to specify specific life improvement items. was there.

  Then, an object of this invention is to provide the health guidance support system which implements homogeneous health guidance efficiently with respect to many health guidance subject.

A typical example of the present invention is as follows. That is, a health guidance support system for conducting health guidance for participants according to instructions to a leader, comprising a processor that performs arithmetic processing, a memory connected to the processor, an interface connected to the processor, and the participation A weight reduction menu database for storing a weight loss menu presented to a participant, a participant information database for storing information for identifying the participant, and an inquiry result database for storing results of an inquiry to the participant And the weight loss menu database stores a weight loss menu classified into a plurality of categories with a predetermined calorie as a unit, the processor accepts the participant information, and the accepted participant The weight loss suitable for the participant based on the registered participant information Select the menu, present the selected weight loss menu to the participant, accept the implementation status of the selected weight loss menu, and the weight loss status of the participant, and accept the implementation status and weight loss. The situation is registered, it is determined whether or not at least one of the registered implementation status and the weight reduction status satisfies a predetermined condition, the result of the determination is displayed, and the same from the weight reduction menu in which the participant is presented When multiple weight loss menus are selected, the selected weight loss menus are managed by assigning different numbers corresponding to the number of the selected weight loss menus, and the participants need to improve based on the results of the interview. Information on the category that is judged to be present and selected as being able to reduce weight is stored in the interview result database and belongs to the selected category. Weight loss menu characterized in that it presented to the participants.

  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.

  Next, embodiments of the present invention will be described 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 mobile terminals such as PDAs or mobile phones on which application programs (for example, web browsers) operate.

  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 setting 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 recording database D5, a guidance recording database D6, an inquiry result database D7, and an individual action target database. D8, meal calorie database D9, exercise calorie database D10, parameter setting database D11, individual weight loss target database D12, and inquiry information database D13 are stored.

  The leader management database D1 stores information such as an identifier, a password, and a name of a leader who performs health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 3, the fixed phrase database D2 stores information on fixed phrases used in health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 4, the periodic event database D3 stores information on periodic events in health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 5, the participant management database D4 stores information on participants who receive health guidance from the health guidance support system according to the present embodiment.

  As shown in FIG. 6, 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.

  As shown in FIG. 7, the guidance record database D6 stores information on the history of health guidance by the health guidance support system of the present embodiment.

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

  As shown in FIG. 9, the individual behavior goal database D8 stores information on behavior goals of participants of health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 10, the meal calorie database D9 stores information on meal menus used for health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 11, the exercise calorie database D10 stores information on exercise menus used for health guidance by the health guidance support system of the present embodiment.

  As shown in FIG. 12, the parameter setting database D11 stores various parameters used by the health guidance support system of the present embodiment.

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

  As shown in FIG. 14, 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 (see FIG. 21). The entered participant information is registered in the participant management database D4 (M22, see FIG. 19).

  Next, the server 400 extracts the inquiry information corresponding to the inputted participant information from the inquiry information data verse D13, and sends the extracted inquiry information to the participant terminal device 300. The contents of the inquiry relate to an action target of a predetermined calorie (for example, 100 kcal). The action goal relates to a meal category or an exercise category. Action goals include goals included in meal categories such as “Do you have a lot of staple foods”, “Do you drink alcohol”, “Do you eat snacks”, “Do you walk for more than 30 minutes every day”, “Daily sports” And a goal included in an exercise category such as “Do you do?”.

  Participant terminal device 300 accepts an answer to the inquiry information and an input of an intention as to whether a category related to each inquiry is targeted (see FIG. 22). The answer to the inputted inquiry is registered in the inquiry result database D7 (M22, see FIG. 19).

  In such health guidance, if there are many choices of behavioral goals (weight reduction menu), it becomes possible to respond to the various needs of participants, but there is a problem that it takes time to select behavioral goals. However, in the health guidance support system of the present embodiment, by saving the participant's intention for each category, only the action target of the category expressing the intention of the participant as the target is set as the selection range of the action target. Allows participants to select action goals efficiently.

  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.

  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. Even in the same exercise, the amount of exercise for each predetermined calorie consumption is determined by referring to the participant information registered in the participant management database D4 from the physical characteristics of the participant (for example, the calorie consumption changes depending on the body weight). Calculated.

  The participant terminal device 300 presents the transmitted meal menu and exercise menu to the participant as a weight reduction menu (see FIG. 23). Participant terminal device 300 accepts an input of a target weight from the participant (see FIG. 24).

  When the weight reduction menu is selected, the weight reduction menu in which the participant expresses his / her intention to make a goal (can be performed by the participant) is selected with reference to the result of the interview registered in the interview result database D7. In addition, the amount of calorie reduction required per day to achieve the target weight is calculated, and the number of weight reduction menus that satisfy the calculated calorie is selected.

  In such health guidance, participants set action goals individually, so it was necessary to evaluate the implementation status of action goals individually. However, in the health guidance support system of this embodiment, all participants set behavioral goals according to a common weight reduction menu for a certain number of calories, so that the implementation of behavioral goals can be evaluated on a uniform scale. Can be made more efficient, and variation in health guidance by leaders can be suppressed.

  Participant terminal device 300 accepts selection of a meal menu and exercise menu by the participant (see FIG. 25). These input target weights, selected meal menus and selected exercise menus determine the participant's weight loss program. These inputted target weights are registered in the individual weight loss target database D12, and the selected meal menu and exercise menu are registered in the individual behavior target database D8 (see M22, FIG. 19, and FIG. 20).

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

  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). This determination cycle may be set at a cycle different from the participant's life cycle. For example, in general, a holiday is set for a person's life in a cycle of one week, and the holiday has a different life pattern from a weekday. For example, an event may be detected with a 10-day cycle different from the life pattern (7-day cycle). 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. In the instruction record database D6, the contents that the instructor actually changed from the contents of the instruction (for example, the text of the e-mail) recorded in the fixed phrase database D2 are also registered. The periodic event editing process (M53, see FIG. 37) refers to the change contents of the instruction registered in the instruction record database D6, and changes the fixed phrases to be changed and the data of the participants to be newly set as events. Extract and update the fixed phrase database D2 and the regular event database D3.

  Next, the server 400 extracts the determination result of the data input by the participant from the instruction record database D6, and transmits the extracted determination result to the instructor terminal device 200. The leader terminal device 200 displays the received determination result (see M4, FIG. 33).

  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. If guidance is provided without going through the health guidance support system of this embodiment (for example, by telephone or interview), the leader inputs the guidance content and registers the entered guidance content in the guidance record database D6. To do.

  In the health guidance support system of the present embodiment, the contents of health guidance can be managed in a unified manner, so that when the history of health guidance is necessary, the guidance results for the participants can be efficiently extracted without omission.

  Next, the configuration of each database according to the present embodiment will be described.

  FIG. 3 is an explanatory diagram showing the 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. 4 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 (other than the time condition) determined to be an event is registered. “Intervention determination OK” in the condition D303 is data set when it is determined in step 484 (see FIG. 30) of the intervention determination process that health guidance should be given.

  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, an event is detected, and 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 weight reduction menu execution rate 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. 5 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. 6 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 execution status D504 of serial number 1, the implementation status D505 of serial number 2, the implementation status D506 of serial number 3, and the implementation status D507 of serial number 4, the implementation time 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 number as the serial number registered in the serial number D803 of the individual-specific action target 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. 7 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. 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. 8 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, and a goal intention D704.

  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.

  In the goal intention D704, a flag indicating whether or not this inquiry content is targeted is registered. For example, “1” is registered in the target intention D 704 if the response content is “target”, and “2” is registered if the response content is “not target”.

  FIG. 9 is an explanatory diagram showing the configuration of the individual-specific action target database D8 of the present embodiment.

  The individual action target 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 behavior goal database D8 includes a participant identifier D801, a behavior goal registration date D802, a serial number D803, a menu identifier D804, and an increase / decrease D805.

  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 the action goal is registered in the action goal 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, different numbers corresponding to the selected number are assigned.

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

  In the increase / decrease D805, a flag indicating whether to reduce or increase the selected weight loss menu as an action target is registered. For example, “1” is registered in the increase / decrease D805 when the goal is to reduce as in the weight loss menu for meals, and “2” is added to the increase / decrease D805 in the case where the goal is to increase as in the weight loss menu for exercise. Is registered.

  FIG. 10 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, a meal type and a meal amount are set for each predetermined calorie (for example, 100 kcal).

  The meal calorie database D9 stores a meal menu identifier D901, a meal category D902, and a meal menu name D903.

  An identifier for uniquely identifying a meal menu is registered in the meal menu identifier D901. A meal type is registered in the meal category D902. For example, “1” if the meal type is staple food, “2” if the meal type is liquor, “3” if the meal type is snack, and “9” if the meal type is not related to meals. "Is registered in the category D902. The name and amount of this meal menu are registered in the meal menu name D903.

  FIG. 11 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 meal calorie database D10 includes an exercise menu identifier D1001, an exercise category D1002, an exercise menu name D1003, a reference weight D1004, and a reference time D1005.

  In the exercise menu identifier D1001, an identifier for uniquely identifying the exercise menu is registered. In the exercise category D1002, the type of exercise 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 menu name D1003, the name of this exercise menu is registered. In the reference body weight D1004, a body weight (in kg) serving as a reference for the exercise time registered in the reference time D1005 is registered. In the reference time D1005, the time (in minutes) for which the exercise menu D1003 should be performed in the reference weight D1004 is registered.

This is because, even in the same exercise, the calorie consumption varies depending on the weight of the participant, so the reference weight D1004 is used to calculate an appropriate amount of exercise based on the weight of the participant. Specifically, exercise of the reference time D1005 is necessary for a participant with the reference weight D1004 to consume 100 kcal. Similarly, in order for a person with a weight of Wkg to consume 100 kcal, exercise for the time calculated by the following formula 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.

  FIG. 12 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. 12 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 priority is given. Specifically, if the setting content D1103 is “111”, it indicates that meal, category = 1 (meal category “1” indicates “main meal”), and is preferentially presented.

  In the setting content D1103, a parameter for determining the priority order of the weight reduction menu is registered. The parameter identifier “333” means that the weight loss menu is presented in the order of staple food, alcohol, etc. in the meal.

  FIG. 13 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. 14 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, a meal category D1302, an exercise category D1303, and an inquiry content D1304.

  The inquiry identifier D1301 is a unique identifier for identifying the contents of the inquiry. The meal category D1302 and the exercise category D1303 are codes for classifying the inquiry contents. For example, “1” is an inquiry about staple food, “2” is an inquiry about liquor, “3” is an inquiry about snacks, and “9” is an inquiry not related to meals. Registered in An identifier common to the meal category D902 of the meal calorie database D9 is used for the meal category D1302.

  In the exercise 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. For this exercise category D1303, an identifier common to the exercise category D1002 of the exercise calorie database D10 is used.

  FIG. 15 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 of 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 email transmission / reception based on data in 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. 16 is a flowchart of processing by the mail service processing means M14 of this 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 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 server 400 determines the type of processing included in the access request and branches the processing (141). As a result of the determination, if the access request is activation of the mail service, the server 400 sets the mail reception interval and the event detection interval (142), and activates the event check processing means M43 to receive the mail. Processing and event detection processing are executed (143).

  On the other hand, if the access request is a stop of the mail service, the server 400 stops receiving the mail and detecting the event by stopping the event check processing means M43 (144).

  Further, if the access request is an event issue, the server 400 issues an event having the accepted content (145).

  By the processing described above, the server 400 can control the activation and termination of the event check processing means M43, whereby the reception of mail and the issue of events can be controlled.

  FIG. 17 is a flowchart of processing by the priority order setting processing means M17 of the present embodiment.

  The administrator terminal device 100 (or the instructor terminal device 200) requests selection of a category (meal menu or exercise menu) for setting or changing the priority order. The administrator terminal device 100 accepts the selection of the meal menu or exercise menu and the selection of the meal menu category D902 of the meal calorie database D9 or the exercise menu category D1002 of the exercise calorie database D10 (171). The administrator terminal device 100 transmits the selected category to the server 400.

  When the server 400 receives the selection of the category transmitted from the administrator terminal device 100, the server 400 identifies the database in which the priority is set from the received category, and the identified database (meal calorie database D9 or exercise calorie database D10). The data of the category selected from is read, and the read data is transmitted to the administrator terminal device 100.

  Thereafter, the administrator terminal device 100 receives an input of the priority order of the received data (menu) (172). The administrator terminal device 100 transmits the input priority order to the server 400.

  When receiving the priority order transmitted from the administrator terminal device 100, the server 400 determines whether or not to register the received priority in the database (173). As a result of this determination, when the priority is registered in the database, the received priority is registered in the database (meal calorie database D9 or exercise calorie database D10).

  For example, when a category of a meal menu is selected on the administrator terminal device 100, the server 400 reads the meal menu name D903 of the selected category from the meal calorie database D9, and the read meal menu name D903 is the administrator terminal. Transmit to device 100. Then, the administrator terminal device 100 receives an input of the priority order of the meal menu and transmits the input priority order to the server 400. The server 400 registers the received priority in the meal calorie database D9. In FIG. 10, the priority column of the meal calorie database D9 is not shown. Similarly, in FIG. 11, the priority column of the exercise calorie database D10 is not shown.

  By the above processing, the administrator can arbitrarily set or change the priority registered in the meal calorie database D9 and the exercise calorie database D10 for each category of each database. Thereby, the priority of a meal menu and an exercise menu can be set according to the implementation status of a participant's habit, thought, age, sex, and weight loss menu (meal menu 8 and exercise menu).

  In step 172, an example in which the administrator inputs priority is shown. However, when a plurality of priority patterns are set in advance and a pattern is selected from the administrator terminal device 100, the server 400 is selected. The menu order may be determined according to the pattern. For example, you may prepare the setting pattern which ranks with respect to the exercise menu of the exercise calorie database D10 in order with the short exercise time.

  Moreover, you may determine the order | rank of the meal calorie database D9 and the exercise calorie database D10 in order with a high 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. And the meal menu) may be extracted from the serial numbers D504 to D507, and the priority order may be determined in descending order of appearance frequency of the extracted weight loss menu.

  Further, the implemented weight loss menu is extracted from the serial numbers D504 to D507 of the weight loss recording database D9, the implementation rate of the extracted weight loss menu is obtained for each category, and the order of the weight reduction menu is determined in descending order of the obtained implementation rate. It may be assigned.

  Furthermore, the server 400 may be configured to correct the priority assigned to the weight reduction menu from the administrator terminal device 100 after assigning the priority of the weight reduction menu in the pattern as described above.

  FIG. 18 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, from the leader terminal device 200, information on participants who receive health guidance by the health guidance support system of the present embodiment.

  When the server 400 receives an access request from the leader terminal device 200, the server side management means (M20) starts the leader authentication process (M21). The leader authentication process (M21) collates information (for example, an identifier and a password) included in the access request with information registered in the leader management database D1, and authenticates the access.

  After successful authentication, the participant process registration process is started to register the participant information (M22).

  FIG. 19 is a flowchart of the processing by the participant registration processing means M22 of this 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 (see FIG. 21) 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 D13 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 (see FIG. 22) 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 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. At this time, when the inquiry result is not registered in the inquiry result database D7, the server 400 does not extract items to be selected as the weight loss menu, and does not extract all items registered in the meal calorie database D9 and the exercise calorie database D10. The item is sent 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 weight loss program setting screen (see FIG. 23) (226).

  Next, the server 400 sends information necessary for setting the weight loss program to the participant terminal device 300. At this time, the weight loss program setting screen (see FIG. 23) is displayed on the participant terminal device 300, and the participant inputs information necessary for creating the 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 (227).

  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 weight loss program setting screen (see FIG. 24) (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 process of step 229 will be described in detail later with reference to FIG. The selected weight loss menu is transmitted to the server 400 and registered in the individual action target database D8 (230).

  In addition, although the target calorie was calculated in the server 400, the participant terminal device 300 may execute the calculation of the target calorie without sending the information necessary for creating the weight loss program to the server 400 in step 227. In this case, in step 230, information is registered in the individual reduction target database D12.

  FIG. 20 is a flowchart of detailed processing in step 229 among the processing by the participant registration processing means M22 of the present embodiment.

  First, it waits for a presentation request of a recommended weight reduction menu from the participant (2401). When the participant requests presentation of the recommended weight loss menu, the process proceeds to step 2402. On the other hand, if the participant does not request the presentation of the recommended weight reduction menu, the weight reduction menu is selected from the weight reduction menu displayed on the initial screen (FIG. 23) of the weight reduction menu setting (2420).

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

  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 (2403), and an exercise menu is acquired from the exercise calorie database D10 (2404).

  Next, an inquiry showing a target intention D704 is extracted from the inquiry result database D7. Thereafter, referring to the inquiry information database D13, the inquiry categories D1302 and D1303 extracted from the inquiry result database D7 are specified (2405).

  Thereafter, the process enters a loop of steps 2406 to 2411. That is, in step 2406, after the counter (Count) = 1 and the calorie counter (CalCnt) = 0, the loop processing up to step 2411 is repeatedly executed while the counter value is equal to or less than the number of extracted menus. To do.

  In the loop, one menu belonging to the inquiry category indicating the target intention is extracted from the meal menu and exercise menu (2407), and the calorie corresponding to the extracted menu is added to CalCnt (2408). . In the present embodiment, the calorie corresponding to each menu is set to 100 kcal.

  Next, the calorie target to be reduced per day calculated in step 228 is compared with CalCnt (2409). As a result, if CalCnt is equal to or more than the target of calories to be reduced per day, the menu to be presented is ready, so the process exits the loop and proceeds to step 2412. On the other hand, if CalCnt is below the target of calories to be reduced per day, 1 is added to the counter value (Count) (2410). If the number of extracted menus is less than the counter value, the process returns to step 2407 to further extract menus presented to the participants.

  On the other hand, if the counter value (Count) exceeds the number of extracted menus, the upper limit of the number of menus to be presented has been reached, so the process exits the loop (2411) and proceeds to step 2412.

  Then, the extracted menu is transmitted to the participant terminal device 300, and is displayed in a state where the extracted menu is selected on the weight reduction menu setting screen (FIG. 25) (2412).

  FIG. 21 is an explanatory diagram of a participant information input screen by a health guidance participant in the present embodiment.

  The participant information input screen is displayed on the leader terminal device 200, and the leader inputs information using this screen.

  On the participant information input screen, the participant's name, gender, date of birth, and e-mail address are entered as basic information. Also, height and weight (participant's physical characteristics) are input as measurement information of the participant. Furthermore, as the participant system information, the participant identifier, password, instructor name, and necessity of inquiry are input. Setting the weight loss menu (without displaying the inquiry answer input screen (FIG. 22)) without requesting the participant to answer the interview by entering “No” for the necessity of this inquiry It is possible to proceed to FIG.

  By operating the “decision” button, the input information is transmitted to the server 400 and registered in the participant management database D4.

  FIG. 22 is an explanatory diagram of an input screen for answers to an inquiry to a health guidance participant in the present embodiment.

  The inquiry answer input screen is displayed on the participant terminal device 300, and the participant inputs an answer to the inquiry using this screen.

  On the inquiry answer input screen, the contents of the inquiry regarding meals and exercise are displayed classified by category. The participant inputs an answer “YES” or “NO” to each inquiry content. If the instructor / participant can determine that improvement is necessary for the contents of the interview, answer “YES”, and if it can be determined that improvement is not required, answer “NO”. Is made.

  Furthermore, it is possible to select whether or not to target this category. Selecting to target this category preferentially presents the weight loss menu associated with this category. If the answer to the question is “NO”, the participant can determine that there is no need to improve the question. Therefore, it is controlled so that “to make this category a goal” cannot be selected. . This prevents the category weight loss menu from being presented. In this way, by not presenting categories that do not need to be improved as targets, selectable cards can be limited, and the participant can efficiently select the weight loss menu. In addition, since the weight loss menu is selected in the category in which the participant is aware of the problem, the effect of weight loss is improved.

  By operating the “decision” button, the input information is transmitted to the server 400 and registered in the participant inquiry result database D7. By operating the “Skip” button, the participant can proceed to the setting of the weight reduction menu (FIG. 23) without answering the inquiry.

  FIG. 23 to FIG. 25 are explanatory diagrams of a setting screen for a weight reduction menu by a health guidance participant in the present embodiment. FIG. 23 shows a screen at the time of initial display, FIG. 24 shows a screen at the time of inputting weight / target weight / weight loss period, and FIG. 25 shows a screen at the time of card selection.

  The weight reduction menu setting screen is displayed on the participant terminal device 300, and the participant uses this screen to set the weight reduction menu.

  The weight at the start is displayed on the weight loss menu setting screen. Further, the weight reduction menu setting screen is provided with input fields for a target weight, a weight reduction start date, and a weight reduction implementation period. In addition, the weight loss menu setting screen is provided with display fields for weight after weight loss and calories per day to be reduced. In addition, the weight loss menu setting screen displays the weight loss menu (meal menu and exercise menu) in card form, and provides operation buttons for displaying the recommended weight loss menu and a display field for the selected weight loss menu. It is done. Further, in the case where the inquiry result is registered in the inquiry result database D7, the weight reduction menu of the category that the participant intentionally displays as the target is displayed in a card format. In this way, since the weight reduction menu displays only the category that the participant has indicated as a goal, the card that the participant is likely to execute can be easily selected. In this weight loss menu, one card 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, sake, snacks, etc., and exercises are classified into walks / runs, sports, etc. and displayed. Therefore, the participant can easily select a suitable card. 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.

  As shown in FIG. 23, at the time of initial display, the start weight input in the participant registration (221 in FIG. 19) is displayed.

  Thereafter, as shown in FIG. 24, 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.

  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. 25, a list of the selected weight loss menus is displayed in a predetermined display field, calories to be 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 loss menus selected, the number of meal menus with high calories (less meals corresponding to 100 kcal) is reduced by X, and the menu of meals with low calories (large meals equivalent to 100 kcal) is increased by Y. Ease . 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.

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

  FIG. 26 is a block diagram showing functional elements of the participant data input / browsing processing means M3 of the present embodiment.

  The participant data input process is a process of registering from the participant terminal device 300 the state of the participant who receives the health guidance by the health guidance support system of the present embodiment (the implementation status of the weight loss menu, change in weight, etc.). . In the participant data browsing process, the past state of the participant who receives the health guidance by the health guidance support system of the present embodiment (the implementation status of the weight loss menu, the change in weight, etc.) is displayed on the participant terminal device 300. It is processing.

  When the server 400 receives an access request from the leader terminal device 300, the server-side management means M30 activates the participant authentication process (M31). The participant authentication process (M31) authenticates access from the participant terminal device 300 to the health guidance support system using the participant identifier D401 and the password D407 (see FIG. 5).

  After successful authentication, the individual weight loss record display process is activated (M32). Specifically, a record of the participant in the past predetermined period is extracted from the weight loss recording database D5 using the identifier of the authenticated participant. The extracted record is transmitted to the participant terminal device 300 and displayed on the data input screen (see FIG. 27).

  Next, the participant terminal device 300 receives the data input by the participant by the data input processing means (M33). Data input by the participant is transmitted to the server 400.

  The server 400 activates the data registration processing means and registers the data input by the participant in the weight loss recording database D5 (M34).

  FIG. 27 is an explanatory diagram of a screen for inputting daily data of a participant by a health guidance participant in the present embodiment.

  The data input screen is displayed on the participant terminal device 300, and the participant inputs daily weight and the like using this screen.

  The data input screen displays the change in the weight of the participant and the implementation status of the weight loss menu. As for the past implementation status, the implementation status of the card of the same date is displayed by an icon in the graph displaying the weight. For example, if the calorie reduction resulting from the weight loss menu is 50% or more of the target calorie per day, a laughed face icon is displayed. On the other hand, if the calorie reduction due to the weight reduction menu is less than 50% of the target calorie per day, a crying face icon is displayed.

  Specifically, if the daily calorie to be reduced by a participant is 272 kcal, if two or more weight loss menus can be implemented to reduce the calorie by 200 kcal or more, the icon of the laughing face Is displayed. On the other hand, if one or less weight reduction menus are implemented and only 100 calories or less can be reduced, a crying face icon is displayed.

  In this way, the weight of the participants and the implementation status of the weight loss menu are displayed in a graph, so if you make an effort, the weight will decrease, and if you do not make an effort, the weight will not decrease (increased). Can give participants a chance to notice if they are affected.

  In addition, a data input field is provided on the data input screen. The date, the weight of the day, and the implementation status of the selected weight loss menu are entered in the data entry field. The participant inputs the date of the data to be input in the date column, and inputs the weight of the day and whether or not the selected weight loss menu is executed.

  Finally, by operating the “OK” button, these input data are transmitted to the server 400 and registered in the weight loss recording database D5.

  FIG. 28 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.

  When the server 400 receives the access request from the leader terminal device 200, the server side management means M40 activates the leader authentication processing means M41. The leader authentication processing means M41 authenticates access to the health guidance support system from the leader terminal device 200 (M41).

  In addition, the server 400 activates an event check process (see FIG. 29) at a predetermined timing (for example, repeatedly every predetermined period), and detects the occurrence of an event that requires action on the participant. (M42). Then, an intervention determination process (see FIG. 30) is activated to determine whether an intervention (action) is necessary for the detected event (M48). The leader authentication process M41 is activated in response to an access request from the leader terminal apparatus 200, whereas the event check processing means M42 does not depend on a request from the leader terminal apparatus 200 but has a predetermined timing set in advance. It is started with.

  After successful authentication in the leader authentication process M41, the server 400 starts an event check result display process (see FIG. 31), and displays the detected event on the leader terminal apparatus 200 (M43). The leader looks at the event check result display screen (FIG. 33) and determines the content 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).

  Moreover, after a successful authentication, a participant list display process (refer to FIG. 32) 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 (FIG. 33).

  Further, after the authentication is successful, the instruction record registration process is started, the instruction record registration screen (FIG. 34) is displayed on the instructor terminal device 200, and input of instruction contents from the instructor is accepted (M46).

  Further, after successful authentication, the individual weight loss record display process is started, the weight loss record is read from the weight loss record database D5, and the individual weight loss record is displayed (M45).

  FIG. 29 is a flowchart of processing by the event check processing means M42 of the present 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, the weight loss record of the participant is compared with the periodic event detection condition D303 (4206). As a result, when the weight loss record of the participant satisfies the detection condition D303, the mail title / text corresponding to the identifier registered in the participant mail wording identifier D305, and the leader wording identifier D306 are registered. The text for the leader corresponding to the identifier is read from the fixed phrase database D2, and an e-mail text to be notified to the participant and a notification text to the instructor are created (4207). At this time, a keyword (for example, name) included in the read word is replaced so as to be suitable for the participant.

  On the other hand, if the weight loss record of the participant does not satisfy the periodic event detection condition D303, this event is not executed for this participant, and the counter 2 is incremented in order to process the next participant ( 4212).

  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.

  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.

  FIG. 30 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 executed when the periodic event detection condition D303 is related to the intervention determination in step 4206.

  In the intervention determination process 4208, first, the weight reduction start date of the participant is acquired from the individual weight loss target database D12, and the number of improvement implementation items registered in the weight loss recording database D5 in the period from the start date to the present (at the time of intervention determination). Is acquired (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. 31 is a flowchart of 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 D612 is “1” is acquired from the instruction record database D6, and the acquired data is transmitted to the instructor terminal device 200 (431).

  Upon receiving the data, the leader terminal device 200 displays the event data as shown in FIG. 33 (432). The content of the event displayed on the event check result display screen (FIG. 33) is determined 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, on the event check result display screen, the instructor can change the check result display flag D612 by changing the 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 (433). If the operation of the “Done Delete” button is detected, the event whose state is changed to “Done” is deleted from the screen. Then, the changed check result display flag is registered in the instruction record database D6 (434).

  FIG. 32 is a flowchart of processing by the participant list display processing means M44 of the present 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, daily weight, target weight, etc. of the participant in charge of the instructor are recorded in the participant management database D4, the weight loss recording database D5, and the individual weight loss target. Obtained from the database D12 (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. 33 is an explanatory diagram of an event check result display screen according to the present embodiment.

  The event check result display screen is displayed on the leader terminal device 200, and the leader inputs an instruction for an action (health guidance) for the event.

  The event check result display screen is provided with an event check result display field. The event check result display processing means (M43) generates data to be displayed in the event check result display field.

  In the check result display field, the date and time when the event is detected, the name of the participant related to the event, the content of the detected event, and the state of the event are displayed. Also, in the check result display field, if the event is related to email, an email processing instruction button ("Edit" and "Send" if the status is "Not", "View" if the status is "Complete") Is provided. When the instructor operates the “send” button, an e-mail for providing health guidance to the participant is transmitted without changing the title / text. On the other hand, when the instructor operates the “Edit” button, the screen for editing the title / text of the email that provides health guidance to the participant is displayed, and the email is sent to the participant after the editing of the title / text Is done. As described above, since the mail transmitted to each participant can be edited, it is possible to provide guidance suitable for each participant. In addition, by operating the “browse” button, it is possible to browse the title / sentence of a mail that has already been sent. As described above, since the sent mail can be referred to, the instructor can refer to the past instruction.

  The event check result display screen is provided with a “Done Delete” button. When the instructor operates the “Done Delete” button, the event whose state is changed to “Done” is deleted from the event check result display screen.

  Further, a list of participants who are subjects of health guidance is displayed on the event check result display screen. The participant list display processing means (M44) generates data to be displayed on the participant list. The participant list includes the name of the participant, the number of days elapsed since the start of the instruction, the weight at the start of the instruction, the weight on the tenth day from the start of the instruction, the weight on the 20th day from the start of the instruction, and the 30th day from the start of the instruction. Weight, target weight, intervention determination result, and summary of previous guidance are displayed.

  In the column for displaying the weight on the tenth day from the start of the instruction, the weight on the tenth day is displayed on the upper row, the target weight on the tenth day is displayed on the middle row, and the target achievement status on the tenth day is displayed on the lower row. As the target achievement status, “◯” is displayed if the target is achieved, and “X” is displayed if the target is not achieved. The weight on the 20th day and the weight on the 30th day are displayed in the same manner as the weight on the 10th day. The weight on the 20th day and the weight on the 30th day are displayed in the same manner as the weight on the 10th day.

In the intervention determination result, the result of the intervention determination (M48) (required / not required, determination date) is displayed.
In the overview of the previous instruction, the previous instruction content registered in the instruction record database D6 is displayed. By displaying the previous instruction content, even when the number of participants in charge of the instructor increases, it can be an opportunity to remind each participant when and what kind of instruction was provided.

  By operating a “Go” button provided in the participant list, a transition is made to the data input / browsing screen of each participant. For this reason, since the leader can confirm the details of the weight loss situation for each participant as necessary, guidance suitable for each participant is possible.

  FIG. 34 is an explanatory diagram of a guidance content registration screen in the present embodiment.

  The guidance record registration screen is displayed on the leader terminal device 200 and inputs a record of health guidance conducted by the leader on the participants. In addition, although the record of the health guidance automatically performed by the system (for example, automatically transmitted e-mail) is automatically registered in the guidance record database D6, the health performed by the instructor separately from the system The instruction record needs to be input by the instructor using the instruction record registration screen.

  The instruction record registration screen includes a participant identifier input field, a participant name display field, a leader identifier input field, and a leader name display field. When the participant identifier is entered in the participant identifier input field, the participant name is displayed. When the leader identifier is entered in the leader identifier input field, the leader name is displayed. The

  Further, the instruction record registration screen is provided with input fields for the instruction implementation date, instruction type, and instruction contents. The instruction type is selected from preset types such as “telephone”, “mail”, and “interview”. A text sentence is input to the instruction content.

  Finally, by operating the “OK” button, the input information is transmitted to the server 400 and registered in the instruction record database D6.

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

  The event setting means M5 is activated when an administrator requests access to the regular event database D3 or the fixed phrase database D2 of the server 400 via the administrator 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 M51 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 contents of the received fixed phrase database D2 and transmits data input by the administrator to the fixed phrase edit 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 and transmits the data input by the administrator 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. 36 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 there is (5201). 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 (5202). Then, the fixed phrase editing processing means M52 sets the category of the fixed phrase addressed to the participant to “P” (5203), and proceeds to step 5206.

  On the other hand, as a result of the determination in step 5201, if the edit request for the fixed phrase is a request for editing the fixed phrase addressed to the instructor, a record in which the phrase identifier D201 of the fixed phrase database D2 starts with “S” is selected and selected. The record data is transmitted to the administrator terminal device 100 (5204). Then, the fixed phrase editing processing means M52 sets the category of the fixed phrase addressed to the instructor to “P” (5205), and proceeds to step 5206.

  Next, the server 400 inquires whether to select a fixed phrase already registered in the fixed phrase database D2 (5206). If a registered fixed phrase is selected as a response to the inquiry from the administrator terminal device 100, the process proceeds to step 5209. If a registered fixed phrase is not selected, the process proceeds to step 5207 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 (5207). Thereafter, the server 400 generates a serial number, adds the generated serial number to the category set in step 5203 or 5205, and generates an identifier of the wording. Then, a new record is added to the fixed phrase database D2, and the identifier of the generated phrase is registered. Then, the title and text received by the server 400 from the administrator terminal device 100 are respectively registered in the title D202 and text D203 of the fixed phrase database D2 (5208).

  On the other hand, if the registered fixed phrase is selected in step 5206, the administrator terminal apparatus 100 is inquired whether 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 5213, and if the response is not “delete”, the process proceeds to step 5210 (5209).

  In step 5210, the selected fixed phrase data 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 (5210).

  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 (5211).

  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 (5208). On the other hand, if the result of the determination is update, the edited title D202 and body D203 are registered in the record of the word identifier D201, and the standard wording database D2 is updated (5212).

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

  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. 37 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 unit 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 5304 to update or delete the periodic event. On the other hand, if the registered regular event is not designated, the process proceeds to step 5302 to register the regular event for new registration.

  In the case of new registration, the administrator terminal device 100 accepts input of timing, event contents, and conditions, and sends the accepted information to the server 400 (5302). Next, the server 400 generates a serial number, and determines the generated serial number as an event identifier. Then, a new record is added to the periodic event database D3, and an event identifier D301 is registered (5303). 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 D303 of the regular event database D3, respectively.

  On the other hand, if a registered regular event is specified in step 5301, the administrator terminal device 100 is inquired whether or not to delete the registered regular event. If the response to the inquiry is “delete”, the process proceeds to step 5308, and if the response is not “delete”, the process proceeds to step 5305 (5304).

  In step 5305, 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 transmitted to the server 400 (5305).

  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 (5306).

  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 update, the edited timing D302, condition D303, and event content D304 are registered in the record of the event identifier D301, and the regular event database D3 is updated (5307).

  When deleting a periodic event, the record of the event ID 301 designated from the administrator terminal device 100 is deleted (5308).

  Through the above processing, the administrator (or instructor) can edit the periodic event database D3, and can arbitrarily set conditions and timing for transmitting or creating a desired message.

  FIG. 38 is a block diagram showing functional elements of the PDA data registration means M6 of the present embodiment.

  The PDA data registration process is a process of registering the participant data transmitted from the participant terminal device 300 in the e-mail format in the weight loss recording database D5.

  Using the participant terminal device 300, the participant transmits the daily weight and the implementation status of the weight loss menu to the server 400. When the participant terminal apparatus 300 is a mobile phone in which only a few resources are mounted, or when the bandwidth of the communication line is narrow, these data may be transmitted in a standard e-mail format.

  When the server 400 receives the data transmitted from the participant in the electronic mail format from the participant terminal device 300, the server side management means M61 activates the data transmission mail receiving means M61. The data transmission mail receiving means M61 sends the received electronic mail to the mail analysis processing means M62. The mail analysis processing means M62 analyzes the received electronic mail, and extracts the date, the weight of the participant, and the implementation status data of the weight loss menu included in the electronic mail transmitted by the participant. Then, the data registration processing means M64 registers the extracted date, weight, and implementation status of the weight loss menu in the weight loss recording database D5.

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 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 regular event database 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 weight loss recording database structure 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 which shows the structure of the inquiry result database of embodiment of this invention. It is explanatory drawing which shows the structure of the action target database classified by individual 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 which shows the structure of the parameter setting database 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 structure of the inquiry information database 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 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 block diagram which shows the functional element of the participation preparation process means of embodiment of this invention. It is a flowchart of the process by the participant registration process means of embodiment of this invention. It is a flowchart of the process by the participant registration process means of embodiment of this invention. It is explanatory drawing of the participant information input screen of embodiment of this invention. It is explanatory drawing of the inquiry reply input screen of embodiment of this invention. It is explanatory drawing of the weight reduction menu setting screen of embodiment of this invention. It is explanatory drawing of the weight reduction menu setting screen of embodiment of this invention. It is explanatory drawing of the weight reduction menu setting screen 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 explanatory drawing of the daily data input screen of the participant 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 flowchart of the process by the event check 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 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 explanatory drawing of the event check result display screen of embodiment of this invention. It is explanatory drawing of the instruction | indication record registration screen of embodiment of this invention. It is a block diagram which shows the functional element of the event setting means of this Embodiment. 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 of the process by the PDA data registration means of this Embodiment.

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 setting means M6 PDA data registration means D1 Instructor management database D2 Fixed wording database D3 Regular event database D4 Participant management database D5 Weight loss record database D6 Instruction record database D7 Questionnaire result database D8 Individual action goal database D9 Dietary calorie database D10 Exercise calorie database D11 Parameter setting database D12 Individual Separate weight loss target database D13 Interview information database

Claims (10)

A health guidance support system for conducting health guidance for participants according to instructions from a leader,
A processor for performing arithmetic processing, a memory connected to the processor, an interface connected to the processor, a weight loss menu database in which a weight loss menu presented to the participant is stored , and for identifying the participant A participant information database in which information is stored, and an interview result database in which results of interviews with the participants are stored ,
The weight loss menu database stores a weight loss menu, with a predetermined calorie as a unit , classified into a plurality of categories ,
The processor is
Accept the participant information, register the accepted participant information,
Based on the registered participant information, select a weight loss menu suitable for the participant, and present the selected weight loss menu to the participant;
Accept the implementation status of the selected weight loss menu and the status of the participant's weight loss, register the accepted implementation status and weight loss status,
Determine whether at least one of the registered implementation status and weight loss status satisfies a predetermined condition, and display the result of the determination;
When the same weight loss menu is selected from the weight loss menu presented by the participant, the selected weight loss menu is managed by assigning different numbers corresponding to the number of the selected weight loss menus ,
The participant determines that improvement is necessary based on the result of the interview, and stores information on the category selected as being able to make an effort for weight loss in the interview result database.
A health guidance support system , wherein a weight loss menu belonging to the selected category is presented to the participant . The weight loss menu presented to the participant is classified into a plurality of categories and stored in the weight loss menu database,
The participant information includes information on categories selected by the participant that allow for weight loss efforts,
The health guidance support system according to claim 1, wherein the processor preferentially selects a weight loss menu included in the selected category and presents the weight reduction menu to the participant.   The processor is configured such that the total number of calories corresponding to the weight loss menu selected as suitable for the participant is equal to or less than a target of calories to be reduced by the participant per day, and the upper limit of the number of menus to be presented is below If so, the health guidance support system according to claim 2, wherein the weight reduction menu is further selected and presented to the participant. The information of the participant includes information for identifying the participant and a result of an inquiry to the participant,
The health guidance support system includes:
A weight loss recording database storing the implementation status and weight loss status for each participant;
An event database that stores determination conditions for the implementation status and the weight loss status, and
The processor is
Based on the results of the interview stored in the interview result database, select a weight reduction menu suitable for the participant to conduct,
Based on the result of comparing the implementation status and the weight reduction status for each participant stored in the weight loss recording database with the determination conditions stored in the event database, at least one of the implementation status and the weight reduction status is a predetermined condition. The health guidance support system according to claim 1, wherein it is determined whether or not the condition is satisfied. The processor is
Based on the result of the determination, determine the content of health guidance for the participants, implement the health guidance of the determined content,
The health guidance support system according to claim 1, wherein the implemented health guidance is recorded. The weight loss menu includes a menu that consumes calories by exercise performed by the participant,
The participant information includes the weight of the participant,
The processor is
Based on the weight of the participant, calculate the amount of exercise that the participant should perform to consume the predetermined calories,
The health guidance support system according to claim 1, wherein a menu for reducing the calculated amount of exercise is presented to the participant.   The health guidance support system according to claim 1, wherein the processor repeatedly determines whether at least one of the registered implementation status and weight reduction status satisfies a predetermined condition at a predetermined timing.   The health guidance support system according to claim 7, wherein the predetermined timing is set with a number of days different from the life cycle of the participant. The health guidance support system includes a leader terminal device used by the leader, a participant terminal device used by the participant, a server device connected to the leader terminal device and the participant terminal device, With
The server device receives the participant information input from the participant terminal device, registers the received participant information in a storage device, and based on the participant information registered in the storage device Selecting a weight reduction menu suitable for implementation by the participant, transmitting information of the selected weight loss menu to the participant terminal device,
The participant terminal device displays the selected weight loss menu;
The server device receives the implementation status of the selected weight loss menu input from the participant terminal device and the status of the participant's weight loss, registers the received implementation status and the weight loss status, It is determined whether or not the registered implementation status and weight loss status satisfy a predetermined condition, and the result of the determination is transmitted to the leader terminal device,
The health guidance support system according to any one of claims 1 to 8, wherein the leader terminal device displays the result of the determination. A program for causing a health guidance support system that performs health guidance for participants according to instructions from a leader to execute the following procedure,
The health guidance support system includes a processor that performs arithmetic processing, a memory connected to the processor, an interface connected to the processor, a weight loss menu database that stores a weight loss menu presented to the participant, A participant information database in which information for identifying the participant is stored; and an inquiry result database in which a result of an inquiry to the participant is stored ;
The weight loss menu database stores a weight loss menu, with a predetermined calorie as a unit , classified into a plurality of categories ,
The program is
Receiving the participant information and registering the received participant information;
Selecting a weight loss menu suitable for the participant based on the registered participant information and presenting the selected weight loss menu to the participant;
A procedure for accepting the implementation status of the selected weight loss menu and the status of the participant's weight loss, and registering the accepted implementation status and weight loss status;
Determining whether or not at least one of the registered implementation status and weight loss status satisfies a predetermined condition, and displaying a result of the determination,
If you select multiple identical weight loss menu from the weight loss menu the participants are presented, by assigning a fraction different numbers of the selected reduced menu to manage the selected reduced menu,
The participant determines that improvement is necessary based on the result of the interview, and stores information on the category selected as being able to make an effort for weight loss in the interview result database.
A program for presenting a weight loss menu belonging to the selected category to the participant .

Images