Product Compliance And Certification For Wearable Medical Device In Switzerland

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

A smartwatch, adhesive patch, ring or connected wrist sensor is not a Swiss medical device simply because it measures heart rate or oxygen saturation. Start with the manufacturer’s intended medical purpose, all claims in the app and advertising, and the decisions the outputs are intended to support. Then check the other regimes triggered by its Bluetooth/cellular radio, battery and handling of health data.

For Switzerland, the principal medical-device framework is the Medical Devices Ordinance (MedDO), aligned with the EU MDR but accompanied by Swiss-specific market-operator, language and swissdamed obligations. This is a product-level route map, not an assertion that a specific wearable is Class IIa or has been approved. Swissmedic ordinarily supervises the market rather than granting a product-by-product premarket authorisation.

Gate 1 — Fix the medical purpose and the real risk classification

Freeze the intended-purpose statement, clinical target population, body location, duration of wear and every app/alert claim before choosing a class. Class I, IIa, IIb and III follow MedDO Article 15 and EU MDR Annex VIII. Active monitoring and software decision-support require separate rule checks; neither a sensor name nor “AI-powered” determines the final class.

Product/claim fact	Classification question	Consequence to test
Fitness-only pulse trend, no diagnosis/treatment claims	Is the purpose genuinely non-medical across website, app and IFU?	May fall outside MedDO; radio, privacy and battery checks can still apply.
ECG arrhythmia detection or hypoxaemia alert	Does the output diagnose or monitor a physiological parameter, including potentially immediate danger?	Analyse active-device monitoring rules, including Rule 10; a higher-risk route may result.
App predicts deterioration or recommends clinical action	Is the software providing information for diagnosis or therapeutic decisions?	Assess software qualification and Rule 11, including severity of the decision’s consequences.
Patch, electrode or strap in prolonged skin contact	Which materials, duration and users are exposed?	Build contact-specific biological safety, irritation and usability evidence.
App/cloud is supplied as part of the wearable	Which functions drive/influence the device and which have an independent medical purpose?	Document hardware–software boundaries, individual or combined classification and change ownership.

Gate 2 — Check the regulatory layers simultaneously

A device may comply with the medical-device rules yet still be blocked by missing radio evidence, unsuitable Swiss instructions or an unprepared local supply chain. The matrix identifies applicability tests, not automatic universal certifications.

Layer	Trigger for a wearable	Decision/evidence required before sale
Medical-device conformity (MedDO / EU MDR)	Intended purpose is medical	Risk class and rules; general safety/performance, clinical evaluation, QMS, technical documentation, conformity assessment and CE declaration; designated/notified body where the selected route requires one.
Medical software, cybersecurity and updates	Device firmware or app impacts a medical output	Software lifecycle, clinical performance of algorithm, cybersecurity threats, failure-safe behaviour, update/version validation; standards are means of evidence, not statutes.
Radio equipment (OFCOM / FAV)	Bluetooth, Wi-Fi, NFC with transmission, cellular or other radio	Applicable radio conformity, frequency/interface restrictions, RF/EMC evidence, declaration, marking and regional user information.
Data protection (FADP)	Identifiable heart rhythm, physiological trends or cloud patient profiles	Identify the controller, processing purposes and Swiss FADP privacy-by-design, transparency, security and data-minimisation measures; assess justifications/consent where the processing requires them, cross-border transfers and any separate GDPR exposure. Swiss FADP is not simply the GDPR legal-basis checklist.
Battery and end-of-life obligations	Rechargeable or replaceable battery supplied with device	For a battery built into the wearable, identify who first places it on the Swiss market and verify INOBAT reporting and any advance disposal-fee responsibility (including whether it is fulfilled through an authorised collection arrangement); check free take-back duties as well as charger/accessory rules separately.
Swiss market access / swissdamed	A regulated device is made available in Switzerland	CH-REP where required, CHRN actor registration, Swiss importer duties, product UDI registration and subsequent importer linkage; EUDAMED is not a substitute.

Evidence packet specific to a connected wearable

Request these records for the actual model and software release, not a generic CE certificate for the entire product family:

Claim-by-claim intended-purpose and borderline analysis covering box, website, mobile app and clinical dashboard.
EU MDR Annex VIII classification justification for wearable hardware and relevant software functions, with rule-by-rule rationale.
Device architecture, sensor specifications, applied-body materials, contact duration, battery and radio-module identification.
Performance validation against appropriate reference measurements, including motion artefacts, skin-tone/fit effects where relevant, alarm thresholds and known limitations.
Clinical evaluation and risk-management trace linking foreseeable misuse, false negatives/positives, cyber incidents and mitigation evidence.
Software/firmware inventory, threat model, verification, updates, Bluetooth/data-path testing and version-specific change record.
Radio test/declaration package and confirmation that intended bands/powers and use restrictions work in Switzerland.
Manufacturer conformity declaration, relevant third-party certificate if required, UDI and packaging/IFU mock-ups, CH-REP/importer responsibilities and swissdamed data owner.

Gate 3 — Sequence the Swiss launch without confusing registration with approval

Swissmedic recognises qualifying EU conformity assessments/CE marking for Swiss marketing, but this does not waive Swiss local duties. For a wearable using an older MDD/AIMDD CE certificate, separately verify eligibility under the conditional legacy-device transition and restrictions on significant changes; the older CE mark alone does not prove that the transition remains available. The market actor, device registration and importer link are distinct activities:

