The Four Principles of Medicines Optimisation in Primary Care

Note* - All images used are for editorial and illustrative purposes only and may not originate from the original news provider or associated company.

Related stories

When to Bring in Outside Help for FDA Cybersecurity Compliance (and What to Look For)

Medical device cybersecurity has become too important to treat...

Billerud Introduces New Pharmaceutical Packaging Option

Billerud has officially introduced PharmaKraft, a specialized fibre-based packaging...

AstraZeneca Advances AI Drug Discovery Deal with insitro

AstraZeneca has inked a billion-dollar AI drug discovery partnership...
- Advertisement -

Medicines optimisation in primary care became a formal discipline in 2013, when the Royal Pharmaceutical Society set out a four-principle framework that has guided the work ever since. The language was new at the time, but the underlying ideas were not. The framework redirected clinical attention from the medicine to the patient taking it and asked primary care teams to build that approach into routine prescribing.

More than a decade on, the four guiding principles still define how clinical pharmacy support is structured within GP practices and PCNs. NICE guideline NG5, issued in 2015, gave the principles formal clinical standing, and they now form the reference framework most clinical pharmacists, GPs and practice teams work from when designing medicines-related services. They also correspond closely to the day-to-day work of ARRS-funded pharmacy roles.

Key takeaways

  • The RPS framework sets out four principles that continue to guide medicines optimisation work in primary care.
  • NICE NG5 turned those principles into formal clinical guidance in 2015.
  • Each principle maps to specific operational work, from shared decision-making to deprescribing.
  • Clinical pharmacists in PCNs deliver against all four principles through their routine clinical work.
  • The DHSC’s National Overprescribing Review reinforced the practical urgency of these objectives.

Why the Principles Still Matter

The case for getting medicines optimisation right has only grown sharper since 2013. The Department of Health and Social Care’s National Overprescribing Review found that 8.4 million people in England take five or more medicines on a regular basis, and that around 10% of items dispensed in primary care are not clinically needed. Adverse drug events cost the NHS around £400 million a year, while avoidable medication errors add another £98.5 million, with primary care prescribing responsible for around a third of harmful errors.

These are not problems any single intervention can resolve, which is why the framework treats medicines optimisation as four connected disciplines rather than a sequential checklist.

Principle One: Aim to Understand the Patient’s Experience

The first principle asks clinicians to take the patient’s experience of their medicines seriously, which includes whether they are taking each medicine as prescribed, what side effects they notice, what they believe each one does for them, and whether they can manage the regimen alongside their daily routine.

In practice this requires structured conversation rather than interrogation. A patient who has quietly stopped taking a statin because of muscle aches will not always raise that at a routine appointment, but a clinical pharmacist conducting a structured medication review with twenty or thirty minutes of dedicated time can surface the problem, document it and act on it. Shared decision-making is built into this principle, and patients who understand the rationale for each medicine they take are typically more consistent with adherence and report side effects sooner. They also respond more openly to deprescribing recommendations, an important factor in PCN deprescribing programmes.

Principle Two: Evidence-Based Choice of Medicines

The second principle covers the prescribing decision itself. Every medicine added to a patient’s regimen should rest on current evidence, follow NICE guidance and the local formulary, and stand up to a check against the existing medicines list for interactions and duplications.

This is also where prescribing cascades come to light. Common examples include a diuretic prescribed for ankle swelling caused by a calcium channel blocker, a proton pump inhibitor prescribed for indigestion caused by an NSAID, or an antidepressant added without consideration of an existing tricyclic. In each case the prescriber missed an opportunity to deprescribe the medicine causing the problem rather than add a new one. The framework therefore treats evidence-based prescribing as ongoing rather than a one-off event, which is why structured medication reviews carry as much weight as the original prescription.

Principle Three: Ensure Medicines Use Is as Safe as Possible

The third principle covers safety in routine practice, where monitoring, interaction checking and deprescribing function as continuous activities rather than appointment-bound events. Patients on high-risk medicines such as anticoagulants, lithium, methotrexate and certain immunosuppressants require recall systems that flag overdue blood tests before another prescription is issued. Patients on ten or more regular medicines are significantly more likely to be admitted to hospital with a drug-related problem, and that risk rises with each additional medicine.

