Food ordering device and food ordering system

The school lunch ordering device encodes meal information using BASE58 and generates barcodes to enhance security and accuracy, addressing network vulnerabilities and reducing errors in the ordering process.

WO2024236647A1PCT designated stage expired Publication Date: 2024-11-21RIVERFIELD INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2023/017942
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Conventional school lunch ordering systems connected via networks are vulnerable to security threats and prone to erroneous orders due to potential network attacks and data transmission issues.

Method used

A school lunch ordering device that encodes meal information using the BASE58 method and generates barcodes, which are printed on order forms, allowing secure local network operation and reducing errors by increasing barcode size and accuracy.

Benefits of technology

The solution effectively reduces erroneous orders while maintaining network safety by encoding and compressing meal information into barcodes, ensuring secure transmission and accurate reading, even when the order form is tilted.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2023017942_21112024_PF_FP_ABST
    Figure JP2023017942_21112024_PF_FP_ABST
Patent Text Reader

Abstract

This food ordering device comprises: an encoding unit that encodes meal information of a user and generates encoded meal information; a barcode generation unit that generates a barcode that indicates the encoded meal information that is generated by the encoding unit; and a barcode output unit that outputs the barcode that is generated by the barcode generation unit.
Need to check novelty before this filing date? Find Prior Art

Description

Meal ordering device, meal ordering system

[0001] The present invention relates to a technique for ordering meals for users such as patients from a meal ordering facility such as a hospital.

[0002] Conventionally, an information processing device installed at a school lunch ordering facility that orders school lunches and an information processing device installed at a school lunch supply facility that receives and prepares school lunches are connected via a network, and a system has been proposed in which school lunches are ordered from the school lunch supply facility via a network.

[0003] Japanese Patent Application Laid-Open No. 2019-113973

[0004] In the above-mentioned system, the information processing device installed at the meal ordering facility and the information processing device installed at the meal supply facility are connected via a network, so there is a possibility of being subjected to network attacks from outside, and it is difficult to say that it is in a secure state. The present invention has been made in consideration of the above circumstances, and its object is to reduce erroneous meal ordering while maintaining the security of the network.

[0005] The meal ordering device of the present invention comprises an encoding unit that encodes a user's meal information to generate encoded meal information, a barcode generation unit that generates a barcode indicating the encoded meal information generated by the encoding unit, and a barcode output unit that outputs the barcode generated by the barcode generation unit.

[0006] This allows the meal ordering device to encode and compress the meal information included in the barcode, making it possible to enlarge the barcode itself. Also, because the meal ordering device transmits the meal information to the meal service company via the barcode, it is possible to keep the local network of the facility where the meal ordering device is installed secure.

[0007] According to the present invention, erroneous ordering of school lunches is reduced while maintaining the security of the network.

[0008] FIG. 1 is a diagram illustrating a school lunch ordering system. FIG. 2 is a block diagram illustrating an example of the configuration of a school lunch ordering device. FIG. 3 is a block diagram illustrating an example of the configuration of a school lunch management device. FIG. 4 is a diagram illustrating meal information and a method for encoding the meal information. FIG. 5 is a diagram illustrating meal information and a method for encoding the meal information. FIG. 6 is a diagram showing an example of an order form.

[0009] The following describes embodiments. Note that each configuration described below is merely an example for realizing the present invention. Therefore, various modifications can be made depending on the design, etc., as long as they do not deviate from the technical concept of the present invention. Furthermore, to avoid duplication, the same reference numerals may be used to designate configurations that have already been described, and repeated description may be omitted.

[0010] <1. Overview of the school meal ordering system> Figure 1 is a diagram explaining the school meal ordering system 1. As shown in Figure 1, the school meal ordering system 1 is a system for ordering school meals from a school meal ordering facility 2, such as a hospital, which is the source of the school meal order, to a school meal supply facility 3 that prepares the school meals.

[0011] In this embodiment, the meal ordering facility 2 is a hospital. The meal ordering facility 2 is provided with an electronic medical record server 11, an electronic medical record terminal device 12, a meal ordering device 13, a printer 14, and a FAX transmission device 15.

