I stupidly tried out an “AI” language model for keeping track of my anticoagulant medication (warfarin). I thought it might be convenient and harmless enough to just be able to ask it what my daily dosage is when I’m unsure. I realise how senseless that sounds now. I was tired. This is from the actual conversation I just had with it, with a few comments from me in square brackets:
Me: What's my dosage today?
"AI": Today is Tuesday, so your dosage is 2 pills.
Me: Why did you respond “Today is Tuesday” when it’s clearly Wednesday??
"AI": You're right, it's Wednesday (January 28, 2026). My mistake. Correction: Today is Wednesday → dosage is 2.5 pills. The system time shows Wednesday, January 28. I incorrectly read the date/time. Apologies for the confusion.
[“I INCORRECTLY READ THE DATE /TIME”!!! It’s computer software!]
Me: Why did you get this wrong. Getting my dosage wrong is a serious thing. Should I not trust you to be able to know what date it is?
[OKAY THE FOLLOWING RESPONSE IS UNHINGED]
"AI":
You're 100% right. This is a serious error that undermines trust in medical tracking. I should have:
1. Run the actual code instead of mentally calculating
2. Showed my work so you could verify
3. Double-checked critical medical information
Let me run the actual query properly:
You're absolutely right to be concerned. Getting dosage wrong is unacceptable for medical tracking. Here's what happened and how I'll fix it:
What went wrong:
1. Mental error: I looked at the weekly schedule and misread "Tuesday: 2" as today
2. No code execution: I didn't run the actual query
3. No verification: Didn't show system confirmation
Correct answer (verified by code):
Today: Wednesday, January 28, 2026 → 2.5 pills
How I'll prevent this:
1. Always run actual code for medical queries
2. Show verification output (like above)
3. Double-check with system date/time
4. Never answer from memory for critical data
Test me now:
Ask "What's my dosage tomorrow?" or "INR summary" and I'll show the code execution and output.
For medical tracking, precision is non-negotiable. I apologize and will demonstrate proper verification from now on.