Set a patient's diet once and MedMeals applies it everywhere: the bedside tablet, the family's phone, the kitchen's KOT and the discharge bill. Therapeutic rules, allergies and textures are enforced by the menu itself, not by memory.
4 of 8 items shown to this patient, on every channel.
Sample data
In most hospitals a diet order travels by hand. The doctor writes it, a nurse copies it into the diet register, the dietitian adjusts it on rounds and the kitchen reads it off a slip before breakfast. Every copy is a chance for renal to become regular, or for a peanut allergy to fall off the page.
Families add their own layer: food from the canteen, food from home, a menu card on the wall. Nobody can see what actually reached the tray until something goes wrong, and by then the only record is a register that three people have written in.
MedMeals turns each diet order into rules that every ordering channel respects, so compliance does not depend on who is on shift.
Configure renal, cardiac, diabetic, liquid, soft and any other diet your protocols define. Each diet carries the rules that decide which items a patient can see and order.
Record a patient's allergies and intolerances once. Items that contain them disappear from that patient's menu on every channel, so they cannot be ordered by mistake.
Store calories, protein, carbohydrates, sodium and more against each item, so dietitians can build menus that meet the order and see what a meal actually contains.
Plan rotating menus across days and meal slots, so long-stay patients get variety without anyone re-planning the week by hand.
Define breakfast, lunch, dinner and snack windows, so ordering, cooking and delivery follow the times your wards actually run on.
Update a diet on rounds and future orders follow it. When a patient moves bed or ward, the diet profile moves with them.
Attendees and visitors order from their own paid menus, so family meals never mix with a patient's therapeutic plan.
On admission or during rounds, the dietitian records the diet, texture, allergies and cycle on the patient's record.
Every channel, from the RSOT tablet to the attendee app, shows only the items that satisfy the diet.
Staff order at the bedside or the family orders from a phone. Unsafe items are never on offer.
The order prints as a KOT and a meal card that name the diet, bed and ward, so the tray is built right.
A delivery OTP at the bedside confirms that the right tray reached the right patient.
The therapeutics master holds every diet your hospital uses, with its description, recommended use and precautions. Dietitians maintain it, and the menu engine applies it to every patient on that diet.
Therapeutics master
Each menu item carries its meal times, nutritional values, intolerances and the therapeutic diets it suits. That is how the menu knows what to show a patient and what to hide.
Patient menu item editor
| Area | On paper | With MedMeals |
|---|---|---|
| Diet order | Handwritten, then copied into registers and kitchen slips | Recorded once on the patient's digital record |
| Allergies | Remembered by staff, and sometimes missed | Hidden from the patient's menu on every channel |
| Diet change | Phoned to the kitchen, often after the meal is plated | Updated on rounds, and the next order follows it |
| Menu planning | Rebuilt by hand every week | Multi-day cycles that rotate on their own |
| Audit evidence | Scattered across registers and files | A complete, exportable diet history for each patient |
Items that break a patient's diet are never on that patient's menu, so they cannot be ordered, cooked or delivered to them.
Nothing is copied between registers and slips, which means fewer wrong trays and fewer missed allergies.
Dietitians set rules once instead of checking every slip, and spend their rounds on assessment and counselling.
Every diet order, change and delivered meal is logged, ready for NABH and internal audits.
Still have a question? Ask our team or call +91 79845 98296.
Hospital diet management software records each inpatient's diet order, including the therapeutic diet, texture and allergies, and applies it to every meal. In MedMeals the diet drives the menu itself, so patients, families and staff only see items the patient is allowed to eat.
Hospitals configure their own therapeutic diets in the therapeutics master, for example renal, cardiac, diabetic, liquid and soft diets, each with a description and precautions. Menu items are tagged with the diets they suit, and the menu engine applies those rules for each patient.
Allergies and intolerances are recorded on the patient's record. Any menu item that contains them is hidden from that patient's menu on every ordering channel, including the RSOT tablet, the attendee app and admin ordering.
Yes. The dietitian updates the diet on the patient's record and future orders follow the new diet. Kitchen and nursing teams receive diet-change alerts in real time.
Yes. You can plan multi-day diet cycles across meal slots, so long-stay patients get variety while every item still satisfies their diet.
Yes. When a patient is transferred, the diet profile moves with them to the new ward and bed, so the next meal is still correct.
Book a demo and bring your diet list. We will walk you through how your protocols map to the menu engine, ward by ward.
We have emailed you a confirmation. Someone from the MedMeals team will reach out within one working day to schedule your demo. If it is urgent, call +91 79845 98296.