Cooking charge determination system and program

Abstract

To provide a cooking charge determination system that prevents a resident who is not feeling well from cooking.SOLUTION: A cooking charge determination system 10 comprises a wearable device 20 worn by a resident, a user terminal 30 held by a user, and a management server 40. The management server 40 acquires residents' biological data, such as body temperature, blood pressure, sleep time, heart rate, and respiratory rate, from a wearable terminal 20 via a user terminal 30. The management server 40 determines the resident's current health condition based on the acquired biometric data. The management server 40 excludes a resident deemed to be in poor health from the candidates for today's dinner cooking charge and determines the cooking charge among other residents. The management server 40 notifies the residents of the determined cooking charge via the user terminal 30.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a system for determining who will be in charge of cooking for the day. [Background technology]

[0002] Patent Document 1 discloses a housework sharing system that assigns housework to each resident in a family consisting of multiple residents. This housework sharing system includes multiple cameras installed in each room of the house, a biometric sensor, and a controller. The controller calculates the resident's stress level while performing housework based on the images captured by the cameras and the resident's biometric information acquired by the biometric sensor. The controller determines the share of housework for this month based on the resident's stress level while performing housework last month. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-177447 Summary of the Invention [Problem to be solved by the invention]

[0004] The system disclosed in Patent Document 1 has the problem that it determines the share of housework based on the stress felt while doing the housework, and does not take into account stress other than housework. Also, the system disclosed in Patent Document 1 determines the share of housework for a certain period of time, such as January, so there is a problem that even if you are not feeling well, for example, you have to do the shared housework.

[0005] The present invention has been made in view of the above-mentioned circumstances, and its purpose is to provide a cook decision system that can prevent a resident who is not feeling well from cooking. [Means for solving the problem]

[0006] (1) A cook selection system according to the present invention includes a biosensor that detects biometric data of multiple residents, a notification device, and a control device that can communicate with the biosensor and the notification device. The control device executes a biometric data acquisition process that acquires biometric data from the biosensor, a health condition determination process that determines the health condition of each resident at a predetermined time on a predetermined day based on the biometric data, a cook selection process that determines a cook for the predetermined day based on the determined health condition of each resident, and a notification process that notifies the determined cook via the notification device.

[0007] The predetermined time is set to a time before meal cooking begins. At the predetermined time, the control device acquires biometric data from the biometric sensors, determines the physical condition of each resident today (the predetermined day) based on the acquired biometric data, and determines who will cook today's meal based on the identified physical condition of each resident and notifies the resident.

[0008] (2) The control device may further execute a storage process for storing the determined cook in memory as performance data in association with a date. The cook determination process is a process for determining a cook by determining residents to exclude from the candidate cooks based on the performance data.

[0009] The cooks determined by the cook determination system of the present invention are stored in memory as performance data in association with the date. If a resident has been the cook for two consecutive days in the performance data, for example, they will be removed from consideration as candidates for the next cook. This ensures fairness in the allocation of cooking responsibilities among residents.

[0010] (3) The cook determination system according to the present invention may further include an input interface capable of communicating with the control device. The control device further executes a question notification process that causes the notification device to notify the question stored in memory at a predetermined time, and an answer acquisition process that acquires the resident's answer to the question, which answer is input through the input interface, and the cook determination process is a process that determines a cook based on the answer.

[0011] Mental fatigue may not appear as a change in biometric data. The control device can identify mental fatigue that does not appear in biometric data based on the answers to the questions. Therefore, the cook selection system according to the present invention can select a cook based on the physical and mental fatigue of each resident.

[0012] (4) The question may have a plurality of question items, each of which may have a plurality of answer options, and the answer options may be associated with scores in memory. The cook determination process may determine the cook based on a total score calculated based on the answers.

[0013] Answers to each question are made by selecting an answer option, and each answer option is associated with a score, so the control device can quantify (score) the resident's mental fatigue and obtain it, and determine the level of mental fatigue of each resident based on the number.

[0014] (5) The physical condition identification process may be a process of identifying the physical condition of each resident based on the amount of variation in the biometric data relative to basic biometric data stored in a memory.

[0015] The physical condition of the resident is determined based on the amount of deviation of the biometric data from the basic biometric data, and the control device can therefore obtain the physical condition of the resident as a numerical value.

[0016] (6) The type of dish and the cooking level may be associated in memory. The control device further executes a menu determination process to determine a dish with a cooking level corresponding to the determined physical condition level of the responsible cook as the dish to be proposed to the responsible cook. The notification process is a process to notify the determined responsible cook and the type of dish.

[0017] For example, if all residents who can cook are in poor health and a resident in relatively good health is selected as the cook, dishes with a low cooking level, i.e., dishes that are easy to prepare, will be suggested to the selected resident, thereby reducing the burden on the unwell cook.

[0018] (7) The type of dish and the physical condition level may be associated in the memory. The control device further executes a menu determination process to determine the type of dish to be proposed to the cook according to the physical condition level of the resident other than the resident determined as the cook. The notification process is a process to notify the determined cook and the type of dish.

[0019] The menu (food) is decided based on the health condition of the residents other than the resident selected as the cook, and the cook is notified. As a result, residents who are not feeling well can eat easily digestible food such as porridge or boiled tofu.

[0020] (8) The cook determination process may determine to notify a suggestion stored in memory instead of a cook based on the determination that the health of the resident identified in the health identification process is worse than a threshold level for all residents who can cook, and the notification process may be a process of notifying the determined cook or the suggestion through the notification device.

[0021] If all residents who can cook are unwell, no one will be assigned to cook, and residents will be asked to order takeout.

[0022] (9) The suggestions may include contact information that has been previously stored in memory.

[0023] The contact information may be, for example, the phone number, email address, or URL of the store that delivers the food, or the phone number or email address of the parent who lives nearby. The resident contacts the store indicated by the notified contact information to order food delivery, or asks the parent who lives nearby to cook the food.

[0024] (10) A program according to the present invention includes a first program implemented in an information processing device having a first communication interface and a first computer, and a second program implemented in a user terminal having a display, a second communication interface, and a second computer. The second program causes the second computer to execute a biometric data acquisition process for acquiring biometric data from a biometric sensor that detects biometric data of multiple residents, and a biometric data transmission process for transmitting the acquired biometric data to the information processing device via the second communication interface. The first program causes the first computer to execute a health condition identification process for identifying the health condition of each resident at a predetermined time on a predetermined day based on the received biometric data, a cook determination process for determining a cook for the predetermined day based on the identified health condition of each resident, and a cook transmission process for transmitting the determined cook to the user terminal via the first communication interface. The second program causes the second computer to execute a notification process for displaying the received cook on the display.

[0025] The present invention can also be regarded as a program invention. [Effects of the Invention]

[0026] The cook decision system according to the present invention can prevent a resident who is not feeling well from cooking. [Brief explanation of the drawings]

[0027] [Figure 1] FIG. 1 is a configuration diagram and a functional block diagram of a cook determination system 10 according to an embodiment. [Figure 2] FIG. 2(A) is a diagram showing a user management database, FIG. 2(B) is a diagram showing a performance management database, FIG. 2(C) is a diagram showing a cooking database, and FIG. 2(D) is a diagram showing a question scoring table. [Figure 3] FIG. 3(A) is a diagram showing a biometric data scoring table, and FIG. 3(B) is a diagram showing a determination table. [Figure 4] FIG. 4 is a flowchart of the management process. [Figure 5] FIG. 5 is a part of a flowchart of the decision notification registration process. [Figure 6] FIG. 6 shows another part of the flowchart of the determination notification registration process. [Figure 7] FIG. 7(A) is a diagram showing the first screen, and FIG. 7(B) is a diagram showing the second screen. [Figure 8] FIG. 8(A) is a diagram showing the third screen, and FIG. 8(B) is a diagram showing the fourth screen. [Figure 9] FIG. 9(A) is a diagram showing a help request screen, and FIG. 9(B) is a diagram showing a help confirmation screen. [Figure 10] FIG. 10(A) is a diagram showing the first cook notification screen, and FIG. 10(B) is a diagram showing the menu recommendation screen. [Figure 11] FIG. 11(A) is a diagram showing the second cook notification screen, and FIG. 11(B) is a diagram showing the menu recommendation screen. DETAILED DESCRIPTION OF THE INVENTION

[0028] Hereinafter, an embodiment of the present invention will be described. Note that the embodiment described below is merely one example of the present invention, and it goes without saying that the embodiment of the present invention can be modified as appropriate without departing from the spirit of the present invention. Furthermore, the order of execution of each process (each step) shown in the flowcharts of Figures 4 to 6 may be changed as appropriate, some may be omitted, other processes may be added, or other equivalent processes may be substituted, without departing from the spirit of the present invention.

[0029] [Overview of Cooking Staff Decision System 10] The cook selection system 10 (see FIG. 1) described in this embodiment is a system that provides a service that selects and notifies a candidate to cook tonight's dinner. The service is provided to families in which there are multiple people who can cook (hereinafter also referred to as "qualified cooks") in one home. Qualified cooks include, for example, husbands, wives, mothers, fathers, and adult children. Those who cannot cook include, for example, underage children, elderly mothers, fathers, grandfathers, and grandmothers. Qualified cooks receive the service by downloading an application program provided by a service provider (hereinafter also referred to as "service provider") to their user terminals.

[0030] A service provider is, for example, a business that builds a house. The service provider provides a service using the cook decision system 10 as one of the various services it offers to the builder of the house. The various services include, for example, services related to home maintenance and services that support comfortable living in the house. The cook decision system 10 is operated in conjunction with, for example, systems that provide other services. For example, the cook decision system 10 provides data used by the other systems. Alternatively, the cook decision system 10 acquires data required for operation from the other systems. In other words, the cook decision system 10 also functions as a data collection system for the other systems.

[0031] However, the cook determination system 10 may be operated as a standalone system, or may be operated by a business operator other than the business operator that built the house.

[0032] [Configuration of Cook Decision System 10] 1, the cook determination system 10 includes multiple wearable devices 20, a user terminal 30, and a management server 40. Note that only one wearable device 20 is shown in FIG. 1, and the other wearable devices 20 are not shown.

[0033] [Wearable Device 20] The wearable device 20 is a device that acquires biometric data of a resident. The wearable device 20 may be a device owned by the resident, or may be a device sold or loaned to the resident by a service provider. For example, a general commercially available product may be used as the wearable device 20. The wearable device 20 is an example of a biometric sensor.

