Declare regulated medical device - First check if need to based on UI copy and intent

[KimiEatsCode]

Please declare the regulated medical device status for the app. See more details at:

https://developer.apple.com/help/app-store-connect/manage-app-information/declare-regulated-medical-device-status

[KimiEatsCode]

Write
Notifications
2
Home
Library
Profile
Stories
Stats
Following
Towards AI
Towards AI
UX Planet
UX Planet
John Au-Yeung
John Au-Yeung
Sheri Byrne-Haber, CPACC
Sheri Byrne-Haber, CPACC
Trilogicals
Trilogicals
GeekyAnts
GeekyAnts
Michal Malewicz
Michal Malewicz
Code Like A Girl
Code Like A Girl
0𝕏koji
0𝕏koji
The Airbnb Tech Blog
The Airbnb Tech Blog
When is an app considered a medical device?
The Distance
The Distance
7 min read
·
Jan 6, 2026

Digital health apps are everywhere right now. From symptom tracking to long-term condition management, more organisations are using digital products to support patients and modernise care.

But here’s what often gets missed: Some health apps are legally classed as medical devices, even when they don’t look like one.

That classification changes everything. How the app is designed, how data is handled, how it’s tested, and what you’re responsible for after it goes live.

If you’re building a health-focused app in the UK, it’s essential to know where that line sits. So let’s get clear on when a health app becomes a medical device, and what that means for your product.
Start with the simplest (and most important) filter: What’s the app for?

The MHRA (the regulator for medical devices in the UK) doesn’t start with features or technology. It starts with an intended purpose.

In practice, that means:

What does your app claim to do?
What do users believe it will help them with?
How will the information it provides be used?

If your app is aimed at general wellbeing (encouraging steps, supporting meditation, logging moods or habits), you’re probably safe on the “lifestyle app” side of the fence.

But if your app is designed to:

diagnose a condition
monitor a disease
predict symptoms or flare-ups
recommend treatments or actions
or inform clinical decisions

…then you’ve crossed the line into medical device territory.

And here’s the nuance that catches people out:

It doesn’t matter whether the app is capable of medical accuracy, only whether it claims to be.

If your onboarding screen says “We’ll help identify early signs of X”, that’s a medical claim. If your website says “Our app can help you determine whether you need clinical attention”, that’s a medical claim. If your UI displays a score that implies a diagnosis or treatment recommendation, that’s a medical claim.

Even if that claim was meant to be “friendly” or “helpful”, it still triggers regulation.

This is why we encourage partners to involve their development agency early in the product design phase, especially teams that understand how quickly small wording changes across UX, onboarding, and marketing can shift an app into a higher risk category.
What to do next if you think you might be making a medical claim

Before you go too far in design or development, it’s worth doing a quick internal “claims audit”. Nothing complicated, just a structured sweep of every place your app talks to the user:

onboarding screens
notifications
dashboards / scoring systems
website landing pages
marketing content
investor decks (yep, these get scrutinised too)

Ask one question of each:

“Does this wording imply diagnosis, prediction, treatment, or clinical action?”

You’d be surprised how often a medical claim sneaks in through UI copy or a single line of marketing messaging.

If something might be interpreted as clinical, it’s a good moment to pause and bring in a product, UX, or regulatory specialist before you go further. It’s infinitely easier to adjust messaging early than to retro-fit the entire app into a medical-device workflow later.
What about apps that feel medical but aren’t actually medical devices?

Let’s clear up the other side of the line, because not all health-adjacent apps need clinical approval.

Apps that typically don’t qualify as medical devices include:

step counters
sleep trackers
calorie or nutrition logs
journaling or mood-tracking apps
meditation and breathing apps
menstrual cycle trackers that don’t make medical predictions

Press enter or click to view image in full size

To put it simply:

Wellbeing apps help you notice patterns.

Medical apps help you act on them.

The moment your app influences action (especially medical action), the rules tighten.

Image source.
Why making this distinction early matters (and not just for compliance)

If your app might fall under medical device regulation, discovering this late in development is the worst-case scenario.

It affects almost everything under the surface:
Your data model

Medical-grade apps need clearer audit trails, more structured data, and tighter security controls.
Your UX and visual design

