The previous four lessons are about what AI does badly. This one is about something different and less comfortable: what happens when it goes wrong and there are consequences.
Three things worth settling before you need them
1. AI is not a source
A source is something another person can open and check: the SmPC on the emc, the BNF, a clinical guideline, the Drug Tariff. A conversation with a model is not reproducible — ask the same question tomorrow and it may answer differently — and that disqualifies it as a source by definition, not out of distrust.
Which does not mean it is useless. It means its output has to be anchored to a real source before you use it, which is what lesson 3 was for.
2. What gets documented is the check, not the query
If an intervention ends up recorded — a medication review, a patient-facing report, a note on a compliance aid — what goes down is the source that supports it and what you decided. Not "checked with AI". And not to hide it: that detail simply tells nothing to whoever reads the record afterwards.
3. Delegating the writing is not delegating the content
That a text was written by an AI changes nothing: you are signing it. It is exactly like a notice written by a colleague you did not review. The difference is that you distrust the colleague by default and a well-written text, you do not — and that is the trap.
Where the line sits, in practice
| What the AI does | What stays yours |
|---|---|
| Draft the advice | That the advice is correct and applies to this person |
| Summarise a report | What the summary left out |
| Propose a regimen | Checking it against the SmPC before saying it aloud |
| Order and format | That what it ordered is what was there |
| Translate for the patient | That the translation does not shift the clinical meaning |
| Suggest when to refer | The decision to refer |
What this site will not tell you
There is no legal reading here of what would happen in a specific case, and be wary of anyone who offers you one on a web page. What is solid and enough to work with: the professional act is performed by you, and using a tool does not transfer that to anyone else. For the rest — indemnity cover, your regulator's rules on advice and advertising, local requirements — the good answer is your professional body, not this page.
A full example, and what is wrong with it
The table above is understood by reading it. What reading it does not show you is how fast a well-written text crosses the line without warning, and how well the crossing is camouflaged. This example is the most innocent request there is.
What gets asked: "Write me a short note to give an elderly patient who is taking an anti-inflammatory and is also on an anticoagulant, for them to read at home."
Information for you
According to the product information, combining anti-inflammatories with oral anticoagulants increases the risk of bleeding. What you have is a moderate-risk interaction, common in patients of your age.
We recommend stopping the anti-inflammatory and replacing it with paracetamol 1 g every 8 hours while the pain lasts. Watch for bruising, bleeding gums or dark stools.
If you have any questions, ask your pharmacist.
Pharmacy ____________ · Date ____________
And now, what is wrong with that reply:
- "According to the product information" is signed by you, not by it. That sentence turns a model's reply into a citation of an official source, and printing it means endorsing it: whoever reads the paper will understand that somebody went and looked it up. If you did not, you have just attributed to the regulator something it did not say. And the worst part is that the failure is not in the content — the interaction is real — but in the attribution, which is precisely what nobody reviews because it sounds like rigour.
- "What you have is…" is a diagnosis in writing. It shifts register without it showing: it moves from informing to characterising that person's case. And it assigns a severity ("moderate") without having seen a single test result or the rest of the medication. Nobody would phrase it that way at a counter; on a printed page it stays written, with the pharmacy's name underneath, and it can be shown to their doctor.
- "Stop taking" plus a specific regimen: that is the line. Stopping a treatment is a clinical decision and it belongs to whoever prescribed it. And the "paracetamol 1 g every 8 hours" arrives without asking about renal function, liver disease or anything else they take. The model has done nothing strange: you asked for a useful note and useful notes end in a recommendation. It is the request that walks you to the line, not the model — which is why you have to put the line into the request yourself.
- And the footer turns it into a document from your pharmacy. "Pharmacy ____ · Date ____" is not something you asked for: it added it because that is what documents shaped like this one carry. With those two blanks filled in, the paper stops being a note and becomes something that looks like a professional record, which is how the doctor it gets shown to will read it. And "ask your pharmacist" at the end rescues nothing: it comes after telling them what to stop and what to take.
The version that can be printed says the same and crosses nothing: what to watch for, when to come back to the pharmacy or see the doctor, and not one decision taken. You get it by saying so in the request — "do not recommend stopping anything, no doses, no cited sources" — and it costs eleven words.
The rule that stays with you: anything that will carry your name gets read with the question "would I say this, in these words?", not "is it well written?". The model answers the second question better than you do; nobody else can answer the first.
And if your pharmacy is not like that
When it does not work first time
Before moving on
- I know a conversation with a model is not a source, and why.
- I document the source and my decision, not the tool I used.
- I know signing an AI-written text is signing it all the same.
- I can tell what the AI may do from what stays mine.
- For indemnity and regulatory questions I ask my professional body.
← Revisit: AI bias
Next: when NOT to use AI →
← Back to the AI School