Product Compliance And Certification For Wearable Medical Device In The Eu

Scope and evidence must be confirmed before any paid tests or filings.

A wearable is not a separate EU regulatory class. A wristband, adhesive patch or smart ring may be a wellness product, an MDR medical device, a medical-device accessory or part of a combined system. The route follows the manufacturer’s intended medical purpose, the functions and the evidence—not the word ‘wearable’ or an existing CE mark on a radio module.

Use this map for a product sold or supplied in the EU, including a sensor, firmware, companion application and cloud alarms. The example outcomes are decision prompts, not final classifications. Freeze the marketed claims and the complete configuration before selecting a notified body or ordering tests.

Wearable claims that change the regulatory question

Proposed function or claim	Classification question	What remains open
“Show heart rate during exercise” with no medical claim	Is the intended purpose solely fitness or wellbeing?	Not automatically an MDR device; assess applicable consumer, radio and environmental legislation.
“Detect possible atrial fibrillation” from wrist signals	Does the medical diagnostic alert make the hardware, software or combination an MDR device?	Review device qualification, clinical evidence and Rules 10/11; do not assign class by sensor type alone.
“Alert a clinician to dangerous respiratory deterioration”	Are vital parameters monitored where variation may mean immediate danger?	Rules 10/11 may raise the class; document intended patients, alert latency and action consequences.
“Adjust medication delivery from continuous sensor data”	Does an active therapeutic system have integrated diagnostic decision-making?	Assess Rules 9/12/22 as applicable, as well as software and delivery hazards; no class follows automatically.

Claims in advertising, app-store text, instructions and clinical evaluation must be consistent. A disclaimer such as “not for diagnosis” cannot neutralise an otherwise medical intended purpose.

Classify the sensor, clinical software and combined function

Under MDR Article 2, qualification depends on the intended medical purpose. Under Annex VIII, consider Rule 10 for active diagnostic/monitoring devices, Rule 11 for medical device software (including decisions and physiological monitoring), and other applicable rules such as 9, 12 and 22 for therapeutic or integrated functions. Apply the implementing rules and the highest resulting class where several rules apply. A medical-device software component may be classified separately when independent; software driving or influencing a device follows the Annex VIII implementing rule.

Do not treat every pulse sensor as Class IIa, every AI output as Class III or every wellness watch as exempt from all CE rules. The distinction between measurement, clinical interpretation, alarm and automatic treatment determines the evidence and whether a notified body is required. Under MDR Article 52, most Class I devices self-declare, subject to specified exceptions; Class IIa, IIb and III ordinarily require a notified body.

EU cross-regime decision matrix for a connected wearable

Regulatory layer	Wearable-specific trigger	Decision / important exception
MDR 2017/745	Medical intended purpose, accessory or covered system	Classify function and software; risk management, clinical evaluation, technical file, conformity assessment, CE, PMS and vigilance.
RED 2014/53/EU	Bluetooth, Wi-Fi, cellular or another intentional radio transmitter	Assess spectrum, electrical safety and EMC. The extra RED Art. 3(3)(d)–(f) cyber requirements under Regulation 2022/30 do not apply to radio equipment also covered by MDR; RED itself may still apply.
RoHS / WEEE	Electrical or electronic wearable and its end-of-life stream	Check substance restrictions, any relevant exemptions, separate collection and national producer duties; medical status is not a blanket exemption.
Batteries Regulation 2023/1542	Rechargeable or primary battery incorporated in the wearable	Screen battery obligations and design for Article 11 removability from 18 February 2027; verify precise safety/data-integrity derogations and any later amendments.
GDPR 2016/679	Identifiable wearer or patient data, including health data	Set controller/processor roles, legal basis, Article 9 condition where needed, data security and retention; MDR CE is not a GDPR authorization.
EU AI Act 2024/1689	AI model performs medical interpretation or supports safety-critical decisions	Check whether it is an AI system, high-risk status and obligations applicable on the actual launch date; MDR class and AI Act status are different tests.
Cyber Resilience Act 2024/2847	Separate product with digital elements and network connectivity	Art. 2(2) excludes products to which MDR applies; recheck stand-alone non-MDR components instead of asserting CRA for every connected medical wearable.

