Ask a GP what software they use and most will say EMIS or SystmOne. But the modern consultation actually runs on a whole stack of embedded tools, layered on top of the clinical system and largely invisible until you name them: templates structuring the review, prompts firing as you prescribe, resources for inhalers and cancer risk, and platforms hosting local guidelines. Each solves a real problem, and each has a hard limit. This is a map of the hidden GP software stack, what every layer does well, what none of them can do, and where clinical reasoning still lives.
In brief: UK general practice runs on a layered software stack: EMIS, SystmOne or Vision as the clinical system, with tools like Ardens (templates and coding), OptimiseRx (prescribing prompts), RightBreathe (inhalers), C the Signs (cancer risk) and Eolas (local guidelines) layered on top. Each captures data or prompts an action; none replaces clinical reasoning, prioritisation or judgement, which remain with the clinician and are supported by a reference and reasoning layer such as iatroX.
Key takeaways
- Every UK consultation runs on EMIS, SystmOne or Vision, with multiple embedded tools layered on top.
- Each tool is specialised: templates, prescribing prompts, inhaler selection, cancer risk, or local guidelines.
- These tools capture data, prompt actions and standardise workflow, which is genuinely valuable.
- None of them prioritise, interpret, or safety-net, which is the clinical work that remains with you.
- A reference and reasoning layer sits across the whole stack, helping you decide and learn.
The foundation: EMIS, SystmOne and Vision
At the base of the stack is the clinical system itself. Almost every UK GP works in EMIS Web, SystmOne or, less commonly, Vision, and these are the operating environment for everything: consultations, prescribing, referrals, documents, coding and reporting. They matter for the stack because they determine what can be layered on top, since most third-party tools integrate with EMIS and SystmOne first, and because their template-driven, code-driven design shapes how every consultation is recorded. For a new GP, locum or IMG, learning the system is foundational, but it is only the base layer, and the tools built on top are where much of the day-to-day experience actually happens.
The template layer: Ardens
On top of the clinical system sits the templating and coding layer, dominated by Ardens, whose clinical resources are used across the large majority of practices in England. Ardens provides the templates that structure long-term condition reviews, the prompts that drive consistent SNOMED coding, and the searches and reports practices use for QOF and population health. It is excellent at reducing omissions and capturing coded data consistently. What it cannot do is decide what matters in the consultation, distinguish a routine review from an early deterioration, or safety-net, which is why a completed template is not the same as a safe consultation. We cover this in detail in Ardens templates versus clinical reasoning.
The prescribing layer: OptimiseRx
As you prescribe, the medicines-optimisation layer activates, and here OptimiseRx dominates, used in more than 4,500 practices and credited with helping the NHS save over £500 million. It reads the coded record and fires patient-specific prompts, blending safety, best-practice and cost messages drawn from national guidance and local formularies. It is a valuable safety net for coded, rule-based risks. Its limits are alert fatigue and the fact that a prompt is decision support, not an instruction, so safety and cost messages deserve different weight and the clinician must judge each against the individual patient. We explore this in OptimiseRx and alert fatigue.
The specialist resource layer: RightBreathe and C the Signs
For specific clinical domains, dedicated tools sit in the stack. RightBreathe supports inhaler selection across the 120-plus licensed device and drug combinations, strong for device and product choice and technique, though it references London pathways and is not a management guideline; the reasoning about diagnosis, escalation and the shift to AIR and MART sits elsewhere, as we cover in inhaler prescribing. C the Signs analyses the record to flag cancer risk and suggest referral pathways, integrated across EMIS, SystmOne and Vision, useful for surfacing risk and structuring safety-netting, but supporting rather than replacing NICE NG12 and clinical judgement, as we discuss in C the Signs versus NG12. Both are strong at their narrow task and silent on everything outside it.
The knowledge layer: local guidelines and population health
Two more layers complete the picture. Local guidelines increasingly reach clinicians through platforms such as Eolas, which many Trusts now use for antimicrobial and other local policy, and these govern how care is delivered locally, overriding national guidance for empirical antimicrobial choice. Separately, population-health and risk-stratification tools, such as Eclipse, RAIDR and QAdmissions, flag cohorts for review under contract requirements. Both layers point at patients or policies; neither conducts the structured review or the reasoning that follows a flag, which again is clinical work.
What the whole stack cannot do
Step back, and a pattern is obvious. Every layer of this stack does one of three things: it captures data, it prompts an action, or it standardises a workflow. Templates capture, prompts prompt, resources surface options, platforms host policy. What no layer does is the clinical reasoning that ties them together: deciding what matters most in this consultation, judging whether a value or a flag is clinically significant for this patient, distinguishing routine from acute, weighing a prompt against the full picture, and deciding what to safety-net and when to review. The stack is superb at capture, prompting and standardisation, and structurally incapable of judgement. That gap is not a flaw to be engineered away; it is the part of medicine that is irreducibly the clinician's.
Where iatroX fits across the stack
iatroX is deliberately not another capture or prompting tool competing for a slot in the stack. It sits across the whole thing as the reference and reasoning layer, the part every other tool assumes but none provides. When a template raises a question, a prompt suggests a switch, a resource offers a product, or a flag surfaces a risk, Ask iatroX gives a guideline-grounded answer from NICE, CKS, SIGN and the SmPC with the source attached, its reasoning support helps you prioritise and safety-net, and its adaptive practice turns the decision into retained learning for practice and exams. The other tools help you capture and act; iatroX helps you decide and understand. Try it at Ask iatroX.
Frequently asked questions
What software do UK GPs actually use? A layered stack: EMIS, SystmOne or Vision as the clinical system, with embedded tools such as Ardens for templates and coding, OptimiseRx for prescribing prompts, RightBreathe for inhalers, C the Signs for cancer risk, and platforms like Eolas for local guidelines, plus population-health tools.
Do these tools make clinical decisions? No. They capture data, prompt actions and standardise workflows. They do not prioritise, interpret significance, distinguish routine from acute, or safety-net, which are clinical acts. The tools support the consultation; the clinician makes the decisions and remains accountable.
Why do GP practices use so many separate tools? Because each solves a specific problem the clinical system does not fully address on its own: structured reviews and coding, patient-specific prescribing safety, inhaler selection, cancer risk, local guidance and population health. They are specialised layers rather than one integrated solution.
What is missing from the GP software stack? The reasoning layer. Every tool captures or prompts, but none supplies the clinical judgement that ties them together, deciding what matters, weighing significance, and safety-netting. That gap is filled by the clinician, supported by a reference and reasoning tool such as iatroX.
How does iatroX differ from tools like Ardens or OptimiseRx? Ardens and OptimiseRx capture data and prompt actions inside the clinical system. iatroX is a source-grounded reference and reasoning layer that helps interpret findings, check guideline logic, decide and learn. It works across the stack rather than occupying a single functional slot.