Choose your access period

Both options include the full course: 45 video lessons, 11 exercises with worked solutions, templates and a certificate of completion. The course takes about 23 hours, so 90 days fits about 2 hours a week.

The scope

Check the scope before you choose a course.

Reviewers, auditors and regulators do not run your software. They read your records. The course teaches the whole chain those records come from, from the first risk file to the release decision. Device software and production and quality system software are taught side by side, with their different evidence, and the rest of the chain around them, in 13 chapters.

  • Regulated software and the status of rulesWhich software in a product is regulated, and how to tell law, guidance, standards and drafts apartCh 1
  • QMSR and ISO 13485Where software V&V sits in the QMSR, in effect since February 2, 2026Ch 2
  • Risk file to testsSoftware in the ISO 14971 risk file, and hazard-to-test traceabilityCh 2
  • IEC 62304 for testersSafety classes, unit, integration and system testing, SOUP, anomalies, release, and product validation beyond IEC 62304Ch 3
  • Test design and test recordsTechniques and coverage by risk, scripted and exploratory testing, records an auditor can follow, regression from change impactCh 4
  • FDA premarket documentationDocumentation level, testing and unresolved anomalies, OTS software, changes after clearanceCh 5
  • Automation, tools and pipelinesTool validation, release evidence from agile and CI pipelines, testing on the cloudCh 6
  • Cybersecurity testingThe final FDA cybersecurity guidance of February 2026, security test plans, penetration test review, patchesCh 7
  • Production and QMS softwareComputer software assurance (final FDA guidance, February 2026 edition), Part 11 records, AI tools in the QMSCh 8
  • AI-enabled device softwareTest data, performance by subgroup, changes under a PCCP, generative AI features. The FDA lifecycle guidance for AI-enabled device software functions is still a draft, and the course teaches it as oneCh 9
  • EU requirementsEU MDR software V&V, EU cybersecurity, and the AI Act testing duties with the dates they apply fromCh 10
  • Health software and health ITHealth software outside device rules, clinical safety in England, US health IT certificationCh 11
  • Great Britain and other marketsThe GB rules for software evidence, and software expectations in other marketsCh 12

Drafts are taught as drafts, never as requirements. The capstone in chapter 13 brings it all together in one release evidence package.

Regulations, standards and guidance

The regulations, standards and guidance in the lessons, with their status.

Every rule in the lessons is dated and labelled: law, final guidance, recognized standard or draft. Some standards are covered at scope and status level. You do not need your own copy of any standard: the lessons give what the exercises need in the course’s own words.

US law and FDA regulations

  • 21 CFR Part 820, Quality Management System Regulation (QMSR), in effect since February 2, 2026
  • 21 CFR Part 11, electronic records and electronic signatures
  • FD&C Act section 524B, cyber devices
  • FD&C Act section 515C, predetermined change control plans
  • FD&C Act section 520(o), software functions outside the device definition
And 2 more in US law and FDA regulationsShow fewer in US law and FDA regulations
  • 21 CFR Part 806, corrections and removals
  • 21 CFR 801.50, unique device identifier for stand-alone software

FDA guidance

  • Content of Premarket Submissions for Device Software Functions (2023)
  • General Principles of Software Validation (2002)
  • Computer Software Assurance for Production and Quality Management System Software (2026 edition)
  • Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (2026)
  • Deciding When to Submit a 510(k) for a Software Change to an Existing Device (2017)
And 7 more in FDA guidanceShow fewer in FDA guidance
  • Marketing Submission Recommendations for a Predetermined Change Control Plan for AI-Enabled Device Software Functions (2025)
  • Off-The-Shelf Software Use in Medical Devices (2023)
  • Postmarket Management of Cybersecurity in Medical Devices (2016)
  • Part 11, Electronic Records; Electronic Signatures: Scope and Application (2003)
  • Software function policies: Clinical Decision Support Software, Device Software Functions and Mobile Medical Applications, General Wellness, Medical Device Data Systems and Multiple Function Device Products
  • Interoperable medical devices (2017) and the use of consensus standards (2018, 2020)
  • Compliance Program 7382.850, QMSR inspections (from February 2, 2026)

International standards

  • IEC 62304:2006 with Amendment 1:2015, software life cycle processes
  • ISO 13485:2016, quality management systems
  • ISO 14971:2019, risk management, and ISO/TS 24971-2:2026 for machine learning
  • IEC 82304-1:2016, health software
  • IEC 81001-5-1:2021, security in the product life cycle
