The MDR does not reference IEC 60601-1 by name anywhere in its articles or annexes. What the MDR does, through Article 8, is establish a legal mechanism called presumption of conformity: if a harmonised European standard has its reference published in the Official Journal of the European Union, and you apply it correctly, you are presumed to meet the MDR requirements that standard covers. EN 60601-1:2006+A1+A12+A2+A13:2024 is the harmonised European adoption of IEC 60601-1 that carries this presumption for the electrical, mechanical, thermal, and radiation safety requirements of Annex I Sections 14, 17, and 18. The MDR is the obligation. The standard is the tool the MDR allows you to use to discharge that obligation efficiently.

By Tibor Zechmeister and Felix Lenhard. Last updated 10 April 2026.

TL;DR

  • The MDR never names IEC 60601-1. What it does is create a legal channel — Article 8 — through which harmonised standards can deliver presumption of conformity with specific requirements of the Regulation.
  • A standard carries that presumption only when its reference is published in the Official Journal of the European Union (OJEU) with a stated link to specific MDR articles and annex sections.
  • EN 60601-1:2006+A1+A12+A2+A13:2024 is the European harmonised version of IEC 60601-1 that, when listed in the OJEU, provides presumption of conformity for electrical, mechanical, thermal, and radiation hazards under Annex I Sections 14, 17, and 18.
  • The mapping from standard clauses to MDR requirements is formalised in each standard's Annex Z — the normative annex that tells you which parts of the standard address which parts of the Regulation.
  • Presumption of conformity is strong but rebuttable. It does not relieve you of addressing residual risks outside the standard's scope, and it does not convert the standard into the obligation itself.

Why founders ask the wrong version of this question

Founders new to MDR often ask "where in the MDR does it say I have to use 60601?" The question is natural and the answer surprises them: nowhere. The MDR does not list standards. It does not tell you which test methods to follow. It does not prescribe creepage distances, dielectric strength values, or electromagnetic immunity levels. Searching the MDR for "60601" returns zero hits.

The instinct that follows the surprise is usually wrong. Founders conclude either that 60601 is optional (it is not, in practice) or that regulators are hiding something (they are not). The real answer is structural. EU product regulation has been built on a specific legal pattern for decades: the Regulation states the safety outcome the legislator wants, and a separate legal mechanism — the harmonised standard listed in the Official Journal — delivers a recognised, shared way to demonstrate that the outcome has been met. The MDR follows this pattern exactly. Article 8 is where the mechanism lives. EN 60601-1:2006+A1+A12+A2+A13:2024 is what flows through it for electrical safety.

This post walks through how that mechanism actually works, clause by clause, so the next time a Notified Body reviewer asks why your technical file cites the standard, you can answer the regulatory logic and not just the custom.

The Article 8 mechanism, in the MDR's own words

MDR Article 8 is titled "Use of harmonised standards." Its operative sentence is short and carries the entire mechanism.

"Devices that are in conformity with the relevant harmonised standards, or the relevant parts of those standards, the references of which have been published in the Official Journal of the European Union, shall be presumed to be in conformity with the requirements of this Regulation covered by those standards or parts thereof." — Regulation (EU) 2017/745, Article 8, paragraph 1.

Three things follow from this sentence, and every startup should understand all three.

First, presumption of conformity is a legal state, not a technical description. When your device conforms to a harmonised standard whose reference is published in the OJEU, the law assumes you have met the corresponding MDR requirements. The burden of proving otherwise shifts to anyone who wants to challenge the presumption — a Notified Body, a competent authority, a market surveillance inspector. You are not required to re-prove the underlying safety outcome from first principles.

Second, the presumption is tied to the parts of the standard that are actually listed. If only parts of a standard are cited in the OJEU, only those parts carry the presumption. Everything else in the standard is still useful state-of-the-art guidance but does not confer the legal shortcut.

Third, the presumption covers only the MDR requirements that the standard is mapped against. A standard on electrical safety cannot give you presumption of conformity with biocompatibility requirements. The scope of the coverage is defined by the standard's Annex Z, which is the piece we come to below.

Article 8 is also where the MDR acknowledges that standards are not the only route. Paragraph 1 uses "shall be presumed," not "shall comply with." You are legally allowed to demonstrate conformity another way. In practice, for electrical safety in medical devices, no realistic alternative exists that a Notified Body will accept without extraordinary justification — but the legal door is not closed.

