Eating management method, eating management system, eating management device, food service check terminal, and program
The food management system addresses serving errors by using parent and classroom monitors to ensure students receive allergen-free meals, improving meal safety and health outcomes.
Patent Information
- Application Number
- JP2023077300
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-09
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2043-05-09
AI Technical Summary
Existing school lunch management systems fail to prevent students from consuming meals that contain ingredients they are allergic to, despite precautions taken during meal production, due to errors during serving.
A food management system utilizing parent, school, and classroom monitors to track student allergies, display meal availability, and detect serving errors, ensuring accurate distribution of allergen-free meals.
Prevents students from receiving meals they are allergic to by providing real-time monitoring and correction of serving errors, enhancing meal safety and student health.
Smart Images

Figure 2024162098000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a meal management method, a meal management system, a meal management device, a meal distribution check terminal device, and a program. [Background technology]
[0002] Students may develop allergic reactions based on the ingredients in school lunches. There is a need for technology to manage school lunches so that they are not served meals that cause allergic reactions.
[0003] In the menu management system disclosed in Patent Document 1, when a planned menu contains an allergy-causing ingredient, the nutritional value of the allergy-causing ingredient is identified and an alternative menu is planned. Also, based on the information of registered students, information on children who should be accommodated is output. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2016-038645 A Summary of the Invention [Problem to be solved by the invention]
[0005] Traditionally, in school lunches, pots containing meals for multiple people are brought into classrooms in serving units and distributed to each student by the students. Even if consideration is given to whether students can eat the meals during the lunch preparation stage, if a mistake occurs during distribution, there is a possibility that students may develop allergic reactions.
[0006] The menu management system disclosed in Patent Document 1 does not take into consideration the possibility that when food is served, a menu item that a student would like to avoid may be presented.
[0007] The present invention has been made in consideration of the above points, and aims to provide a technology that prevents students from being served menu items that they would like to avoid eating when food is being served. [Means for solving the problem]
[0008] The present application includes a number of means for solving at least some of the above problems, examples of which are as follows.
[0009] In order to solve the above problem, one embodiment of the present invention provides an eating management method that uses a parent terminal device owned by a parent, a eating management device owned by a school, and a classroom monitor installed in a classroom, and is characterized in that it comprises an eating schedule registration step in which, when an input of whether or not eating is possible for each of a plurality of serving units included in lunches provided to students by the school is received from the parent terminal device, eating schedule information is registered in the eating management device, and a list display step in which, based on the eating schedule information, on the day lunches are provided, information indicating the students included in the classroom is associated with information indicating whether or not each serving unit can be eaten, and the list display is displayed on the classroom monitor.
[0010] The eating management method of the present invention may be characterized by comprising a student information reading procedure in which a student information reading device reads student information that identifies a student, and a food serving display procedure in which a food serving table monitor arranged near the food serving table displays whether or not the student whose student information has been read in the student information reading procedure is able to eat.
[0011] The eating management method of the present invention may be characterized by comprising a tableware distribution procedure in which tableware is distributed to students, a tableware type reading procedure in which a tableware information reading device reads the type of tableware distributed to the student, and a serving error display procedure in which, if a serving error occurs regarding the tableware read in the tableware type reading procedure for a student whose student information has been read in the student information reading procedure, information indicating the serving error is displayed on the serving counter monitor.
[0012] The present invention may be characterized in that in the food serving display procedure, the availability of food for each serving unit is displayed in a different color, and in the tableware distribution procedure, tableware of a color corresponding to the color displayed in the food serving display procedure is distributed for each serving unit.
[0013] In addition, in order to solve the above-mentioned problems, an eating management system according to another aspect of the present invention is characterized in that it comprises an eating schedule registration unit that registers in eating schedule information whether or not each of a plurality of serving units included in the lunch provided by the school to students can be eaten based on input operations by a parent, and a list display control unit that uses the eating schedule information to associate information indicating the students in the classroom on the day the lunch is provided with information indicating whether or not each serving unit can be eaten, and displays the associated information on a classroom monitor installed in the classroom.
[0014] The eating management system of the present invention may comprise an allergy information registration unit which registers a student's allergic ingredients in student-specific allergy information based on input operations by a guardian; a menu registration unit which registers the serving unit of school lunches and the ingredients contained in the serving unit; and an eating schedule registration request unit which displays, for each day school lunches are provided, a number of serving units and whether or not the student has an allergy to the ingredients of the serving unit, and accepts input operations by the student's guardian as to whether or not the student can eat the ingredients for each serving unit, and the eating schedule registration unit may be characterized in that it registers the information input operations received by the eating schedule registration request unit in the eating schedule information.
[0015] The eating management system of the present invention may be characterized by comprising a student information acquisition unit that acquires student information that identifies a student, and a food serving display control unit that displays information indicating whether or not the student whose student information has been acquired by the student information acquisition unit is able to eat on a food serving table monitor installed on a food serving table.
[0016] The eating management system of the present invention may be characterized by comprising a tableware information acquisition unit that acquires tableware information indicating the type of tableware from a recording medium carried by each piece of tableware distributed to a student, and a serving error detection unit that determines whether there is an excess or deficiency in the serving unit that the student whose student information has been acquired by the student information acquisition unit plans to eat, based on the type of tableware acquired by the tableware information acquisition unit and the eating plan information.
[0017] The serving display control unit of the present invention may be characterized in that when the serving error detection unit determines that there is an excess or shortage in the serving, information identifying the serving unit that is insufficient or surplus is displayed on the serving counter monitor.
[0018] The list display control unit of the present invention may be characterized in that it displays on the classroom monitor students for whom the food service error detection unit has determined that the food service is neither excessive nor insufficient, differently from other students.
[0019] The eating schedule registration unit of the present invention may be characterized in that it registers in the eating schedule information whether or not each of the serving units, which indicate a staple meal, side dish, supplementary meal, or beverage, can be eaten, and the serving display control unit displays on the serving counter monitor the serving units that the student can eat and the serving units that the student cannot eat using a different code for each serving unit.
[0020] In addition, in order to solve the above-mentioned problems, an eating management device according to another aspect of the present invention is characterized in that it comprises an allergy information registration unit that registers a student's allergy ingredients in student-specific allergy information based on an input operation into a parent terminal device; a menu registration unit that registers the unit of school lunch serving and the ingredients contained in the unit of serving; an eating plan registration unit that queries the parent terminal device held by the parent of a student whose school lunch contains the allergy ingredients in the unit of serving of school lunches served during a specified period about eating plans, obtains information indicating whether or not eating is possible for each unit of serving, and registers this as eating plan information; and a display request reception unit that transmits the eating plan information of students included in a classroom in response to a request from a teacher terminal device that specifies a classroom.
[0021] In addition, in order to solve the above problem, a food serving check terminal device according to another aspect of the present invention is characterized in that it comprises a student information acquisition unit that reads student information that identifies a student, a tableware information acquisition unit that acquires tableware information indicating the type of tableware from a recording medium carried by each piece of tableware distributed to the student, an eating plan acquisition unit that acquires eating plan information for a specified period of time for the student, and a serving error detection unit that determines whether there is an excess or deficiency in the serving unit that the student whose student information has been acquired by the student information acquisition unit plans to eat, based on the type of tableware acquired by the tableware information acquisition unit and the eating plan information.
[0022] In addition, in order to solve the above-mentioned problems, a program according to another aspect of the present invention is a program that causes an eating management device to execute an eating management method, and is characterized in that it executes the following steps: an allergy information registration procedure for registering a student's allergy ingredients in student-specific allergy information based on an input operation into a parent terminal device; a menu registration procedure for registering the unit of school lunch serving and the ingredients contained in the unit of school lunch serving; an eating plan registration procedure for inquiring about eating plans from the parent terminal device held by the parent of a student for whom the allergy ingredients are present in the unit of school lunch serving provided during a specified period, obtaining information indicating whether or not eating is possible for each unit of serving, and registering this as eating plan information; and a display request acceptance procedure for transmitting the eating plan information of students included in a classroom in response to a request from a teacher terminal device that specifies a classroom.
[0023] In addition, in order to solve the above problem, a program according to another aspect of the present invention is a program that causes a food serving check terminal device to execute a food serving check method, and is characterized by executing the following steps: a student information acquisition step of reading student information that identifies the student from a recording medium held by the student; a tableware information acquisition step of acquiring tableware information indicating the type of tableware from a recording medium held by each of the tableware or containers distributed to the student; an eating plan acquisition step of acquiring eating plan information for the student for a specified period of time; and a food serving error detection step of determining whether or not there is an excess or deficiency in the serving unit that the student whose student information was acquired in the student information acquisition step plans to eat, based on the type of tableware acquired in the tableware information acquisition step and the eating plan information. Effect of the Invention
[0024] According to the present invention, it is possible to provide a technology that prevents a student from being served a menu item that he or she wishes to avoid eating.
[0025] Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]
[0026] [Figure 1] FIG. 1 is a diagram illustrating an example of an overview of an application support system. [Diagram 2] FIG. 2 is an example of a functional block diagram of a food management system. [Diagram 3] FIG. 13 is a diagram showing an example of a data structure of student-specific allergy information. [Figure 4] FIG. 2 is a diagram showing an example of a data structure of menu allergen information. [Diagram 5] FIG. 4 is a diagram showing an example of a data structure of eating schedule information. [Figure 6] FIG. 2 is a diagram illustrating an example of a hardware configuration of the dietary management device. [Figure 7] 13 is a flowchart showing an example of an allergy information registration process. [Figure 8] 13 is a flowchart showing an example of a menu information registration process. [Figure 9] FIG. 11 is a sequence diagram showing an example of an eating schedule registration process. [Figure 10] 13 is a flowchart showing an example of an eating list display process. [Figure 11] 13 is a flowchart showing an example of a food distribution check process. [Figure 12] 13 is a flowchart showing an example of a catering management process. [Figure 13] FIG. 13 is a diagram showing an example of an allergy information registration screen. [Figure 14] FIG. 13 is a diagram showing an example of a menu registration screen. [Figure 15] FIG. 13 is a diagram showing an example of an eating registration screen. [Figure 16] FIG. 11 is an image diagram showing an example of a process for determining the presence or absence of allergies. [Figure 17] FIG. 13 is a diagram showing an example of an eating list screen. [Figure 18] 13A to 13C are diagrams illustrating an example of screen transitions on the student serving schedule screen. [Figure 19] FIG. 13 is a diagram showing an example of an error output (part 1). [Figure 20] FIG. 2 is a diagram showing an example of an error output (part 2). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0027] The present invention will be outlined below with reference to the drawings. Fig. 1 is a diagram showing an example of an outline of a meal management system 1. The meal management system 1 includes a meal management device 10, a parent terminal device 20, a school lunch center terminal device 30, a teacher terminal device 40, a classroom monitor 460, a serving counter monitor 560, a student information reading device 570, and a tableware information reading device 580.
[0028] The meal management device 10 is a device managed by, for example, a business that provides meal management services. The parent terminal device 20 is a device owned by parent A of student B. The school lunch center terminal device 30 is a device owned by a school lunch center that provides school lunches, and may be installed within a school or may be set up at the business premises of a school lunch provider outside a school.
[0029] The teacher terminal device 40 is a device owned by the teacher. The classroom monitor 460 is a display device installed in a classroom, connected to the teacher terminal device 40, and displays information in response to a display instruction from the teacher terminal device 40. The serving counter monitor 560 is a device placed near the serving counter, and displays information in response to a display instruction from a serving check terminal device 50 (not shown). The student information reading device 570 and the tableware information reading device 580 are installed near the serving counter and connected to the serving check terminal device 50. The serving check terminal device 50 is installed, for example, in a classroom and executes processing in response to an input operation to the serving counter monitor 560 composed of a touch panel, but may be installed outside the classroom. That is, among the devices owned by the eating management system 1, at least the teacher terminal device 40, the classroom monitor 460, the serving counter monitor 560, the student information reading device 570, and the tableware information reading device 580 are installed in a classroom.
[0030] In the example shown in Fig. 1, the parent terminal device 20 is connected to the meal management device 10 via a network N. The meal management device 10, the school lunch center terminal device 30, the teacher terminal device 40, and the meal distribution check terminal device 50 are connected to each other via an internal network that can be connected only in a closed environment such as a school or a board of education. However, the connection status of each device is not limited to the example shown in Fig. 1. Each device may be connected to each other via the network N so that they can communicate with each other.
[0031] When the parent terminal device 20 accepts the input operation of the food ingredients that cause allergic symptoms for Student B, it sends the input information to the eating management device 10. When the menu has been decided, the school lunch center terminal device 30 accepts the input operation of the school lunch serving date and menu. The input information is sent to the eating management device 10. The eating management device 10 sends the menu to be served during a specified period to the parent terminal device 20. The parent terminal device 20 accepts the input operation of whether or not each menu item sent from the eating management device 10 can be eaten, and sends a request to register the eating plan to the eating management device 10.
[0032] On the day when the school lunch is provided, the teacher terminal device 40 obtains the eating schedule of the students B in the class from the eating management device 10. The teacher terminal device 40 displays information on the classroom monitor 460 indicating whether or not the students B in the classroom (i.e., the class) can eat the school lunch in each serving unit.
[0033] In the example shown below, one meal of school lunch includes multiple serving units. In this embodiment, each serving unit indicates a distinction between a staple food, a side dish, a supplementary food, and a beverage, and each serving unit is served in a different colored dish or container. The serving units included in the school lunch are not limited to the distinction between a staple food, a side dish, a supplementary food, and a beverage. For example, one staple food may be divided into multiple serving units, or a side dish and a supplementary food may make up one serving unit.
[0034] When serving the food, student B has the student information reading device 570 read the IC card X. Note that the storage medium that student B has read is not limited to an IC card. For example, a two-dimensional code printed on a printed material distributed to student B may be read. The IC card X stores a student ID that identifies student B. The food serving check terminal device 50 identifies student B who read the IC card X, and displays information indicating whether student B can eat or not on the food serving counter monitor 560 for each serving unit.
[0035] After presenting IC card X to student information reader 570, student B places the tableware on the tray and walks forward, causing the tableware to be read by tableware information reader 580. Tableware information reader 580 reads IC chip Y in the tableware and obtains the tableware information stored in IC chip Y. Note that the storage medium in the tableware is not limited to an IC chip. Also, the tableware may not yet have lunch served inside, or may already have lunch served inside. Note that the color of the tableware may correspond to a code displayed on the serving counter monitor 560 indicating whether or not the tableware can be eaten.
[0036] The food distribution check terminal device 50 compares the eating schedule of student B, whose student information has been read, with the types of tableware contained in the tableware information read by the tableware information reading device 580, and determines whether there is a shortage or surplus. If there is a shortage or surplus, the food distribution check terminal device 50 causes the tabletop monitor 560 to display an error screen.
[0037] FIG. 2 is an example of a functional block diagram of the eating management system 1. The eating management device 10 is an information processing device such as a server computer or a PC (Personal Computer). The eating management device 10 includes a processing unit 110, a storage unit 120, an input unit 130, an output unit 140, and a communication unit 150. The processing unit 110 controls the entire eating management device 10. The storage unit 120 stores information required for processing by the processing unit 110. The input unit 130 accepts input of information from each input device connected via an input IF (Interface) 14 described later. The output unit 140 outputs information via an output device connected via an output IF 15 described later. The communication unit 150 mediates the transmission and reception of information to and from other devices connected to be able to communicate with each other.
[0038] The processing unit 110 includes a menu registration unit 111, an allergy information registration unit 112, a meal schedule registration unit 113, a meal distribution management unit 114, and a display request reception unit 115. In response to a menu allergen information registration request from the school lunch center terminal device 30, the menu registration unit 111 registers the menu of each serving unit that constitutes the lunch and the ingredients contained in the menu in the menu allergen information 122 described below. The allergy information registration unit 112 registers allergy ingredients of student B in the student-specific allergy information 121 described below based on an input operation by guardian A to the guardian terminal device 20.
[0039] In the example shown below, the food eating management system 1 in this embodiment registers Student B's allergenic ingredients in the food eating management device 10. However, the food eating management system 1 only needs to register ingredients that Parent A wants Student B to avoid eating. In other words, factors that Parent A wants to avoid eating are not limited to those that cause allergic reactions.
[0040] The eating schedule registration unit 113 inquires about eating schedules from the parent terminal device 20 owned by parent A of student B, who has an allergy-causing ingredient in the school lunch menu provided during a specified period. As a result of the inquiry, the eating schedule registration unit 113 acquires an eating schedule registration request in which information indicating whether or not eating is possible is associated with each of a plurality of serving units included in the school lunch provided to student B by the school, and registers the request in the eating schedule information 123 described below. For example, the eating schedule registration unit 113 registers whether or not eating is possible for each of staple foods, side dishes, supplementary foods, and beverages.
[0041] When the food distribution management unit 114 acquires information indicating the completion of food distribution to each student B from the food distribution check terminal device 50 for each student B, it transmits the information to the teacher terminal device 40. In response to an eating schedule request from the teacher terminal device 40 that specifies a classroom, the display request receiving unit 115 transmits eating schedule information 123 of student B who is included in the classroom. Also, in response to an eating schedule request from the food distribution check terminal device 50 that specifies a student ID, the display request receiving unit 115 transmits eating schedule information 123 of student B.
[0042] The storage unit 120 stores student-specific allergy information 121, menu allergen information 122, and eating schedule information 123. The student-specific allergy information 121 is information in which ingredients that cause allergic symptoms in student B are registered. In this embodiment, it is sufficient that ingredients that student B cannot eat or wants to avoid eating are registered.
[0043] Menu allergen information 122 is information that registers ingredients that may be allergens for each serving unit of the provided school lunch. Eating schedule information 123 is information that registers the serving date of the school lunch and the serving unit that Student B plans to eat.
[0044] The parent terminal device 20 is an information processing device such as a PC, a smartphone, or a tablet. The parent terminal device 20 includes a processing unit 210, an input unit 230, an output unit 240, and a communication unit 250. The processing unit 210 performs overall control of the entire parent terminal device 20. The input unit 230 accepts information input from each input device connected via an input IF. The output unit 240 outputs information via an output device connected via an output IF. The communication unit 250 mediates the transmission and reception of information to and from other devices connected for communication.
[0045] The processing unit 210 includes an allergy registration request unit 211 and an eating schedule registration request unit 212. In response to an input operation from parent A, the allergy registration request unit 211 transmits an allergy information registration request including ingredients that cause an allergic reaction in student B to the eating management device 10. When the eating schedule registration request unit 212 receives an inquiry about an eating schedule from the eating management device 10, it displays multiple serving units and whether student B has an allergy to the ingredients of the serving units for each day that school lunches are provided, and receives an input operation by parent A as to whether or not eating is possible for each serving unit. The eating schedule registration request unit 212 transmits an eating schedule registration request to the eating management device 10 in response to an input operation by parent A.
[0046] The school lunch center terminal device 30 is a device that accepts input operations from staff at the school lunch center, and is, for example, an information processing device such as a PC, a smartphone, or a tablet. The school lunch center terminal device 30 includes a processing unit 310, an input unit 330, an output unit 340, and a communication unit 350. The processing unit 310 performs overall control of the school lunch center terminal device 30 as a whole. The input unit 330 accepts input of information from each input device connected via an input IF. The output unit 340 outputs information via an output device connected via an output IF. The communication unit 350 mediates the transmission and reception of information to and from other devices that are communicatively connected.
[0047] The processing unit 310 includes a menu registration request unit 311. In response to an input operation by the person in charge, the menu registration request unit 311 transmits a menu allergen information registration request to the eating management device 10. The menu allergen information registration request lists ingredients that may be allergens for each serving unit of meals provided during a specified period.
[0048] The teacher terminal device 40 is an information processing device such as a PC, a smartphone, or a tablet, and includes a processing unit 410, an input unit 430, an output unit 440, and a communication unit 450. The processing unit 410 performs overall control of the entire school lunch center terminal device 30. The input unit 430 accepts information input from each input device connected via an input IF. The output unit 440 outputs information via an output device connected via an output IF. The communication unit 450 mediates the transmission and reception of information to and from other devices connected for communication.
[0049] The processing unit 410 includes a list display control unit 411. When the list display control unit 411 receives an input operation specifying the grade and class for which the list is to be displayed, it transmits information indicating an eating schedule request that specifies the input grade and class to the eating management device 10. The list display control unit 411 uses the eating schedule information received as a response to the eating schedule request to display an eating list screen on the classroom monitor. On the eating list screen, the name of student B, who has a serving unit that cannot be eaten, is associated with information indicating whether or not each serving unit can be eaten.
[0050] The output unit 440 of the teacher terminal device 40 displays information on a classroom monitor 460. The classroom monitor 460 is a display device such as an OLED (Organic Light Emitting Diode) display. The classroom monitor 460 may be a touch panel display that accepts input operations.
[0051] The food distribution check terminal device 50 is an information processing device such as a PC, a smartphone, or a tablet, and includes a processing unit 510, an input unit 530, an output unit 540, and a communication unit 550. The food distribution check terminal device 50 may be integrated with the eating management device 10 or the teacher terminal device 40.
[0052] The processing unit 510 performs overall control of the entire food service center terminal device 30. The input unit 530 accepts information input from each input device connected via an input IF. The output unit 540 outputs information via an output device connected via an output IF. The communication unit 550 mediates the transmission and reception of information to and from other devices connected for communication.
[0053] The processing unit 510 includes a student information acquisition unit 511, a tableware information acquisition unit 512, an eating schedule acquisition unit 513, a tableware serving error detection unit 514, and a tableware serving display control unit 515. The student information acquisition unit 511 causes the student information reading device 570 to read the student information identifying student B contained in the IC card X. The tableware information acquisition unit 512 causes the tableware information reading device 580 to read tableware information indicating the type of tableware to be distributed to student B. The tableware includes containers such as milk packages.
[0054] The eating schedule acquisition unit 513 acquires eating schedule information for a specified period of time for student B. When there is a surplus or shortage between the tableware distributed to student B and the eating schedule, the serving error detection unit 514 causes the serving counter monitor 560 to display information indicating a serving error. When tableware of a serving unit that is not scheduled to be consumed is distributed to student B, or when tableware of a serving unit that is scheduled to be consumed is not distributed to student B, the serving error detection unit 514 determines that there is a serving error and causes the serving counter monitor 560 to display information indicating that an error has been detected.
[0055] The serving display control unit 515 causes the serving counter monitor 560 to display whether or not the student B, whose student ID is read by the student information acquisition unit 511, can eat the food. The serving display control unit 515 causes the serving counter monitor 560 to display information specifying the serving unit that is insufficient or excessive.
[0056] The input section 530 of the meal distribution check terminal device 50 is connected to a student information reading device 570 and a tableware information reading device 580. The student information reading device 570 is a device that reads information from an IC card X held by student B. A student ID that identifies student B is stored in the IC card X as student information. The tableware information reading device 580 is a device that reads tableware information from an IC chip Y attached to the tableware. The tableware information includes information that identifies the type of tableware. The type of tableware corresponds to information that indicates the unit of serving of school lunches. There are no limitations on the types of IC card X and IC chip Y, and general chips and tags can be used.
[0057] The output unit 540 of the food service check terminal device 50 is connected to a food service counter monitor 560. The food service counter monitor 560 is a touch panel device that accepts input operations.
[0058] 3 is a diagram showing an example of the data structure of the student-specific allergy information 121. The student-specific allergy information 121 is information in which ingredients that cause allergic symptoms in student B are registered for each piece of information indicating student B. The student-specific allergy information 121 is generated in response to a request for allergy information registration from the parent terminal device 20.
[0059] 4 is a diagram showing an example of the data structure of the menu allergen information 122. The menu allergen information 122 is information in which the date on which the school lunch is served, information specifying the serving unit, and ingredients included in the menu for that serving unit are registered in association with each other.
[0060] FIG. 5 is a diagram showing an example of the data structure of eating schedule information 123. The eating schedule information 123 is information in which the date of school lunch provision and information indicating whether or not each unit of provision can be consumed are associated with each combination of the grade, class, and name to which student B belongs. In the following, the combination of grade and class may be explained using the word "classroom." The top record of the eating schedule information 123 shown in this figure indicates that "Yamada Hanako" who belongs to "Class 1-1" can consume "staple food," "supplementary food," and "drinks" from the school lunch provided on "June 1st," but is not allowed to consume "side dishes."
[0061] 6 is a diagram showing an example of the hardware configuration of the dietary management device 10. The dietary management device 10 includes a calculation device 11, a memory 12, an external storage device 13, an input IF 14, an output IF 15, and a communication IF 16, and each component is connected by a bus.
[0062] The arithmetic device 11 is a arithmetic device such as a CPU (Central Processing Unit), and executes processing according to a program recorded in the memory 12 or the external storage device 13. In the diet management device 10, processing is performed by the arithmetic device 11 which operates according to a program read onto the memory 12 or the external storage device 13. Each of the processing units constituting the processing unit 110 realizes its respective function by the arithmetic device 11 executing a program.
[0063] The memory 12 is a storage device such as a RAM (Random Access Memory) or a flash memory, and functions as a storage area from which programs and data are temporarily read. The external storage device 13 is, for example, a writable and readable storage medium such as a HDD (Hard Disk Drive), a CD-R (Compact Disc-Recordable), or a DVD-RAM (Digital Versatile Disk-Random Access Memory), and a storage media drive.
[0064] The input IF14 is an interface connected to an input device such as a mechanical key or a touch panel, and receives an operation signal from the input device. The output IF15 is an interface for outputting information to an output device built into or connected to the eating management device 10. The communication IF16 is an interface for connecting the eating management device 10 to a network N and a bus, and is connected to a communication device such as a LAN (Local Area Network) card. The function of the communication unit 150 is realized by the communication IF16. The eating management device 10 may have a storage medium drive device (not shown) and input and output information from a portable medium.
[0065] The hardware configurations of the parent terminal device 20, the school lunch center terminal device 30, the teacher terminal device 40, and the meal distribution check terminal device 50 are similar to that of the meal management device 10, so explanations will be omitted.
[0066] 7 is a flowchart showing an example of allergy information registration processing. For example, before the processing of this flowchart starts, a two-dimensional code including a URL of a web page used by the dietary management device 10 for the allergy information registration processing is provided from the school to parent A. The processing of this flowchart starts when the parent terminal device 20 reads the two-dimensional code via the input unit 230 and requests the dietary management device 10 for an allergy information registration screen using the URL.
[0067] First, the allergy registration request unit 211 displays the allergy information registration screen 261 and accepts input (step S11).
[0068] 13 is a diagram showing an example of the allergy information registration screen 261. For example, the allergy information registration screen 261 displays a list of selectable ingredients along with the name of student B. The allergy information registration screen 261 accepts the selection of ingredients that student B wants to avoid eating.
[0069] Returning to Fig. 7 for the explanation, the allergy registration request unit 211 then transmits the input information to the eating management device 10 (step S12). Specifically, the allergy registration request unit 211 transmits information indicating an allergy information registration request, including a student ID identifying student B and information identifying the ingredient selected on the allergy information registration screen 261, to the eating management device 10. Thereafter, the allergy registration request unit 211 ends the processing of this flowchart.
[0070] When the allergy information registration unit 112 of the dietary management apparatus 10 receives the information indicating the allergy information registration request, it generates the student-specific allergy information 121 using the received information.
[0071] Fig. 8 is a flowchart showing an example of menu information registration processing. For example, before the processing of this flowchart starts, a two-dimensional code including a URL of a web page used by the dietary management device 10 for the menu information registration processing is provided from the school to a person in charge of the school lunch center. The processing of this flowchart starts when the school lunch center terminal device 30 reads the two-dimensional code via the input unit 330 and requests the dietary management device 10 for a menu registration screen using the URL.
[0072] First, the menu registration request unit 311 displays the menu registration screen 361 and accepts input (step S21).
[0073] 14 is a diagram showing an example of menu registration screen 361. Menu registration screen 361 is a screen that displays the menu for the serving unit of the lunch to be served on the date and the candidate ingredients included in the menu so that they can be input. The staff at the school lunch center inputs the menu corresponding to the serving unit and the ingredients included in the menu to school lunch center terminal device 30.
[0074] Returning to Fig. 8 for explanation, the menu registration request unit 311 then transmits the input information to the dietary management device 10 (step S22). Specifically, the menu registration request unit 311 transmits information indicating a menu registration request including a date, a menu for each serving unit, and a combination of ingredients to the dietary management device 10. After that, the menu registration request unit 311 ends the processing of this flowchart.
[0075] When the menu registration unit 111 of the dietary management device 10 receives the information indicating the menu registration request, it generates menu allergen information 122 using the received information.
[0076] 9 is a sequence diagram showing an example of an eating schedule registration process. Before the process of this sequence diagram starts, for example, the email address of guardian A is registered in the eating management device 10. When the menu registration unit 111 of the eating management device 10 generates the menu allergen information 122, for example, the eating schedule registration unit 113 of the eating management device 10 sends an email containing a URL for accessing an eating schedule registration screen to the email address of guardian A. When the parent terminal device 20 accesses the address described in the received email and a student information input screen (not shown) is displayed, the process of this sequence diagram starts.
[0077] First, the eating schedule registration request unit 212 of the parent terminal device 20 accepts input of the grade, class, and name on the student information input screen (step S31). The eating schedule registration request unit 212 transmits the input information to the eating management device 10.
[0078] Next, the eating schedule registration unit 113 of the eating management device 10 refers to the menu allergen information 122 and determines whether or not the student has an allergy during the specified period (step S32). Specifically, the eating schedule registration unit 113 selects the menu allergen information 122 of the school lunch provided during the specified period as the processing target. The eating schedule registration unit 113 identifies the student-specific allergy information 121 using the name of the student B input in step S31, and compares it with the menu allergen information 122 to be processed, thereby determining whether or not the student B has an allergy during the specified period for each serving unit.
[0079] Fig. 16 is an image diagram showing an example of the allergy judgment process. In the example shown in this figure, first, for the serving unit of "(1) staple food (bread)", the menu includes the ingredient "wheat", but "wheat" is not registered as an ingredient that causes allergic symptoms in the student-specific allergy information 121 of the relevant student B. The eating schedule registration unit 113 calculates the logical product of the student-specific allergy information 121 and the menu allergen information 122 for the serving unit of "staple food", and judges that there is no allergy.
[0080] Next, regarding the serving unit of "(2) Side dish (crab ball)," the menu includes the ingredient "crab," while the student-specific allergy information 121 of the relevant student B registers "crab" as an ingredient that causes allergic symptoms. The eating schedule registration unit 113 calculates the logical product of the student-specific allergy information 121 and the menu allergen information 122 regarding the serving unit of "side dish," and determines that it is not edible because it causes an allergy.
[0081] Similarly, the eating schedule registration unit 113 calculates the logical product of the student-specific allergy information 121 and the menu allergen information 122 for each serving unit of "(3) Supplementary meal (pudding)" and "(4) Beverage (milk)" and determines that there is no allergy. As a result, the eating schedule registration unit 113 determines that only the "side dish" is not edible and that the other serving units are edible for the school lunch on that day.
[0082] Returning to Fig. 9 for explanation, next, the eating schedule registration unit 113 of the eating management device 10 inquires about the eating schedule for the relevant period if the user has an allergy (step S33). Specifically, if the eating schedule registration unit 113 judges, as a result of the judgment process in step S32, that there is a serving unit that may cause an allergic reaction in the menu allergen information 122 to be processed, it transmits the menu allergen information 122 for the relevant period to the parent / guardian terminal device 20 and inquires about the eating schedule.
[0083] If the eating schedule registration unit 113 determines that the menu allergen information 122 being processed does not contain a serving unit that would cause an allergic reaction, the eating schedule registration unit 113 ends the processing of this sequence diagram. In addition, the eating schedule registration unit 113 may transmit information indicating that there is no serving unit that would cause an allergic reaction to the parent terminal device 20. In this case, the eating schedule registration request unit 212 of the parent terminal device 20 displays information indicating that there is no serving unit that would cause an allergic reaction, and ends the processing of this sequence diagram.
[0084] Alternatively, the eating schedule registration unit 113 may transmit the menu allergen information 122 for the relevant period to the parent / guardian terminal device 20. In this case, the eating schedule registration request unit 212 of the parent / guardian terminal device 20 displays the school lunch menu for the relevant period and ends the processing of this sequence diagram. A list of school lunches to be provided to student B during the relevant period is displayed on the parent / guardian terminal device 20, and parent / guardian A can visually confirm the list of school lunches. However, unlike the eating registration screen 262 described below, the displayed screen is not a screen that accepts input operations related to allergies.
[0085] Next, the eating schedule registration request unit 212 of the parent terminal device 20 displays the eating schedule registration screen 262 for the relevant period, and accepts an input operation of the eating schedule (step S34).
[0086] 15 is a diagram showing an example of the eating registration screen 262. The eating schedule screen includes dates included in a predetermined period, menus for each serving unit provided on the dates, and an area for receiving a selection of whether or not eating is possible for each serving unit. The eating schedule registration request unit 212 refers to the eating schedule received from the eating management device 10, and displays "allowed to eat" for serving units that are allowed to be eaten, and displays "not allowed to eat" for serving units that are not allowed to be eaten.
[0087] The display of "eating permitted" and "eating prohibited" can be changed by an input operation by guardian A. That is, the eating schedule registration request unit 212 can change a serving unit determined as "eating prohibited" by the eating management device 10 to "eating permitted" in response to an input operation. Similarly, the eating schedule registration request unit 212 can change a serving unit determined as "eating permitted" to "eating prohibited" in response to an input operation.
[0088] In addition, the eating schedule registration request unit 212 displays ingredients that cause allergic reactions and are included in the menu for the serving unit that is "not edible." In other words, parent A who refers to the eating registration screen 262 can know why the menu is determined to be "not edible."
[0089] According to this screen, guardian A can select whether to permit or prohibit eating on the eating registration screen 262. For example, even if a menu item is related to a serving unit that contains ingredients that cause an allergic reaction, if the reaction is mild and the doctor has instructed the patient to gradually lift the restrictions, the guardian can easily select whether to permit or prohibit eating for each serving unit, which is highly convenient. In addition, even if a menu item is determined to be permitted for a serving unit, it can be easily changed to prohibited if the patient wishes to avoid eating the menu item due to factors other than allergies.
[0090] Returning to Fig. 9 for the explanation, next, the eating schedule registration request unit 212 of the parent / guardian terminal device 20 accepts the selection of the registration button, and transmits the input contents to the eating management device 10 (step S35). Specifically, the eating schedule registration request unit 212 generates information indicating an eating schedule registration request in which information indicating whether or not eating is possible for each serving unit is associated with the menu for the predetermined period to be processed, and transmits the information to the eating management device 10.
[0091] Next, the eating schedule registration unit 113 of the eating management device 10 generates eating schedule information 123 (step S36). The eating schedule registration unit 113 uses the information included in the eating schedule registration request to generate the eating schedule information 123 for the specified period of the corresponding student B. After that, the parent terminal device 20 and the eating management device 10 end the processing of this sequence diagram.
[0092] In addition, the eating plan registration unit 113 of the eating management device 10 may send information to the parent terminal device 20 prompting the parent terminal device 20 to register an eating plan, for example, if a request to register an eating plan is not received even after a predetermined period of time has passed since sending an e-mail to the parent terminal device 20, or if a request to register an eating plan is not received even after a predetermined period of time has passed since sending an inquiry about an eating plan.
[0093] 10 is a flowchart showing an example of the eating list display process. The process of this flowchart is executed in the teacher terminal device 40.
[0094] First, the list display control unit 411 accepts an input operation of an instruction to display an eating list screen specifying a grade and class (step S41). The list display control unit 411 accepts an input operation of specifying a grade and class for which the eating list screen is to be displayed on a classroom specification screen (not shown). The list display control unit 411 generates information indicating an eating schedule request including the input grade and class, and transmits it to the eating management device 10.
[0095] The display request receiving unit 115 of the eating management device 10 refers to the eating schedule information 123 using the information included in the eating schedule request, and extracts the records for the day the eating schedule request was received and for student B who is enrolled in the corresponding classroom. The display request receiving unit 115 does not need to extract the records for student B who does not have a serving unit that does not allow eating on that day. The display request receiving unit 115 generates eating schedule information for that day using the extracted records, and transmits it to the teacher terminal device 40.
[0096] Next, the list display control unit 411 receives the eating schedule information 123 for the day from the eating management device 10 (step S42). Note that, as an example, the eating schedule information received by the list display control unit 411 is associated with one or more students B who have a serving unit that cannot be eaten in the school lunch for the day, and information indicating the serving unit that cannot be eaten by the student B.
[0097] Next, the list display control unit 411 displays the eating list screen 461 showing a list of students B who have serving units that cannot be eaten on the day on the teacher terminal device 40 and the classroom monitor 460 (step S43).
[0098] FIG. 17 is a diagram showing an example of the eating list screen 461. The eating list screen 461 is a screen that displays the name of student B in association with information indicating whether or not the serving unit is edible. For example, the eating list screen 461 displays the serving units that student B is allowed to eat or not allowed to eat, using different codes for each serving unit. In the eating list screen 461 shown in FIG. 17, the serving units that are allowed to eat are displayed in different colors for each serving unit. This allows even student B, who cannot read, to recognize which serving units are allowed or not allowed to eat.
[0099] The eating list screen 461 is also displayed on a monitor (not shown) of the teacher terminal device 40. In addition, an upper limit may be set for the number of students B displayed on the eating list screen 461. When the number of students B who have serving units that cannot be eaten on the day exceeds the upper limit, the students B displayed on the eating list screen 461 may be periodically switched in order to display all of the students B.
[0100] Returning to Fig. 10 for explanation, the list display control unit 411 then judges whether or not it has acquired information indicating the completion of serving food to student B from the eating management device 10 (step S44). The list display control unit 411 judges whether or not it has received information indicating the completion of serving food and specifying student B from the eating management device 10. If the list display control unit 411 judges that it has not received information indicating the completion of serving food to student B (if "NO" in step S44), it repeats the process of step S44.
[0101] When the list display control unit 411 determines that it has received information indicating that the student B has finished serving the food (if "YES" in step S44), it makes the display of the student B different from the other displays (step S45). Specifically, the list display control unit 411 makes the display of the student B included in the eating list screen 461, which it has determined in step S44 has been received, different from the display of the other students B, and displays it on the classroom monitor 460 and the monitor of the teacher terminal device 40. For example, the list display control unit 411 shades the part of the name of the student B who has finished serving the food. The list display control unit 411 may delete the information indicating the student B who has finished serving the food from the eating list screen 461.
[0102] Next, the list display control unit 411 judges whether or not information indicating that serving of meals to all the class members has been completed has been acquired (step S46). If the list display control unit 411 judges that information indicating that serving of meals to all the class members has been completed has not been acquired from the eating management device 10 (if "NO" in step S46), the process proceeds to step S44.
[0103] When the list display control unit 411 determines that information indicating that the serving of meals to all the students in the class has been completed has been acquired (YES in step S46), it ends the display of the eating list screen 461 on the classroom monitor 460 and the monitor of the teacher terminal device 40 (step S47). After that, the processing unit 410 ends the processing of this flowchart.
[0104] 11 is a flowchart showing an example of a food service check process. The process of this flowchart is executed in the food service check terminal device 50. Before the start of this process, a screen for receiving an input operation to start the check is displayed on the food service counter monitor 560.
[0105] First, the meal arrangement display control unit 515 accepts an input operation to start checking (step S51).
[0106] Fig. 18 is a diagram showing an example of the screen transition of the student-specific food serving schedule screen 561. As shown in the top part of Fig. 18, first, a "Start check" button that accepts an input operation to start a check is displayed on the student-specific food serving schedule screen 561. When the "Start check" button is selected, the display transitions to the standby screen in the middle part of Fig. 18.
[0107] Returning to Fig. 11 for explanation, next, the student information acquiring unit 511 acquires the student ID using the student information reading device 570 (step S52). Specifically, the student information acquiring unit 511 acquires the student ID read by the student information reading device 570 from the IC card X of the student B presented to the student information reading device 570.
[0108] Next, the eating schedule acquisition unit 513 requests the eating schedule of Student B for that day from the eating management device 10 (step S53). Specifically, the eating schedule acquisition unit 513 generates eating schedule request information including the student ID acquired in step S52, and transmits it to the eating management device 10. When the display request acceptance unit 115 of the eating management device 10 receives the eating schedule request information, it refers to the eating schedule information 123 and extracts a record that includes the student ID included in the eating schedule request information and that includes the date on which the eating schedule request information was received. The display request acceptance unit 115 transmits the eating schedule information 123 including the extracted record to the meal distribution check terminal device 50.
[0109] In addition, if the student in question does not have any non-edible serving units on that day, the display request receiving unit 115 of the eating management device 10 sends information to the food distribution check terminal device 50 indicating that there are no non-edible serving units.
[0110] Next, the food serving display control unit 515 displays the eating schedule of student B for that day (step S54). Specifically, the food serving display control unit 515 uses the eating schedule information 123 received as a result of the request in step S53 to display information indicating whether or not student B, whose student ID was acquired in step S52, can eat for each serving unit on the food serving schedule screen for each student 561. If the student does not have a serving unit that does not allow eating, the food serving display control unit 515 causes the food serving counter monitor 560 to display information indicating that there is no serving unit that does not allow eating.
[0111] The bottom part of Fig. 18 shows an example of the student-specific serving schedule screen 561 displayed in this step. For example, as shown in this figure, the student-specific serving schedule screen 561 displays a code of a different color for each serving unit that can be eaten. Note that the student-specific serving schedule screen 561 may also display a code for a serving unit that cannot be eaten.
[0112] Returning to Fig. 11 for explanation, next, the tableware information acquisition unit 512 judges whether tableware information has been acquired (step S55). When the tableware is distributed to student B, the tableware information acquisition unit 512 acquires the tableware information contained in the IC chip Y read by the tableware information reading device 580, and acquires the type of tableware. If the tableware information acquisition unit 512 judges that tableware information has not been acquired ("NO" in step S55), it repeats this process until tableware information is acquired.
[0113] When the tableware information acquisition unit 512 determines that tableware information has been acquired (step S55: YES), the serving error determination unit checks the eating schedule for the day against the tableware (step S56). Specifically, the serving error determination unit checks the eating schedule information acquired in step S54 against the type of tableware detected in step S55.
[0114] Next, the food service error determination unit determines whether there is an excess or shortage in the serving unit of the school lunch that Student B plans to eat (step S57). Specifically, the food service error determination unit determines that there is an insufficiency when the serving unit is edible in the eating plan information acquired in step S54 but the corresponding tableware is not read in step S55. The food service error determination unit also determines that there is an excess when the serving unit is ineligible in the eating plan but the corresponding tableware is read.
[0115] If the food distribution error determination unit determines that there is an excess or shortage (YES in step S57), it outputs an error (step S58).
[0116] Fig. 19 is a diagram (part 1) showing an example of an error output. Fig. 19 shows an example of an error output when there is an excess in serving food. When the food serving error detection unit 514 determines that there is an excess in serving food, the food serving display control unit 515 displays a food serving error display area 562 on the food serving schedule screen 561 for each student, and displays information specifying the excess serving unit in the food serving error display area 562.
[0117] Fig. 20 is a diagram (part 2) showing an example of an error output. Fig. 20 shows an example of an error output when there is a shortage in serving food. When the food serving error detection unit 514 determines that there is a shortage in serving food, the food serving display control unit 515 displays a food serving error display area 562 on the food serving schedule screen 561 for each student, and displays information specifying the shortage in the food serving unit in the food serving error display area 562.
[0118] Returning to Fig. 11 for explanation, after outputting the error, the serving error detection unit 514 shifts the process to step S55. That is, the processes from step S55 to step S58 are repeated until tableware of the type corresponding to the serving unit to be consumed is detected.
[0119] When the food service error detection unit 514 determines that there is no shortage or excess ("NO" in step S57), it transmits a notification of completion of food service to the food consumption management device 10 (step S59). Specifically, the food service error detection unit 514 transmits the student ID acquired in step S52 and information indicating that food service to student B has been completed to the food consumption management device 10. Thereafter, the food service error detection unit 514 shifts the process to step S52. That is, in step S52, the student information acquisition unit 511 acquires the student ID of another student B.
[0120] The information transmitted to the eating management device 10 in this step is referred to when the eating management device 10 determines in step S44 of FIG. 10 whether or not it has acquired information indicating that meal distribution has been completed.
[0121] 11, after the serving of food to student B is completed, the IC card X of another student B is read. However, the process from reading the IC card X of student B to serving food to that student B may be performed in parallel with the process from reading the IC card X of another student B to serving food. In that case, for example, the food serving error detection unit 514 executes the process from step S53 to step S59 in the order in which the student IDs are acquired.
[0122] The eating schedule acquisition unit 513 may store the eating schedule information related to the multiple student IDs acquired by the student information acquisition unit 511 in a storage unit (not shown) of the food service check terminal device 50. In this case, the food service error detection unit 514 may accept the selection of the student B to be checked when the IC chip Y attached to the tableware is detected in step S55. The food service error detection unit 514 may read the eating schedule information 123 of the selected student B from the storage unit and check it against the type of tableware. In addition, the food service management system 1 may be provided with multiple food service counter monitors 560, and a screen indicating whether or not the student can eat before the food is served and a screen indicating an error related to the tableware after the tableware is distributed may be displayed on different food service counter monitors 560.
[0123] 12 is a flowchart showing an example of the meal distribution management process. This process is executed by the meal management device 10 for each classroom, that is, for each combination of grade and class.
[0124] First, the display request receiving unit 115 acquires a request for an eating schedule that specifies a student ID (step S61). The information acquired by the meal distribution management unit 114 in this step is the information transmitted from the meal distribution check terminal device 50 in step S53 in FIG.
[0125] Next, the display request receiving unit 115 transmits the eating schedule to the meal distribution check terminal device 50 (step S62). Specifically, the display request receiving unit 115 extracts, from the records of the eating schedule information 123, records that include the student ID specified by the information acquired in step S61 and have the date on which the request for the eating schedule was acquired as the serving date, and transmits the extracted records to the meal distribution check terminal device 50.
[0126] Next, the food service management unit 114 acquires information indicating that food service has been completed (step S63). Specifically, the food service management unit 114 acquires the student ID and information indicating that food service has been completed from the food service check terminal device 50. The information acquired by the food service management unit 114 in this step is the information transmitted from the food service check device in step S59 in FIG. 11.
[0127] Next, the meal distribution management unit 114 transmits information indicating the completion of meal distribution and the student ID to the teacher terminal device 40 (step S64). Note that the information transmitted in this process is received by the teacher terminal device 40 in step S44 of FIG.
[0128] Next, the food service management unit 114 judges whether there is a student B for whom food service has not been completed (step S65). Specifically, the food service management unit 114 judges that there is a student B for whom food service has not been completed if the unit 114 has not acquired information indicating completion of food service in step S63 for any of the students B included in the records of the meal schedule information 123 that belong to the classroom being processed and are included in the records for the serving date.
[0129] When the food service management unit 114 determines that there is a student B for whom food service has not been completed (YES in step S65), the process proceeds to step S61. That is, the process from step S61 to step S65 is repeated until food service is completed for all students B who have a non-eating serving unit on the serving date among the records included in the eating schedule information 123.
[0130] When the food distribution management unit 114 determines that there is no student B for whom food distribution has not been completed (NO in step S65), that is, when food distribution has been completed for all students B who have non-edible serving units, it transmits a notification of completion of food distribution to all students to the teacher terminal device 40 (step S66). Specifically, the food distribution management unit 114 transmits information indicating that food distribution to all students has been completed to the teacher terminal device 40 of the teacher in charge of the class being processed. The information transmitted in this step is received by the teacher terminal device 40 in step S46 in FIG. 10. After that, the food distribution management unit 114 ends the processing of this flowchart.
[0131] As described above, in this embodiment, a list of student Bs with serving units that cannot be eaten is displayed in the classroom, so each student B in the classroom can refer to the classroom monitor 460 to know which student B has serving units that cannot be eaten among the provided school lunches and which serving units the student B cannot eat. This provides an opportunity for the student B to notice even if a school lunch with a serving unit that cannot be eaten is served to student B. In addition, other students B around the student B can notice that the nearby student B is about to eat a school lunch that cannot be eaten. Therefore, it is possible to prevent student B from eating a school lunch with a serving unit that cannot be eaten.
[0132] In addition, the same list screen is also displayed on the teacher's terminal device 40 of the homeroom teacher, so that the teacher can carry around the teacher's terminal device 40 and refer to it to check at hand which Student B has a provision unit that cannot be consumed, thereby improving convenience.
[0133] In this embodiment, the classroom monitor 460 and the teacher terminal device 40 display the student B for whom the meal has been served differently from the student B for whom the meal has not been served. As a result, when the meal is served to the student B who has a serving unit that cannot be consumed on the day and has not presented the IC card X, the student B is displayed on the eating list screen 461 as the student B for whom the meal has not been served. Therefore, even though the student B is displayed as the student B for whom the meal has not been served, the student B or the student B around him who notices that the meal has been served on the desk can notice the non-presentation of the IC card X, and the mistaken serving of the non-edible meal can be prevented.
[0134] In addition, by displaying the availability of food for Student B who reads IC card X near the serving counter for each serving unit, not only can Student B himself recognize the serving unit that he cannot eat, but Student B, who is in charge of serving the food, can also recognize the serving unit that he cannot eat, preventing the serving of school lunches that he cannot eat. When displaying the availability of food for each serving unit with a different code, even Student B who cannot read can recognize the availability of food.
[0135] Furthermore, if the color of the code indicating whether or not food can be eaten corresponds to the color of the tableware on the serving counter monitor 560, even if there is a surplus or shortage in the serving units being served, the surplus or shortage can be easily recognized, thereby improving convenience.
[0136] The above describes an example of managing school lunch meals using the meal management system 1. However, the meal management system 1 can also manage meals other than school lunches. For example, meal management can be performed efficiently even when providing hospital meals to patients in a hospital or when providing meals to residents in a welfare facility.
[0137] Although the embodiments and modifications according to the present invention have been described above, the present invention is not limited to the above-mentioned embodiment, and various modifications are included. For example, the above-mentioned embodiment has been described in detail to make the present invention easier to understand, and the present invention is not limited to having all the configurations described here. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment. It is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace other configurations with respect to a part of the configuration of each embodiment. In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in hardware by designing them as integrated circuits, for example, in part or in whole. In addition, the control lines and information lines in the figures are those that are considered necessary for explanation, and not all of them are necessarily shown. It may be considered that almost all of the configurations are connected to each other.
[0138] Furthermore, the functional configurations of the above-mentioned meal management device 10, school lunch center terminal device 30, teacher terminal device 40, and meal distribution check terminal device 50 are classified according to the main processing contents for ease of understanding. The classification method and names of the components do not limit the present invention. As described above, the configurations of the above-mentioned meal management device 10, school lunch center terminal device 30, teacher terminal device 40, and meal distribution check terminal device 50 can be further classified into more components according to the processing contents. Also, one component can be classified to perform even more processes.
[0139] For example, the eating schedule information 123 may be stored in the teacher terminal device 40 or the meal distribution check terminal device 50. In this case, when the teacher terminal device 40 performs the eating list display process, it can display the eating list screen 461 by referring to a storage unit (not shown). Also, when the meal distribution check terminal device 50 performs the meal distribution check process, it can identify the eating schedule of student B by referring to a storage unit (not shown) and perform an error determination. In addition, each processing unit of the eating management device 10 may be provided in the teacher terminal device 40, and the eating management device 10 and the teacher terminal device 40 may be configured as an integrated terminal device. Similarly, each processing unit of the eating management device 10 may be provided in the meal distribution check terminal device 50, and the eating management device 10 and the meal distribution check terminal device 50 may be configured as an integrated terminal device. Naturally, the teacher terminal device 40 and the meal distribution check terminal device 50 may be configured as an integrated terminal device. [Explanation of symbols]
[0140] 1: Eating management system, 10: Eating management device, 11: Calculation device, 12: Memory, 13: External storage device, 14: Input IF, 15: Output IF, 16: Communication IF, 20: Parent terminal device, 30: School lunch center terminal device, 40: Teacher terminal device, 50: Food distribution check terminal device, 110, 210, 310, 410, 510: Processing device, 111: Menu registration unit, 112: Allergy information registration unit, 113: Eating schedule registration unit, 114: Food distribution management unit, 115: Display request reception unit, 120: Memory unit, 121: Student-specific allergy information, 122: Menu allergen information, 123: Eating schedule information, 130, 230, 330, 430, 530: Input unit, 140, 240, 340, 440, 540: Output unit, 150·250·350·450·550: communication unit, 211: allergy registration request unit, 212: eating schedule registration request unit, 261: allergy information registration screen, 262: eating registration screen, 311: menu registration request unit, 361: menu registration screen, 411: list display control unit, 460: classroom monitor, 461: eating list screen, 511: student information acquisition unit, 512: tableware information acquisition unit, 513: eating schedule acquisition unit, 514: food delivery error detection unit, 515: food delivery display control unit, 560: food delivery table monitor, 561: food delivery schedule screen for each student, 562: food delivery error display area, 570: student information reading device, 580: tableware information reading device, A: guardian, B: student, N: network, X: IC card, Y: IC chip
Claims
1. A dietary management method using a parent terminal device owned by a parent, a dietary management device owned by a school, and a classroom monitor installed in a classroom, comprising: a meal schedule registration step in which, when an input of whether or not eating is possible for each of a plurality of serving units included in the school lunch provided to the student by the parent terminal device is received, eating schedule information is registered in the eating management device; a list display step of displaying information indicating whether each serving unit can be eaten or not in association with information indicating the students included in the classroom on the day the school lunch is provided based on the eating schedule information on the classroom monitor; A food intake management method comprising:
2. The food intake management method according to claim 1, a student information reading step for causing a student information reading device to read student information for identifying a student; a food serving display step of displaying on a food serving table monitor disposed near the food serving table whether or not the student whose information is read in the student information reading step can eat; A food intake management method comprising:
3. The food intake management method according to claim 2, The tableware distribution procedure by which tableware is distributed to students; a tableware type reading procedure for having a tableware information reading device read the type of tableware distributed to the students; a serving error display step of displaying information indicating a serving error on the serving counter monitor when a serving error occurs regarding the tableware read in the tableware type reading step for a student whose student information is read in the student information reading step; A food intake management method comprising:
4. The food intake management method according to claim 3, In the food distribution display step, the availability of food is displayed in different colors for each serving unit, The meal management method is characterized in that in the tableware distribution step, tableware of a color corresponding to the color displayed in the food distribution display step is distributed for each serving unit.
5. A meal plan registration unit that registers whether or not each of a plurality of serving units included in the school lunch provided to the student is edible in the meal plan information based on an input operation of a guardian; a list display control unit that uses the eating schedule information to associate information indicating the students in the classroom with information indicating whether each serving unit can be eaten on the day the school lunch is provided, and displays the information on a classroom monitor installed in the classroom; A food management system comprising:
6. The food management system according to claim 5, an allergy information registration unit that registers the student's allergy ingredients in student-specific allergy information based on the parent's input operation; A menu registration unit that registers the serving unit of the meal and the ingredients included in the serving unit; and a meal schedule registration request unit that displays, for each day that school lunches are provided, a number of serving units and whether or not the student has an allergy to the ingredients of the serving unit, and receives an input operation by the guardian of the student as to whether or not the student can eat the food for each serving unit. The eating schedule registration unit registers information input by the eating schedule registration request unit into the eating schedule information.
7. The food management system according to claim 5 or 6, a student information acquisition unit that acquires student information for identifying a student; This eating management system is characterized by comprising a food serving display control unit that displays information indicating whether or not the student whose student information has been acquired by the student information acquisition unit is able to eat on a food serving table monitor installed on the food serving table.
8. The food management system according to claim 7, a tableware information acquiring unit that acquires tableware information indicating the type of tableware from a recording medium included in each of the tableware distributed to the students; This eating management system is characterized by comprising a serving error detection unit that determines whether the serving unit that a student whose student information has been acquired by the student information acquisition unit plans to eat is insufficient or excessive, based on the type of tableware acquired by the tableware information acquisition unit and the eating plan information.
9. The food management system according to claim 8, This is a meal management system characterized in that the food serving display control unit displays information identifying the serving unit that is insufficient or surplus on the food serving counter monitor when the food serving error detection unit determines that there is an surplus or deficiency in the food serving.
10. The food management system according to claim 8, This is a food management system characterized in that the list display control unit displays students for whom the food service error detection unit has determined that the food service is neither too much nor too little on the classroom monitor, distinguishing them from other students.
11. The food management system according to claim 9, The eating schedule registration unit registers whether or not each of the serving units indicating a distinction between a staple food, a side dish, a supplementary food, or a beverage can be eaten in the eating schedule information, This is an eating management system characterized in that the food serving display control unit displays the serving units that students can eat or the serving units that students cannot eat on the food serving counter monitor using different codes for each serving unit.
12. an allergy information registration unit that registers the allergy ingredients of the students in the student-specific allergy information based on an input operation to the parent / guardian terminal device; A menu registration unit that registers the serving unit of the meal and the ingredients included in the serving unit; an eating schedule registration unit that inquires about eating schedules from the parent / guardian terminal device owned by the parent / guardian of the student whose school lunch serving unit contains the allergy-causing ingredient, obtains information indicating whether or not the student can eat the food for each serving unit, and registers the information as eating schedule information; A dining management device comprising: a display request receiving unit that transmits the dining schedule information of students included in a classroom in response to a request from a teacher terminal device that specifies the classroom.
13. a student information acquisition unit that reads student information for identifying a student; a tableware information acquiring unit that acquires tableware information indicating the type of tableware from a recording medium included in each of the tableware distributed to the students; An eating schedule acquisition unit that acquires eating schedule information of the student for a predetermined period of time; A food serving check terminal device characterized by comprising a food serving error detection unit that determines whether the serving unit that a student whose student information has been acquired by the student information acquisition unit plans to eat is insufficient or excessive, based on the type of food serving acquired by the food serving information acquisition unit and the eating plan information.
14. A program for causing an eating management device to execute an eating management method, an allergy information registration step for registering the student's allergy ingredients in the student-specific allergy information based on an input operation into the parent / guardian terminal device; A menu registration procedure for registering a serving unit of a meal and ingredients included in the serving unit; an eating schedule registration procedure for inquiring about eating schedules from the parent / guardian terminal device owned by the parent / guardian of a student for whom the allergy-causing ingredient is present in the unit of school lunch provided during a specified period, obtaining information indicating whether or not eating is possible for each unit of school lunch provided, and registering the information as eating schedule information; a display request receiving procedure for transmitting the eating schedule information of students included in a classroom in response to a request from a teacher terminal device that specifies the classroom, the program executing the program.
15. A program for causing a meal distribution check terminal device to execute a meal distribution check method, a student information acquisition step of reading student information identifying the student from a recording medium possessed by the student; a tableware information acquisition step of acquiring tableware information indicating the type of tableware from a recording medium included in each of the tableware or containers distributed to the students; A meal schedule acquisition step for acquiring meal schedule information of the student for a predetermined period of time; A program characterized by executing a serving error detection procedure that determines whether the serving unit that a student whose student information was acquired in the student information acquisition procedure plans to eat is over or underserved based on the type of tableware acquired in the tableware information acquisition procedure and the eating plan information.
Citation Information
Patent Citations
Cooking / table setting confirmation program
JP2004287690A
System for managing service of food and drink
JP2011076270A
Order system, its server and order management method
JP2012133457A
Server device, food information reference system, food information reference method, and program
JP2016110568A
Food allergy management and check method for student in food allergy accident suppression system for school lunch
JP2016126542A
