---
title: MDR Electrical Safety Updates: Key Changes in IEC 60601-1 Edition 3.2 for Startups
description: EN 60601-1 has accumulated amendments through A1, A12, A2, A13 — sometimes called Edition 3.2. Here are the changes that matter for startups.
authors: Tibor Zechmeister, Felix Lenhard
category: Electrical Safety & Systems Engineering
primary_keyword: IEC 60601-1 edition 3.2 updates
canonical_url: https://zechmeister-solutions.com/en/blog/iec-60601-1-edition-3-2-updates
source: zechmeister-solutions.com
license: All rights reserved. Content may be cited with attribution and a link to the canonical URL.
---

# MDR Electrical Safety Updates: Key Changes in IEC 60601-1 Edition 3.2 for Startups

*By Tibor Zechmeister (EU MDR Expert, Notified Body Lead Auditor) and Felix Lenhard.*

> **IEC 60601-1 edition 3.2 updates is the informal shorthand for the current consolidated version of the general medical electrical equipment safety standard — EN 60601-1:2006+A1+A12+A2+A13:2024. Edition 3 was published in 2005. Edition 3.1 consolidated amendment A1 in 2012. "Edition 3.2" is the working label the community uses for the state of the standard after A2 and A13 are layered in. The IEC itself has not re-released the standard as a numbered Edition 3.2; the authoritative reference under the MDR remains EN 60601-1:2006+A1+A12+A2+A13:2024. For startups the practical question is not the label. It is which specific changes in A2 and A13 touch your design, your risk file, and your test plan — and which do not.**

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

---

## TL;DR

- The current consolidated form of the general standard is EN 60601-1:2006+A1+A12+A2+A13:2024. "Edition 3.2" is an informal community label for this state of the standard, not an official IEC edition number.
- Edition 3 (2005) was the large structural rewrite. A1 (2012) became Edition 3.1 and reworked risk management integration and essential performance language. A2 (2020 at IEC level, layered into the EN in 2021) added targeted clarifications across many clauses. A13:2024 is the current A-deviation layer relevant to the European EN version.
- The amendments are mostly clarifications, not revolutions. If your design was already disciplined about risk management, essential performance definition, and protection strategies, the updates are manageable. If it was not, the updates surface pre-existing weaknesses earlier.
- The changes map to the same MDR Annex I provisions as the base standard — Sections 14, 17, and 18. The Regulation has not moved; the harmonised tool around it has.
- For startups the practical impact is narrow: verify you are citing the current consolidated reference in your technical file, confirm your essential performance definition survives the clarified language, and check that your EMC collateral version is current.

---

## Why the version of the standard matters

A Notified Body reviewer opens the technical file. The first thing they check, after the device description, is which version of each harmonised standard you applied. If the version is outdated, every piece of evidence built on top of that version is now in question. Not automatically invalid — but in question, which in regulatory work is close to the same thing.

The MDR framework treats harmonised standards as the efficient route to presumption of conformity under Article 8. That presumption only attaches to the version of the standard whose reference is published in the Official Journal of the European Union. When a new amendment lands and the reference in the OJEU moves, the previous version starts a transition window. Work done under the old version is not immediately invalid — but the file has to show which version was used, why, and whether any changes in the new version affect the evidence.

For electrical safety this matters more than for most standards, because the 60601 family has been amended repeatedly over two decades and the consolidated reference is long. EN 60601-1:2006+A1+A12+A2+A13:2024 is the correct current reference. Not "IEC 60601-1 3rd edition." Not "60601-1 with amendments." The full consolidated reference, exactly as written, is what belongs in the standards list of the technical file.

## What "Edition 3.2" actually means

The IEC publishes 60601-1 as a numbered edition with formal amendments attached. Edition 3 was published in 2005 and represented the largest rewrite of the standard in its history, most visibly because it moved the entire standard onto a risk-management foundation aligned with ISO 14971. Edition 3.1 was the consolidated form after amendment A1 (published in 2012) was folded in. There is no IEC-issued "Edition 3.2" as a numbered release. The phrase is the working label the community uses when A2 is layered on top of Edition 3.1.

On the European side, the picture is slightly different because the EN version carries additional A-deviations — the A11, A12, and A13 amendments are European common modifications or A-deviations layered on top of the IEC base. The current consolidated EN reference is EN 60601-1:2006+A1+A12+A2+A13:2024. Every amendment in that stack is authoritative. Dropping any of them in your citation makes the citation incomplete.

