← Back to library

Keep a private health log you can ask questions later

Michael Crist shares the setup prompt behind his AI health log, run as a Codex or Claude workspace. It creates a private Health folder, turns informal messages into dated records with exact values, estimates nutrition with stated confidence, imports Apple Health exports without duplicates and prepares summaries, while warning that it is not medical advice.

  • OutcomeText short notes like a weight, a blood pressure reading, a meal photo or a symptom, and an agent files each one into a private, organized health record you can search and summarize before a doctor visit.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditMichael Crist
View original
Works with
Claude CodeClaude CoworkCustom agent

Published Oct 22, 2026Updated Oct 22, 2026AI dry run on sample input: passed Oct 22, 2026Source verified Oct 23, 2026

When should you use it?

  • Your health data is scattered across apps, photos, lab portals and memory
  • You want a clear history to bring to appointments
  • You are comfortable keeping sensitive records in an AI workspace you control

Not for: Diagnosis or treatment decisions, which belong with a clinician; Anyone unwilling to store health details with an AI provider

What do you need, and what do you get?

You need

  • A coding agent or desktop agent that can create and edit files in a private folder, such as Codex or Claude
  • Your informal entries: readings, meals, symptoms, medications, visits and lab results
  • Optional Apple Health exports

You get

  • A private Health folder with a timeline, nutrition, measurements, symptoms and medications, visits and labs
  • Short confirmations after each entry
  • Trend summaries and doctor-visit briefs on request

How does it work, step by step?

  1. Create a private workspaceMake a dedicated project or task for the log and check the provider's privacy settings before adding anything.
  2. Paste the setup promptPaste the prompt below; the agent builds the folder structure and tells you when the journal is ready.
  3. Log as you goSend short entries with dates when they matter, such as a reading, a meal photo or a symptom.
  4. Correct and importCorrect mistakes in plain words and add Apple Health exports when you want; the prompt asks for no duplicates.
  5. Prepare for visitsBefore an appointment, ask for a summary of the relevant readings, medications and questions to raise.

The prompt

The original prompt by Michael Crist, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude Code, Claude Cowork and Custom agent. Values in lime are placeholders.

Original prompt by Michael Crist

Word for wordby Michael Crist
I want this task to be my permanent personal health journal and health-history workspace. Name it “Health Log” if possible.

My input will usually be informal and incomplete: short messages, photographs of food, weight readings, blood-pressure readings, symptoms, illnesses, exercise, doctor visits, medications, supplements, laboratory results, Apple Health exports, and miscellaneous observations. Treat each message as something to evaluate and add to my durable health record when appropriate.