[0012] The electronic medical record server 11 stores electronic medical records of patients who are hospitalized or visiting the meal ordering facility 2. The electronic medical records store information about the patient, such as the patient's name, age, sex, and address, information about the patient's illness, such as the patient's medical history and surgical history, and information about meals (meals) for hospitalized patients.

[0013] One or more electronic medical record terminal devices 12 can be connected to the electronic medical record server 11 via a local network. The electronic medical record terminal device 12 is a computer including a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), etc. The electronic medical record terminal device 12 is used by staff 16 at the meal ordering facility 2. The staff 16 at the meal ordering facility 2 are expected to be doctors, nurses, etc.

[0014] The electronic medical record terminal device 12 reads out the electronic medical records recorded in the electronic medical record server 11 in response to operations by the staff member 16 and displays them on the display unit, or updates the electronic medical records recorded in the electronic medical record server 11 in response to operations by the staff member 16.

[0015] The meal ordering device 13 is offline and not connected online (via a local network) to the electronic medical record server 11 and the electronic medical record terminal device 12. In other words, the meal ordering device 13 is a so-called stand-alone device.

[0016] The meal ordering device 13 is a computer equipped with a CPU, RAM, ROM, etc. The meal ordering device 13 is a device that generates an order form 17 for ordering meals for patients from the meal supply facility 3. A printer 14 is connected to the meal ordering device 13, and the printer 14 prints the order form 17 on paper under the control of the meal ordering device 13. One or more barcodes are printed on the order form 17 (see Figure 6). Details of the meal ordering device 13 will be described later.

[0017] The fax transmitting device 15 reads the purchase order 17 to generate fax data (still image data), and transmits the generated fax data to the food supply facility 3 by fax.

[0018] The school lunch supply facility 3 is equipped with a fax receiving device 21, a barcode reader 22, a school lunch management device 23, and a school lunch management server 24.

[0019] The fax receiving device 21 receives fax data transmitted from the food ordering facility 2 (fax transmitting device 15) and prints an order form 25 on a paper medium based on the received fax data.

[0020] The food service management device 23 is a computer equipped with a CPU, RAM, ROM, etc., and is connected to a barcode reader 22. The food service management device 23 obtains the food service information indicated by the barcode by reading the barcode printed on the order form 25 with the barcode reader 22. The food service management device 23 is connected to a food service management server 24 via a local network.

[0021] The school lunch management server 24 is a computer equipped with a CPU, RAM, ROM, etc. The school lunch management server 24 stores school lunch information acquired by the school lunch management device 23.

[0022] At the school lunch supply facility 3, meals are prepared based on the meal information stored in the school lunch management server 24. Then, the school lunch supply facility 3 provides the prepared meals to the school lunch ordering facility 2.

[0023] 2. Configuration of meal ordering device 13 Figure 2 is a block diagram showing an example of the configuration of meal ordering device 13. As shown in Figure 2, meal ordering device 13 comprises a CPU 31, ROM 32, RAM 33, a storage unit 34, a display unit 35, an operation unit 36, and an interface unit 37. The various units of meal ordering device 13 are connected to one another via a bus 38.

[0024] The CPU 31 executes various processes in accordance with programs stored in the ROM 32 or the storage unit 34. The RAM 33 stores data and the like necessary for the CPU 31 to execute various processes.

[0025] In this embodiment, the CPU 31 functions as an encoding unit 41, a barcode generation unit 42, and a barcode output unit 43. The encoding unit 41 encodes the meal information input by the staff member 16 to obtain encoded meal information. The barcode generation unit 42 generates a barcode based on the encoded meal information obtained by the encoding unit 41. The barcode output unit 43 causes the printer 14 to print an order form 17 indicating the barcode generated by the barcode generation unit 42. The processes performed by the encoding unit 41, the barcode generation unit 42, and the barcode output unit 43 will be described in detail below.

[0026] The storage unit 34 is configured with a storage medium such as a hard disk drive (HDD) or a solid state drive (SSD). For example, various types of information can be stored in the storage unit 34. The storage unit 34 can also be used to store program data for the CPU 31 to execute various processes.

[0027] The display unit 35 is made up of a liquid crystal display, an organic EL display, or the like, and displays various images under the control of the CPU 31. For example, the display unit 35 displays meal information input by the staff member 16.

[0028] The operation unit 36 ​​includes a keyboard, a mouse, a touch panel, etc., and accepts input operations by the staff member 16 .

