Mental health products often start with a simple idea. A team wants to help people track their mood, understand stress, build healthier habits, or access structured self-help content. At that stage, the product may look like a wellness app.
But the regulatory question changes when the product starts to assess symptoms, guide decisions, recommend interventions, or support the management of a recognised mental health condition. That is when the product may move from general wellness software into mental health SaMD.
The difference is not always obvious from the interface. A mood tracker and a regulated product can both ask users how they feel. A journaling app and a therapeutic support tool can both include exercises.
The real question is what the product is intended to do, what it claims to do, and what the user is expected to do with the output.
What is a mental health SaMD?
A mental health SaMD is software intended to perform a medical purpose in the field of mental health, without being part of a hardware medical device. Under the EU MDR, software can be considered a medical device when it is intended for a medical purpose, such as diagnosing, monitoring, treating, or alleviating disease. The MDR also states that software is considered an active device.
In practice, a mental health SaMD may assess symptoms, monitor changes in a condition, support treatment, provide clinically relevant recommendations, or help manage a diagnosed mental health condition.
This does not mean every mental health app is a mental health SaMD.
An app that helps users write down thoughts, follow general mindfulness content, or build daily habits may remain a wellness product, as long as it does not make medical claims or generate outputs that guide clinical decisions. The key point is purpose.
If the product is positioned as general support for wellbeing, it is more likely to sit in the wellness category. If the product is positioned as helping diagnose, monitor, treat, alleviate, or manage a mental health condition, it should be assessed as a potential mental health SaMD.
Why the distinction between wellness software and mental health SaMD matters
The distinction matters because wellness software and mental health SaMD follow very different regulatory paths.
A wellness product may still need to comply with data protection, cybersecurity, consumer protection, and advertising rules. But it is not automatically subject to medical device requirements. A mental health SaMD is different.
If the software qualifies as a medical device under the EU MDR, the manufacturer needs to consider qualification, classification, conformity assessment, clinical evaluation, risk management, post-market surveillance, and technical documentation.
This can affect the product roadmap, claims, evidence strategy, and time needed to enter the market.
It can also affect fundraising and commercial partnerships. Investors, healthcare providers, and insurers often want to know whether a product is a wellness tool or a mental health SaMD before they decide how to evaluate it.
Intended purpose is the starting point
For mental health software, the intended purpose is usually the most important question.
The intended purpose is not only what the team says internally. Under the EU MDR, it is reflected in the label, instructions for use, promotional or sales materials, statements, and clinical evaluation.
This is why two products with similar features can be categorized differently.
One app may say:
“Track your mood and reflect on daily patterns.”
Another app may say:
“Assess symptoms of depression and receive personalised recommendations to manage your condition.”
The first statement sounds like wellness.
The second statement points much closer to mental health SaMD because it connects the product output to a recognised condition and a management purpose. The same feature can be low risk in one context and regulated in another. Mood logging is not automatically a medical device function. But interpreting mood data to flag deterioration, classify symptom severity, or recommend condition-specific interventions can change the analysis.
Clinical claims can turn wellness software into mental health SaMD
Claims are often where the boundary becomes clear. Wellness claims usually focus on general well-being.
For example:
- supports emotional wellbeing
- helps you build healthier routines
- encourages reflection
- supports mindfulness
- helps you understand daily stress patterns
These claims are broad, as they do not say the product diagnoses, treats, prevents, or manages a mental health condition.
Claims that may point towards mental health SaMD are more specific.
For example:
- assesses depression symptoms
- helps manage anxiety disorder
- reduces symptoms of PTSD
- recommends therapeutic exercises based on symptom severity
- monitors relapse risk
- supports treatment decisions between sessions
- identifies users who may need clinical support
These claims do not need to appear only in formal documentation. They can appear on the website, in app store screenshots, onboarding flows, pitch decks, user emails, or sales conversations. If the market understands the product as a tool for a mental health condition, it becomes harder to defend it as a general wellness product.
Functionality matters too
Features alone do not determine classification, but functionality is also important. A product that stores information without changing it is usually easier to position as wellness. For example, an app that allows users to record mood, export notes, or read fixed educational content may have limited regulatory functionality.
The analysis changes when the product processes user inputs and produces personalised, interpretive, or directive outputs.
For example, the product may:
- calculate a symptom score
- classify a user as low, moderate, or high risk
- suggest a specific exercise based on reported symptoms
- recommend seeking professional care
- prioritise users for clinician review
- adapt a programme based on deterioration or response
This type of functionality can make the product look less like passive wellness software and more like mental health SaMD.
The important question is not only whether the product collects data.
The question is what it does with that data and what the user is expected to do next.
Marketing and user expectations
A product may be designed as a wellbeing tool, but if the website says it helps users manage depression, reduce anxiety symptoms or prevent relapse, the product may be understood differently.
The same applies to user profiles. If the product is mainly used by people with a diagnosed mental health condition, or sold to clinics as part of care delivery, it may be harder to argue that the product is only a general wellness tool.
This does not automatically mean the product is a mental health SaMD, but it does mean the manufacturer should reassess the intended purpose, claims, user population, and output before going further.
Examples of wellness products and mental health SaMD
A wellness product may include a mood journal, breathing exercises, sleep hygiene tips, habit tracking, and general educational content.
It may help users feel more organised, more reflective, or more aware of patterns in their daily life.
A mental health SaMD may use similar inputs, but the output is different.
For example, a mental health SaMD may assess symptoms of depression, support the management of anxiety disorder, recommend structured interventions based on a user profile, or monitor whether a patient is deteriorating between clinical appointments.
The difference is not whether the product feels clinical.
The difference is whether the product has a medical purpose.
A calm interface does not make a product wellness. A simple questionnaire does not make a product regulated by itself. What matters is the intended purpose, claims, functionality, and clinical relevance of the output.
How software classification can affect the next steps
Once software qualifies as a medical device, classification also needs to be considered. Under EU MDR Rule 11, software intended to provide information used to make decisions for diagnosis or therapeutic purposes is generally classified as class IIa, unless the potential impact of those decisions places it into a higher class.
For a mental health SaMD, this means the regulatory pathway should be considered early. Classification can influence the level of evidence, the conformity assessment route, the role of a notified body, and the content of the technical documentation.
This is why qualification should not be treated as a late legal question. It is a product strategy question.
Is your product a mental health SaMD?
A practical way to assess the product is to step back from features and ask two questions.
First, what is the product intended to do?
Second, what is the user expected to do with the output?
If the product supports general well-being, provides fixed content, and gives users space to reflect, it may remain a wellness product.
If the product assesses symptoms, identifies deterioration, recommends interventions, supports management of a recognised condition, or influences care decisions, it may be a mental health SaMD. The boundary is not always obvious, but it becomes clearer when the team looks beyond features and focuses on intended purpose, claims, user population, and output.
Need help determining whether your product is a mental health SaMD?
Before building the regulatory strategy, you need to define the product correctly. Aura Health supports digital health teams in understanding whether their software is a wellness product, medical device software, or mental health SaMD.
This includes intended purpose review, claims assessment, MDR qualification, classification strategy, technical documentation planning, and clinical evaluation support.
The earlier this question is addressed, the easier it is to avoid rework. If you are developing a mental health product and are unsure whether it qualifies as a mental health SaMD, schedule a 30-minute free consultation with our team.