SaMD, IEC 62304 and IEC 82304-1
- Online course
- EU and US requirements
- Beginner - intermediate
- Last updated - Aug 2026
Learn how to create and manage high quality, safe Software as a Medical Device (SaMD) during this self-paced, interactive online course.
Hello, software friends. I assume you landed on this video because you are interested in software as a medical device, also known as SaMD. In this short course, I want to share my thoughts what to get right when working with software-only products. And at the end of this video, I will also share tips about software risk management, which is painful if you don't get it right. I am Christian Kaestner, and I started my career as embedded software engineer in the early 90s. After a couple of years, I moved into the medical device field, where I have developed sterilisation equipment, transplantation devices, wound care therapy, and much more. Several years ago, I joined the project teams authoring IEC 62304 and IEC 82304-1, and I also work as a lead auditor. This short course applies to you if you are developing software as a medical device. For example, an app, a cloud service, or a regular desktop application. I will be showing you some key concepts in the medical device software area to help you understand it and avoiding mistakes. To get things right, I first want you to know the difference between a software release and a product release. Then I want you to know about the necessary standards that are needed for a smooth approval process. But standards are not too exciting, so I also want to share a few practical tips on how to conform to the standards. And I've saved the best for the last: software risk management. Now, let's get to it. I often hear people say that working with software as a medical device is different from working with other medical devices. In my opinion, on product level, there are no differences because you must work with planning, requirements, risk management, verification, and validation, regardless of what type of medical device product you develop. But, to be fair, there are some differences when it comes to the development of software. Let me share what I believe are the two main differences. The first and the most obvious reason is software bugs. A software product comes with all bugs enabled, but you don't know when they will pop up. If you have a car, you can take it to a garage and ask them to check your brakes or oil level. But for software, there is no such option. One infamous example of software bug is a Windows blue screen. It is very unexpected when it happens, and you lose all your unsaved work. When working with medical devices, the same blue screen can mean the loss of a patient's life. Clearly, this makes people nervous because there's no way to confidently claim 100% test coverage when working with software. This brings me to the second topic, which is about how products are created. The vast majority of software issues or bugs are traceable back to errors made during the design and development process. And this is logical because there is no manufacturing process when working with software products. For tangible products, designing the manufacturing process is a significant part of your development work. In the manufacturing process, you can implement checkpoints like in-process controls and apply statistical process controls. When working with software products, process control is not an option because there is no manufacturing process. You simply have to trust that the development was done correctly, and all quality controls must be part of your development work. And again, sorry to say, or sorry for repeating myself, there is no final production test where you can implement inspections to capture product failures. The closest thing in software would perhaps be the software release note, which is not at all the same thing. Speaking of software release takes me to software release versus product release. In modern software development, it is common to find continuous integration and continuous deployment. Continuous delivery is a software development methodology where the release process is automated. Every software change is automatically built, tested, and can be deployed to production at any time. This is cool, but before you get too excited, this is usually a software release and not a product release. Now you might think, when talking about software as a medical device, there are no other components than the software system. Perhaps not components, but in an audit situation, I would expect to find accompanying documents, such as the instruction for use and evidence of a successful design validation in your product release. It may be a simplification, but you could say that a software as a medical device product is the combination of software and its relevant documentation. And product documentation is usually overlooked in a software release. As you can see, a complete medical device release flow spans many more activities than the software release you find on the left-hand side. Just to mention a few, there are requirements for design validation and accompanying documents, such as the instruction for use. These activities will result in what I call a design release. You may be using another term. Once the design release is done, you may need to wait for regulatory approval before product release and placing the product on the market. After initial product release, you can usually manage non-significant changes without new third-party regulatory approval. However, please ensure you maintain relevant regulatory documentation. For example, keep the MDR general safety and performance checklist and technical documentation up to date. When working with standalone software, you can merge software release and design release into a single activity. For example, by including technical documentation and instruction for use as configuration items in your development work. This is a lean approach and makes sense in most cases. Still, I want you to be careful about placing a software on the market without considering all the activities and deliverables needed for a product release. Now you know the difference between a software release, design release, and a product release. Next up is the essential standards applicable to software as a medical device. Standards aren't the most exciting part of software development, but the idea with standards is to establish a common way of thinking which can be recognised by various stakeholders, such as regulatory authorities. So, by conforming to standards, you help reviewers and auditors to understand your development process and the resulting output. If you do this right, your chances of a smooth approval process increases significantly. When working with a software as a medical device, there are six essential standards you should be aware of and preferably also understand and implement. At the bottom, you will find something often referred to as management standards. They're usually the core in any quality management system. ISO 13485 contains requirements on your quality management system. That is, how you're supposed to work in general. This includes, for example, requirements on design and development, and that you have to establish design and development inputs. But ISO 13485 also contains requirements that are not related to design and development. For example, how to structure your quality management system and how to manage documents in general. Getting back to the design and development inputs. They are inputs to your software requirements and software development process. In IEC 62304, the design and development inputs, as they are called in ISO 13485, are referred to as system requirements. When working with standalone software, too many layers of a requirement might just complicate things. If so, feel free to merge requirements into fewer or even a single document. Just remember to include the requirements for all applicable standards. ISO 14971 contains requirements on your risk management process. That is, how you should be performing risk management. The risk management process provides one of the most important inputs to a software development process, and that is hazardous situations. A good understanding of hazardous situations is key to performing meaningful software risk management and getting it right. And as it so happens, you can find courses on both ISO 13485 and ISO 14971 on Medical Device HQ. IEC 62304 is the leading process standard you need to understand for software development. Luckily for you, we will be sure to take a closer look at IEC 62304. If you have a user interface of any kind in your software, you will also bump into IEC 62366-1, which is about usability engineering. The usability engineering process can contribute to both functional requirements and user interface related risks, which you need to consider in your development work. Please note, though, the definition of user interface in the usability engineering standard is broad. It is not only the user interface you see in the software. So, be aware, even if your software is intended to run as a technical background service without any traditional user interface, the usability standard might still be applicable. For example, when working with instruction for use and installation instructions that are connected to how to use the software product. The last process standard I want you to be aware of is IEC 81001-5-1, which is about security. It might not be applicable to all SaMD products, but if you are working with standalone software, there is a high likelihood that security is something you should keep a close eye on. The next and the last standard to be covered in this overview is IEC 82304-1. It is a product standard for standalone software, such as apps, PC program, and cloud services that are supposed to run on generic hardware platforms. So, when working with standalone software, this standard applies to you and your product. IEC 82304 is a product standard for health software. The standard defines requirements for establishing high-level product requirements for your software product. You also find requirements on design validation and accompanying documents. But, in all honesty, IEC 82304-1 essentially duplicates the requirements you find on design inputs and design validation in ISO 13485. Therefore, when working with a software as a medical device, my recommendation is to adapt your existing quality management procedure to embrace the additions you find in IEC 82304-1 instead of establishing a standalone procedure for IEC 82304-1. But in one aspect, IEC 82304-1 is much more specific than what you find in ISO 13485, which is requirements about accompanying documents. As a product standard, it defines the detailed requirements on what to include in the instruction for use and a technical description of your software. For example, the following activities are expected to be described in instructions for use: installation, startup, shutdown, operating, and decommissioning. Now, let's have a closer look at IEC 62304, which is a process standard, meaning you will not find details like performance or screen resolution requirement or what to include in instructions for use. What you will find is a list of requirements and activities you should carry out throughout your development cycle. If you are a software developer, this standard will influence your work the most. This is because the standard defines requirements you must relate to in your daily work. Many SaMD developers are working Agile nowadays, and unfortunately, the standard is very sequential, which implies a waterfall-ish development method. However, the standard has no requirement forcing you to apply a specific development method. You're 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 standard's essential elements: development, risk management, configuration management, problem resolution, and maintenance. Each process is 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 industry or mobile phone industry, you would find that the ways of working are similar but use different names. There's one difference though. In the medical device industry, we are obsessed with safety. Because in the medical device industry, a software bug is not only a blue screen, it can literally be a blue screen of death. 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. The flow through the standard is the same, but the rigour is different depending on your classification, which is further explained in the standard. This graphical overview visualises the scope of IEC 62304. Blue boxes are in scope, grey are out of scope. The arrows between blue and grey is where there is an information exchange. And as you learned before, IEC 62304 gets its input from IEC 82304-1 and ISO 13485. 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 a screen or alarm management. It can also be hardware constraints, even for standalone software. For example, do you have one or more CPUs available, or should communications happen over USB or Ethernet? In the standard, there is a clause about software requirement content, but nothing about how you document your requirements. You can capture requirements in any way you want. It can be tickets, stories, wiki pages, or advanced requirement management tools. It is 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, which I would call a baseline. This is particularly important when working with Agile methods. You should be able to identify the complete set of requirements applicable to a specific version, even if you work in sprints. Requirements shall also be reviewed and improved. Please make sure your setup can support you in this work. Traceability is also required by the standard. Ideally, your choice of requirement management also supports you with traceability from requirement to verification. In addition to when software releases are expected, you also need to plan for content, purpose, and how to deliver each software release. The expectations are most likely different if you're releasing for a demonstration, usability test, or aim for a design release. Here we are back to our obsession with safety. To develop a safe software, we need input about hazardous situations to understand what we must avoid. This input often includes risk-related requirements, for example, a clear warning when a diagnosis can't be decided. The go-to standard for risk management is ISO 14971. Your risk management process should provide you with all information necessary to effectively implement software risk management. The bulk of your development work will be in the highlighted section, where you can see the various development activities that will take place and 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. One way to do this is by working with Agile methods. Agile development methods embrace changes and allow a product to evolve over time. Let's look at an example with the help of Scrum. You might feel there is a mismatch between the waterfall approach in the standard compared to working with Agile methods. But there is no need to be worried. Working with backlog stories and sprint planning can be compared with when eating an elephant, take one bite at a time. Let's 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 wording might differ, but you certainly don't want contradictions and ambiguity in your stories. If I simplify things, you verify software 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 to have nearly a full set of requirements and then go for a review. In this later 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 principles and meet the standard requirements. It is only a question of how you have chosen to meet the requirements. In case you're into Agile development, there is an excellent technical report from AAMI, TIR45, which is a guidance on the use of Agile principle. Enjoy your reading. There's much more to talk about when it comes to theory and standards. But for now, I will continue with other topics which I believe you have more practical use of. Let's kick off with planning. I'm not a planning guy, but I've learned to accept the importance of proper planning. When working with software as a medical device, you will spend most of your time in software development, which should be planned following the requirements of IEC 62304. The standard requires you to plan configuration management, software risk management, and much more. You can choose to split these into different plans, but 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 your project team. For example, if you have a separate test team, then it could make sense to have a dedicated verification plan. The software development plan is a perfect place to explain how the team is structured and how you interact with your quality management system. Let's take a look at an example of what interacting with 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. I would say in the source code. There is 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 file 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 document, but you need to identify where it can be found and how you control it. In this example, I've used Doxygen format for the comments. In case you really must, you can also easily extract the comments to traditional document formats. When you later maintain the code, the documentation is available, which supports the developer the most, and it's also much easier to maintain. If you take this one step further, technical documentation can be an integral part of your build process by creating a build pipeline for documentation running in parallel with your software build. This would ensure that documentation always being in sync with the software. Let's talk about configuration management. I would say that a software product usually has more configuration items to control than all documents together in a complete 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 difficult if you compare with documents which typically are released with the help of signatures in a much lower pace. Maybe ask yourself, what is a configuration item? A 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 quickly 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 the practical aspects of 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 procedure 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 good practice is that you are 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. And while you're at it, also take the opportunity to review relevant documentation. 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 documented, but not as traditional documents. If you haven't done it yet, spend some time in looking for good configuration management tool that can satisfy your needs. And please, make sure you validate the system setup and use it as much as you can. I assume you have some basic understanding of risk management. If you don't, I recommend you watch the videos about risk management at Medical Device HQ. One of the most misunderstood statements in this field is that the probability of occurrence of harm should be set to 100% just because you're working with software. I can tell you that statement is wrong. The 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 the probability of occurrence of harm and claim it shall be 100%, they refer to P1. But also this assumption can be challenged. Let's look at an example where a software is used to recommend the proper 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 the wrong medication. What is the Po for this risk? The correct 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 result in choosing drug A. For the sake of safety, we could assume that drug A will always 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 the software failure always will happen, but I 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 occurring is 20%. It is quite a difference. To summarise, if you are working a lot with software, please do yourself a favour and start using P1 and P2. If you stay with Po only, you will be in a challenging situation. I will, of course, go into more depth on this topic in the full course, and also explain how to 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 as a medical device, IEC 62304, and IEC 82304-1, I welcome you to sign up for the full online course Introduction to SaMD, IEC 62304 and IEC 82304-1. 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, usability engineering, design control, quality management, and clinical investigation for medical devices. Drop us a line on 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 device development in general. I hope to hear from you.
| Course length | approx. 10-29 hours (21 CPD points) |
Do you want this course on your internal LMS? Contact us
Unsure whether this course or the Software for Medical Devices and IEC 62304 online course is right for you?
Click here for a course comparison.
Select your course plan
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
YOU ARE HERE
€ 499
Average completion time 10-29 hours
Total video duration 7.5 hours
CPD points 21
Number of quizzes 37
Final exam
Course certificate
Ask the instructor
6 months access to the course and instructor
ONLINE LIFETIME
€ 599
Average completion time 10-29 hours
Total video duration 7.5 hours
CPD points 21
Number of quizzes 37
Final exam
Course certificate
Ask the instructor
Lifetime access to the course and instructor
BLENDED
€ 1149
Average completion time 17-36 hours
Total video duration 7.5 hours
CPD points 28
Number of quizzes 37
Final exam
Course certificate
Ask the instructor
Lifetime access to the course and instructor
Printed course companion
Classroom sessions (2 * 3.5 hours)
Templates
IN-HOUSE TRAINING
CONTACT US
Tailored training to meet your company's needs
Course overview
This online course is an adaptation of our existing popular course Software for Medical Devices and IEC 62304 with a special focus on developing Software as a Medical Device (SaMD).
SaMD specific topics include software types and terminology, product requirements in IEC 82304-1, introduction to cybersecurity and artificial intelligence.
The course looks at the development aspects of the IEC 62304 standard. It also includes an introduction to the IEC 82304-1 standard and its relation to ISO 13485 (quality management). In the course, you will also learn about the relationship to ISO 14971 (risk management) when developing medical device software.
The course is suitable for anyone working with SaMD development, such as R&D engineers, quality assurance department and auditors of SaMD. The course does not cover actual coding.
It is made up of pre-recorded videos, quizzes, and a final exam. There is also a downloadable course companion within the course. You will receive a course certificate upon successful completion of the course.
If you purchase the ‘Online’ course plan you will have access to the course for 6 months from enrolment. If you purchase the ‘Online lifetime’ course plan you will have lifetime access (conditions apply).
Benefits for you
Direct access to standards authors
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.
You can ask our instructors questions during the online course thereby gaining exclusive up-to-the-minute information.
Training effectiveness and record-keeping
Participants’ knowledge is assessed through pre-training quizzes and a final exam, enabling a true measure of the training’s effectiveness.
Furthermore, we provide records, including the final exam score and course certificate, to satisfy ISO 13485 requirements, ensuring compliance and accountability.
Self-paced and bite-sized learning
Our interactive online courses offer the flexibility to learn at your own pace. The high-quality videos are designed in bite-sized segments, making it easier to grasp and retain information.
This format provides a convenient alternative to traditional classroom courses accommodating different learning styles and preferences.
Course modules
- Welcome
- What you need to know
- Set your course goal completion date
- Pre-course assessment quiz
- What is software and what makes it different
- Software types and terminology
- Introduction to the regulatory landscape
- Introduction to classification of medical devices and software
- Introduction to risk
- SaMD relevant standards
- The relationship between IEC 82304-1 and ISO 13485
- Product requirement in IEC 82304-1
- Scope and general terminology- Part 1
- Scope and general terminology- Part 2
- General requirements (IEC 62304)
- Development process and compliance
- Software safety classification – Part 1
- Software safety classification – Part 2
- Software safety classification – Part 3
- Understanding software risk management
- Cybersecurity
- Development process as risk control – Part 1
- Development process as risk control – Part 2
- Software risk management in IEC 62304 – Part 1
- Software risk management in IEC 62304 – Part 2
- Software causes
- Software risk control measures
- Development planning – Part 1
- Development planning – Part 2
- Development planning – Part 3
- Configuration management
- SOUPs, how to management and document – Part 1
- SOUPs, how to management and document – Part 2
- Software requirements – Part 1
- Software requirements – Part 2
- Software architecture – Part 1
- Software architecture – Part 2
- Software architecture and cloud services
- Quality control of cloud services
- Software detailed design
- Software design – AI/ML – Part 1
- Software design – AI/ML – Part 2
- Software unit implementation
- Software integration testing
- Software system testing
- Software release per IEC 62304
- SaMD product release per IEC 82304-1/ ISO 13485
- Maintenance plan
- Problem resolution – the process
- Change control
- Wrap up
- Final exam
- Course evaluation
- Learn more in a live virtual class
- The virtual class product
- Get your questions answered in the live virtual class
NOTE – The course program structure is subject to change
Do you want this course on your internal LMS? Contact us
Frequently asked questions
The course is not a webinar. This online course is made up of carefully scripted pre-recorded videos to maximize your learning. You can watch it as many times as you like, whenever and wherever you want. You can not download the course though, thus you will need to have an internet connection to take the course.
All in all, the average time to complete the course is 10-29 hours, but you can complete it in less time if you don’t repeat any of the lessons and have just one attempt at the quizzes. Please note, you don’t have to watch the whole course at once. In fact you can pause, resume and replay as often as you like. The only limitation is the final exam, where you will only have one shot.
If you purchase the ‘Online’ course plan you will have access to the course for 6 months from enrolment. If you purchase the ‘Online lifetime’ course plan you will have lifetime access to the course if you complete the final exam within 6 months of enrolment (conditions apply).
You need to have contact with our servers for your results to register on the final exam. If your computer for some reason has a problem and does not allow you to send the result of the final exam to our servers, we recommend that you take a photo or a “print screen” of the screen with your results. E-mail this image to us and we will investigate if you have successfully completed the exam and therefore should receive a course certificate even though the result has not been registered, or if you have to do the final exam again.
There is no pass/fail on the final exam (as long as you complete it within the time frame). Your result will be printed on the course certificate which means you can be really proud of your result if you get between 90% and 100% of the answers correct!
The course certificate is available for download after completing the final exam. All you need to do is log in to your account, go to My Courses and scroll down. You will find it under Your Course Certificates.
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.
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.
If you purchase five seats for the same online course at the same time, we will give you one extra seat for free on that same course (e.g. buy 5 get 6, buy 10 get 12, etc). The free seat is assigned manually after the order has been received.
The instructor continuously participates in authoring the IEC 62304 and IEC 82304-1 standards. This ensures the instructor has access to first hand information and understanding of the meaning of the standard’s requirements. This is the highest qualification available for teaching the course.
There are no pre-requisites for this course but basic understanding of risk management is recommended.
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 the course, you are awarded 21 CPD points for the online course and 28 CPD points for the blended course.
Your course certificate will display the exact number of CPD points. Read more.
Reviews
Medical Devices
InViva Healthcare Management
Director
Vision RT
Lemberg Solutions
Haermonics B.V.
Insparya Hair Company
NSAI
Phillips Medisize
and Software Development
MagForce, The Nanomedicine Company
Annalise.ai
He is currently involved in the authoring of the updated IEC 62304 as part of TC 62/SC 62A, and serves as convener of TC 62/ahG9, a group tasked with finding consensus regarding the understanding of AI-related terms and concepts (e.g., ISO/IEC 22989-2) in IEC TC 62.
He has extensive experience of medical device development and, as a software developer, 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.
Group purchase
If you wish to purchase two or more seats on the same online course, click the ‘Buy multiple seats’ button below which will take you to the product page where you can simply enter the number of seats you require.
If you purchase three seats or more on the same online course at the same time, you will be added to the Professional Plan for free. This means a group account will be created for you that you can manage. You will be able to track the participant’s course progress from your group account and view quiz results.
It is the person that places the order who will be our single-point-of-contact and group leader for the group account. If you wish to change this to someone else later on, you can email us at support@medicaldevicehq.com.