Designing a High-Risk Medication Monitoring System That Works in a PCN

High-risk medication monitoring is one of the most operationally demanding parts of medicines safety work a PCN takes on, and where a network is most exposed if the process breaks down. The reliability of the service comes from designing high risk medication monitoring as a network-level programme that runs consistently across every member practice, with defined recall protocols, named clinical responsibility and a workflow that catches overdue patients before another prescription is issued.

The design choices that determine whether a monitoring programme is reliable are less clinical than operational. Deciding who identifies eligible patients, how recall is triggered, what happens when a test is overdue and who authorises the next prescription is what separates a well-run monitoring service from one that patches gaps after the event.

Key takeaways

• High-risk medication monitoring can be reliable when PCNs run it as a single network-level service with consistent recall protocols across member practices.
• Clinical-system searches help identify patients prescribed medicines that require monitoring and form an important part of the service’s safety controls.The Specialist Pharmacy Service publishes regularly reviewed monitoring advice that can inform local protocols alongside relevant national guidance, product information, shared-care agreements and individual patient needs.The clearest division of labour is pharmacy technicians running the operational recall flow, clinical pharmacists interpreting results and implementing prescribing changes, and named GP supervision for edge cases.
• Regular audit cycles are what turn a monitoring service from reactive to reliable.

The safety cost of monitoring gaps

The safety consequences of gaps in monitoring are well documented. Avoidable adverse drug reactions cost the NHS around £98.5 million a year and contribute to significant hospital admissions, with high-risk medicines including anticoagulants, lithium, methotrexate and disease-modifying anti-rheumatic drugs accounting for a disproportionate share. Individual practices can run local recall for a handful of patients, but a PCN with fifty thousand or more registered patients cannot rely on individual clinicians remembering which cohort needs which test.

The picture changes with a network-level service design. When the same recall protocols apply across every member practice, when a single technician runs the overdue-monitoring searches on the same schedule, and when documentation is standardised so any clinician can see where a patient is in the cycle, the operational reliability of the programme rises sharply. Practices with unusual local circumstances can still apply variation; the point is that the variation is chosen, not accidental.

Identifying patients who need monitoring

The foundation of a working service is knowing who is on which medicine and why. Searches should run frequently enough to identify patients before their individual monitoring deadline, with the schedule reflecting the medicines covered and the risks associated with delayed follow-up.

Most PCNs delegate this to a pharmacy technician working across EMIS or SystmOne, depending on the network’s clinical system, and running the search to a defined template so that outputs are comparable from month to month. The technician generates the overdue list, cross-references against booked appointments and outstanding blood tests, and routes patients to the recall workflow. Running the search and coordinating recall can follow an agreed protocol, while ambiguous results, exceptions and decisions about treatment must be escalated to an appropriately qualified clinician.

Setting the recall protocols

Frequency by medicine class

The Specialist Pharmacy Service publishes maintained monitoring recommendations that specify the required tests and frequency for each high-risk medicine class. Networks that hold their local protocols against these recommendations at least annually stay current with any changes and reduce the risk of drifting out of line with national guidance.

When to escalate

A well-run programme spells out clearly what happens when a test comes back abnormal or is significantly overdue. Written escalation routes name the responsible clinician for each medicine class and specify the time window within which a follow-up must happen. Without this, borderline results pile up unresolved and the safety net begins to fail.

Division of labour

A clear split between clinical pharmacists, pharmacy technicians and prescribers is central to a working service:

• Pharmacy technicians can manage defined monitoring and recall workflows, while appropriately qualified clinicians interpret results and make prescribing decisions. Clear clinical ownership, supervision and escalation arrangements should apply throughout.Clinical pharmacists interpret results within their clinical competence and, where they hold the necessary prescribing authority, make or authorise dose changes and deprescribing decisions.
• Named GPs supervise edge cases, complex decisions and any prescribing outside pharmacist scope.

Audit cycles and CQC evidence

Audit is what turns a monitoring service from reactive to reliable. Regular risk-based audit can identify monitoring gaps, test whether protocols are working and support continuous improvement. Documented audit and improvement activity can help demonstrate effective medicines governance against CQC’s medicines-optimisation and related quality statements.

Shared care and hospital interfaces

Many high-risk medicines are initiated in hospital under a shared care agreement, with prescribing and monitoring transferring to primary care only where an appropriate shared-care arrangement has been agreed and accepted. Networks that build the shared care handover explicitly into their monitoring workflow, logging the shared care agreement, confirming responsibility and setting up the recall in a single handover, avoid one of the more common ways monitoring falls through.

Reviewing a monitoring service

For PCNs building or reviewing their high-risk monitoring service, working with an experienced service provider can help design the recall protocols, embed the searches into a consistent workflow across member practices and structure the division of labour so that pharmacist time is spent where it matters most, rather than leaving individual practices to run local monitoring in isolation.