PCN clinical pharmacists typically take operational responsibility for this work, which usually includes:

  • Running system searches for patients overdue for high-risk medication monitoring.
  • Auditing high-risk prescribing across member practices for trends and outliers.
  • Coordinating practice responses to MHRA drug safety alerts.
  • Leading deprescribing work to remove medicines no longer benefiting the patient.

Pharmacy technicians support the underlying repeat prescribing workflow, which is where many safety problems originate before they reach a prescriber for review.

Principle Four: Make Medicines Optimisation Part of Routine Practice

What the principle requires

The fourth principle deals with structure. Medicines optimisation cannot rest on individual goodwill or one-off projects, and the framework specifies that it must be built into routine workflow if it is to produce lasting change. That requires defined responsibilities, agreed protocols, clinical supervision arrangements, and the data infrastructure needed to show whether the work is having a measurable effect on prescribing quality and patient outcomes.

What it looks like in a PCN

In a PCN this typically means protected time for SMRs, named clinical leads for medicines safety, regular audit cycles tied to risk areas such as high-risk medication monitoring and polypharmacy in older adults, and clear escalation routes between pharmacy team members and prescribers. It also requires treating medicines optimisation as a clinical activity that warrants ongoing investment, rather than as a finite improvement project with a closing date.

How the Principles Translate to PCN Workforce Planning

The four principles correspond directly to the day-to-day work of ARRS-funded pharmacy roles. Clinical pharmacists deliver against principles one and three through SMRs and high-risk medication monitoring, while principle two depends on prescribers, including independent-prescribing pharmacists, working within evidence-based pathways and the local formulary. Principle four belongs to the network itself, expressed through workforce plans, clinical supervision arrangements and the operational integration of pharmacy roles into practice teams.

Networks that map their pharmacy workforce to these principles tend to use their ARRS allocation more effectively than those treating it as a generic recruitment fund, because the workforce plan reflects clinical need rather than headcount. Working with a specialist provider can help PCNs build pharmacy roles around all four principles from the outset, rather than retrofitting the framework when gaps appear.

Never miss a pharmaceutical headline

The pharmaceutical industry moves fast – stay on top of it with our must - read briefings.

  • The top pharma and life sciences stories, straight to your inbox
  • The biggest news, features, interviews, and analysis
  • Dedicated coverage of the key developments driving the global pharmaceutical sector

Subscribe

- Never miss a story with notifications

- Gain full access to our premium content

- Browse free from any location or device.

Media Packs

Expand Your Reach With Our Customized Solutions Empowering Your Campaigns To Maximize Your Reach & Drive Real Results!

– Access the Media Pack Now

– Book a Conference Call

– Leave Message for Us to Get Back

Latest stories

Related stories

When to Bring in Outside Help for FDA Cybersecurity Compliance (and What to Look For)

Medical device cybersecurity has become too important to treat...

Billerud Introduces New Pharmaceutical Packaging Option

Billerud has officially introduced PharmaKraft, a specialized fibre-based packaging...

AstraZeneca Advances AI Drug Discovery Deal with insitro

AstraZeneca has inked a billion-dollar AI drug discovery partnership...

Managing Quality and Regulatory Risks in Pharmaceutical Technology Transfer

