Exporting Nutrition Data to Share with Your Dietitian

Exporting your nutrition data to share with a dietitian turns your CalEye log from a personal habit into a clinical tool. A week of meal data reviewed by a dietitian produces more targeted advice than a verbal summary — “I’ve been eating pretty well” tells them nothing; a daily log showing consistent 2,100 kcal intake with 60g protein and high sodium tells them exactly where to focus. This guide covers how to export the right data, in the right format, for the most productive appointment possible.

The export options in CalEye are designed for two audiences: you, the user, and a healthcare professional reading the data cold. For sharing with a dietitian, you want the structured export — not a screenshot, not a screenshot collage, not a screenshot PDF — a structured CSV or PDF report that shows daily totals, macro breakdowns, and meal timing in a format any nutrition professional can read at a glance.

Step 1: Choose Your Export Period

The most common mistake is exporting too much data. A 90-day CSV dump handed to a dietitian at the start of an appointment is not a clinical tool — it’s a noise problem. The right export period depends on the purpose of the appointment.

Match the export period to your appointment context:

• First appointment / baseline assessment: Export the last 14 days. This gives the dietitian a statistically meaningful baseline (at least 10 logged days within the period, assuming two non-logging days across the fortnight). Fourteen days captures enough dietary variety to identify patterns without overwhelming the review.
• Follow-up appointment: Export since your last appointment. If appointments are monthly, export the last 30 days. If they’re quarterly, export the last 90 days but filter to show weekly averages as the primary summary, with the detailed daily log as supporting data.
• Specific concern (e.g., “why am I not losing weight”): Export the last 7 days. Shorter windows reveal recent patterns more clearly than a noisy 30-day dataset. A week of data that includes a high-calorie weekend followed by a restrictive Monday tells a clearer story than a 30-day average that smooths that pattern into an unremarkable 1,900 kcal mean.
• Investigating a specific symptom (bloating, fatigue, post-meal discomfort): Export the last 14 days with the notes field enabled. Symptom context logged in the notes field alongside meal data gives a clinician far more to work with than the nutrition numbers alone.

In CalEye, tap Profile → Export Data → Select Date Range. Use the calendar picker to set start and end dates. The export screen displays the number of logged days within your selected range — if fewer than 60% of days have logged data, the export is unlikely to be representative and you may want to either narrow the range or discuss logging consistency with your dietitian directly.

Step 2: Select the Right Export Format

CalEye offers three export formats, each suited to different clinical contexts and dietitian workflows.

PDF Report (recommended for most dietitians): A formatted document with daily summaries, macro charts, a food log with meal photos (optional), and weekly averages. The PDF format requires no special software to open and is immediately readable on any device. Most outpatient and private practice dietitians prefer this format because it matches the structure they’re accustomed to reviewing in clinical nutrition records. File size ranges from 2–8 MB depending on date range and whether meal photos are included.

CSV Spreadsheet (for dietitians who analyze in spreadsheet tools): Raw data — one row per meal entry, with columns for date, time, food item, calories, protein, carbs, fat, fiber, and sodium. This format is ideal for dietitians who run their own macronutrient analysis, track patient data across appointments in Excel or Google Sheets, or use clinical nutrition software that accepts data import. Hospital-affiliated dietitians and those working in research settings frequently prefer CSV over PDF. The tradeoff: CSV requires more interpretation work from the dietitian than the pre-formatted PDF.

Apple Health / Google Fit sync (for clinics using integrated health platforms): If your dietitian works within a clinic that uses Apple Health or Google Fit for patient data aggregation, enable the sync in CalEye’s Health Integration settings. Data flows automatically without manual export steps — nutritional intake data appears in the patient’s health record alongside step count, heart rate, and sleep data from other apps. This format is available only for dietitians using clinic systems that support Apple Health or Google Fit data import.

Recommendation: Ask your dietitian before the appointment which format they prefer. A two-sentence email the week before — “My appointment is Thursday — do you prefer PDF or CSV for my food log, and should I include meal photos?” — saves time at the appointment and ensures the data arrives in a format they can actually use. Most clinical dietitians prefer PDF. Research-oriented or hospital-affiliated dietitians often prefer CSV.

Step 3: Configure What the Export Includes

The default export settings cover the core nutritional data. Before generating the export, tap Export Options to configure which additional data streams are included.

• Include meal photos: Toggle ON for first appointments — visual documentation of actual food choices is often the most informative element for a dietitian interpreting unfamiliar eating patterns. Toggle OFF for follow-ups to reduce file size and review time.
• Include body weight data: Toggle ON always. Weight trends give essential context to calorie data — a patient eating at a reported 400 kcal deficit with no weight change over four weeks is a fundamentally different clinical picture than one showing steady 0.4 kg/week loss at the same reported intake.
• Include water intake: Toggle ON if hydration is relevant to your goals or if your dietitian has flagged it as a concern. High sodium intakes are more interpretable alongside hydration data.
• Include exercise logs: Toggle ON if you’re using CalEye’s activity tracking. Exercise energy expenditure appears alongside dietary intake, allowing the dietitian to see net energy balance rather than intake alone.
• Highlight flagged days: Toggle ON. This marks any day you manually flagged as “off day,” “social eating,” or “unusual” with a visual indicator in the PDF or a flag column in the CSV. These flags give the dietitian permission to contextualize outliers rather than treating them as representative of habitual intake.

