All resources
Medical Devices 2 June 2026 7 min read

Software as a Medical Device (SaMD) in the UK, do you need to register?

Not every health app is a medical device. But many that don't think they are, are. Here's how to make the right call without over- or under-classifying.

Software qualifies as a medical device under UK MDR 2002 (as amended) when it has a medical purpose, diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease. The intended purpose is what matters, not the technology.

Get the call wrong in either direction and you have a problem. Under-classify and you sell an unregistered medical device, regulator action, product recall, reputational damage. Over-classify and you waste a year and six figures on a process you didn't need.

How classification works

Important: most ambient voice technology (AVT) scribes used in clinical settings will land at Class I as a minimum, because they support a clinical record. The Class I MHRA registration burden is small, but the obligation is real.

  • Class I, low risk (most wellness, signposting, basic monitoring tools)
  • Class IIa, measuring function, short-term monitoring
  • Class IIb, long-term monitoring, therapy decisions
  • Class III, direct diagnosis/treatment, life-supporting

What MHRA registration involves

If your product is a medical device, you'll need a UK Responsible Person (if you're outside the UK), a technical file, a quality management system aligned to ISO 13485 (proportionate to class), UKCA marking, and registration with the MHRA.

How DigiSafe helps

We give you a straight, honest classification call, backed by the regulatory rationale, and only take you down the MHRA route if you genuinely need to be there. When you do, we run the project end to end.

Want this applied to your product?

We turn standards like this into evidence packs, safety cases and embedded CSO support, so you can focus on building.