If you work in UK general practice, you use Ardens, probably many times a day, often without thinking about it. Its templates structure your long-term condition reviews, prompt your coding, and shape how QOF and contract data is captured in EMIS and SystmOne. They are a genuinely valuable piece of infrastructure, and they are also easy to over-trust. A completed template is not the same as a safe consultation, and the difference is entirely clinical reasoning. This is a detailed look at what Ardens templates do well, where they can quietly mislead, and the judgement they cannot replace.
In brief: Ardens templates help standardise clinical reviews, coding, QOF data capture and local workflows in EMIS and SystmOne. They are useful for reducing omissions and supporting contract and quality requirements, but they do not replace clinical reasoning, prioritisation or judgement about what actually matters in the consultation in front of you.
Key takeaways
- Ardens provides EMIS and SystmOne templates, searches, reports, referrals and formulary resources.
- It is deeply embedded, with Ardens stating its clinical tools are used across the large majority of practices in England.
- Templates reduce omissions and support accurate coding and QOF, which is real and useful value.
- They can mislead through tick-box completion, prompt overload, and over-documenting low-value fields while missing risk.
- The clinical work of prioritising, interpreting and safety-netting remains with the clinician.
What Ardens is
Ardens is a suite of clinical templates, searches, reports, referral resources and formulary tools that sits inside EMIS Web and SystmOne, the two dominant UK GP clinical systems. Ardens states that its clinical resources are used across the large majority of GP practices in England, which makes it one of the most embedded pieces of general-practice software, quietly shaping how millions of consultations are structured and coded. Its purpose is to standardise and support the routine, structured work of general practice: it provides ready-made templates for long-term condition reviews, prompts for the right SNOMED codes, resources aligned to QOF and the wider contract, localised referral information, and searches and reports practices use for population health and contract management. In short, it is the layer that turns the blank clinical system into a structured, contract-aware workflow.
What Ardens does well
The value is real, and worth stating plainly. Ardens is very good at reducing omissions in structured reviews, because a well-designed template prompts you to check and record the things a condition review should cover, so you are less likely to forget the foot check, the blood pressure, or the mood question. It supports accurate, consistent coding, which matters not only for QOF income but for the integrity of the record and for population-health searches. It aligns data capture with QOF and contract requirements, reducing the administrative burden of hitting those targets. It surfaces localised referral information at the point of need. And it does all of this inside the clinical system, without switching screens, which is exactly where workflow tools earn their place. For the routine, structured, codeable parts of general practice, Ardens does a genuinely useful job.
Where templates genuinely help
Templates are at their best in structured, protocol-driven reviews where completeness matters:
| Review | What the template helps capture |
|---|---|
| Diabetes annual review | HbA1c, BP, lipids, renal function, foot check, smoking, retinal screening, coding |
| Asthma / COPD review | Symptom control, exacerbations, smoking, spirometry, inhaler use, technique, coding |
| Hypertension review | Readings, targets, medication, QOF coding |
| CKD review | eGFR, ACR, BP, monitoring, coding |
| Mental health review | Mood, risk, medication, physical health checks, coding |
| Medication monitoring | Bloods and parameters due for high-risk drugs |
In each of these, the template's job is completeness and consistency, and it does that well. The risk begins when completeness is mistaken for sufficiency.
Where templates can mislead
The failure modes are subtle precisely because the template feels thorough. The first is tick-box completion: working through the fields without synthesising them, so every box is filled but no one has stood back and asked what the whole picture means. The second is prompt overload: a comprehensive template in a ten-minute consultation can generate more prompts than there is time to address, pushing the clinician to click through rather than think. The third is agenda substitution: assuming the template has captured why the patient actually came, when the patient's real concern may be nowhere in the coded fields. And the fourth is misdirected attention: spending effort on low-value fields that happen to be prompted, while a genuine risk that the template does not flag goes unexamined. None of these are the template's fault; they are what happens when a tool for capture is used as a substitute for judgement.
The clinical reasoning gap
Here is what a template structurally cannot do, and what the clinician must. It cannot prioritise: when a patient has diabetes, CKD, low mood and a new symptom, the template captures all of them but does not decide which matters most today. It cannot distinguish routine from acute: a "routine annual review" may actually be an early deterioration, and only clinical reasoning notices the breathlessness that has changed since last year. It cannot judge significance: a number can be technically abnormal but clinically irrelevant, or technically normal but concerning in context, and the template records the value without weighing it. It cannot decide whether the patient fits the pathway, or is the exception the pathway was not written for. And it cannot safety-net: deciding what to warn about, what to review, and when, is a clinical act the template does not perform. These five questions, what to prioritise, whether this is acute, whether the numbers matter, whether the patient fits, and what to safety-net, are the consultation, and they sit outside the template entirely.
A worked example
Consider a diabetes annual review where the Ardens template is completed perfectly: HbA1c recorded, BP recorded, foot check done, retinal screening coded, medication reviewed, everything green. The template is satisfied. But the patient mentioned, in passing, increasing nocturia and thirst over two months, and their weight has fallen. The coded review is complete and QOF is achieved, yet the clinical picture, worsening control or something more, is the part that matters, and it is not in the template's logic. A clinician reasoning through the case catches it; a clinician working the template to completion may not. The template did its job. The thinking was still required.
How to use templates well, and a note for trainees
The healthy model is simple: use the template to structure and code, and use reasoning to decide. Complete the relevant fields, then deliberately step back and ask the five questions above before you finish. For GP trainees, the risk is dependency, learning to complete templates fluently without building the underlying reasoning, and it is worth actively guarding against. A good habit is to treat every prompt as a question rather than a command: why is this field here, what risk is it trying to reduce, and does it apply to this patient? Trainees who can explain the reasoning behind each part of a review, rather than just complete it, are the ones who become safe unsupervised. The template should scaffold your thinking, not replace it.
Where iatroX fits
Ardens and iatroX solve different halves of the review. Ardens structures the consultation and captures the coded data; iatroX helps you understand and act on it. When a template raises a clinical question, is this HbA1c a reason to intensify treatment given the CKD, does this result cross a referral threshold, what monitoring does this drug need, Ask iatroX gives a guideline-grounded answer from NICE, CKS, SIGN and the SmPC with the source attached, and its reasoning support helps you work through the prioritisation and safety-netting the template cannot. It also lets you turn a routine coded review into genuine CPD and exam-relevant learning. Try it at Ask iatroX, and for how templates sit within the wider practice software stack, see the hidden GP software stack. For the reviews that follow a risk flag, see risk stratification and the GP contract.
Frequently asked questions
Is Ardens a clinical decision-support tool? Not in the diagnostic sense. Ardens is primarily a templating, coding, reporting and workflow layer for EMIS and SystmOne, supporting structured reviews and QOF. It structures and captures data rather than making clinical decisions, which remain with the clinician.
Does completing a template mean the review is safe? No. A completed template means the fields were captured, not that the clinical picture was synthesised, prioritised and safety-netted. Completeness is not the same as sufficiency, and a fully coded review can still miss the issue that matters.
How should GP trainees use templates without becoming dependent on them? Treat every prompt as a question rather than a command: why is this field here, what risk does it reduce, does it apply to this patient? Trainees who can explain the reasoning behind a review, not just complete it, build the judgement that makes them safe unsupervised.
Can templates worsen consultation quality? They can, if used passively. Prompt overload in short consultations, tick-box completion without synthesis, and attention drawn to low-value fields can crowd out the patient's actual agenda and the clinical reasoning. Used deliberately, they improve quality; used as a substitute for thinking, they can degrade it.
How do Ardens and iatroX differ? Ardens structures reviews, coding and QOF capture inside the clinical system. iatroX is a source-grounded reference and reasoning layer that helps interpret findings, check guideline logic, and learn from the case. One captures the data; the other helps you reason about it.