<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Jul 2026 &#8211; Eisner Safety Consultants</title>
	<atom:link href="https://eisnersafety.com/category/jul-2026/feed/" rel="self" type="application/rss+xml" />
	<link>https://eisnersafety.com</link>
	<description>Regulatory &#38; Safety Experts for Global Medical Device Approvals</description>
	<lastBuildDate>Tue, 28 Jul 2026 09:21:08 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://eisnersafety.com/wp-content/uploads/2025/08/favicon-45x45.png</url>
	<title>Jul 2026 &#8211; Eisner Safety Consultants</title>
	<link>https://eisnersafety.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>The IEC 60601-1 4th edition, in one place: the map, the timeline, and where to actually start</title>
		<link>https://eisnersafety.com/2026/07/28/iec-60601-1-4th-edition-in-one-place/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=iec-60601-1-4th-edition-in-one-place</link>
		
		<dc:creator><![CDATA[leoeisner]]></dc:creator>
		<pubDate>Tue, 28 Jul 2026 09:21:07 +0000</pubDate>
				<category><![CDATA[60601-1]]></category>
		<category><![CDATA[60601-1, 4th edition]]></category>
		<category><![CDATA[AI]]></category>
		<category><![CDATA[Architecture Specification]]></category>
		<category><![CDATA[Coexistence]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[Design Specification]]></category>
		<category><![CDATA[Device]]></category>
		<category><![CDATA[Draft Guidance]]></category>
		<category><![CDATA[EMC]]></category>
		<category><![CDATA[Essential Performance]]></category>
		<category><![CDATA[FDA]]></category>
		<category><![CDATA[Guidance]]></category>
		<category><![CDATA[Hamonised Standards]]></category>
		<category><![CDATA[Harmonized Standards]]></category>
		<category><![CDATA[Hazards]]></category>
		<category><![CDATA[IEC]]></category>
		<category><![CDATA[IEC 60601-1]]></category>
		<category><![CDATA[IMDRF]]></category>
		<category><![CDATA[ISO 20417]]></category>
		<category><![CDATA[Jul 2026]]></category>
		<category><![CDATA[Labeling]]></category>
		<category><![CDATA[Marking]]></category>
		<category><![CDATA[MDR]]></category>
		<category><![CDATA[Mechanical]]></category>
		<category><![CDATA[Medical Device]]></category>
		<category><![CDATA[Medical Device Regulation]]></category>
		<category><![CDATA[Notified Bodies]]></category>
		<category><![CDATA[Patient Safety]]></category>
		<category><![CDATA[PEMS]]></category>
		<category><![CDATA[Physiologic Closed-Loop Control]]></category>
		<category><![CDATA[Regulation]]></category>
		<category><![CDATA[Regulatory Affairs]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[SaMD]]></category>
		<category><![CDATA[SiMD]]></category>
		<category><![CDATA[Single Fault Condition]]></category>
		<category><![CDATA[Standards]]></category>
		<category><![CDATA[Standards Development]]></category>
		<category><![CDATA[State of the Art]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Usability Engineering Process]]></category>
		<category><![CDATA[User Interfaces]]></category>
		<category><![CDATA[Workshops]]></category>
		<guid isPermaLink="false">https://eisnersafety.com/?p=8585</guid>

					<description><![CDATA[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.]]></description>
										<content:encoded><![CDATA[
<article class="esc-blog">
<style>
  .esc-blog{--navy:#143A5E;--blue:#2E75B6;--ltblue:#9FC0E0;--cream:#F4EFE2;--ink:#1c2b38;
    max-width:820px;margin:0 auto;padding:0 18px;
    font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif;
    color:var(--ink);line-height:1.65;font-size:18px;}
  .esc-blog h1{color:var(--navy);font-size:2.05rem;line-height:1.2;margin:.2em 0 .35em;}
  .esc-blog h2{color:var(--navy);font-size:1.5rem;margin:1.8em 0 .5em;
    border-bottom:3px solid var(--ltblue);padding-bottom:.25em;}
  .esc-blog .dek{font-size:1.15rem;color:var(--blue);font-weight:600;margin:0 0 1.2em;}
  .esc-blog a{color:var(--blue);text-decoration:underline;}
  .esc-blog figure{margin:1.4em 0;text-align:center;}
  .esc-blog figure img{max-width:100%;height:auto;border-radius:8px;}
  .esc-blog figcaption{font-size:.9rem;color:#5a6b78;margin-top:.5em;font-style:italic;}
  .esc-blog .imgslot{border:2px dashed var(--blue);background:var(--cream);border-radius:8px;
    padding:26px 18px;color:var(--navy);font-size:.95rem;}
  .esc-blog .imgslot strong{display:block;font-size:1rem;margin-bottom:4px;}
  .esc-blog table{width:100%;border-collapse:collapse;margin:1.2em 0;font-size:.96rem;}
  .esc-blog th{background:var(--navy);color:#fff;text-align:left;padding:10px 12px;font-weight:600;}
  .esc-blog td{padding:9px 12px;border-bottom:1px solid #d8e2ec;vertical-align:top;}
  .esc-blog tbody tr:nth-child(even){background:#eef4fa;}
  .esc-blog .cd2{color:#1d6b3a;font-weight:700;}
  .esc-blog .cd3{color:#0f7a5a;font-weight:700;}
  .esc-blog .cd1{color:#8a6d1f;font-weight:600;}
  .esc-blog .callout{background:var(--cream);border-left:6px solid var(--blue);
    border-radius:6px;padding:14px 18px;margin:1.4em 0;}
  .esc-blog ul.shelf{list-style:none;padding-left:0;}
  .esc-blog ul.shelf li{padding:10px 0 10px 30px;border-bottom:1px solid #e3e9ee;position:relative;}
  .esc-blog ul.shelf li:before{content:"▸";color:var(--blue);position:absolute;left:6px;top:9px;font-size:1.1em;}
  .esc-blog ul.actions li{margin:.4em 0;}
  .esc-blog .cta{background:var(--navy);color:#fff;border-radius:10px;padding:22px 24px;margin:2em 0 1em;}
  .esc-blog .cta h2{color:#fff;border:none;margin-top:0;}
  .esc-blog .cta a{color:var(--ltblue);font-weight:600;}
  .esc-blog .cta .btn{display:inline-block;background:var(--blue);color:#fff;text-decoration:none;
    padding:11px 20px;border-radius:6px;font-weight:700;margin:8px 8px 0 0;}
  .esc-blog .cta-mini{background:var(--navy);color:#fff;border-radius:10px;
    padding:14px 18px;margin:1.3em 0;display:flex;flex-wrap:wrap;align-items:center;gap:10px;}
  .esc-blog .cta-mini p{margin:0;font-size:.98rem;color:#fff !important;flex:1 1 300px;}
  .esc-blog .cta p, .esc-blog .cta-mini p, .esc-blog .cta p strong, .esc-blog .cta-mini p strong,
  .esc-blog .cta-mini p span{color:#fff !important;}
  .esc-blog .cta-mini p span{display:block;}
  .esc-blog .cta-mini .btn{display:inline-block;background:var(--blue);color:#fff;text-decoration:none;
    padding:8px 14px;border-radius:6px;font-weight:700;font-size:.92rem;}
  .esc-blog .tags{color:var(--blue);font-size:.9rem;margin-top:1.4em;}
  .esc-blog .draftnote{font-size:.82rem;color:#8a6d1f;background:#fbf6e6;border:1px solid #e6d8a8;
    border-radius:6px;padding:8px 12px;margin:1em 0;}
</style>

<p class="dek">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.</p>

<figure>
  <img decoding="async" src="https://eisnersafety.com/wp-content/uploads/2026/07/Binders-Tall-Ladder-scaled.jpg" alt="A tall stack of binders with a ladder leaning against it">
  <figcaption>Edition 3.2 is around 500 pages. The 4th edition is heading past 1,000.</figcaption>
</figure>

<p>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.</p>

<p>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.</p>

<div class="cta-mini">
  <p style="color:#ffffff !important"><span style="color:#ffffff !important"><strong style="color:#ffffff !important">Want this mapped to your specific device</strong></span>
  <span style="color:#ffffff !important"><strong style="color:#ffffff !important">or learn more about IEC 60601-1, 4th Ed.?</strong></span>
  <span style="color:#ffffff !important">That is the work my team does with clients.</span></p>
  <a class="btn" target="_blank" rel="noopener" href="https://eisnersafety.com/schedule-call/">Schedule a call</a>
  <a class="btn" target="_blank" rel="noopener" href="https://mailchi.mp/eisnersafety.com/newsletter-signup">Get the newsletter</a>
</div>

<h2>1. The structure: twelve hazard-based fragments</h2>

<p>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:</p>

<table>
  <thead><tr><th>Fragment</th><th>Working&nbsp;Group</th><th>Hazard area</th><th>Latest draft</th></tr></thead>
  <tbody>
    <tr><td>Frag 1</td><td>WG 37</td><td>General requirements</td><td><span class="cd2">CD2 (Jul 2026)</span></td></tr>
    <tr><td>Frag 2</td><td>WG 38</td><td>Physical environment hazards</td><td><span class="cd2">CD2 (Jul 2026)</span></td></tr>
    <tr><td>Frag 3</td><td>WG 39</td><td>User interface hazards: (usability, information supplied by the manufacturer, alarms)</td><td><span class="cd2">CD2</span></td></tr>
    <tr><td>Frag 4</td><td>WG 40</td><td>Materials hazards: (biocompatibility; cleaning, disinfection, &amp; sterilization)</td><td><span class="cd3">CD3 (Jul 2026)</span></td></tr>
    <tr><td>Frag 5</td><td>WG 41</td><td>PEMS / software: (SaMD, SiMD, firmware, apps, OS, drivers)</td><td><span class="cd1">CD1</span></td></tr>
    <tr><td>Frag 6</td><td>WG 42</td><td>Electrical hazards</td><td><span class="cd1">CD1</span></td></tr>
    <tr><td>Frag 7</td><td>WG 43</td><td>Mechanical hazards: (including acoustic, pneumatic, vibration energy)</td><td><span class="cd1">CD1</span></td></tr>
    <tr><td>Frag 8</td><td>WG 44</td><td>Thermal and fire hazards</td><td><span class="cd1">CD1</span></td></tr>
    <tr><td>Frag 9</td><td>WG 45</td><td>Optical radiation hazards: (visible, UV, IR)</td><td><span class="cd1">CD1</span></td></tr>
    <tr><td>Frag 10</td><td>WG 46</td><td>Ionizing radiation hazards</td><td><span class="cd2">CD2 (Jul 2026)</span></td></tr>
    <tr><td>Frag 11</td><td>WG 47</td><td>Electromagnetic exposure (EMF) hazards, including SAR</td><td><span class="cd2">CD2</span></td></tr>
    <tr><td>Frag 12</td><td>WG 48</td><td>Electromagnetic disturbances: emissions, immunity, wireless coexistence</td><td><span class="cd1">CD1</span></td></tr>
  </tbody>
</table>
<p class="draftnote">Draft status, committee-draft stage, as of July 2026. &#8220;CD&#8221; = committee draft; higher numbers are later rounds. Treat all fragment content as current draft, not final.</p>

<p>That structure is not arbitrary, and you do not have to take my word for it. Behind it sits the <strong>Architectural Specification</strong> (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 <strong>Design Specification Outline</strong> (30 November 2023) then implements that architecture, laying out how the work is grouped into the twelve hazard concepts above. An editing team, <strong>AG 50</strong>, the leadership of all twelve working groups, keeps twelve fragments reading as one standard.</p>

<div class="callout">
  <p style="margin:0 0 .4em"><strong>Both specifications are public documents you can read yourself:</strong></p>
  <p style="margin:0">Architectural Specification (2020): <a target="_blank" rel="noopener" href="https://assets.iec.ch/public/tc62/62_348e_Q%20(posted).pdf?2026071947">assets.iec.ch/public/tc62/62_348e_Q</a><br>
  Design Specification Outline (2023): <a target="_blank" rel="noopener" href="https://assets.iec.ch/public/sc62a/IEC_60601-1_Ed._4.0_Design_Specification_2023-11-03.pdf?2026071926">assets.iec.ch/public/sc62a/IEC_60601-1_Ed._4.0_Design_Specification</a></p>
</div>

<p>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.</p>

<h2>2. Where the drafts stand, and the timeline</h2>

<p>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.</p>

<p>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 <strong>25 September 2026</strong>.</p>

<p><strong>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.</strong></p>

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

<figure>
  <img decoding="async" src="https://eisnersafety.com/wp-content/uploads/2026/07/SW1_slide1_v2_blog.png" alt="IEC 60601-1 4th edition timeline from July 2026 to publication in April 2031" style="max-width:560px;">
  <figcaption>The 4th-edition timeline, from where we are now to publication around 2031.</figcaption>
</figure>

<table>
  <thead><tr><th>Milestone</th><th>Target</th></tr></thead>
  <tbody>
    <tr><td>Official kickoff</td><td>April 2024</td></tr>
    <tr><td>Fragment committee drafts (CD1 / CD2 / CD3)</td><td>Through 2026 into early 2027</td></tr>
    <tr><td>Fragments begin merging into one document (toward CDV1)</td><td>~ October 2027</td></tr>
    <tr><td>Submit Merged CDV1</td><td>December 2028 (goal June 2028)</td></tr>
    <tr><td>Merged CDV2 comments resolved</td><td>~ June 2030</td></tr>
    <tr><td>FDIS Submitted</td><td>~ January 2031</td></tr>
    <tr><td>IS Publication</td><td>~ April 2031</td></tr>
  </tbody>
</table>

<p>Treat the dates as goals; these schedules are likely to shift again. The point is the opposite of &#8220;relax, it is years away.&#8221; 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.</p>

<h2>3. Where to go deeper (the shelf)</h2>

<p>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:</p>

<ul class="shelf">
  <li>The <a target="_blank" rel="noopener" href="https://go.tuv.com/iec-seminar-thankyou">TÜV Rheinland 4th-edition seminar</a>, presented by Leo Eisner, Caitlin Brady and Elizabeth Casey. Working-group material from the people writing the drafts.</li>
  <li>The <a target="_blank" rel="noopener" href="https://eisnersafety.com/wp-content/uploads/2026/07/EN-60601-1-EU-REP-MDR-cheat-sheet.pdf">EU MDR / EN 60601-1 harmonisation cheat sheet</a> on how the current standard lines up with the MDR, Annex ZZ, and state of the art.</li>
  <li>The <a target="_blank" rel="noopener" href="https://eisnersafety.com/wp-content/uploads/2026/07/IEC60601_4thEd_Podcast_Resource_Kit_One_Pager_v22.pdf">4th-edition one-page cheat sheet</a>: IEC 60601-1, 4th Edition: Strategic Changes and Preparation Strategy.</li>
  <li>The LinkedIn series this hub grew from: <a target="_blank" rel="noopener" href="https://www.linkedin.com/posts/leoeisnersafetyconsultants_iec601guy-standardsdevelopment-medicaldevices-activity-7482437445863501824-XA7f">start with the very first post</a>. 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.</li>
</ul>

<figure>
  <img decoding="async" src="https://eisnersafety.com/wp-content/uploads/2026/07/Dont-waste-time-on-a-project-design-copy-scaled.png" alt="Do not waste time on a project design">
  <figcaption>Start the readiness work early, so project time is not lost to avoidable redesign later.</figcaption>
</figure>

<h2>4. Strategic readiness: your action items</h2>

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

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

<p>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.</p>

<div class="cta">
  <h2>Turn this into practical action</h2>
  <p style="color:#ffffff !important">If you have been meaning to get oriented on the 4th edition and did not know where to start: start here, with Eisner Safety Consultants support.</p>
  <a class="btn" target="_blank" rel="noopener" href="https://eisnersafety.com/schedule-call/">Schedule a call with Leo, the IEC 60601 Guy</a>
  <a class="btn" target="_blank" rel="noopener" href="https://mailchi.mp/eisnersafety.com/newsletter-signup">Join the ESC newsletter</a>
  <a class="btn" target="_blank" rel="noopener" href="https://www.linkedin.com/in/leoeisnersafetyconsultants/">Connect with Leo on LinkedIn</a>
  <p style="margin:.9em 0 0;color:#ffffff !important">The newsletter carries the deeper analysis and the extras that never make the short LinkedIn posts. Keep the conversation going on LinkedIn.</p>
</div>

</article>




<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
