The IEC 60601-1 4th edition, in one place: the map, the timeline, and where to actually start

Almost nobody reads a thousand-page draft cover to cover. So here is one place to get oriented, then go deep only where it touches your device.

You have heard the headline: the IEC 60601-1 4th edition is coming, and it is big. Edition 3.2 is around 500 pages. The 4th edition is heading past 1,000, written across twelve hazard-based working groups.

The headline is not the useful part. The useful part is the question underneath it: where do you start, and what do you actually need to read? Almost nobody reads a thousand-page draft cover to cover, and nobody should have to. So this is a hub. It is one place to get oriented and then go deep only where it touches your device, as your device likely will not touch every corner of the standard.

1. The structure: twelve hazard-based fragments

Edition 3.2 is organized by clause. You find a requirement by its number. The 4th edition is currently organized by hazard, split across fragment working groups that will later be merged into one document. Each hazard concept is a fragment, and each fragment has its own working group. Here is the whole map, and where each fragment stands today:

Draft status, committee-draft stage, as of July 2026. “CD” = committee draft; higher numbers are later rounds. Treat all fragment content as current draft, not final.

That structure is not arbitrary, and you do not have to take my word for it. Behind it sits the Architectural Specification (approved 5 May 2020), which sets the direction for the edition, sharpening the focus of basic safety and essential performance and pushing toward discrete, design-ready requirements. The Design Specification Outline (30 November 2023) then implements that architecture, laying out how the work is grouped into the twelve hazard concepts above. An editing team, AG 50, the leadership of all twelve working groups, keeps twelve fragments reading as one standard.

Most people never look at this layer. The original concepts have evolved since these specs were written, based on the experts and National Committee feedback, but they remain the best window into why the 4th edition is shaped the way it is.

2. Where the drafts stand, and the timeline

You do not have to track every document to stay oriented. Every one of the twelve fragments now has at least a first committee draft. Several are on their second draft, and Fragment 4 is furthest along at CD3. It will probably be the only CD3: for most fragments the intent is to publish a CD2, get comments from the National Committees, and move on. A third CD made sense only for WG 40, which has the time and bandwidth in its group to complete one before the project needs to move into the CDV1 phase.

Three recent fragment drafts dropped on 3 July 2026: Physical environment (Frag 2), Materials (Frag 4) and Ionizing radiation (Frag 10). All three are open for comment until 25 September 2026.

Most National Committees need your comments about two weeks before the IEC deadline so they can process them and submit to Geneva. Submit your comments with that buffer in mind, or check with your National Committee for its national deadline, so you do not miss the window.

And the map just moved again: Fragment 1 (General requirements) issued its next committee draft on 24 July 2026 (62A/1759), with comments open to 16 October 2026. Fragment 12 (electromagnetic disturbances) is the one still expected to reach its CD2 shortly.

Treat the dates as goals; these schedules are likely to shift again. The point is the opposite of “relax, it is years away.” The text that becomes the 2031 standard is being written and commented on right now, and if you or your organization are not directly involved in writing the document (not one of the experts on the WG committees), the comment windows are the best way to provide your feedback.

3. Where to go deeper (the shelf)

You do not need to read everything, but you do need to start preparing now and understand the impact on your device designs, your test plans, your QMS, your document control, and your supply chain. Here is a starter kit to map to your device, plus a couple of orientation pieces:

• The TÜV Rheinland 4th-edition seminar, presented by Leo Eisner, Caitlin Brady and Elizabeth Casey. Working-group material from the people writing the drafts.
• The EU MDR / EN 60601-1 harmonisation cheat sheet on how the current standard lines up with the MDR, Annex ZZ, and state of the art.
• The 4th-edition one-page cheat sheet: IEC 60601-1, 4th Edition: Strategic Changes and Preparation Strategy.
• The LinkedIn series this hub grew from: start with the very first post. The next post in the series is linked in a comment on that post, and each post carries the chain forward the same way. Follow it and you will reach the whole series, including the Standards Watch posts tracking new drafts and comment windows.

4. Strategic readiness: your action items

You do not need the final text to start. Here is the readiness list I walk teams through:

• Map your design controls against the draft working-group requirements now, rather than waiting for the next draft.
• Run a full QMS gap analysis: risk management file, conformity evaluation file, and the EMF and biocompatibility assessment reports.
• Pull R&D, RA/QA, software, labeling, supplier quality and manufacturing into your readiness reviews. This is not a regulatory-only exercise.
• Embed cybersecurity, AI/ML and PEMS design inputs early in the pipeline, not at verification.
• Update labeling, symbols, packaging and IFU against ISO 20417 and the working-group requirements.
• Engage suppliers now for SBOM, spacing changes, power cords and component impacts. Supplier lead time is where these programs slip.

That list is the orientation. Turning it into a real gap analysis and a plan for your specific device is the part that takes experienced hands. Day to day, my team supports manufacturers, test labs, and regulators with exactly this: strategic readiness, CEP/CEF development, and training teams up on the 4th edition. It does not have to be a heavy engagement, either. One client took a four-hour CEP/CEF workshop and had the concept working in their process the next week.