Skip to content

What building a healthcare app in the UK requires

Health data is special-category data, some software counts as a medical device, and the NHS has its own assessment criteria. This page sets out what that means for the build, how the data has to be handled, and the questions we ask before we quote.

We reply within one working day. 020 7078 5151

The rules that shape the build

None of these rules is optional, and most of them shape the design before any code is written. Your compliance adviser or clinical safety officer owns the decisions; we build so the decisions can be met and evidenced.

UK GDPR and the Data Protection Act 2018
Health data is special-category data. Processing it needs a lawful basis and an Article 9 condition, a data protection impact assessment before launch, and clear answers for access, correction and deletion requests. Where we are a processor, a written processing agreement sets out what we may do.
Clinical safety: DCB0129 and DCB0160
If the software supports clinical decisions or care, the manufacturer must follow DCB0129 (a clinical risk management system with a named clinical safety officer and a hazard log) and the deploying organisation DCB0160. That work starts at design, not at launch.
Medical device rules (UK MDR 2002, MHRA)
Software that diagnoses, monitors, predicts or treats can be a medical device and would need the right classification, a conformity assessment and UKCA marking before it goes on sale. Whether your idea crosses that line is the first question to settle, because it changes the budget and the timeline.
NHS Digital Technology Assessment Criteria (DTAC)
Anything sold into the NHS is assessed against DTAC: clinical safety, data protection, technical security, interoperability, and usability and accessibility. Building to it from the start is far cheaper than retrofitting it for a procurement.
Data Security and Protection Toolkit
Organisations with access to NHS patient data complete the DSPT every year. The app and its back end need to make that assessment answerable: access control, audit logs, patching and incident process.
App Store and Google Play health rules
Apple's App Review Guidelines restrict how health data may be used and shared (Guideline 5.1.3) and require a privacy label that matches what the app does. Google Play has equivalent health-app and data-safety requirements. Both reject apps whose stated data practices don't match the code.

How the data has to be handled

  1. 1

    Collect the minimum. Every field of health data you hold is a liability as well as an asset, so the design starts by asking what the service genuinely needs.

  2. 2

    Keep processing on the device where it can be. Checks, measurements and recognition that run on the phone mean less data in transit and less to protect on a server.

  3. 3

    Encrypt in transit and at rest, with keys managed by the cloud provider's key service and secrets never in the app binary.

  4. 4

    Host in UK or EU regions with a provider that publishes its certifications, and write the data flow down so the DPIA and DTAC answers are true.

  5. 5

    Role-based access with the least privilege needed, strong authentication for staff, and an audit log of who saw and changed what.

  6. 6

    Retention and deletion by rule, not by hand: how long each record is kept, and how a deletion request is honoured across backups.

  7. 7

    Integrations through standards (HL7 FHIR for records, NHS login for identity where applicable), each with the supplier's own onboarding and assurance steps allowed for in the plan.

The questions we ask before we quote

Twenty minutes on these usually settles whether the project is sound, what it needs and roughly what it costs.

Book a 20-minute call with our team

We reply within one working day.

  1. 1

    Who is the data controller, and is there a clinical safety officer and a data protection lead we can work with?

  2. 2

    Does the app inform or make clinical decisions, or could a regulator read it that way?

  3. 3

    Will it be sold into the NHS, and if so when does the DTAC assessment fall?

  4. 4

    Which data does the service truly need, and what could stay on the device?

  5. 5

    Which systems must it connect to (records, booking, identity), and who approves each connection?

  6. 6

    How will patients and staff authenticate, and what happens when a phone is lost?

  7. 7

    What is the plan for access, correction and deletion requests, and for an incident?

Technologies we use

Swift and SwiftUI Kotlin React and Next.js Node.js PostgreSQL AWS and Google Cloud (UK regions) HL7 FHIR On-device ML (Vision, Core ML)

After launch

Keep it working after launch

Websites and apps need looking after once they're live. App care is the plan most people choose after this, at £550 a month.

Already have an app or site that needs looking after?

Questions we get asked

By designing for it before the build: a data inventory, a lawful basis and Article 9 condition for each use, a DPIA with your data protection lead, encryption at rest and in transit, access control and audit logging, and working deletion and export. We write these down so they can be checked, and we don't claim compliance for you: that is a judgement your adviser makes on the evidence.

Talk to us before you scope it.

Let's talk about your project and the best way to approach it. No commitment and no pressure, just a conversation about what's possible.