[0034] The wearable terminal 20 is used by being attached to the body of a resident who is qualified to cook. The attachment location may be any of the resident's arms, head, legs, torso, etc.

[0035] The wearable terminal 20 includes a CPU 21, which is a central processing unit, a terminal memory 22, a communication interface 23, a sensor group 24, and a communication bus (not shown) that connects these components.

[0036] The terminal memory 22 is configured by, for example, a ROM, a RAM, an EEPROM, or other storage elements, but may be configured by any type of storage element.

[0037] Although not shown in FIG. 1, the terminal memory 22 stores an OS, which is an operating system, a terminal program, and setting data required for communication with the user terminal 30.

[0038] The terminal program causes the CPU 21 to execute drive control of the various sensors in the sensor group 24, control of communication with the user terminal 30, and the like.

[0039] The setting data necessary for communication is data necessary for communication with the user terminal 30, such as the communication address of the user terminal 30 carried by the wearer of the wearable terminal 20. The setting data is registered in the wearable terminal 20 via the user terminal 30, for example.

[0040] The communication interface 23 is an interface for short-range wireless communication with the user terminal 30. Note that the wearable terminal 20 may be provided with a communication interface connected to the Internet 11 via a mobile communication network instead of or in addition to the communication interface 23.

[0041] The sensor group 24 includes various sensors that detect the wearer's body temperature, blood pressure, heart rate, respiratory rate, and sleep state. The various sensors are a temperature sensor 25, an optical sensor 26, an acceleration sensor 27, and a biopotential sensor 28.

[0042] The temperature sensor 25 receives, for example, infrared rays emitted by the wearer and outputs a temperature corresponding to the amount of infrared rays received, that is, the body temperature of the wearer.

[0043] The optical sensor 26 emits light toward the wearer and receives the light reflected by the wearer's blood vessels. The optical sensor 26 outputs data generated based on the time between the emission of the emitted light and the reception of the reflected light, the phase difference between the emitted light and the reflected light, and other factors. This data indicates the amount of blood flowing through the blood vessels (blood flow rate). The data output by the optical sensor 26 is used to generate biometric data indicating the wearer's blood pressure, heart rate, and whether or not they are asleep.

[0044] The acceleration sensor 27 outputs data corresponding to the tilt, impact, and vibration of the wearer's body. The data output by the acceleration sensor 27 is used to generate biometric data indicating the wearer's blood pressure, heart rate, respiratory rate, and whether or not the wearer is asleep.

[0045] Biopotential sensor 28 detects weak biopotentials emitted by the wearer and outputs data indicating an electrocardiogram, electroencephalogram, and electromyogram. The data output by biopotential sensor 28 is used to generate biodata indicating whether the wearer is asleep or not.

[0046] A terminal program (not shown) installed in the terminal memory 22 of the wearable terminal 20 generates biological data indicating the wearer's body temperature, sleep time, blood pressure, heart rate, and respiratory rate based on the data output by the sensor group 24. The terminal program transmits the biological data to the user terminal 30 via the communication interface 23 periodically or in response to a request from the user terminal 30.

[0047] [User terminal 30] The user terminal 30 is a communication terminal carried by a user (resident). The user terminal 30 is, for example, a smartphone (registered trademark), a tablet (registered trademark), or a personal computer (so-called PC).

[0048] The user terminal 30 may be owned by all residents belonging to a family, by only the competent cook, or by residents other than the competent cook. For example, if one user terminal 30 is configured to receive biometric data from multiple wearable devices 20 and transmit the data to the management server 40, there may be only one user terminal 30. In the following, an example will be described in which each resident who is competent to cook owns a user terminal 30, and a resident who is not competent to cook also owns a user terminal 30.

[0049] The user terminal 30 includes a CPU 31, which is a central processing unit, a terminal memory 32, communication interfaces 33 and 34, a touch panel 35, a speaker 36, and a clock module 37, as well as a communication bus (not shown) that connects these components. The CPU 31 is an example of a second computer.

[0050] The terminal memory 32 is configured by, for example, a ROM, a RAM, an EEPROM, a hard disk drive, a solid state drive (a so-called SSD), a USB memory, or other storage elements and storage devices. Note that the terminal memory 32 may be configured by any type of storage element and storage device.

[0051] The terminal memory 32 stores an operating system (OS) 38, an application program 39, and setting data required for communication. In Fig. 1, the application program 39 is abbreviated as "app 39." The terminal memory 32 is an example of a memory.

[0052] The application program 39 is a program downloaded from a website by the owner of the user terminal 30 and installed on the user terminal 30. The application program 39 may be a program that runs on a browser installed on the user terminal 30. The application program 39 has a function of acquiring biometric data from the wearable terminal 20 and transmitting the acquired biometric data to the management server 40. The application program 39 also has a function of displaying a screen on the touch panel 35 via the OS 38. The application program 39 also has a function of accepting user input via the touch panel 35. The application program 39 may be a single program, or may be a program consisting of multiple programs such as a short-range communication module, an Internet communication module, a UI (user interface) module, and a main body module. The application program 39 is an example of a second program.

[0053] The setting data necessary for communication is data necessary for communication with the wearable terminal 20 and the management server 40, such as the communication address of the wearable terminal 20 and the communication address of the management server 40. The setting data necessary for communication with the management server 40 is stored in the terminal memory 32 when the application program 39 is downloaded. The setting data necessary for communication with the wearable terminal 20 is registered in the user terminal 30 by the owner of the user terminal 30.

[0054] The communication interface 33 is an interface for performing short-range wireless communication. Examples of short-range wireless communication include wireless LAN (registered trademark) such as Wi-Fi (registered trademark) and Bluetooth (registered trademark). When the short-range wireless communication is wireless LAN, the user terminal 30 communicates with the wearable terminal 20 via a router or the like installed in the home. When the short-range wireless communication is Bluetooth (registered trademark), the user terminal 30 performs short-range wireless communication directly with the wearable terminal 20. There are no particular limitations on the communication standard (communication protocol) as long as the user terminal 30 can communicate with the wearable terminal 20.

[0055] The communication interface 34 is an interface for communicating with the management server 40 via a mobile communication network (not shown) and the Internet 11. The communication interfaces 33 and 34 are an example of a second communication interface.

[0056] The touch panel 35 includes a display and a transparent film-like touch sensor superimposed on the display. That is, the touch panel 35 functions not only as a display but also as an input interface that accepts user input. The user terminal 30 may also include a microphone that accepts voice input as an input interface. The touch panel 35 is an example of a notification device and a display. The touch panel 35 and the microphone are an example of an input interface.

[0057] The speaker 36 converts the input audio data into audio and outputs it.

[0058] The clock module 37 outputs date and time information. Note that the user terminal 30 does not need to include a clock module as long as the user terminal 30 is able to acquire date and time information via the Internet 11.

[0059] The user terminal 30 notifies the resident of today's cooking person received from the management server 40 by displaying it on the touch panel 35 or outputting it to the speaker 36. The user terminal 30, the touch panel 35, and the speaker 36 are examples of a notification device.

[0060] The clock module 37 outputs date and time information. If the user terminal 30 obtains date and time information through the communication interfaces 33 and 34, the user terminal 30 does not need to have the clock module 37.

[0061] [Administration Server 40] The management server 40 may be a server owned by the service provider, or may be a rental server that the service provider has the right to use.

[0062] The management server 40 may be a single server or a cloud server made up of multiple servers. The management server 40 is an example of an information processing device.

[0063] The management server 40 includes a CPU 41, which is a central processing unit, a server memory 42, a communication interface 43, and a communication bus (not shown) that connects these. The CPU 41 of the management server 40 is an example of a control device. The CPU 41 of the management server 40 and the CPU 31 of the user terminal 30 are also examples of a control device. The CPU 41 is an example of a first computer.

[0064] The communication interface 43 is connected to, for example, a gateway device (not shown) connected to the Internet 11. In other words, the management server 40 is connected to the Internet 11 via the gateway device. The communication interface 43 is an example of a first communication interface.

[0065] The server memory 42 is configured by, for example, a ROM, a RAM, an EEPROM, a hard disk drive, a solid state drive, a USB memory, or other storage elements and storage devices. Also, a part of the server memory 42 may be configured by a storage server.

[0066] The server memory 42 stores an OS 44, which is an operating system, a management program 45, and a management database.

[0067] Management program 45 is a program that executes the processes shown in Figures 4 to 6. Management program 45 may be a single program, or may be a program consisting of multiple programs such as a communication module, a UI module, and a main body module. Management program 45 is an example of a first program. Management program 45 and application program 39 are examples of programs.

[0068] The management database has the databases and tables shown in Figures 2 and 3. The management database has data that represents the tables and a control program that registers data in the tables and reads data from the tables. The management program 45 instructs the control program via the OS 44 to read and register (write) data.

[0069] The management database includes a user management database shown in Fig. 2(A) The user management database is a database in which information about users (residents) and information about families to which the users belong are registered.

[0070] The user management database has multiple columns with the names "User ID," "Name," "Relationship," "Gender," "Age," "Cooking qualification," "User terminal," "Terminal information," "Wearable," "Basic biometric data," "Address," "Helper information," and "Delivery store information."

[0071] The column field named "User ID" registers the user ID, which is identification information that individually identifies a user (resident). Each record (row) registered in the user management database is individually identified by the user ID.

[0072] The column named "User ID" has a sub-column named "Family" and a sub-column named "Individual." The field of the sub-column named "Family" registers a family ID that identifies the family to which the resident belongs. In other words, residents who belong to the same family have the same family ID. The field of the sub-column named "Individual" registers an ID that individually identifies each individual in the family to which the resident belongs. In other words, each resident can be identified both as a family unit and as an individual.

[0073] The field in the column named "First name" stores the first and last names of residents.

[0074] The field in the column named "Relationship" is where the contractor or the relationship (relationship) with the contractor is registered. A contractor is a person who has ordered the construction of a house from a service provider (constructor) or a person who has applied to the service provider to receive the service.

[0075] The field in the column named "gender" is registered as male or female.

[0076] The field of the column named "age" registers the age of the resident.

[0077] The field of the column named "Qualified to Cook" registers a qualified to cook flag. The qualified to cook flag is either "1" indicating that the person is qualified to cook or "0" indicating that the person is not qualified to cook.

