The Health & Wellness category in AIUNIFY PROS SUITE currently contains three active subscriber-facing tools:
The current Sidebar routes these tools to:
/symptom-journal/meal-plan/workout-routineAll three are currently marked New in the Sidebar.
The Sidebar labels open the following full Tool pages:
All three current Health & Wellness Tools use AIUNIFY's shared:
Standard AI Generator Workspace
There is no specialized medical dashboard, Nutrition database, fitness tracker, wearable integration, symptom calendar, or exercise logging interface in these pages.
The current category operates as:
Describe Your Situation or Goal
→ Generate AI Guidance
→ Review the Output
→ Verify Important Health, Nutrition, or Exercise Information
→ Copy or Download
→ Use the Approved Information in the Appropriate Personal or Professional Workflow
The Health & Wellness Tools can help subscribers:
They should not be treated as independent professional medical, nutritional, or fitness services.
Symptom Journal Analyzer can organize symptoms and suggest potential patterns or triggers.
It does not establish a medical diagnosis.
A generated possible Trigger should be interpreted as something that may be worth reviewing—not as proof of the cause of a symptom.
Meal Plan Generator creates meal-planning content from the subscriber's instructions.
It is not a source-verified clinical Nutrition system.
Workout Routine Builder creates exercise-program recommendations.
It is not a live assessment of:
Health, medical, dietary, and exercise decisions can have consequences that depend on individual circumstances.
Generated content should be reviewed accordingly before it is acted upon.
Sidebar Tool ID:
symptom-journal
Route:
/symptom-journal
Sidebar Tool ID:
meal-plan
Route:
/meal-plan
Sidebar Tool ID:
workout-routine
Route:
/workout-routine
The current Sidebar gives all three Health & Wellness entries:
isNew: true.
None of these three Sidebar entries is currently marked:
Pro
General subscription, assigned-Tool, Token, feature-status, and system-configuration rules can still determine availability.
All three Tools use Standard ToolPage.
The shared workspace requires an authenticated AIUNIFY PROS SUITE session and redirects unauthenticated subscribers toward:
/login.
Each Health & Wellness page displays:
The left-side Card is:
Input
Current shared wording:
Describe what you want to generate.
Each Tool uses a single natural-language Textarea.
There are no dedicated form fields for:
unless the subscriber includes those details in the Prompt.
Because these Tools are natural-language generators, more context can improve relevance.
However, subscribers should provide only information that is useful and appropriate for the requested task.
Select:
Generate
to start the request.
While the response is being produced:
Generating...
appears on the button.
The shared Generate button remains disabled until the Input contains non-whitespace text.
While typing in the Input field:
Ctrl + Enter
can submit the request.
If generation is attempted without useful Input, the current message is:
Input required
with:
Please enter a prompt to continue.
Each current Health & Wellness Tool provides three built-in examples.
Selecting an example fills the Prompt field.
After selecting an example, the subscriber must still:
The shared Standard ToolPage instructs the AI:
“You are a helpful AI assistant for the tool: [Tool Title]. [Tool Description]”
and passes the subscriber's Input as the Prompt.
The shared request also passes the individual Health & Wellness Tool ID.
symptom-journal
meal-plan
workout-routine
The shared ToolPage reads the subscriber's selected AI Model through the authenticated user context.
The shared AI streaming system also obtains the subscriber's configured provider API Keys.
Configured non-empty provider Keys can be sent through provider-specific request headers such as:
x-provider-key-[provider].
Changing the selected Model can change:
Important content should therefore be reviewed rather than assumed to be identical across Models.
The right-side Card is:
Output
Before generation:
Generated content will appear here.
Content appears progressively while the Model generates the response.
Completed Output is displayed using AIUNIFY's Markdown renderer.
This can support:
depending on the response.
When Output exists, a Copy action is displayed.
Copy places the current generated content on the Clipboard.
Current notification:
Copied!
with:
Content copied to clipboard.
Standard ToolPage provides a Download action.
Current Download format:
.txt
Current pattern:
[tool-id]-output.txt
symptom-journal-output.txt
meal-plan-output.txt
workout-routine-output.txt
The three Standard Health & Wellness Tools do not provide a dedicated PDF export.
There is no native Microsoft Word export.
Symptom Journal does not export an EHR/EMR-compatible health record.
Meal Plan does not create a structured .xlsx Nutrition workbook.
Workout Builder does not export a native workout file to a connected fitness application.
The shared Reset control clears:
and returns focus to the Input Textarea.
There is no persistent Save button on these pages.
There is no source-verified generation History for previous:
Standard ToolPage does not provide:
Copy or Download any result you want to keep before Resetting or generating a replacement.
Standard ToolPage calculates its Base Cost using:
The Header displays:
[cost] tokens per use.
The subscriber's current balance is also displayed.
When the selected Model is categorized as OpenAI, Standard ToolPage applies its current:
1.5× Base Cost
display multiplier, rounded upward.
If the live interface shows a different Token Cost from this manual, use the live amount.
| ToolRoute ReferenceFeature CatalogueCurrent Standard Default | |||
| Symptom Journal | 15 | 20 | 20 unless live override |
| Meal Plan | 20 | 20 | 20 |
| Workout Builder | 15 | 20 | 20 unless live override |
The individual Routes define 15 Tokens for Symptom Journal, 20 for Meal Plan, and 15 for Workout Routine.
The synchronized feature catalogue lists all three at 20 Tokens.
Symptom Journal's Route provides:
15 Tokens
but the feature catalogue provides:
20 Tokens.
Because Standard ToolPage gives the feature catalogue higher priority than the Route fallback, the current default Base Reference is:
20 Tokens
unless a live AI Limit overrides it.
Both Route and feature catalogue currently reference:
20 Tokens.
Workout Routine's Route supplies:
15 Tokens
while the feature catalogue supplies:
20 Tokens.
The current default Base Reference is therefore:
20 Tokens
unless a live Tool setting overrides it.
Navigate to:
Sidebar → Health & Wellness → Symptom Journal
Route:
/symptom-journal
The workspace title is:
Symptom Journal Analyzer.
Current description:
Analyze health symptom patterns, identify potential triggers, and generate structured health journals for doctor visits.
Current guidance:
Describe your symptoms, their frequency, duration, and any potential triggers you've noticed...
Built-in example:
Analyze these headache patterns: Mon-morning, Wed-afternoon, Fri-morning — possible triggers and patterns.
Built-in example:
Track and organize these digestive symptoms over the past week with meals and stress levels.
Built-in example:
Create a structured symptom report for my doctor: fatigue, joint pain, sleep issues over 2 weeks.
Describe what was experienced.
If known, state when the symptom began.
Useful information can include:
Describe how long an episode lasts.
Patterns can sometimes be easier to review when the time is included.
If useful, describe severity consistently.
For example:
or a numerical scale you define.
If relevant, describe where the symptom occurs.
Useful surrounding context may include:
when relevant.
The placeholder explicitly invites subscribers to describe:
potential triggers you've noticed.
Describe whether symptoms are:
When several symptoms occur together, explain their relationship and timing as clearly as possible.
The Tool is designed to help identify possible patterns in supplied text.
The Tool description allows AI-generated discussion of:
potential triggers.
The Model is generating possible relationships from the subscriber's written information.
It is not testing or confirming biological causation.
The AI can compare episodes against:
when those facts are supplied.
The AI can organize related symptoms into a more readable narrative.
If a timeline is supplied, the Model can summarize changes over time.
The Tool description explicitly states that it can generate:
structured health journals for doctor visits.
A generated report may be prompted to include:
A concise chronology can help subscribers communicate what they have observed.
The Output is AI-generated plain text.
It does not become an official clinical record merely because it is taken to a healthcare visit.
The Tool does not automatically send the generated report to a healthcare professional.
There is no source-verified connection to:
The Tool does not write directly into an Electronic Health Record.
The source does not establish a dedicated diagnostic engine.
The Tool cannot perform:
through this page.
The page's stated purpose is pattern analysis, potential Trigger identification, and structured journaling.
It should not be documented as a diagnostic decision-support system.
There is no source-verified medication interaction checker.
There is no dedicated clinical allergy-validation engine.
The page is not a structured laboratory-result analyzer.
The current source does not establish a dedicated emergency-triage workflow.
The Tool does not collect live:
There is no source-verified connection to:
Symptom Journal Analyzer uses Standard ToolPage.
There is no day-by-day Symptom calendar.
The Tool does not save each episode as a structured record.
There is no built-in trend Chart.
Previous analyses are not automatically available for comparison.
The Tool does not remind the subscriber to log symptoms.
There is no medication-management function.
The Tool does not book a healthcare visit.
A stronger Prompt separates:
What happened
from:
What you think caused it.
Specific timestamps can make patterns easier to organize.
If tracking over multiple days, use the same scale.
For example:
Headache 7/10, 9:00 AM, slept 5 hours, skipped breakfast.
Provide context relevant to the symptoms being reviewed.
Download or Copy the result if you intend to refer to it later.
Potential medical meaning should be considered with appropriate clinical judgment rather than treated as established by AI.
Navigate to:
Sidebar → Health & Wellness → Meal Plan
Route:
/meal-plan
Meal Plan Generator.
Current description:
Create personalized meal plans with recipes, macro breakdowns, grocery lists, and dietary restriction support.
Current guidance:
Describe your dietary goals, restrictions, calorie target, and preferences...
Current Route and Catalogue Reference:
20 Tokens
subject to live configuration.
Built-in example:
Create a 7-day 2000-calorie vegetarian meal plan with grocery list and macro breakdown.
Built-in example:
Generate a high-protein meal prep plan for 5 workdays under $50 budget.
Built-in example:
Build a gluten-free, dairy-free meal plan for a family of 4 with kid-friendly options.
Describe the intended Meal Plan purpose.
Examples can include:
The placeholder specifically asks for:
restrictions.
The placeholder also asks for a:
calorie target.
There is no dedicated numeric field; state it in natural language.
Describe preferred:
There is no Duration selector.
State:
in the Prompt.
Family size must be stated in the Prompt.
If the number of meals matters, state it explicitly.
Specify whether Snacks should be included.
The built-in high-protein example confirms that Budget constraints can be included.
You can ask for:
If meal-preparation time matters, include a desired maximum.
You can state limitations such as:
You can request the Output by:
Ask for Breakfast entries if needed.
Include Lunch requirements.
Include Dinner requirements.
Include Snack recommendations if desired.
You can ask for portion suggestions in the generated Plan.
The Tool description explicitly includes:
recipes.
The description also includes:
grocery lists.
The source description and first example explicitly support:
macro breakdowns.
The Tool sends the natural-language Prompt to the selected AI Model through Standard ToolPage.
The current page does not establish a connection to a verified nutrient database.
The interface does not independently calculate calories from Ingredient weights.
Protein, carbohydrate, and fat values can be generated by AI, but the page does not source-verify an independent Macro calculation engine.
Generated Macro breakdowns should therefore be reviewed if exact nutritional values matter.
A Meal Plan labeled:
2000 calories
should not automatically be assumed to equal exactly 2,000 calories when independently calculated from actual Product quantities.
Actual nutritional values can vary by:
If serving sizes change, total calories and Macros can change.
The Tool description explicitly states:
dietary restriction support.
The first example specifically supports Vegetarian Meal Planning.
The third example specifically supports a Gluten-Free request.
The same example specifically supports Dairy-Free planning.
Because the Tool uses natural-language Input, multiple requirements can be supplied together.
A generated Plan labeled Gluten-Free or Dairy-Free should still be checked against the actual ingredients and Product labels.
An AI-generated Plan should not be treated as a substitute for verifying the actual contents of Foods when an allergy is involved.
The source explicitly identifies Grocery Lists as an intended Meal Plan output.
The generated Grocery List appears within the Standard Output.
There is no dedicated interactive shopping-list interface.
The Tool does not add Products to an online Grocery cart.
There is no source-verified connection to a grocery retailer.
A Budget-oriented Meal Plan does not establish live local Grocery prices.
Actual cost can vary by:
The Tool does not maintain a persistent nutrition profile containing:
The current Tool does not calculate a calorie target before generation.
Subscribers provide the target themselves when desired.
There is no source-verified Basal Metabolic Rate calculator in this page.
There is no dedicated Total Daily Energy Expenditure calculator.
The Tool does not maintain Weight history.
There is no blood-glucose integration.
Subscribers do not check off or log Meals consumed.
There is no persistent Nutrition tracking Dashboard.
Be specific about planning horizon.
This helps make the generated Grocery quantities more relevant.
Place important restrictions near the beginning of the Prompt.
If there are ingredients you do not want, include them.
Budget constraints can make suggestions more practical.
Examples:
You can request one consolidated Grocery List for the entire Plan.
For efficiency, ask the AI to reuse ingredients or planned leftovers.
When exact calorie or Macro targets matter, calculate against actual Foods and quantities.
Navigate to:
Sidebar → Health & Wellness → Workout Builder
Route:
/workout-routine
The page title is:
Workout Routine Builder.
Current description:
Design personalized exercise programs with exercises, sets, reps, rest times, and progressive overload schedules.
Current guidance:
Describe your fitness level, goals, available equipment, and how many days per week...
Built-in example:
Create a 4-day upper/lower strength training split for intermediate lifters with barbell access.
Built-in example:
Design a 3-day full-body home workout routine using only bodyweight and resistance bands.
Built-in example:
Build a 6-week progressive running plan for a beginner training for a 5K race.
The placeholder explicitly asks for:
fitness level.
Subscribers can describe themselves as:
where appropriate.
State the training objective.
Examples can include:
The placeholder explicitly requests:
available equipment.
Specify how many days per week are available.
If relevant, state:
or another time limit.
Useful context can include:
Provide relevant experience when it changes program complexity.
The description explicitly supports generating Exercise selections.
It also supports:
sets.
It supports:
reps.
It supports:
rest times.
The Tool description explicitly includes:
progressive overload schedules.
The Tool can generate a day-by-day routine as text.
You can ask the Model to specify recommended Exercise order.
You can request a Warm-Up section.
You can request a Cool-Down section.
Ask for week-to-week progression rules.
The first built-in example verifies Upper/Lower strength split generation as an intended use.
The second example verifies Full-Body programming.
Barbell access can be specified.
The Home example confirms Bodyweight-only programming can be requested.
Resistance Bands are explicitly represented in the same built-in example.
The third built-in example requests a progressive Running plan.
The example specifically requests:
6 weeks.
The source verifies Beginner Running-plan generation as an intended use case.
The example specifically uses a:
5K race.
If pace matters, include current or desired pacing context in the Prompt.
Subscribers can request a Run/Walk format through natural-language Prompting.
The Tool is explicitly positioned to create:
progressive overload schedules.
The page does not measure the subscriber's actual performance automatically.
The Tool does not know whether the subscriber completed the recommended Sets or Reps unless that information is supplied in a later Prompt.
There is no persistent Workout log.
The Tool does not source-verify measuring a one-repetition maximum.
There is no bar-speed or velocity sensor integration.
Workout Routine Builder cannot directly evaluate:
The Tool cannot examine an injury.
There is no Camera-based movement assessment in this page.
The page does not retrieve live Heart Rate.
Running distance is not recorded automatically.
There is no source-verified integration with:
The current Standard Output is text-based.
A generated Exercise description does not guarantee correct movement execution.
The Tool does not determine whether an individual is medically cleared for exercise.
The Tool does not save:
as a persistent Workout profile.
The Routine does not change automatically after each Workout.
There are no completion checkboxes.
The Tool does not calculate persistent Training Volume from completed sessions.
There is no PR history.
The page does not provide a Workout Rest Timer.
The Tool does not automatically schedule sessions.
Workout Builder does not send exercise reminders.
This helps prevent overly complex programming.
Do not allow the Plan to assume access to equipment you do not have.
Give the realistic number of training days available.
This helps control session length.
A Routine designed for running a 5K is different from one designed around strength.
Request clear rules for increasing:
where appropriate.
If equipment or movement options are limited, request substitutions.
Make sure the generated Plan is appropriate to your actual capabilities and context.
| CapabilitySymptom JournalMeal PlanWorkout Builder | |||
| Standard ToolPage | Yes | Yes | Yes |
| Prompt Input | Yes | Yes | Yes |
| Examples | Yes | Yes | Yes |
| Streaming Output | Yes | Yes | Yes |
| Copy | Yes | Yes | Yes |
| TXT Download | Yes | Yes | Yes |
| Direct Edit | No | No | No |
| Save | No | No | No |
| History | No | No | No |
| Selected Model | Yes | Yes | Yes |
| Provider API-Key pathway | Yes | Yes | Yes |
| FunctionCurrent Support | |
| Organize symptom descriptions | Yes |
| Generate possible pattern/Trigger ideas | Yes |
| Produce structured doctor-visit summary | Yes |
| Diagnose disease | No |
| Generate Meal Plan text | Yes |
| Generate Grocery List text | Yes |
| Generate Macro-oriented estimates | Yes |
| Calculate clinically verified Nutrition | No |
| Generate Workout Routine text | Yes |
| Generate Sets/Reps/Rest structure | Yes |
| Generate progression suggestions | Yes |
| Track actual Workouts | No |
| Measure physical performance | No |
| External SystemDirect Connection Verified? | |
| Electronic Health Record | No |
| Patient Portal | No |
| Pharmacy System | No |
| Apple Health | No |
| Apple Watch | No |
| Fitbit | No |
| Garmin | No |
| Food/Nutrition database | No |
| Grocery retailer | No |
| Fitness tracking service | No |
Enter non-whitespace Input.
Provide more relevant details.
Standard ToolPage does not provide direct Output editing.
Copy or Download the result.
There is no persistent Save action.
No generation History is source-verified.
This is the current Standard ToolPage behavior.
Add:
Treat generated Trigger suggestions as possibilities.
Remove unsupported assumptions and regenerate with more accurate context.
Symptom Journal Analyzer is not source-verified as a diagnostic system.
Its stated purpose is:
Explicitly request sections such as:
The current Tool does not render a persistent symptom Trend Chart.
There is no built-in logging calendar.
Maintain the observations externally and paste the relevant timeline when analysis is needed.
Restate important restrictions clearly and regenerate.
The page does not use a source-verified deterministic Nutrition calculator.
Verify important values against actual ingredients and serving sizes.
The same limitation applies to generated Macro values.
The Tool does not retrieve live Grocery pricing.
Generated Budget estimates can differ from local actual prices.
State the actual number of people/servings and regenerate.
Include:
where relevant.
No Grocery-app integration is source-verified.
This is consistent with the current source.
workout-routine a 20-Token value, and Standard ToolPage prioritizes the catalogue over the Route fallback.The same source behavior applies to Symptom Journal.
List the exact available equipment and regenerate.
Explicitly state your training experience and ask for an appropriate level.
The source includes a built-in Bodyweight + Resistance Band home-workout example.
Use similar context.
Specify:
The Tool generates Workout text; it does not include a Training Log.
There is no interactive Rest Timer in this workspace.
Consider whether every personal detail is necessary before submitting it.
For many requests, useful context can be provided without:
No Health & Wellness Tool needs a Password inside the Prompt.
AI provider Keys belong in the dedicated API-Key configuration workflow.
Only provide medical-record information that is necessary and appropriate for the intended task.
Avoid unnecessary identifiable information about other individuals.
A subscriber could manually use observations from a Symptom Journal to inform questions they want to consider while planning meals.
There is no automatic data transfer between the Tools.
A subscriber can use the two Tools in parallel when organizing a general wellness routine.
The Tools do not automatically coordinate calorie or training calculations.
A subscriber can manually record how they felt around exercise sessions and later provide those observations to Symptom Journal.
No automatic fitness-to-symptom synchronization exists.
The three Tools do not share a persistent Health & Wellness profile.
Record what actually happened.
Include:
Use Symptom Journal Analyzer to organize the observations.
Check that the AI did not introduce facts you did not provide.
Keep observed facts distinct from AI-generated hypotheses.
Copy or Download the useful summary.
Use the organized information in the appropriate health decision or professional conversation where needed.
State what the Plan should accomplish.
List required exclusions and preferences.
State number of days.
State the number of people.
Supply targets explicitly rather than expecting the Tool to determine them.
Create the first Meal Plan.
Check every Meal.
Calculate against actual Foods when precision matters.
Remove unnecessary duplication and adjust quantities.
Use the approved Plan in your actual Grocery and Meal-preparation workflow.
Describe your current experience.
Identify what the Program should accomplish.
List available resources.
State training days.
Example:
6 weeks
Create the Routine.
Check:
Modify the Plan to match actual capabilities, scheduling, and relevant limitations.
Because the Tool does not maintain Workout history, record completed sessions in the system of your choice.
Provide updated goals or context when requesting a revised Routine.
Symptom Journal Analyzer currently supports:
It does not establish:
Meal Plan Generator currently supports:
It does not establish:
Workout Routine Builder currently supports:
It does not establish:
The current effective Standard ToolPage references are:
AIUNIFY PROS SUITE currently exposes three active Health & Wellness Tools:
All three are marked New in the current Sidebar.
There is no specialized Health & Wellness workspace in the current subscriber source.
All three use:
Input → Generate → Streaming Markdown Output → Copy → TXT Download
The Sidebar's Symptom Journal opens:
Symptom Journal Analyzer.
Its stated purpose is to:
Its built-in examples include:
The current Tool does not establish a medical-diagnosis, clinical examination, EHR, wearable, or persistent symptom-tracking system.
Meal Plan Generator is designed to create personalized Plans containing:
Its examples include:
The current source does not establish a deterministic Nutrition database or verified calorie/Macro calculation engine, so important nutritional values should be checked against actual Foods and quantities.
Workout Builder opens:
Workout Routine Builder.
Its description explicitly supports:
and its examples include:
The current Tool does not track completed Workouts, measure technique, connect to wearables, or automatically adapt the Program from actual performance.
The individual Route values are:
while the synchronized feature catalogue lists all three at:
20 Tokens.
Because Standard ToolPage resolves:
Live AI Limit → Feature Catalogue → Route Fallback
the current default Base Reference for all three is 20 Tokens unless a live Tool setting overrides it.
The central operating principle for Chapter 45 is:
AIUNIFY PROS SUITE Health & Wellness Tools help subscribers organize symptom observations, generate Meal Plans, and develop Workout Routine ideas. They are AI-assisted planning and information tools—not substitutes for the medical assessment, verified nutritional calculation, physical evaluation, real-world monitoring, or professional judgment needed when health or safety depends on the result.