The practical advice is to write the full reference, always, with no abbreviation. A Notified Body reviewer can tell at a glance whether a startup is disciplined about standards from how the references are written in the file. A sloppy reference is a reliable leading indicator of sloppy evidence.

## Key technical changes — where A2 and A13 actually land

The amendments are mostly clarifications and targeted updates rather than rewrites of fundamental requirements. That is good news and bad news. Good news: a disciplined design built against the earlier consolidated form rarely has to be redesigned. Bad news: the clarifications sharpen the requirements, which means half-measures that used to pass quiet review now draw questions.

The broad areas where clarifications concentrate:

**Risk management integration.** The standard is explicit that risk management under ISO 14971 is not parallel to 60601-1 compliance — it is underneath it. The amendments reinforce that the risk management file feeds the essential performance definitions, the single-fault condition analysis, and the selection of protection strategies. Teams that treated risk management as a separate binder see this cleanup as the biggest change. Teams that were already running a live risk file barely notice.

**Essential performance language.** The definition of essential performance has been tightened in successive amendments. The current form expects a written, specific, verifiable definition for every device in scope, or a documented conclusion that no essential performance exists for that device. Hand-wavy definitions — "the device shall be accurate and reliable" — were always weak; under the clarified language they are formally insufficient. The deep-dive post on basic safety and essential performance walks through what a verifiable definition looks like.

**Means of Protection nomenclature and application.** MOP, MOOP, and MOPP terminology is unchanged in intent, but the clauses that describe how to select and document the protection strategy have been clarified, particularly around patient-contact parts and the interaction between isolation barriers and applied-part classification.

**Single-fault condition analysis.** Clarifications around what counts as a credible single fault, how the fault is introduced during test, and how the device must behave under that fault. The spoke post on single-fault condition analysis goes deeper.

**Documentation expectations.** Clearer expectations on what goes into the risk management documentation that accompanies the standard's test report, and how the manufacturer's rationale is recorded.

None of these is a new requirement invented out of nothing. Every one of them sharpens a requirement that already existed in the earlier consolidated form.

## EMC and immunity updates

EMC sits in a separate document — EN 60601-1-2:2015 + A1:2021, the collateral standard — but it is impossible to discuss the edition-3.2 era of the general standard without naming the EMC collateral, because the two are applied together and because the collateral has moved in the same period.

The 2014/2015 version of EN 60601-1-2 was itself a significant rewrite of the EMC collateral, introducing the environment-based approach — professional healthcare facility environment, home healthcare environment, and special environments — and raising the immunity levels to reflect the realities of modern clinical spaces full of wireless signals. The A1:2021 amendment layered clarifications on top.

The practical impact on startups: immunity is effectively mandatory for any device with electronics, because MDR Annex I Section 14.2(d) and Section 17.1 require resistance to electromagnetic disturbances. The collateral's pass/fail criteria lean directly on the manufacturer's essential performance definition. A device whose essential performance definition was weak under the earlier form of the general standard will now produce weak EMC pass/fail decisions under the collateral, because there is no clear yardstick for what "still working" means during the exposure.

The spoke post on EMC requirements under EN 60601-1-2 walks through the emission limits, immunity levels, and the environment-based scoping.

## Alarm system updates

For devices that generate alarms as part of their clinical function — infusion pumps, patient monitors, ventilators, dosing systems, home-use monitoring devices — the alarms collateral (EN 60601-1-8) applies on top of the general standard. The alarms collateral has moved in parallel with the general standard, and the clarifications in the general standard's edition-3.2-era wording interact with the alarm collateral's requirements on alarm priorities, alarm signal inactivation, and alarm logging.

The practical change for startups is the same pattern as with EMC: the collateral always relied on the manufacturer's essential performance definition to decide whether a degraded alarm behaviour is a failure. The sharper essential performance expectations in the current general standard force that definition to be explicit about alarms. "Alarms shall function correctly" is not a verifiable criterion. "The high-priority alarm shall be announced within N seconds of the threshold being crossed, under normal and single-fault conditions, including during EMC immunity exposure" is.

If your device produces physiological alarms, the alarms collateral is in scope and the essential performance definition has to cover alarm behaviour explicitly. The deeper treatment lives in the alarms spoke post.

## Home-use considerations

The home healthcare environment is one of the three environments defined by the EMC collateral, and devices intended for home use face tighter immunity and usability expectations than devices restricted to professional healthcare facilities. The home healthcare collateral adds further requirements on robustness, user profile, training, and environmental conditions.

