When should you use it?
- A relative sees several specialists
- Medication lists keep changing
- Nobody seems to have the whole picture
Not for: Changing any medication without a clinician; Replacing medical advice
What do you need, and what do you get?
You need
- Records and visit notes from each provider
- Current medication list
- Test results
You get
- Dated history across providers
- Flagged conflicts with sources
- Questions for the next appointment
How does it work, step by step?
- Collect recordsRequest notes and results from every provider and keep them in one folder.
- Build a timelineHave the assistant list visits, tests and medication changes in date order.
- Check for conflictsAsk it to flag doses, schedules or facts that disagree across records.
- Turn flags into questionsWrite clear questions with the supporting record for the care team.
- Share at the next appointmentShare the summary and let clinicians decide.
The prompt
Our own prompt, inspired by light_hue_1 on Hacker News and written to work in Claude, ChatGPT and Gemini. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here are records for {patient} from several providers: {records} Build a dated timeline of visits, tests and medication changes. Flag any dose, schedule or fact that differs between records, citing each source. Turn each flag into a neutral question for the care team. Do not recommend treatment changes.
Inspired by light_hue_1 on Hacker News: Hacker News comment on an AI coordinating a relative's cancer care. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Assistants can misread clinical notes; every flag is a question, not a conclusion.
- Health data is sensitive; use a service and settings you trust.
Our take
This is a painful story and an important one. Fragmented care meant no single clinician saw everything, and putting every record in one place to ask for inconsistencies found real errors. Frame outputs as questions for clinicians, not as orders to change care. Request notes and results from every provider and keep them in one folder, then have the assistant build a timeline of visits, tests and medication changes. Ask it to flag doses, schedules or facts that disagree across records, and turn each flag into a clear question with the supporting record attached. Assistants can misread clinical notes, so treat every flag as a question, not a conclusion. Bring the summary to the next appointment and let the care team decide. Never change a medication based on the assistant's output. Health records are sensitive, so choose a service and privacy settings you trust. Keep the folder updated after every visit so the timeline stays useful.
Where the time goes back: Scattered records become one timeline, so errors can be spotted and raised at the next visit.
FAQ
Can the assistant change treatment?
How did doctors react?
Source and credit
Inspired by light_hue_1 on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Hacker News comment on an AI coordinating a relative's cancer care
- Creator
- light_hue_1 on Hacker News
- Published on
- Hacker News
- Original date
- Oct 15, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- 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 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.