[0078] Note that only residents who are qualified to cook can be selected as cooks, so residents who are not qualified to cook do not need to be registered in the user management database. However, if the selected cook is notified to residents other than the selected cook, residents who are not qualified to cook will also be registered in the user management database. Furthermore, if the cook selection system 10 also serves as an information collection system, or if the cook selection system 10 is linked to a system that provides other services, information about residents who are not qualified to cook will also be registered in the user management database to the extent possible.

[0079] In the field of the column named "User Terminal", "1" is registered, indicating that the resident possesses a user terminal 30, or "0" is registered, indicating that the resident does not possess a user terminal 30. Note that residents who do not possess a user terminal 30 do not need to be registered in the user management database.

[0080] The field in the column named "Terminal Information" registers information related to communication with the user terminal 30 owned by the resident. The information related to communication includes a communication address and an email address. The information related to communication is used, for example, when the management server 40 notifies the user terminal 30 of the determined cook.

[0081] The field in the column named "Wearable" is registered with "1" indicating that the resident is wearing the wearable terminal 20 and biometric data can be acquired, or "0" indicating that the resident is not wearing the wearable terminal 20 and biometric data cannot be acquired. Note that for residents whose cooking qualification is "1", "1" is always registered in the field in the column named "Wearable".

[0082] In the field of the column labeled "Basic Biometric Data," basic biometric data of residents, such as body temperature, is registered. The basic biometric data is used to determine the resident's physical condition. The resident's physical condition is also used to determine the type of dish to be proposed, as well as to determine the cook. Therefore, it is desirable to register basic biometric data not only for residents who are qualified to cook, but also for other residents. Furthermore, if the cook selection system 10 also serves as an information collection system, or if the cook selection system 10 is linked to a system that provides other services, it is desirable to register basic biometric data of residents who are not qualified to cook in the user management database.

[0083] The column entitled "Basic Biological Data" has a number of sub-columns entitled "Body Temperature," "Sleep Hours," "Blood Pressure," "Heart Rate," and "Respiration Rate," respectively.

[0084] The field of the subcolumn named "body temperature" registers the resident's normal body temperature. The normal body temperature may be the average of body temperatures previously detected by the wearable device 20, a general body temperature according to the resident's gender and age, or a body temperature declared by the resident through the application program 39.

[0085] The sub-column field named "Sleep Hours" registers the resident's usual sleep hours. The usual sleep hours may be the average sleep hours previously detected by the wearable device 20, the typical sleep hours according to the resident's gender and age, or the sleep hours declared by the resident through the application program 39.

[0086] The sub-column field named "Blood Pressure" registers the resident's normal blood pressure. The normal blood pressure may be the average blood pressure previously detected by the wearable device 20, a general blood pressure according to the resident's gender and age, or a blood pressure reported by the resident through the application program 39.

[0087] The sub-column field named "Heart Rate" registers the resident's normal heart rate. The normal heart rate may be the average heart rate previously detected by the wearable device 20, a general heart rate according to the resident's gender and age, or a heart rate reported by the resident through the application program 39.

[0088] The field of the subcolumn named "Respiration Rate" registers the resident's normal respiration rate. The normal respiration rate may be the average respiration rate previously detected by the wearable device 20, a general respiration rate according to the resident's gender and age, or a respiration rate declared by the resident through the application program 39.

[0089] The field of the column named "Address" is where the addresses of residents (family members) are registered.

[0090] The field of the column named "Helper Information" is used to register information about people who can provide cooking assistance to the family (hereinafter referred to as "helpers"), such as parents who live close to the family home. This information includes the helper's name, address, phone number, email address, etc. If there is no helper, "0" is registered to indicate that there is no helper.

[0091] The field of the column named "Delivery Store Information" stores information about stores that can deliver food to the family's home (hereinafter referred to as "delivery stores"). This information includes the name of the delivery store, the type of delivery store, the names of dishes that can be delivered, the price, a phone number, an email address, a URL, etc. The types of delivery stores include Chinese, pizza, Japanese food, sushi, etc.

[0092] The user inputs the following information into the user terminal 30: "Name," "Relationship," "Gender," "Age," "Cooking qualification," "User terminal," "Terminal information," "Wearable," "Basic biometric data," "Address," and "Helper information" when or after downloading the application program 39 to the user terminal 30. The application program 39 then transmits application data containing the input "Name," "Relationship," "Gender," "Age," "Cooking qualification," "User terminal," "Terminal information," "Wearable," "Basic biometric data," "Address," and "Helper information" to the management server 40 via the Internet 11. Upon receiving the application data, the management program 45 of the management server 40 creates a new record in the user management database, assigns a unique user ID to the created record, and registers the "Name," "Relationship," "Gender," "Age," "Cooking qualification," "User terminal," "Terminal information," "Wearable," "Basic biometric data," "Address," and "Helper information" included in the application data.

[0093] The management database may have a correspondence table that associates general basic biometric data with gender and age. In this case, the management server 40 obtains basic biometric data corresponding to the "gender" and "age" included in the application data from the table and registers it in a newly created record. In other words, the data declared by the user may be used as the initial basic biometric data, or general data according to gender and age may be used. The management server 40 may then update the initial basic biometric data to suit the characteristics of each resident based on the biometric data obtained by the wearable device 20.

[0094] In addition, if the service provider is a construction company that built the house in which the resident lives, the ``name,'' ``relationship,'' ``gender,'' ``age,'' ``eligibility to cook,'' ``user terminal,'' ``terminal information,'' ``wearable,'' ``basic biometric data,'' ``address,'' and ``helper information'' may be registered in the user management database by an operator of the service provider who interviews the resident when the house is ordered (receives an order) or after construction.

[0095] Furthermore, the "Name," "Relationship," "Gender," "Age," "Cooking qualification," "User terminal," "Terminal information," "Wearable," "Basic biometric data," "Address," and "Helper information" may be sent to the management server 40 by each resident using their own user terminal 30, or may be sent to the management server 40 by a contractor on their behalf. Information about residents who do not have a user terminal 30 is sent to the management server 40 by a resident who has a user terminal 30, such as a contractor.

[0096] The "delivery store information" may be registered in the user management database by the resident himself / herself searching for and selecting a store and sending it to the management server 40 using the user terminal 30, or the management program 45 may search based on the resident's address registered in the user management database and register it in the user management database.

[0097] The management database includes the track record management database shown in FIG. 2(B). The track record management database is a database in which the user IDs of previously determined cooks are registered in association with dates. Each record registered in the track record management database is mutually identified using a family ID. That is, for each family, the user ID of the resident who has become the cook is registered in association with a date. Note that if no cook is determined and a helper provides cooking assistance or if a delivery order is placed, "0" is registered in the track record management database instead of the user ID.

[0098] The management database includes the recipe database shown in Figure 2(C). The recipe database is a database that manages data on each dish. The recipe database has multiple columns named "dish name," "cooking level," and "total score (physical condition level)."

[0099] The column field named "Dish Name" is where the names of dishes such as Twice Cooked Pork, Rice Porridge, and Yudofu are registered. In other words, a record is created for each dish name.

[0100] The field in the column named "Cooking Level" is registered with either "0" indicating that the dish is easy to prepare or "1" indicating that it is time-consuming to prepare. In other words, a dish with a cooking level of "0" indicates that it is easy to prepare, and a dish with a cooking level of "1" indicates that it is carefully prepared. If the resident selected as the cook is in good health, a dish (menu) with a cooking level of "1" will be suggested to the cook, and if the resident selected as the cook is in poor health, a dish (menu) with a cooking level of "0" will be suggested to the cook.

[0101] The field of the column named "Total Score (Physical Condition Level)" registers a total score indicating the physical condition level. The physical condition level indicates the physical condition of the person for whom the dish is suitable. For example, porridge and boiled tofu have a total score (physical condition level) of "5 or more" and are suitable for people who are not feeling well, while double-cooked pork has a total score (physical condition level) of 4 or less and is suitable for people in good physical condition.

[0102] The dishes proposed (recommended) to the resident selected as the cook are determined (selected) based on the physical condition of the resident selected as the cook and the physical condition of the other residents who will be eating the dishes.

[0103] The management database includes a question scoring table shown in FIG. 2(D). The question scoring table is a table that associates answer options selected by residents in response to questions with scores. In the example shown in FIG. 2(D), the answer option "No problem" for the question asking about "feelings" is associated with "0" points, the answer option "Tired" is associated with "2" points, and the answer option "Can't recover" is associated with "5" points. Furthermore, the answer option "No problem" for the question asking about "sleepiness" is associated with "0" points, and the answer option "Sleepy" is associated with "1" points. Furthermore, the answer option "Days 1-3" for the question "Menstruation," which is restricted to women, is associated with "1" points, and the answer option "Other" is associated with "0" points. "Feelings," "Sleepiness," and "Menstruation" are examples of question items.

[0104] The question scoring table quantifies mental fatigue that does not appear in biometric data.

[0105] The management database includes a biometric data scoring table shown in Fig. 3(A). The biometric data scoring table is a table for scoring the biometric data of the resident acquired by the wearable device 20 using the basic biometric data registered in the user management database (see Fig. 2(A)).

[0106] The biological data scoring table has records related to "body temperature," "sleep hours," "blood pressure," "heart rate," and "respiratory rate."

[0107] In the record related to "body temperature," a score is assigned on a four-level scale according to the deviation of the resident's body temperature today from the body temperature A in the basic biological data, which is the normal body temperature (absolute value of "A - body temperature"). Specifically, if the deviation is 0.4°C or less, the score is "0." If the deviation is more than 0.4°C and less than 0.8°C, the score is "1." If the deviation is more than 0.8°C and less than 1.6°C, the score is "3." If the deviation is more than 1.6°C, the score is "5." Note that today's body temperature is the body temperature at a predetermined time a predetermined time before the time to start cooking dinner.

[0108] Records related to "sleep time" are scored on a four-point scale according to the amount of deviation in the resident's sleep time last night from sleep time B in the basic biological data, which is their normal sleep time. Specifically, if last night's sleep time was 90% of their normal sleep time (0.9 times or more), they receive a score of "0." If last night's sleep time was 80% of their normal sleep time (0.8 times or more but less than 0.9 times), they receive a score of "1." If last night's sleep time was 60% of their normal sleep time (0.6 times or more but less than 0.8 times), they receive a score of "3." If last night's sleep time was less than 60% of their normal sleep time, they receive a score of "5."