And 3 more in international standardsShow fewer in international standards
  • ISO/IEC/IEEE 29119 software testing series, and ISO/IEC TR 29119-11:2020 on testing AI-based systems
  • IEC TR 80002-1:2009 on software risk management, and ISO/TR 80002-2:2017 on validation of quality system software
  • IEC 60601-1 Edition 3.2, clause 14 on programmable electrical medical systems

AAMI, IMDRF and industry practice

  • AAMI TIR45:2023, agile practices
  • ISPE GAMP 5 Second Edition and the GAMP guides on testing and on AI
  • IMDRF documents on SaMD, cybersecurity, good machine learning practice and PCCPs
  • AAMI TIR57:2016/(R)2023, security risk management
  • AAMI TIR115:2026, public cloud computing for medical device functions
And 2 more in AAMI, IMDRF and industry practiceShow fewer in AAMI, IMDRF and industry practice
  • CVSS v4.0, the CISA Known Exploited Vulnerabilities catalog and OWASP LLM01:2025
  • ANSI/AAMI SW91:2018, defect classification

European Union

  • Medical Device Regulation (EU) 2017/745 and IVD Regulation (EU) 2017/746
  • MDCG guidance on software, cybersecurity, clinical evaluation of software and AI
  • EU AI Act, Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744
  • Cyber Resilience Act (EU) 2024/2847
  • Harmonised standards under the MDR, and Team-NB best practice guidance
  • European Health Data Space (EU) 2025/327 and Product Liability Directive (EU) 2024/2853

UK, US health IT and other markets

  • UK Medical Devices Regulations 2002, with the GB post-market surveillance rules (SI 2024/1368)
  • MHRA guidance on stand-alone software and apps, and the GB designated standards
  • NHS England DCB0129 and DCB0160 clinical safety standards, and DTAC
  • ONC Health IT Certification Program, the HTI-5 final rule and real world testing, with HL7 FHIR
  • Software requirements and guidance in Japan, Singapore, India and Brazil, and MDSAP
And 2 more in UK, US health IT and other marketsShow fewer in UK, US health IT and other markets
  • Health Canada guidance on machine learning-enabled medical devices
  • Australia: Therapeutic Goods (Medical Devices) Regulations 2002 and TGA software guidance

Watch items, taught with their status: IEC 62304 Edition 2, IEC 81001-5-1 Edition 2 and IEC 63450 (drafts); the FDA draft guidances on AI-enabled device software functions and on PCCPs for all devices; and the proposed revision of the MDR and IVDR.

Instructor-supported

Learn at your own pace. Never learn alone.

Expert instructor support is included with your Nopmark course. Get the flexibility of self-paced online learning with the personal guidance of an experienced industry professional.

  • Direct instructor access Email your questions about the lessons to your instructor. Your instructor responds within two business days.
  • Practical workplace guidance Get help to understand how the course concepts apply to the challenges at your own work.
Niranjan Maharajh
“Have a question about a lesson? Want to understand how to apply a technique in your own workplace? I’m here to help you succeed, not just finish the videos.”

Niranjan Maharajh, your instructor. Medical device software development and V&V experience. Teaches software validation for medical devices.

Your schedule. Your pace. Real expert support.

Instructor support is included during your course access period. Workplace guidance is educational and does not include consulting deliverables or formal document reviews.

The work you do

11 pieces of work you do yourself.

You do not only watch. In each exercise you fill in a course template with the facts of the case. Then you compare your work with a worked solution and its “Check your work” list. You keep all 13 templates.

From an FDA warning letter, October 2, 2025
“test plans do not include established acceptance criteria prior to testing”

The finding, at one firm, was about test plans created to validate device software designs. In the course, you set each pass/fail criterion before the run, and keep the raw data and the version that you tested.

  1. Hazard-to-test trace matrixBuild and review the trace matrix for a release, and find the gaps that a reviewer would raise.
  2. Software safety classificationClassify the software system and its items with IEC 62304.
  3. SOUP list reviewReview the SOUP list of the patch firmware.
  4. Risk-based test planWrite the core of the test plan for a release.
  5. Test record from execution logsWrite the test case first, then turn raw logs into a record that an auditor can follow.
  6. Regression analysisSelect the regression tests for a maintenance release.
  7. FDA documentation levelDecide Basic or Enhanced for 4 software products.
  8. Security test plan and penetration test reviewPlan the security testing and review a penetration test report.
  9. CSA recordMake the risk assessment and assurance record for a factory test station.
  10. AI test data and subgroup resultsReview the test data and results of a machine learning classifier.
  11. Release evidence packageThe capstone: review the evidence for a release before it ships.

