Product Compliance And Certification For Wearable Medical Device In Italy

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

A wearable sold in Italy is not classified by its shape. The decisive facts are its manufacturer-stated intended purpose, the clinical claim, who receives the output and what action it supports. A step counter and a watch that flags possible atrial fibrillation may look alike but demand different compliance decisions.

This is a product-specific route map, not a class determination or a certificate. Before ordering tests or printing CE labels, freeze the wearable–app–cloud configuration, review the advertising and user instructions, and identify which legal regimes apply to each supplied component.

First decide what the wearable is claiming

Under MDR Article 2, a product intended for diagnosis, prevention, monitoring or treatment of disease can qualify as a medical device. A generic fitness purpose does not automatically do so; merely calling a device ‘wellness’ does not neutralise specific medical promises.

Compare packaging, website, app-store text, clinical dashboards and sales demonstrations; record any inconsistent medical claims.
Describe sensors and outputs: raw heart rate versus arrhythmia suspicion, steps versus fall alerts, trends versus treatment recommendations.
Identify intended patients and users, environment (home/ward), wear time, alarm urgency and consequences if a reading is missed or wrong.
Define separately the strap/sensor, firmware, companion app, cloud algorithm and charger; determine whether software is integral, an accessory or a distinct medical device.

Four wearable configurations — four different questions

These are classification prompts, not automatic assignments to MDR classes. Apply Annex VIII, including the active-device rules and Rule 11 where relevant, to the finished intended purpose.

Configuration	Decisive question	Evidence to obtain
Sports band showing steps and general fitness trends	Are all claims non-medical, including alerts and marketing? If yes, MDR may not apply; product law still can.	Claims register, app screens, technical architecture, radio/battery inventory.
Wrist ECG with ‘possible AF’ notification	Is it intended to detect/monitor a medical condition, and are algorithmic conclusions a separate software function?	ECG accuracy against reference, clinical-validation design, false-alert analysis, firmware/app versions.
Connected patch monitoring vital signs for clinicians	Does continuous monitoring or an alarm concern parameters whose variation could create immediate danger? Assess active monitoring and alarm rules.	Alarm thresholds and latency, sensor dropouts, clinical workflow, human-factors and risk files.
General-purpose watch connected to a medical app	Who is manufacturer of each regulated function, and does the app transform data into patient-specific medical information?	Hardware–software interface specification, intended-purpose statements, integration and update contracts.

Multi-regime decision matrix for the Italian launch

Medical CE marking does not erase other applicable obligations; each row below needs a documented scope decision. A single product may meet several legal acts, without several unrelated ‘medical licences’.

Layer	Trigger / boundary	Launch implication
MDR 2017/745	Medical intended purpose of wearable, accessory or qualifying software; risk class under Annex VIII.	Choose Article 52 conformity path; notified body for IIa/IIb/III and specified class I features; clinical evaluation, risk/QMS, UDI, CE and surveillance.
Companion software	App/cloud creates medical conclusions or drives a regulated device; MDCG 2019-11 rev.1 and 2023-4 are non-binding guidance.	Decide integral versus separately regulated software; verify Rule 11, hardware combinations, interoperability and controlled updates.
Radio / electrical	Bluetooth, Wi-Fi or cellular radio normally triggers RED 2014/53/EU; no-radio designs need their own EMC/electrical scope check.	Test spectrum, EMC and radio safety as applicable. RED incorporates low-voltage safety objectives without a voltage floor; do not automatically apply LVD separately to radio equipment.
Materials / end of life	Electronic components, batteries, skin-contact materials and packaging.	Assess RoHS, applicable battery/WEEE and chemicals duties and Italian producer-responsibility arrangements; medical status is not a blanket exclusion.
Personal health data	Identifiable physiological/health data sent to an app, clinician or cloud.	Assess GDPR lawful basis and Article 9 condition, controller roles, security, transfers and whether a DPIA is required; CE marking does not authorise processing.
Cyber / AI perimeter	Networked software or AI may attract additional law; MDR/IVDR products are excluded from CRA scope under CRA Article 2(2).	Apply MDR cybersecurity duties; check CRA only for distinct non-MDR digital products and AI Act applicability separately rather than assuming all connected wearables are CRA products.

