Global Medical Device Podcast powered by Greenlight Guru cover art

Global Medical Device Podcast powered by Greenlight Guru

Global Medical Device Podcast powered by Greenlight Guru

By: Greenlight Guru + Medical Device Entrepreneurs
Listen for free

The Global Medical Device Podcast, powered by Greenlight Guru, is where today's brightest minds in the medical device industry go to get their most useful and actionable insider knowledge, direct from some of the world's leading medical device experts and companies.Greenlight Guru Economics Hygiene & Healthy Living Physical Illness & Disease
Episodes
  • #460: FDA AI Regulations: Master the QA/RA Skills to Stay Ahead

    #460: FDA AI Regulations: Master the QA/RA Skills to Stay Ahead
    May 18 2026
    The FDA is actively shaping the regulatory landscape for Artificial Intelligence (AI) and Machine Learning (ML) in real time. As the agency expands its internal expertise through the Digital Health Center of Excellence, FDA reviewers are becoming highly sophisticated. The era of submitting vague algorithm descriptions is over, paving the way for a more level playing field that rewards companies executing documentation correctly.Navigating this evolving space requires a dual-front approach for global medical device companies. Manufacturers must balance the FDA's framework with the EU AI Act, which classifies AI medical devices as high-risk systems demanding rigorous conformity assessments and human oversight. Fortunately, a robust quality management system designed around proactive frameworks, such as the Predetermined Change Control Plan (PCCP), can bridge the gap between US and international expectations.For Quality Assurance and Regulatory Affairs (QA/RA) professionals, this shift represents an unprecedented career opportunity. The future belongs to those who combine regulatory fluency with AI literacy. Success in the MedTech industry will not belong solely to the most complex algorithm, but to the companies and professionals who build compliant, disciplined systems around their AI technologies.Key Timestamps00:19 – Introduction to the current state of FDA AI regulation and leadership transitions.01:34 – The role of the FDA Digital Health Center of Excellence and shifting reviewer expectations.02:08 – Navigating global regulations: Balancing the EU AI Act and EU MDR.02:46 – The 5 guiding principles for AI/ML-based Software as a Medical Device (SaMD).03:41 – Analyzing FDA warning letters: Why documentation takes precedence over algorithm performance.04:19 – Bridging the language barrier between AI engineers and FDA reviewers in submissions.05:27 – The future of QA/RA careers: The rising demand for AI-literate regulatory professionals.06:21 – Actionable strategies to stay ahead: Implementing PCCPs early and training quality teams.07:23 – Treating post-market surveillance for AI products as an evolving product lifecycle.Quotes"The companies getting in trouble aren't the ones with bad AI, they're the ones with incomplete quality systems." - Etienne Nichols"Your job in a regulatory submission is not to demonstrate that your AI is sophisticated. Your job is to demonstrate that it's safe and effective in its intended use." - Etienne NicholsTakeawaysBuild Your PCCP First: Develop your Predetermined Change Control Plan (PCCP) concurrently with or prior to algorithm development to ensure post-clearance modifications match your design process.Close the Team Knowledge Gap: Educate quality engineering teams on fundamental AI concepts like training data, validation datasets, and demographic representation before facing regulatory audits.Proactively Audit Your DHF: Review your existing Design History File (DHF) against current FDA AI guidance documents well ahead of submission deadlines to eliminate documentation gaps without timeline pressure.Evolve Post-Market Surveillance: Treat your AI post-market surveillance plan as a living product by implementing version control, clear ownership, and defined thresholds to detect algorithm drift.Achieve Dual Literacy for Career Growth: QA/RA professionals who master both regulatory frameworks and basic AI literacy will position themselves at the top of an uncrowded talent pool.ReferencesFDA, Health Canada, & UK MHRA Joint Statement (2022): The five joint guiding principles established for machine learning medical device development.FDA AI/ML Action Plan (2021) & PCCP Guidance (2023): Core foundational reading material for understanding regulatory expectations.International Medical Device Regulators Forum (IMDRF) Guidance: Global harmonized guidelines concerning AI/ML-based SaMD.EU AI Act: High-risk classification rules and conformity requirements affecting medical software in Europe.Connect with the Host: Follow Etienne Nichols on LinkedIn for more MedTech insights and discussion.MedTech 101 SectionOverfittingThink of overfitting like a student who memorizes the exact questions and answers on a practice exam instead of learning the underlying concepts. When they take the real test with slightly altered questions, they fail. In AI, overfitting happens when an algorithm learns the training data too perfectly, making it excellent at analyzing that specific dataset but unable to make accurate predictions on new patient data.Algorithm DriftImagine a GPS map app that was programmed perfectly five years ago. Over time, new roads are built, traffic patterns change, and old exits close. If the app is never updated, its navigation becomes less accurate. Algorithm drift occurs when an AI medical device becomes less effective over time because the real-world clinical environment or patient demographics shift away from the original data it was trained on.SponsorsThis ...
    Show More Show Less
    15 mins
  • #459: The Purolea Warning Letter & Validating AI in Medical Devices - What FDA Actually Requires

    #459: The Purolea Warning Letter & Validating AI in Medical Devices - What FDA Actually Requires
    May 11 2026
    The MedTech industry widely misread the FDA's recent warning letter to Purolea Cosmetics Lab as a direct crackdown on Artificial Intelligence (AI). Host Etienne Nichols challenges this narrative, explaining that viewing the event strictly through an AI lens causes medical device manufacturers to miss the actual compliance lesson. At its core, the Purolea situation is not a story of bad software, but rather a fundamental failure of process validation and quality system oversight.When stripped of its technical novelty, the regulatory citation reveals an inspector's nightmare: lack of microbiological testing, absent process validation, and a non-functional quality unit. The AI components were merely downstream symptoms of a quality vacuum. Purolea utilized AI agents to draft critical product specifications and master production records, blindly trusting the software without human oversight. When confronted, the company claimed the AI agent simply never informed them that process validation was a legal requirement.For medical device companies shifting from pharmaceutical regulations to the Quality Management System Regulation (QMSR), this episode serves as an urgent reminder of human accountability. The FDA did not write new regulations for this case; they applied foundational principles of human ownership to automated outputs. Whether content is drafted by a junior intern or a Large Language Model (LLM), a qualified human must own, review, and validate the output against defined specifications within a controlled, compliant architecture.Key Timestamps00:15 - The Purolea Cosmetics Lab warning letter and the media's misinterpretation of an FDA AI crackdown.01:04 - The reality of the Purolea inspection: Pests, missing microbiological tests, and total quality vacuum.01:42 - How Purolea used AI agents to draft production records and why blaming the algorithm failed.02:18 - 21 CFR Part 211.22 and its medical device parallel (QMSR 820.20): Defining the Quality Control unit’s ultimate accountability.03:11 - Treating AI as an internal consultant: The balance of sensitivity and specificity in automated tools.04:00 - Can you validate an AI algorithm vs. inspecting outputs? Deterministic software vs. Machine Learning.05:25 - The 3-Part Validation Data Framework: Training data, validation data (development set), and the holdout test data.06:21 - When human-in-the-loop output verification works, and when 100% automated inspection fails.07:22 - Deep dive into Computer Software Assurance (CSA) guidance and risk-proportionate validation rigor.08:16 - Essential regulatory standards and guidance documents list for MedTech AI developers.09:25 - The 2010s Paper vs. eQMS debate compared to modern unstructured AI chat windows.10:35 - Five concrete questions to assess if your quality system is ready for an FDA AI inspection.Quotes"If you use AI as an aid in document creation, you must review the AI generated documents to ensure that they were accurate and actually compliant... The person who signed off on them is responsible. This is nothing new." - Etienne Nichols"A perfectly engineered AI agent drafting into a quality vacuum is going to produce the same results as a sloppy one." - Etienne NicholsTakeawaysHuman-in-the-Loop Ownership: Automated tools must be treated like junior interns or external consultants. Every document, specification, or SOP drafted by an LLM requires rigorous, qualified human review and physical signature sign-off before entering a controlled QMS.Strict Split for ML Data Sets: For true machine learning algorithmic validation, companies must strictly partition data into Training, Validation, and Holdout Test data. Merging or leaking data between validation and training sets entirely compromises the regulatory integrity of the submission.Validation Rigor Must Match Risk Profile: Under Computer Software Assurance (CSA) principles and ISO 14971, validation intensity must be proportionate to risk. Low-risk form-populators do not require the same exhaustive testing protocols as automated diagnostic algorithms driving real-time clinical decisions.Chat History is Not an Audit Trail: Pasting AI outputs from an uncontrolled chat window into unmanaged text editors violates electronic record standards. AI-assisted documentation must reside within an infrastructure that maintains version control and clear change histories.ReferencesFDA Guidance (2002): General Principles of Software Validation — The bedrock document for baseline software expectations in medical tech.FDA Guidance Update: Computer Software Assurance (CSA) for Production and Quality System Software — The framework shifting focus from excessive paperwork to risk-based testing assurance.International Standard ISO 13485: Medical devices — Quality management systems — The global standard now tied directly into US compliance via the QMSR transition.International Standard ISO 14971: Medical devices — Application of risk management to medical ...
    Show More Show Less
    24 mins
  • #458: What the FDA Actually Says About AI in Medical Devices

    #458: What the FDA Actually Says About AI in Medical Devices
    May 4 2026
    The medical device industry is undergoing a paradigm shift as Artificial Intelligence (AI) and Machine Learning (ML) transition from novelties into heavily regulated realities. The turning point arrived when the FDA integrated its own internal AI tool, Elsa, into its scientific review and inspection targeting processes. With regulators actively leveraging the technology, MedTech companies can no longer treat AI as a buzzword; it demands a deep understanding of concrete regulatory frameworks and actual engineering rules.To properly understand this evolution, the traditional internet analogy must be cast aside in favor of a more accurate comparison: electricity. Just as the adoption of electricity brought a wave of safety infrastructure, inspectors, and the National Electrical Code, AI is bringing an imminent mountain of new standards to the medical device landscape. Winning device companies will not be those that market themselves as "AI companies," but rather those whose devices simply perform better because of the technology and whose quality systems can explicitly prove that enhanced performance to regulators.Navigating this terrain requires mastering fundamental regulatory concepts, beginning with Software as a Medical Device (SaMD) pathways and the distinction between locked and adaptive algorithms. Because adaptive algorithms continuously change in the field, they present a unique regulatory challenge that requires a total product lifecycle approach. By utilizing a Predetermined Change Control Plan (PCCP) and integrating proactive post-market surveillance directly into the Quality Management System (QMS), manufacturers can successfully clear these checkpoints and avoid costly deficiency letters.Key Timestamps00:19 – The evolution of AI from an amusing novelty to industry fatigue.00:54 – The turning point: The FDA's adoption of Elsa in its internal scientific review process.01:34 – Moving past the hype: Focus on the actual rules of AI in MedTech.01:54 – The Electricity Analogy: Shifting from candles to infrastructure and the National Electrical Code.03:13 – The Electric Toaster lesson: Focus on a better product, not the technology powering it.03:57 – Understanding Software as a Medical Device (SaMD) as a full regulatory pathway.04:26 – Micro-timestamp: Defining Locked vs. Adaptive Algorithms and the core regulatory challenges of evolving data.05:14 – The Total Product Lifecycle Approach: Viewing FDA clearance as a checkpoint, not a finish line.05:40 – Breaking down the 2021 AI/ML Action Plan and its five core areas of focus.06:17 – Deep dive into Predetermined Change Control Plans (PCCPs) and the Omnibus Act framework.06:55 – Micro-timestamp: The three mandatory components of a successful PCCP submission.07:54 – Evaluating the 2021 draft guidance on 510(k) considerations for AI/ML-based SaMD.08:04 – Micro-timestamp: Data requirements (training, validation, testing) and managing demographic/clinical bias.08:35 – Algorithm transparency: Balancing proprietary tech with reviewer clarity.08:58 – Building QMS infrastructure for AI: Moving away from retrofitted legacy systems.09:27 – Micro-timestamp: Applying Risk Management under ISO 14971 and AAMI TIR34971 to AI-specific failure modes.10:14 – Proactive vs. Reactive Post-Market Surveillance: Tracking algorithm drift in the real world.10:53 – Key takeaways and lessons learned from building an off-grid home electrical system.11:59 – Teaser for next week: Common mistakes and patterns that trip up companies in AI submissions.Quotes"The device companies that are going to win aren't the ones making the biggest deal out of having AI. They're the ones whose devices actually work better because of it and whose quality systems can prove that to the FDA." - Etienne Nichols"With AI, clearance is more of a checkpoint. You're going to have multiple of these checkpoints along the way." - Etienne NicholsTakeawaysRegulatory & SubmissionsTreat the PCCP as an Operational Reality: A Predetermined Change Control Plan cannot be written at the last minute as a mere submission document. It must strictly reflect your active software development process, covering planned modifications, modification protocols, and detailed impact assessments.Ensure Data Demographics Match Intended Use: The FDA scrutinizes the clinical, geographical, and demographic composition of your training, validation, and testing data. Algorithms must perform consistently across subpopulations to prevent significant safety risks.Commit to Algorithm Transparency: While the FDA does not require your proprietary source code, you must explain the algorithm's functionality and failure modes clearly enough for a reviewer to confidently assess its safety and effectiveness.Quality Management Systems (QMS)Design Controls and AI Risk Mitigation: QMS architectures must be built from the ground up to handle AI-specific failure modes (such as false positives, false negatives, or ...
    Show More Show Less
    19 mins
adbl_web_anon_alc_button_suppression_t1
No reviews yet