When should you use it?
- You have a condition that comes and goes
- Your watch or band has logged several years
- Your episodes have known dates
Not for: Diagnosing a condition you do not have confirmed; Replacing lab tests or your specialist
What do you need, and what do you get?
You need
- Wearable exports
- Dates of past episodes
- Lab dates and results
You get
- Trained model and validation report
- Backtest on past episodes
- Simple alert or app view
How does it work, step by step?
- Export everythingDownload the full history from each device into one folder.
- Label past episodesMark start and end dates from your records or lab results.
- Compare modelsHave the agent train several models and report results on data held out by time, not shuffled.
- BacktestCheck when it would have warned you before each past episode, and how often it raised false alarms.
- Alert, then confirmSend yourself a heads-up and take it to your doctor for a lab check.
The prompt
Our own prompt, inspired by u/ThatAi_guy on r/ClaudeAI and written to work in Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Data: {wearable_exports}. Past episodes (start, end): {episodes}. Build features from resting heart rate, HRV, sleep and activity. Train at least 4 model types. Validate on a time-based holdout (most recent {holdout_months} months), not shuffled data. Report: precision, recall, false alarms per month, and how many days before each past episode the model would have warned. Explain limits plainly.
Inspired by u/ThatAi_guy on r/ClaudeAI: I Gave Claude Code 9.5 Years of Health Data to Help Manage My Thyroid Disease. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Shuffled validation on time-series data inflates accuracy; hold out the most recent period.
- Few labeled episodes means the model can overfit; watch false alarms.
Our take
This is among the strongest personal health-data projects in the pool: a narrow question, labeled history from the person's own records, and a backtest against real episodes. Insist on time-based validation so future leaks do not inflate accuracy. Treat alerts as reasons to contact a clinician, not as diagnoses. Share methods with your doctor if you rely on alerts. Export the full history from each device into one folder and label past episodes with start and end dates from your records or lab results. Have the agent compare several models on data held out by time, not shuffled, and backtest when each would have warned you and how often it raised false alarms. Few labeled episodes means the model can overfit. Use alerts as a prompt for a lab check with your doctor, and never use this to diagnose a condition you do not have confirmed. Share the method with your specialist if you rely on it.
Where the time goes back: Instead of noticing an episode once symptoms hit, you get a prompt to book a lab check earlier.
FAQ
Is 98% accuracy reliable?
Can I share the model?
Source and credit
Inspired by u/ThatAi_guy on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Gave Claude Code 9.5 Years of Health Data to Help Manage My Thyroid Disease
- Creator
- u/ThatAi_guy on r/ClaudeAI
- Published on
- Original date
- Jan 20, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
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 24, 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.