A nutritionist who wants grilled chicken and brown rice in lunch should not retype seven macro fields in every plan. The only reuse Smart Clinic used to offer was cloning an entire template — all or nothing. There is now a diet library of foods, meals, and days, and a full-page builder that puts that library next to the plan.
Print layouts, PDF export, and WhatsApp still send the finished plan. The library is how the plan is built; it is not a second document the patient has to learn.
Three building blocks
- Foods — the atom: a named portion with calories and macros, in English and Arabic if you want both.
- Meal blocks — a named set of foods with a suggested time, for example a high-protein breakfast.
- Day blocks — a named set of meals, for example a 1600 kcal diabetic day.
Every entry can carry tags (goal, condition, cuisine, meal type, allergen, diet style) and searchable calorie and protein ranges. The palette can show “breakfast, 300–450 kcal, at least 25 g protein, tagged diabetic”. Cards show how often the clinic actually uses that block, so the usual breakfast rises to the top.
Whole-plan templates still exist. The library is the smaller unit of reuse — the piece you needed between “clone everything” and “start from zero”.
Find what this patient needs
Search by name. Filter with chips. Narrow by calories or a protein floor. When the plan belongs to a patient, the palette can highlight blocks tagged for that patient’s conditions — diabetes, hypertension, and the rest — instead of making you remember which breakfast you use for which complaint.
Shared starter rows sit beside the clinic’s own. Editing a shared entry copies it first; the original stays for every other clinic.
Assemble, type, or ask AI
The builder is a full page, not a cramped modal. Search and filter on one side; the plan canvas on the other. It autosaves. Click or drag a block to insert it. Scale a portion (half, one-and-a-half, double) as it lands. A mis-drop can be undone.
Typing a food that has never existed is still allowed. Nothing about the library is a gate. A one-click save puts a meal already sitting in a plan back into the library if it is worth keeping. You can also create a block in the palette and insert it in the same motion.
The diet assistant can still draft a meal, a day, or a whole plan. It now searches the clinic’s own approved blocks first, and it says when a proposed meal came from the library rather than from thin air. You still review before anything is applied.
Getting content in
Four ways, all first-class:
- Add entries by hand on the library page — a proper editor, not a tiny popover. See usage, archive what is dead weight, and tag in bulk after an import.
- Import from Excel, with downloadable sheets for foods and meals.
- Extract a PDF, Word file, or photo of an existing plan into reviewable blocks. Nothing is written until you accept the proposal.
- Save a day, meal, or item already sitting in a plan.
New clinics also get a shared starter catalogue — foods, meals, and days they can use as-is or copy and adapt, including Gulf, Levantine, and Egyptian dishes a Western food list would miss.
The snapshot rule
Inserting copies the content into the plan. Changing a library entry later does not rewrite a plan a patient is already following. That is a clinical safety property, not a convenience.
The patient still receives the same printable plan and the same WhatsApp message as before. What changed is the empty page the nutritionist used to face.