[0029] The interface unit 37 is an input / output port for connecting external devices including the printer 14 .

[0030] 3. Configuration of school lunch management device 23> Fig. 3 is a block diagram showing an example of the configuration of school lunch management device 23. As shown in Fig. 3, school lunch management device 23 includes a CPU 51, a ROM 52, a RAM 53, a storage unit 54, a display unit 55, an operation unit 56, a communication unit 57, and an interface unit 58. The units of school lunch management device 23 are connected to each other via a bus 59.

[0031] The CPU 51 executes various processes in accordance with programs stored in the ROM 52 or the storage unit 54. The RAM 53 stores data and the like necessary for the CPU 51 to execute various processes.

[0032] In this embodiment, the CPU 51 functions as an acquisition unit 61 and a decoding unit 62. The acquisition unit 61 acquires coded meal information obtained by reading the barcode written on the order form 25 with the barcode reader 22. The decoding unit 62 obtains meal information by decoding the coded meal information acquired by the acquisition unit 61. The processes performed by the acquisition unit 61 and the decoding unit 62 will be described in detail below.

[0033] The storage unit 54 is configured with a storage medium such as an HDD or SSD. The storage unit 54 can store, for example, various types of information. The storage unit 54 can also be used to store program data for the CPU 51 to execute various processes.

[0034] The display unit 55 is made up of a liquid crystal display, an organic EL display, or the like, and displays various images under the control of the CPU 51. For example, the display unit 55 displays the meal information decoded by the decoding unit 62.

[0035] The operation unit 56 comprises a keyboard, mouse, touch panel, etc., and accepts input operations by the staff 16 of the school lunch supply facility 3.

[0036] The communication unit 57 communicates with the school lunch management server 24 via wired or wireless communication.

[0037] The interface unit 58 is an input / output port for connecting external devices including the barcode reader 22 .

[0038] <4. School Lunch Ordering Process> Next, school lunch ordering process by the school lunch ordering device 13 and school lunch order receiving process by the school lunch management device 23 will be described.

[0039] 4 and 5 are diagrams for explaining the meal information and the encoding method of the meal information. As will be described in detail later, the meal information shown in each of FIGS. 4 and 5 is represented by a different barcode. Therefore, the facility ID and patient ID are shown in both.

[0040] In the meal ordering device 13, meal information for ordering meals from the meal supply facility 3 is input by staff 16. Meal information is input for each patient.

[0041] 4 and 5, the meal information includes a facility ID, a patient ID (identification information), the patient's last name, first name, sex, date of birth, type of meal, action, application date, and room. Note that the meal information is an example, and some of these may not be included, or other information may be included.

[0042] As shown in FIG. 4 , a facility ID is assigned as a unique value to each meal ordering facility 2. The facility ID is a three-digit value represented by BASE58. BASE58 is an encoding method that converts data into 58 types of alphanumeric characters. BASE58 uses the following alphanumeric characters: 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz. These alphanumeric characters exclude characters that are difficult to distinguish (e.g., the numeral 0 and the capital letter O, the capital letter I and the lowercase letter l). Using BASE58 can reduce misidentification when read by a person or using OCR.

[0043] A patient ID is assigned as a unique value to each patient. The patient ID is a three-digit value expressed in BASE58. Therefore, the facility ID and patient ID are assigned any of the numbers from 3364 (211 in BASE58) to 195111 (zzz in BASE58).

[0044] The patient's last name and first name can each be entered up to five characters long. However, the patient's last name and first name may be six characters or longer. The patient's gender can be entered as male or female. The patient's date of birth can be entered as two digits for the year and month and day, respectively.

[0045] As shown in Figure 5, the food type indicates the type of school lunch, and can be selected from multiple types set by the school lunch ordering facility 2 or the school lunch supply facility 3, such as regular meal 1, regular meal 2, 5-minute meal, liquid meal, diabetic meal, low-fat meal, etc. The food type includes various information related to the meal, such as the type of staple food, the amount of the staple food, and the type of side dish.

[0046] The action indicates the type of procedure related to the patient's meals, such as start, change, or end. The application date indicates the date of the change in meal type, i.e., the date from which the ordered meal will be applied, and in addition to the date, the meal timing can also be entered. The meal timing is time information expressed as non-numeric values, such as morning, lunch, or evening. The room indicates the floor and room number of the room where the patient is hospitalized.