For an AI system that is a regulated medical product or its safety component, AI Act Article 6(1) and Annex I require, among other conditions, third-party conformity assessment under the applicable product legislation for that high-risk route. An AI feature alone does not establish high-risk status. Following Regulation (EU) 2026/1744, the Chapter III Sections 1–3 high-risk requirements for Article 6(1)/Annex I systems apply from 2 August 2028; the separate Article 6(2)/Annex III route applies from 2 December 2027. Other AI Act duties may already apply; verify each provision and any transition rules.

Assess the RED delegated cybersecurity exclusion for each item of radio equipment, not for the commercial bundle in the abstract. A consumer smartwatch used by an MDR medical app does not automatically become radio equipment subject to MDR; if it remains outside MDR, independently check its applicable RED Article 3(3)(d)–(f) requirements. The medical app is not a blanket exemption for the watch.

For a sealed wearable patch, first confirm that the cell is a 'portable battery' within Article 11. From 18 February 2027, Article 11(1) generally requires end-user removability and replaceability. Article 11(2) permits independent-professional replacement (not permanent non-replaceability) for listed products, including professional medical imaging/radiotherapy equipment and IVD devices; it is not a blanket medical-device exemption. Article 11(3) separately disapplies paragraph 1 only where permanent battery connection and continuous power are necessary for user/product safety, or for data integrity when collecting and supplying data is the product's main function. Record battery category, servicing method and the evidence for any specific derogation; recheck amendments before launch.

When a consumer watch or cloud service becomes part of the medical evidence

Map the regulated system boundary: sensor, attachment and skin interface; embedded software; radio link; supported phone/OS; cloud processing; clinical dashboard; algorithm and alerts. Identify which party makes each medical claim and which elements are devices, accessories or ordinary consumer hardware. MDCG 2023-4 specifically addresses medical software working with hardware that is not itself an MDR device.

If a medical app depends on a general-purpose smartwatch sensor, consumer CE marking does not prove that the combination meets the claimed clinical performance. Validate intended models, firmware versions, signal quality, disconnected operation, false alarms, update pathways and responsibility for changes. A separate CE-marked radio module also cannot substitute for conformity assessment of the complete medical function.

MDCG 2023-4 distinguishes an MDR medical device/accessory used with the software from non-MDR consumer hardware. In the latter case, the medical-software manufacturer cannot rely on the hardware's MDR conformity and must substantiate the safety, performance and reproducibility of the intended combinations. MDCG guidance interprets existing requirements; it is not itself binding legislation.

Wearable-specific evidence pack before conformity assessment

Create a traceable package that ties every claimed clinical output to a specific configuration and test result:

Claims and intended-purpose register: patient group, conditions, users, environments, indications, exclusions, clinical actions and every app-store/marketing statement.
Architecture and supplier boundary: components, firmware, phones, cloud, data flows, radio frequencies, battery chemistry, software/AI versions and owner of each safety function.
Classification memorandum: device/accessory/software boundaries; each relevant Annex VIII rule; rationale for class and notified-body pathway.
Safety and performance evidence: sensor accuracy across movement and skin conditions; skin-contact biological risks; electrical/EMC/radio testing; battery and usability hazards.
Clinical and software evidence: clinical evaluation, representative users and settings; algorithms, datasets, verification/validation; alarm sensitivity, false positives and time to action.
Operational controls: cybersecurity threat model, vulnerability/patch management, traceability, post-market surveillance, incident reporting and supplier change notifications.

Standards such as EN ISO 14971, EN IEC 62304, EN IEC 62366-1, relevant EN IEC 60601 standards and EN ISO 10993 series may provide methods of demonstrating conformity where applicable. A standard is not itself an additional law; check applicability, edition and harmonised status rather than asserting that every listed test is compulsory.