Technology transfer moves more than manufacturing instructions. It moves process knowledge, supplier dependencies, labeling requirements, packaging specifications, and the evidence needed to demonstrate control. For medical device manufacturers, including those supporting drug-device combination products, these interfaces can become recurring sources of compliance gaps during site transitions, acquisitions, and remediation. The central problem is often not a missing procedure. It is a quality system that allows connected activities to change independently. A label revision may be approved while packaging artwork, supplier instructions, or production-system data still reflect an obsolete version. Staying inspection-ready requires manufacturers to manage these dependencies as one controlled system. Why Compliance Gaps Keep Recurring Findings are treated as documentation defects Revising a procedure can resolve an immediate discrepancy without changing the behavior that caused it. If unclear decision rights, weak escalation, or ineffective training remain, the same failure may surface elsewhere. Corrective and preventive action should distinguish the observed finding from its underlying cause and establish how effectiveness will be demonstrated. Ownership is divided across connected functions Quality, Regulatory Affairs, labeling, packaging engineering, operations, suppliers, and digital-system owners often maintain separate workflows. Each team may complete its assigned task while an interface remains uncontrolled. For example, changing an instruction for use can affect packaging configuration, translations, technical documentation, inventory disposition, and release controls. Transitions expose unresolved weaknesses Acquisitions and site transfers can introduce conflicting procedures, incomplete knowledge transfer, or different assumptions about validated processes. Regulatory changes add further demands. When these events coincide with CAPA or change-control backlogs, teams may prioritize administrative closure over risk reduction. Without a coordinated impact assessment, local fixes can create new gaps downstream. Establish the Regulatory Baseline Inspection readiness starts with knowing which requirements apply to the product, activity, and market. Pharmaceutical, device, and combination-product obligations are not interchangeable; transfer planning should identify the applicable requirements rather than assume one quality framework covers every operation. According to FDA’s Quality Management System Regulation overview and FAQs, the QMSR became effective on February 2, 2026, incorporates ISO 13485:2016 by reference, and introduced the updated device inspection process under Compliance Program 7382.850. ISO 13485 certification does not exempt a manufacturer from FDA inspection or guarantee compliance with FDA requirements. For devices marketed in the European Union, Regulation (EU) 2017/745, Annex I, Section 23, provides the primary requirements for information supplied with devices, including labels and instructions for use. Teams should assess the applicable provisions alongside relevant language, product-specific, and market requirements. A labeling review should therefore evaluate required content and consistency with the device’s intended purpose and supporting documentation—not merely artwork accuracy. How to Identify the Real Gaps Begin with a cross-functional assessment that follows actual product and information flows. Select representative transfers, label changes, supplier changes, and CAPAs, then trace each from initiation through implementation and effectiveness review. Map dependencies: Identify affected specifications, suppliers, packaging components, systems, validation activities, and training. Compare records with practice: Check whether approved procedures match what operators and reviewers actually do. Test traceability: Follow a requirement through technical documentation, labeling, production instructions, and release evidence. Examine recurrence: Look for repeated deviations, reopened actions, overdue changes, and findings shared across sites. Assess capacity: Determine whether qualified owners have enough time and authority to complete corrective work. Prioritize gaps by potential patient or user harm, regulatory impact, likelihood of recurrence, and detectability. Document the rationale; an old overdue item is not automatically more important than a newly identified high-risk weakness. Align Quality, Labeling, Packaging, and Change Control Create a coordinated remediation plan with one accountable owner for each action, named contributors, acceptance criteria, and required evidence. Separate immediate containment from systemic correction. Containment might prevent obsolete labels from being issued; correction might redesign approval and implementation controls so obsolete versions cannot return. Use change control as the integration point. Before approval, evaluate effects on regulatory submissions or notifications, technical documentation, supplier controls, packaging performance, validation, electronic master data, inventory, and training. Record both identified impacts and justified decisions that particular activities are unaffected. During technology transfer, define readiness gates before production or release responsibilities move. These should address the transfer of process knowledge, acceptance criteria, receiving-site capability, required qualification or validation, approved documents, and personnel competence. The appropriate evidence depends on the product and process; a generic checklist cannot replace a documented assessment. Finally, verify implementation where the work happens. Confirm that current instructions are available, suppliers received approved requirements, systems contain correct versions, and affected personnel can perform their tasks. A signed approval is not evidence that every downstream change took effect. Mistakes That Undermine Inspection Readiness Closing CAPAs on task completion alone: Effectiveness checks should test whether the underlying failure has been controlled. Updating labels in isolation: Assess packaging, supplier, system, documentation, and inventory consequences. Counting closures instead of evidence: Dashboards need defensible records behind their status indicators. ...

Subscribe

- Never miss a story with notifications

- Gain full access to our premium content

- Browse free from any location or device.

Media Packs

Expand Your Reach With Our Customized Solutions Empowering Your Campaigns To Maximize Your Reach & Drive Real Results!

– Access theMedia Pack Now

– Book a Conference Call

– Leave Message for Us to Get Back

Translate »