The edition-3.2-era clarifications reinforce that the intended use environment must be declared explicitly, and that the test scope follows from the declared environment. A device that is occasionally used at home but primarily in a clinic still has to be tested to the home environment if the IFU permits home use. Teams sometimes try to avoid the home scope by writing the IFU to exclude home use, which is a legitimate design decision with consequences for market scope — but it has to be deliberate, documented, and reflected in the labelling.

The Subtract to Ship move here is to choose the narrowest intended environment consistent with the business model, because each additional environment in scope adds test work and design constraints. The trade-off is market reach versus scope cost, and it is a conscious decision, not a default.

## What startups should check before testing

Before a formal test lab visit, a founder should work through a short checklist to confirm the standards baseline is current and the evidence will survive review.

**Reference check.** Confirm the technical file lists the current consolidated reference exactly: EN 60601-1:2006+A1+A12+A2+A13:2024. If the file still carries an older form, update it and re-state which version each piece of evidence was produced against.

**Collateral check.** Confirm that every applicable collateral is listed at its current version — EN 60601-1-2:2015+A1:2021 for EMC at minimum, plus any other collaterals (alarms, home healthcare, usability) that your intended use triggers.

**Particular standards check.** If a particular standard applies to your device category, confirm the version in your file is the current one. Particular standards move independently of the general standard.

**Essential performance check.** Read your essential performance definition out loud to a test engineer. Ask: can you verify this? If the answer is hesitation, the definition is not specific enough. Rewrite before the lab visit, not during it.

**Risk file check.** Confirm the ISO 14971 risk management file is live, current, and explicitly feeds the essential performance definition and the single-fault condition analysis. A risk file that was last touched six months ago is a red flag to a Notified Body reviewer.

**Mapping check.** For each planned test in the test plan, confirm it maps to a specific MDR Annex I provision — Section 14, 17, or 18. Evidence that does not map to an obligation is not useful, and obligations without mapped evidence are gaps.

Running this checklist before the lab week is cheap. Running it after a failed test report is expensive.

## Common mistakes

- **Citing an incomplete standard reference.** Writing "EN 60601-1:2006" in the technical file without the amendment chain. Immediate credibility problem with the reviewer.
- **Treating "Edition 3.2" as if it were an official IEC release.** It is a community label. The authoritative reference is the full consolidated EN citation.
- **Forgetting to update the file when the standard moved.** The standard was republished with A13 in 2024. Files that still reference pre-A13 forms without justification are behind.
- **Leaving the essential performance definition unchanged after the clarified language landed.** A weak definition that passed quiet review under the earlier form will draw questions under the current form.
- **Mixing up general and collateral versioning.** EN 60601-1 and EN 60601-1-2 move independently. Updating one without checking the other creates an inconsistent standards list.
- **Assuming the particular standard inherits the general standard's updates automatically.** It does not. Each particular has its own publication and amendment history and must be verified independently.
- **Treating the amendments as a pure paperwork update.** Some of the clarifications have design consequences — especially around protection strategy documentation and single-fault condition interpretation — and skipping a design review when the standard moves is how surprises land at the lab.

## The Subtract to Ship angle

The temptation when a standard updates is to re-do everything. That is maximal addition, and it is exactly what Subtract to Ship cuts. The right move is not "re-test the whole device against the new version." The right move is to identify which specific clauses changed, which of those clauses touched evidence in your file, and to update only those pieces.

For most startups applying the current consolidated form of EN 60601-1:2006+A1+A12+A2+A13:2024 to a device that was already designed with risk management discipline and a specific essential performance definition, the amendment work is a documentation refresh plus a small number of targeted verifications — not a full retest. For startups that skipped the discipline the first time, the amendment work is heavier, but that weight is the cost of the earlier skip, not the cost of the amendment.

The obligation remains the MDR. Annex I Sections 14, 17, and 18 have not moved. The harmonised tool has sharpened. Keep the direction clear — Regulation is the North Star, standard is the route — and the amendment work stays tractable.

## Reality Check — Where do you stand?

1. Does your technical file cite the full current reference EN 60601-1:2006+A1+A12+A2+A13:2024, or an incomplete abbreviation of it?
2. Have you read the clauses that changed in A2 and A13, with someone who can interpret them for your specific device?
3. Is your essential performance definition specific enough to survive a test lab's verification without follow-up questions?
4. Have you checked whether the collaterals in your scope (EMC, alarms, home healthcare, usability) are at their current versions?
5. If a particular standard applies to your device, have you confirmed its version independently of the general standard?
6. Has your ISO 14971 risk file been updated to reflect the clarified integration points with the current consolidated form of the standard?
7. For each test in your plan, can you map it back to a specific MDR Annex I Section — 14, 17, or 18?