1. Manufacturer signs off intended purpose, risk classification, clinical/performance evidence and the correct conformity-assessment route; involve a designated/notified body when legally required.
2. Identify the manufacturer, the written CH-REP mandate when required (including the Liechtenstein-manufacturer exception), and the actual Swiss importer/distributor roles in this supply chain. Register actors subject to CHRN duties before first market placement; a company acting as both CH-REP and importer must register both roles and receives two CHRNs.
3. Prepare Swiss labels and IFU; verify medical CE/DoC, UDI where applicable, CH-REP and importer indications, plus OFCOM declarations/information for the radio variant.
4. For devices subject to UDI Devices registration, assign a responsible Swiss manufacturer or authorised representative to register in swissdamed: mandatory since 1 July 2026, with a general transition until 31 December 2026. Devices involved in reportable serious incidents, FSCAs or trends do not benefit from that transition. Custom-made, repackaged/relabelled and in-house devices have distinct form-notification routes; do not assume that this ordinary UDI procedure replaces those notices. EUDAMED does not synchronise with swissdamed.
5. The importer links its CHRN to each relevant registered UDI-DI: function available since 1 October 2026; Swissmedic’s link-transition runs to 1 April 2027. A missing link grace period is not permission to neglect the other importer checks.

Labelling, alerts and country-specific release controls

For ordinary public-facing medical-device product information, Swissmedic states the default is German, French and Italian. Narrow professional-use exceptions to reduced languages/English depend on the conditions of MedDO Article 16; do not treat English-only consumer screens as automatically sufficient.

Show the medical intended purpose, warnings and limits consistently in box, IFU, onboarding, app store listing and push-alert text; a “wellness” disclaimer cannot neutralise medical diagnostic claims elsewhere.
Check CH-REP identity/contact address and importer identification in the permitted locations. A shipping invoice not accompanying the device does not replace required importer identification.
Keep evidence for both medical and radio conformity identifiable, even where a combined declaration is permitted. OFCOM radio information and operating restrictions must also be understandable in the official language(s) of the region where the product is offered; medical CE marking is not an unrestricted Swiss spectrum permission.
Treat alarm localisation, units, time zones, offline behaviour and accessibility as patient-safety design verification, not merely translation.

Three edge cases that change the route

Apply the matrix to the actual sales configuration rather than the component supplier’s certificate:

A “fitness ring” adds an atrial-fibrillation warning in an update: re-evaluate intended purpose, Rule 10/11 applicability, clinical validation, notified-body route and affected claims before release.
A CE-marked EU patch is sold directly to Swiss patients: check CH-REP/CHRN, labels and importer role; EU registration by itself does not populate swissdamed.
A hospital pilot streams ECG to a cloud dashboard: document whether it is routine supply or a clinical investigation, medical software boundaries, privacy/controller roles and applicable Swiss ethics/Swissmedic study approvals.

Changes after launch that reopen the analysis

Maintain post-market surveillance, complaint/vigilance escalation, cybersecurity fixes and version traceability. Reassess the route when the device gains a diagnostic claim, an alert algorithm changes, contact materials or target patients change, a radio chipset/frequency changes, or the responsible Swiss economic operator changes.

Do not assume an ISO 13485 certificate or IEC 60601/62304 test report is a Swiss product authorisation; use standards as evidence matched to legal requirements.
Do not apply a Swissmedic clinical-investigation approval workflow to every commercial sale. A prospective Swiss clinical investigation has a separate category-dependent approval analysis.
For general Swiss medical-device obligations rather than wearable-specific cross-regime choices, consult the related Swiss medical-device compliance overview; for the EU side of the underlying wearable assessment, consult the EU wearable medical-device route.

Official authorities and source material

Swiss law and regulator guidance control over this planning matrix; legal instruments are binding, guidance and harmonised/technical standards are not interchangeable with legislation.

Wearable device FAQs

Does a smartwatch become a medical device when it measures oxygen saturation?: Not solely because of the sensor. Inspect intended medical claims and how readings are used for diagnosis/monitoring. A clinical hypoxaemia alarm requires a different qualification analysis from general fitness trending.
Can an EU CE-marked ECG patch be shipped directly to Swiss buyers?: A relevant EU conformity assessment may be recognised, but verify the Swiss authorised representative, operator registration, product/language information, import responsibility and swissdamed steps for the actual sales chain.
Is the app classified separately from the wrist sensor?: Sometimes. Determine whether the app merely controls or influences the hardware, provides independently regulated medical decision support, or has only non-medical functions. Assess the applicable rules, including Rule 11, on the documented intended purpose.
Does Bluetooth certification replace the MDR assessment?: No. Radio compliance under Swiss OFCOM/FAV addresses different risks from medical safety, clinical benefit, monitoring algorithms and post-market controls. Both assessments may be needed.
What must be done about swissdamed in October 2026?: Determine who must register the relevant UDI-DI, and whether the ordinary 31 December 2026 transition applies; reportable vigilance events can remove that grace period. Special devices may still use form notifications. Importer linkage has been available since 1 October 2026, with enforcement transition until 1 April 2027.