JP2008027148A - Nutritional management system, nutritional management server, nutritional management method, and nutritional management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a nutritional management system, a nutritional management server, a nutritional management method and a nutritional management program capable of managing data to be used for nutritional guidance and a record of the nutritional guidance based on the data and giving the nutritional guidance efficiently and easily with respect to the nutritional management system, the nutritional management server, the nutritional management method and the nutritional management program which manage meals to be provided to patients. <P>SOLUTION: The nutritional management system for managing menus of meals to be provided to the patient comprises: a diet prescription information acquisition means for acquiring diet prescription information on the patient; a contraindication information registering means for registering contraindication information to information on dishes composing the menu; a personal menu target extracting means for collating the contraindication information registered by the contraindication information registering means with the diet prescription information on each patient to extract a combination of the patient who needs personal menus and the menu; and an alternative candidate extracting means for extracting candidates of alternative dishes with respect to the menu for the patient extracted by the personal menu object extracting means. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a nutrition management system, a nutrition management server, a nutrition management method, and a nutrition management program, and in particular, a nutrition management system, a nutrition management server, a nutrition management method, and a nutrition management server for managing meals provided to patients. , Concerning nutritional management program.

  In providing hospital meals for hospitalized patients, the type of meal (food type) is classified according to disease, and the menu of 3 meals (morning, lunch and evening) is decided for each food type and made common. Although efforts are being made to improve efficiency, some hospitals still have to do a lot of work, such as creating menus for more than 100 meals per day. In order to improve this, a system for creating a planned menu based on past menu contents has been proposed (see, for example, Patent Document 1).

Further, nutritional guidance for individual patients is provided by a dietitian according to the content of nutritional guidance instructions by a doctor. For example, a dietitian receives a nutrition instruction instruction such as “meat ban” by a doctor as a document, and inputs the content of the nutrition instruction instruction to a computer. Then, from the patient's menu, change the dishes using ingredients that cannot be eaten by some patients or ingredients that cannot be eaten by the doctor's instructions to another meal with equivalent nutrition, and create a menu for each patient. . Conventionally, a system in which this nutritional guidance is systematized by a computer system has been proposed (for example, see Patent Document 2).
Japanese Patent Laid-Open No. 7-296071 JP 2000-348013 A

  However, in order to reflect nutritional guidance for individual patients to a menu that is standardized for each type of meal, it is necessary to examine alternatives to food while referring to nutritional guidance instruction information of different doctors for each patient. It takes a lot of work. In addition, since it is necessary to change a part of the menu on the day according to the patient's medical condition that changes every day, it is preferable that the treatment can be performed in a short time. Furthermore, it is also expected to improve the eating rate and make patient nutrition more effective by providing dishes that meet the preferences of hospitalized patients within a range that does not affect treatment.

  The present invention has been made in view of the above points, and it is possible to efficiently and easily perform personal menu creation management based on nutritional guidance of individual patients while performing menu management standardized for each type of food. It is an object to provide a nutrition management system, a nutrition management server, a nutrition management method, and a nutrition management program.

  The present invention is a nutritional management system for managing a menu of meals to be provided to a patient, and includes contraindications for registering contraindication information in meal information acquisition means for acquiring the patient's meal information and cooking information constituting the menu Information registration means, and personal menu object extraction means for collating the contraindication information registered by the contraindication information registration means with the meal information of each patient and extracting a combination of a patient and a menu that require personal menu. Features.

  Furthermore, it has an alternative candidate extracting means for extracting alternative dish candidates for the patient's menu extracted by the individual menu target extracting means.

  Further, the present invention is characterized by having nutrition amount acquisition means for totaling the nutritional amount of the meal for one day for each component and acquiring the nutritional amount taken by the patient that changes in accordance with the cooking change at the time of creating the individual menu.

  Further, the alternative candidate extracting means is characterized in that a dish using ingredients that the patient is not good at can be changed to another dish based on the patient preference information as contraindication information.

  Further, the present invention is a nutrition management method for managing a menu of meals to be provided to a patient, and registers contraindication information in a meal information acquisition procedure for acquiring the patient's meal information and information on dishes constituting the menu A contraindication information registration procedure to be performed, and a personal menu target extraction procedure for extracting a combination of a patient and a menu that require personal menu by comparing the contraindication information registered in the contraindication information registration procedure with each patient's meal information. It is characterized by that.

  Furthermore, the present invention registers in a computer with a meal information acquisition procedure for acquiring patient meal information, a contraindication information registration procedure for registering contraindication information in the information of the dishes constituting the menu, and a contraindication information registration procedure. This is a computer-readable program that executes a personal menu target extraction procedure for collating the contraindicated information and the meal information of each patient and extracting a combination of a patient and a menu that require personal menu.

  According to the present invention, the patient's meal information is acquired, the contraindication information is registered in the dish information constituting the menu, the registered contraindication information is compared with each patient's meal information, and the individual menu is required. The combination of patient and menu can be extracted, and the menu provided to each patient can be examined based on the results of this review, and the patient can be provided with a meal according to the patient's constitution, medical condition, and preference. The eating rate is improved, and it can help the patient recover from nutritional aspects.

  FIG. 1 shows a system configuration diagram of an embodiment of the present invention.

  The nutrition management system 100 of the present embodiment is configured such that the nutrition management server 111, the terminal 112, and the medical information database 113 can communicate with each other via the hospital network 114.

  FIG. 2 shows a block diagram of the nutrition management server 111.

  The nutrition management server 111 includes a computer system and includes a communication unit 121, a processing unit 122, and a meal information database 123.

  The communication unit 121 controls communication with the terminal 112 and the medical information database 113 via the hospital network 114.

  The processing means 122 executes a process of easily creating and extracting personal meal information and menus from the meal information database 123 based on a nutrition management program installed in advance.

  FIG. 3 shows a data configuration diagram of the meal information database 123.

  The meal information database 123 includes a contraindication information master 123c, a meal note database 123a and a dish master 123b, an ingredient master 123d, a menu database 123e, a meal number database 123f, a personal menu database 123g, a dish conversion result database 123h, and a prohibited ingredient-use dish database 123i. Etc.

  The meal note database 123a is a database for managing information on meals that each patient should ban or avoid taking from each meal unit. The meal date database 123a includes a meal provision date, a meal category, a patient number, a food type code, contraindication information, and the like. It is configured. The meal provision date indicates the meal provision date, and the meal classification indicates the distinction between breakfast, lunch, and dinner. The patient number is identification information for identifying a patient. The food type code is menu category information created for each disease.

  The contraindication information is stored in the form of a list of prohibition codes such as foods whose intake is prohibited or avoided for reasons such as allergies, drinking with drugs, medical conditions, and preferences. For example, if the ingestion of meat is prohibited, the prohibition code corresponding to the contraindication comment “inhibition of meat” indicates “inhibition of fish” when ingestion of fish is prohibited, “inhibition of eggs” "If soba consumption is prohibited, a prohibition code corresponding to a contraindication comment such as" no soba "is set. In addition, for example, a prohibition code corresponding to a contraindication comment of “egg allergy” when the patient has an egg allergy constitution and “egg dislike” when egg cooking is not good is set.

