How Poor Referral Quality is Slowing Down NHS Elective Surgery Recovery
February 23, 2026
.svg)
May 7, 2026
A system under pressure — and why eRS is back at the centre
Elective care reform in the NHS has entered a more structural phase.
The immediate backlog response is giving way to something more fundamental: a redesign of how patients move through the system. At the centre of that redesign sits the NHS e-Referral Service (eRS). This is not as a new product, but as an increasingly mandated foundation for how referrals, triage, and clinical advice are coordinated.
Recent guidance has created a degree of confusion. Headlines that eRS is becoming “mandatory” from October risk oversimplifying what is, in reality, a more nuanced shift. Most organisations are already using eRS for consultant-led referrals. The change is not about introducing eRS, but about expanding its role within a more structured, pre-referral model of care.
To understand what is happening, it helps to separate policy intent from operational reality.
Historically, eRS has functioned primarily as a booking and referral management tool. What is now emerging is a repositioning of eRS as the entry point to elective care pathways, particularly through the expansion of Advice and Refer.
This shift reflects a broader policy direction:
Advice and Refer is central to this. Increasingly, it is not framed as an optional step, but as a default mechanism for managing demand, allowing specialists to support primary care without formal referral.
In that sense, the change is less about technology and more about clinical workflow. eRS is simply the infrastructure through which that workflow is standardised and recorded.
What is less frequently discussed in the move towards Advice & Refer and structured triage is its direct impact on clinicians themselves.
As more activity is shifted upstream, clinicians, particularly in secondary care, are expected to spend significantly more time reviewing cases digitally, providing advice, and participating in triage decisions before a patient is ever formally referred.
This creates a new kind of pressure.Not one driven purely by volume of patients seen, but by the volume of decisions made.
Done well, this model can reduce unnecessary referrals and improve patient outcomes. But done poorly, it risks introducing additional layers of administrative burden, fragmenting workflows, and increasing clinician frustration.
This is where the choice of digital infrastructure becomes critical. If eRS is used in isolation, many of the challenges clinicians already experience, such as incomplete information, inefficient communication, and disjointed workflows, are likely to be amplified rather than resolved.
As a result, organisations need to take a more critical view of their current setup:
For many services, the honest answer is that current approaches are already stretched. Expanding those same processes without rethinking the supporting infrastructure risks making existing problems worse.
In that context, the shift towards more structured triage is not just a policy or operational question. It is a usability and clinician experience question, and one that will ultimately determine whether these changes succeed in practice.
Alongside A&R, another important development is the continued rollout of Single Points of Access (SPoA) and structured triage models.
Rather than referrals being directed to individual services, they are increasingly:
This reflects the NHS’s longer-term ambition to left-shift care, moving activity away from hospitals and into neighbourhood and community settings.
However, while the direction is national, implementation is not. Integrated Care Boards (ICBs) retain significant control over pathway design. The result is a landscape that is standardising in principle, but heterogeneous in practice.
That tension, between national consistency and local variation, is where many of the current challenges sit.
The idea that eRS is “becoming mandatory” is not entirely wrong, but it is often misrepresented. eRS has long been mandated for most consultant-led referrals. What is changing is the expectation that: Advice and Refer is used more systematically, referral pathways are structured and auditable, and that activity flows through nationally recognised infrastructure.
In effect, the NHS is tightening the expectation that elective care activity is visible, consistent, and managed through standardised routes. What is not being mandated is the exclusive use of eRS as a standalone interface.
One of the more persistent misconceptions is that the shift towards eRS implies the removal of third-party platforms. There is no indication of this in national guidance.
In fact, the opposite is often true in practice. As pathways become more complex, incorporating A&R, SPoA models, community services, and multi-step triage, the limitations of using eRS in isolation become more apparent.
Third-party systems can play a critical role in:
From a technical perspective, eRS remains the system of record. But from an operational perspective, it does not need to be the system of interaction.
Organisations that conflate the two often create unnecessary friction for clinicians.
If there is a single theme that underpins the current phase of eRS expansion, it is the gap between policy intent and operational delivery.
National systems provide consistency and governance. But they are not always designed for:
This is particularly visible in areas such as Advice and Refer, where success depends less on the existence of a function and more on how well it is embedded into day-to-day clinical practice.
Without that embedding, A&R risks becoming just another administrative step, which will be iInconsistently applied, and poorly understood by referrers. The result is predictable: low adoption, variable quality, and limited impact on demand.
Another complicating factor is the degree of variation across ICBs.
While the direction of travel is shared, more A&R, more triage, more community care, the specifics differ:
Any solution operating in this space needs to accommodate that variability, rather than assume a single national model.
Within this context, the role of third-party platforms becomes clearer. Cinapsis, for example, does not replace eRS. It operates alongside it, using the Cinapsis Smart Sync, ensuring that:
Just as importantly, it addresses a less visible but critical issue: support.
National infrastructure is, by necessity, centralised. But implementation is local. The difference between a pathway that works and one that doesn’t often comes down to:
That layer is rarely provided by national systems alone.
It is tempting to frame the current changes as a technology story. In reality, they are part of a broader shift in how the NHS manages demand and delivers care.
At a strategic level, the direction is clear:
eRS is a critical enabler of that vision. But it is not, in itself, the solution.
Organisations that treat it as such risk focusing on compliance rather than usability.
Those that take a more pragmatic view, treating eRS as infrastructure, and investing in the layers around it, are more likely to achieve the outcomes the policy is designed to deliver.
The current wave of eRS-related guidance has created noise, particularly around what is and isn’t mandated.
Stripped back, the message is relatively straightforward:
What remains flexible is how organisations implement that model in practice.
That flexibility is not a loophole. It is a recognition that healthcare systems are complex, local, and variable. The challenge, and opportunity, is to design pathways that meet national expectations without losing sight of how clinicians actually work.
See how your team can streamline the new eRS changes using Cinapsis.
.svg)
