Cooking person decision system and program
The system addresses the limitations of existing housework allocation by using biosensors to determine who cooks based on current health and preferences, ensuring well-being and fair distribution.
Patent Information
- Application Number
- JP2024011255
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-01-29
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2044-01-29
AI Technical Summary
Existing housework allocation systems, such as the one described in Patent Document 1, fail to consider stress factors beyond housework and do not allow residents to opt out of assigned tasks if they are unwell, leading to potential health issues.
A system that includes biosensors to detect biometric data, a control device to identify physical and mental conditions, and a notification process to determine and notify the person in charge of cooking based on current health and preferences, ensuring fair distribution and considering well-being.
Prevents residents who are unwell from cooking by considering both physical and mental fatigue, maintaining fairness in task distribution and providing appropriate meal options or assistance.
Smart Images

Figure 0007586353000001_ABST
Abstract
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 biosensor, and a controller. The controller calculates the stress level of the resident while performing housework based on the images captured by the cameras and the resident's biometric information acquired by the biosensor. 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] JP 2020-177447 A Summary of the Invention [Problem to be solved by the invention]
[0004] The system disclosed in Patent Document 1 has the problem that the allocation of housework is decided based on the stress felt while doing the housework, and stress other than housework is not taken into consideration. In addition, the system disclosed in Patent Document 1 has the problem that the allocation of housework is decided for a certain period of time, such as January, so that even if a person is not feeling well, for example, they have to do the assigned housework.
[0005] The present invention has been made in consideration of the above-mentioned circumstances, and has an object 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 determination system according to the present invention includes a biosensor that detects biometric data of a plurality of residents, a notification device, and a control device capable of communicating with the biosensor and the notification device. The control device executes a biometric data acquisition process that acquires the biometric data from the biosensor, a physical condition identification process that identifies the physical condition of each resident at a predetermined time on a predetermined day based on the biometric data, a cook determination process that determines a cook for the predetermined day based on the identified physical 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 sensor, identifies 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 of that decision.
[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 a resident to be excluded from candidates for the cook based on the performance data.
[0009] The cooks determined by the cook determination system according to 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, he / she will be removed from the list of candidates for the next cook. As a result, fairness in the allocation of cooking responsibilities between residents is maintained.
[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 for causing the notification device to notify a question stored in memory at a predetermined time, and an answer acquisition process for acquiring an answer to the question from the resident that is input through the input interface, and the cook determination process is a process for determining 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 by answering 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 be a process of determining a cook based on a total score calculated based on the answers.
[0013] Answers to each question item are made by selecting an answer option, and each answer option is associated with a score, so that the control device can quantify (score) the resident's mental fatigue and determine the level of mental fatigue of each resident based on the numerical value.
[0014] (5) The physical condition identification process may be a process of identifying the physical condition of each resident based on an amount of deviation of the biometric data from 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 thus obtain the physical condition of the resident as a numerical value.
[0016] (6) The type of food may be associated with the cooking level in the memory. The control device further executes a menu determination process for determining a food with a cooking level corresponding to the determined physical condition level of the cook as a food to be proposed to the cook. The notification process is a process for notifying the determined cook and the type of food.
[0017] For example, if all residents who can cook are in poor health and a resident who is in relatively good health is selected as the cook, low-level dishes, i.e., dishes that are easy to prepare, are suggested to the selected resident, thereby reducing the burden on the unwell cook.
[0018] (7) The type of food and the physical condition level may be associated in the memory. The control device further executes a menu determination process for determining, as food to be proposed to the cook, a type of food according to the physical condition level of the resident other than the resident determined as the cook. The notification process is a process for notifying the determined cook and the type of food.
[0019] The type of menu (food) according to the physical condition of the residents other than the resident selected as the cook is decided and notified to the cook. 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 decide 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 via the notification device.
[0021] If all residents who are capable of cooking are unwell, no one will be appointed to cook and residents will be asked to order takeout.
[0022] (9) The suggestions may include contact information that is pre-registered in memory.
[0023] The contact information is, for example, a telephone number, email address, or URL of a store that delivers food, or a telephone number or email address of a parent living nearby, etc. The resident contacts the store indicated by the notified contact information to order food delivery, or asks the parent living 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 a plurality of residents, and a biometric data transmission process for transmitting the acquired biometric data to the information processing device through 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 through 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 understood as a program invention. Effect 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 description of the drawings]
[0027] [Figure 1] FIG. 1 is a configuration diagram and a functional block diagram of a cooker determination system 10 according to an embodiment. [Diagram 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. [Diagram 3] FIG. 3A is a diagram showing a biometric data scoring table, and FIG. 3B is a diagram showing a determination table. [Figure 4] FIG. 4 is a flowchart of the management process. [Diagram 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 a second cook notification screen, and FIG. 11(B) is a diagram showing a menu recommendation screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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 appropriately modified without changing the gist of the present invention. In addition, the order of execution of each process (each step) shown in the flowcharts shown in Figures 4 to 6 may be appropriately changed, some may be omitted, other processes may be added, or other equivalent processes may be replaced, without changing the gist of the present invention.
[0029] [Outline of Cooking Person Decision System 10] The cook determination system 10 (see FIG. 1) described in this embodiment is a system that provides a service of determining and notifying a candidate who will 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 residence. 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 own user terminal.
[0030] The 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 various services provided to the builder of the house. The various services are, for example, services related to home maintenance and services that support comfortable living in the home. The cook decision system 10 is operated in conjunction with, for example, a system that provides other services. For example, the cook decision system 10 provides data used by the other system. Alternatively, the cook decision system 10 obtains data required for operation from the other system. In other words, the cook decision system 10 also functions as a data collection system for the other system.
[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 who built the house.
[0032] [Configuration of Cooking Person Decision System 10] As shown in Fig. 1, the cook determination system 10 includes a plurality of wearable devices 20, a user terminal 30, and a management server 40. Note that Fig. 1 shows only one wearable device 20, and the other wearable devices 20 are omitted.
[0033] [Wearable Device 20] The wearable terminal 20 is a device that acquires biometric data of a resident. The wearable terminal 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 terminal 20. The wearable terminal 20 is an example of a biometric sensor.
[0034] The wearable terminal 20 is used by being worn on the body of a resident who is qualified to cook. The location where the wearable terminal 20 is worn 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, and a sensor group 24, as well as a communication bus (not shown) which connects these together.
[0036] The terminal memory 22 is composed of, for example, a ROM, a RAM, an EEPROM, or other storage elements, but may be composed of 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 a communication address of the user terminal 30 carried by a person wearing the wearable terminal 20. The setting data is registered in the wearable terminal 20 through the user terminal 30, for example.
[0040] The communication interface 23 is an interface for performing short-range wireless communication with the user terminal 30. Note that the wearable terminal 20 may include 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 for detecting the body temperature, blood pressure, heart rate, respiratory rate, and sleep state of the wearer. The various sensors include a temperature sensor 25, an optical sensor 26, an acceleration sensor 27, and a bioelectric potential sensor 28.
[0042] The temperature sensor 25 receives, for example, infrared rays emitted by the wearer and outputs a temperature according to the amount of infrared rays received, that is, the body temperature of the wearer.
[0043] The optical sensor 26 irradiates 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 from the emission of the irradiated light to the reception of the reflected light, the phase difference between the irradiated light and the reflected light, and the like. The 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 the wearer is asleep.
[0044] The acceleration sensor 27 outputs data corresponding to the inclination, 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] The biopotential sensor 28 detects weak biopotentials generated by the wearer and outputs data indicative of an electrocardiogram, an electroencephalogram, and an electromyogram. The data output by the biopotential sensor 28 is used to generate biodata indicative of whether or not the wearer is in a sleeping state.
[0046] A terminal program (not shown) implemented 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 each 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, may be owned only by a person qualified to cook, or may be owned by residents other than the person qualified to cook. For example, if one user terminal 30 is set 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 qualified to cook owns a user terminal 30, and a resident who is not qualified 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) which connects these components. The CPU 31 is an example of a second computer.
[0050] The terminal memory 32 is composed of, 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. The terminal memory 32 may be composed of any type of storage elements and storage devices.
[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 to "application 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 in the user terminal 30. The application program 39 may be a program that runs on a browser installed in 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 through the OS 38. The application program 39 also has a function of accepting user input through 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-distance wireless communication. Examples of short-distance wireless communication include wireless LAN (registered trademark) such as Wi-Fi (registered trademark) and Bluetooth (registered trademark). When the short-distance wireless communication is wireless LAN, the user terminal 30 communicates with the wearable terminal 20 via a router or the like installed in the house. When the short-distance wireless communication is Bluetooth (registered trademark), the user terminal 30 performs short-distance wireless communication directly with the wearable terminal 20. As long as the user terminal 30 can communicate with the wearable terminal 20, there is no particular limitation on the communication standard (communication protocol).
[0055] The communication interface 34 is an interface that communicates 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 as an input interface that accepts user input in addition to a display function. The user terminal 30 may 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 voice data into voice and outputs it.
[0058] The clock module 37 outputs date and time information. If the user terminal 30 is capable of acquiring date and time information via the Internet 11, it does not have to include a clock module.
[0059] The user terminal 30 notifies the resident of today's cook, received from the management server 40, by displaying it on the touch panel 35 or outputting it through 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. When the user terminal 30 obtains date and time information through the communication interfaces 33 and 34, the user terminal 30 does not need to include 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 may be a cloud server configured with a plurality of 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) which 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 an example 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. That is, 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 composed of, 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. A part of the server memory 42 may be composed of a storage server.
[0066] The server memory 42 stores an operating system (OS) 44, a management program 45, and a management database.
[0067] Management program 45 is a program that executes the processes shown in Fig. 4 to Fig. 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 database 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 named after the following: "User ID," "Name," "Relationship," "Gender," "Age," "Cooking ability," "User terminal," "Terminal information," "Wearables," "Basic biometric data," "Address," "Helper information," and "Delivery store information."
[0071] The field of the column 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". A family ID that identifies the family to which the resident belongs is registered in the field of the sub-column named "Family". In other words, residents who belong to the same family have the same family ID. An ID that individually identifies an individual in the family to which the resident belongs is registered in the field of the sub-column named "Individual". In other words, each resident can be identified on a family basis and also on an individual basis.
[0073] The column field named "First name" stores the first and last names of residents.
[0074] The field of the column named "Relationship" is used to register the contractor or the relationship (relationship) with the contractor. A contractor is a person who has ordered the construction of a house from a service provider (construction owner) or a person who has applied to the service provider to receive the provision of services.
[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] A cooking qualification flag is registered in the field of the column named "Cooking Qualification". The cooking qualification flag is "1" indicating that the person is a qualified cook or "0" indicating that the person is not a qualified cook.
[0078] Note that only residents who are qualified to cook can be selected as a cook, so residents who are not qualified to cook do not need to be registered in the user management database. However, if the determined cook is notified to residents other than the person determined to be the cook, residents who are not qualified to cook are also registered in the user management database. In addition, if the cook determination system 10 also serves as an information collection system, or if the cook determination system 10 is linked to a system that provides other services, information on residents who are not qualified to cook is also registered in the user management database to the extent possible.
[0079] In the field of the column named "User Terminal", a "1" is registered indicating that the user has a user terminal 30, or a "0" is registered indicating that the user does not have a user terminal 30. Note that residents who do not have a user terminal 30 do not need to be registered in the user management database.
[0080] The field of 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] In the field of the column named "Wearable", a "1" is registered, indicating that the resident is wearing the wearable device 20 and biometric data can be acquired, or a "0" is registered, indicating that the resident is not wearing the wearable device 20 and biometric data cannot be acquired. For residents whose cooking suitability is "1", a "1" is always registered in the field of the column named "Wearable".
[0082] In the field of the column named "basic biological data", basic biological data of the resident, such as body temperature, is registered. The basic biological data is used to identify the physical condition of the resident. The physical condition of the resident is also used to determine the type of cuisine to be proposed, as well as to determine the cook. Therefore, it is desirable to register basic biological data not only for residents who are qualified to cook, but also for other residents. Furthermore, when the cook determination system 10 also serves as an information collection system, or when the cook determination system 10 is linked to a system that provides other services, it is desirable to register basic biological 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 body temperature previously detected by the wearable device 20, a general body temperature according to the resident’s gender and age, or a body temperature reported by the resident through the application program 39.
[0085] The field of the sub-column named "sleep time" registers the resident's usual sleep time. The usual sleep time may be the average value of the sleep time previously detected by the wearable device 20, or may be the general sleep time according to the resident's gender and age, or may be the sleep time declared by the resident through the application program 39.
[0086] The field of the subcolumn 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 sex and age, or a blood pressure reported by the resident through the application program 39.
[0087] The field of the subcolumn named "heart rate" registers the resident's normal heart rate. The normal heart rate may be an average of heart rates 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] In the field of the sub-column named "Respiration rate", the resident's normal respiration rate is registered. The normal respiration rate may be an 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 reported 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" registers information about people who can provide cooking assistance to the family (hereinafter referred to as "helpers"), such as parents who live close to the house where the family lives. The 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 home where a family lives (hereinafter also referred to as "delivery stores"). The information includes the name of the delivery store, the type of delivery store, the name of the food that can be delivered, the price, a telephone number, an email address, a URL, etc. The types of delivery stores include, for example, Chinese food, pizza, Japanese food, sushi, etc.
[0092] The "Name", "Relationship", "Sex", "Age", "Cooking Suitability", "User Terminal", "Terminal Information", "Wearable", "Basic Biological Data", "Address", and "Helper Information" are input by the user to the user terminal 30 when or after the application program 39 is downloaded to the user terminal 30. The application program 39 transmits application data including the input "Name", "Relationship", "Sex", "Age", "Cooking Suitability", "User Terminal", "Terminal Information", "Wearable", "Basic Biological Data", "Address", and "Helper Information" to the management server 40 via the Internet 11. The management program 45 of the management server 40 generates a new record in the user management database based on receiving the application data, assigns a unique user ID to the generated record, and registers the "Name", "Relationship", "Sex", "Age", "Cooking Suitability", "User Terminal", "Terminal Information", "Wearable", "Basic Biological 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 acquires basic biometric data corresponding to the "gender" and "age" included in the application data from the table and registers the data in a newly generated 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 match the characteristics of each resident based on the biometric data acquired by the wearable device 20.
[0094] In addition, if the service provider is the construction company that built the house in which the resident lives, the ``name,'' ``relationship,'' ``gender,'' ``age,'' ``fitness to cook,'' ``user terminal,'' ``terminal information,'' ``wearables,'' ``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 (when an order is received) or after construction.
[0095] Furthermore, the "Name", "Relationship", "Gender", "Age", "Cooking suitability", "User terminal", "Terminal information", "Wearable", "Basic biometric data", "Address", and "Helper information" may be transmitted to the management server 40 by each resident using the user terminal 30, or may be transmitted to the management server 40 by a contractor on behalf of the resident. Information regarding residents who do not have a user terminal 30 is transmitted to the management server 40 by a resident who has a user terminal 30, such as a contractor, using the user terminal 30.
[0096] The "delivery store information" may be registered in the user management database by the resident himself / herself searching for and sending the selected store to the management server 40 using the user terminal 30, or the management program 45 may perform a search based on the resident's address registered in the user management database and register the information in the user management database.
[0097] The management database includes a track record management database shown in Fig. 2(B). The track record management database is a database in which the user ID of a previously determined cook is registered in association with a date. 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 a cook has not been determined and a helper provides cooking assistance or if a delivery is ordered, "0" is registered in the track record management database instead of the user ID.
[0098] The management database includes the recipe database shown in Fig. 2(C). The recipe database is a database that manages data on each dish. The recipe database has multiple columns with the names of "dish name," "cooking level," and "total score (physical condition level)."
[0099] The field of the column named "dish name" is where the names of dishes such as Twice Cooked Pork, Rice Porridge, and Hot Tofu are registered. In other words, a record is created for each dish name.
[0100] In the field of the column named "cooking level", either "0" indicating that cooking is easy or "1" indicating that cooking is time-consuming is registered. In other words, a dish with cooking level "0" indicates easy cooking, and a dish with cooking level "1" indicates thorough cooking. If the resident selected as the cook is in good health, a dish (menu) with a cooking level of "1" is 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" is 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 hot tofu have a total score (physical condition level) of "5 or more" and are suitable for people who are in poor physical condition, while twice-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 in which answer options selected by residents for questions are associated with scores. In the example shown in FIG. 2(D), the answer option "no problem" for a 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. In addition, the answer option "no problem" for a question asking about "sleepiness" is associated with "0" points, and the answer option "sleepy" is associated with "1" points. In addition, the answer option "1st to 3rd day" for the question "menstruation", which is a limited question for 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 allows mental fatigue that does not appear in biometric data to be quantified.
[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 in four stages according to the deviation of the resident's body temperature today from the body temperature A of 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", and 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 specified time a specified time before the time to start cooking dinner.
[0108] Records related to "sleep time" are scored on a four-level scale according to the amount of deviation in the resident's sleep time last night from the sleep time B in the basic biometric data, which is the normal sleep time. Specifically, if the resident's sleep time last night was 90% of the normal sleep time (0.9 times or more), it is given a "0" point; if the resident's sleep time last night was 80% of the normal sleep time (0.8 times or more but less than 0.9 times), it is given a "1" point; if the resident's sleep time last night was 60% of the normal sleep time (0.6 times or more but less than 0.8 times), it is given a "3" point; and if the resident's sleep time last night was less than 60% of the normal sleep time, it is given a "5" point.
[0109] In records related to "blood pressure," a score is assigned in two stages according to the amount of 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 mentioned above.
[0110] In the records 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 vital 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 records related to "respiratory rate", a score is assigned in two stages according to the deviation of the resident's today's respiratory rate from the respiratory rate E of the basic vital data, which is the normal respiratory rate (absolute value of "E - respiratory rate"). If the deviation is 3 breaths / min or less, the score is "0", and if the deviation is more than 3 breaths / min, the score is "1". Note that today's respiratory rate is the respiratory rate at the above-mentioned specified time.
[0112] The resident's physical fatigue is quantified using a vital data scoring table.
[0113] The management database includes a judgment table shown in Fig. 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 in charge of cooking. The judgment table is generated or updated every day. Note that the current physical condition refers to the physical and mental fatigue at the specified time.
[0114] The judgment table has several columns named "User ID," "Name," "Biometric data score," "Question answer score," "Total score," "Consecutive responsibility flag," "Cooking responsibility flag," and "Help / delivery flag."
[0115] In the fields of the columns named "User ID" and "First name", the user ID and the first 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" of "User ID". That is, a record is generated for each family. Each record has a sub-record generated for each resident included in the family who has "1" registered in "Wearable" in the user management database (see FIG. 2(A)). That is, the physical condition of only the resident who wears the wearable device 20 is identified. Note that a sub-record may also be generated for a resident who does not wear the wearable device 20. In that case, the physical condition of the resident who does not wear the wearable device 20 is identified only from the answer to the question. 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 determined to be in charge of cooking.
[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] In the field of the subcolumn named "body temperature score", a body temperature score determined based on the body temperature of the resident acquired by the wearable device 20 is registered. In more detail, the management program 45 of the management server 40 calculates the absolute value of the difference between the acquired "body temperature today of the resident" and "body temperature A at normal time of the resident". "Body temperature A at normal time of the resident" is the body temperature in the basic biological data registered in the user management database (see FIG. 2(A)). The management program 45 determines the score based on the calculated "absolute value of the difference between body temperature A at normal time and body temperature today" and the biological 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 biological data is 36.6°C and the body temperature today is 37.5°C, so the absolute value of the difference is 0.9°C. In the biological data scoring table, "0.9°C" is associated with "3" points.
[0120] The sub-column named “sleep time” registers the resident's sleep time acquired by the wearable device 20.
[0121] In the field of the subcolumn named "sleep score", a sleep score determined based on the resident's sleep time last night acquired by the wearable device 20 is registered. More specifically, the management program 45 of the management server 40 reads out 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 sleep time under normal circumstances". 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 field of the subcolumn named "sleep score". In the example of "Yamada Taro" in the judgment table, the sleep time of the basic biometric data is 6.5 hours and the sleep time last night is 5.5 hours, so the "resident's sleep time last night" is 8.4% of the "resident's sleep time under normal circumstances", and the score associated with "8.4%" in the biometric data scoring table is "1".
[0122] The sub-column entitled “Blood Pressure” registers the resident's blood pressure acquired by the wearable device 20.
[0123] In the field of the subcolumn named "blood pressure score", a blood pressure score determined based on the resident's blood pressure acquired by the wearable device 20 is registered. In more detail, the management program 45 of the management server 40 calculates the absolute value of the difference between the acquired "today's blood pressure of the resident" and "the resident's normal blood pressure C". The "normal blood pressure C of the resident" is the blood pressure in the basic biometric data registered in the user management database (see FIG. 2(A)). The management program 45 determines the score based on the calculated "absolute value of the difference between the normal blood pressure C and today's blood pressure" and the biometric data scoring table, and registers the determined score in the field of the subcolumn 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" is associated with "1" point.
[0124] The sub-column named “heart rate” registers the resident's heart rate acquired by the wearable device 20.
[0125] In the field of the subcolumn named "heart rate score", a heart rate score determined based on the resident's heart rate acquired by the wearable device 20 is registered. In more detail, 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 of the subcolumn named "heart rate score". In the example of "Yamada Taro" in the judgment table, the heart rate in the basic biometric data is 72 beats / min, and the heart rate today is 80 beats / min, so the absolute value of the difference is 8 beats. In the biometric data scoring table, "8 times" is associated with "1" point.
[0126] The sub-column named “Respiration rate” registers the resident's respiration rate acquired by the wearable device 20.
[0127] In the field of the sub-column named "breathing score", a respiration score determined based on the respiration rate of the resident acquired by the wearable terminal 20 is registered. In more detail, the management program 45 of the management server 40 calculates the absolute value of the difference between the acquired "today's respiration rate of the resident" and the "normal respiration rate E of the resident". The "normal respiration rate E of the resident" 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 today's respiration rate" and the biometric data scoring table, and registers the determined score in the field of the sub-column named "breathing score". In the example of "Yamada Taro" in the judgment table, the respiration rate of the basic biometric data is 16 breaths / min, and the respiration rate of today is 20 breaths / min, so the absolute value of the difference is 4 breaths. In the biometric data scoring table, "4 breaths" is associated with "1" point.
[0128] The field of the column named "Question Answer Score" registers the resident's answers to each of the questions asked to the resident, "Feelings," "Sleepiness," and "Menstruation," as well as the scores 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 "consecutive cook flag", "1" is registered if the resident was in charge of cooking for two consecutive days, yesterday and the day before yesterday, and "0" is registered otherwise. The management program 45 of the management server 40 registers "1" or "0" in the field of the column named "consecutive cook flag" based on the data registered in the performance management database (see FIG. 2(B)). If a request for cooking assistance is made to a helper or a delivery order 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 a delivery order was placed two days ago (the day before yesterday), a consecutive cook flag is registered for that resident. The consecutive cook flag is an example of performance data.
[0131] In the field of the column named "Cook flag", a "1" is registered if the resident has been decided as the cook for today, and a "0" is registered if the resident is not the cook for today. The management program 45 of the management server 40 decides the cook in the decision notification registration process shown in Figures 5 and 6, and registers a "1" for the resident decided as the cook and a "0" for the other residents.
[0132] In the field of the column named "Help / Delivery Flag", a "1" is registered indicating that a request for cooking assistance has been made to a helper or that a delivery has been requested, or a "0" is registered indicating that a person has been selected to be in charge of cooking. The management program 45 of the management server 40 registers a "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 Fig. 5 and Fig. 6, and registers a "0" when it has been decided that a person will be in charge of cooking.
[0133] [Operation of Cooking Decision 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. Note that 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 terminal 20 acquires biometric data and temporarily stores the acquired biometric data in the terminal memory 22 (S11). The acquisition of biometric data is performed, for example, at a predetermined time interval or at each predetermined time. The wearable terminal 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 an interval longer than the acquisition interval of the biometric data, and multiple pieces of biometric data may be transmitted collectively to the user terminal 30, or an average value of the multiple pieces of biometric data may be transmitted to the user terminal 30. Alternatively, the wearable terminal 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 terminal 20 may transmit the biometric data periodically, or may transmit the biometric data only when necessary.
[0135] The user terminal 30 receives the biometric data transmitted by the wearable terminal 20 through 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 come (S15: Yes), it displays a question answer screen (see FIGS. 7 and 8) on the touch panel 35 (S16). Specifically, the terminal memory 32 of the user terminal 30 stores in advance screen data showing the question 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 answer screen on the touch panel 35 by inputting the screen data stored in the terminal memory 32 into the touch panel 35. The screen data showing the question 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 process 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 are feeling today” and a “Next” icon 50. The resident carrying the user terminal 30 selects the “Next” icon 50.
[0140] Based on the selection of the "Next" icon 50 on the first screen (S17 in FIG. 4), the user terminal 30 causes the touch panel 35 to display the second screen shown in FIG. 7(B).
[0141] The second screen has the text "How are you feeling today?", a radio button 51 and the text "No problem" that correspond to each other, a radio button 52 and the text "Tired" that correspond to each other, a radio button 53 and the text "Can't recover" that correspond to each other, and a "Next" icon 54. A resident who possesses the user terminal 30 selects any one of the radio buttons 51, 52, 53 and then selects the "Next" icon 54.
[0142] Based on the selection of the "Next" icon 54 on the second screen (S17 in FIG. 4), the user terminal 30 causes the touch panel 35 to display the third screen shown in FIG. 8(A).
[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 was sleepy" that are associated with each other, and a "Next" icon 57. A resident who possesses the user terminal 30 selects either of the radio buttons 55, 56 and then selects the "Next" icon 57.
[0144] Based on the selection of "Next" icon 57 on the third screen (S17 in FIG. 4), user terminal 30 causes touch panel 35 to display the fourth screen shown in FIG. 8(B).
[0145] The fourth screen has the text "Menstrual Cycle", a radio button 58 and the text "Days 1-3" that are associated with each other, a radio button 59 and the text "Other", and an "End" icon 60. A resident who possesses the user terminal 30 selects either of the radio buttons 58, 59, and then selects the "End" icon 60.
[0146] The fourth screen is displayed on the touch panel 35 only in user terminals 30 owned by female residents. The application program 39 stores in advance in the terminal memory 32 the gender of the owner of the user terminal 30, and if the gender stored in the terminal memory 32 is female, the fourth screen is displayed on the touch panel 35, and if the gender is male, the fourth screen is not displayed on the touch panel 35. In 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 the 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 process 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 process 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. The scores related to the biometric data mainly indicate the physical fatigue level of the resident, and the higher the score, the higher the physical fatigue of the resident, and the lower the score, the lower the physical fatigue of the resident. High physical fatigue of the resident indicates poor physical condition, and low physical fatigue of the resident indicates good physical condition.
[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 answers in the judgment table (see FIG. 3(B)) (S24). For example, for the name "Yamada Taro" in the judgment table, mood is registered at "2", sleepiness at "1", and menstruation at "0" in the judgment table. The score for the question answers 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 answer to the question calculated in step S24 (S25). The management server 40 registers the calculated total score in the judgment table (see FIG. 3(B)) (S25). The process from step S22 to S25 for calculating the total score and registering it in the judgment table is an example of a physical condition determination 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 user IDs read out match, management server 40 registers a consecutive cooking flag of "1" in the record having a user ID that matches the user ID of the resident who was in charge of cooking for two consecutive days in the judgment table, and registers a consecutive cooking flag of "0" for the records of the other residents (S26).
[0156] The management server 40 executes a determination notification registration process to determine who will cook or who will be responsible for help / delivery, and to notify and register the determination based on the total score and the consecutive cook flag (S27).
[0157] Details of the determination notification registration process will be described with reference to Figures 5 and 6. Note that the determination notification registration process is executed for each family member.
[0158] 5, the management server 40 judges whether the total score of all residents who are qualified to cook is 5 points or more in the judgment 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 the residents selected "can't recover" in the question answer (S32). The determination in step S32 is made based on whether "feeling" is registered as 5 points in the determination table.
[0160] When the management server 40 determines that all residents who are qualified to cook have selected “can’t recover” in answering the question (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 be requested to provide cooking assistance for the target family.
[0161] When the management server 40 determines that the 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) possessed by each resident periodically sends an HTTP request including inquiry information to the management server 40 via the communication interface 33 etc. 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 proposal notified to the 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 is 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 the resident with the lowest overall score (in best physical condition), or all user terminals 30.
[0163] The user terminal 30 receives the HTTP response via the communication interface 33 etc. (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). To explain in more detail, 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 (the helper's first and last name) received in step S36 into an input field of the format data, generates 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 00?", a "Request" icon 61, and a "Do not request" icon 62. The process 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 assistance is to be requested (S38 in Fig. 5), and selects the "Do not request" icon 62 if assistance is not to be requested (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 pre-packaged 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 you accept cooking help from Mr. 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 cooking assistance is available from a helper, and transmits 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 judges whether the help notification information received in step S42 indicates that the helper has accepted the cooking support (S43). If the management server 40 judges that the helper has accepted the cooking support (S43: Yes), it registers the help / delivery flag of "1" in the judgment table (see FIG. 3(B)), and registers "0" in the field of the column named "cook" in the performance management database (S44), and ends the decision notification registration process (S27 in FIG. 4). On the other hand, if the management server 40 judges that the helper has declined the cooking support (S43: No), it returns an HTTP response including the delivery restaurant information read out in step S22 from the user management database (see FIG. 2(A)) to the user terminal 30 through 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 suggestion to be notified to the resident. The phone 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 etc. (S45). The user terminal 30 displays a delivery restaurant display screen (not shown) including the received delivery restaurant information on the touch panel 35 (S46). The delivery restaurant display screen has text indicating the store name, dish name, and price, and an "OK" icon. The process of step S46 is an example of a notification process. 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 name of the delivery restaurant and the name of the dish, 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, management server 40 registers a help / delivery flag of "1" in the judgment table (see Figure 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 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 a 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 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 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). 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, may be the user terminal 30 owned by a resident who has cooking qualifications, may be the user terminal 30 owned by the resident with the lowest overall score (in the best physical condition), or may be 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 for cooking is not 5 points or more (S31: No), that is, if 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 for cooking (S51). The identified resident is a resident who is qualified to cook and has a total score of less than 5 points (4 points or less) (hereinafter also referred to as a "person in good health").
[0178] As shown in FIG. 6, the management server 40 judges whether there are two or more residents in good health (S52). If the management server 40 judges that there are two or more residents in good health (S52: Yes), it judges 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 judges whether the residents in good health were in charge of cooking for two consecutive days based on whether a consecutive cook flag is registered in the judgment 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 is 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 health who has cooked the 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 specified period before. The specified period is, for example, one day. In other words, the resident in good health who did not cook yesterday is determined to be the cook. Alternatively, the specified period is one month. In other words, the resident who has 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 the resident cooked in the previous month (past cooking frequency) is an example of past cooking performance. The process 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 who was 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 process of step S56 is an example of a menu determination process.
[0181] More specifically, the management server 40 judges whether the total score of the resident selected as the cook is below a predetermined score (e.g., 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 in good health, it picks up dishes (solid menus) with a cooking level of "1" registered from the cooking database.
[0182] Next, the management server 40 further selects from the selected dishes dishes that suit the physical condition of the resident who will eat the dishes, based on the total scores of all residents other than the resident who has been selected as the cook (residents who will eat the dishes). For example, if the total score of all residents who will eat the dishes is 4 points or less and it is determined that they are in good physical condition, a dish such as "twice cooked pork" with a total score of "4 points or less" is selected. If the total score of one of the residents who will eat the dishes is 4 points or more and it is determined that the resident is in poor physical condition, a dish such as "rice porridge" with a total score of "5 points or less" is selected.
[0183] The management server 40 generates an HTTP response including the user ID of the resident determined to be 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 of the resident's user terminals 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 terminals 30 possessed by persons qualified to cook. The process 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, the terminal memory 32 of the user terminal 30 stores format data for the cook notification screen when the application program 39 is downloaded. The format data includes data for the resident determined to be the cook and data for the other residents. The user terminal 30 generates data to be entered into the input fields of the format data based on each piece of data included in the HTTP response, such as the user ID, and generates screen data for the cook notification screen. The user terminal 30 inputs the generated screen data into the touch panel 35 to display the cook notification screen on the touch panel 35.
[0186] FIG. 10(A) shows a first cook notification screen displayed on the touch panel 35 of the user terminal 30 of the resident who has been selected as the cook. The first cook notification screen has the text "You will be the cook for 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 there is a resident with a total score of 5 or more. The resident who has been selected as the cook recognizes that he or she has been selected as the cook and that there is a resident who is not feeling well through the first cook notification screen. After confirming these items, the resident who has been selected as the cook selects the "Next" icon 65. The user terminal 30 displays the menu recommendation screen shown in FIG. 10(B) on the touch panel 35 based on the selection of the "Next" icon 65.
[0187] The menu recommendation screen shown in Fig. 10(B) has the text "Since your mother-in-law is not feeling well, we recommend the following menu for your mother-in-law," candidate menus (names of dishes), and an "OK" icon 66. The resident who has been selected to be in charge of cooking selects a dinner menu from the recommended menus and selects the "OK" icon 66 (S59 in Fig. 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 has the text "Today's cook for dinner is Yamada Taro," the text "The health of all family members is good," the text "We recommend a good menu," and a "Next" icon 67. The resident other than the resident selected as the cook recognizes the name of the resident selected as the cook, that there is a resident who is not feeling well, and that all family members are in good health through the second cook notification screen. After confirming these items, 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 that the residents other than the resident determined to be the cook would like to eat in particular from the recommended menu, they will inform the resident determined to be the cook of the desired dish. The resident determined to be 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 determined to be 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 FIG. 6, based on receiving the resident's selection of the "OK" icon 66 on the menu recommendation screen (see FIG. 10(B)), the user terminal 30 sends an HTTP request including notification information having 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 through the communication interface 43 (S60). The management server 40 registers the user ID of the resident who was determined to be the cook in step S55 and the menu (dish name) received in step S60 in the performance management database (see FIG. 2(B)) (S61), and ends the decision notification registration process (S27 in FIG. 4) (return). Note that in FIG. 2(B), the display of the menu (dish name) selected by the resident who became the cook is omitted. 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 displays the names of dishes that have been cooked less or more times in the past (specialty dishes) among the picked menus (dish names) on the user terminal 30 of the resident who was determined to be the cook, with the names being ranked higher. 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), any resident who has not cooked for two consecutive days is 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 was in charge of cooking for two consecutive days, that is, 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). After that, the management server 40 and the user terminal 30 execute the processes from steps S56 to S61 described above, and end the determination notification registration process (S27 in FIG. 4) (return). The process of step S63 is an example of the cook determination process.
[0195] When 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 "can't recover" to the question (S64). When the management server 40 determines that all residents other than the specified person have selected the answer option "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 "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 "can't recover" (S64: No), it selects the resident who has not selected the answer option "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 will determine the cook based on past cooking performance. For example, the management server 40 will select the resident who cooked the least number of times last month as the cook.
[0197] In this way, if the person in the best physical condition has not been the cook 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 the cook for two consecutive days (S62: Yes), he / she is exceptionally determined to be the cook only if the other residents have selected "can't recover" (S64: Yes → S63). If the person in the best physical condition has been the cook for two consecutive days (S62: Yes) and none of the other residents have 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 identifies the physical condition (physical fatigue) of each resident who is qualified to cook at a predetermined time before cooking dinner begins based on the biometric data, and determines who will cook the meal for today (a predetermined day) based on the identified 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 who is 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 successive cook flag generated based on the user ID registered in the performance data management database. This ensures fairness in the allocation of cooking duties among residents who are qualified to cook.
[0200] In this embodiment, mental fatigue, which is difficult to identify from biometric data, is identified by the answers to questions given to the resident. Therefore, the cook selection system 10 can select a cook for the day by considering not only the physical fatigue of a resident who is qualified to cook, but also the mental fatigue.
[0201] In this embodiment, in the question scoring table, answer options (radio buttons 51 to 53, 55, 56, 58, 59) for questions are associated with scores. Therefore, the cook determination system 10 can specify 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 from 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 type of menu is determined according to the physical condition of the residents other than the resident selected as the cook, and the cook is notified. Therefore, the cook selection system 10 can feed easily digestible food 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 residents are asked to ask a helper for cooking assistance, or are offered a suggestion to order delivery, etc. 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 decision system 10 makes it easy for the resident to request cooking assistance from the helper and to order delivery.
[0207] [Variations] In the embodiment, an example has been described in which the cooker determination system 10 includes the management server 40. However, when the cooker determination system 10 does not require a data collection function, it may include a personal computer (so-called PC) installed in the home instead of the management server 40. In other words, the cooker determination system 10 may be a stand-alone system separated from an external server. The PC may be, for example, a PC owned by a resident, or a PC installed in the home by a service provider for managing the home. A program that executes the same process as the management program 45 is implemented in the PC. 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 a 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 that 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 member. 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 included 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 a house.
[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 biodata of the resident.
[0211] In the embodiment, an example has been described in which the wearable terminal 20 includes the temperature sensor 25, the optical 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 optical sensor 26, the acceleration sensor 27, and the biopotential sensor 28. In addition, the wearable terminal 20 may not include some of the sensors among the temperature sensor 25, the optical 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 a part 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 is possible to 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 directly transmit the acquired biometric data 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 is described in which the physical condition of a resident who is qualified to cook is identified based on biometric data and a question answer. However, the physical condition of a resident who is qualified to cook may be identified only from biometric data. In other words, the physical condition of a resident who is qualified to cook may be identified only from physical fatigue.
[0216] In the embodiment, an example is described in which a cook is determined based on the physical condition of the identified resident today and the past cooking performance. However, a cook may be determined based only on the physical condition of the identified resident today. For example, a resident in the best physical condition (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 to a question are associated with scores and answers to a question are scored. However, instead of ranking a plurality of combinations of answer options to quantify the mental fatigue of a resident, a ranking of mental fatigue may be performed on the residents. For example, the residents may be ranked in terms of mental fatigue, with the ranking of residents who selected "can't recover," "sleepy," and "1st to 3rd day" being ranked first, and the ranking of residents who selected "no problem," "no problem," and "other" being ranked last. Then, when the physical fatigue levels identified from the biometric data are the same, the resident with the lowest ranking in terms of mental fatigue may be determined to be in charge of cooking.
[0218] In the embodiment, an example has been described in which a recommended menu is determined based on the physical condition of the resident determined to be 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 determined to be the cook, or the recommended menu may be determined based only on the physical condition of the residents other than the resident determined to be 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 included in the user terminal 30. In that 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 Saturday and Sunday every week. In this case, Saturday and Sunday every week are examples of predetermined days.
[0221] In the embodiment, an example is described in which, instead of determining who will cook, if all residents who are qualified to cook are in poor health, the residents are suggested to ask a helper to help with cooking or to order takeout. However, such a suggestion does not have to be made, and for example, if all residents who are qualified to cook are in poor health, the notification process may only 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 health condition determination process for determining the health condition of each resident at a predetermined time on a predetermined day based on the biometric data; A process of determining who will be in charge of cooking for the specified day based on the physical condition of each identified resident; and a notification process of notifying the determined cook via the notification device.
[0223] [Appendix 2] The control device includes: A storage process is further performed to store the determined cook in memory as performance data in association with a date, The cook determination system according to claim 1, wherein the cook determination process is a process of determining a cook by determining residents to be excluded from 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 an answer of the resident to the question, the answer being inputted through the input interface. 3. The cook determination system according to claim 1, wherein the cook determination process is a process of determining a cook further based 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 a physical condition indicated by a total score calculated based on the answers.
[0226] [Appendix 5] The cook determination system according to claim 1, wherein the physical condition identification process is a process of identifying the physical condition of each resident based on an amount of deviation of the biological data from basic biological 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 having a cooking level corresponding to the determined physical condition level of the cook as a dish to be proposed to the cook; The cook determination system according to claim 1, wherein the notification process is a process of notifying the selected 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, as dishes to be proposed to the person in charge of cooking, dishes according to the physical condition levels of the residents other than the resident determined to be the person in charge of cooking; The cook determination system according to claim 1 or 6, wherein the notification process is a process of notifying the selected cook and type of food.
[0229] [Appendix 8] The above-mentioned cooking staff selection process is as follows: Based on the determination that the physical condition of the resident 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 suggestion stored in the memory instead of the person in charge of cooking; The cook decision 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 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 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 process of determining who will be in charge of cooking 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 through the first communication interface; The second program 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. Terminal 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 health condition determination process for determining the health condition of each resident at a predetermined time on a predetermined day based on the biometric data; A process of determining who will be in charge of cooking for the specified day based on the physical condition of each identified resident; and notifying the determined cook via the notification device.
2. The control device includes: A storage process is further performed to store the determined cook in memory as performance data in association with a date; 2. 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 further based 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 an answer of the resident to the question, the answer being inputted through the input interface. The cook determination system according to claim 1 , 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 a 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 determining process determines the physical condition of each resident based on a deviation of the biological data from basic biological 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 having a cooking level corresponding to the determined physical condition level of the cook as a dish to be proposed to 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.
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, as dishes to be proposed to the person in charge of cooking, dishes according to the physical condition levels of the residents other than the resident determined to be the person in charge of cooking; The cook determination system according to claim 1 , wherein the notification process notifies the user of the determined cook and type of food.
8. The above-mentioned cooking staff selection process is as follows: Based on the determination that the physical condition of the resident 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 suggestion stored in the memory instead of the person in charge of cooking; The cook determination system according to claim 1 , wherein the notification process notifies the user of the determined cook or the suggestion through the notification device.
9. The cook determination system according to claim 8 , wherein the suggestion includes contact information preregistered 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 process of determining who will be in charge of cooking 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 through the first communication interface; The second program is A program that causes the second computer to execute a notification process for displaying the received name of the person in charge of cooking on the display.
Citation Information
Patent Citations
Menu creation system
JP2009169605A
Housekeeping allotment system
JP2020177447A
Cited By
Cooking assistance work management system
JP2026125169A