How a standard actually becomes harmonised

A standard does not become harmonised because a committee says it is good. It becomes harmonised through a formal EU process, and only at the end of that process does it start to deliver presumption of conformity. MDCG 2021-5 Rev.1, the guidance document on standardisation for medical devices, walks through the full mechanism. The short version:

  1. The European Commission issues a standardisation request to the European Standardisation Organisations (CESCE — CEN and CENELEC for most MDR-relevant standards, ETSI for a few telecom-adjacent ones). The request names the MDR requirements the standard must cover.
  2. The ESOs develop the European standard, typically by adopting an international ISO or IEC standard and adding an Annex Z that maps the standard's clauses to the specific MDR requirements in the standardisation request.
  3. The European Commission assesses the standard against the request. If the assessment is positive, the Commission adopts an implementing decision that publishes the standard's reference in the Official Journal of the European Union.
  4. From the date of OJEU publication, the standard (or the listed parts of it) confers presumption of conformity with the MDR requirements stated in the OJEU listing itself.
  5. If the standard is revised, the Commission must re-assess and re-publish. Until re-publication, the old listed version remains the one that confers presumption.

IEC 60601-1 is an international standard published by the International Electrotechnical Commission. It does not, by itself, have any status under EU law. What has status under EU law is the European adoption of that international standard, with the European Annex Z added, published as EN 60601-1 and listed in the OJEU. This is why the exact reference you cite matters. The current consolidated European version is EN 60601-1:2006+A1+A12+A2+A13:2024. That string is not a typographical flourish — it names a specific legal object: the 2006 base standard, with Amendment 1, with the A12 European-specific amendment, with Amendment 2, and with the 2024 A13 amendment rolled together.

The OJEU listing is the moment it matters

The Official Journal of the European Union is the official publication of EU legal acts. For harmonised standards, the listing takes the form of a Commission implementing decision that names the standards and states the MDR articles and annex sections each one covers. The listing is live, not static. New standards are added. Old versions are withdrawn with cessation-of-presumption dates. The Commission also publishes amendments to existing listings.

Two practical consequences for founders.

You must check the current OJEU listing, not rely on memory or a consultant's slide from two years ago. A standard that was listed last year may have been superseded by a new amendment whose reference has now replaced it. The date on which the old version stops conferring presumption is stated in the listing itself. Missing that date means your technical file is citing a standard that no longer gives you the legal shortcut.

You must cite the exact reference string from the OJEU listing in your technical file. Writing "IEC 60601-1" without the amendment chain is ambiguous and will raise a flag in any competent Notified Body review. The reference you should cite for electrical safety, when it matches the current OJEU listing, is EN 60601-1:2006+A1+A12+A2+A13:2024.

A companion spoke post in this category covers the current OJEU status for the 60601 family and how to verify it yourself.

What presumption of conformity actually covers

Presumption of conformity is narrower than most founders assume and stronger than most founders assume, at the same time.

It is narrower because it only covers the MDR requirements the standard is mapped to. EN 60601-1:2006+A1+A12+A2+A13:2024 is mapped, via its Annex Z, to the electrical, mechanical, thermal, and radiation safety requirements of MDR Annex I — principally Sections 14 (construction and interaction with the environment), 17 (electronic programmable systems), and 18 (active devices). It does not give you presumption of conformity with the clinical evaluation requirements of Article 61, or the post-market surveillance requirements of Articles 83-86, or the biocompatibility requirements of Annex I Section 10. For those, you need different standards or different evidence.

It is stronger because, within its scope, the presumption is a real legal state. A Notified Body reviewing your technical file is not re-deriving your electrical safety evidence from Annex I first principles. They are checking that you applied the listed standard correctly to your device, that the applied part classifications and isolation strategies match your risk management file, and that the test report from the accredited lab matches the version of the standard cited in the OJEU. If all of that holds, the Annex I electrical safety requirements are presumed met.

The presumption is also rebuttable. If a reviewer identifies a residual hazard that the standard does not address — for example, a novel failure mode in a new device architecture that the standard was never written to cover — the presumption does not shield you. You still owe a risk control for that hazard, documented in the risk management file and justified against Annex I. This is where the "as far as possible" language in Annex I bites: the standard is the efficient route for the risks it covers, and Annex I still governs the risks it does not.

The Annex Z mapping — where the two documents meet