[0109] In records related to "blood pressure," a score is assigned in two stages according to the deviation of the resident's blood pressure today from the blood pressure C of the basic vital data, which is the normal blood pressure (absolute value of "C - blood pressure"). If the deviation is 5 mmHg or less, the score is "0," and if the deviation is more than 5 mmHg, the score is "1." Note that today's blood pressure is the blood pressure at the specified time.

[0110] In the record related to "heart rate," a score is assigned in two stages according to the deviation of the resident's heart rate today from the heart rate D of the basic biological data, which is the normal heart rate (absolute value of "D - heart rate"). If the deviation is 7 beats / minute or less, the score is "0," and if the deviation is more than 7 beats / minute, the score is "1." Note that today's heart rate is the heart rate at the specified time.

[0111] In the record related to "respiratory rate," a score is assigned in two stages according to the deviation of the resident's current respiratory rate from the respiratory rate E of the basic biological data, which is the normal respiratory rate (absolute value of "E - respiratory rate"). If the deviation is 3 breaths / minute or less, the score is "0," and if the deviation is more than 3 breaths / minute, the score is "1." Note that the current respiratory rate is the respiratory rate at the specified time.

[0112] The biometric data scoring table quantifies the physical fatigue of residents.

[0113] The management database includes a judgment table shown in Figure 3(B). The judgment table is a table for identifying the current physical condition of residents who are qualified to cook and determining who will be responsible for cooking. The judgment table is generated or updated daily. Note that the current physical condition refers to the physical and mental fatigue at the specified time.

[0114] The judgment table has multiple columns named "User ID," "Name," "Biometric data score," "Question answer score," "Total score," "Continuous in-charge flag," "Cooking in-charge flag," and "Help / Delivery flag."

[0115] In the fields of the columns named "User ID" and "Name", the user ID and the name of the resident are registered, respectively, as in the user management database (see FIG. 2(A)).

[0116] Each record is identified for each family by the family ID registered in the field of the column named "Family" in "User ID." In other words, a record is created for each family. Each record has a sub-record created for each resident included in the family who has "1" registered in "Wearable" in the user management database (see FIG. 2(A)). In other words, the physical condition of only the resident wearing the wearable device 20 is identified. Note that a sub-record may also be created for a resident who does not wear the wearable device 20. In this case, the physical condition of the resident who does not wear the wearable device 20 is identified only from the answers to the questions. The physical condition identified for the resident who does not wear the wearable device 20 is used to determine the type of food to be proposed to the resident who is selected as the cook.

[0117] The column named "Biometric Data Score" has sub-columns named "Body Temperature," "Body Temperature Score," "Sleep Time," "Sleep Score," "Blood Pressure," "Blood Pressure Score," "Heart Rate," "Heart Rate Score," "Respiration Rate," and "Respiration Score."

[0118] The sub-column named "body temperature" registers the body temperature of the resident acquired by the wearable device 20.

[0119] The field of the subcolumn named "body temperature score" registers a body temperature score determined based on the resident's body temperature acquired by the wearable device 20. More specifically, the management program 45 of the management server 40 calculates the absolute value of the difference between the acquired "resident's body temperature today" and "the resident's normal body temperature A." The "resident's normal body temperature A" is the body temperature in the basic biometric data registered in the user management database (see FIG. 2(A)). The management program 45 determines a score based on the calculated "absolute value of the difference between normal body temperature A and today's body temperature" and the biometric data scoring table, and registers the determined score in the field of the subcolumn named "body temperature score." In the example of "Yamada Taro" in the judgment table, the body temperature in the basic biometric data is 36.6°C and today's body temperature is 37.5°C, so the absolute value of the difference is 0.9°C. In the biometric data scoring table, "0.9°C" is associated with "3" points.

[0120] The sub-column named "sleep time" is where the sleep time of the resident acquired by the wearable device 20 is registered.

[0121] The sub-column field named "Sleep Score" registers a sleep score determined based on the resident's sleep time last night acquired by the wearable device 20. More specifically, the management program 45 of the management server 40 reads the resident's normal sleep time B from the user management database (see FIG. 2(A)). The management program 45 calculates what percentage of the "resident's sleep time last night" is the "resident's normal sleep time." The management program 45 determines a score based on the calculated percentage and the biometric data scoring table, and registers the determined score in the sub-column field named "Sleep Score." In the example of "Yamada Taro" in the determination table, the sleep time in the basic biometric data is 6.5 hours and the sleep time last night is 5.5 hours. Therefore, the "resident's sleep time last night" is 8.4% of the "resident's normal sleep time," and the score associated with "8.4%" in the biometric data scoring table is "1."

[0122] The sub-column named "Blood Pressure" registers the blood pressure of the resident acquired by the wearable device 20.

[0123] The sub-column field named "Blood Pressure Score" registers a blood pressure score determined based on the resident's blood pressure acquired by the wearable device 20. Specifically, the management program 45 of the management server 40 calculates the absolute value of the difference between the acquired "resident's today's blood pressure" and the "resident's normal blood pressure C." The "resident's normal blood pressure C" is the blood pressure in the basic biometric data registered in the user management database (see FIG. 2(A)). The management program 45 determines a score based on the calculated "absolute value of the difference between normal blood pressure C and today's blood pressure" and the biometric data scoring table, and registers the determined score in the sub-column field named "Blood Pressure Score." In the example of "Yamada Taro" in the judgment table, the blood pressure in the basic biometric data is 125 mmHg and the blood pressure today is 135 mmHg, so the absolute value of the difference is 10 mmHg. In the biometric data scoring table, "10 mmHg" corresponds to "1" point.

[0124] The sub-column named "heart rate" registers the resident's heart rate acquired by the wearable device 20.

[0125] A field in the subcolumn named "heart rate score" registers a heart rate score determined based on the resident's heart rate acquired by the wearable device 20. More specifically, the management program 45 of the management server 40 calculates the absolute value of the difference between the acquired "resident's heart rate today" and the "resident's normal heart rate D." The "resident's normal heart rate D" is the heart rate in the basic biometric data registered in the user management database (see FIG. 2(A)). The management program 45 determines a score based on the calculated "absolute value of the difference between the normal heart rate D and today's heart rate" and the biometric data scoring table, and registers the determined score in the field in the subcolumn named "heart rate score." In the example of "Yamada Taro" in the determination table, the heart rate in the basic biometric data is 72 beats per minute, and the heart rate today is 80 beats per minute, so the absolute value of the difference is 8 beats per minute. In the biometric data scoring table, "8 times" corresponds to "1" point.

[0126] The sub-column named "Respiration rate" is where the resident's respiration rate acquired by the wearable device 20 is registered.

[0127] A field in the subcolumn named "Respiration Score" registers a respiration score determined based on the resident's respiration rate acquired by the wearable device 20. More specifically, the management program 45 of the management server 40 calculates the absolute value of the difference between the acquired "resident's respiration rate today" and the "resident's normal respiration rate E." The "resident's normal respiration rate E" is the respiration rate in the basic biometric data registered in the user management database (see FIG. 2(A)). The management program 45 determines a score based on the calculated "absolute value of the difference between the normal respiration rate E and the today's respiration rate" and the biometric data scoring table, and registers the determined score in the field in the subcolumn named "Respiration Score." In the example of "Yamada Taro" in the determination table, the respiration rate in the basic biometric data is 16 breaths / minute and the today's respiration rate is 20 breaths / minute, so the absolute value of the difference is 4 breaths / minute. In the biometric data scoring table, "4 breaths" is associated with "1" point.

[0128] The field in the column named "Question Answer Score" stores the resident's answers to each question asked to them, such as "feelings," "sleepiness," and "menstruation," as well as the score determined from the question scoring table (see Figure 2(D)).

[0129] The field of the column named "Total Score" registers the total score of the biometric data score and the question answer score. In the example of "Yamada Taro" in the judgment table, the biometric data scores are "3", "1", "1", "1", and "1", and the question answer scores are "2", "1", and "0", so the total score is "10". The total score is an example of physical condition and physical condition level.

[0130] In the field of the column named "Continuous Cooking Flag," a "1" is registered if the resident was in charge of cooking for two consecutive days, yesterday and the day before yesterday, and a "0" is registered otherwise. The management program 45 of the management server 40 registers a "1" or a "0" in the field of the column named "Continuous Cooking Flag" based on the data registered in the performance management database (see FIG. 2(B)). Note that if a request for cooking assistance from a helper or an order for delivery is placed but the resident is not cooking, "two consecutive days" is determined excluding the day on which the resident did not cook. For example, if a resident cooked one day ago (yesterday) and three days ago and ordered delivery two days ago (the day before yesterday), a continuous cooking flag is registered for that resident. The continuous cooking flag is an example of performance data.

[0131] The field of the column named "Cook Flag" registers "1" if the resident has been selected as the cook for today, and "0" if the resident is not the cook for today. The management program 45 of the management server 40 determines the cook in the selection notification registration process shown in Figures 5 and 6, and registers "1" for the resident selected as the cook and "0" for other residents.

[0132] The field of the column named "Help / Delivery Flag" is registered with "1" indicating that a request for cooking assistance has been made to a helper or that a delivery has been requested, or "0" indicating that a person has been selected to be in charge of cooking. The management program 45 of the management server 40 registers "1" in the field of the column named "Help / Delivery Flag" when it has been decided to request assistance from a helper or to request delivery in the decision notification registration process shown in Figures 5 and 6, and registers "0" when it has been decided that a person will be in charge of cooking.

[0133] [Operation of Cooking Person Determination System 10] The following describes the management processing (see FIG. 4) executed by the management server 40 and the user terminal 30. Note that each process (each step) executed by the management server 40 in the management processing is a process executed by the CPU 41 of the management server 40, and is also a process that the management program 45 of the management server 40 causes the CPU 41 to execute. Also, each process (each step) executed by the user terminal 30 in the management processing is a process executed by the CPU 31 of the user terminal 30, and is also a process that the application program 39 of the user terminal 30 causes the CPU 31 to execute.

