October 10th, 2026 at 09:58 am
By Ronak Shah, Nordstone | Last updated: October 2026
A UK healthtech app typically costs £40,000 to £110,000 for a patient-facing wellness product, £90,000 to £250,000 for telemedicine, and £180,000 to £450,000 or more for NHS-facing clinical software. Regulation drives the premium: as a planning figure, clinical safety, DTAC, MHRA classification and NHS integrations can add roughly £35,000 to £130,000 to the core build.
TL;DR
- Cost range: Nordstone’s planning ranges run from £40,000 to £110,000 for a wellness app up to £220,000 to £550,000 or more for AI diagnostics, with NHS-facing clinical software at £180,000 to £450,000 or more.
- Compliance premium: Nordstone’s planning ranges put compliance and regulatory work at £15,000 to £50,000, and retrofitting it after the build usually costs more than planning for it from the start.
- NHS DTAC: Version 2 was published on 24 February 2026 with about 25% fewer questions, and the old form could not be used after 6 April 2026. It is a buyer’s assurance process, not an NHS approval badge.
- Medical device rules: intended purpose decides whether the MHRA regime applies, and conformity assessment costs usually sit outside a software build quote.
- NHS integrations: budget £6,000 to £55,000 per integration (NHS Login £10,000 to £20,000; GP Connect £25,000 to £55,000) plus eight to sixteen weeks of assurance. The NHS App had 41.6 million registrations by May 2026.
Saving money safely: scope regulation first, build one journey, phase integrations and never cut clinical safety, security or accessibility.
How much does a healthtech app cost in the UK?
There is no single price, because “healthtech” covers everything from a habit-tracking app with no regulatory exposure to a clinical decision-support tool sold to NHS trusts. Cost follows clinical risk far more closely than screen count. The two products might look similar on a wireframe, yet one needs a clinical safety case, an MHRA assessment and national-standard integrations, while the other needs a privacy notice and good security.
Nordstone’s planning ranges for current UK builds are set out below. They assume a UK-based agency, a cross-platform build and a phased approach that gets a first release to market early. Other UK suppliers publish different numbers, mostly because they define scope differently. Square Root places a healthcare MVP at £40,000 to £90,000 according to its UK cost guide, while a UK healthcare software guide from Mecanik puts a substantial application with integration, information governance and a DTAC submission at £35,000 to £75,000, with formally risk-managed enterprise products starting above that and routinely exceeding £250,000. These are commercial estimates, not official benchmarks, so always compare like-for-like scope.
| App type | Typical UK cost | Typical timeline | Regulatory complexity |
| Wellness or patient-facing app | £40,000–£110,000 | 3–6 months | Low to medium |
| Appointment booking | £50,000–£130,000 | 3–6 months | Low to medium |
| Telemedicine | £90,000–£250,000 | 6–12 months | Medium to high |
| Mental health and therapy | £80,000–£200,000 | 5–10 months | Medium |
| Chronic disease management | £120,000–£320,000 | 8–14 months | High |
| Clinical or NHS-facing app | £180,000–£450,000+ | 9–18 months | High |
| AI-powered diagnostics | £220,000–£550,000+ | 12–18+ months | Very high |
Source: Nordstone planning ranges.
For non-health benchmarks and a wider view of what drives app pricing, see our flagship guide on how much it costs to build an app in the UK. If you are comparing sectors, our other vertical cost guides cover fintech apps, eCommerce apps and logistics and delivery apps.
Why does a healthtech app cost more than a standard app?
Three things push the price up: regulated evidence, higher engineering standards and scarcer specialist roles. Health data is special category data under UK GDPR, so security and consent design carry more weight. Clinical software must show it is safe, which means hazard logs, safety cases and a named clinical safety officer. And NHS buyers expect interoperability with national systems, which brings its own build and assurance effort.
UK pricing guides describe the same pattern. Mecanik, for example, frames healthcare software as standard custom-software cost with a compliance premium layered on top. For healthtech aimed at NHS procurement that premium tends to be larger, because clinical safety documentation and DTAC evidence go beyond ordinary GDPR work. Timing matters just as much: retrofitting MHRA classification, DPIA documentation or clinical safety assessments after the build usually costs more than planning for them from the start, because architecture, data flows and test plans have to be reopened.
Running costs rise too. Our planning figure for annual maintenance is 15% to 20% of the build cost, which covers fixes, operating-system updates, hosting and regulatory updates as standards change.
What does each part of a health tech budget cover?
The table below breaks a full-featured healthtech build into its main components. Treat the ranges as per-component guides for a product with clinical or NHS ambitions; they do not add up neatly to the type-based bands above, because a lean MVP reduces or defers several of these lines.
| Cost component | What it covers | Typical cost |
| Discovery and clinical scoping | Requirements, regulatory pathway assessment, architecture planning | £10,000–£25,000 |
| UX and product design | Patient and clinician journeys, accessibility, usability testing | £15,000–£40,000 |
| Core app development | iOS and Android, backend, APIs, admin system | £50,000–£180,000 |
| Compliance and regulatory | MHRA classification, DPIA, DCB0129 clinical safety case, DTAC preparation | £15,000–£50,000 |
| EHR and NHS integrations | HL7 FHIR, GP Connect, NHS Login, PDS | £20,000–£80,000 |
| Security audit and pen testing | Independent review, vulnerability assessment, Cyber Essentials support | £7,500–£25,000 |
| QA and clinical validation | Functional and clinical scenario testing, usability studies | £10,000–£30,000 |
| Ongoing maintenance | Bug fixes, OS updates, hosting, regulatory updates | 15–20% of build per year |
Source: Nordstone planning ranges.
Our wider healthcare app development guide covers features, regulation and supplier selection in more depth; this article focuses on what you will actually pay for and why.
How does NHS DTAC affect the cost of a health tech app?
The Digital Technology Assessment Criteria (DTAC) are the baseline framework NHS organisations use to assure digital health technology. According to NHS England’s DTAC guidance, DTAC covers five areas, including clinical safety and data protection, and applies alongside rather than instead of other required approvals. NHS England’s developer guidance describes DTAC as best practice rather than a legal requirement, though an essential one in practice for anyone selling to the NHS.
Version 2 of the form arrived on 24 February 2026. NHS England’s Innovation Service reports a 25% reduction in questions, with duplication removed against the Data Security and Protection Toolkit and the pre-acquisition questionnaire, and a full transition by 6 April 2026. That makes the paperwork lighter, but it does not lower the bar on the underlying evidence.
For budgeting, the important point is that the form itself costs nothing; the evidence behind it does. A credible submission draws on a clinical safety case, a DPIA, penetration-test results, accessibility and interoperability evidence, and a DSPT submission. Those artefacts are cheapest when they are produced as the product is built, which is why our compliance and regulatory line (£15,000 to £50,000) sits inside the project plan rather than at the end. Our DTAC compliance guide walks through the version 2 changes and the evidence pack in detail.
Will MHRA medical device rules add to the cost?
They can, and the deciding factor is intended purpose, not technology. Under the UK Medical Devices Regulations 2002, software intended for diagnosis, prevention, monitoring, treatment or alleviation of disease is a medical device and must meet the regulations before it is placed on the market. The MHRA’s guidance on stand-alone software including apps explains how to decide whether your product qualifies and how classification follows the risk it poses. A general wellness or administrative tool usually falls outside the regime; a symptom checker that steers treatment decisions often does not.
Intended purpose is read from what you claim, so wording matters. Reporting by Inside EU Life Sciences on the MHRA’s July 2026 guidance for ambient voice technology says summarisation alone does not make an AI scribe a medical device, which shows how sensitive classification is to function. In budget terms, a software build quote rarely includes conformity assessment, clinical evidence generation or any Approved Body fees, and these vary widely with device class. Ask for them as separate line items once your classification is settled, and confirm the current marking route with your Approved Body. If your product uses AI to analyse clinical data, our AI app development cost guide covers the model, data and infrastructure costs that sit alongside regulation.
What do clinical safety and data protection add?
Clinical safety comes first for anything sold into NHS or social care services in England. NHS England’s clinical safety assurance page describes two standards: DCB0129 for manufacturers of health IT systems and DCB0160 for the organisations that deploy them. Both require a nominated Clinical Safety Officer with suitable training in clinical risk management, and in practice that means a clinical risk management plan, a hazard log and a clinical safety case. NHS England Digital has started a review of both standards, so plan for the documentation requirements to evolve. The Clinical Safety Officer can be an employee, a fractional hire or an outsourced service; decide early, because the role must be in place before development rather than after.
Data protection is the second layer. The ICO confirms that health data is special category data, so you need both an Article 6 lawful basis and an Article 9 condition, and you should identify both before processing begins. For many commercial apps, explicit consent is the realistic Article 9 route, whereas providers of health or social care may be able to rely on a different condition; take advice on which applies. A DPIA is expected for large-scale or novel processing of health data. Our UK GDPR checklist for app founders covers consent, retention and user rights in detail.
Finally, suppliers that handle NHS data should expect the Data Security and Protection Toolkit. The DSPT organisation types guidance defines a Supplier category for organisations that contract with NHS or care bodies to provide digital goods and services, with scope limited to the health and care data they process. Some NHS buyers also ask for Cyber Essentials certification, and an independent penetration test (our range: £7,500 to £25,000) is the usual way to evidence technical security.
How much do NHS integrations cost?
If your app needs to verify patient identity, read GP records or exchange data with clinical systems, you will be working with national APIs and standards. Each one adds build effort, registration and assurance. The table gives our indicative ranges.
| Integration | What it enables | Complexity | Indicative cost |
| NHS Login | Verified NHS patient identity and authentication | Medium | £10,000–£20,000 |
| GP Connect | GP records, appointments and structured data | High | £25,000–£55,000 |
| HL7 FHIR APIs | Standardised health data exchange | High | £20,000–£50,000 |
| NHS App integration | Listing and deep-link access through the NHS App | Medium | £12,000–£30,000 |
| PDS (Patient Demographics) | NHS number lookup and identity matching | Medium | £10,000–£25,000 |
| Wearable data | Apple Health and Google Fit ingestion | Low to medium | £6,000–£18,000 |
Source: Nordstone planning ranges.
Build time matters as much as cost. NHS integrations require registration with NHS England’s developer programme, information governance agreements and technical assurance, so plan for eight to sixteen weeks of integration-specific work on top of core development. The prize can justify the effort: NHS England Digital’s statistics show 41,613,543 all-time NHS App account registrations by the end of May 2026, with 14,863,212 distinct users logging in during that month alone. Even so, integrate only where it supports your first commercial customer; every additional integration adds both cost and assurance work.
How can you reduce healthtech app cost without cutting safety?
Start by narrowing intended purpose. A tightly defined purpose can keep a product out of a higher device class, and every feature you add can widen the regulatory footprint. Then run discovery and regulatory scoping first, ideally in the opening six weeks, so that classification, DTAC scope and integration needs are known before design begins. This is the cheapest compliance money you will spend.
Next, build one high-value journey, release to a limited user group and gather real-world evidence before expanding. Delay NHS integrations until a buyer needs them, produce DPIA, clinical safety and security evidence as you go, and use a cross-platform stack where device features allow. You may also be able to offset part of the cost: see our guides to Innovate UK grants and funding for app startups and R&D tax credits for app development. What you should not cut is clinical safety, security, accessibility or testing, because retrofitting them later is where budgets overrun.
If you are weighing delivery models, our mobile app development service page outlines how we structure phased builds for regulated products.
Frequently asked questions
How much does a healthtech app cost in the UK?
Why is a healthtech app more expensive than a standard app?
How much does NHS DTAC add to the cost?
Does my healthtech app count as a medical device?
How much do NHS integrations like NHS Login and GP Connect cost?
How long does it take to build a healthtech app?
Do I need NHS approval to launch a healthtech app?
How can I reduce the cost of a healthtech app?
Get a healthtech cost and compliance scoping session
A reliable healthtech budget starts with the regulatory pathway, not the feature list. Nordstone builds health and telemedicine products for UK startups, private providers and NHS-adjacent organisations, with clinical safety, data protection and NHS assurance planned from the first sprint. Book a scoping conversation with our team and we will map your classification, compliance workload and a phased budget before you commit to a build.