Radio-cyber boundary in 2026: Delegated Regulation (EU) 2022/30 activates RED Article 3(3)(d)–(f) cybersecurity requirements for certain radio wearables, but its Article 2(1) expressly exempts radio equipment also subject to the MDR or IVDR from those additional requirements—not from RED radio, EMC or safety rules. Do not extend the exemption automatically to a separately marketed non-medical watch or radio accessory. Regulation (EU) 2026/339 repeals the delegated act only from 11 December 2027; MDR cybersecurity responsibilities remain.

AI Act timing: an algorithm is not high-risk solely because it uses AI. Check Article 6(1) of Regulation (EU) 2024/1689: is the AI system itself a product or a safety component within the listed product legislation, and does the product require third-party conformity assessment? Following Regulation (EU) 2026/1744, the high-risk obligations for Article 6(1) product AI systems are scheduled to apply from 2 August 2028; other AI Act rules may apply earlier. Keep the MDR clinical and software requirements in force independently.

Wearable-specific evidence: minimum design-review pack

Request these records before choosing a laboratory or notified body. They translate the promised medical outcome into verifiable evidence and reveal when a hardware change invalidates the app evidence.

Evidence unit	What to preserve / test
Claims-to-function trace	Intended-purpose statement, claim screenshots by language/channel, patient group, output-to-clinical-action map; link each claim to verification and clinical evidence.
Signal & body interface	Sensor accuracy across skin tone, motion, placement, sweat and wear duration where relevant; skin-contact safety, usability, charging/thermal hazards.
Software & interoperability	Locked firmware/app/model versions, dataset and validation limits, false positives/negatives, offline behaviour, Bluetooth loss, cloud latency, alarm escalation.
Clinical and quality dossier	MDR Annexes I–III/ XIV as applicable: risk-benefit, clinical evaluation, technical documentation, QMS, PMS/PMCF plan, complaint and vigilance pathway.
Industrial and traceability map	Bill of materials, radio module and battery evidence, critical suppliers, manufacturing changes, UDI-DI/Basic UDI-DI strategy, label artwork and translation control.

Italy-specific labeling and registration dependencies

Italian Legislative Decree 137/2022, Article 6(2), requires the written information supplied by the manufacturer to users and patients under MDR Annex I section 23 to be in Italian on delivery to the final user, including professional use. Review labels, warnings and instructions; app safety information should be assessed against the same real-use risk, without assuming every interface field has an identical statutory translation rule.

Since 28 May 2026, four EUDAMED modules have been mandatory: Actor registration, UDI/Device registration, Notified Bodies & Certificates, and Market Surveillance (the latter primarily concerns authorities). Determine product/actor registration duties and the Commission's transitional rules for pre-existing devices; do not rely on older guidance describing EUDAMED as voluntary. Italy's national BD/RDM and sector-specific national duties need a separate, current applicability check, not an assumed second EU approval.

For a new device first placed on the EU market from 28 May 2026, complete the applicable actor and UDI/device registration steps before placement. The Italian Ministry explains that eligible legacy devices and MDR-compliant devices already placed on the market before 28 May 2026 and still placed afterwards have an additional six-month device-registration period, to 27 November 2026; notified-body certificate reporting has a different transition. Neither extension is an automatic exemption for a new launch.

For a non-EU manufacturer, verify a written EU authorised-representative mandate under MDR Article 11, identify importer/distributor duties under Articles 13–14, and check packaging information accordingly. A CE mark is the outcome of the correct conformity assessment, not a marketing authorisation issued by the Italian Ministry of Health.