[0134] As shown in FIG. 4, the wearable device 20 acquires biometric data and temporarily stores the acquired biometric data in the device memory 22 (S11). The biometric data is acquired, for example, at predetermined time intervals or at predetermined times. The wearable device 20 establishes communication (handshake) with the user terminal 30 through the communication interface 23 (S12) and then transmits the acquired biometric data to the user terminal 30 (S13). The establishment of communication in step S12 may be performed, for example, at intervals longer than the biometric data acquisition interval, and multiple sets of biometric data may be transmitted collectively to the user terminal 30, or an average value of the multiple sets of biometric data may be transmitted to the user terminal 30. Alternatively, the wearable device 20 may transmit the most recent biometric data to the user terminal 30 in response to a request from the user terminal 30. That is, the wearable device 20 may transmit biometric data periodically or only when necessary.

[0135] The user terminal 30 receives the biometric data transmitted by the wearable terminal 20 via the communication interface 33 (S13). The process of step S13 is an example of a biometric data acquisition process. The user terminal 30 performs the biometric data acquisition process every day. Every day is an example of a predetermined day.

[0136] The user terminal 30 temporarily stores the received biometric data in the terminal memory 32 (S14). The user terminal 30 also determines whether a predetermined time has arrived (S15). The predetermined time is a predetermined time (e.g., one hour) before the time to start cooking dinner. The user terminal 30 repeatedly executes the processes from steps S12 to S14 until the predetermined time arrives (S15: No).

[0137] When the user terminal 30 determines that the predetermined time has arrived (S15: Yes), it displays a question and answer screen (see FIGS. 7 and 8) on the touch panel 35 (S16). Specifically, the terminal memory 32 of the user terminal 30 pre-stores screen data showing the question and answer screen. The screen data is, for example, HTML data, and is stored in the terminal memory 32 when the application program 39 is downloaded. The user terminal 30 displays the question and answer screen on the touch panel 35 by inputting the screen data stored in the terminal memory 32 into the touch panel 35. Note that the screen data showing the question and answer screen may be stored in the server memory 42. In this case, the user terminal 30 obtains the screen data from the management server 40 via the Internet 11. The processing of step S16 is an example of a question notification process.

[0138] The question and answer screen includes a first screen shown in Fig. 7(A), a second screen shown in Fig. 7(B), a third screen shown in Fig. 8(A), and a fourth screen shown in Fig. 8(B). The user terminal 30 first displays the first screen shown in Fig. 7(A) on the touch panel 35.

[0139] The first screen has the text "Please select how you feel today" and a "Next" icon 50. The resident carrying the user terminal 30 selects the "Next" icon 50.

[0140] When the "Next" icon 50 is selected on the first screen (S17 in FIG. 4), the user terminal 30 displays the second screen shown in FIG. 7(B) on the touch panel 35.

[0141] The second screen has the text "How are you feeling today?", a radio button 51 and the text "No problem" that are associated with each other, a radio button 52 and the text "I'm exhausted" that are associated with each other, a radio button 53 and the text "I can't recover" that are associated with each other, and a "Next" icon 54. A resident who has user terminal 30 selects any of radio buttons 51, 52, 53 and then selects "Next" icon 54.

[0142] When the "Next" icon 54 is selected on the second screen (S17 in FIG. 4), the user terminal 30 displays the third screen shown in FIG. 8(A) on the touch panel 35.

[0143] The third screen has the text "How sleepy were you during the day today?", a radio button 55 and the text "No problem" that are associated with each other, a radio button 56 and the text "I felt sleepy" that are associated with each other, and a "Next" icon 57. A resident who has the user terminal 30 selects either of the radio buttons 55, 56 and then selects the "Next" icon 57.

[0144] When the "Next" icon 57 is selected on the third screen (S17 in FIG. 4), the user terminal 30 displays the fourth screen shown in FIG. 8(B) on the touch panel 35.

[0145] The fourth screen has the words "Menstrual Cycle", a radio button 58 and the words "Days 1-3" that are associated with each other, a radio button 59 and the words "Other", and an "End" icon 60. A resident carrying the user terminal 30 selects either radio button 58 or 59, and then selects the "End" icon 60.

[0146] The fourth screen is displayed on the touch panel 35 only on user terminals 30 owned by female residents. The application program 39 stores the gender of the owner of the user terminal 30 in the terminal memory 32 in advance, and if the gender stored in the terminal memory 32 is female, the fourth screen is displayed on the touch panel 35, but if the gender is male, the fourth screen is not displayed on the touch panel 35. On user terminals 30 owned by male residents, an "Exit" icon 60 is displayed on the third screen instead of the "Next" icon 57.

[0147] The process of step S17 in which the user terminal 30 accepts the selection of the radio buttons 51 to 53, 55, 56, 58, and 59 by the resident is an example of an answer acquisition process. Moreover, the radio buttons 51 to 53, 55, 56, 58, and 59 are an example of answer options.

[0148] 4, when the "End" icon 60 is selected on the third or fourth screen (S17), the user terminal 30 temporarily stores answer information in the terminal memory 32 (S18). The answer information is information indicating the radio button selected by the resident in response to the question.

[0149] The user terminal 30 generates transmission data including the biometric data and answer information temporarily stored in the terminal memory 32, and the user ID previously stored in the terminal memory 32 (S19). The user terminal 30 transmits an HTTP request including the generated transmission data to the management server 40 via the communication interface 33 or the communication interface 34 and the Internet 11 (S20). Hereinafter, the communication interface 33 or the communication interface 34 will also be referred to as the communication interface 33, etc. The processing of step S20 is an example of a biometric data transmission process.

[0150] The management server 40 receives the HTTP request sent by the user terminal 30 (S20). The management server 40 returns an HTTP response including an ACK (acknowledgement) indicating that the HTTP request has been received to the user terminal 30 via the communication interface 43 and the Internet 11 (S21). The processing of step S20 in which the management server 40 receives the HTTP request including the question and answer and biometric data is an example of an answer acquisition process and a biometric data acquisition process.

[0151] The management server 40 identifies a record in the user management database (see FIG. 2(A)) that has a user ID that matches the user ID included in the transmission information received in step S20. The management server 40 reads out the data registered in the identified record and temporarily stores it in the calculation processing area in the server memory 42 (S22).

[0152] The management server 40 scores the biometric data of the resident based on the basic biometric data read out in step S22, the biometric data received in step S20, and the biometric data scoring table (see FIG. 3(A)) (S23). The management server 40 registers the scores related to the biometric data in the judgment table (see FIG. 3(B)) (S23). For example, for the name "Yamada Taro" in the judgment table, a body temperature score of "3", a sleep score of "1", a blood pressure score of "1", a heart rate score of "1", and a respiration score of "1" are registered in the judgment table. Note that the scores related to the biometric data mainly indicate the resident's physical fatigue level, with a higher score indicating a higher level of physical fatigue and a lower score indicating a lower level of physical fatigue. A high level of physical fatigue of a resident indicates poor physical health, and a low level of physical fatigue of a resident indicates good physical health.

[0153] The management server 40 also scores the resident's answer to the question based on the answer information received in step S20 and the question scoring table (see FIG. 2(D)) (S24). The management server 40 registers the scores for the question and answer in a judgment table (see FIG. 3(B)) (S24). For example, for the name "Yamada Taro" in the judgment table, mood is registered with a score of "2", sleepiness with a score of "1", and menstruation with a score of "0". The score for the question and answer indicates the resident's mental fatigue level, with a higher score indicating a higher mental fatigue and a lower score indicating a lower mental fatigue. High mental fatigue indicates a poor state of mind, and low mental fatigue indicates a good state of mind.

[0154] The management server 40 calculates a total score by adding the score for the biometric data calculated in step S23 and the score for the question answer calculated in step S24 (S25). The management server 40 registers the calculated total score in the judgment table (see FIG. 3(B)) (S25). The processes from steps S22 to S25 for calculating the total score and registering it in the judgment table are an example of a physical condition identification process.

[0155] Furthermore, management server 40 identifies a record having a family ID that matches the family ID, which is the family portion of the user ID received in step S20, and reads out the user ID of the resident who was in charge of cooking yesterday and the user ID of the resident who was in charge of cooking the day before yesterday. If the two read user IDs match, management server 40 registers a consecutive cooking flag of "1" in the judgment table for the record having the user ID that matches the user ID of the resident who was in charge of cooking for two consecutive days, and registers a consecutive cooking flag of "0" for the records of other residents (S26).

[0156] The management server 40 executes a determination notification registration process to determine who will cook or who will provide help / delivery based on the total score and the consecutive cooking flag, and notifies and registers the determination (S27).

[0157] Details of the determination notification registration process will be described with reference to Figures 5 and 6. The determination notification registration process is executed for each family.

[0158] As shown in Fig. 5, the management server 40 determines whether the total score of all residents who are qualified to cook is 5 points or more in the determination table (see Fig. 3(B)) (S31). The total score of "5 points" is an example of a threshold level.

[0159] When the management server 40 determines that the total score of all residents who are qualified to cook is 5 points or more (S31: Yes), it determines whether all of the residents selected "I can't recover" in the question and answer section (S32). The determination in step S32 is made based on whether a score of 5 is registered for "feelings" in the determination table.

[0160] If the management server 40 determines that all residents who are qualified to cook have selected "can't recover" in the question answer (S32: Yes), it determines whether helper information (see FIG. 2(A)) is registered in the record read from the user management database in step S22 (S33). That is, in step S33, it is determined whether there is a helper who can request cooking assistance for the target family.

[0161] If the management server 40 determines that helper information has been registered (S33: Yes), it reads out the helper information from the user management database (see FIG. 2(A)) (S34). Meanwhile, the user terminal 30 (application program 39) owned by each resident periodically sends an HTTP request including inquiry information to the management server 40 via the communication interface 33 or the like and the Internet 11 (S35). In response to the received HTTP request, the management server 40 sends an HTTP response including the helper information read out in step S34 to the user terminal 30 via the communication interface 43 and the Internet 11 (S36). The helper information is an example of a suggestion notified to a resident. The address, telephone number, and email address of the helper included in the helper information are examples of contact information.

[0162] The user terminal 30 that transmits the helper information may be a user terminal 30 owned by a resident who has been pre-registered in the user management database as a representative, a user terminal 30 owned by a resident who is qualified to cook, a user terminal 30 owned by a resident with the lowest overall score (in the best physical condition), or all user terminals 30.

[0163] The user terminal 30 receives the HTTP response via the communication interface 33 or the like (S36). The user terminal 30 generates a help transmission format based on the helper information included in the received HTTP response, and displays it on the touch panel 35 (S37). More specifically, the terminal memory 32 of the user terminal 30 stores format data for the help request screen when the application program 39 is downloaded. The user terminal 30 inputs the helper information (first and last name of the helper) received in step S36 into the input fields of the format data to generate help request screen data, and displays the help request screen (see FIG. 9(A)) on the touch panel 35.