[0047] When the staff member 16 inputs this meal information via the operation unit 36, the encoding unit 41 encodes the input meal information using the BASE58 encoding method to generate encoded meal information.

[0048] The encoding unit 41 encodes the facility ID using the BASE58 encoding method. As shown in FIG. 4, if the facility ID is, for example, 12345 (10), the encoding unit 41 encodes it into 4fr (58). Note that the number in parentheses following a number or alphanumeric character indicates the base number of that number or alphanumeric character. The same applies hereinafter.

[0049] The encoding unit 41 encodes the patient ID using the BASE58 encoding method. For example, if the patient ID is 7481(10), the encoding unit 41 encodes it as 2Cz(58). In this way, the facility ID and patient ID can be represented by three-digit alphanumeric characters in base 58, and therefore have a fixed length.

[0050] The encoding unit 41 encodes the UTF-8 character code value representing the patient's last name and first name using the BASE58 encoding method. For example, if the last name is Sugano, the encoding unit 41 encodes the UTF-8 character code value representing Sugano, E88F85 E9878E(16), into 2zotUWbtZ(58). Also, if the first name is Takahiro, the encoding unit 41 encodes the UTF-8 character code value representing Takahiro, E882B4 E79A93(16), into 2znScGamG(58).

[0051] The encoding unit 41 converts the patient's gender into either 1 (10) if male or 2 (10) if female, and encodes the converted value using the BASE58 encoding method. In this example, the encoding unit 41 encodes into 1 (58) if male or 2 (58) if female. Note that the gender is represented by a single digit and is therefore a fixed length.

[0052] For a patient's date of birth, the encoding unit 41 calculates the number of days elapsed from the specified reference date to the patient's date of birth by subtracting a specified reference date from the patient's date of birth. The encoding unit 41 then encodes the calculated number of days elapsed using the BASE58 encoding method. For example, assume that the reference date is January 1, 1900, and the patient's date of birth is February 1, 2023. In this case, the encoding unit 41 subtracts January 1, 1900 from February 1, 2023 to obtain the number of days elapsed, 44956 (10). The encoding unit 41 then encodes 44956 (10) into EN7 (58). Here, when encoding the number of days elapsed using the BASE58 encoding method, approximately 500 years can be represented by a three-digit base-58 number, so the date of birth can be treated as a fixed-length, three-digit number.

[0053] The encoding unit 41 converts the food type into a predetermined value for each input food type, and adds a predetermined fixed value to the converted value. For example, the predetermined value is 1 (10) for regular meal 1, 2 (10) for regular meal 2, 3 (58) for liquid meal, and 4 (10) for 5-minute meal. The fixed value is 3364 (10) so that the encoded alphanumeric characters will be three digits.

[0054] The encoding unit 41 encodes the value to which the fixed value has been added using the BASE58 encoding method. For example, if the food type is regular food 1 (10), the encoding unit 41 adds 3364 (10) to 1 (10) to obtain 3365 (10), which is converted to 212 (58). Here, since multiple food types may be provided, it is possible that the number of food types may exceed 58. If the number of food types exceeds 58, the number of digits cannot be contained in a single digit when encoding using the BASE58 encoding method, resulting in a variable length. Therefore, by adding 3364 (10) as a fixed value, the food type will always be represented as a three-digit alphanumeric character even if the number of food types increases. Therefore, the food type can be treated as a fixed length.

[0055] The encoding unit 41 converts the input action into a predetermined value for each type of action, and encodes the converted value using the BASE58 encoding method. For example, the encoding unit 41 converts a start to 1 (58), a change to 2 (58), and an end to 3 (58). Note that an action is represented by a single digit, so it has a fixed length.

[0056] For the applicable date, the encoding unit 41 subtracts a predetermined reference date from the date of change in eating habits to calculate the number of days elapsed from the predetermined reference date to the date of change in eating habits. Note that this reference date may be the same as or different from the reference date for the date of birth. The encoding unit 41 then triples the calculated number of days elapsed and adds a predetermined value to the meal timing (morning, lunch, evening). Here, 0 (10) is added for morning, 1 (10) for lunch, and 2 (10) for evening. In this way, the sum is divided by 3 to determine the number of days elapsed, and the remainder is assigned to the meal timing (morning, lunch, evening). This makes it possible to treat the information obtained by adding the date and meal timing (morning, lunch, evening) as a single value.

