The direction of travel in the NHS is towards care organised around neighbourhoods rather than single practices working in isolation. The idea is straightforward: bring together the teams that look after a defined local population, join up the work they do, and design services around the people who live there. For general practice and primary care networks, this raises a practical question that does not always get asked early enough. If care is going to be planned and delivered at neighbourhood scale, how does the medicines work that sits underneath all of it get organised so it actually holds together?
Medicines touch almost everything in primary care: long-term condition management, hospital discharge, frailty, polypharmacy, the monitoring of high-risk drugs and the steady churn of prescription queries. When neighbourhood health and medicines work are planned together, a neighbourhood model only holds up if this clinical pharmacy work is consistent across the practices in it, not patchy from one site to the next. This post looks at what the neighbourhood direction means for how medicines and clinical pharmacy are organised and run across practices and PCNs, and where a managed, remote service fits that picture.
What neighbourhood health is really asking of medicines work
Neighbourhood working is about scale and coordination. Instead of each practice solving the same problems separately, the aim is to share approaches, reduce variation and use limited clinical capacity where it has the most effect across a wider population. Policy framing on this continues to develop, so it is worth checking the current NHS England and BMA documentation for the specifics. The thematic direction, though, is clear enough to plan around.
For medicines, that direction creates three practical pressures. First, consistency. A structured medication review or a high-risk drug recall should look broadly the same whether a patient is registered at one practice or the one down the road. Second, coverage. Neighbourhood populations are larger and more varied, which means the clinical pharmacy effort has to stretch across more lists without thinning out. Third, accountability. When work is shared across organisations, someone still has to own the quality of it, the audit trail behind it and the governance that keeps it safe.
These pressures are organisational before they are clinical. The clinical pharmacy skills already exist. The harder part is arranging the work so it runs the same way across several practices, holds up to scrutiny, and does not collapse the moment a key person is off.
The organising problem: variation, continuity and ownership
Most PCNs already know what variation looks like in practice. One practice runs a tight, well-documented medication review process. Another does reviews when time allows. A third has good intentions and a backlog. Stack these differences across a neighbourhood and you get uneven care for patients who, on paper, sit in the same local health system.
Continuity is the second issue. Clinical pharmacy work that depends on a particular individual is fragile. When that person leaves, goes on leave or is pulled onto something urgent, the work stalls and the knowledge often goes with them. At neighbourhood scale this fragility multiplies, because there are more moving parts and more handover points where things can drop.
Then there is ownership. Sharing work across practices is sensible, but it can blur who is responsible for what. Who signs off the audit? Who holds the quality assurance? Who is accountable if a monitoring regime slips? Clarity here matters more as the unit of organisation gets bigger, not less.
Why the delivery model matters as much as the clinical work
It is tempting to treat the answer as simply more pharmacists. More hands certainly helps, but adding people without sorting out how the work is organised tends to reproduce the same variation on a larger scale. The model of delivery, how the work is structured, governed and made consistent, is what turns clinical effort into reliable population-level outcomes.
This is where it helps to distinguish a managed service from a staffing arrangement. With a staffing or agency model, a practice or PCN takes on individuals and remains responsible for organising, supervising and governing what they do. The variation problem stays with the buyer. A managed clinical pharmacy service is different in kind. The provider owns the way the work is delivered, the standards it is held to and the accountability for getting it right. That is what a neighbourhood model needs, because the whole point is consistency and clear ownership across multiple sites.
Virtual Pharmacist provides a fully managed, remote clinical pharmacy service to GP practices, PCNs and ICBs. The work is delivered inside each practice’s own clinical system, EMIS, SystmOne, Vision or Medicus, by a national team of GPhC-registered pharmacists and pharmacy technicians. For neighbourhood working in particular, Virtual Pharmacist holds the clinical governance, quality assurance and accountability for the service it delivers, so the buyer is not left stitching together standards across several practices on their own.
How a managed, remote service fits a neighbourhood model
Remote delivery suits neighbourhood working well, because the work is not tied to who happens to be physically present at one site on one day. A managed remote service can apply the same standards and processes across every practice in a neighbourhood at the same time, which is the consistency the model is trying to achieve. A few concrete examples of where this lands:
- Consistent reviews across practices. Structured medication reviews can be run to the same standard across every list in a neighbourhood, whatever the local capacity at each site.
- Reliable high-risk drug monitoring. High-risk drug monitoring is the kind of repetitive, safety-critical work that benefits most from a single governed process applied uniformly, instead of separate ad hoc systems per practice.
- Population-level medicines optimisation. Medicines optimisation work can be coordinated across a neighbourhood, which is where the prescribing and safety gains tend to scale.
- Backlog and prescribing support that does not stall. Because the service is managed and team-based, prescription queries and prescribing support carry on when an individual is unavailable, which removes a common single point of failure.
For networks carrying coordination and reporting load, this can also ease the management burden. PCN management support sits alongside the clinical work, helping turn funded roles and network responsibilities into consistent activity across the neighbourhood.
Governance and accountability at neighbourhood scale
The bigger the unit of organisation, the more governance has to be designed in rather than assumed. Clinical pharmacy work delivered into a GP practice sits within that practice’s own CQC registration and clinical governance, and the pharmacists doing it are regulated by the GPhC. A managed service does not change where that sits, but it does take responsibility for the quality, documentation and assurance of the work it delivers, which makes the practice’s own governance easier to evidence.
Information governance matters here too, because neighbourhood working means information moving more freely between teams. Virtual Pharmacist operates a full information governance stack, including NHS Data Security and Protection Toolkit compliance, Cyber Essentials, HSCN connectivity, ICO registration and data sharing agreements. You can read more about clinical governance and data security and how the service is held accountable.
There are also workforce changes worth noting. From September 2026, newly qualified pharmacists in Great Britain qualify as independent prescribers, which over time widens what clinical pharmacy teams can do directly within primary care. That makes the question of how this expanding capability is organised across a neighbourhood, and who holds the governance for it, more important, not less.
Planning ahead without over-committing
Neighbourhood health is a direction, not a finished blueprint, and the detail will keep moving. The sensible response is not to wait for every framework to settle, but to get the medicines work organised in a way that will hold up whatever the precise arrangements turn out to be. In practice that means consistency across practices, continuity that does not depend on any one person, and clear ownership of governance and quality. A managed, remote clinical pharmacy service is one practical way to put those foundations in place across a PCN or neighbourhood now, in a form that scales as the model develops. You can see the full range of clinical pharmacist support and pharmacy technician support available.
Frequently asked questions
What does neighbourhood health mean for medicines work?
It means organising clinical pharmacy work across a defined local population, not practice by practice. The priorities become consistency across sites, coverage of a larger population, and clear accountability for quality and governance. The policy detail continues to develop, so check current NHS England and BMA documentation for specifics.
How is a managed service different from hiring pharmacists?
With a staffing arrangement, the practice or PCN takes on individuals and remains responsible for organising, supervising and governing their work. A managed service is different: the provider owns how the work is delivered, the standards it meets and the accountability for it. For neighbourhood working, that ownership is what keeps the work consistent across multiple practices.
Can clinical pharmacy work be delivered consistently across several practices?
Yes. A managed, remote service works inside each practice’s own clinical system and applies the same processes and standards across every list at once. This suits neighbourhood working, where the aim is to reduce variation and run safety-critical work, such as high-risk drug monitoring, to a single governed standard.
Where does CQC and clinical governance sit in this model?
Clinical pharmacy work delivered into a GP practice sits within that practice’s own CQC registration and clinical governance, and the pharmacists are regulated by the GPhC. A managed service does not change where that sits, but it takes responsibility for the quality and assurance of the work it delivers, which makes the practice’s governance easier to evidence.
Does remote delivery suit a neighbourhood model?
It fits well. Because the work is not tied to who is physically present at one site, a managed remote service can apply the same standards across every practice in a neighbourhood at the same time, and the team-based approach means the work continues when any one person is unavailable.
Related reading
- GP federations and integrated neighbourhood teams: how medicines work is organised
- Multi-neighbourhood providers: what they mean for medicines work
If you are a GP practice, PCN or ICB thinking about how to organise medicines and clinical pharmacy work for a neighbourhood model, Virtual Pharmacist can help you put consistent, governed delivery in place. Get in touch with Virtual Pharmacist to discuss your needs.