Separate Italian advertising gate: Article 26 of Legislative Decree 137/2022 prohibits advertising to the public for certain devices, including those requiring professional assistance by law or manufacturer instructions, prescription-only devices and custom-made devices. Public advertising of other medical devices generally needs Ministry of Health authorisation unless an exemption applies. The 26 January 2023 decree exempts, on stated conditions, certain remote-sale listings limited to device/pack images and descriptions and intended purpose as given in the instructions for use, provided the full instructions are accessible; broader promotional claims cannot automatically use that exception. Information addressed to healthcare professionals follows the separate Article 26(7) rule. Record target audience and the exact Italian ad, website and app-store copy before launch.

Five release gates for a wearable in Italy

Claims gate: approve one intended-purpose statement and archive Italian advertising, clinical-use scenarios and app-store copy; block unsupported diagnosis or alarm claims.
Scope gate: document MDR status, Annex VIII class and notified-body need, then separate decisions for RED, RoHS, battery/WEEE, GDPR and any AI-related requirements.
Evidence gate: close the traceability between signals, algorithms, clinical benefit-risk, radio/electrical tests, wearability and cybersecurity; set version-controlled acceptance criteria.
Operator gate: verify manufacturer, EU representative if needed, importer, EUDAMED/UDI data and any surviving Italian national obligations; do not substitute registration for conformity.
Release gate: finalise EU declaration of conformity and applicable CE marking, Italian user information, PMS/vigilance ownership and change-control triggers before first commercial placement.

When the same watch needs a fresh assessment

Do not assume the existing evidence covers a new medical claim, a revised alarm threshold or a model trained on new data. Under MDR the manufacturer maintains conformity throughout the lifecycle; whether additional notified-body review is necessary depends on the change and the applicable conformity route.

New AF/apnoea claim or clinical user group → re-open qualification, risk class and clinical evaluation.
New optical sensor, battery or radio stack → re-check measurement performance, skin/thermal safety, RED and materials evidence.
Firmware/model/cloud update changing outputs or alarms → run documented software, clinical, cybersecurity and labeling impact assessments.

Where the broader rules are covered

For a country-wide MDR pathway without wearable signal and software detail, use general medical-device compliance in Italy. For EU-wide wearable mapping without Italy's language and registry checks, use wearable medical-device compliance across the EU. These pages supplement—not replace—the product-specific decision matrices here.

Frequently asked questions about medical wearables in Italy

Is a heart-rate watch automatically a medical device?

No. Intended medical purpose and actual claims control the MDR qualification. Fitness display alone is not a definitive medical claim; arrhythmia detection or clinician-directed monitoring calls for a documented MDR assessment.

Does a CE-marked Bluetooth module certify the entire ECG wearable?

No. Component documentation is useful evidence, but the final manufacturer must assess the assembled product, including RED interfaces and the distinct MDR clinical, software, labeling and post-market requirements.

Can we ship an English-only wearable to an Italian hospital?

Do not assume so. Italian Decree 137/2022 Article 6(2) requires Italian written manufacturer information under MDR Annex I section 23 at delivery to the final professional or lay user. Review UI warnings and safe-use flows as well.

Must a 2026 launch register only with Italy's BD/RDM?

No generic ‘BD/RDM only’ rule should be used. Mandatory EUDAMED modules began on 28 May 2026; check the device's timing, applicable transitional provisions, operator roles and any distinct Italian national register duties.

Can an app update add AF alerts under the old wellness approval?

No automatic carry-over. A medical alert can change intended purpose and MDR status. Reassess the app and watch separately/in combination, clinical evidence, risk controls, labeling and the applicable conformity route before release.

Can we advertise a CE-marked AF-alert watch directly to Italian consumers?

Not on the strength of CE marking alone. First check whether advertising to the public is prohibited because professional assistance or a prescription is required. Otherwise assess Ministry authorisation or a specific 2023-decree exemption; an IFU-faithful remote-sales listing with complete IFU access is different from a disease-treatment advertising campaign. Information for healthcare professionals is governed separately.