Every harmonised European standard contains an Annex Z (sometimes ZA, ZB, ZZ — the lettering varies). Annex Z is a normative annex whose job is to tell the reader, clause by clause, which MDR requirements a given part of the standard addresses.

Reading Annex Z of EN 60601-1 is the fastest way to understand why the standard sits under the MDR at all. The table in Annex Z lists the MDR general safety and performance requirements on one side and the standard's clauses on the other. A single MDR requirement can map to many clauses; a single clause can map to several MDR requirements. The mapping is the legal glue.

For the electrical safety clauses, Annex Z of EN 60601-1 maps to MDR Annex I requirements covering: protection against risks associated with the use of energy sources (Section 14), risks from electronic programmable systems (Section 17.1), and the active-device-specific risks in Section 18 including alarms, supply interruption, fault conditions, and unintended output.

Two practical rules for founders reading Annex Z.

The mapping is the scope of the presumption. If a clause is listed in Annex Z against an MDR requirement, compliance with that clause contributes to presumption of conformity with that requirement. If a clause is not in Annex Z, it does not contribute to the legal shortcut — it may still be useful engineering, but it is not earning presumption.

The absence of a requirement from Annex Z is the signal you need other evidence. If an MDR requirement is not covered in the Annex Z of any standard you are applying, you must demonstrate conformity with that requirement directly — from your risk management file, from your design verification, from your clinical evaluation, from your IFU. This is the test that tells you whether your standards scope is complete for your device or whether you have gaps.

What the standard does not cover

Understanding what is outside EN 60601-1:2006+A1+A12+A2+A13:2024 is as important as understanding what is inside.

The standard does not cover the software lifecycle process in any meaningful way. It addresses programmable electrical medical systems at the system-safety level, but the detailed software development lifecycle requirements live in EN 62304:2006+A1:2015. The two standards are complementary, not substitutable.

It does not cover usability engineering. Usability for medical devices is the scope of EN 62366-1:2015+A1:2020.

It does not cover risk management as a process. It invokes ISO 14971 repeatedly and is unworkable without a real risk management file, but the process standard itself is EN ISO 14971:2019+A11:2021.

It does not cover biocompatibility. Biological evaluation lives in the EN ISO 10993 family.

It does not cover cybersecurity in the sense of software vulnerability management. Cybersecurity lifecycle activities are covered by EN IEC 81001-5-1:2022.

Each of these other standards has its own Annex Z and its own listing, and each one carries presumption of conformity with a different slice of MDR Annex I. The full standards scope for a typical active electrical medical device is a set, not a single document. EN 60601-1 is the central one for electrical safety, and exactly that — not everything.

Common misunderstandings

"We are 60601-compliant, so we are MDR-compliant." No. You are presumed to meet the Annex I requirements the standard is mapped to, within the scope of Annex Z. You still owe conformity with every other MDR obligation — classification, technical documentation, clinical evaluation, QMS, PMS, vigilance, registration in Eudamed. The standard covers a slice of Annex I. The MDR covers the whole regulatory life of the device.

"IEC 60601-1 is the mandatory standard for medical devices." No. Article 8 is explicit that harmonised standards deliver presumption of conformity, not legal obligation. A manufacturer may demonstrate conformity another way. In practice, for electrical safety, no Notified Body accepts an alternative route without extraordinary justification, so the standard is effectively required. But effectively required is not legally mandatory, and the distinction matters in the technical file argument.

"We cited IEC 60601-1, so we are covered." Citing the international IEC reference is not the same as citing the European harmonised EN reference that is actually listed in the OJEU. The legal object with presumption of conformity is the EN version with the amendment chain. Write the full reference.

"Our old test report from 2019 still holds." Only if the version cited in that report is still the version listed in the OJEU. The A13:2024 amendment changed the current consolidated reference. A report against an older consolidated version needs a gap assessment against the current one to stay in force.

"Annex Z is optional reading." Annex Z is the only place where the bridge between the standard and the MDR is explicitly written down. Skipping it is skipping the mechanism that lets the standard do its legal job.

The Subtract to Ship angle

