If you’re building a digital health or wellness product, chances are you’re still in the “ideas, wireframes, and prototypes” phase. Your team is small, budgets are tight, and decisions are made fast. At this stage, most teams simply need someone who can review the product direction early and flag obvious regulatory risks. Especially when it comes to the borderline between consumer wellbeing products and regulated medical devices.
The regulations have a broader reach than most founders expect. Many HealthTech products that are pure software can qualify as medical devices under Swiss or EU law.
Getting the classification wrong can mean placing a non-CE-marked medical device on the market, exposing the company to regulatory enforcement, suspension, removal from market, and liability exposure.
That’s where initial legal and clinical sense‑checking comes in. A focused review early on can help you avoid turning a simple non-clinical or self‑help tool into something that quietly triggers the Medical Devices Regulation (MDR) in Europe or the respective Medical Devices Ordinance in Switzerland. It gives you a clearer, more defensible roadmap for investors and users.
Why MDR catches many HealthTech teams off guard
Many digital health founders are deeply fluent in their problem space and user needs but less familiar with how regulators read the same product. Wording, UX micro‑copy, and even a single feature sketch can send your product from “lifestyle app” toward “medical‑device‑candidate” without anyone in the room realising it.
An initial review is about asking three key questions:
- What is your product actually promising to do for users?
- How might regulators, insurers, or sophisticated partners interpret that promise?
- Are you comfortable with the compliance, liability, and funding implications of that interpretation?
Answering those early helps you build intentionality into your product strategy instead of reacting to regulatory or investor feedback later.
Wellbeing and when MDR starts to matter
At its core, the MDR applies when a product is intended for a medical purpose: diagnosis, monitoring, or treatment of disease or health‑related conditions. In the digital realm, that often shows up when:
- An app or platform claims to detect, predict, or monitor a specific condition.
- Algorithms generate “clinical‑style” recommendations that look like a treatment plan.
- Marketing or UX positions the product as a tool that can manage or replace professional care in certain situations. We discussed similar issues in the context of AI-related marketing claims in our blog post on the EU AI Act and high-risk marketing copy.
Digital consumer health products typically sit in a different zone:
- They support general awareness, self‑care habits, or lifestyle improvements.
- They offer education or guidance without promising specific medical outcomes.
- They stay clear of diagnostic or therapeutic claims and instead frame the experience as “informational” or “empowering”.
In practice, the distinction often comes down to how the product is described and positioned, not just the underlying functionality. For example, describing a feature as “helping users manage stress” creates a very different regulatory impression than saying it “detects anxiety symptoms”. The intended audience also matters: tools marketed to healthcare professionals or designed for clinical workflows are more likely to be viewed as medical devices than products aimed at healthy users.
How a short expert review reduces risk
In the beginning you often just need a short, structured review that looks at:
- Your core product description and value proposition.
- In‑app copy, help content, and onboarding flows.
- Marketing materials, landing pages, and investor decks.
An expert can quickly flag:
- Over‑promising claims that sound like clinical interventions.
- UX patterns that mimic medical workflows without the backing of clinical validation.
- Gaps in basic legal‑health documentation (e.g., disclaimers, consent flows).
It’s much easier to change wording in a prototype than after launch – especially once investors, partners, or users start relying on those claims.
Points to review before launch
You can use a simple framework in your own internal discussions, or when you bring in an external advisor:
- Does your product claim a medical purpose?
- Is this mainly about education, self‑awareness, or general well-being?
- Or is it about clinical‑style detection, monitoring, or treatment for a disease, injury, or disability?
Common trap: Companies sometimes use clinical language in investor materials or on their website without realising it triggers the medical device definition.
- Review your claims and language
- Look at your app copy, landing page, and investor materials.
- Ask: “Would a regulator or cautious partner read this as a medical‑device‑style claim?”
- Think through your risk appetite
- Are you comfortable staying in the wellbeing zone for the next 12–18 months?
- Or are you actively planning to invest in clinical validation and regulatory pathways later?
- Bring in an expert
- Book a limited‑scope session with a legal or regulatory‑health advisor.
- Share your intended‑use statement, key copy, and a high‑level feature map.
- Ask them to flag: unclear claims, regulatory red‑flag wording, and minimal viable documentation you should consider.
- Document and iterate
- Capture the feedback in a simple internal checklist or memo.
- Revisit it before major releases, partnerships, or fundraising conversations.
This is about building clarity and resilience into your product so that you can make product decisions with a clearer understanding of the regulatory implications.
How to get started with an initial assessment
If you’re building a digital health product and want to make sure you’re not accidentally drifting over the line from general wellbeing into MDR territory, even a limited review can help identify issues early.
In the beginning, the goal is usually not a full regulatory analysis. What helps most is having someone review the product positioning, claims, and onboarding flow before those decisions become embedded in the product or marketing.
In many cases, a brief discussion is enough to identify wording or feature choices that could later create unnecessary MDR exposure.
LEXR regularly works with HealthTech and MedTech teams that are still refining product scope and positioning. Whether you need a short review of your product positioning, help drafting essential legal‑health documentation, or guidance on when and how the MDR, Medical Devices Ordinance, or IVDR might start to apply, a targeted engagement can give you a solid foundation.