The patient number and the corresponding patient name and medical information are registered and managed in the medical information database 113 connected via the in-hospital network 114. The input of the meal data may be manually input based on a doctor's meal slip or may be obtained by searching the medical information database 113.

  The contraindication information master 123c is a database that manages the contents of the contraindication information of patients and foods, and the inhibition codes and the contraindication comments are associated with each other. By registering the contraindication information, which has been conventionally specified in the patient's meal note, with the food that is the subject of the contraindication information, it is possible to automatically determine the contraindication food.

    The ingredient master 123d is a database for managing the contraindication information of the ingredient, and is composed of the ingredient code, the ingredient name, and the contraindication information. The food material code is information for identifying the food material. The ingredient name is information indicating the name of the ingredient. The contraindication information indicates what contraindications the food is.

    The dish master 123b is composed of a dish code, a dish name, ingredients information, contraindication information, an ingredient amount, and the like. The dish code is information for identifying a dish. The dish name is information indicating the name of the dish. The contraindication information is registered by collecting all the contraindication information for all ingredients used in cooking. For example, in the dish name “Fish Meunier”, a prohibition code corresponding to the contraindication comment “Fish Prohibition” is set. In addition, in the dish name “Chicken salt grilled”, a prohibited code corresponding to the prohibited comment “Chicken prohibited” is set.

The ingredients used are set in the ingredients information. For example, “white fish” is set as the ingredient information for the dish name “Fish Meunier”, and “chicken” is set as the ingredient information for the dish name “Chicken Salt”, and the amount of each is stored as the edible amount.
The amount of ingredient is information according to ingredient of the amount of nutrition of the whole dish.

