The most consequential sentence in any NICE Evidence Standard 12 submission is the one most companies write without thinking: “Our digital health technology complements existing care.”
It sounds humble. It sounds safe. It is, in fact, a declaration that you are about to add new activity to a service that has 112,846 FTE vacancies and a 7.7% workforce gap — and you are asking the commissioner to find capacity that does not exist.
Standard 12 of the NICE Evidence Standards Framework is the moment in your evidence package where the value proposition stops being abstract and starts being operational. It is the test of whether you understand the NHS well enough to actually work within it. And the single question that decides the fate of most submissions is the one in the framework’s own pathway change typology: does this DHT replace an existing step, complement current care, or add something entirely new? The honest answer to that question is the centre of gravity for everything downstream — the economic model, the implementation plan, the commissioning conversation. Get it wrong here and the rest of the file collapses under cross-examination.
What Standard 12 Actually Requires
Standard 12 sits in the “Describing Value” group of the ESF (Standards 10–13) and applies to all DHTs across Tiers A, B and C. Its job is to translate the value proposition you established under Standard 10 (intended purpose) and Standard 11 (current pathway) into a credible map of what care looks like with your product in it.
NICE asks for a specific set of artefacts. A stepwise flowchart of the proposed pathway, mapped against the current pathway under Standard 11, with each change clearly annotated. An explicit statement of pathway position: replace, complement, or add. Infrastructure and workforce requirements at each changed step. Training needs, broken down by who, what, how often, and at what cost. Identification of any care boundary crossings — primary to secondary, health to social care, NHS to community provider. And a structured analysis of barriers and enablers grounded in actual NHS engagement, not generic implementation theory.
What looks on the surface like a documentation requirement is in fact the bridge between clinical evidence and commissioning reality. The proposed pathway is the structural backbone of the economic case under Standards 17 and 18 and the implementation plan under Standards 19 to 21. A weak Standard 12 produces weak everything downstream.
The Additive Trap
The most common Standard 12 failure I see is what I call the additive trap. A team builds a genuinely useful product, generates strong clinical pilot data, and writes a proposed pathway in which the DHT is “complementing” the GP, “supporting” the specialist nurse, or “augmenting” the consultant review. The pathway map shows the existing care steps unchanged, with new digital activity added alongside.
Read with a commissioner’s eye, every one of those verbs translates to the same thing: more work, performed by clinicians who do not currently have time to do it, paid for by a budget that does not currently exist.
The NHS is operating at the edge of its capacity envelope and has been for a decade. The latest NHS England figures show providers spent £8.3 billion on temporary staffing in 2024/25 — a near £1 billion reduction on the year before, but still substantially above pre-pandemic levels. Nursing vacancy rates run into double digits in parts of the country. London’s overall vacancy rate sits at 11.5%. In that environment, a proposed pathway whose first-order effect is to add clinical workload — however valuable that workload — has a commercial problem before it has a clinical one.
The additive trap is not solved by avoiding the word “complement”. It is solved by quantifying. If your DHT genuinely adds activity to the pathway, Standard 12 expects you to say so explicitly, count the additional minutes per patient encounter, identify whose time those minutes come out of, and explain why the outcomes justify the resource. Submissions that do this well — that own the addition and defend it — fare significantly better than submissions that bury it in soft verbs.
Why Substitutive Pathways Win
Pathways that genuinely replace existing resource use sit in a different commercial category. A DHT that releases clinical time, rather than absorbing it, gives the commissioner a coherent answer to the only question they actually care about: where is the capacity coming from?
This is not a theoretical advantage. NHS England’s own virtual ward programme illustrates it. Virtual ward capacity grew from 9,713 to 12,325 beds in the 11 months to May 2024 — a 27% increase — and was credited with helping deliver the first improvement in 4-hour A&E performance since 2009. The proposition was substitutive at its core: a hospital admission avoided is a bed-day saved, a length of stay reduced, a workforce hour redirected. The pathway logic was tractable to commissioners precisely because it described a resource swap, not an addition. When ring-fenced funding ended in March 2024, the rate of expansion slowed sharply — a useful reminder that even substitutive pathways need a clear funding mechanism, but the underlying commissioning case held.
The lesson for DHT founders is to interrogate your own pathway map without flinching. Where does clinical time come out? Which step is genuinely deleted, not just digitised? Which downstream resource is no longer required? The strongest submissions can point to specific deleted activities — a face-to-face follow-up replaced by asynchronous review, a triage call replaced by automated symptom assessment with clinician escalation, a diagnostic test rendered unnecessary by upstream stratification. Each deletion is a unit of value the commissioner can recognise, count, and pay for.
If, on honest analysis, your product is additive — and many genuinely valuable DHTs are — the strategic question changes. You need to identify the outcome benefit large enough to justify the additional cost, structure the commercial model to make the additional resource explicit and budgeted, and align with a funding source (national tariff, transformation fund, ICS investment programme) that is designed to absorb additive activity rather than steal capacity from existing services.
The ICS Layer Standard 12 Has Not Yet Caught Up With
Standard 12 was developed before England’s commissioning architecture changed. Since the Health and Care Act 2022 made all 42 Integrated Care Systems statutory bodies on 1 July 2022, the unit of commissioning, accountability, and pathway design has shifted from individual CCGs and trusts to system-level Integrated Care Boards holding both commissioner and provider functions across populations of one to three million people.
This changes the strategic calculus of cross-boundary pathways. A DHT whose proposed pathway crosses primary to secondary care, or NHS to community provider, used to face a commissioning impasse: the costs sat with one organisation, the savings with another, and no one had the authority to align them. Within an ICS, that authority now exists. The same pathway, framed correctly, is a population health management story rather than a contract negotiation problem.
Companies still writing Standard 12 submissions to a CCG-era model — single commissioner, single provider, single contract — are missing the most significant strategic shift in NHS commissioning in a decade. The strongest current submissions explicitly locate the proposed pathway within an ICS governance model, identify the population health metric the pathway moves, and align the value case with the system priorities the Integrated Care Board is being held accountable for. That framing turns a cross-boundary problem into a system-level proposition, which is exactly what ICSs were designed to commission.
Comparing the Three Pathway Positions
The framework’s three pathway positions look like a taxonomy. They are, in practice, three different commercial propositions with three different evidence and commissioning profiles. The table below summarises how each one tends to land in NHS contexts.
The honest categorisation of your product against this matrix is the single most important strategic exercise in your Standard 12 preparation. It is also the conversation most company founders are reluctant to have with themselves until a commissioner has it for them.
The Pathway Annotation Framework
A proposed pathway map that simply shows the new pathway is doing half the work. The version NICE evaluators and NHS commissioners actually want to see is one where the proposed pathway is annotated against the current pathway — every step coded for what it changes — and each change is explicitly linked to its resource, workforce, and training implication. That side-by-side comparison is what turns a flowchart into a value argument.
So What?
Standard 12 looks like documentation. It is, underneath, a stress test of whether your company understands the NHS well enough to operate inside it. Most DHT submissions fail this test in the same way: they describe an aspirational pathway, hide an additive cost behind soft verbs, understate the boundary-crossing complexity, and assume infrastructure or workforce capacity that does not exist in the settings where deployment is planned.
The teams that pass do it by doing one thing differently. They categorise their proposed pathway honestly against the substitute / complement / add taxonomy, accept the commercial implications of that categorisation, and build the rest of the evidence package around it. If you are a DHT founder reading the framework for the first time, this is the standard where the next twelve months of your commercial strategy gets decided. Do the categorisation properly, and Standards 17 to 21 fall into place. Skip it, and you will spend the next two years stuck in pilot.
If you’d like a structured walk-through of how your product maps against this matrix — and what it means for your NHS commissioning strategy — get in touch.
