EU MDR qualification and borderline products

The MDR definition of a medical device turns on the manufacturer's intended use for humans and the specific medical purpose claimed. Check the label, instructions for use, promotional and sales statements, product specifications, clinical evaluation plan, website claims, sales training, and release notes before relying on an internal label such as wellness, cosmetic, analytics, platform, or accessory.

A product points toward MDR qualification when the intended purpose is diagnosis, prevention, monitoring, prediction, prognosis, treatment, or alleviation of disease; diagnosis, monitoring, treatment, alleviation, or compensation for injury or disability; investigation, replacement, or modification of anatomy or a physiological or pathological process or state; or information from in vitro examination of human specimens. The principal intended action must not be pharmacological, immunological, or metabolic, although those means may assist the device.

If the product is not itself a medical device, test whether it is an accessory. Under the MDR, an accessory is not itself a medical device but is intended to be used with one or more particular medical devices to enable their intended purpose or directly assist their medical functionality. Cables, controllers, consumables, connectors, apps, and service components therefore need a specific device-function link; a general healthcare customer base is insufficient.

For software, apply the MDCG software qualification steps. Software that only stores, archives, communicates, losslessly compresses, or performs simple search is not qualified on that basis alone. Software that acts on data for the benefit of individual patients, drives or influences a hardware device, functions as an accessory, or is an Annex XVI product can fall into the medical devices framework and then needs classification.

Annex XVI products are different: they are listed product groups without an intended medical purpose that the MDR brings in once common specifications apply. Examples based on the common specifications include non-corrective contact lenses, products introduced into the body to modify anatomy, dermal fillers, adipose-tissue reduction equipment, high-intensity optical radiation equipment for skin treatment, and non-invasive brain-stimulation equipment. If the same product has both medical and non-medical purposes, keep both requirement sets in the file.

Borderline files should explain why the MDR route, another EU route, or an escalation path applies. The MDR expressly excludes IVDs covered by Regulation (EU) 2017/746 and medicinal products covered by Directive 2001/83/EC, with principal mode of action central to the medicinal-product boundary. Where a device incorporates an IVD part, MDR governs the device while IVDR requirements apply to the IVD part.

For MDSW whose output fulfils both the MDR and IVDR definitions and uses IVD and medical-device data, MDCG 2019-11 uses the significance of the data sources for the intended purpose to decide whether the software belongs under MDR or IVDR. If the intended purpose is substantially driven by IVD data sources, the IVDR route is indicated; if substantially driven by medical-device data sources, the MDR route is indicated.

A company qualification memo records the manufacturer's rationale; it is not a binding Union-wide scope decision. Article 4 allows the Commission, after consulting the MDCG, to determine by implementing act whether a product or product group meets the medical-device or accessory definition. Member State competent authorities handle case-specific market questions, while MDCG guidance and the borderline manual are non-binding interpretive aids.

Where GPSR, cosmetics, machinery, or general product-safety law raises a genuine boundary question, record the product facts and controlling legal provision. Resolve the boundary before choosing the classification and conformity route.

A yes-scope answer is not enough for market release. Once the file concludes that the product is an MDR device, accessory, MDR medical device software, or Annex XVI product, route it into MDR classification, technical documentation, clinical evaluation or safety evidence, and conformity assessment planning.

For software, MDCG 2019-11 points from qualification into Annex VIII classification. Software that drives or influences another device falls in the same class as that device; independent software is classified in its own right; and if several rules or sub-rules apply, the higher classification applies. Rule 11 is the central software rule for information used for diagnostic or therapeutic decisions and monitoring physiological processes.

For Annex XVI products, the implementing regulation requires documented risk-management responsibilities, criteria, records, lifecycle updates, and information supplied with the product. Information for a non-medical purpose should not carry clinical-benefit claims; mixed medical and non-medical products need the claims separated.