Is Your Product a Medical Device? Understanding MDR Scope and Definitions

The net is wider than you think

A lot of companies discover they have a medical device problem when they were not expecting one. MDR casts a wide net — almost anything with a claimed or implied medical purpose qualifies, whether it touches the body or not. Software that helps clinicians interpret diagnostic results. Apps that track symptoms for medical use. Hardware that measures physiological parameters. Accessories that support a device already on the market. All of these can fall under MDR, and the definition does not require physical contact with a patient.

The definition in Article 2(1) is broad by design: a product qualifies if it is intended to diagnose, prevent, monitor, predict, treat, or alleviate disease or injury — or to examine, replace, or modify anatomy or a physiological process. That covers an enormous range of products. What it specifically excludes is products that achieve their principal intended action by pharmacological, immunological, or metabolic means. Those are medicinal products. The borderline between drugs and devices is one of the most contested areas in MDR practice, and it trips up combination products regularly.

Where teams run into trouble

The most common mistake is relying on how the product has always been described internally rather than on what it actually does and how it is being marketed. MDR scope follows intended purpose — not just technical function. If your website, IFU, or sales materials imply a medical use, regulators will read that as a medical claim, even if the product is technically general wellness.

Another trap is accessories. An accessory to a medical device is itself regulated as a medical device under MDR Article 2(2), even if the accessory has no medical function on its own. A carrying case that is specifically designed to maintain a device's sterility, or a calibration tool that is only used with a regulated device, can pull the accessory into scope. Teams that manage accessories separately from their device portfolio often find scope issues late in the compliance process.

Borderline products — those sitting between medical devices and cosmetics, wellness products, or food supplements — require a formal borderline determination. MDCG has published guidance on this (MDCG 2022-5 on borderline and classification), but the guidance does not resolve every case. When in doubt, the assumption should be that the product is in scope until you can document otherwise.

Software and in vitro diagnostics

Software gets its own specific attention under MDR. MDCG 2019-11 (updated) provides a decision tree for determining whether software qualifies as a medical device or an IVD. The key question is whether the software performs an action on data that goes beyond storage, archiving, retrieval, or simple search — and whether that action is for a medical purpose. Software that calculates a dosing recommendation, flags an abnormal result, or supports a clinical decision typically qualifies.

IVDs sit under a separate regulation — IVDR (EU 2017/746) — rather than MDR. If your product is used to examine specimens derived from the human body for diagnostic purposes, IVDR is the applicable framework. MDR and IVDR share significant structural similarities, but they are separate regulations with different Annexes, different Notified Body requirements, and different timelines. Getting this distinction wrong early creates a lot of rework.

What to do if you are not sure

Document your reasoning. Regulators and Notified Bodies are not expecting manufacturers to get every borderline case right on the first attempt — they are expecting manufacturers to show they have thought it through carefully and reached a reasoned conclusion. A brief borderline/scope analysis in your technical file or quality system is far more defensible than no documentation at all.

The EU MDR does not include a formal pre-classification service the way some national competent authorities do, but many national authorities (BfArM in Germany, ANSM in France, MHRA post-Brexit) will provide informal or formal opinions on scope. For complex cases, this is worth pursuing before committing to a compliance pathway.