Clinical recipe library vs. generic cookbook
Allergens, macros, normalised ingredients, and plan integration — not just «meal ideas»
An Instagram cookbook or a «100 healthy recipes» PDF is not a clinical tool. In practice you need recipes with **calculated macros**, **identified allergens**, **normalised ingredients**, and **filtering by patient restrictions**. This guide explains the difference between a clinical library and a generic cookbook, and how to integrate them into the plan without duplicating work.
Generic cookbook: inspiration yes, clinical use no
- Free-text ingredients («a handful of spinach»)
- Estimated or missing macros
- No reliable allergen filter
- No link to patient file
- No traceability of what was prescribed and when
Fine for patient inspiration, but not for building a plan with medical restrictions (coeliac disease, CKD, tree nut allergy) without manual ingredient-by-ingredient review.
What defines a clinical recipe library
1. Master ingredients with nutritional values per 100 g and common units
2. Automatic calculation of kcal and macros per serving from actual quantities
3. Allergen and diet flags (gluten-free, lactose-free, vegetarian…) inherited from ingredients
4. System recipes + own recipes by professional or centre
5. Filter by patient restrictions before assigning to plan
6. Patient preferences (favourite / dislike) recorded in file
Without master ingredients, every clinician recalculates macros in Excel and errors multiply.
Public recipes vs. private centre recipes
Professional recipes: your own formulations, centre protocols, recipes adapted to local population.
Shared centre recipes: in multi-clinician clinics, avoid each dietitian reinventing the «post-workout egg white omelette».
Use clinical tags (`high-protein`, `low-fodmap`, `paediatric`) for quick filtering; avoid vague tags (`healthy`, `tasty`).
Clinical workflow: from library to patient plan
2. Filter library: exclude allergens and incompatible diets
3. Select recipes for breakfast / lunch / dinner / snacks
4. Adjust servings to match overall plan macros
5. Patient sees recipes on portal with ingredients and steps
6. At follow-up, log preferences (favourite / rejected) for next prescriptions
Avoid: copying recipes from the plan as Word text without library link → impossible to recalculate if you change a serving.
Recipes and AI: complement, not substitute
- Ingredients exist in the local database
- Patient allergens are excluded
- Macros match the signed plan
A solid clinical library feeds AI with verified data; a generic cookbook feeds it estimates and nutritional hallucinations.
Criteria to evaluate a software recipe module
1. Are ingredients normalised or free text?
2. Do macros recalculate when servings change?
3. Can I create own recipes and duplicate system ones?
4. Does it filter by allergens in the patient file?
5. Does the patient see recipes on portal or only static PDF?
6. Are recipes available in multiple languages for international patients?
7. Can I export or print the recipe with macros per serving?
Want clinical recipes integrated with plan and patient portal?
NutriManager links a recipe library with master ingredients, allergen filters, and direct assignment to the nutrition plan.
Frequently asked questions
Yes. It includes system and own recipes, master ingredients with allergens, macro calculation per serving, and plan linking. Patients can view them on the portal.
You can create them manually in the recipe module. If you have many, prioritise the 20-30 you prescribe most; ROI is higher than migrating an entire cookbook at once.
You can duplicate a public recipe and adapt it to your protocol without changing the original system version.
Use timing tags (`pre-workout`, `post-workout`) and filter by high protein or carbohydrate macros per phase. The clinical library lets you repeat prescriptions per mesocycle without rewriting.