Development Updated 02 Nov 2026 7 min read

Software as a medical device (SaMD) in the UK: is your app a medical device?

Building a healthcare product? Free working prototype in 5–10 days
Get a quote
Nick Selin
Nick Selin
Consulting Director
SaMD (Software as a medical device): Examples and Trends Updated 02 Nov 2026

SaMD in the UK: when health software becomes a medical device under UK MDR, MHRA examples, classes, UKCA marking, DTAC and DCB0129, and what it means for build cost.

Short answer. Under UK MDR, software intended to support a diagnosis or a treatment decision can be a medical device (software as a medical device, SaMD) that needs UKCA marking. Administrative, wellbeing and information products usually are not. The line turns on the product's intended purpose and on how its results are worded to the user, so settle it before you build: a product that crosses the line quietly is a product that stops at procurement. Regulated health products typically cost £80,000–£120,000 over 5–8 months to build at Magora; a first release of a non-device product starts from £10,000.

This guide is for founders and product owners in health. It shows where MHRA guidance usually places common products, what changes if yours is a device, and how that affects the build.

Last checked: 2 November 2026.

This is a general guide, not regulatory advice. Magora is not your regulatory advisor: confirm the position for your product with a specialist or the MHRA, and check the current guidance, which changes from time to time.

SaMD examples: four common products

ProductUsuallyWhyWhat would change it
Mood trackerNot a deviceMHRA says monitoring general fitness, health and wellbeing is not usually considered a medical purpose.It claims to diagnose, screen for or treat a condition, or advises on treatment.
Patient portalNot a deviceBooking appointments, requesting prescriptions or hosting a consultation is administrative; a record that replaces a paper file is not a device.It interprets results, calculates a risk score or a dose, or tells the patient what to do clinically.
Symptom checkerLikely a deviceSoftware that outputs matching conditions, indicates likelihood or recommends treatment is listed by MHRA as an example that may be a device.Only signposting (“see your GP”), or reference information in a fixed order, is unlikely to be a device.
Skin-lesion analysis appLikely a deviceMHRA lists apps that diagnose, assess or monitor the skin using images as examples that may be devices.An app that only records images, with no analysis, is unlikely to be a device.

Source: MHRA, Medical devices: software applications (apps). Also on our healthcare software development page.

Intended purpose decides it, and so does the wording

Two apps built on the same code can sit on different sides of the line. What counts is what the product is for and what it says to the user: “your readings are above your target, contact your clinic” is very different from “you may have condition X”. That is why we write the intended purpose and the user-facing wording in the first fortnight, before the design is fixed.

If your software is a medical device

  • Classification. Many software devices are Class I, which the manufacturer self-declares. A higher class, such as Class IIa for software that allows direct diagnosis, needs a UK Approved Body.
  • UKCA marking under UK MDR, with a quality management system and technical documentation behind it.
  • Clinical safety. A hazard log kept live through the build, with failure behaviour designed in: what happens when data is missing, late or wrong.
  • More testing and evidence, which is the main reason regulated products take longer and cost more.

SaMD, DTAC, DCB0129 and DSPT: how they fit together

Whether or not your product is a device, an NHS buyer will usually ask for DTAC responses, DCB0129 clinical safety evidence and DSPT alignment. These shape the architecture: audit logging, role separation, data residency and failure behaviour. Our guide NHS software compliance: DTAC, DCB0129 and DSPT covers each one.

What a health product costs to build

StageTypical timeMagora band (GBP)
Free working prototype5–10 working days£0
Discovery: scope, architecture, fixed-price quote2 weeksFrom £3,000
First release (MVP)6–8 weeksFrom £10,000
Full production system3–6 months£25,000–£60,000
Regulated or integration-heavy system5–8 months£80,000–£120,000
Support after launchMonthlyFrom £1,000 a month

Rates behind the bands: from £49 an hour per developer, and £65–£70 an hour for a full team with QA and product ownership. Source: Magora UK software development pricing, 2 November 2026. Figures exclude VAT.

Health products that connect to clinical records (FHIR, HL7, GP Connect) or carry device-level evidence sit in the regulated band. More detail in healthcare software development cost.

Building a health product? Send us a short brief. We will raise the medical-device question in the first conversation and build a free working prototype in 5–10 working days. See healthcare software development and healthcare app development.

Frequently asked questions

What is software as a medical device (SaMD)?

Software that is itself a medical device: it has a medical purpose, such as supporting a diagnosis or a treatment decision, without being part of a hardware device. In the UK it falls under UK MDR and needs UKCA marking.

Is my health app a medical device?

It depends on its intended purpose and on what it claims to do, not on the technology. Apps that track wellbeing, book appointments or replace a paper record are usually not devices; symptom checkers that suggest conditions and apps that assess skin images are likely to be. Confirm the position with a specialist or the MHRA.

What class is my SaMD?

Many software devices are Class I, which the manufacturer self-declares. A higher class, for example Class IIa for software that allows direct diagnosis, needs a UK Approved Body.

Does SaMD make development more expensive?

Yes. Clinical safety work, a hazard log, more testing and documentation are part of the build. At Magora regulated or integration-heavy products typically cost £80,000–£120,000 over 5–8 months, while a first release of a non-device health product starts from £10,000.

What is the difference between SaMD, DTAC and DCB0129?

SaMD is about whether the software is a medical device under UK MDR. DTAC is the NHS assessment of digital health technologies, and DCB0129 is the clinical risk management standard for manufacturers of health IT. An NHS buyer will usually ask for DTAC and DCB0129 evidence whether or not the product is a device.

Nick Selin

Nick Selin

Consulting Director

Nick is a Consulting Director at Magora. He focuses on driving growth and creating valuable partnerships. With a sharp eye for market trends and a natural ability to connect with people, Andrew leads initiatives that keep Magora at the cutting edge of innovation and success in the tech industry.

LinkedIn
Newsletter

Get the next one in your inbox.

One email a month. Practical, no fluff. Unsubscribe anytime.

— Cookies

We use cookies to measure traffic and make our marketing more relevant. Necessary cookies stay on. See our We use cookies to measure traffic and marketing. Privacy and · Cookie Notice.

Free 30-min consult Free consult