## Frequently Asked Questions

**Is there an official "IEC 60601-1 Edition 3.2"?**
No. Edition 3 was published in 2005. Edition 3.1 consolidated amendment A1 in 2012. The informal label "Edition 3.2" is sometimes used for the state of the standard after A2 (and, at the European level, A13) is layered in, but the IEC has not issued a numbered Edition 3.2. The authoritative reference in a European technical file is EN 60601-1:2006+A1+A12+A2+A13:2024.

**Do I have to redo my test report if I updated to the current consolidated version?**
Not automatically. The decision depends on which clauses changed and whether any of those clauses touched evidence in your existing test report. In most cases the work is targeted — re-verify a small number of points, update the documentation, and keep the rest. A full retest is usually unnecessary unless the design itself moved at the same time.

**Does edition 3.2 change the MDR obligations?**
No. The MDR Annex I obligations — Sections 14, 17, and 18 for electrical safety — are unchanged. What changes is the harmonised tool used to demonstrate conformity with those obligations. The Regulation is the North Star and has not moved. The standard sharpened around it.

**How do I know which version of the standard is harmonised under the MDR?**
Check the list of harmonised standards published in the Official Journal of the European Union for Regulation (EU) 2017/745. The OJEU reference is the authoritative statement of which version of a standard currently provides presumption of conformity. References in the OJEU move as amendments are published, and the transition windows are communicated in the same list.

**What happens if my file still references an older consolidated form of 60601-1?**
It is not automatically invalid, but it is a finding. The file has to show which version was used, why, and whether the subsequent amendments affect the evidence. The cleanest move is to update the reference to the current consolidated form and run the short checklist above to confirm nothing substantive is affected.

**Does the current consolidated standard change anything for software-only devices (SaMD)?**
No. EN 60601-1 applies to medical electrical equipment — physical devices with electronic components. Software as a medical device running on general-purpose hardware is covered by EN 62304 for the software lifecycle and other relevant standards. The 60601 family is not the right tool for pure SaMD.

## Related reading

- [MDR Electrical Safety Requirements: How IEC 60601-1 Helps You Demonstrate Conformity](https://www.zechmeister-solutions.com/blog/mdr-electrical-safety-requirements) — the hub post for the Electrical Safety category.
- [MDR Basic Safety and Essential Performance: Understanding IEC 60601-1 Requirements](https://www.zechmeister-solutions.com/blog/basic-safety-essential-performance-iec-60601-1) — the two organising concepts the amendments sharpen.
- [Electrical Safety Testing for Medical Devices](https://www.zechmeister-solutions.com/blog/electrical-safety-testing-medical-devices) — how the test campaign is structured in practice.
- [Electrical Hazard Protection Under IEC 60601-1](https://www.zechmeister-solutions.com/blog/electrical-hazard-protection-iec-60601-1) — creepage, clearance, Means of Protection, and applied-part classification.
- [EMC Requirements Under IEC 60601-1-2](https://www.zechmeister-solutions.com/blog/emc-requirements-iec-60601-1-2) — the collateral whose immunity tests lean on essential performance.
- [MDR Particular Standards — The IEC 60601-2-XX Family](https://www.zechmeister-solutions.com/blog/mdr-particular-standards-iec-60601-2-xx) — how particulars layer on top of the general standard.
- [Single Fault Condition Analysis Under IEC 60601-1](https://www.zechmeister-solutions.com/blog/single-fault-condition-iec-60601-1) — the test architecture the clarifications sharpen.
- [Electrical Safety Costs Under IEC 60601-1](https://www.zechmeister-solutions.com/blog/electrical-safety-costs-iec-60601-1) — realistic budget ranges for startups.
- [The Subtract to Ship Framework for MDR Compliance](https://www.zechmeister-solutions.com/blog/subtract-to-ship-framework-mdr) — the methodology that keeps the re-scoping work honest when a standard moves.

## Sources

1. Regulation (EU) 2017/745 of the European Parliament and of the Council of 5 April 2017 on medical devices, 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. EN 60601-1:2006+A1+A12+A2+A13:2024 — Medical electrical equipment — Part 1: General requirements for basic safety and essential performance.

---

*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 — and when the tool sharpens, the work is to update precisely, not to rebuild everything.*

---

*This post is part of the [Electrical Safety & Systems Engineering](https://zechmeister-solutions.com/en/blog/category/electrical-safety) cluster in the [Subtract to Ship: MDR Blog](https://zechmeister-solutions.com/en/blog). For EU MDR certification consulting, see [zechmeister-solutions.com](https://zechmeister-solutions.com).*