There are two things to know about IEC 62304 Edition 2 this month. The first is that the August 2026 milestone is CD2, the second committee draft, not publication. The second is that on the reported committee timeline, publication is years out rather than weeks.
Here is the current stage, the reported dates, and the method for checking both yourself.
What is actually happening this month
The Johner Institute and VDE both track the IEC committee work directly. Both report the same thing. The milestone for IEC 62304 Edition 2 in August 2026 is the release of CD2, the second committee draft.
The working group, IEC SC62A maintenance team MT49, received roughly 1,500 comments on the first committee draft from 2025. CD2 is the version that incorporates those comments. It then goes out for another round of comment.
The Johner Institute reports that an FDIS is not expected until 2028, and that publication may therefore not happen until 2029. IEC's own forecast publication date is listed as October 2028. All three of those are reported figures, not settled dates, and committee schedules move.
Whatever the dates turn out to be, the stage itself is not in doubt, and a committee draft is not a standard. Comments received on CD2 will keep being evaluated, and the Johner Institute is explicit that substantive changes to central requirements remain possible before publication.
How to read a standard's stage
Testers already know how to do this from software versioning. You would not ship against an API that was still in preview and call it stable. A standard has the same kind of version ladder, and it is public.
The stages run in this order:
- CD (committee draft): the working group's text, circulated for comment. Content can still change a lot. This is where Edition 2 sits.
- CDV (committee draft for vote): circulated for technical comment and a vote. Prior IEC 62304 Edition 2 work reached this stage under document number 62A/1422/CDV.
- FDIS (final draft international standard): the text is essentially frozen and national committees vote yes or no. This is the point where planning against clause numbers becomes reasonable.
- Publication: the standard exists and can be cited.
Before you plan work against any standard revision, find its stage. A summary that names a publication date without naming the document stage may not have checked either.
What Edition 2 currently proposes, correctly labelled
Everything in this section is draft content, which makes it useful to know and premature to implement.
The reported changes are significant, starting with scope. It widens from medical device software to health software, which may pull in products that never claimed device status. The three safety classes A, B and C are replaced by two software process rigor levels. Level I stands in for Class A, and Level II combines Classes B and C, so the draft stops separating them. IEC's own drafting documents write the term out and set no abbreviation, while VDE's summary shortens it to PRL I and PRL II. New requirements cover cloud decommissioning, maintenance, and verification of the software architecture. AI and agile development each get an annex, and both annexes are reported as informative, meaning they carry guidance rather than requirements.
If that list looks like a large migration, it is. On the reported timeline you have years rather than months, and the clause numbers you would migrate to are not final.
What to do now, and what to leave alone
So what is safe to do this year? Which part of the Edition 2 work can start now without being done twice? The answer is the classification work Edition 1 already asks for. Take the Edition 2 migration item off this year's roadmap, and tailor what you keep to Edition 1 as it stands.
- Build the software item inventory. List every software item, its current safety class, and where that classification is written down. The inventory tends to turn up incomplete before anything else does.
- Write down the classification rationale. Record the reasoning, not only the class. Why is this item Class B and not C? Which hazardous situation did you decide it cannot contribute to? A rationale that lives in one engineer's head may cost you during any reclassification, and it can turn into a finding at your next audit regardless.
- Leave your procedures alone. Do not rewrite SOPs against draft clause numbers, and do not rename artifacts to match the rigor levels. That work would be done twice.
- Read CD2 when it lands, and log comments if you can. The comment period is the only point where a manufacturer can influence the text.
Neither the inventory nor the rationale is early Edition 2 work. Edition 1 already asks for both, and many quality systems may carry a gap there today.
Where Nopmark fits
Nopmark's IEC 62304 course teaches Edition 1 as it stands. That means classification, lifecycle documentation, and the V&V evidence that survives an audit. That remains the version you are held to, and on the reported timeline it will stay that way for several years. The course sits with the software validation and risk management courses in the medical device bundle. When Edition 2 does publish, enrolled learners get the update at no extra cost. Nopmark does not put a year on when that will be.
FAQ
When does IEC 62304 Edition 2 publish?
No published date exists. The Johner Institute reports that an FDIS is not expected until 2028, with publication possibly in 2029, and IEC's forecast publication date is listed as October 2028. None of these dates is a commitment.
What is happening in August 2026?
CD2, the second committee draft, is expected. The Johner Institute and VDE both report this. It follows roughly 1,500 comments received on the first committee draft from 2025.
Why do some sites say Edition 2 arrives in 2026?
Standards summaries are often written from a target date without naming the document stage that date belongs to. A target for a committee milestone reads as a publication date once the stage label is dropped. Check the stage before you trust the year.
Should I start migrating to software process rigor levels now?
No. The rigor levels are draft content and the clause numbers can still change. Build your software item inventory and write down your classification rationale instead, because both are useful under Edition 1 today.
Does IEC 62304 Edition 1 still apply?
Yes. Edition 1 remains the version in force and the version regulators recognise. Nothing about the committee draft changes your current obligations.
Nopmark's IEC 62304 course teaches the standard as it stands today, with accredited instructors and worked examples drawn from real quality systems. That is where the classification and lifecycle evidence that holds up at audit gets built.