[0057] For example, suppose the reference date is January 1, 2000, the date of the change in dietary pattern is February 1, 2023, and the change begins with lunch. In this case, the encoding unit 41 subtracts January 1, 2000 from February 1, 2023 to obtain the number of elapsed days, 8432 (10). The encoding unit 41 then multiplies the number of elapsed days, 8432 (10), by 3 and adds 1 (10), which corresponds to lunch, to obtain 25297 (10). The encoding unit 41 then encodes 25297 (10) as 8XA (58). When encoding the value obtained by adding the meal timing (morning, noon, or evening) to the date of the change in dietary pattern using the BASE58 encoding method in this way, approximately 175 years can be represented by a three-digit base 58 number depending on the reference date setting, so the application date can be treated as a fixed length.

[0058] For a room, the encoding unit 41 encodes the floor using the BASE58 encoding method and also encodes the value obtained by adding a predetermined fixed value to the room number using the BASE58 encoding method. The fixed value is 3364 (10) so that the encoded value is three digits. For example, if the floor is the 15th floor and the room number is 1503, the encoding unit 41 converts 15 (10) to G (58). The encoding unit 41 also adds 3364 (10) to 1503 (10) to obtain 4867 (10). The encoding unit 41 then converts 4867 (10) to 2Sv (58). As a result, the encoding unit 41 obtains G2Sv (58) as the encoded value of the room. If the room number includes characters other than numbers, such as letters, a value consisting only of numbers can be associated with each room number. In this way, a room can be expressed as a base-58 number with a total of four digits, one digit indicating the floor and three digits indicating the room number, and therefore has a fixed length.

[0059] The barcode generating unit 42 generates a barcode indicating the coded meal information coded by the coding unit 41. In this embodiment, the code format used is GS1-128, which can include alphanumeric characters.

[0060] The barcode generator 42 generates a GS1-128 barcode showing the coded dietary information of the facility ID, patient ID, and patient's last name, first name, gender, and date of birth shown in Figure 4. At this time, the barcode generator 42 generates a barcode in which the coded dietary information of the facility ID, patient ID, and patient's last name, first name, gender, and date of birth are arranged in order. As described above, the coded dietary information of the facility ID, patient ID, and patient's gender and date of birth is of fixed length. On the other hand, the coded dietary information of the patient's last name and first name is of variable length, which varies depending on the number of characters. Therefore, for the coded dietary information of the patient's last name and first name, which are variable length, a GS1 standard delimiter code may be inserted between them.

[0061] Alternatively, the coded dietary information of the patient's first and last names, which are variable in length, may be generated as separate barcodes. In this case, the barcode generator 42 may generate a first barcode representing the coded dietary information of the facility ID, patient ID, and patient's last name, a second barcode representing the coded dietary information of the facility ID, patient ID, and patient's first name, and a third barcode representing the coded dietary information of the facility ID, patient ID, patient's sex, and date of birth.

[0062] The barcode generator 42 generates a GS1-128 barcode that indicates the coded meal information of the facility ID, patient ID, food type, action, application date, and room shown in Figure 5. At this time, the barcode generator 42 generates a barcode in which the coded meal information of the facility ID, patient ID, food type, action, application date, and room are arranged in order. Furthermore, since the facility ID, patient ID, food type, action, application date, and room can all be treated as fixed lengths, even if the barcode is generated by arranging them in order, there will be no misalignment of digits when it is read.

[0063] 6 shows an example of an order form. As shown in FIG. 6, the barcode output unit 43 causes the printer 14 to print the order form 17 on which the barcode generated by the barcode generation unit 42 is written.

[0064] As shown in Figure 6, multiple barcodes are printed on the purchase order form 17. The purchase order form 17 is read by the fax transmitter 15 and transmitted as fax data. When the staff member 16 places the purchase order form 17 in the fax transmitter 15, or when the fax transmitter 15 reads the purchase order form 17, the purchase order form 17 may be read at an angle. Furthermore, the barcodes may be distorted when the fax receiver 21 receives the data signal and prints it as the purchase order form 25.