Course curriculum

    1. Start Here: How this course works

    1. 1.1.1 Why medtech software testing is different

    2. 1.1.1 Checks: Why medtech software testing is different

    3. 1.1.2 Find the regulated software in a product

    4. 1.1.2 Checks: Find the regulated software in a product

    5. 1.2.1 Read the rules: law, guidance, standards and drafts

    6. 1.2.1 Checks: Read the rules: law, guidance, standards and drafts

    1. 2.1.1 Find software V&V in the QMSR and ISO 13485

    2. 2.1.1 Checks: Find software V&V in the QMSR and ISO 13485

    3. 2.2.1 Find software in the risk file

    4. 2.2.1 Checks: Find software in the risk file

    5. 2.2.2 Trace hazards to tests

    6. 2.2.2 Checks: Trace hazards to tests

    7. 2.2.2 Exercise: Trace hazards to tests for release 3.0

    8. 2.2.2 Worked solution: Trace hazards to tests for release 3.0

    1. 3.1.1 Classify software with IEC 62304

    2. 3.1.1 Checks: Classify software with IEC 62304

    3. 3.1.1 Exercise: Classify the RCM-4 software items

    4. 3.1.1 Worked solution: Classify the RCM-4 software items

    5. 3.1.2 Review requirements and architecture as a tester

    6. 3.1.2 Checks: Review requirements and architecture as a tester

    7. 3.2.1 Verify units and integration

    8. 3.2.1 Checks: Verify units and integration

    9. 3.2.2 Test the software system and release it

    10. 3.2.2 Checks: Test the software system and release it

    11. 3.3.1 Review SOUP and legacy software

    12. 3.3.1 Checks: Review SOUP and legacy software

    13. 3.3.1 Exercise: Review the patch firmware SOUP list

    14. 3.3.1 Worked solution: Review the patch firmware SOUP list

    15. 3.4.1 Handle anomalies, maintenance and configuration

    16. 3.4.1 Checks: Handle anomalies, maintenance and configuration

    17. 3.5.1 Validate the product beyond IEC 62304

    18. 3.5.1 Checks: Validate the product beyond IEC 62304

    1. 4.1.1 Plan risk-based testing for a release

    2. 4.1.1 Checks: Plan risk-based testing for a release

    3. 4.1.1 Exercise: Write the risk-based test plan for release 3.0

    4. 4.1.1 Worked solution: Write the risk-based test plan for release 3.0

    5. 4.1.2 Choose test techniques and coverage by risk

    6. 4.1.2 Checks: Choose test techniques and coverage by risk

    7. 4.2.1 Use scripted and exploratory testing for device software

    8. 4.2.1 Checks: Use scripted and exploratory testing for device software

    9. 4.2.2 Write test records an auditor can follow

    10. 4.2.2 Checks: Write test records an auditor can follow

    11. 4.2.2 Exercise: Write the test record from the release 3.0 execution logs

    12. 4.2.2 Worked solution: Write the test record from the release 3.0 execution logs

    13. 4.3.1 Select regression tests from a change impact analysis

    14. 4.3.1 Checks: Select regression tests from a change impact analysis

    15. 4.3.1 Exercise: Select the regression tests for release 3.0.1

    16. 4.3.1 Worked solution: Select the regression tests for release 3.0.1

    1. 5.1.1 Decide the FDA documentation level

    2. 5.1.1 Checks: Decide the FDA documentation level

    3. 5.1.1 Exercise: Decide the documentation level for 4 software products

    4. 5.1.1 Worked solution: Decide the documentation level for 4 software products

    5. 5.1.2 Present software testing and unresolved anomalies to FDA

    6. 5.1.2 Checks: Present software testing and unresolved anomalies to FDA

    7. 5.2.1 Document OTS software for FDA

    8. 5.2.1 Checks: Document OTS software for FDA

    9. 5.2.2 Assess a software change after clearance

    10. 5.2.2 Checks: Assess a software change after clearance

About this course

  • $400.00
  • 114 lessons
  • 11.5 hours of video content

Discover your Take your next step towards mastering Medical Device and MedTech Software Validation and Testing, starting today