The EU Medical Device Regulation (MDR) is one of the most demanding regulatory regimes a manufacturer can face, and in 2026 it is still in motion: extended transition deadlines are running down, notified-body capacity remains a bottleneck, and the Commission has opened a revision of the regulation itself. This guide lays out what MDR requires, where the deadlines stand, and the guidance and standards that actually decide whether a device gets to market.

The standards and guidance landscape below is drawn from Obsidian's verified standards register, the same tier-0 data our MCP server serves to AI assistants.

What MDR is

MDR is Regulation (EU) 2017/745, governing medical devices placed on the EU market. It replaced the older Medical Devices Directive and raised the bar across the board: stricter classification, mandatory clinical evidence, unique device identification, post-market surveillance, and oversight by notified bodies. Its sister regulation, the IVDR (Regulation (EU) 2017/746), does the same for in-vitro diagnostics.

MDR applied from 26 May 2021. Because the notified-body system could not certify the entire legacy device base in time, the EU staggered extended transition deadlines (by device risk class, into 2027 and 2028) so that compliant legacy devices could remain on the market while recertification caught up. Notably, the Commission opened a revision proposal of the MDR framework in December 2025, so the regime itself is now under review.

The pieces that decide market access

  • Classification. Devices fall into classes (I, IIa, IIb, III) by risk, which determines the conformity-assessment route and whether a notified body is involved.
  • CE marking and notified bodies. Most devices require a notified body to assess conformity before CE marking. Notified-body capacity remains the practical bottleneck.
  • Clinical evidence. Manufacturers must demonstrate safety and performance with clinical data, a far higher bar than under the old directive.
  • Post-market surveillance. Obligations continue after launch: vigilance reporting, periodic safety update reports, and EUDAMED registration.

The guidance and standards that actually matter

MDR is the legal text, but day-to-day compliance is driven by the harmonised standards and the guidance issued by the Medical Device Coordination Group (MDCG). Obsidian's register tracks 81 standards and guidance documents, 76 of them medical, with their current-versus-superseded status. The ones manufacturers reference most:

  • MDCG guidance from the European Commission, including qualification and classification of software as a medical device, cybersecurity for medical devices, device classification, clinical evaluation under MDR, significant changes during the transition period, and notified-body capacity. These are revised regularly, so knowing the current version matters.
  • ISO 13485, the quality management system standard, the backbone of any MDR submission.
  • ISO 14971, application of risk management to medical devices.
  • IEC 60601 series, safety and performance of medical electrical equipment.
  • IEC 62304, software life-cycle processes, and ISO 10993, biological evaluation.
  • Team-NB position papers, reflecting how notified bodies themselves interpret the rules.

For medical devices, the regulation tells you the obligation, but the MDCG guidance and harmonised standards tell you how to actually satisfy it, and those move faster than the law.

Ask your AI which MDCG guidance is current, get a verified answer

Connect Obsidian to Claude, ChatGPT, or Cursor and query MDR standards, MDCG guidance versions, and status in plain English, with the source and current-or-superseded status on every answer. Free tier, two-minute setup.

Explore the Obsidian MCP

Why this is hard to track with AI alone

MDR compliance is unusually version-sensitive. An MDCG guidance document can be superseded; a harmonised standard can be updated; a transition deadline can shift by device class. A general AI model has no reliable way to tell you whether the guidance it is quoting is the current version or one withdrawn two years ago. As we cover in what tier-0 regulatory data means, the fix is a dataset that tracks current-versus-superseded status, not a model guessing from memory.

The takeaway

In 2026, MDR is a regulation under revision, with transition deadlines still in play and a guidance landscape that changes continually. Getting a device to market depends less on knowing the 2017 text and more on knowing the current MDCG guidance and standards, with their version status. That is a data problem, and the kind of question agentic regulatory intelligence is built to answer.