How to document a pharmacist consultation (with examples)

When something goes wrong in primary care, the question is rarely whether the clinician made a reasonable decision: it is whether anyone can tell from the record. Knowing how to document a pharmacist consultation well, so the note shows what you asked, what you checked and why you decided what you did, is a clinical skill in its own right. This guide covers what a defensible note contains, a worked example, and the traps that catch busy pharmacists out.

This is general guidance to support your practice. Record-keeping expectations vary between organisations and systems, so individualise your approach and follow local policy and current professional guidance.

Documentation is the clinical act, not the admin after it

It is tempting to treat the note as paperwork after the real work. In a shared GP record the opposite is true. The GP who sees the patient in three weeks, the out-of-hours clinician at 2am: neither was in your consultation. For them, your note is the consultation. A decision that was careful and well reasoned but recorded as "advised, will monitor" looks identical to one that was neither.

There is a professional dimension too. GPhC standards expect clear, accurate records, and if your practice is ever questioned the contemporaneous note is usually your strongest evidence. If it matters clinically or medico-legally, it belongs in the record.

What a defensible consultation note contains

You do not need a long note; you need a complete one. A defensible note answers six questions.

• What was the issue? The reason for the consultation, in one line.
• What did you check? The relevant history, including pertinent negatives: the red flags you asked about and did not find.
• What did you examine or review? Observations taken, results looked at, the repeat list or discharge letter read: name your sources.
• What did you decide, and why? The impression and the reasoning, in a sentence. This is the part most often missing, and the one that protects you.
• What is the plan, and whose is it? Each action with an owner (you, the GP, the patient) and a timeframe.
• What was the safety-net? The specific symptoms you told the patient to act on and where to go, as covered in our guide to safety-netting in primary care.

The classic SOAP structure (Subjective, Objective, Assessment, Plan) maps neatly onto the same questions and works well for pharmacist consultations; the label matters less than the discipline of separating them.

A worked example: weak note versus strong note

The following consultation is entirely fictional and written for teaching. A patient in their late sixties phones the practice reporting light-headedness on standing since their ACE inhibitor dose was increased two weeks ago.

The weak note: "T/c pt. Dizzy since ramipril increased. Advised. Will monitor." Every word is true, and the note is almost useless. It does not say what "dizzy" meant, what was ruled out, what "advised" contained, or who is monitoring what, by when.

The strong note, still short:

• Telephone consultation; identity confirmed, happy to discuss by phone.
• Light-headed on standing since ramipril increase two weeks ago; settles within a minute of sitting. No falls, blackouts, chest pain or palpitations. Drinking normally, no recent illness.
• Reviewed: repeat list (no other new medicines), most recent BP and renal function.
• Impression: likely postural symptoms after the dose increase; no red flags today. Assessment by history only, not examined.
• Plan: patient to record home lying and standing BP readings this week; blood test booked; continue current dose. I will review results and discuss with the GP if low.
• Safety-netting: sit or lie down if dizzy; contact the practice or NHS 111 the same day after any fall, blackout or worsening; 999 for collapse or chest pain. Patient understood and agreed.

The second note takes perhaps ninety seconds longer, shows a structured assessment, names its own limits, and hands the next clinician everything they need.

Phrasing patterns that keep notes fast and clear

Concise notes come from reusable sentence shapes, not typing speed. A few that earn their keep: "Reports ..., denies ..." for history with pertinent negatives; "Reviewed ..." to name your sources; "Impression: ... because ..." to force the reasoning into one line; "Plan: [who] to [what] by [when]" for ownership; "Advised to seek help if ... via ..." for the safety-net; and "declined ... after discussion of ..." to record an informed refusal without judgement.

What to code and what to free-text

Codes and free text do different jobs. A SNOMED code is for anything a search, recall, audit or QOF indicator will need to find: the consultation type, the problem, key findings such as a blood pressure, procedures such as "medication review done", and allergies. Free text carries the reasoning, the discussion, the pertinent negatives and the safety-net. Codes let the system find the event; free text lets a human understand it. You need both, and our guide to clinical coding and SNOMED codes for GP pharmacists covers the detail. If an action sits with the GP, put it where they will actually see it: a task or a clear structured message, using the approach in writing a medication review action letter to a GP, not a line buried in your free text.

Telephone and remote consultations

Remote consultations need everything above, plus three extras. Record the mode ("telephone consultation") and that you confirmed who you were speaking to. Make the limits explicit: "assessment by history only, not examined" is an honest, protective sentence. And record the threshold for converting to face-to-face: if you offered an in-person review or agreed criteria for one, say so. Safety-netting carries extra weight remotely, so be specific about symptoms, actions and timescales.

Common traps

The retrospective gap. Notes written hours later lose detail and credibility. Write at the time where you can; where you cannot, add the entry as soon as possible and label it as retrospective with the time of the contact. Never backdate.

Copying forward. Pulling the last note or a template through and leaving stale text (an old blood pressure, "no changes") creates a record that claims things you did not check today. Templates are fine; unedited templates are a liability.

Opinion recorded as fact. "Non-compliant" is a judgement; "reports missing doses most mornings" is a finding. "Anxious" is a diagnosis; "appeared anxious, speech rapid" is an observation. Keep impressions labelled as impressions.

Plans without owners. "For repeat bloods" satisfies no one: who is arranging them, and who reviews the result? Every action needs a name and a timeframe, even if the name is the patient's.

Making good notes a habit

Documentation improves like any clinical skill: through practice with feedback, not reading about it once. Pick one consultation this week, write the note, then reread it as the out-of-hours clinician who has never met the patient, and see what is missing. Records and coding also run through the cases in our Start in Primary Care induction course, so you practise the note alongside the decision it belongs to.