Interfaces must avoid misleading users; subtle colour choices or wording can imply risk levels, which instantly changes classification.
Your testing and documentation

Medical devices need traceability, validation, and repeatable processes. Your QA process suddenly becomes part of the legal compliance journey.
Your release strategy

Submitting a regulated medical app to app stores involves more than the usual checklist, you also need to ensure compliance with regulatory requirements, provide supporting documentation, and confirm that all safety and validation processes are complete before it can go live.
Your long-term responsibility

Once it’s live, you’re required to monitor incidents, update safely, and report any issues proactively.

None of this is difficult when planned, but it’s incredibly challenging when bolted on at the end. This is why partnering with seasoned app developers (who have worked within regulated sectors before, like us!) can save months of rework.
What actually changes if the app is a medical device?

If you do fall into regulated territory, you’ll need to build with a few extra layers baked in from the start. The big ones:

1. Documented requirements (not just Jira tickets)

Medical-grade apps need formal requirements that map directly to testing, risk controls, and release notes.
2. A risk management file

This is essentially a living document that spells out:

what could go wrong
how likely it is
what controls the app has in place
how those controls are tested

It’s not scary, but it is mandatory.
3. Usability engineering

UX isn’t just “clean and intuitive”. You have to prove users won’t misinterpret data, colour coding, or language in a way that could put them at risk.
4. Verification & validation testing

You’re not just testing whether the app “works”. You’re testing whether it works as intended, for the intended user, in the intended environment, every single time.
5. A post-launch safety plan

Even after release, regulated apps need:

incident monitoring
a clear update process
a way to handle user-reported issues
documented safety checks before each release

These are the things that often catch teams off guard, and the reason it’s worth making the medical/non-medical decision early in the journey.
Press enter or click to view image in full size
A simple way to understand how apps are classified

Medical device classification sounds intimidating, but you don’t need a regulatory degree to understand the basics.

Here’s a simplified version:

The more impact your app might have on someone’s health, the higher its classification, and the stricter the requirements.

Imagine three different apps dealing with the same condition:

App A: “Track your asthma symptoms and see patterns over time.” ➡ Likely not a medical device.

App B: “Based on your symptoms, we’ll show your risk of a potential asthma flare-up.” ➡ Likely is a medical device.

App C: “Based on your flare-up risk, we recommend you increase inhaler use.” ➡ Definitely a medical device, and a higher-risk one.

Nothing technical changes between A, B, and C. The difference is the impact on user decisions.
Where AI complicates things (and why that’s OK)

Many modern health apps now use machine learning (even simple forms of it) to detect trends, classify symptoms, or automate decision support.

But here’s the key line:

If AI influences diagnosis or treatment, regulation becomes non-negotiable.

That doesn’t mean AI is off-limits, far from it.

It simply means transparency, explainability, and validation matter even more. And this is why working with skilled app developers who understand both AI and healthcare is so important, it’s easy to unintentionally create a medical device without meaning to.
Further reading & useful resources

If you want to dig a little deeper (or check how your app might be classified), these are great starting points:

[MHRA: Medical Device Regulations](https://www.gov.uk/guidance/regulating-medical-devices-in-the-uk) — plain-language guidance on where the lines are drawn.
[MHRA: Software and AI as a Medical Device (SaMD) change programme](https://www.gov.uk/government/publications/software-and-ai-as-a-medical-device-change-programme/software-and-ai-as-a-medical-device-change-programme-roadmap) — the latest thinking on how AI tools will be regulated.
[NHS Digital Service Manual ](https://service-manual.nhs.uk/)— best practices for designing safe, user-centred digital health products.
[BS EN 62304](https://knowledge.bsigroup.com/products/medical-device-software-software-life-cycle-processes) — the recognised standard for medical software lifecycle processes.
[IMDRF SaMD Framework](https://www.imdrf.org/working-groups/software-medical-device-samd) — useful if you’re planning global rollouts beyond the UK.

They’re not bedtime reading, but if you’re building something health-focused, they’re absolutely worth bookmarking.
So… when should you treat your app as a medical device?

If you’re unsure, this rule rarely fails you:

If the app guides medical decisions (even a little), assume it’s a medical device.

It’s safer, it’s clearer, and it ensures users aren’t misled.
Build boldly, but build with intention

Digital health is one of the most exciting areas in tech right now. The potential for apps to support patients, lighten workloads, and improve access to care is huge. But it comes with responsibility — not just to regulators, but to users who depend on that information.

Understanding when an app becomes a medical device isn’t there to slow innovation. It’s there to make sure innovation is safe, reliable, and trustworthy.

And if you’re stepping into this space (whether you’re commissioning an app or building one yourself), choosing the right development partner matters. You’ll want a team that understands what makes a great user experience and what medical-grade quality looks like behind the scenes.

If you’re curious to see how this works in practice, check out our success stories with projects like iPrescribe, Slimming World, and Health Swap to see real examples of safe, effective, and user-friendly health apps in action.

Let us guide you through the medical device journey
Medical Devices
Mobile App Development
Medical Apps
Wellness App

The Distance
Written by The Distance
8 followers
·
1 following

At The Distance, we build more than apps – we create experiences, seamlessly aligning with your team to deliver award-winning expertise and innovation.
No responses yet
Sarah Kimi Rettig
Sarah Kimi Rettigshe/her


More from The Distance
What is invisible UI and why it’s changing product design
The Distance

The Distance
What is invisible UI and why it’s changing product design
If you haven’t heard the term Invisible UI yet, don’t worry, you’re not alone.
Mar 11
6
How to use AI to validate your app idea before you start
The Distance

The Distance
How to use AI to validate your app idea before you start
Having an app idea is exciting. But before you start thinking about design, tech stacks, or budgets, it’s crucial to understand whether…
Feb 11
4
How AI Is changing the landscape of cybersecurity in app development
The Distance

The Distance
How AI Is changing the landscape of cybersecurity in app development
Discover how AI is transforming app security for product owners, boosting protection, trust, and growth while supporting smarter…
Sep 10, 2025
1
What to expect in your first 30 days after launch
The Distance

The Distance
What to expect in your first 30 days after launch
You’ve done it. You’ve partnered with experienced UK-based app programmers, trusted application developers in the UK, or a full-service…
Dec 3, 2025
See all from The Distance
Recommended from Medium
6 brain images
Write A Catalyst

In

Write A Catalyst

by

Dr. Patricia Schmidt
As a Neuroscientist, I Quit These 5 Morning Habits That Destroy Your Brain
Most people do #1 within 10 minutes of waking (and it sabotages your entire day)
Jan 14
42K
804
My full web design workflow, toolkit, hardware and software plan
Michal Malewicz

Michal Malewicz
My Complete Web design & build workflow for 2026
25 years of experience condensed into the best process there is.
Mar 12
527
11
Stanford Just Killed Prompt Engineering With 8 Words (And I Can’t Believe It Worked)
Generative AI

In

Generative AI

by

Adham Khaled
Stanford Just Killed Prompt Engineering With 8 Words (And I Can’t Believe It Worked)
ChatGPT keeps giving you the same boring response? This new technique unlocks 2× more creativity from ANY AI model — no training required…
Oct 19, 2025
25K
685
I Woke Up at 4:30 AM Every Day for 30 Days — Here Is What Nobody Tells You
ILLUMINATION

In

ILLUMINATION

by

Sufyan Maan, M.Eng
I Woke Up at 4:30 AM Every Day for 30 Days — Here Is What Nobody Tells You
Here is what actually happened, from someone who did it & tracked everything.
Mar 7
3.2K
140
Linear Regression: From Intuition to Mathematics to Code
Pradyumna Srivastava

Pradyumna Srivastava
Linear Regression: From Intuition to Mathematics to Code
Introduction
3d ago
52
1
AI Can Generate Content. It Can’t Generate Experience.
Keith Belanger

Keith Belanger
AI Can Generate Content. It Can’t Generate Experience.
I stopped mid-scroll the other day looking at a beautifully designed data architecture diagram. Clean layers. Perfect flow. Confident…
3d ago
4
See more recommendations

Help

Status

About

Careers

Press

Blog

Privacy

Rules

Terms

Text to speech