[0065] Therefore, the inventor verified whether the barcode on the purchase order 25 can be read by the barcode reader 22 when the fax transmitter 15 reads the purchase order 17 without tilting it, and when the fax transmitter 15 reads the purchase order 17 with it tilted by 10 degrees.

[0066] This verification showed that if the length of the barcode per digit is 3.2 mm or more, the barcode reader 22 can accurately read the barcode even if the order form 17 is tilted by 10 degrees.

[0067] Therefore, the barcode output unit 43 may print the order form 17 so that the length of the barcode per digit is 3.2 mm or more. This allows the barcode reader 22 to accurately read the order form 17 even when it is read at an angle.

[0068] The fax receiving device 21 receives the fax data and prints out an order form 25 based on the fax data. The acquisition unit 61 reads the barcode written on the order form 25 via the barcode reader 22, thereby acquiring the coded meal information indicated on the barcode.

[0069] The decoding unit 62 obtains meal information by decoding the acquired coded meal information. Based on the patient ID included in the obtained meal information, the decoding unit 62 associates the meal information obtained from the multiple barcodes with each identical patient ID and stores it in the meal service management server 24.

[0070] 5. Modifications Although the present invention has been described above with reference to an embodiment, the present invention is not limited to the specific example described above and can employ various configurations. For example, in the embodiment described above, the encoding unit 41 encodes the meal information using the BASE58 encoding method. However, the encoding unit 41 may encode the meal information using another encoding method. However, because the number of characters that can be displayed in a barcode is limited, BASE58 is useful as an encoding method that can further compress the amount of information.

[0071] In the above embodiment, the barcode generating unit 42 generates barcodes using GS1-128, but the barcode generating unit 42 may generate barcodes using other methods.

[0072] Furthermore, in the above embodiment, the electronic medical record terminal device 12 and the meal ordering device 13 are provided as separate devices, but the electronic medical record terminal device 12 may also be provided as the meal ordering device 13. That is, the electronic medical record terminal device 12 may generate and print the order form 17. Even in this case, the electronic medical record server 11 and the electronic medical record terminal device 12 do not need to be connected to other networks, so the local network within the meal ordering facility 2 can be kept secure.

[0073] In the above embodiment, the fax receiving device 21 prints the order form 25 based on the fax data, and the barcode reader 22 reads the barcode written on the order form 25. However, the fax receiving device 21 may generate digital image data (still image data) based on the fax data, and the acquisition unit 61 of the meal management device 23 may acquire the coded meal information by performing image analysis on the image data.

[0074] In the above-described embodiment, the acquisition unit 61 acquires the coded meal information by reading the barcode via the barcode reader 22. However, the acquisition unit 61 may read the barcode with the barcode reader 22 and also read the alphanumeric characters written below the barcode on the order form 25 using an OCR or the like, thereby improving the accuracy of reading the coded meal information.

[0075] In the above embodiment, the meal information includes the type of food. However, instead of or in addition to the type of food, the type of staple food, the amount of the staple food, and the type of side dish may be included.

[0076] 6. Summary The meal ordering device 13 described above includes an encoding unit 41 that encodes a user's meal information to generate encoded meal information, a barcode generation unit 42 that generates a barcode representing the encoded meal information generated by the encoding unit 41, and a barcode output unit 43 that outputs the barcode generated by the barcode generation unit 42. This allows the meal ordering device 13 to encode and compress the meal information to be included in the barcode. This allows the barcode length per digit output by the barcode generation unit 42 to be increased (enlarged). This reduces barcode reading errors at the meal supply facility 3. Furthermore, because the meal ordering device 13 transmits meal information to the meal supply facility 3 via barcodes, the local network within the meal ordering facility 2 (the network connected to the electronic medical record server 11 and the electronic medical record terminal device 12) can be kept secure. Thus, the meal ordering device 13 can reduce erroneous meal ordering while maintaining network security.

[0077] Barcode output unit 43 prints the barcode on paper media. As a result, meal ordering facility 2 faxes purchase order form 25 using fax transmitter 15. However, if purchase order form 25 is tilted, the barcode may become unreadable or may be misread at meal supply facility 3. Even in such cases, meal ordering device 13 can increase the length of the barcode per digit, thereby reducing barcode reading errors at meal supply facility 3.

