Articles Questions

Updated May 31, 2023

Can We Bring a Lifestyle Device to Market First?

Dr. Oliver Eidel


We’re developing software as a medical device which might be class I or IIa under the MDR. Right now, we don’t want to go through all the regulatory pain and are wondering whether we can bring it to market as a “lifestyle”, non - medical device first. Is that possible?

Short Answer

Yes! With some limitations though.

The most important one is that the product which you bring to market must not fulfil the definition of a medical device. Specifically, it shouldn’t do diagnosis, therapy, monitoring or prevention of a disease (the actual definition is longer, of course).

If you manage to “water down” your product to something which does not fulfil this definition of a medical device, it just becomes just another normal software on t he planet and you can bring it to market any time!

Long Answer

Let’s look at some examples as my short answer above was rather abstract.

Example 1: App For Psychotherapy

Everyone seems to be developing apps for psychotherapy-like use cases nowadays, so this could be a widely applicable example. Assuming you are developing software which should treat a mental disease (e.g. depression, anxiety disorder, etc.), well, that’s clearly a medical device, because you’re doing therapy of disease, among other things.

Okay, so far so good. But if you change your content and description of your app from “treating depression” to “reducing stress”, then, suddenly, you’re no longer a medical device, because “stress” is not a disease (at least in the ICD-10 code.. I think?). In other words, you’re simply an app like all those meditation apps out there.

Obviously you shouldn’t hide things here - if you claim to only reduce stress, then all your content inside your app should mirror that message - you shouldn’t have content in your app which suddenly claims to treat depression (duh).

Now, does this even make sense if you have to change so much in your app? I’d argue that, yes, in many cases, this might make sense, because from a product perspective, you can test many things: You can test whether users generally like your app, whether they would be willing to pay for it if you offer additional purchases, and whether it actually delivers value (do people like it because it truly reduces their stress levels?).

All of these things are very hard to test when developing a medical device because you’re essentially blind until you release your first version, and that might take quite a while because you’re slowed down by regulatory compliance work. And, arguably, there’s an overlap between the lifestyle app and medical device app of things you might want to test: Do people regularly use these sort of apps or do they uninstall them? What amount of money are people willing to pay? etc.

Of course this doesn’t work for all scenarios. If your software is meant to treat people with schizophrenia, then, well, I don’t know how a watered-down lifestyle version of that might look like. Maybe you’re more creative than me here.

Example 2: Sleep Tracker

This is a really cool example. Tracking someone’s sleep with software does not automatically make your product a medical device. It depends on your intention behind that sleep tracking (your intended use, as regulatory people call it). If it’s for optimizing your performance as an athlete, it’s not a medical device. If it’s for improving your meditation practice, it’s also not a medical device. If it’s for detecting sleep apnea, well, then it’s a medical device (= diagnosis / monitoring of disease). You get the idea?

Now - if your software can detect sleep apnea, does that make it a medical device? No! It depends on what you display to the user. If you e.g. only display “sleep interruptions” to the user and don’t mention sleep apnea anywhere, then it’s still a lifestyle device. If you display “sleep apnea events” to the user, well, then you’re a medical device again.

Why all these specific examples? Because that’s pretty much what Emfit, a Finnish company, did, and it’s perfectly legal (as far as I can tell, not a lawyer, obviously): You could buy their “personal” sleep tracker for “hobby” use to track your sleep data (like for those quantified self people), or you could buy their “certified” sleep tracker for detecting sleep apnea events. As far as I could tell, the devices looked really, really similar, or were even identical - only the software would differ slightly for the certified version. The hobby version would not include any mention of sleep apnea.

(Their product lineup seems to have changed in the meantime - maybe there were hit by the MDR class I up-classification fiasco, no clue)


So there you have it. Is bringing a medical device to market as a lifestyle device always possible? No, definitely not. But, in many cases, you can bring a similar product to market to test your business and product assumptions, and that might provide your company with valuable user feedback.

Again, it’s all about not fulfilling the definition of a medical device.

One More Thing

Ah, and one more thing: Don’t do shady things like “our app treats depression but it states it’s not a medical device everywhere” - no, dude, just because you state it, your app won’t magically become a lifestyle device. It’s really about what it’s used for - that’s what counts.

On a slighty different note: You want to get your medical software certified under MDR but don't know where to start? No worries! That's why we built the Wizard. It's a self-guided video course which helps you create your documentation yourself. No prior knowledge required. You should check it out.

Or, if you're looking for the most awesome (in our opinion) eQMS software to manage your documentation, look no further. We've built Formwork, and it even has a free version!

If you're looking for human help, did you know that we also provide some limited consulting? It's limited because we are not many people. We guide startups from start to finish in their medical device compliance.

Congratulations! You read this far.

Get notified when we post something new.

Sign up for our free newsletter.

Dr. Oliver Eidel

I'm a medical doctor, software engineer and regulatory dude. I'm also the founder of OpenRegulatory.

Through OpenRegulatory, I've helped 100+ companies with their medical device compliance. While it's also my job that we stay profitable, I try to dedicate a lot of my time towards writing free content like our articles and templates. Maybe that will make consulting unnecessary some day? :)

If you're still lost and have further questions, just send me an email.

Read more about me here.

Digital Health Jobs No Cookie For You Privacy Policy Imprint
No QMS on this planet will save you from creating crappy software.