Subtract to Ship applied to this topic is about scope discipline. The temptation when you learn how Article 8 and Annex Z work is to pile on more harmonised standards, "just to be safe." The reality is the opposite. Every standard added to your scope costs test time, document time, and review time. The standards you should apply are the ones whose Annex Z actually maps to the MDR requirements your device triggers — no more, no less. The MDR is the North Star. Each harmonised standard is a tool you pick up only because a specific MDR requirement exists that it efficiently discharges. When no MDR requirement justifies the standard, the standard leaves the scope. This is what keeps the electrical safety work honest and what keeps the test budget from quietly tripling before the first lab visit.

Reality Check — Where do you stand?

  1. Can you state, in one sentence, what presumption of conformity means legally and what it does not do for you?
  2. Have you located MDR Article 8 in the current consolidated text and read it?
  3. Do you cite the full harmonised reference string EN 60601-1:2006+A1+A12+A2+A13:2024 in your technical file, or are you citing "IEC 60601-1" loosely?
  4. Have you checked the current OJEU listing within the last quarter to confirm the version you cite is still the one conferring presumption?
  5. Have you read Annex Z of EN 60601-1 and mapped its rows to the specific Annex I sections your device triggers?
  6. Do you have a written list of the MDR requirements your device must meet that are NOT covered by any Annex Z in your standards scope, with a plan for how you will demonstrate each one?
  7. When a reviewer asks "why 60601?" can you answer with Article 8 and Annex Z, or only "because everyone uses it"?

Frequently Asked Questions

Does the MDR mention IEC 60601-1 by name? No. The MDR text contains no reference to IEC 60601-1 or EN 60601-1. What it contains is MDR Article 8, which establishes presumption of conformity for harmonised standards whose references are published in the Official Journal of the European Union. EN 60601-1:2006+A1+A12+A2+A13:2024 is one of the standards listed through that channel.

What is the difference between IEC 60601-1 and EN 60601-1? IEC 60601-1 is the international standard published by the International Electrotechnical Commission. EN 60601-1 is the European adoption of that international standard, published by CENELEC, with a European Annex Z that maps the standard's clauses to specific MDR requirements. Only the EN version, listed in the OJEU, confers presumption of conformity under MDR Article 8.

What does Annex Z do? Annex Z is the normative annex in every harmonised European standard that maps the standard's clauses to the MDR requirements the standard is intended to address. It is the legal bridge between the standard and the Regulation. Reading Annex Z tells you exactly which MDR requirements a given standard covers and, by implication, which ones it does not.

If I follow EN 60601-1, am I fully MDR-compliant? No. Following EN 60601-1:2006+A1+A12+A2+A13:2024 gives you presumption of conformity with the electrical, mechanical, thermal, and radiation safety requirements of Annex I that the standard's Annex Z maps to. It does not cover classification, clinical evaluation, QMS, post-market surveillance, vigilance, or any of the other MDR obligations that a manufacturer owes independently.

Where do I find the current OJEU listing of harmonised standards under MDR? The European Commission publishes and updates the list of harmonised standards on the EUR-Lex website and on the Commission's own DG GROW pages. The listing takes the form of implementing decisions that name the standards and state which MDR requirements they cover. MDCG 2021-5 Rev.1 explains the mechanism in full.

Is presumption of conformity legally binding on a Notified Body? Yes, within its scope. A Notified Body cannot reject an MDR requirement as unmet if the manufacturer has correctly applied a harmonised standard that carries presumption of conformity for that requirement, absent specific evidence that the presumption does not hold for the device in question. The presumption is rebuttable but not arbitrary.

Sources

  1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, Article 8 (Use of harmonised standards), Annex I Section 14 (construction of devices and interaction with their environment), Annex I Section 17 (electronic programmable systems), Annex I Section 18 (active devices and devices connected to them). Official Journal L 117, 5.5.2017.
  2. MDCG 2021-5 Rev.1 — Guidance on standardisation for medical devices. Revision 1, July 2024. Medical Device Coordination Group.
  3. EN 60601-1:2006+A1+A12+A2+A13:2024 — Medical electrical equipment — Part 1: General requirements for basic safety and essential performance. European adoption of IEC 60601-1:2005 with amendments A1:2012, A12:2014, A2:2020 and A13:2024.

This post is part of the Electrical Safety & Systems Engineering Under MDR series in the Subtract to Ship: MDR blog. Authored by Felix Lenhard and Tibor Zechmeister. The MDR is the North Star. EN 60601-1:2006+A1+A12+A2+A13:2024 is the harmonised tool Article 8 lets you pick up to discharge a defined slice of Annex I efficiently — nothing more, nothing less.