[0164] As shown in FIG. 9(A), the help request screen has the text "Everyone is unwell," the text "Would you like to request cooking assistance from Mr. / Ms. 00?", a "Request" icon 61, and a "Do not request" icon 62. The processing of step S37 is an example of a notification process. The owner (resident) of the user terminal 30 on which the help request screen is displayed selects the "Request" icon 61 if they wish to request assistance (S38 in FIG. 5), and selects the "Do not request" icon 62 if they do not wish to request assistance (S38 in FIG. 5).

[0165] 5, when the resident selects the "Request" icon 61, the user terminal 30 uses the helper information received in step S36 to send information indicating a request for cooking assistance to the communication terminal carried by the helper (S39). Note that instead of a request for cooking assistance, a request to buy ready-to-eat foods or the like may be sent to the helper. The helper who receives the request for cooking assistance can accept or decline the request.

[0166] After transmitting the information indicating a request for cooking assistance, the user terminal 30 displays a help confirmation screen (see FIG. 9(B)) on the touch panel 35 (S40). The help confirmation screen is a screen for confirming whether the helper has accepted or declined the cooking assistance.

[0167] 9(B), the help confirmation screen has the text "Can I receive cooking help from Mr. / Ms. 00?", a "Yes" icon 63, and a "No" icon 64. If the helper accepts the request for cooking help, the owner (resident) of the user terminal 30 selects the "Yes" icon 63 (S41 in FIG. 5), and if the helper declines the request for cooking help or is unable to receive a reply, the owner (resident) of the user terminal 30 selects the "No" icon 64 (S41 in FIG. 5).

[0168] The user terminal 30 generates an HTTP request including help notification information indicating whether or not the user is available to receive cooking assistance from a helper, and sends the generated HTTP request to the management server 40 via the communication interface 33, etc. and the Internet 11 (S42).

[0169] The management server 40 receives the HTTP request through the communication interface 43 (S42). The management server 40 determines whether the help notification information received in step S42 indicates that the helper has accepted cooking support (S43). If the management server 40 determines that the helper has accepted cooking support (S43: Yes), it registers a help / delivery flag of “1” in the determination table (see FIG. 3(B)), and registers “0” in the field of the column named “Cook” in the performance management database (S44), and terminates the decision notification registration process (S27 in FIG. 4). On the other hand, if the management server 40 determines that the helper has declined cooking support (S43: No), it returns an HTTP response including the delivery restaurant information read from the user management database (see FIG. 2(A)) in step S22 to the user terminal 30 via the communication interface 43 and the Internet 11 as a response to the HTTP request received in step S42 (S45). The delivery store information is an example of a proposal that is notified to the resident. The telephone number, email address, and URL included in the delivery store information are examples of contact information.

[0170] The user terminal 30 receives the HTTP response including the delivery restaurant information via the communication interface 33 or the like (S45). The user terminal 30 displays a delivery restaurant display screen (not shown) containing the received delivery restaurant information on the touch panel 35 (S46). The delivery restaurant display screen has text indicating the restaurant name, dish name, and price, as well as an "OK" icon. The processing of step S46 is an example of notification processing. The resident selects a delivery restaurant and dish from the delivery restaurants displayed on the touch panel 35 and places an order. After checking the delivery restaurant name, dish name, etc., the resident selects the "OK" icon (S47).

[0171] Based on the selection of the "OK" icon on the delivery store display screen, the user terminal 30 sends an HTTP request including delivery information indicating that delivery has been ordered to the management server 40 via the communication interface 33, etc. and the Internet 11 (S48).

[0172] The management server 40 receives the HTTP request through the communication interface 43 (S48). Although not shown in Fig. 5, the management server 40 returns an HTTP response including an ACK (acknowledgement) indicating that the HTTP request has been received to the user terminal 30 through the communication interface 43 and the Internet 11.

[0173] In step S48, based on receiving the delivery notification information, the management server 40 registers a help / delivery flag of "1" in the judgment table (see Figure 3(B)), and also registers "0" in the field of the column named "Cook" in the performance management database (S44), and terminates the decision notification registration process (S27 in Figure 4).

[0174] If the management server 40 determines in step S33 that the helper information is not registered in the user management database (see FIG. 2(A)) (S33: No), it returns an HTTP response including the delivery restaurant information read from the user management database in step S22 to the user terminal 30 as a response to the HTTP request received in step S35 (S45). The user terminal 30 to which the HTTP response including the delivery restaurant information is returned may be a user terminal 30 owned by a resident who is registered in advance in the user management database as a representative, a user terminal 30 owned by a resident who is qualified to cook, a user terminal 30 owned by the resident with the lowest overall score (in best physical condition), or all user terminals 30.

[0175] In this way, if all residents have selected "can't recover" (S32: Yes) and a helper is registered (S33: Yes), the resident is suggested to ask the helper for cooking assistance, and if no helper is registered (S33: No), the resident is suggested to order from a food delivery restaurant. Also, if all residents are feeling unwell (S31: Yes) but even one resident has not selected "can't recover," the resident is suggested to order from a food delivery restaurant.

[0176] If the management server 40 determines in step S32 that not all residents have selected the answer "I can't recover" (S32: No), that is, if it determines that there is even one resident who has not selected the answer "I can't recover," it returns an HTTP response including the delivery restaurant information read from the user management database in step S22 to the user terminal 30 as a response to the HTTP request received in step S35 (S45). Note that the user terminal 30 to which the HTTP response including the delivery restaurant information is returned is the user terminal 30 owned by the resident who has not selected the answer "I can't recover." However, the user terminal 30 to which the HTTP response including the delivery restaurant information is returned may be the user terminal 30 owned by a resident who is registered in advance in the user management database as a representative, or the user terminal 30 owned by a resident who is qualified to cook, or the user terminal 30 owned by the resident with the lowest overall score (the resident in the best physical condition), or all user terminals 30.

[0177] 5 and 6, if the management server 40 determines in step S31 that the total score of all residents qualified to cook is less than 5 points (S31: No), that is, if it determines that there is even one resident with a total score of less than 5 points (4 points or less), it identifies the resident with the lowest total score among the residents qualified to cook (S51). The identified resident is a resident qualified to cook who has a total score of less than 5 points (4 points or less) (hereinafter also referred to as a "person in good physical condition").

[0178] As shown in FIG. 6, the management server 40 determines whether there are two or more residents in good health (S52). If the management server 40 determines that there are two or more residents in good health (S52: Yes), it determines whether the residents in good health were in charge of cooking for two consecutive days, yesterday and the day before yesterday (S53). Specifically, the management server 40 determines whether a resident in good health was in charge of cooking for two consecutive days based on whether a consecutive cooking flag is registered in the determination table (see FIG. 3(B)). The management server 40 excludes residents who were in charge of cooking for two consecutive days (residents in good health) from the residents identified in step S51 (S54). In other words, a resident who was determined to be in charge of cooking for two consecutive days will be excluded from the selection of the next cook, even if the resident is in good health.

[0179] The management server 40 determines the resident in good physical condition who has cooked least frequently in the past as the cook (S55). Past cooking frequency is, for example, the number of times cooking has been done from today (today) until a predetermined period of time ago. The predetermined period is, for example, one day. In other words, the resident in good physical condition who did not cook yesterday is determined to be the cook. Alternatively, the predetermined period is one month. In other words, the resident who cooked the least number of times in the past month is determined to be the cook. Therefore, fairness is maintained among residents who are qualified to cook. The cook yesterday or the number of times a resident cooked in the past month (past cooking frequency) is an example of past cooking performance. The processing of step S55 is an example of a cook determination process.

[0180] Next, the management server 40 determines a recommended menu, which is a menu of dishes to be proposed to the cook, based on the physical condition (total score) of the resident selected as the cook and the physical condition (total score) of the other residents (S56). The recommended menu is, for example, the names of multiple dishes. The processing of step S56 is an example of a menu determination process.

[0181] More specifically, the management server 40 determines whether the total score of the resident selected as the cook is below a predetermined score (for example, 4 points) and whether the resident is in good health. If the management server 40 determines that the total score of the resident selected as the cook is below 4 points and the resident is in good health, it selects from the cooking database a dish (a solid menu) with a cooking level of "1."

[0182] Next, the management server 40 further selects from the selected dishes dishes that are suited to the physical condition of the resident who will eat the food, based on the total scores of all residents (residents who will eat the food) other than the resident who was selected as the cook. For example, if the total score of all residents who will eat the food is 4 points or less and it is determined that they are in good physical condition, a dish such as "twice cooked pork" registered with a total score of "4 points or less" will be selected. If the total score of one resident who will eat the food is 4 points or more and it is determined that they are in poor physical condition, a dish such as "porridge" registered with a total score of "5 points or less" will be selected.

[0183] The management server 40 generates an HTTP response including the user ID of the resident selected as the cook, the recommended menu, and the user IDs and overall scores (physical condition) of the other residents. The management server 40 transmits the generated HTTP response to each resident's user terminal 30 via the communication interface 43 and the Internet 11 as a response to the HTTP request received in step S35 (S57). Note that the HTTP response may be transmitted only to the user terminal 30 possessed by the qualified cook. The processing of step S57 is an example of a cook transmission process.

[0184] The user terminal 30 receives the HTTP response sent by the management server 40 via the communication interface 33 or the like (S57). The user terminal 30 displays a cook notification screen (FIGS. 10 and 11) on the touch panel 35 based on the received user ID, recommended menu, and total score (S58). The processing of step S58 is an example of notification processing.

[0185] More specifically, when the application program 39 is downloaded, the terminal memory 32 of the user terminal 30 stores format data for the cook notification screen. This format data includes data for the resident selected as the cook and data for the other residents. Based on the user ID and other data included in the HTTP response, the user terminal 30 generates data to be entered into the input fields of the format data and generates screen data for the cook notification screen. The user terminal 30 inputs the generated screen data into the touch panel 35, causing the touch panel 35 to display the cook notification screen.

