What a fully pharmacist-led repeat prescribing service actually looks like

Repeat prescribing is one of the largest recurring workloads in any practice, and one of the least visible until something goes wrong. A fully pharmacist-led service takes the entire repeat cycle off the GP's desk, but it only works if the boundaries, the paperwork and the escalation routes are agreed before the first prescription is touched. This article sets out what that looks like in practice.

The tasks the pharmacist takes on

In a fully led model, the pharmacist owns the repeat prescribing workflow end to end. That means more than re-authorising requests. The day-to-day tasks typically include:

• Processing repeat requests against agreed protocols, including checking adherence, interactions and whether monitoring is up to date before issuing.
• Reauthorising medications at review date, with a structured medication review where one is due.
• Managing queries from patients, community pharmacies and care homes about repeats, quantities and synchronisation.
• Handling prescription-related letters and requests, such as hospital discharge changes and outpatient recommendations, within agreed scope.
• Flagging patients who need blood tests, reviews or dose adjustments before their next issue, rather than letting the repeat roll on.

The practical effect is that the repeat inbox stops being a GP task. GPs see only the cases the pharmacist has assessed and escalated, which is a small fraction of the total volume.

Where GP input is still needed

Pharmacist-led does not mean pharmacist-only. There are clear points where GP involvement remains essential, and a good service defines them explicitly rather than leaving them to judgement on the day:

• New diagnoses and first prescriptions, which remain a prescriber decision outside the repeat process.
• Complex polypharmacy or multimorbidity where the clinical picture has changed and the repeat is no longer clearly appropriate.
• Controlled drugs and other high-risk medicines outside the agreed protocol scope.
• Any request where the pharmacist identifies a red flag, such as a possible adverse reaction or a significant interaction that needs a prescribing decision.

Escalation should be a normal, expected part of the service, not a sign of failure. If a pharmacist never escalates, the protocols are probably too loose.

SOPs and SLAs: the paperwork that makes it safe

Two documents carry the service. The standard operating procedure sets out, step by step, how each type of request is handled: what is checked, in what order, what can be issued under protocol, and what must be escalated. It should be written for the practice's own systems (SystmOne or EMIS), not adapted from a generic template, and it should be reviewed at least annually.

The service level agreement sets expectations the other way: turnaround times for routine requests, how urgent requests are identified and handled, cover arrangements for leave, and how performance is reported back to the practice. A typical SLA commits to routine requests being processed within two working days, with same-day handling for genuinely urgent items.

Safety netting

Every repeat service needs a safety net for the cases that fall between protocols. In practice that means a named route for patients to raise concerns about their medicines, a clear process for requests that arrive without recent monitoring, and a rule that no repeat is issued indefinitely without review. Patients on high-risk medicines should be on an accurate register with monitoring dates tracked, so the repeat process itself becomes a checkpoint rather than a rubber stamp.

What to measure

A service that cannot show its impact will not survive a contract review. The measures that matter are simple:

• Volume and turnaround: requests processed per week and time from request to issue.
• Escalation rate: the proportion sent to a GP, with reasons, reviewed monthly.
• Medication reviews completed and monitoring gaps closed as a by-product of the repeat process.
• GP time released, estimated from the volume of requests no longer reaching GP inboxes.
• Safety incidents or near misses, which should be recorded and fed back into the SOP.

Report these monthly to the practice or PCN in a one-page summary. When the numbers are visible, the value of the service is visible, and the conversation about renewing or extending it becomes straightforward.