Label, registration and launch gates

Do not treat “CE certified” as one generic permit. Close these interdependent gates in order:

Agree final claims, intended use, device/software boundaries, classification and all other applicable EU acts before quoting a certification route.
Establish manufacturer duties and QMS, technical documentation and clinical evaluation. Engage an MDR-designated notified body if the classification/procedure requires one; verify its designation scope.
Identify non-EU manufacturer’s EU authorised representative if relevant; map importer and distributor responsibilities, including complaint and traceability channels.
Prepare EU declaration(s) of conformity, CE marking and notified-body number where applicable; verify UDI, registration and the EUDAMED modules mandatory since 28 May 2026.
Approve patient-facing labels/IFU and risk warnings in Member-State-required languages, any applicable separate radio/battery/WEEE information, and a workable PMS, vigilance and update plan.

The four EUDAMED modules mandatory since 28 May 2026 do not create four manufacturer filing duties: relevant economic operators register as actors, manufacturers register devices/UDI where required, notified bodies enter certificate information, and the Market Surveillance module serves competent authorities and the Commission. Vigilance and clinical-investigation modules were not among these four mandatory modules. Check transitional provisions for existing devices and records.

Offshore hosting or a non-EU manufacturer does not automatically remove a cloud diagnostic service from the MDR. Under Article 6(1), devices offered by information-society services to a person established in the Union must comply. Under Article 6(2), a device not placed on the market but used in a commercial activity to provide a diagnostic or therapeutic service offered to such a person—whether paid or free, directly or via an intermediary—must also comply. Establish who is offered the device or service, where the recipient is established, the clinical intended use and the device actually used; mere data hosting is not in itself proof of qualification.

Changes that reopen the wearable compliance assessment

Reassess qualification, class, evidence and regulatory layers when an update changes medical purpose or risk. Use a controlled impact review rather than treating all changes as “minor software updates”.

New arrhythmia or dosing claim, different user group or home-to-hospital deployment.
New optical sensor, adhesive, wearable placement, battery design or supported watch/phone model.
AI model retraining, changed alert threshold, cloud outage behaviour, radio design or material cybersecurity finding.

Scope boundary and related route

This page owns the wearable cross-regime route—not a full restatement of the general MDR conformity assessment procedure. For the wider medical-device framework, see the EU medical-device compliance route.

Wearable medical device: specific questions

Does measuring pulse or oxygen saturation automatically make a smartwatch an EU medical device?

No. Qualification depends on intended medical purpose, including promotional and software claims. A diagnostic or disease-monitoring claim can change the outcome; the measurement alone cannot establish the MDR class.

Can an AF-detection app rely on the consumer smartwatch’s existing CE marking?

Not by itself. The manufacturer of the medical function must support safety and clinical performance for the defined sensor, firmware and app configurations, and classify the medical device software or combination.

Does Bluetooth mean an MDR wearable must meet the extra RED cybersecurity clauses?

The RED may apply to its radio functions, but Delegated Regulation (EU) 2022/30 Article 2(1) excludes equipment also subject to MDR from the specific Art. 3(3)(d)–(f) requirements. MDR cybersecurity duties still matter.

May a sealed medical patch keep a non-user-replaceable battery?

Do not assume a blanket medical-device exemption. Battery Regulation Article 11 applies from 18 February 2027 and contains narrowly framed derogations; document the exact safety, design or data-integrity basis and recheck the rules in force.

Does MDR CE marking allow processing identifiable patient readings?

No. GDPR duties need a separate analysis of parties, lawful basis, any Article 9 health-data condition, security, notices and transfers.

Is an AI-based deterioration alert automatically Class III or already fully subject to the AI Act high-risk regime?

Neither follows automatically. Determine the MDR class from intended clinical use and consequences under Annex VIII, then separately test AI Act definitions, risk criteria and the provisions applicable on the placing-on-market date.