Articles Questions

Updated January 27, 2023

How Do SemVer Versions Map to Significant Changes for a Medical Device?

Dr. Oliver Eidel


We’re using semantic versioning (semver) for assigning version numbers to our software which we want to certify as a medical device. For future updates, We’re currently trying to understand what constitutes a significant change. We’re wondering: Semver structures the version number as major.minor.patch. Does that mean that we can only increment the patch number as otherwise we’d be making a significant change and would have to get approval of our notified body?

Short Answer

No. You can increment whatever number you want. It depends entirely on the content of the change, not your version number. See my answer on significant changes.

Long Answer

When assessing (significant) changes, it’s all about what you’re changing, not what your new version number will look like. See the answer linked above.

Consider this thought experiment: Instead of semver, you use a versioning scheme which just has one integer number which is incremented. So the first release would be version 1 and the 25th release would be version 25. There’s no way to tell which release contains “major” changes in the semver sense. But some of those changes might still have been significant in the context of a medical device.

So: Use whatever versioning scheme you want, increment the numbers however you like, but assess the content of your changes whether they’re significant.

On a slighty different note: You want to get your medical software certified under MDR but don't know where to start? No worries! That's why we built the Wizard. It's a self-guided software which helps you create your documentation yourself, for only 149€ / month. No prior knowledge required. You should check it out.

Or, if you're looking for some human help, did you know that we also provide consulting, often guiding startups from start to finish in their medical device compliance?

And there's so much more: If you're looking for the best QMS software ever, look no further. We've built Formwork, and it's free!

Congratulations! You read this far.

Get notified when we post something new.

Sign up for our free newsletter.

Dr. Oliver Eidel

I'm a medical doctor, software engineer and regulatory dude. I've helped 50+ companies with their medical device compliance. I mainly work as a regulatory consultant, but my goal is to make consulting unnecessary by publishing all of our articles and templates for free :)

If you're still lost and have further questions, just send me an email. Read more about me here.

Digital Health Jobs No Cookie For You Privacy Policy Imprint
No QMS on this planet will save you from creating crappy software.