Never blank in the doctor’s office again
You walk in with an organized symptom timeline and question list, and walk out actually understanding what was said.
The problem
You leave appointments having forgotten half your questions, then puzzle over jargon in the after-visit notes.
What you get
A working system with the steps, tools, checkpoints, and expected return made explicit.
- Setup
- 15 minutes
- Back each week
- 0.5 hours
- Difficulty
- starter
Expected return
The working case
A planning estimate, not a guaranteed result. Measure the first four weeks against your own baseline.
24
hours returned per year
At 0.5 hours/week across 48 working weeks.
1
week to earn back setup
Compare the setup estimate with the weekly time returned.
Operating contract
Input
The source material, constraints, and examples a human would need to do this work well.
Checkpoint
A person reviews judgment calls, sensitive content, unfamiliar tools, and irreversible actions.
Success signal
Track time returned, corrections required, and exceptions. Keep it only if the measured result compounds.
The steps
- 01
Before: organize the visit.
Copy this prompt
I have a doctor’s appointment about [issue]. Symptoms and history, messy: [dump everything with rough dates]. Organize into: 1) a clear timeline, 2) the questions worth asking given limited time, ordered by importance, 3) what information the doctor will likely want that I should have ready.
- 02
After: paste the visit summary or notes and ask for a plain-language explanation and a list of follow-ups you are responsible for.
- 03
Keep one running health-notes document per family member; paste each visit’s summary into it so the timeline builds.
What it runs on
- Claude
Prep and translation; it will say clearly it is not a doctor.
Where this goes wrong
- Symptom-checking is preparation, not diagnosis; alarming possibilities from AI are questions for the doctor, not conclusions.
- Health data is sensitive; use first names only and consider what you are comfortable having in any chat history.
Definition of done
Run it for four weeks. Then make it earn its place.
- □ Baseline the manual time before launch.
- □ Keep a human approval step for consequential output.
- □ Record corrections and exceptions, not just successes.
- □ Expand, revise, or retire it after the first review.
Build the system around it
Related workflows
If this one stops working, tell us. Three reports in a month and it leaves the library until a person has looked at it again.