Every ICB is being asked to do more or less the same thing right now: manage more referrals through advice and triage rather than automatic outpatient bookings, expand Single Points of Access, and shift more care into community settings, all without a meaningful increase in staff or budget.
On paper, that's the right ambition. In practice, it's creating an operational problem that doesn't get talked about enough: the tools being asked to carry this weight weren't built for it.
The NHS e-Referral Service exists to do one thing extremely well: standardise how referrals are booked and tracked across the whole of England. Its Advice and Guidance functionality, layered on top, was a genuine improvement, giving primary care a way to ask a question before defaulting to a referral.
What it wasn't built for is running that process at the volume and pace high-functioning Advice & Refer pathways now demand. Push enough cases through a system designed for asynchronous, occasional advice requests, and the cracks show up in predictable places: information gets entered twice across different systems, referrals arrive with gaps a specialist then has to chase, and clinicians end up spending more time on admin than the model was ever supposed to add.
We are told that clinicians struggle now with using eRS to manage the current small proportion of A&G numbers and that they are genuinely worried about how they can manage the huge increase when all cases fall under the A&R process.
None of this is a criticism of eRS doing its actual job badly. It's a mismatch between what the system was designed for and what it's increasingly being asked to carry.
It gets harder still. NHS England is tightening the rules around how Advice and Guidance has to work, including extending requirements to organisations using third-party tools for triage and Advice & Refer. The intent is reasonable: keep the national record consistent and prevent referral activity from fragmenting across systems NHS England can't see into.
But for any ICB or trust that's already built an efficient triage workflow outside eRS's native functionality, because that's often the only way to handle the volume, this creates a genuine bind. Retreat fully into eRS's native process, and you likely reintroduce the slow, disconnected workflow that pushed teams elsewhere in the first place. Keep doing what currently works, and you risk falling out of step with where national requirements are heading.
That's not really a technology problem. It's a structural one: two entirely reasonable goals, national consistency and local operational efficiency, that don't naturally pull in the same direction.
Solving this properly takes more than picking a side. It needs a workflow where the national system of record stays accurate without anyone re-entering data twice, where the clinician triaging a case has enough context, patient history and clinical record included, to make a confident decision without chasing more information, and where Advice & Refer can scale to high volumes without increasing the load on clinicians and administrators running the service.
That's a fairly specific set of requirements, and it's exactly what eRS SmartSync was built to meet. Rather than treating compliance and efficiency as a trade-off, Smart Sync keeps eRS as the system of record while letting clinicians do the actual triage and decision-making inside Cinapsis, with activity synced automatically between the two. Organisations using it report managing cases more than four times faster than through eRS alone, without losing visibility where it's needed.
The volume pressure on Advice & Refer isn't going away, and the compliance requirements around it aren't loosening either. The organisations that come out ahead won't be the ones that pick a side between national consistency and operational efficiency. They'll be the ones that found a way to stop treating it as a choice in the first place.
If that's the problem you're currently trying to solve, it's worth taking a closer look at how eRS SmartSync handles it, or talking it through directly with the Cinapsis team.