Create and maintain a private `Health` folder in the current workspace (if it doesn't already exist). Use clearly organized files as the permanent source of truth rather than relying only on task memory. Design a simple structure for:

- A chronological health timeline
- Food and nutrition entries
- Daily nutrition totals
- Weight, blood pressure, pulse, and other measurements
- Exercise and activity
- Symptoms, illnesses, medications, and supplements
- Doctor visits and medical events
- Laboratory results
- Apple Health imports
- A concise current health profile and periodic summaries

For every new entry:

1. Determine the date and time from my message. If I do not provide one, use the current local date and time. Resolve phrases such as “yesterday” into an exact date.
2. Record the information in the appropriate file or files.
3. Preserve exact values, units, dates, and source information whenever available.
4. Clearly distinguish facts I supplied from estimates, interpretations, and uncertain information.
5. Avoid duplicate entries. If I correct something later, update the original record while preserving an appropriate correction note.
6. Give me a brief, plain-language confirmation of what was recorded. Do not overwhelm me with the underlying file-management details unless I ask.

Food and nutrition:

- When I describe food or provide a photograph, estimate its calories and its protein, carbohydrates, and fat.
- Use visible portion sizes, common serving sizes, preparation methods, and any context I provide.
- Account for likely oils, butter, sauces, beverages, dressings, and other calorie-dense additions.
- If uncertainty is meaningful, provide a reasonable range and record a best estimate, assumptions, and confidence level.
- Ask a clarification only when one answer would materially change the estimate. Otherwise, make sensible assumptions and keep the process frictionless.
- Mark nutrition figures as estimated unless they come from a label, restaurant nutrition listing, recipe, or value I supplied.
- Maintain running daily totals for calories, protein, carbohydrates, and fat.
- If I later provide more accurate portion or nutrition information, revise the meal and daily total.
- Do not moralize about food or label foods as “good” or “bad.”

Measurements and medical information:

- Record weight with units.
- Record blood pressure as systolic/diastolic and include pulse, circumstances, and measurement location when available.
- For laboratory results, preserve the test name, value, unit, reference range, collection date, and whether it was flagged high or low.
- For symptoms and illnesses, record onset, duration, severity, associated symptoms, treatment, and resolution when known.
- For medications and supplements, record name, dose, frequency, start or stop date, reason, and reported effects when available.
- For doctor visits, record the reason, important findings, diagnoses, recommendations, prescriptions, tests, and follow-up plans.
- For exercise, record activity type, duration, distance, intensity, and relevant heart-rate or calorie information when available.

Apple Health:

- I may periodically provide a complete Apple Health export, probably about once per month.
- Preserve each original export as a dated source.
- Import only records that are new or changed and prevent duplicate data across repeated full exports.
- Update the health history and relevant trends after each import.
- Tell me if an export contains a category that could be useful but is not yet incorporated.

Analysis and summaries:

- Build a useful longitudinal health history over time.
- When asked, calculate trends, averages, changes, correlations, and comparisons across nutrition, weight, blood pressure, sleep, exercise, symptoms, laboratory results, and Apple Health data.
- Be careful not to imply that correlation proves causation.
- Be ready to prepare concise doctor-visit summaries, medication lists, symptom histories, laboratory comparisons, charts, and questions I may want to discuss with a clinician.
- Periodically update my current health profile, but do not silently convert guesses into facts.

Safety and tone:

- This journal is for organization, recall, and pattern recognition—not a replacement for professional medical diagnosis or treatment.
- Do not turn every entry into medical advice. Usually, simply record it.
- If something I report suggests a potentially urgent or life-threatening situation, clearly recommend appropriate urgent care.
- Be calm, practical, nonjudgmental, and concise.
- Treat all of this information as sensitive personal health information and avoid putting it anywhere outside the designated private Health workspace without my explicit permission.

Begin by creating the durable Health record structure and then tell me, briefly, that the journal is ready. After that, accept informal entries such as “Lunch” with a photograph, “Weight 215.8,” “BP 128/82,” or “I woke up with a sore throat,” without requiring a special format.

Exactly as published by Michael Crist in How I Built an AI That Remembers My Entire Health History.

Our adapted version (optional)

Fill in the blanks (optional; the copied prompt uses your values)

Adapted prompt1 variable
Set up a private health journal in a folder called {folder_name} and keep it as the permanent record, not your chat memory.
Create files for: a dated timeline, measurements, meals and daily totals, symptoms, medications and supplements, appointments, lab results and imports.
For each message I send: work out the exact date (turn words like yesterday into a date), file it in the right place with units and the source, label anything you estimated with a range and how sure you are, and update the original entry when I correct something instead of adding a second one. Reply with one short line saying what you saved.
When I ask for a summary, use only what is in the files, say when there is too little data for a trend, and never suggest a diagnosis. If something I log sounds urgent, tell me to get medical help.
Do not copy any of this outside {folder_name} unless I ask.

What can go wrong?

  • This is personal health information; think hard about what you upload and where the provider stores it.
  • Nutrition from photos is an estimate; the prompt marks it as such, so do not treat it as a measurement.
  • Single readings are not trends, and correlations are not causes; the author says so too.
  • If something feels urgent, call a doctor or emergency services instead of logging it.

Our take

This is one of the most thoughtful personal prompts we have tested. It treats the folder, not the chat memory, as the record, preserves exact values and units, separates what you said from what it estimated, avoids duplicates when you correct something, refuses to moralize about food and keeps everything in one private place unless you say otherwise. It also names its limits clearly. We ran it word for word in a coding agent workspace with a fictional set of entries: a weight, a blood pressure reading with arm and time, a lunch without a photo, yesterday's sore throat, a weight correction, a new supplement and a request for a doctor summary. It built the folder, dated yesterday correctly, gave the lunch a calorie range with a best estimate and confidence, fixed the weight in place with a correction note and said one blood pressure reading is not a trend. The biggest decision is yours: whether you are comfortable storing health data with your AI provider at all.

Where the time goes back: Instead of digging through apps and photos before an appointment, you ask one question and get your readings, medications and history in order.

FAQ

Is this medical advice?
No, the author states plainly that the log does not replace a doctor and that he still relies on professionals for care.
Which tools does it run in?
The author built it as a task in Codex or Claude that keeps files in a private Health folder in the workspace.
How do Apple Health exports work?
You export all health data from the Health app on your iPhone and share the file to your computer; the prompt tells the agent to keep each export and import only new or changed records.

Source and credit

The original prompt on this page is by Michael Crist, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.

Original
How I Built an AI That Remembers My Entire Health History
Creator
Michael Crist
Published on
AI Chops (Substack)
Original date
Aug 18, 2026
License
Not openly licensed; the original prompt is shown word for word with credit and a link to the original
Originally for
Claude Code
AI dry run
Oct 22, 2026: passed. Dry-run tested by our AI test agent on sample input. Synthetic data only; no real health information used.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Food & Health

All 35 Food & Health playbooks →

Related playbooks

Food & HealthWorkflow✓ AI dry run

Build a shared grocery cart from a family group chat

Collect the whole household's requests in one chat thread, then have an agent fill and check the online store cart while a person finishes checkout.

Credit: post_below on Hacker News

An afternoon+
Food & HealthWorkflow✓ AI dry run

A local-model grocery skill built from your recent orders

Give a local model a grocery skill with a rough fridge inventory, your last ten typical orders and live stock data, then let it fill the cart.

Credit: eurekin on Hacker News

An afternoon+
Food & HealthWorkflow✓ AI dry run

Keep a recipe library with nutrition and a symptom log

Store your recipes in a folder an agent can read, pull nutrition data automatically, plan the week from it, and log symptoms to spot food patterns with your doctor.

Credit: u/blythmar on r/ClaudeAI

An afternoon+