[0186] FIG. 10(A) shows a first cook notification screen displayed on the touch panel 35 of the user terminal 30 of the resident selected as the cook. The first cook notification screen displays the text "You will be cooking dinner tonight," the text "Your mother-in-law is not feeling well," and a "Next" icon 65. The text "Your mother-in-law is not feeling well" is displayed, for example, when a resident has a total score of 5 or more. The resident selected as the cook recognizes from the first cook notification screen that they have been selected as the cook and that there are other residents who are not feeling well. After confirming these details, the resident selected as the cook selects the "Next" icon 65. Based on the selection of the "Next" icon 65, the user terminal 30 displays the menu recommendation screen shown in FIG. 10(B) on the touch panel 35.

[0187] The menu recommendation screen shown in Figure 10(B) includes the text "Your mother-in-law is not feeling well, so we recommend the following menu for her," candidate menus (dish names), and an "OK" icon 66. The resident selected as the cook selects a dinner menu from the recommended menus and selects the "OK" icon 66 (S59 in Figure 6).

[0188] FIG. 11(A) shows a second cook notification screen displayed on the touch panel 35 of the user terminal 30 of a resident other than the resident selected as the cook. The second cook notification screen displays the text "Today's dinner cook is Yamada Taro," the text "The whole family is in good health," the text "We recommend a solid menu," and a "Next" icon 67. Residents other than the resident selected as the cook can see the name of the resident selected as the cook, the fact that some residents are feeling unwell, and the fact that the whole family is in good health from the second cook notification screen. After confirming these details, the resident other than the resident selected as the cook selects the "Next" icon 66. Based on the selection of the "Next" icon 67, the user terminal 30 displays the menu recommendation screen shown in FIG. 11(B) on the touch panel 35.

[0189] The menu recommendation screen shown in FIG. 11(B) has the words "Recommended Menu," a recommended menu (name of dish), and an "OK" icon 68. If there is a dish from the recommended menu that a resident other than the resident selected as the cook would particularly like to eat, they can inform the resident selected as the cook of the desired dish. The resident selected as the cook may, for example, select a dish that the family member desires from the recommended menu displayed in FIG. 10(B) and select the "OK" icon 66 (S59 in FIG. 6). Note that when a resident other than the resident selected as the cook selects the "OK" icon 68 on the menu recommendation screen shown in FIG. 11(B), the user terminal 30 terminates the display of the menu recommendation screen.

[0190] As shown in Figure 6, based on receiving the resident's selection of the "OK" icon 66 on the menu recommendation screen (see Figure 10(B)), the user terminal 30 sends an HTTP request including notification information with the menu (dish name) selected by the resident who has been selected as the cook to the management server 40 via the communication interface 33, etc. and the Internet 11 (S60).

[0191] The management server 40 receives the HTTP request sent by the user terminal 30 via the communication interface 43 (S60). The management server 40 registers the user ID of the resident who will cook in step S55 and the menu (dish name) received in step S60 in the performance management database (see FIG. 2(B)) (S61), and terminates the decision notification registration process (S27 in FIG. 4) (return). Note that FIG. 2(B) does not show the menu (dish name) selected by the resident who will cook. The menu registered in the performance management database is used, for example, to determine the recommended menu in step S56. For example, the management server 40 ranks the selected menus (dish names) by ranking the names of dishes that have been cooked less frequently or more frequently (specialty dishes) at the top of the list, and displays them on the user terminal 30 of the resident who will cook. The process of step S61 is an example of a storage process. The user ID and menu (dish name) registered in the performance database are an example of performance data.

[0192] In this way, if there are two or more people in the best physical condition (S52: Yes), residents who have not cooked for two consecutive days are excluded (S54), and of the remaining residents, the resident who cooks least frequently is selected as the cook (S55).

[0193] If the management server 40 determines in step S52 that there is only one resident with the lowest total score (S52: No), it determines whether the resident with the lowest total score cooked for two consecutive days, yesterday and the day before yesterday (S62). This determination is made based on the continuous cooking flag registered in the determination table (see FIG. 3(B)).

[0194] If the management server 40 determines that the resident with the lowest total score (hereinafter also referred to as the "specified person") was not the person who cooked for two consecutive days, yesterday and the day before yesterday (S62: No), it selects the specified person as the cook (S63). Thereafter, the management server 40 and user terminal 30 execute the processes from steps S56 to S61 described above, and end the selection notification registration process (S27 in FIG. 4) (return). The process of step S63 is an example of the cook selection process.

[0195] If the management server 40 determines in step S62 that the specified person has cooked for two consecutive days (S62: Yes), it determines whether all residents other than the specified person have selected the answer option "I can't recover" to the question (S64). If the management server 40 determines that all residents other than the specified person have selected the answer option "I can't recover" to the question (S64: Yes), it determines the specified person as the cook (S63). In other words, if all residents other than the specified person have selected the answer option "I can't recover," the specified person is exceptionally determined to be the cook even if the specified person has cooked for two consecutive days.

[0196] If the management server 40 determines in step S64 that there is a resident other than the specified person who has not selected the answer option "I can't recover" (S64: No), it selects the resident who has not selected the answer option "I can't recover" (the resident with the second lowest total score) as the cook (S65). The management server 40 then executes the processes from steps S56 to S61 described above and ends the selection notification registration process (S27 in FIG. 4) (return). Note that if there are two or more residents with the second lowest total scores, the management server 40 selects the cook based on past cooking performance. For example, the management server 40 selects the resident who has cooked the least number of times in the last month as the cook.

[0197] In this way, if the person in the best physical condition has not been in charge of cooking for two consecutive days, he / she is determined to be the cook (S62: No → S63), and if the person in the best physical condition has been in charge of cooking for two consecutive days (S62: Yes), he / she is exceptionally determined to be the cook only if another resident has selected "can't recover" (S64: Yes → S63).If the person in the best physical condition has been in charge of cooking for two consecutive days (S62: Yes) and none of the other residents has selected "can't recover," that resident is determined to be the cook (S64: No → S65).

[0198] [Effects of the embodiment] In this embodiment, the management server 40 determines the physical condition (physical fatigue) of each resident who is qualified to cook at a predetermined time before dinner cooking begins based on their biometric data, and determines who will cook for today's meal (a predetermined day) based on the determined physical condition of each resident and notifies the resident. Therefore, the cook determination system 10 can prevent a resident who is not feeling well from cooking.

[0199] In this embodiment, the user ID of the resident selected as the cook is registered in the performance data management database in association with the date. The cook is then determined based on a succession flag generated based on the user ID registered in the performance data management database. This ensures fairness in the allocation of cooking duties among qualified residents.

[0200] In this embodiment, mental fatigue, which is difficult to determine from biometric data, is identified from the answers to questions posed to the resident. Therefore, the cook selection system 10 can select a cook for the day by taking into consideration not only the physical fatigue of a resident who is qualified to cook, but also their mental fatigue.

[0201] In this embodiment, the answer options (radio buttons 51 to 53, 55, 56, 58, 59) for questions are associated with scores in the question scoring table. Therefore, the cook determination system 10 can identify the mental fatigue of a resident by a numerical value.

[0202] In this embodiment, the physical condition (physical fatigue) of a resident is determined based on the amount of variation in biological data relative to basic biological data. Therefore, the cook determination system 10 can determine the physical condition of a resident as a numerical value.

[0203] In this embodiment, a menu with a cooking level (easy cooking / thorough cooking) that matches the physical condition of the resident selected as the cook is recommended to the resident. Therefore, when the resident selected as the cook is in poor physical condition, the cook selection system 10 can reduce the cooking burden on the resident.

[0204] In this embodiment, the cook selection system 10 determines the type of menu based on the physical condition of the residents other than the resident selected as the cook, and notifies the cook. Therefore, the cook selection system 10 can provide easily digestible dishes such as porridge or boiled tofu to residents who are not feeling well.

[0205] In this embodiment, if all residents who are qualified to cook are in poor health, no cook is selected, and the resident is asked to ask a helper for cooking assistance or is offered a delivery service. Therefore, the cook selection system 10 can prevent a resident who is in poor health from cooking.

[0206] In this embodiment, the contact information of the helper or the delivery store is notified to the resident. Therefore, the cook determination system 10 makes it easy for the resident to request cooking assistance from the helper and order delivery.

[0207] [Variations] In the embodiment, an example has been described in which the cook decision system 10 includes the management server 40. However, if the cook decision system 10 does not require a data collection function, it may include a personal computer (PC) installed in the home instead of the management server 40. In other words, the cook decision system 10 may be a standalone system separated from an external server. The PC may be, for example, a PC owned by the resident, or a PC installed in the home by a service provider for home management purposes. The PC is installed with a program that executes processing equivalent to the management program 45. The PC communicates with the user terminal 30 and the wearable device 20 directly or via a LAN attached to the home. The PC is an example of an information processing device.

[0208] In the embodiment, an example has been described in which the cook determination system 10 includes the management server 40, and the management server 40 determines the cook. However, the cook determination system 10 may not include the management server 40 and may be composed of only the user terminal 30 and the wearable device 20. In this case, the processing executed by the management program 45 is executed by an application program 39 of the user terminal 30. Furthermore, a management database such as a user management database is stored in the terminal memory 32 of the user terminal 30 when the application program 39 is downloaded. The management database stored in the terminal memory 32 is a database that manages only one family. In this case, the CPU 31 of the user terminal 30 is an example of a control device.

[0209] In the embodiment, the touch panel 35 and the speaker 36 provided in the user terminal 30 are examples of the notification device. However, the notification device may be a monitor (display) or a speaker installed in the home.

[0210] In the embodiment, the wearable terminal 20 has been described as an example of a biosensor. However, instead of the wearable sensor 20, other biosensors, such as a stationary biosensor, may be used as long as they can acquire biometric data of the resident.

[0211] In the embodiment, an example has been described in which the wearable terminal 20 includes the temperature sensor 25, the light sensor 26, the acceleration sensor 27, and the biopotential sensor 28. However, the wearable terminal 20 may include sensors other than the temperature sensor 25, the light sensor 26, the acceleration sensor 27, and the biopotential sensor 28. Furthermore, the wearable terminal 20 may not include some of the sensors among the temperature sensor 25, the light sensor 26, the acceleration sensor 27, and the biopotential sensor 28.

[0212] In the embodiment, an example has been described in which the biometric data for identifying the resident's physical condition is body temperature, sleep time, blood pressure, heart rate, and respiratory rate. However, the biometric data for identifying the resident's physical condition may be biometric data other than body temperature, sleep time, blood pressure, heart rate, and respiratory rate. Furthermore, the biometric data may be some of body temperature, sleep time, blood pressure, heart rate, and respiratory rate. In other words, the type of biometric data of the resident acquired by the management server 40 may be any type of biometric data as long as it can identify the resident's physical condition.

