OperationsLive · in the productQueue & board

BedsideMenu

Patients order hospital meals from bed, inside the salt, calorie and fluid budget of their diet.

Installs with KitchenDiet, whose screen it works on

Get BedsideMenu Open the appAvailable nowHow pricing works →

What it is

The patient chooses lunch from their bed, and their diet decides what fits. The diet is the one ordered in KitchenDiet — cardiac, renal, diabetic, soft — and the dietician adds the day’s budget: salt in grams, calories, fluid in ml (or the diet’s standard budget applies, and the menu says so). The kitchen keeps its dishes with their calories, salt and fluid. From the QR on the bed the patient sees the meal’s menu with each dish marked fits, counts as fluid, or not on their diet, and three live bars for salt left today, calories and fluid as they pick. The server — not the screen — refuses a meal that would take the day’s salt or the meal’s fluid over, a dish the diet excludes, an order after the kitchen’s cut-off, and any order for a patient who is nil by mouth. The kitchen gets a list per meal by ward and bed, and the nurse sees who has not ordered yet and can order for them.

Who uses it: Built for: Every specialty
Reads: The active diet order and any pre-op fast, the kitchen’s dishes with calories, salt and fluid, the bed and ward
Writes: The dietician’s daily budget, each meal order, the bed’s menu link
Never: It never lets a meal past the day’s salt or the meal’s fluid, never serves a patient who is nil by mouth, and never changes the diet itself — that stays with the doctor and the dietician in KitchenDiet.
Access: Only people whose role includes it — the clinic owner decides who
Your data: PHI-lite. Hosted in Boston, United States. On uninstall: Bedside ordering stops. Diets, budgets and past meal orders are kept; KitchenDiet’s own meal ticks carry on.

How it works

Set the budget on the dietThe dietician adds salt, calories and fluid for the day to the diet KitchenDiet already holds.
Patient orders from bedThey scan the bed’s QR, pick from dishes marked to fit their diet, and watch the salt and fluid bars as they choose.
Kitchen cooks to the listEach meal’s orders by ward and bed, and the beds that have not ordered, for the nurse to help.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It never lets a meal past the day’s salt or the meal’s fluid, never serves a patient who is nil by mouth, and never changes the diet itself — that stays with the doctor and the dietician in KitchenDiet.

AI in BedsideMenu

AskQuestions about what is on screen — “What needs attention in BedsideMenu today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

BedsideMenu — Bedside Menu — Let inpatients order meals from bed, kept inside their diet’s salt, calories and fluid — 01Bedside Menu — Let inpatients order meals from bed, kept inside their diet’s salt, calories and fluidCaptured from the running demo clinic

01Bedside Menu — Let inpatients order meals from bed, kept inside their diet’s salt, calories and fluidCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 3

KitchenDiet Patient Registry WardLine

See the whole clinic →

Questions clinics ask

What does BedsideMenu do?

Patients order hospital meals from bed, inside the salt, calorie and fluid budget of their diet. The patient chooses lunch from their bed, and their diet decides what fits. The diet is the one ordered in KitchenDiet — cardiac, renal, diabetic, soft — and the dietician adds the day’s budget: salt in grams, calories, fluid in ml (or the diet’s standard budget applies, and the menu says so). The kitchen keeps its dishes with their calories, salt and fluid. From the QR on the bed the patient sees the meal’s menu with each dish marked fits, counts as fluid, or not on their diet, and three live bars for salt left today, calories and fluid as they pick. The server — not the screen — refuses a meal that would take the day’s salt or the meal’s fluid over, a dish the diet excludes, an order after the kitchen’s cut-off, and any order for a patient who is nil by mouth. The kitchen gets a list per meal by ward and bed, and the nurse sees who has not ordered yet and can order for them.

What data does BedsideMenu read and write?

BedsideMenu reads the active diet order and any pre-op fast, the kitchen’s dishes with calories, salt and fluid, the bed and ward and writes the dietician’s daily budget, each meal order, the bed’s menu link. Its data class is PHI-lite. Every app works on the same patient record — nothing is copied into a silo.

What does BedsideMenu deliberately not do?

What happens to our data if we uninstall BedsideMenu?

Bedside ordering stops. Diets, budgets and past meal orders are kept; KitchenDiet’s own meal ticks carry on.

Is BedsideMenu available today?

Yes — BedsideMenu is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see BedsideMenu running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Operations

All 146 →