Food they will actually eat, inside the limits their diet sets
For caregivers and dietitians of people with kidney disease, diabetes, dysphagia or hypertension
CareCuisine drafts a week of the food a patient grew up with, adapted to the limits their condition sets. The Qloo Taste Graph works out what will feel like theirs; USDA nutrient data and a deterministic safety gate check every dish; the dietitian has the last word.
The server is being woken up in the background so your first plan is fast.
Mediterranean heritage · keeps lemon, oregano, garlic and olive oil
Per serving, computed from grams × USDA values · limits from KDIGO 2024 for CKD stage 3
"You can't eat your food any more."
Generic low-sodium meal plans replace the food that feels like home, and patients drift back to it.
Each plan runs the same five stages. Nothing reaches the week without passing the gate. The planner's agent trace shows every stage as it ran.
Condition, heritage cuisines, the music, films and home region they love, and any caregiver constraints.
Symptoms are checked first. Emergency phrases stop the plan; rare-disease descriptions get specialist suggestions.
Tastes become Qloo entities; each cuisine and venue is scored against them. Cuisines they love more get more dinners.
Every recipe's USDA-computed nutrients, texture and glycemic band are checked, along with policy and caregiver rules.
Seven dinners, home-cooked first, plus questions for the dietitian. It downloads as a draft for their review.
The planner is one form on the left and the plan on the right. Six steps, about a minute:
Pick Maria, Harold, Rosa or Dana to fill the form, then change anything. Search the 13 conditions (kidney, diabetes, heart, swallowing, liver) and the limits with their sources (KDIGO, ADA, AHA/ACC, ESPEN…) appear under the field. If yours is not listed, choose Other and enter it: CareCuisine then enforces only what you type and says what it did not check.
One or more of nine: Mediterranean, Italian, Mexican, Cuban, East Asian, South Asian, Japanese, Southern and Diner. Qloo may add a neighbouring cuisine when it scores at least 90% as well as their own. Dishes from it are labelled suggested by Qloo.
Music, films and home region are optional, and the most interesting inputs. Each is looked up in the Qloo Taste Graph, and every candidate is re-scored against it. Maria loves Frank Sinatra and Roman Holiday, so Qloo leans her week Italian.
Per-meal sodium, potassium, phosphorus and carbohydrate. Any number entered here replaces the guideline default and is enforced on every dish, so a dish over it is rejected. Choose 0–3 meals out per week; the rest are cooked at home.
Pick what to leave out (gluten, dairy, egg, shellfish…) and dishes containing it are removed. Caregiver constraints (low sodium, soft foods, wheelchair access) are checked against every suggestion. Symptoms are screened before any food is suggested. "Chest pain" stops the plan and shows emergency guidance instead.
Press Build plan. Read the week, open any recipe to see grams and USDA sources, then use Download for dietitian. You get a draft with recipes, ingredient IDs and the open questions, ready to take to the appointment.
Which limits were enforced, which were not checked, and what the avoid list removed. For a custom condition this says plainly that no guideline is behind it.
Where each number came from: live Qloo or sample data, USDA or estimate, real LLM or none. Check this first.
Seven dinners with nutrient chips against the limits, each recipe's grams, steps and USDA links, and a weekly summary of the highest values.
What the draft could not decide: individualised potassium, protein needs, portions, whether meals out are acceptable.
Restaurants that passed the venue screen, with how to order. Their nutrient values are labelled estimates.
Every rejected dish and venue stays visible, with the exact reason, e.g. "Phosphorus 301 mg is over the 250 mg per-meal limit".
The same request answered by a model with no taste data or gate, so you can see what grounding changes.
Each tool call in order: Qloo search, insights, trending and audiences, the screening and the gate.
Deterministic code, not a model, decides what is safe to suggest. Every candidate passes through three layers and gets one of three verdicts.
A blocklist of prohibited actions: no instructions about medication, doors, money or home devices. Places that cannot serve a meal, such as pharmacies or liquor stores, are rejected.
Per-condition limits for sodium, potassium, phosphorus, carbohydrate, glycemic band and texture, each with a cited source. Dietitian limits replace the defaults.
Low sodium, soft foods and wheelchair access, checked against every suggestion.
Passed all three layers with every nutrient known.
A nutrient value is missing, or a conditional guideline flag fired. It is never auto-approved.
Over a limit or against policy. Shown with the reason, never hidden.
/search | Turns "Frank Sinatra" or "Roman Holiday" into Taste Graph entities |
/v2/insights | Scores places and cuisines against each taste signal |
/v2/trending | Down-weights places whose popularity is cooling |
/v2/audiences | Who else loves this cuisine; shapes the explanation |
/v2/tags | Maps caregiver needs such as wheelchair access to Qloo tags for the outing agent |
Only candidates that passed the gate are ranked. Taste decides among safe options; it never overrides a limit. Dinners are shared out between cuisines in proportion to Qloo affinity.
The sample week takes a couple of seconds. Change one taste and build again to see the plan move.