Wellness App vs Medical Device Under EU MDR: The Line That Matters
Under EU MDR (Regulation (EU) 2017/745), whether a health app qualifies as medical device software depends entirely on its intended purpose — the use the manufacturer specifies in labelling, instructions, and promotional materials. An app that claims to detect, diagnose, or treat a medical condition is likely MDSW. One offering wellness insights and personal data trends is not — provided its developer makes no medical claims.
On this page
If you have ever wondered whether the health app on your phone is held to the same legal standard as a hospital diagnostic tool, the answer turns on one question: what does its developer claim it does? That single factor — known in EU law as intended purpose — separates a regulated medical device from an unregulated wellness tool, regardless of how sophisticated the underlying software is.
The question that determines everything
EU MDR (Regulation (EU) 2017/745) applies to software in the same way it applies to physical instruments, implants, and diagnostic equipment. What makes something a medical device is not the technology involved — it is the purpose for which the manufacturer intends it to be used.
This is deliberate. Regulators recognised that anchoring classification in technical features would create an arms race of workarounds. Instead, the regulation ties classification to what the manufacturer actually claims — in their labelling, their app store listing, their marketing materials, and their instructions for use.
The practical consequence: an app that says "track your sleep patterns for lifestyle awareness" sits in a fundamentally different legal category from one that says "screen for sleep disorders." The underlying algorithm might be identical. What changes is the claim.
What the medical device definition actually says
The definition of "medical device" in Article 2(1) of Regulation (EU) 2017/745, quoted directly in MDCG 2019-11, covers any software "intended by the manufacturer to be used... for human beings for one or more of the following specific medical purposes":
- diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease
- diagnosis, monitoring, treatment, alleviation of, or compensation for, an injury or disability
- investigation, replacement or modification of the anatomy or of a physiological or pathological process or state
Software that meets one of these purposes is Medical Device Software (MDSW) and falls within the full scope of EU MDR, including CE marking requirements, clinical evidence obligations, and post-market surveillance. Software that does not is outside MDR's scope — subject only to general consumer law, data protection rules, and applicable advertising regulations.
The regulatory definition of "intended purpose" under Article 2(12) of Regulation (EU) 2017/745, as set out in MDCG 2019-11: "the use for which a device is intended according to the data supplied by the manufacturer on the label, in the instructions for use or in promotional or sales materials or statements and as specified by the manufacturer in the clinical evaluation."
In plain terms: the intended purpose is not what the software is technically capable of — it is what the developer states it does, across every piece of public-facing text including the app store description.
Three questions that determine which side of the line you are on
MDCG 2019-11 sets out a structured decision process for qualifying software. Simplified for a non-specialist reader, it comes down to three questions.
1. Does the software do more than store, transfer, or display data unchanged? An app that simply archives your health records, forwards them to another system, or presents them without further processing is not MDSW. The regulation specifically excludes "simple search," lossless data compression, and basic archival from qualification. A steps counter that shows you a bar chart of yesterday's walk is not, by itself, MDSW.
2. Is the output directed at an individual user — not just a population? Software intended only to aggregate population data, generate generic health information not directed at a specific person, or support epidemiological research does not qualify as MDSW. The moment the output is directed at an individual user and makes a claim relevant to their health condition, the analysis changes.
3. Is the software's purpose medical? This is the decisive step. MDCG 2019-11 states plainly: "Software must have a medical purpose on its own to be qualified as a medical device software (MDSW). It should be noted that the intended purpose as described by the manufacturer of the software is relevant for the qualification and classification of any device."
Where the line sits in practice
MDCG 2019-11 provides worked examples that make the line concrete.
On the MDSW side of the line:
A smartwatch app "intended to send alarm notifications to the user and/or health practitioner when it recognises irregular heartbeats for the purpose of detecting cardiac arrhythmia" is MDSW — regardless of the consumer hardware it runs on. Similarly, a mobile app that "analyses a user's heartbeat, detects abnormalities and informs a physician accordingly" is classified as Class IIb under MDR Rule 11. Software that generates a cardiovascular disease risk score from user-entered data is MDSW. Software that scores depression based on user-inputted symptoms is MDSW.
Outside MDR scope — not MDSW:
Software for invoicing or staff scheduling: not MDSW, no medical purpose. Systems that only store, archive, or transfer data without processing it for a medical purpose: not MDSW. A fertility tracking app using a validated algorithm to predict ovulation and display a colour indicator: listed in MDCG 2019-11's Annex IV as Class I — the lowest risk tier — because despite collecting health-related inputs, its informational significance for clinical decision-making is low.
The pattern is consistent throughout the guidance: it is the medical claim, not the technical capability, that determines MDR classification.
One clarification from MDCG 2019-11 that often surprises developers: "the risk of harm to patients, users of the software, or any other person, related to the use of the software within healthcare, including a possible malfunction is not a criterion on whether the software qualifies as a medical device." A technically capable app can carry genuine risks and still not be MDSW. Conversely, a lower-stakes app can be MDSW if its intended purpose is medical.
What making a medical claim actually means
Once a developer frames their software in language that gives it a medical intended purpose, obligations follow immediately. Article 7 of EU MDR, cited in MDCG 2019-11, requires that "any claims relating to the intended medical purpose of their MDSW are supported by clinical evidence. If this is not the case, the software would not meet the requirements of the regulations and therefore may not be CE marked as a medical device, nor present said claims."
This is a double constraint. Making a medical claim without CE marking is a regulatory violation under EU MDR. But obtaining CE marking requires clinical evidence — a significant investment in time and resource that most consumer app developers are not positioned to undertake.
The practical result is a hard boundary: developers who want to stay outside MDR scope must frame all their claims in wellness and lifestyle language. A single sentence in an app store listing — "detects early warning signs of illness," for example — can push an otherwise uncertified app into a regulatory category it cannot lawfully occupy.
This is also why the language in a health app's description is not just a marketing question. Under EU law, it is a legal classification question.
MDCG 2025-4 and the app store dimension
In June 2025, the MDCG published MDCG 2025-4, guidance specifically addressing how MDSW apps should be made available on online platforms. One section bears directly on the wellness/medical distinction.
The guidance recommends that app platform providers "create a clear delineation in their libraries between MDSW apps and health apps with no intended medical purpose." The regulatory line that determines whether an app is a medical device should, in other words, also be reflected in how it is categorised in the place where users download it — not mixed in with lifestyle and wellness tools.
MDCG 2025-4 also confirms that making an MDSW app available via an app store constitutes "placing on the market" under MDR. For non-EU developers distributing via EU-based platforms, the guidance notes that the platform provider may take on the role of importer — with the MDR obligations that accompany that role.
The direction of travel is clear: the EU is progressively extending MDR obligations into the app distribution chain, not just the app itself.
Where Sam Health fits in
Sam's intended purpose is wellness awareness. It collects and visualises the health data your Apple Watch records — heart rate, sleep, activity, and related metrics — and presents trends and patterns over time as lifestyle insights. Sam does not claim to diagnose, detect, predict, screen for, monitor for, or treat any medical condition.
Under the framework established in MDCG 2019-11, software without a medical intended purpose falls outside the scope of EU MDR. Sam is a wellness app, not a medical device. For any health concern, always consult a qualified healthcare professional.
Try Sam HealthSources
- MDCG 2019-11 Rev.1: Guidance on Qualification and Classification of Software in Regulation (EU) 2017/745 – MDR and Regulation (EU) 2017/746 – IVDR. Medical Device Coordination Group, June 2025 (Rev.1 of the original October 2019 guidance). https://health.ec.europa.eu/document/download/b45335c5-1679-4c71-a91c-fc7a4d37f12b_en?filename=mdcg_2019_11_en.pdf. Accessed 17 May 2026. The Rev.1 update retains the same statutory definitions (Articles 2(1) and 2(12) of EU MDR), the same intended-purpose test, and the same structured decision framework cited throughout this article.
- MDCG 2025-4: Guidance on the safe making available of medical device software (MDSW) apps on online platforms. Medical Device Coordination Group, June 2025. https://health.ec.europa.eu/document/download/ec9b0f40-7f82-43a7-b833-ebd45b772eae_en?filename=mdcg_2025-4_en.pdf. Accessed 16 May 2026.
- Regulation (EU) 2017/745 (EU MDR), Article 2(1) (definition of medical device), Article 2(12) (definition of intended purpose), Article 7 (claims). EUR-Lex. https://eur-lex.europa.eu/eli/reg/2017/745/oj/eng. Accessed 16 May 2026.
Frequently Asked Questions
What makes a health app a medical device under EU law?+
Under Regulation (EU) 2017/745 (EU MDR), an app qualifies as medical device software (MDSW) when its intended purpose — as specified by the manufacturer in labelling, instructions, and promotional materials — is one or more of the following: diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease; or diagnosis, monitoring, treatment or alleviation of an injury or disability. The intended purpose is what the manufacturer claims, not what the software is technically capable of.
Can an app be a medical device if it only uses a smartwatch's sensors?+
Yes. Classification depends on intended purpose, not hardware. MDCG 2019-11 includes a worked example of a smartwatch app intended to detect cardiac arrhythmia — it qualifies as MDSW regardless of the fact that it runs on a consumer device. What matters is whether the app makes a medical claim directed at individual users, not which device collects the underlying data.
What is the difference between a wellness app and medical device software?+
A wellness app offers general lifestyle insights, trend visualisation, and personal data awareness without claiming to diagnose, detect, predict, treat, or prevent any specific medical condition. Medical device software (MDSW) makes one or more of those medical-purpose claims for the benefit of individual users. The line is drawn by the manufacturer's stated intended purpose — specifically what appears in their labelling and marketing.
Does a high-risk feature automatically make an app a medical device?+
No. MDCG 2019-11 explicitly states that the risk of harm to users is not a criterion for qualifying software as a medical device. Classification is determined by intended purpose alone. However, once an app is classified as MDSW, its risk class — and the conformity assessment required — depends on the potential consequences of its outputs.
What happens if a wellness app makes a medical claim without CE marking?+
It likely violates EU MDR Article 7, which requires that any claims relating to an intended medical purpose be supported by clinical evidence. Without CE marking for that intended purpose, the claim may not be made. In Germany, the same claim would also trigger HWG and UWG obligations, which carry the additional risk of competitor cease-and-desist actions.
Does EU MDR apply to apps developed outside the EU?+
Yes, if the app is placed on the EU market. EU MDR applies to any medical device available on the EU market regardless of where the manufacturer is based. Non-EU manufacturers must appoint an EU Authorised Representative. MDCG 2025-4 also notes that an EU-based app platform provider may assume the role of importer — with corresponding MDR obligations — when the manufacturer is based outside the EU.
Where can I check if an app is CE-marked as a medical device in the EU?+
Medical devices CE-marked under EU MDR must be registered in EUDAMED — the European database for medical devices — which has a public search interface. MDCG 2025-4 also recommends that app stores create clear separation between MDSW apps and health or lifestyle apps with no medical intended purpose, to help users identify which category they are downloading from.