Clinical Intervention Record
The catch is the easy part. What gets lost is the record: what was found, what evidence supported it, what the prescriber was told, what they decided, and what happened to the patient afterwards. Without that chain the intervention is invisible to audit, to remuneration, and to the next pharmacist who sees the same patient.
What This Skill Produces
- The intervention record — what was found, the class of problem, and the evidence relied on
- Severity and likelihood — assessed and stated, so a reviewer can see why this warranted a call
- The prescriber-call script — the thirty-second version that gets a decision rather than a callback
- The outcome — what the prescriber decided, including when they decided to continue unchanged
- Patient follow-up — what to monitor and who is doing it
- Aggregate fields — the data points that make interventions countable for audit and remuneration
Required Inputs
Ask for these if not provided:
- What you found — the interaction, contraindication, dose issue, duplication, or allergy conflict
- The medicines and the patient context — doses, timing, indication, renal and hepatic function, age, and other therapy
- Your evidence — the reference consulted and what it says, including the severity rating it assigns
- The prescriber — who they are and how they are best reached
- The outcome, once known — what was decided and whether the patient was affected
Framework: Evidence, Severity, Specific Ask
- Check a current reference before you call. Confident recall is where interaction errors come from. Name the source in the record.
- Assess severity and likelihood separately. A theoretically severe interaction with negligible likelihood is a different call from a moderate one that is near-certain in this patient.
- Establish patient-specific relevance. Renal function, age, concurrent therapy and indication determine whether a listed interaction matters here. Generic warnings get dismissed.
- Lead the call with the ask. 'I am calling about Mrs Shah's warfarin and the new fluconazole — I would suggest an INR check within three days' gets a decision. A recital of the interaction gets a callback.
- Record the decision, whatever it is. 'Prescriber elected to continue, monitoring arranged' is a complete and legitimate outcome and protects everyone.
- Close the loop. An intervention without follow-up is half an intervention.
Output Format
Intervention: [patient] · [date] · [pharmacist]
Found: [the problem, stated specifically] · Class: [interaction / contraindication / dose / duplication / allergy / other]
Medicines involved: [drug A + drug B, doses, start dates]
Patient-specific relevance: [renal/hepatic function, age, indication, concurrent therapy — why this matters for this patient rather than in general]
Evidence: [reference consulted, what it states, severity rating assigned] · Checked: [date/time]
Assessment: severity [high/moderate/low] · likelihood [high/moderate/low] · basis: [one line]
Prescriber contact: [who, how, when] · Said: [the thirty-second ask]
Outcome: ☐ Changed to [what] ☐ Dose adjusted ☐ Monitoring arranged ☐ Continued unchanged — [prescriber's stated reason] ☐ Unable to contact — [what was done instead]
Follow-up: [what is monitored · by whom · when] · Patient informed: [what they were told]
A documentation framework for a licensed pharmacist. It makes no clinical determination. Every interaction, severity rating, and monitoring interval must be verified against current validated references for the individual patient; do not rely on this structure, or on recall, for the clinical content.
Quality Checks
Anti-Patterns
- Calling from memory. The single most common source of a wrong severity claim.
- Reporting the interaction without the ask. Prescribers act on proposals, not on alerts.
- Ignoring patient-specific relevance. Undifferentiated warnings train prescribers to dismiss you.
- Not recording 'continued unchanged'. It looks like the call never happened, and it is the outcome most likely to be reviewed later.
- No follow-up owner. Monitoring assigned to nobody is monitoring that does not occur.
- Logging only the dramatic catches. Aggregate data is what funds and defends the service.
Example Trigger Phrases
- "Document the interaction I just called the GP about"
- "Record a clinical intervention for audit"
- "How do I write up a near-miss?"
- "Script for calling a prescriber about a warfarin interaction"
- "The prescriber decided to continue anyway — how do I document that?"
1---2name: drug-interaction-intervention-23description: Document a pharmacist's clinical intervention — the interaction or error spotted, what was done, what the prescriber decided, and the outcome — so the record shows the catch and the care that followed. Use when asked to document a clinical intervention, record a prescriber call about an interaction, log a near-miss, or build an intervention record for audit or remuneration. Produces the intervention record with severity and evidence, the prescriber-call script, the outcome and follow-up, and the aggregate reporting fields. A documentation framework for a licensed pharmacist; every interaction and severity judgement must be verified against current references.4---56# Clinical Intervention Record78The catch is the easy part. What gets lost is the record: what was found, what evidence supported it, what the prescriber was told, what they decided, and what happened to the patient afterwards. Without that chain the intervention is invisible to audit, to remuneration, and to the next pharmacist who sees the same patient.910## What This Skill Produces1112- **The intervention record** — what was found, the class of problem, and the evidence relied on13- **Severity and likelihood** — assessed and stated, so a reviewer can see why this warranted a call14- **The prescriber-call script** — the thirty-second version that gets a decision rather than a callback15- **The outcome** — what the prescriber decided, including when they decided to continue unchanged16- **Patient follow-up** — what to monitor and who is doing it17- **Aggregate fields** — the data points that make interventions countable for audit and remuneration1819## Required Inputs2021Ask for these if not provided:22- **What you found** — the interaction, contraindication, dose issue, duplication, or allergy conflict23- **The medicines and the patient context** — doses, timing, indication, renal and hepatic function, age, and other therapy24- **Your evidence** — the reference consulted and what it says, including the severity rating it assigns25- **The prescriber** — who they are and how they are best reached26- **The outcome, once known** — what was decided and whether the patient was affected2728## Framework: Evidence, Severity, Specific Ask29301. **Check a current reference before you call.** Confident recall is where interaction errors come from. Name the source in the record.312. **Assess severity and likelihood separately.** A theoretically severe interaction with negligible likelihood is a different call from a moderate one that is near-certain in this patient.323. **Establish patient-specific relevance.** Renal function, age, concurrent therapy and indication determine whether a listed interaction matters here. Generic warnings get dismissed.334. **Lead the call with the ask.** 'I am calling about Mrs Shah's warfarin and the new fluconazole — I would suggest an INR check within three days' gets a decision. A recital of the interaction gets a callback.345. **Record the decision, whatever it is.** 'Prescriber elected to continue, monitoring arranged' is a complete and legitimate outcome and protects everyone.356. **Close the loop.** An intervention without follow-up is half an intervention.3637## Output Format3839### Intervention: [patient] · [date] · [pharmacist]4041**Found:** [the problem, stated specifically] · **Class:** [interaction / contraindication / dose / duplication / allergy / other]4243**Medicines involved:** [drug A + drug B, doses, start dates]4445**Patient-specific relevance:** [renal/hepatic function, age, indication, concurrent therapy — why this matters for this patient rather than in general]4647**Evidence:** [reference consulted, what it states, severity rating assigned] · **Checked:** [date/time]4849**Assessment:** severity [high/moderate/low] · likelihood [high/moderate/low] · **basis:** [one line]5051**Prescriber contact:** [who, how, when] · **Said:** [the thirty-second ask]5253**Outcome:** ☐ Changed to [what] ☐ Dose adjusted ☐ Monitoring arranged ☐ Continued unchanged — [prescriber's stated reason] ☐ Unable to contact — [what was done instead]5455**Follow-up:** [what is monitored · by whom · when] · **Patient informed:** [what they were told]5657> A documentation framework for a licensed pharmacist. It makes no clinical determination. Every interaction, severity rating, and monitoring interval must be verified against current validated references for the individual patient; do not rely on this structure, or on recall, for the clinical content.5859## Quality Checks60- [ ] A current reference was consulted and is named with the date checked61- [ ] Severity and likelihood are assessed separately62- [ ] Patient-specific relevance is stated, not just the generic interaction63- [ ] The prescriber call led with a specific proposed action64- [ ] The outcome is recorded even when nothing changed65- [ ] Follow-up monitoring has a named owner and a date66- [ ] The patient was informed where appropriate, and that is recorded6768## Anti-Patterns69- **Calling from memory.** The single most common source of a wrong severity claim.70- **Reporting the interaction without the ask.** Prescribers act on proposals, not on alerts.71- **Ignoring patient-specific relevance.** Undifferentiated warnings train prescribers to dismiss you.72- **Not recording 'continued unchanged'.** It looks like the call never happened, and it is the outcome most likely to be reviewed later.73- **No follow-up owner.** Monitoring assigned to nobody is monitoring that does not occur.74- **Logging only the dramatic catches.** Aggregate data is what funds and defends the service.7576## Example Trigger Phrases77- "Document the interaction I just called the GP about"78- "Record a clinical intervention for audit"79- "How do I write up a near-miss?"80- "Script for calling a prescriber about a warfarin interaction"81- "The prescriber decided to continue anyway — how do I document that?"