SaMD Training for Medical Device Software Teams: What to Learn and Why Now
What good Software as a Medical Device training covers: qualification, IEC 62304, cybersecurity and AI/PCCP lifecycle, and why US demand for it is rising.
Software as a Medical Device (SaMD) is one of the fastest-growing corners of the industry, and it is pulling regulatory, quality and software teams into territory their original training never covered. This guide sets out what dedicated SaMD training should include, who needs it, and why demand for it is climbing in the US market right now.
Who needs SaMD training
- Regulatory affairs specialists moving from hardware devices onto software or AI-enabled products.
- Software and quality engineers who need to understand regulatory expectations, not just write compliant code.
- Product managers and founders at digital health and AI-enabled device start-ups preparing a first FDA submission.
- Anyone unsure whether their product even qualifies as a device. Start with is my software a medical device?
Why demand is rising in the US
Three things are converging. First, FDA continues to clear a growing share of AI- and software-enabled devices every year, and employers are paying a premium for regulatory staff who understand machine learning lifecycle concepts. Second, the predetermined change control plan (PCCP) pathway lets manufacturers plan for post-market model updates in the original submission, which is a new skill most regulatory teams were never trained on. Third, the FDA’s QMSR, in force since February 2, 2026, folds software validation and risk management more tightly into the quality system, so software teams can no longer treat compliance as someone else’s job. See AI-enabled devices and FDA PCCP for where the guidance stands today.
What good SaMD training covers
1. Qualification and classification
Whether software meets the device definition, how intended use and risk to the patient drive classification, and how this differs from traditional hardware classification logic.
2. IEC 62304 software lifecycle
Software safety classes A, B and C, software development and maintenance processes, and how SOUP (software of unknown provenance) is handled and documented.
3. Computer software validation and assurance
How CSV differs from CSA, and when a risk-based assurance approach is appropriate for quality system software. See CSV and CSA for medical devices.
4. Cybersecurity
Threat modelling, a secure product development framework, and the documentation FDA expects in a submission.
5. AI/ML lifecycle and PCCP
Locked versus adaptive algorithms, what a predetermined change control plan contains, and how to plan post-market monitoring for model drift.
6. Submission strategy
How 510(k), De Novo and PMA pathways apply to software, and what reviewers look for in a software submission package.
How to choose a programme
- Does it go beyond definitions and include worked examples from real submissions and audit findings?
- Is it current on PCCP and AI lifecycle guidance, which is still evolving?
- Does it cover both the regulatory side and the IEC 62304 engineering side, rather than just one?
- Is there a practice element: a mock classification exercise, a SOUP assessment or a submission outline?
Where AptSkill can help
Our SaMD Training course and SaMD Masterclass cover qualification, IEC 62304, cybersecurity and submission strategy, with a regulatory strategy deep dive for teams that need more than an overview. If you are preparing for a software-focused interview, see SaMD and software quality interview questions.
Frequently asked questions
Is SaMD training only for software engineers?
No. Regulatory, quality and clinical staff who work with software products benefit just as much, since most of the content is about classification, documentation and risk rather than coding.
How is SaMD training different from general FDA regulatory training?
It focuses on software-specific concepts such as IEC 62304 safety classes, SOUP, cybersecurity and AI lifecycle management, which general regulatory courses usually only mention briefly.
Do I need a coding background to take SaMD training?
No. Courses aimed at regulatory and quality professionals explain the engineering concepts you need without assuming you can write software yourself.
Talk to the AptSkill team
Tell us your background and what you are trying to prepare for, and we will point you to the right SaMD course or resources.
Ask about SaMD training
Ready to take the next step?
Questions? Email aptskill6@gmail.com and the AptSkill team will respond promptly.