EUDAMED registration is sometimes mistaken for full European market coverage, including in Switzerland. This assumption doesn't hold – and the reason traces back to a regulatory relationship that fell apart a few years ago.
Why Switzerland needed its own database
When the EU–Switzerland Mutual Recognition Agreement (MRA) for medical devices was no longer updated to reflect the EU Medical Device Regulation (MDR) in 2021, Switzerland was effectively excluded from the EU's medical device conformity assessment and regulatory cooperation framework. The EU consequently treated Switzerland as a third country for medical devices, and Swissmedic lost access to EUDAMED and participation in the EU's medical device surveillance network. Switzerland responded by revising its own Medical Devices Ordinance (MedDO) and, subsequently, its In Vitro Diagnostic Medical Devices Ordinance (IvDO), closely aligning Swiss requirements with the EU MDR and IVDR while maintaining them as independent Swiss law.
This created a need for Switzerland to maintain its own national registration infrastructure rather than relying on EUDAMED. Swissmedic therefore developed Swissdamed, the Swiss database for medical devices and IVDs. Swissdamed is deliberately modelled on the corresponding EUDAMED modules to preserve regulatory equivalence and reduce the administrative burden for manufacturers, but it is a separate national database and does not synchronize with EUDAMED.
Two systems, two clocks
It would be reasonable to assume that EUDAMED and Swissdamed run on the same calendar. They don't. In the EU, use of the relevant EUDAMED modules – including Actor Registration and UDI/Device Registration – became mandatory on 28 May 2026, with a six-month transition period running until 27 November 2026. Swissdamed follows a separate timeline: registration of devices, systems and procedure packs became mandatory from 1 July 2026, with a transition period lasting until 31 December 2026. The obligations cover both devices under the current legislation and “legacy” devices under the former directives.
Where the two systems actually meet
Swissdamed and EUDAMED aren't unrelated systems built from scratch in isolation. The Swiss database shares a largely equivalent data model and business rules with EUDAMED, and supports the same registration methods – manual entry through the online editor, XML bulk upload, and machine-to-machine integration.
In practice, this means UDI data already built and validated for EUDAMED doesn't start from zero when Swiss registration comes into scope. The underlying dataset – device identifiers, classifications, product attributes – carries over conceptually. What doesn't carry over on its own is market status: Swissdamed still calls for Swiss market placement to be reflected within its own system, rather than assumed from an EU filing. That step is manual and easy to overlook when "already in EUDAMED" gets mistaken for "already covered."
The XML layer behind the scenes
Bulk upload sounds like the efficient option – one structured file, submitted once, rather than manual entry field by field. In practice, the XML formats behind both EUDAMED and Swissdamed carry their own structural rules, validation logic, and nested data requirements, and getting them right is a fairly technical exercise. A single malformed attribute, an incorrectly nested element, or a mismatched code list reference can be enough for a submission to bounce back, and diagnosing why often means digging into schema documentation that reads more like software specification than regulatory guidance.
This is where a lot of otherwise well-prepared registration efforts slow down. Regulatory affairs and registration teams are typically strong on the substance of what needs to be reported, but XML structuring and validation sits closer to a data engineering skill set than a regulatory one. It's a reasonable gap to have – the two disciplines rarely overlap in a single role – but it's also the point where timelines start slipping, particularly under the pressure of parallel EUDAMED and Swissdamed deadlines.
A note on registration strategy
In some instances, the mistake isn't ignoring Swissdamed but rather treating it as a second, unrelated project that duplicates work already done for the EU. That framing costs time and risks overlooking the fact that the two obligations run on different clocks, and that the technical side of submission carries its own separate risk.
A more effective approach treats EU UDI data as a foundation for Swiss compliance – recognizing where the two systems genuinely align, where Swissdamed still calls for its own input, and where the underlying file formats need careful handling regardless of which system they're headed for.
Two deadlines, one limited-time offer
Qserve has spent the past several months building and testing exactly this kind of workflow – first for EUDAMED XML submissions, and, more recently, extending that same foundation to cover Swissdamed as well. For organizations navigating both deadlines at once, this is where existing data can carry weight, and where the technical details still deserve a closer look. With the EUDAMED legacy-device deadline of 28 November 2026 and the Swissdamed transition period ending on 31 December 2026, the window for preparing and validating your data is rapidly closing.
Sign up for Qserve’s EUDAMED legacy bulk-upload support before 1 October 2026, and we will manage your Swissdamed upload free of charge. Our team will coordinate both registration projects while addressing the specific requirements of each database.
Contact us today to discuss your device portfolio and secure this limited-time offer.