[0213] In the embodiment, an example has been described in which the wearable terminal 20 transmits the acquired biometric data to the user terminal 30. However, the wearable terminal 20 may transmit the acquired biometric data directly to the management server 40 via the communication interface 23 and the Internet 11.

[0214] In the embodiment, an example has been described in which the wearable terminal 20 and the user terminal 30 are separate devices. However, the wearable terminal 20 and the user terminal 30 may be a single device.

[0215] In the embodiment, an example has been described in which the physical condition of a resident who is qualified to cook is identified based on biometric data and questions. However, the physical condition of a resident who is qualified to cook may be identified based only on biometric data. In other words, the physical condition of a resident who is qualified to cook may be identified based only on physical fatigue.

[0216] In the embodiment, an example has been described in which a cook is determined based on the identified resident's physical condition today and their past cooking performance. However, a cook may also be determined based only on the identified resident's physical condition today. For example, a resident in the best physical condition (with the lowest overall score) may be determined to be the cook, and if there are multiple residents in the best physical condition, the resident may be allowed to select which of the residents to be the cook.

[0217] In the embodiment, an example has been described in which answer options for a question are associated with scores and answers to the question are scored. However, instead of ranking multiple combinations of answer options and quantifying the resident's mental fatigue level, the residents may be ranked based on their mental fatigue. For example, the residents who selected "Can't recover," "Sleepy," and "Days 1-3" may be ranked first, and the residents who selected "No problem," "No problem," and "Other" may be ranked last. Then, if the physical fatigue levels identified from the biometric data are the same, the resident with the lowest mental fatigue ranking may be selected as the cook.

[0218] In the embodiment, an example has been described in which a recommended menu is determined based on the physical condition of the resident selected as the cook and the physical conditions of the other residents. However, the recommended menu may be determined based only on the physical condition of the resident selected as the cook, or the recommended menu may be determined based only on the physical condition of the residents other than the resident selected as the cook.

[0219] In the embodiment, an example has been described in which the determined cook is notified to the resident by being displayed on the touch panel 35. That is, the touch panel 35 is an example of a notification device. However, the determined cook may be notified to the resident by voice through the speaker 36 provided in the user terminal 30. In this case, the speaker is an example of a notification device.

[0220] In the embodiment, an example has been described in which the cook determination system 10 determines a cook for dinner every day. However, the cook determination system 10 may similarly determine a cook for breakfast or lunch every day. The cook determination system 10 may also determine a cook for dinner on holidays such as Saturdays and Sundays every week. In this case, Saturdays and Sundays every week are examples of predetermined days.

[0221] In the embodiment, an example is described in which, instead of determining who will be responsible for cooking, if all residents who are qualified to cook are in poor health, the residents are asked to request cooking assistance from a helper or are offered a suggestion to order delivery. However, such a suggestion does not have to be made. For example, if all residents who are qualified to cook are in poor health, the notification process may simply notify the residents that they are unable to cook.

[0222] [Appendix 1] a biometric sensor for detecting biometric data of a plurality of residents; a notification device; a control device capable of communicating with the biosensor and the notification device, The control device includes: a biometric data acquisition process for acquiring biometric data from the biometric sensor; a physical condition determination process for determining the physical condition of each resident at a predetermined time on a predetermined day based on the biometric data; a cook determination process for determining a cook for the specified day based on the physical condition of each identified resident; and a notification process for notifying the determined cook via the notification device.

[0223] [Appendix 2] The control device includes: A storage process is further performed in which the determined cook is associated with the date and stored in memory as performance data; The cook determination system according to claim 1, wherein the cook determination process determines a cook by determining residents to exclude from the cook candidates based further on the performance data.

[0224] [Appendix 3] Further comprising an input interface capable of communicating with the control device; The control device includes: a question notification process for causing the notification device to notify the question stored in the memory at a predetermined time; and further executing an answer acquisition process for acquiring the answer of the resident to the question, the answer being input through the input interface; 3. The cook determination system according to claim 1, wherein the cook determination process determines a cook based further on the response.

[0225] [Appendix 4] The above question has multiple questions, The above questions each have multiple answer options, The answer options above are associated with scores. The cook determination system according to claim 3, wherein the cook determination process determines a cook based on the physical condition indicated by a total score calculated based on the answers.

[0226] [Appendix 5] 2. The cook determination system according to claim 1, wherein the physical condition determination process is a process of determining the physical condition of each resident based on a deviation amount of the biometric data from basic biometric data stored in a memory.

[0227] [Appendix 6] The type of food and the cooking level are associated in the memory, The control device includes: A menu determination process is further performed to determine a dish to be proposed to the cook based on the cooking level corresponding to the determined physical condition level of the cook; The cook determination system according to claim 1, wherein the notification process notifies the user of the determined cook and type of food.

[0228] [Appendix 7] The type of food and the physical condition level are associated in the memory, The control device includes: A menu determination process is further performed to determine the type of food to be proposed to the cook according to the physical condition level of the residents other than the resident determined to be the cook; The cook determination system according to claim 1 or 6, wherein the notification process notifies the user of the determined cook and type of food.

[0229] [Appendix 8] The above-mentioned cook selection process is as follows: Based on the determination that the physical condition of the residents identified in the physical condition identification process is worse than a threshold level for all residents who can cook, it is decided to notify the suggestions stored in the memory instead of the person in charge of cooking; The cook determination system according to claim 1, wherein the notification process is a process of notifying the selected cook or the suggestion via the notification device.

[0230] [Appendix 9] The cook decision system according to claim 8, wherein the proposal includes contact information pre-registered in the memory.

[0231] [Appendix 10] a first program implemented in an information processing device having a first communication interface and a first computer; a second program implemented in a user terminal having a display, a second communication interface, and a second computer; The second program mentioned above is a biometric data acquisition process for acquiring biometric data from a biometric sensor that detects biometric data of a plurality of residents; a biometric data transmission process of transmitting the acquired biometric data to the information processing device through the second communication interface, The first program mentioned above is a physical condition determination process for determining the physical condition of each resident at a predetermined time on a predetermined day based on the received biometric data; a cook determination process for determining a cook for the specified day based on the physical condition of each identified resident; a cook sending process for sending the determined cook to the user terminal via the first communication interface; The second program mentioned above is A program that causes the second computer to execute a notification process that displays the received name of the person in charge of cooking on the display. [Explanation of symbols]

[0232] 10. Cooking staff selection system 11. Internet 20. Wearable device (an example of a biosensor) 24 Sensor group 30 User terminal 31 CPU (an example of a control device and a second computer) 32. Device memory 33, 34: Communication interface (an example of a second communication interface) 35 Touch panel (an example of a notification device and input interface) 36. Speaker (an example of a notification device) 37. Clock module 39. Application program (an example of the second program) 40 Management server (an example of an information processing device) 41 CPU (an example of a control device and a first computer) 42 Server memory (an example of memory) 43 Communication interface (an example of a first communication interface) 45 Management Program (Example of the First Program) 51-53, 55, 56, 58, 59...Radio buttons (examples of answer options)

Claims

1. a biometric sensor for detecting biometric data of a plurality of residents; a notification device; a control device capable of communicating with the biosensor and the notification device, The control device includes: a biometric data acquisition process for acquiring biometric data from the biometric sensor; a physical condition determination process for determining the physical condition of each resident at a predetermined time on a predetermined day based on the biometric data; a cook determination process for determining a cook for the specified day based on the physical condition of each identified resident; and a notification process for notifying the determined cook via the notification device.

2. The control device includes: A storage process is further performed in which the determined cook is associated with the date and stored in memory as performance data; The cook determination system according to claim 1 , wherein the cook determination process determines a cook by determining residents to be excluded from cook candidates based further on the performance data.

3. Further comprising an input interface capable of communicating with the control device; The control device includes: a question notification process for causing the notification device to notify the question stored in the memory at a predetermined time; and further executing an answer acquisition process for acquiring the answer of the resident to the question, the answer being input through the input interface; The cook determination system according to claim 1 or 2, wherein the cook determination process determines a cook based further on the response.

4. The above question has multiple questions, The above questions each have multiple answer options, The answer options above are associated with scores.

4. The cook determination system according to claim 3, wherein the cook determination process determines a cook based on the physical condition indicated by a total score calculated based on the answers.

5. 2. The cook determination system according to claim 1, wherein the physical condition determination process determines the physical condition of each resident based on a deviation of the biometric data from basic biometric data stored in a memory.

6. The type of food and the cooking level are associated in the memory, The control device includes: A menu determination process is further performed to determine a dish to be proposed to the cook based on the cooking level corresponding to the determined physical condition level of the cook; The cook determination system according to claim 1 , wherein the notification process notifies the user of the determined cook and the type of food.

7. The type of food and the physical condition level are associated in the memory, The control device includes: A menu determination process is further performed to determine the type of food to be proposed to the cook according to the physical condition level of the residents other than the resident determined to be the cook; The cook determination system according to claim 1 or 6, wherein the notification process notifies the user of the determined cook and the type of food.

8. The above-mentioned cook selection process is as follows: Based on the determination that the physical condition of the residents identified in the physical condition identification process is worse than a threshold level for all residents who can cook, it is decided to notify the suggestions stored in the memory instead of the person in charge of cooking; The cook determination system according to claim 1 , wherein the notification process is a process of notifying the selected cook or the proposal via the notification device.

9. The cook determination system according to claim 8 , wherein the suggestion includes contact information pre-registered in the memory.

10. a first program implemented in an information processing device having a first communication interface and a first computer; a second program implemented in a user terminal having a display, a second communication interface, and a second computer; The second program is a biometric data acquisition process for acquiring biometric data from a biometric sensor that detects biometric data of a plurality of residents; a biometric data transmission process of transmitting the acquired biometric data to the information processing device through the second communication interface; The first program is a physical condition determination process for determining the physical condition of each resident at a predetermined time on a predetermined day based on the received biometric data; a cook determination process for determining a cook for the specified day based on the physical condition of each identified resident; a cook sending process for sending the determined cook to the user terminal via the first communication interface; The second program is A program that causes the second computer to execute a notification process that displays the received name of the person in charge of cooking on the display.

Images