Regulatory Matters · Issue 002
Register your devices in EUDAMED by 28 November
- If your device was on the EU market before 28 May 2026, its EUDAMED records are due by 28 November.
- From December, the Commission plans for manufacturers to upload each device's safety summary, a job Notified Bodies do today.
- For devices already on the market, the last date for that upload is 27 March 2027.
- In Switzerland, register your devices in swissdamed by 31 December. Fees are invoiced from January.
- Also inside: tests for rare diseases, classifying software under Rule 11, four FDA cases, and eight dates to watch.
By Daren Wilson, Chief Operating Officer · Regulatory statements reviewed by Niko Mangold
- Published
- 9 November 2026
- Covering
- 22 October to 8 November 2026
- Next issue
- 26 November 2026

At a glance
If you already sell in the EU, your EUDAMED records are due by 28 November
| Date | What it means |
|---|---|
| 28 Nov | EUDAMED records due for devices already on the market |
| 30 Nov | Comments close on the US Food and Drug Administration's (FDA) proposed guidance lists for fiscal year 2027 |
| Dec | Planned: manufacturers can upload safety summaries in EUDAMED |
| 31 Dec | Swiss registration transition ends; fees invoiced from January |
Sources: MDR Art. 123(3)(e), as amended by Reg. (EU) 2024/1860 · MDCG 2026-4 rev.1 · HPRA · Swissmedic information sheet BW630_40_001. Checked 9 Nov 2026.
Register your devices in EUDAMED by 28 November
From December, the Commission plans to have you upload each device's safety summary instead of your Notified Body
EUDAMED registration became mandatory on 28 May 2026. If your device was already on the EU market then, its records must be in EUDAMED by 28 November 2026. That is when the six-month transition that followed mandatory use ends, and the Irish and Norwegian medicines regulators both give the date on their EUDAMED pages.
Today your Notified Body uploads each device's safety summary, the SS(C)P, to EUDAMED when it registers a new certificate. A position paper from the MDCG, MDCG 2026-4 rev.1, says the guidance is being revised so that manufacturers do this upload themselves. The upload functions are planned for the live system in December 2026.
MDCG 2026-4 rev.1: guidance MDCG 2019-9 rev.1 "is being revised to assign to the manufacturer the task to upload the SSCPs in EUDAMED".
For devices placed on the market before 28 May 2026, upload the summary as soon as you can, and by 27 March 2027 at the latest. The paper notes that this, in practice, shortens the six months originally allowed for these uploads.
Sources: MDR Art. 123(3)(e), as amended by Regulation (EU) 2024/1860; MDCG 2026-4 rev.1, "MDCG Position Paper: Management of SS(C)P in EUDAMED after mandatory use", October 2026; HPRA, 23 March 2026; Norwegian Medical Products Agency, updated 4 June 2026. Checked 9 November 2026.
Applies to you if your device was on the EU market before 28 May 2026, or you hold or are applying for a certificate for such a device.
What it means for you
- MedTech founders. Plan to upload your summary yourself from December, and ask your Notified Body who uploads it until then.
- Companies already on the market. Register your device records by 28 November, and plan the summary upload for 27 March 2027 at the latest.
- Regulatory professionals. Expect the details to change, because the guidance behind the paper, MDCG 2019-9 rev.1, is still being revised.
Next step. Not sure which of your devices the 28 November deadline covers? Talk to a regulatory expert.
Switzerland wants your devices registered by 31 December, and starts charging in January
What Swissmedic says about registration and the fee
Registration in swissdamed, the Swiss device database, has been mandatory since 1 July 2026, and the transition phase ends on 31 December 2026. A device you have to report to Swissmedic for a serious incident, a field safety corrective action, or a trend gets no transition: it has had to be registered since 1 July. From January 2027, Swissmedic invoices a fee for every device model (UDI-DI) registered by 31 December with the status "On the market".
The fee is 200 Swiss francs (CHF) for the first UDI-DI registered in a year and CHF 20 for each further one. Each manufacturer pays no more than CHF 10,000 a year. A device you no longer place on the market on 31 December, and mark that way in swissdamed, carries no fee. A legacy device newly registered under the MDR or IVDR counts as a new registration and carries the fee. If you are based outside Switzerland, the invoice goes to your Swiss authorised representative (CH-REP). It falls due 30 days after the invoice date, and credit cards are not accepted.
Sources: Swissmedic information sheet BW630_40_001, version 2.0, valid from 27 October 2026; Swissmedic notice of 1 July 2026. Checked 9 November 2026.
Applies to you if you place devices on the Swiss market, directly or through a Swiss authorised representative.
What it means for you
- MedTech founders. Budget for a fee on each device model, and decide which devices you will still place on the market after 31 December.
- Companies already selling in Switzerland. Mark any device you no longer place on the market before the year ends, because that status removes the fee.
- Regulatory professionals. Check how your legacy devices will be registered, since a new MDR or IVDR registration carries the fee even when the UDI-DI is unchanged.
Next step. Selling in more than one market? The Venitara Market Atlas sets your launch order and the requirements behind each market.
Tests for rare diseases get their own guidance on clinical evidence
What MDCG 2026-6 asks of manufacturers and Notified Bodies
MDCG 2026-6, published in November 2026, covers the clinical evidence needed for orphan in vitro diagnostics. An orphan test is one for a condition found in no more than 12,000 people in the EU each year; a test for a rare disease, one affecting no more than 5 in 10,000 people, can qualify on that basis. It asks that the IVDR's requirements be applied to these tests in a balanced and proportionate way.
You justify the orphan status yourself, and your Notified Body should check it as early as possible, during the application phase.
Source: MDCG 2026-6, sections 4.1 and 4.2, November 2026. Checked 9 November 2026.
Applies to you if you make a test for a rare disease and are planning or going through a conformity assessment, the check that a device meets the rules before it can be sold.
What it means for you
- MedTech founders. Write your orphan-status justification before you apply, and give it to your Notified Body with the application.
- Companies with tests in assessment. Ask your Notified Body whether it has checked the orphan status yet.
- Regulatory professionals. Read the paper alongside your clinical evidence plan.
Next step. Building a test for a rare disease? Talk to a regulatory expert before you apply.
How to: classify your software under Rule 11
For software that is, or contains, a medical device.
Rule 11 in Annex VIII of the MDR sets the class of software, and MDCG 2019-11 rev.1, of June 2025, explains how to apply it.
- Ask whether the software has a medical purpose of its own. Software that only stores, archives, communicates, searches simply, or compresses data without loss is not medical device software by itself. Write your intended purpose first: what the device is for, as stated on the label and in the instructions. The guidance warns that an unclear statement leads to the wrong class. MDR Art. 2(1); MDCG 2019-11 rev.1, section 3
- Ask whether it controls a hardware device. Software that drives or influences a device takes that device's class. Software independent of any device is classified in its own right. Software with its own medical purpose that also drives a device is classified on that purpose, but no lower than the device. The guidance's example is melanoma image analysis software that drives a class IIa laser scanner, which is class III under Rule 11. MDR Annex VIII, rule 3.3; MDCG 2019-11 rev.1, section 4.1
- Ask whether it informs a diagnosis or treatment decision. The guidance says this description fits nearly all software with a medical purpose, so expect class IIa or higher. Its example is software that analyses arterial stiffness to prevent illness, which counts as a diagnosis purpose. MDR Annex VIII, Rule 11; MDCG 2019-11 rev.1, section 4.2.1
- Ask what a wrong output could cause. If it could cause death or an irreversible decline in health, the software is class III. If it could cause a serious decline in health or surgery, it is class IIb. The guidance includes a table that maps the risk categories of the International Medical Device Regulators Forum (IMDRF) to Rule 11 classes. MDR Annex VIII, Rule 11
- Ask whether it only monitors. Monitoring-only software is class IIa, or class IIb if a change in what it tracks could put the patient in immediate danger. The guidance names respiration, heart rate, cerebral functions, blood gases, blood pressure, and body temperature as such vital parameters. MDR Annex VIII, Rule 11
- Check the other rules. Software that fits none of the steps above is class I. Where more than one rule applies, the strictest wins, and Rules 9, 10, 12, 13, 15, and 22 are all candidates. The guidance puts software used for contraception in class IIb under Rule 15. MDR Annex VIII, rule 3.5; MDCG 2019-11 rev.1, section 4.2
- Write the reasoning down. Record the intended purpose, the paragraph of the rule that applies, and the harm you considered. For software built from modules, the guidance asks you to define and justify each module's intended purpose and how the modules depend on each other. MDCG 2019-11 rev.1, section 7
Source: Regulation (EU) 2017/745, Annex VIII, Rule 11 and implementing rule 3.3, and MDCG 2019-11 rev.1, June 2025. Checked 9 November 2026.
Next step. Check your device's likely class in about ten minutes with the free MedTech Compass (AI-generated, not validated). For a written classification rationale and your regulatory pathway, see Pathway Ready.
Mistakes on the record: four recent FDA cases
Four FDA cases, and the control that catches each
None of the recall notices below names a regulatory clause as the cause. The warning letter cites clauses of 21 CFR Part 820, the FDA's quality system rules. Each control is general good practice for a company building its first quality system.
Instrumentation Laboratory (Werfen): a blood test that read low without quality control noticing. FDA recall, current as of 30 October. The FDA classes it as the most serious type of recall. The manufacturer found that results from the affected batches ran 20–35% low, which routine calibration and quality control may not catch. The control: check every new batch against results from real patient samples, as well as calibration and quality control.
B. Braun: a dialysis bloodline set that could leak because an assembly step was skipped. FDA Early Alert, a public notice that a device is being removed, current as of 2 November. The manufacturer says a required solvent step was skipped during assembly, so the connector to the dialyser may detach or leak during priming or treatment. The control: record every required assembly step, and hold any unit that has no record.
Compact Medical: a hand-squeezed breathing bag that can develop holes. FDA Early Alert, current as of 3 November. A hole can form in the bag, letting part of each breath escape before it reaches the patient. Lots 000109 to 000117 are being removed, and earlier lots now need a test before each use. The control: where you cannot yet design a defect out, give users a check to run before each use, and confirm they can run it.
Next Medical Products: a product change that needed a 510(k), posted 3 November. FDA warning letter, issued 19 August 2026. The letter says change control covers any change to the device, its labelling, or its packaging. It finds that the changes it describes needed a 510(k). It also finds that the firm was not opening CAPAs to investigate the causes of problems in its processes. The control: check every change against your regulatory submissions before you release it.
Sources: FDA recall and Early Alert pages and warning letter 727918, entries current as of 30 October to 3 November 2026. Each page opened again on 9 November 2026.
Next step. Building your first quality system? The Venitara QMS Foundation sets up its governance, responsibilities, and core registers.
Eight dates to watch before the end of March
What falls due before the end of March
Checked 9 November 2026. CH: Switzerland.
| Date | Market | What falls due, and for whom |
|---|---|---|
| 28 Nov | EU | EUDAMED records for devices on the market before 28 May 2026 |
| 30 Nov | US | Comments close on the FDA's proposed guidance lists for fiscal year 2027 |
| Dec | EU | Planned: manufacturers can upload safety summaries in the live EUDAMED system |
| 14 Dec | EU | Provisional European Parliament plenary date for the MDR and IVDR revision; no committee has voted yet |
| 31 Dec | CH | swissdamed registration transition ends |
| Jan 2027 | CH | swissdamed fees first invoiced |
| 28 Jan 2027 | CH | Consultation closes on the draft ordinance on reporting shortages of vital devices [001 ledger] |
| 27 Mar 2027 | EU | Latest date to upload safety summaries for devices on the market before 28 May 2026 |
The question: who uploads our safety summary until December?
Until the new functions reach the live EUDAMED system, your Notified Body uploads the summary when it registers a new certificate. Ask your Notified Body in writing how it will handle your device, and keep a dated record of the answer.
How this issue was compiled. We used primary sources published between 22 October and 8 November 2026, named under each section. Niko Mangold reviewed every regulatory statement before publication. Regulatory Matters is general information and does not replace an assessment of your device.