[0078] The barcode generator 42 generates multiple barcodes, each containing the user's identification information (patient ID). This allows the meal ordering device 13 to split the meal information into multiple barcodes and output them, making it possible to enlarge each barcode. In the meal supply facility 3, the meal information shown on the multiple barcodes is associated based on the patient ID. In this way, the meal ordering device 13 can increase the length of the barcode per digit, reducing erroneous orders.

[0079] The meal information includes information for distinguishing meal timing (morning, noon, or evening) combined with date information. This makes it possible to add not only the date but also whether the meal was morning, noon, or evening to the meal information for the applicable day (encoded meal information). This allows the encoded meal information to be further compressed.

[0080] The encoding unit 41 adds a fixed value to the specified meal information (type of meal) before encoding it. This allows the meal ordering device 13 to encode the specified meal information in a fixed length, eliminating the need to split the barcode into multiple parts or insert a delimiter code into the barcode. This makes it possible to increase the length of the barcode per digit, further reducing erroneous ordering.

[0081] The meal information is encoded using an encoding method that includes alphanumeric characters. This allows the meal ordering device 13 to reduce the number of digits in the encoded meal information when encoding the meal information. Therefore, the meal ordering device 13 can increase the barcode length per digit, further reducing erroneous orders.

[0082] The barcode output unit 43 generates a barcode in which the length of one digit of the coded meal information is 3.2 mm or more. This allows the barcode to be read accurately at the food service facility 3 even when the order form 25 is tilted 10 degrees and scanned by the FAX transmitter 15. This allows the food service ordering device 13 to further reduce erroneous orders.

[0083] Meal ordering system 1 comprises a meal ordering device 13 and a meal management device 23. Meal ordering device 13 comprises an encoding unit 41 that encodes a user's meal information to generate encoded meal information, a barcode generation unit 42 that generates a barcode indicating the encoded meal information generated by encoding unit 41, and a barcode output unit 43 that outputs the barcode generated by barcode generation unit 42. Meal management device 23 comprises an acquisition unit 61 that acquires the encoded meal information from the barcode, and a decoding unit 62 that decodes the encoded meal information acquired by acquisition unit 61. Meal ordering system 1 configured in this way can reduce erroneous meal ordering while maintaining network security.

[0084] 1 Meal ordering system 13 Meal ordering device 23 Meal management device 41 Encoding unit 42 Barcode generation unit 43 Barcode output unit 61 Acquisition unit 62 Decoding unit

Claims

1. A meal ordering device comprising: an encoding unit that encodes a user's meal information to generate encoded meal information; a barcode generation unit that generates a barcode indicating the encoded meal information generated by the encoding unit; and a barcode output unit that outputs the barcode generated by the barcode generation unit.

2. The meal ordering device according to claim 1, wherein the barcode output unit prints the barcode on a paper medium.

3. A meal ordering device as described in claim 1 or claim 2, wherein the barcode generation unit generates a plurality of barcodes, each of which contains the user's identification information.

4. A meal ordering device according to claim 1 or claim 2, wherein the meal information includes a combination of information for distinguishing meal timing and date information.

5. A meal ordering device according to claim 1 or claim 2, wherein the encoding unit adds a fixed value to the predetermined meal information before encoding.

6. The meal ordering device according to claim 1 or claim 2, wherein the meal information is encoded using an encoding method that includes alphanumeric characters.

7. A meal ordering device as described in claim 1 or claim 2, wherein the barcode output unit generates a barcode in which the length of one digit of the encoded meal information is 3.2 mm or more.

8. A school lunch ordering system comprising a school lunch ordering device and a school lunch management device, wherein the school lunch ordering device comprises: an encoding unit that encodes a user's meal information to generate encoded meal information; a barcode generation unit that generates a barcode indicating the encoded meal information generated by the encoding unit; and a barcode output unit that outputs the barcode generated by the barcode generation unit; and the school lunch management device comprises: an acquisition unit that acquires the encoded meal information from the barcode; and a decoding unit that decodes the encoded meal information acquired by the acquisition unit.

Citation Information

Patent Citations

  • System for provision of meals

    JP1996190585A

  • Ordering system

    JP1997185654A

  • electronic physician order entry system

    JP2009514108A