The menu database 123e is a database that manages the food contents of the common menu for each type of meal, and stores the cooking codes of the dishes constituting the menu.
The number of meals database 123f is a database for managing the provision plan quantity of each menu registered in the menu database 123e.

    The personal menu database 123g is a database for managing the individual menu created in the individual menu creation process, and stores the cooking codes and edible amounts of the dishes constituting the menu.

    The dish conversion record database 123h manages the record of the dish change in the individual menu creation process, and records the dish before the change, the contraindication information in the state before the change, the dish after the change, and its edible amount. .

    The forbidden food-use dish database 123i stores a result of extracting a combination of a patient and a dish that needs individual menu creation.

  The terminal 112 is composed of a computer system, and can communicate with the nutrition management server 111 and the medical information database 113 via the hospital network 114.

  The medical information database 113 is composed of ordering information, patient information, and the like, and the nutrition management server 111 can refer to these information.

  FIG. 4 shows a process flowchart of the nutrition management process of the nutrition management server 111.

  In the nutrition management server 111, the menu to be provided to the patient in step S1-1 is created for each food type and registered in the menu database 123e. The scheduled menu consists of standard hospital food dishes. In addition, the planned number of meals of the planned menu created and registered is registered in the meal number database 123f.

  In step S1-2, the nutrition management server 111 receives personal meal information from the ordering system of the ward to a future date that is a predetermined number of days ahead of the day. The meal note information is configured to include food types, contraindication information such as contraindication comments and patient allergy information. Meal information is acquired from the medical information database 113 managed by the ordering system through the in-hospital network 114 and stored in the meal database 123a.

  In step S <b> 1-3, the nutrition management server 111 creates an individual menu based on the individual meal and schedule menu registered in the database 123.

  Next, the nutrition management server 111 totals the order status based on the individual menu created in step S1-4, and outputs a form in step S1-5.

  Next, the personal menu generating process in step S1-3 will be described.

  FIG. 5 shows a process flowchart of the personal menu generation process.

    First, when there is a request for extraction of an individual menu item from the terminal 112 in step S2-1, the nutrition management server 111 extracts a combination of a patient and a menu item to be personal menu items from the meal information database 123 in step S2-2. The result is written in the prohibited food-use food database 123i.

  The individual menu target extracted in step S2-3 is notified to the request source terminal 112. In addition, the meal provision date is designated as an extraction condition in the extraction request for the individual menu item in step S2-1.

  On the request source terminal 112, a personal menu creation list screen is displayed by a personal menu target notification from the nutrition management server 111.

  FIG. 6 shows a screen configuration diagram of the personal menu list screen.

  Personal menu list screen 210 includes date display field 211, meal category display field 212, food type display field 213, food type name display field 214, patient number display field 215, patient name display field 216, menu presence / absence display field 217, contraindications It is configured to include a comment field 218, an end button 219, a search button 220, a clear button 221, and an execution button 222. Only combinations of patients with contraindicated comments and menus are displayed, and individual menus are to be created. Is shown.

  In the personal menu list screen 210, a date display field 211 displays a meal provision date. In the food type name display column 214, the name of the food type is displayed. The displayed food type name indicates the abbreviated name of the food type.

  In the menu presence / absence display column 217, information indicating whether or not the individual menu has been created is displayed. In the contraindication comment column 218, the results of matching the contraindication information of each patient with the menu are displayed, and by referring to the contraindication comment column 218, it can be easily understood that ingredients that the patient cannot take in the menu are included. By clicking the end button 219, search button 220, clear button 221 and execution button 222 on the screen after the display of the personal menu list screen 210, the individual menu list screen 210 can be selected in units of lines, or can be searched, finished, searched, and cleared ( Operations such as (cancel) / execute (register) can be performed.

  When the row of the list displayed on the request source terminal 112 is selected in step S2-4, the nutrition management server 111 selects the meal provision date, meal category, and food type code of the selected row in step S2-5. The menu database 123e is searched to acquire dishes constituting the menu.

  Next, the nutrition management server 111 searches for a dish having a contraindication comment for the patient in the searched dishes in step S2-6 from the prohibited food using dish database 123i, and acquires a prohibition code. Further, the dish conversion result database 123h is searched from the dish having the contraindication comment and the kind information to obtain alternative dish candidates.

  The nutrition management server 111 displays a personal menu creation screen in step S2-7.

  FIG. 7 shows a screen configuration diagram of the personal menu creation screen.

  The personal menu creation screen 230 includes a personal menu information display field 231, a menu display field 232, a change candidate list display field 233, a nutritional ingredient display field 234, an additional dish nutritional ingredient display field 235, and operation buttons 236.

  In the individual menu information display field 231, contraindication information regarding the patient name, the type of meal, and the patient's meal is displayed as meal note information, and further, the meal provision date and the meal category for which the individual menu is to be created are displayed.

  The menu display field 232 includes an individual menu display field 241, a common menu display field 242, and a contraindication comment display field 243.

  The menu for each individual is displayed in the menu for individual menu display 241. The common menu display column 242 displays a common menu.

  The contraindication comment display column 243 is provided between the individual menu display column 241 and the common menu display column 242, and displays contraindication comments corresponding to the respective dishes of the common menu for the patient. By referring to the individual menu information display column 231, it is possible to recognize at a glance which dishes should be changed and which dishes have been changed.

  In the change candidate list display column 233, a dish list of change candidates is displayed, and corresponding contraindication comments are displayed for the patient for each dish.

  In the nutritional component display column 234, the nutritional component value of the menu being changed is aggregated and displayed based on the component amount information of the cooking master 123b for a meal for one day. Thereby, the operator of the terminal 112 can easily determine whether the patient's daily nutrition intake is appropriate or not due to the menu change.

  In the additional cooking nutrient component display column 235, a list of dishes added to the common menu due to the change is displayed. By changing the edible amount of cooking, it is possible to easily adjust the increase or decrease in nutrient intake accompanying the change in cooking. Note that the component amount when the edible amount of the dish is changed is automatically calculated from the ratio between the two by obtaining the total edible amount of each ingredient of the dish from the registration information in the dish master 123b, for example.

  The operator of the terminal 112 can create a personal menu in which prohibited ingredients are not used by repeating the processes of steps S2-4 to S2-7.

  When accepting the operator's registration operation in step S2-8, the nutrition management server 111 registers the personal menu displayed in step S2-9 in the personal menu database 123g and stores it in the meal number database 123f. Decrement the number of common menu meals before the change. In addition, the dish change record is added to the dish conversion record database 123h.

  In addition, since the required amount of the above-mentioned scheduled menu is managed in the number-of-foods database for each type of meal, it is not necessary to perform the personal menu creation process for all patients. Can be done efficiently.

  Next, the individual menu target extraction process in step S2-2 will be described.

  FIG. 8 shows a process flowchart of the individual menu object extraction process.

  In step S3-1, the nutrition management server 111 sequentially reads the meal provision date records specified in step S2-1 one by one from the meal database 123a. In step S3-2, it is determined whether the read result is EOD (End Of Data). If the read result is EOD, the process ends.

  When it is not EOD, it progresses to step S3-3, and the menu database 123e is searched based on the meal provision date of the acquired meal note record, a meal division, and a food type code. In step S3-4, a dish code included in the menu record of the search result is sequentially selected.

  If it is determined in step S3-5 that all the cooking codes have been processed, the nutrition management server 111 returns to step S3-1 to read the next meal note record, otherwise proceeds to step S3-6 and proceeds to step S3-6. To obtain the prohibition code corresponding to the dish code.

  The prohibition code acquired in step S3-7 and the prohibition code of the meal note record are matched, and if there is a matching code in step S3-8, it is determined that the prohibited food is being used, and the process proceeds to step S3-9. The dish code and the corresponding forbidden code are written in the forbidden food using dish database 123i together with the patient number of the meal record and the like.

  If there is no matching prohibition code in step S3-8, the process returns to step S3-4 to process the next dish code of the menu record. In this way, the target of the individual menu is extracted, and the result is written in the prohibited food-use dish database.

  Next, the alternative dish candidate search process in step S2-6 will be described.

  FIG. 9 shows a process flowchart of the alternative dish candidate search process.

  In step S4-1, the nutrition management server 111 searches the prohibited food-use dish database 123i using the meal provision date, meal category, meal type code, and patient number in the selected row in step S2-4. In step S4-2, the prohibition code stored in the search result record is stored in association with the same dish obtained in the menu search process in step S2-5.

  Proceeding to step S4-3, the dish conversion result database 123h is searched using the food type code, the dish code, and the contraindication information of the prohibited-food-use dish record to search for alternative candidate dishes. Proceeding to step S4-4, the substitute candidate dish as the search result is displayed in the change candidate list display field 233, and the matching result with the prohibition code of the meal record is displayed to easily determine whether or not the substitute is possible. Judgment is possible. Further, an alternative candidate having the latest meal provision date among the search results is displayed as an alternative dish in the individual menu display column 241. In this way, alternative food candidates are retrieved and displayed on the personal menu creation screen 230.

  Further, the created menu information is distributed, for example, in the form of a menu table to the terminal 112 provided in the cooking room (cooking room) together with the menu information other than the personal menu.

  FIG. 10 shows a screen configuration diagram of the contraindication information registration screen.

  The contraindication information registration screen 250 includes an ingredient display column 251, a contraindication comment display column 252, and a contraindication check column 253. In the ingredient display column 251, a list of ingredient names is displayed. In the contraindication check column 253, a check mark can be set for each ingredient in the contraindication comment display column 252 and the ingredient display column 251.

  By adding a check mark to the corresponding contraindication comment in the contraindication check column 253, the contraindication comment is set in the food material master. The contraindication comments registered in the food master are further set in association with the food information of each dish registered in the dish master 123b as the contraindication information of the dish master.

  As described above, contraindication information is registered in the information of the dishes that make up the menu, and the combination of the patient and menu that require individual menu is automatically extracted and extracted by collating with each patient's meal information. By automatically extracting and displaying alternative dish candidates for the menu that has been made, it is possible to efficiently and easily perform the creation of the individual menu.

Also, by displaying the total amount of nutrition for one day by component, you can check the amount of nutrition consumed by the patient that changes with the changes in the dishes at the time of creating the individual menu. And can be done easily.

In addition, by registering the patient preference information as contraindication information, it is possible to change the dish using ingredients that the patient is not good at, so an improvement in the eating rate can be expected.

  In addition, this invention is not limited to the said Example, It cannot be overemphasized that a various modified example can be considered in the range which does not deviate from the summary of this invention.

It is a system configuration figure of one example of the present invention. It is a block block diagram of the nutrition management server 111. It is a data block diagram of the meal information database. It is a process flowchart of the nutrition management process of the nutrition management server 111. It is a process flowchart of an individual menu production | generation process. It is a screen block diagram of a personal menu list screen. It is a screen block diagram of a personal menu production | generation screen. It is a process flowchart of an individual menu object extraction process. It is a processing flowchart of an alternative dish candidate search process. It is a screen block diagram of a contraindication information registration screen.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Nutrition management system 111 Nutrition management server, 112 Terminal, 113 Medical information database 114 Hospital network 121 Communication means, 122 Processing means, 123 Meal information database 123a Meal note database, 123b Cooking master 123b
123c Contraindication information master, 123d Food master, 123e Menu database 123f Meal number database, 123g Personal menu database 123h Dish conversion results database, 123i Banned food use database 210 Personal menu list screen 211 Date display column, 212 Meal category display column, 213 Species name display field 214 Species name display field, 215 Patient number display field, 216 Patient name display field 217 Menu presence / absence display field, 218 Contraindication comment field 219 End button, 220 Search button, 221 Clear button 222 Execute button 230 Create individual menu Screen 231 Individual menu information display column, 232 Menu display column, 233 Change candidate list display column 234 Nutrition component display column, 235 Additional food nutrition component display column, 236 Operation buttons 241 Individual menu display column, 242 Common menu示欄 243 contraindicated comment display column 250 contraindication information registration screen 251 food display column, 252 contraindications comment display column, 253 contraindicated check column

Claims (6)

A nutrition management system for managing a menu of meals to be provided to a patient,
A meal information acquisition means for acquiring the patient's meal information;
Contraindication information registration means for registering contraindication information in the information of the dishes constituting the menu;
A personal menu target extracting means for collating the contraindication information registered by the contraindication information registration means with the meal information of each patient and extracting a combination of a patient and a menu that require personal menu. Nutritional management system. 2. The nutrition management system according to claim 1, further comprising alternative candidate extraction means for extracting alternative dish candidates for the patient menu extracted by the individual menu target extraction means. The nutritional amount obtaining means for obtaining a nutritional amount taken by a patient who changes in accordance with a dish change at the time of creating a personal menu, and totaling the nutritional amount of the meal for one day by component. Nutrition management system. 2. The nutrition management system according to claim 1, wherein the alternative candidate extraction means can change a dish using ingredients that the patient is not good to other dishes based on patient preference information as the contraindication information. . A nutrition management method for managing a menu of meals to be provided to a patient,
A meal information acquisition procedure for acquiring the patient's meal information;
Contraindication information registration procedure for registering contraindication information in the information of the dishes constituting the menu,
A personal menu target extraction procedure for collating the contraindication information registered in the contraindication information registration procedure with the meal information of each patient and extracting a combination of a patient and a menu that require personal menu. How to manage nutrition. On the computer,
A meal information acquisition procedure for acquiring the patient's meal information;
Contraindication information registration procedure for registering contraindication information in the information of the dishes constituting the menu,
Computer-readable to execute the personal menu target extraction procedure for collating the contraindication information registered in the contraindication information registration procedure with the meal information of each patient and extracting a combination of a patient and a menu that require personal menu Program.

Images