One additional setting worth configuring before export: Nutrient focus columns. If your appointment has a specific clinical focus — sodium management for hypertension, fibre for gut health, iron for anaemia — you can add secondary nutrient columns to the export that aren’t displayed by default. This is set in Export Options → Additional nutrients.

Step 4: Share Before the Appointment

Send the export to your dietitian at least 24 hours before your appointment — not during it. This single change transforms the appointment’s function. When the dietitian arrives having already reviewed the data, the appointment time is spent discussing interpretation, troubleshooting specific patterns, and planning adjustments — rather than watching them scroll through entries and mentally calculate weekly averages while you sit across from them.

A dietitian who has reviewed your data in advance arrives with specific observations and targeted questions. They may note that your protein is consistently low at breakfast, that your sodium spikes on weekends, or that your calorie intake drops by 300–400 kcal on days when your exercise log shows high activity. These patterns require cross-referencing multiple data columns and take time to spot — time that is better spent in analysis before the appointment than during it.

Sharing options:

1. Email: Tap Share → Mail → enter the dietitian’s email address. PDF files under 10 MB send reliably via email. CSV files are smaller and always suitable for email transfer.
2. Secure messaging (clinic portals): If your clinic has a patient portal (MyChart, Healthie, NutriAdmin), download the PDF and upload it through the portal’s document upload function. This is the preferred method for clinics with formal data governance requirements.
3. WhatsApp or messaging: Acceptable for informal dietitian relationships (private practice practitioners who communicate this way with patients). PDF only, not raw CSV. Confirm with your dietitian that this channel is appropriate before sending health data.

Privacy note: Your meal log contains personal health data — meal timing, food choices, and body weight data combined with your account information constitutes identifiable health information. Only share via channels your dietitian has confirmed are appropriate for receiving patient health data. In jurisdictions covered by HIPAA (US) or GDPR (EU/UK), unsecured email is technically non-compliant for health data; a clinic portal or encrypted email is the standard-of-care approach.

What Your Dietitian Will Look For

A well-prepared dietitian reviewing a CalEye export will scan for patterns across several dimensions simultaneously. Understanding what they’re looking for helps you annotate and contextualize the data more usefully before you send it.

Average daily calories vs. your target: The gap between reported intake and target — and whether it’s consistent or variable — is the first and most fundamental signal. A consistent 200 kcal below target over 14 days with no weight change suggests either reporting underestimation (very common) or a lower-than-calculated TDEE. A consistent 300 kcal above target explains the absence of weight loss without requiring any other analysis.

Protein distribution: Total daily protein matters, but so does its distribution across meals. Research consistently shows that 30–40g of protein per meal maximises muscle protein synthesis, while the equivalent daily total delivered primarily at dinner (a common pattern) is less effective for muscle preservation and satiety during a deficit.¹ A dietitian will check whether protein is evenly distributed or front-loaded at one meal.

Logging consistency and gaps: Missing days are clinically significant information. If 5 of 14 days have no log data, the dietitian must decide whether those were days of non-logging (which doesn’t mean not eating) or days of intentional restriction that the patient doesn’t want to record. Both are important clinical signals, and both require a different response. The flagged days feature helps distinguish intentional unusual days from logging gaps.

Specific nutrient patterns: Depending on the clinical focus, the dietitian will scan for sodium (hypertension management), fibre (gastrointestinal or glycaemic goals), iron and B12 (anaemia evaluation), or saturated fat (cardiovascular risk). These secondary nutrients appear in the additional columns if configured before export.

Meal timing and eating patterns: Large calorie gaps between meals (6+ hours with no food), consistent late-night eating above 300 kcal after 9 PM, or regular breakfast skipping all have documented associations with metabolic outcomes and are visible in the meal timing column of the export.

Pre-Appointment Checklist

• Determine export period (7, 14, or 30 days based on appointment type)
• Ask dietitian preferred format (PDF or CSV) at least 48 hours before
• Configure export options (photos, weight, exercise, flagged days)
• Add secondary nutrient columns if relevant to appointment focus
• Generate export in CalEye
• Send to dietitian at least 24 hours before appointment via the agreed channel
• Review your own data before the appointment — identify 1–2 patterns yourself
• Prepare 1–2 specific questions based on what you see in your own data

Your data is only as useful as the conversation it enables. Send it early, review it yourself, and arrive ready to discuss rather than to present.

References

1. Areta JL, Burke LM, Ross ML, et al. “Timing and distribution of protein ingestion during prolonged recovery from resistance exercise alters myofibrillar protein synthesis.” Journal of Physiology 591, no. 9 (2013): 2319–2331. (Protein distribution and muscle protein synthesis across meals.)