For most primary care networks, the Network Contract Directed Enhanced Service, usually shortened to the Network Contract DES, is the document that sets the terms of the job. It is the agreement that brings member practices together as a network, defines what the network is expected to deliver, and sits underneath a large share of the funding and workforce that flows into PCN-level work. Pharmacy and medicines work is woven through it, but the DES rarely spells out, line by line, how a network should organise that delivery in practice.
This post looks at the DES through a PCN pharmacy lens. It is not a clause-by-clause reading of the contract, and we deliberately avoid quoting specific figures, thresholds or indicator names, because those change and are best read from the source. The aim is to explain how the framework shapes medicines work at network level, where the Additional Roles Reimbursement Scheme (ARRS) fits within it, and how a managed clinical pharmacy service helps a PCN deliver consistently across every practice rather than unevenly.
What the Network Contract DES actually is
The Network Contract DES is an enhanced service that practices sign up to in order to participate in a PCN. It is the contractual glue between member practices and the NHS, and it is updated through the annual GP contract negotiations between NHS England and the General Practitioners Committee of the BMA. Because it changes each year, the precise requirements, sums and timelines for any given period should always be checked against the current published DES specification and the supporting BMA guidance rather than taken from second-hand summaries.
What stays broadly stable is the shape of the thing. The DES establishes the network as the unit of delivery, sets out service requirements that the network is collectively responsible for, and ties a set of funding streams to participation. It places obligations on the network as a whole, not just on individual practices. That distinction matters for pharmacy, because medicines work is one of the areas where networks are expected to act together.
Why medicines work sits at the heart of it
A great deal of what a PCN is asked to improve runs through medicines. Long-term condition management, safe prescribing, reducing avoidable harm from high-risk drugs, supporting people on multiple medicines, and delivering structured reviews are all clinical pharmacy territory. When the DES and the wider incentive arrangements point networks towards better outcomes, pharmacists and pharmacy technicians are frequently the people doing the underlying work.
This is why the workforce side of the DES and the clinical ambitions of the DES are so tightly linked. A network can be given a service requirement on paper, but it only lands if there is reliable clinical pharmacy capability behind it. The framework assumes that capability exists and is being used well. It does not guarantee that it is.
How ARRS sits within the DES
ARRS is the reimbursement route that allows PCNs to bring additional roles, including clinical pharmacists and pharmacy technicians, into network-level delivery. It is one of the mechanisms that sits inside the wider DES arrangements rather than a scheme that floats separately alongside it. In other words, the DES is the contract; ARRS is one of the funding levers it makes available to help networks build the team that delivers against it.
We have written separately about how PCNs can turn ARRS funding into genuine clinical value on our ARRS support page, so this post does not repeat that ground. The point worth holding here is the relationship: the DES frames the expectation, ARRS helps resource it, and the network is accountable for the result. A PCN that treats ARRS purely as a recruitment budget, without connecting it back to the delivery the DES expects, often ends up with roles in place but outcomes that drift.
The delivery expectations land on the network, not the practice
One of the more demanding features of the DES is that it asks a group of independent practices to behave, for certain purposes, as a single delivery body. Member practices keep their own lists, their own systems, their own ways of working and their own clinical leadership. Yet the network is judged on what it delivers collectively.
For pharmacy, this creates a familiar tension. A medicines optimisation priority, a high-risk drug monitoring standard or a structured medication review programme has to be delivered to a consistent standard across every practice in the network, even though those practices may run on different clinical systems, hold different patient populations and have very different appetites for change. The DES does not resolve that tension for you. It simply makes the network responsible for the outcome.
The practical consequence is that PCN pharmacy work has two jobs at once. It has to be clinically sound at the level of the individual patient, and it has to be organised at the level of the network so that no practice is left behind. Both have to be true for the network to deliver against the framework. You can read more about how we approach the operational side of this on our PCN management support page.
Where DES-driven pharmacy delivery commonly struggles
The same problems come up again and again when networks try to deliver medicines work to a DES standard across several practices:
- Uneven coverage. One or two practices run a strong programme while others lag, so the network reports an average that hides real variation in care.
- Fragile continuity. Delivery depends on a small number of individuals. Sickness, turnover or a vacant role stalls the programme, and the network loses momentum it cannot easily rebuild.
- Inconsistent clinical standards. Without a single agreed approach, reviews, monitoring and prescribing decisions vary from practice to practice, which undermines both safety and reporting.
- Governance gaps. Quality assurance, supervision and accountability are assumed rather than designed, so when something goes wrong it is not clear who held the standard.
- Reporting that does not match reality. The network struggles to evidence what it has done, which matters when delivery against the DES has to be demonstrated.
None of these are failures of effort. They are structural problems that come from asking several independent practices to deliver one consistent service without a delivery model built for that purpose.
What consistent, DES-aligned pharmacy delivery looks like
A network that delivers medicines work well against the DES tends to share a few characteristics. There is a single, agreed clinical approach to the core areas, so a structured medication review or a high-risk drug check means the same thing in every practice. There is continuity, so a pause in one practice does not collapse the whole programme. There is clear governance, so quality assurance and accountability are owned and visible. And there is reporting that the network can actually stand behind.
The work itself is the familiar clinical pharmacy portfolio applied at scale: clinical medication reviews, high-risk drug monitoring, signing prescriptions where the pharmacist is an independent prescriber, prescribing support and broader medicines optimisation. The difference at network level is that all of it has to be coordinated so that the DES is delivered evenly, not just where capacity happens to be strongest.
How a managed clinical pharmacy service helps PCNs deliver
This is where a managed service model differs from simply having pharmacists in post. Virtual Pharmacist provides a fully managed, remote clinical pharmacy service that works inside each practice’s own clinical system, whether that is EMIS, SystmOne, Vision or Medicus. We are not a staffing or agency arrangement. We hold the clinical governance, quality assurance and accountability for the service we deliver, and we apply a consistent clinical standard across every member practice in the network.
For a PCN trying to deliver against the DES, that consistency is the central benefit. The same approach to medication reviews, monitoring and prescribing support runs across all practices, so the network is not relying on one strong practice to carry the average. Continuity is held by us rather than by a single individual, so a vacancy or absence does not stall the programme. And because we maintain a full information governance stack, including NHS DSPT, Cyber Essentials, HSCN connectivity, ICO registration and data sharing agreements, the network can evidence that the work is done safely and to standard. You can read more about our governance position on our clinical governance and data security page.
It is worth being precise about regulation here. CQC registration requirements depend on the regulated activities and delivery arrangements. Where work is delivered within a practice’s registered service, the practice retains its regulatory duties and the provider remains accountable for its own service. Pharmacists are regulated by the GPhC. A managed service does not change who is accountable to CQC; it strengthens the network’s ability to meet that accountability with a consistent, governed approach. There is a wider shift to keep in view as well. From 2026, eligible pharmacists who meet the GPhC’s updated training, assessment and registration requirements join the register as independent prescribers, which gradually widens what clinical pharmacy teams can do within primary care.
For ICBs and larger systems looking across multiple networks, the same logic applies at a higher level. Consistent, governed medicines delivery is easier to commission, support and assure when it follows one model rather than many. That is exactly the basis on which we support ICB medicines management work across primary care.
Reading the DES well, then delivering it
The Network Contract DES sets the terms, points to the outcomes and provides the funding levers. It does not hand a network a delivery model. PCNs that do well with medicines work treat the DES as the framework it is, then build a delivery approach that is consistent, governed and resilient across every practice. For the specifics of any current contract year, including the precise requirements, sums and timelines, always work from the published DES specification and BMA guidance rather than summaries.
Getting the clinical delivery right is the part we can take off a network’s plate, with a managed service that holds the standard so the PCN can hold the strategy.
Frequently asked questions
What is the Network Contract DES?
The Network Contract Directed Enhanced Service is the agreement that GP practices sign to take part in a primary care network. It defines what the network is expected to deliver, sets service requirements at network level, and ties a range of funding streams to participation. It is updated each year through the GP contract negotiations, so current details should be read from the published specification and BMA guidance.
How does ARRS relate to the Network Contract DES?
ARRS, the Additional Roles Reimbursement Scheme, is one of the funding mechanisms made available within the wider DES arrangements. It lets PCNs bring additional roles, including clinical pharmacists and pharmacy technicians, into network delivery. The DES frames the expectation, ARRS helps resource the team, and the network remains accountable for the outcomes.
Why is medicines work so central to PCN delivery under the DES?
Many of the outcomes a PCN is asked to improve run through medicines, including long-term condition management, safe prescribing, high-risk drug monitoring and structured medication reviews. Clinical pharmacists and pharmacy technicians do much of this underlying work, so reliable pharmacy delivery is often what makes DES-related ambitions achievable in practice.
Does using a managed pharmacy service change CQC accountability?
CQC registration requirements depend on the regulated activities and delivery arrangements. Where work is delivered within a practice’s registered service, the practice retains its regulatory duties and the provider remains accountable for its own service. Pharmacists are regulated by the GPhC. A managed service does not move that accountability; it supports it by delivering a consistent, governed standard across the network and holding clinical governance and quality assurance for the service it provides.
How does a managed service help a PCN deliver consistently across practices?
A managed service applies one agreed clinical approach across every member practice, working inside each practice’s own clinical system. It holds continuity centrally, maintains a full information governance stack, and provides evidence of safe delivery. That helps a network deliver evenly against the DES instead of relying on whichever practice has the most capacity.
If you are a GP practice, PCN or ICB working out how to deliver medicines work consistently against the Network Contract DES, we would be glad to talk it through. Contact Virtual Pharmacist to discuss what your network needs and how a fully managed, remote clinical pharmacy service could support it.
