Hi, I assume you landed on this video because you are interested in software and medical devices. If so, this is the right place for you. In this short course, my goal is to give you practical tips when working with software in medical devices. At the end of this video, I will share tips about software risk management, which is painful if you don't get it right. I'm Christian Kaestner, and I started my career as embedded software engineers in the early 90s. After a couple of years, I moved into the medical device field, where I've done sterilisation equipment, transplantation devices, wound care therapy, and much more. Seven years ago, I joined a project team authoring IEC 62304. I also work as a lead auditor. This ensures I have insights from both sides of the fence. This short course applies to you if you are developing a medical device software that is an app, software as a medical device, or embedded software. As a medical device software developer, you need to comply with the standard IEC 62304. For this short course, my goal is to give you inspiration on how to comply with the standard without killing your creativity. I will give you a jump-start into the wonderful world of IEC 62304. Number one, I will show you that the world does not need to be waterfall-ish. Two, I will also show how you can manage legacy products without doing everything from scratch. Three, I will give you a few tips about how version control can do more than just keeping track of your source code. And lastly, number four, you will learn how software risk is calculated. So, let's get started. The general idea with a standard is to establish a common way of thinking which can be recognised by various stakeholders, such as regulatory authorities. When a standard is recognised by authorities, it means that if you comply with the standard, you will most likely also be complying with applicable regulatory requirements. IEC 62304 is a process standard, which means you will not find details like performance or screen resolution requirements. What you will find is a list of requirements and activities you should carry out throughout your development cycle. The standard is structured in a very sequential way, which implies a waterfall-ish development method. But there's no requirements in the standard forcing you to apply a specific development method. You're fully free to use whatever method you want to, as long as you acknowledge the process approach and don't skip any activities in the standard. Let's take a look at the key elements of the standards. We are talking about development, risk management, configuration management, problem resolution, and maintenance. Each of the processes are divided into activities, with the development process having the most activities. And no, this is not rocket science. If you have been working in a mature organisation developing software, whether that be in defence or mobile phone industry, you will find that the ways of working are similar but use different names. But in the medical device industry, we are obsessed with safety. Because in the medical device, a software bug is not only blue screen, it can literally be blue screen of death. Basically, because a bug can kill someone. Back to the standard. A nice thing with this standard is that the number of activities you need to do depends on how harmful your product can be. This is decided with the help of software safety classification, which I will explain to you later. But the flow through the standard is the same, but the rigour is different depending on your classification. This graphical overview visualises the scope of the standard. Blue boxes are in scope, grey are out of scope. The arrows between blue and grey is where there is an information exchange. The first arrow gives you inputs about "what" and "when". "When" is, for example, pre-releases for various purposes before final release. "What" can be functional requirements, such as information to display on screens or alarm management. It can also be hardware constraints, so like, do you have one or more CPUs available, or should communication happen over USB or Ethernet? In the standard, there is a clause speaking of software requirement content, but there's nothing about how you document your requirements. You can capture requirements in any way you want to. It can be tickets, stories, wiki pages, or advanced requirement management tools. It's entirely up to you. But please remember a couple of formal requirements you need to consider. For example, in your system verification, you must reference a specific set of requirements. This is what I call a baseline. Requirements shall also be reviewed and approved, so please make sure your setup can support you in this work. Traceability is also a requirement. Ideally, your choice of requirement management also supports you with traceability to verification. In addition to when releases are expected, we also need to plan for content, purpose, and how to deliver a release. The expectations are most likely different if you are releasing for usability test, clinical study, or final release for production or upload to App Store. Here we are back to our obsession with safety. To develop a safe software, we need to have input about hazardous situations to understand what we must avoid. Very often, this input also includes risk-related requirements, for example, to display a detailed warning when high blood pressure is detected. The highlighted processes are supporting the development process. As already mentioned, the risk management process helps you to develop a safe software. The configuration management process supports you in keeping track of information, changes, and source code. And last but not least, the problem resolution process, which manages issues with your software. And hopefully, this is your least used process. The bulk of your development work will be in the highlighted section, where you can see the various development activities that will take place in the order in which they should ideally happen. However, it is unlikely your development work will happen exactly like this, and your development method should allow you to be adaptive as your knowledge evolves over time. The key to being adaptive is to be good at working with changes. But what happens if we take smaller steps and use information from previous steps and adjust into the next step? Let's look at Agile principles with the help of Scrum. Scrum development principle embraces changes, but you might feel there's a mismatch between the waterfall approach in the standard compared to working with Agile methods. There's no need to be worried. Working with backlog stories and sprints, sprint planning, can be compared with when eating an elephant, take one bite at a time. Let's take a look at an example from the standard and compare the two ways of working. You need to verify the quality of your requirements by, for example, verifying that they do not contradict one another, are expressed in terms that avoid ambiguity, are traceable to system requirements or other sources. If you review a Scrum story before it gets implemented, you do it by taking one bite at a time. The wordings might be different, but you certainly don't want contradictions and ambiguity in your stories. If I simplify things, you verify requirements on a story-based level instead of verifying your complete backlog of requirements. If we now compare with a waterfall approach, you typically aim for having nearly a full set of requirements, and then you go for a review. In this latter example, you will not verify as frequently as you do in Scrum, but you will spend more time in every review. So, you can work with Agile principle and meet the requirements of the standard. It's only a question of how you have chosen to meet the requirements of the standard. In case you are into Agile development, there is a very good technical report from AAMI. I would recommend this report as a very reliable source of information and guidance. Enjoy your reading. Let us return to the software safety classification. The classification is divided into A, B, and C. A is the lowest class, which means that the software is not likely to contribute to hazardous situations, while C is the highest class, which is applicable when there is a likelihood of a serious injury or even death. If your software is linked to risk with high severity, your classification will go up. In the standard, there is a flowchart for the classification process. The basic idea is that high severity should drive the rigour of your development process. If you dislike the outcome of your classification, you are free to go back and change the intended use or the medical device. You could, for example, reallocate features from software to hardware, or even easier, you could change your requirements. There is of course much more to talk about when it comes to theory and general structure of the standard. But for now, I would continue with other goals which I believe you have more practical use of, so let's kick off with planning. If you search the standard for the word "planning", you will find many hits. I've seen several projects where this results in far too many plans, which is a waste of time and highway to audit observation. Waste of time because you spend too much time in just administrating plans, and audit observation because there's a high chance that your plans are outdated or simply not telling the same story. Instead of making your life hard, I suggest you keep it simple and start with a single plan, a single source of truth. You should only start splitting the project into different plans if it adds value to a project team. This could, for example, be if you have a separate test team, then it could make sense to have a dedicated verification plan. The plan is a very good place to explain how the team is structured and how you interact with your quality management system. I consider it more as a tactical document these days. For example, if you want to use Agile methods and you're stuck with waterfall procedures, then the software development plan is a perfect place to explain and document your specific approach. Let's take a look at an example of what interacting with a quality management system could be. Many quality management systems are developed with a physical piece of paper in mind. You could call it a document-based mindset. Software information is typically not organised based on physical papers. Information is structured based on other aspects, such as architectural or functional considerations. And preferably, the information is kept where it supports the developer the most: in the source code. There's a requirement in the standard about detailed design. The conservative approach to this requirement is to write a traditional document. But since you already version control your source code, why not let some of your documentation coexist with the code instead of forcing the information into traditional paper document? Here, it's up to you. Either you keep the information in the source file, or you decide to extract information from source files and create traditional documents. Your way of working with information and documents can be explained in the software development plan, because there's certainly no need to convert all information to paper documents, but you need to identify where it can be found and how you control it. In this example, I have used Doxygen format for the comments. In case you really, really must, you can also easily extract the comments to traditional document formats, but when you later maintain the code, the documentation is available where it supports the developer the most, and it's also much easier to maintain. Just a quick recap: all projects are different, and the standard procedure cannot describe all projects. Make sure the plan helps you in your work. For this video, I've zoomed in on a few practical aspects with planning, but please don't forget timing aspects, such as what and when you need to deliver something. If you have a product already on the market and need to get in compliance with the standard, the legacy clause is there for you. Some people might find these clauses also convenient for new development. They skip implementing the standard, and then by magic, there's a legacy product because it was developed before applying the standard. This is both cheating and inefficient. I will soon tell you why. But let's start with how the clause is intended to be used. The legacy clause starts with risk management activities. The advantage of having a product already on the market is that you have access to post-market information. You're expected to use this information as input to your risk management activities, and the expected output of this step is identification of hazardous situation and software safety classification. Based on the classification, you are now supposed to do a gap analysis and assess what deliverables are missing compared to if you had implemented the standard as intended from the beginning. You have now identified a list of deliverables which are missing compared to the standard. Review the list and prepare plan to fill the gaps in a timely manner. If, for example, detailed design is missing, it probably doesn't make sense to run away and generate detailed design just because it's missing. It's most likely better to fill this gap when updates are implemented, and this is then what you write in your plan. Now is the moment of truth. With the knowledge you now have, can you justify the continued use of your product from a safety perspective? If yes, document your conclusion and deliver according to your gap closure plan. If not, worst case, you need to stop the continued use of the medical device, including your software. But let's hope it's only half bad, and it can be managed by correcting a few software bugs and re-release the software. Back to the cheating part. From the point in time when you claim legacy, you need to comply with the full standard. This means that sooner or later, you must spend the resources you initially try to avoid. One could argue and say this is now easier because you know the end result. But based on my experience, it's much easier to maintain a properly developed product compared to retrospectively patching it into compliance. Just let me give you an example. Assume you didn't run a full system verification. When you now run a full verification, you find alarms which are not working in all conditions. So, what should you do? Well, either you can pretend like nothing happened, which is a bad idea. You simply must correct the software and release a new version. Worst case, I'm sorry to say, you may even have to contact all your customers and tell them to stop using your medical device. Now you know how to deal with legacy software, and please stay away from cheating. Let's talk about configuration management. I would say that a software project usually has more configuration items to control than all documents together in a full development project. If you look at the definition of a configuration item, it says "entity that can be uniquely identified at a given reference point". In the software domain, a given reference point can be down to hours or even minutes. And this is very different if you compare with a document, which is typically released with the help of a signature and at a much lower pace. Maybe ask yourself, what is a configuration item? Configuration item can be many things. It can be precompiled libraries, build files, source code, compiler settings, basically any piece of information needed to create your deliverable, including documentation. One example of configuration management is version control systems, which can support you with traceability. In this example, you see two branches for bug fixes. By using branches, you can easily review how a specific bug has been resolved. In the bigger picture, version control also supports you in reviewing changes between releases. This is super helpful when you're determining how much regression testing needs to be done, or what you should put into your release note. But it's not only practical aspects in gathering data and providing traceability support. Correctly implemented configuration management can also support process aspects of your development work. Let's break down the flow in a couple of steps. The first step is a decision step. For example, when you decide to implement a change request, you can use roles to define who can create branches and use this to control when implementation work starts in response to an approved change request. The next step is the implementation step. If you define in your procedures that you should always work on a branch and never directly in the main, this assures that you always have traceability back to the reason why you are implementing something. The third step is about verification. This is a great step to implement a peer review, and a good practice is that you're not merging back your own code to the main. The verification step is also a step where you can get a lot of compliance work integrated directly into your workflow. If you prepare good work instructions on how to merge back branches to main, you can cover most of the content of the clauses I've listed here on the screen. The documentation part of this would end up as information pieces in your configuration management system. And as I mentioned in the planning section, it will be then documented, but not as traditional documents. If you haven't done it yet, spend some time in looking for good configuration management tools, which can satisfy your needs. And please, make sure you validate the system and use them as much as you ever can. I assume you have some basic understanding of risk management. If you don't, I recommend you watch the videos about risk management here at medicaldevicehq.com. One of the most misunderstood statements in this field is that probability of occurrence of harm should be set to 100% just because you're working with a software. I can tell you, that statement is wrong. Probability of occurrence of harm can be split up into two components: P1 and P2. The probability of occurrence of the hazardous situation is P1. P2 is the likelihood that the hazardous situation will lead to harm. When people are talking about probability of occurrence of harm and claim it shall be 100%, they refer to P1. But also, this assumption can be challenged. Let's have a look at an example where a software is used to recommend the right medication. In this example, we assume that 1% of the patients are allergic to drug A, and we have five different drugs to choose from. The software fails by choosing wrong medication. So, what is Po for this risk? The right answer is: it depends. It depends on the type of software failure we are dealing with. Either the software failure results in randomly selecting one of the five drugs, or the failure always results in choosing drug A. For the sake of safety, we could assume that drug A always will be selected. But if we are talking about random errors, the likelihood for the software to only select drug B or any other drug is as high as it is for only selecting drug A. This results in a different scenario. In the random drug example, I still agree that a software failure always will happen, but it cannot predict the outcome. So, in this particular case, if the hazardous situation is that drug A is incorrectly chosen, the likelihood of the hazardous situation occurs is 20%, and it's quite the difference. To summarise, if you're working a lot with software, please do yourself a favour and start using P1 and P2. As long as you stay with Po, you will find yourself in a very difficult situation. I will, of course, go into more depth on this topic in the full course, where I also will explain how you work with risk control measures in software to reduce P1 and eventually even P2. Thank you for watching this short course. If you want to learn more about software and medical devices, I welcome you to sign up for the full online course Introduction to Software Development and IEC 62304. The full course is similar to this short course, but much more comprehensive, with more in-depth information and quizzes at the end of each topic to test your knowledge and understanding. At the end of the full course, you will also receive a course certificate, which many auditors will be asking for. At medicaldevicehq.com, we offer online courses, public classroom courses, as well as in-house training on safety, risk management, design control, and project management for medical devices. Drop us a line at support@medicaldevicehq.com if you would like to learn more about your options or receive a proposal. Or write to me on the same email address if you have questions relating to medical devices or development in general. I hope to hear from you.
The course covers the aspects of the IEC 62304 standard, as well as the relationship between IEC 62304 and other standards such as ISO 14971, IEC 60601-1 and IEC 82304-1.
You learn the theory first during the online course, and then apply that theory during the two live virtual classroom sessions.
€ 1099/ seat
| Course length | approx. 16-32 hours (25 CPD points) |
| Next classroom sessions |
8-9 Dec, 2026 |
QUICKSTART
FREE
Average completion time 1-3 hours
Total video duration 32 minutes
Number of quizzes 5
30 days access to the course
Digital course companion
ONLINE
€ 449
Average completion time 9-25 hours
Total video duration 6.5 hours
CPD points 18
Number of quizzes 33
Final exam
Course certificate
Ask the instructor
6 months access to the course and instructor
Digital course companion
ONLINE LIFETIME
€ 549
Average completion time 9-25 hours
Total video duration 6.5 hours
CPD points 18
Number of quizzes 33
Final exam
Course certificate
Ask the instructor
Lifetime access to the course and instructor
Digital course companion
BLENDED
YOU ARE HERE
€ 1099
Average completion time 16-32 hours
Total video duration 6.5 hours
CPD points 25
Number of quizzes 33
Final exam
Course certificate
Ask the instructor
Lifetime access to the course and instructor
Digital course companion
Classroom sessions (2 * 3.5 hours)
Templates
IN-HOUSE TRAINING
CONTACT US
Tailored training to meet your company's needs
This course consists of two parts:
1. Software for Medical Devices and IEC 62304 online course
2. Two half-day live virtual classroom sessions held by the course creator
First, you complete the popular software for medical devices online course. It covers topics such as how to efficiently plan and document software, getting requirements right, how to approach software architecture and software risk management, how to perform software safety classification correctly and working with SOUP/OTS software. Note: The course does not cover coding.
You can start the online course immediately and you must successfully complete the final exam prior to the classroom sessions. If you have already completed the online course, you can register for the classroom sessions only.
The unique, highly interactive live virtual classroom sessions are facilitated by Christian Kaestner, an expert in this field. During the sessions, you get to apply the theory you have learnt via case studies, workshops, and discussions. There is plenty of time for Q&As, and with a maximum of 8 people per classroom session, all participants have the opportunity to learn first-hand from an industry expert.
A digital course companion is included, as well as time-saving templates on how to implement software for medical devices effectively and efficiently.
We recommend this course to those who are working with software development, such as R&D engineers, quality assurance department and auditors of software development.
Our blended learning courses combine the best of both worlds: online training and two half-day live virtual classroom sessions afterwards.
The online training allows for the flexibility in the way you learn, so that you can learn in a way which suits you best. You can access it whenever and wherever you want, and you can stop, start, and repeat the lessons and quizzes as often as you would like. To help maximise your learning, you can check your knowledge and understanding every step of the way by taking the assessment test beforehand, as well as the checkpoint quizzes that are found throughout the course. Ultimately, you will take a final exam at the end of the course.
The classroom sessions are highly interactive and focuses on applying the theory you have learnt during the online course with the guidance of the expert instructor. There are real life case scenarios to work through and plenty of time for discussions and questions.
Software development for medical devices can be made incredibly abstract if there is too much focus on the intangible requirements instead of how to actually do the work.
This course is very practical; you will be working on realistic tasks relating to the software lifecycle according to IEC 62304.
Gain exclusive up to the minute information by learning from authors of the standards.
Our courses are developed by members of the standardization committees involved at both national and international levels, ensuring you receive first-hand knowledge and insights.
Our instructors are passionate about what they do, bringing their expertise and love for the subject into the learning experience.
Participate in active learning by asking questions directly to the instructor, taking part in group workshops and discussions. This allows you to seek clarification, share insights, apply and transfer knowledge.
The online course comprises a mixture of pre-recorded videos, quizzes, and a final exam. It is self-paced and flexible in that you can start, stop, and repeat as much as you like. You will have lifetime access to the online course (conditions apply).
The Software for Medical Devices and IEC 62304 online course consists of 11 lessons which are outlined below.
You will attend these two half-day live virtual instructor-led classroom sessions via Zoom. The focus is on practicing the new skills, knowledge, and understanding learnt during the online course, in a relaxed environment, with the guidance of an expert instructor. There are real-life case scenarios to work through, and plenty of time for discussions and questions.
The live virtual classes will cover all aspects of the IEC 62304 standard and the relationship between the IEC 62304 and other standards such as the ISO 14971 standard.
The maximum number of people in a classroom session is 8. Please note, the classroom sessions will have participants from both this course and SaMD, IEC 62304 and IEC 82304-1 – Practitioner Training course.
Included is a digital course companion and the following time-saving templates:
The blended course consists of two parts: the online course, and two half-day live virtual classroom sessions.
The online course is made up of carefully scripted pre-recorded videos in order to maximise your learning. The live virtual classroom sessions are virtual face-to-face sessions where you will be interacting with the instructor and the other course participants via Zoom. You are required to be visible on video when taking the classroom sessions.
Yes, you can.
The time spent on the course varies greatly. If you are a beginner or have very high ambitions, you will typically spend more time on it. If you are already experienced in the field, you will probably finish it more quickly. The online course takes 9-25 hours to finish on average.
You do not have to watch the whole course at once. In fact, you can pause, resume, and replay as often as you like.
The two half-day live virtual classroom sessions take approximately 7 hours in total.
You will be receiving a course certificate after completing the final exam. The course certificate is available when you log in to your account. Go to “My Courses”, and scroll down. You will find it under “Your Course Certificates”.
After successfully completing the classroom session, you will receive a course certificate covering both the online course and the classroom session by email.
If you wish to buy 3 or more seats, we invite you to reach out using the contact form to discuss discount options. Please note, if there are more than 5 people from your organisation wising to take the course, consider arranging an in-house course. The price will be lower, and the course can be customised to your needs.
If you complete the final exam within 6 months of enrolment, you will have lifetime access to the online course (conditions apply). If you do not, your course access will expire after 6 months.
Yes, you can download a course companion within the online course. It contains a selection of key slides from the course and is in PDF format.
The maximum number of participants for the live virtual classroom session is 8.
There is no pass/fail score on the exam as such, but you are required to achieve 85% or more on the final exam to be allowed to attend the classroom session. The check-point quiz questions that are available during the online course will be a good model of what you will get on the final exam.
If you do not achieve 85%, the final exam can be reset for an administrative fee of 50 EUR, and you can take it again.
If you have already completed the online course and taken the final exam more than 3 weeks prior to the classroom sessions, and regardless of whether you have achieved >85%, we will reset the final exam for you for free.
You will need to retake the final exam by 3pm CET the day before the classroom sessions. This is because we insist all participants have the information fresh in their mind in order to maximise the learning experience in the live virtual classroom sessions.
The instructor is an expert member of the project team authoring IEC 62304 and also actively participated in the creation of IEC 82304-1.
He has extensive experience of medical device development and a strong dedication to software development. In the software domain he has worked in many roles such as software developer, project manager, auditing and quality management. This ensures the instructor has access to leading-edge knowledge and information, which is the highest qualification available for teaching the course.
We offer a number of payment methods including credit card, GooglePay, ApplePay, PayPal, wire transfer/invoice depending on the country you are buying from. If you cannot find your country on the list at checkout or you are not given wire transfer as a payment method, you can submit your order via our invoice order form.
Medical Device HQ is proud to be an accredited CPD provider, demonstrating our commitment to your continued professional development with high-quality training courses.
A CPD record showcases your professional growth, boosts confidence in your abilities, and can be presented to management for better career opportunities.
As a participant of a CPD certified course, you will receive a certificate awarding you CPD points following completion of the training.
Upon completion of this blended course, you are awarded 25 CPD points.
Your course certificate will display the exact number of CPD points. Read more.
IMPORTANT – The course will be associated with the account that the purchase is made from. Are you taking the course or is someone else?
Choose your course options below
IMPORTANT – The course will be associated with the account that the purchase is made from. Are you taking the course or is someone else?