Global Medical Device Podcast powered by Greenlight Guru

In this episode, host Etienne Nichols sits down with Michaela Kivett, a seasoned medical device consultant at Greenlight Guru, to break down the complexities of implementing an electronic Quality Management System (eQMS). Drawing from her background in orthopedic implant contract manufacturing and pharmaceutical process engineering, Michaela shares firsthand accounts of the critical inefficiencies that plague traditional paper and generic electronic repositories like SharePoint or Google Drive.
The conversation centers around the strategic planning required to transition between quality management states. Michaela introduces a powerful moving house analogy, illustrating that simply dragging and dropping messy, legacy records into a new digital environment will not solve underlying organizational issues. Instead, a successful migration requires an intentional internal self-evaluation, a culture of quality, and a structured, room-by-room approach to data and process transfer.
Additionally, the episode highlights how forward-thinking MedTech companies are leveraging advanced tools, including artificial intelligence, to streamline their eQMS implementation. By using AI to scan documents for compliance deficiencies against standards like ISO 13485, categorize sprawling folders, and map out workflow updates, manufacturers can dramatically mitigate the transitional efficiency dip and establish a mature, robust foundation for future scale.
Key Timestamps
00:42 – Michaela Kivett’s background: Transitioning from orthopedic quality engineering to pharma process engineering, and finding a passion for MedTech consulting.
03:15 – Operational friction: Real-world pain points of on-site communication, tracking down physical signatures across 100-acre facilities, and booking conference rooms.
04:32 – Version control nightmares: The consequences of multiple departments making parallel redlines without localized system notifications.
06:12 – Defining the eQMS: Distinguishing between a basic electronic file repository (SharePoint/Google Drive) and a specialized, medical device-focused quality platform.
08:58 – The universal MedTech pain point: Systemic organizational complexity and the hidden administrative burden of manual document referencing.
10:43 – The Rube Goldberg illustration: How disconnected spreadsheets, Word files, and manual trackers create fragile operational systems.
13:02 – The three legs of the medical device stool: Balancing ethical, legal, and monetary drivers to build organizational maturity.
16:04 – The "moving house" migration framework: Why dragging and dropping cluttered records fails and how to evaluate a legacy data landscape before a move.
19:25 – Operational entropy: Managing legacy supplier history and updating training matrices during a system overhaul.
21:10 – Leveraging AI in eQMS implementation: Using automated tools to scan documents for ISO 13485 gaps and auto-categorize large file volumes.

Quotes
"Organization is the most common pain point. And it's a very simple pain point. I think every industry probably feels that... but you underestimate exactly how many different documents and records you're going to be producing and how many different places they tie into each other." — Michaela KivettTakeaways
Audit Before You Migrate: Treat an eQMS implementation as an internal audit. Do not lift and shift messy legacy files; instead, use the transition to purge obsolete records and refine active procedures.
Mitigate the Efficiency Dip: Anticipate a temporary slowdown during a software transition. Minimize this area under the curve by building a sequential plan that prioritizes core procedures and training matrices before migrating complex design or risk data.
Design for Future Scale: Choose and configure your digital quality architecture not just for the team you have today, but for the corporate milestones of tomorrow—whether that involves clinical trials, an international 510(k) submission, or M&A.
Deploy AI for Compliance Mapping: Utilize AI tools to systematically scan old documentation folders for standard gaps (such as ISO 13485 or ISO 14971 compliance) and to automate the heavy lifting of categorizing thousands of uncategorized records.

References
ISO 13485: The international standard outlining quality management system requirements specific to the medical device industry.
Greenlight Guru: Purpose-built medical device software platform offering specialized QMS and EDC solutions to accelerate commercialization and ensure lifecycle compliance.
Connect with the host, Etienne Nichols on LinkedIn.

MedTech 101 Section
What is the difference between a QMS and an eQMS?
Think of your QMS (Quality Management System) as the blueprint for an entire house. It represents the actual words, rules, regulations, and standard operating procedures (SOPs) that dictate how your company builds safe medical hardware.
The eQMS (electronic Quality Management System) is the physical structure and construction material of the house. While you can build a rudimentary shelter out of cardboard boxes and tarps (like a disorganized SharePoint or a stack of paper binders), a true, specialized eQMS acts as a reinforced concrete foundation. It automates the pathways between rooms, handles notifications when a door is left open (like an outstanding training task), and ensures that every brick is stamped with a certified, immutable electronic signature.
Feedback Call-to-Action
We want to hear from you! Whether you are currently trapped in a Rube Goldberg web of spreadsheets or in the middle of a major system migration, share your stories, questions, or future topic suggestions with us. We read every email and pride ourselves on sending personalized responses to our community. Drop us a line at podcast@greenlight.guru.
Sponsors
This episode is brought to you by Greenlight Guru, the only dedicated medical device success platform designed specifically for MedTech professionals. Moving away from scattered SharePoint files or paper binders requires a system built with regulatory compliance in its DNA. Greenlight Guru integrates your entire lifecycle by pairing a robust QMS (Quality Management System) solution to automate closed-loop quality processes with a powerful EDC (Electronic Data Capture) solution to streamline your clinical data collection. Stop tracking down signatures and driving back to the office to fix handwritten logbooks. Discover how you can turn your quality architecture into a strategic asset by visiting Greenlight Guru.

The traditional approach to medical device commercialization often treats manufacturing as a distinct, isolated step executed after the design phase is completed. In this episode, Mike Dolphin, CEO of GuideStar Medical Devices, challenges this linear mindset by arguing that manufacturing process development is fundamentally an extension of product development itself. Drawing from his unique background spanning aerospace engineering at JPL, scientific research, and medical device ventures, Dolphin shares how upfront constraints shape a more predictable path to market.
The conversation centers heavily around the engineering and clinical challenges of epidural anesthesia delivery, a high-consequence procedure historically reliant entirely on a physician's tactile sense. Dolphin details how his company approached this clinical risk profile by designing a closed-loop system capable of automatically stopping a needle upon sensing the epidural space. By establishing critical manufacturing constraints—such as choosing injection-molded plastics and radiation sterilization from day one—the design team avoided the common trap of engineering a prototype that cannot be scaled.
Additionally, the episode dives into the practical friction between tight physical tolerances and production realities, showcasing a creative approach to mold development that bypasses typical vendor limitations. Dolphin also shares his perspective on balancing rigorous documentation with early-stage agility, warning founders against premature lock-down of design controls within a Quality Management System (QMS). Ultimately, the discussion underscores that true commercial readiness requires a unified view where the final product and the manufacturing pipeline are developed in parallel.
Key Timestamps
00:41 – Guest introduction: Mike Dolphin’s transition from aerospace engineering at JPL to MedTech leadership.
02:02 – Cross-industry lessons: How regulatory oversight, documentation, and system thinking in aerospace translate directly to medical device design.
03:02 – The clinical problem: Demystifying the high-consequence risks of epidural anesthesia, including accidental dural puncture and nerve damage.
05:14 – Engineering an actuator: Shifting from the clinical request for "better sensors" to building a closed-loop mechanical system.
07:34 – Epidural procedure metrics: The market scale of labor, delivery, and chronic pain injections in the US and globally.
09:47 – Integrating manufacturing early: Why sterilization and material choices must be established during initial requirements gathering.
12:02 – Common founder pitfalls: The danger of designing a product looking for a problem versus evaluating cost, market size, and manufacturability from the start.
13:58 – The documentation vs. QMS overhead balance: Knowing when to record choices and when to formally lock down design controls to preserve startup capital.
16:47 – Overcoming injection molding tolerance limitations: A case study on utilizing first principles physics and progressive mold variations to achieve a 10-micron output consistency.
21:04 – Managing manufacturing consistency: Dealing with brittle plastic runs, operator variances, and securing lines against unauthorized process shortcuts.
22:25 – Impact on the 510(k) pathway: Defining commercial readiness as manufacturing readiness for final finished product submissions.

Quotes
"Having worked in aerospace and in medical device, I can say that this is harder than launching rockets." — Mike Dolphin"Manufacturing is part of development in medical devices. You develop your product, you develop a prototype that works. Now you need to develop your manufacturing process. That takes time, that takes real engineering and real know-how." — Mike DolphinTakeaways
Integrate Manufacturing Into R&D: Do not treat manufacturing as a post-development handoff. Developing the manufacturing pipeline is a core engineering activity required to establish a fully validated, commercial-ready device.
Establish Production Constraints Early: Define your sterilization methods, primary materials, and fabrication methods (e.g., injection molding) during initial requirement generation to restrict the design space and eliminate unproducable prototypes.
Leverage First Principles for Tolerances: When manufacturing vendors claim tight tolerances are impossible due to material shrinkage, analyze the underlying physical limitations. Strategies like building progressive progressive molds can deliver highly consistent micro-level outputs.
Audit Process Consistency: Component quality depends entirely on process parameters. Even with identical raw materials, minor adjustments to cycle times or cooling rates by different operators can alter material properties like brittleness.
De-risk the 510(k) With Finished Production Runs: Because a 510(k) submission requires testing on the final finished product, achieving manufacturing readiness is the critical path to compiling compliant regulatory submissions.

References
GuideStar Medical Devices: The med-tech start-up developing safety solutions for epidural space placement to eliminate accidental dural punctures.
EpiZact: GuideStar’s flagship closed-loop epidural device referenced contextually during the design and tolerance discussion.
Connect with the Host: Etienne Nichols on LinkedIn

MedTech 101 Section
Actuator (vs. Sensor)
In engineering, a sensor is a component that detects a physical change in the environment (like a thermometer reading a drop in temperature) and turns it into a signal. An actuator is the component responsible for moving or controlling a mechanism based on a signal (like a switch turning an air conditioner on or off). In the context of this episode, instead of just giving doctors a sensor to show them where the needle is, the team built an actuator that physically stops the forward motion of the needle automatically, closing the loop between detection and mechanical action.
DFM (Design for Manufacturing)
Design for Manufacturing is the practice of designing physical products in a way that makes them easy, cost-effective, and consistent to produce at scale. Think of it like baking cookies: if you design a cookie shape that requires intricate, hand-carved detailing on every piece, it will take hours to make a single batch. If you design it to be stamped out cleanly by a cookie cutter, you can make thousands of identical units per hour with minimal errors.
Feedback Call-to-Action
We want to hear from you. Do you agree that manufacturing is an inseparable part of the development phase, or do you prefer a distinct handoff? Share your thoughts, leave us a review on your favorite podcast platform, or suggest a topic you want uncovered next. Send an email directly to podcast@greenlight.guru—we read every message and look forward to delivering the personalized insights you need to build compliant, high-quality medical technology.
Sponsors
This episode of the Global Medical Device Podcast is brought to you by Greenlight Guru. For MedTech companies looking to bridge the gap between early development and commercial scale, scattered documentation can quickly derail your timeline. Greenlight Guru provides the only dedicated Medical Device Success Platform designed specifically to unite your Quality Management System (QMS) with advanced Electronic Data Capture (EDC) solutions. By tracking your design history and managing production quality in a unified environment, Greenlight Guru helps you prove consistency, manage supplier risk, and build a clear, audit-ready data trail from your first prototyping run all the way through commercial manufacturing. Learn how to streamline your path to market at www.greenlight.guru.

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 Timestamps
00: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 NicholsTakeaways
Build 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.

References
FDA, 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 Section
Overfitting
Think 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 Drift
Imagine 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.
Sponsors
This episode is brought to you by Greenlight Guru. Navigating the fast-moving compliance landscape for AI-enabled medical devices requires software that keeps pace with innovation. Greenlight Guru offers comprehensive Quality Management System (QMS) and Electronic Data Capture (EDC) solutions designed specifically for MedTech. By streamlining your documentation, tracking design history, and capturing robust clinical data, Greenlight Guru helps you build the rigorous quality systems required to clear regulatory hurdles globally. Learn more at www.greenlight.guru.
Feedback Call-to-Action
We want to hear from you! What are your thoughts on the future of AI regulation? Are you implementing PCCPs in your current workflows? Send your thoughts, feedback, and topic suggestions to podcast@greenlight.guru. Etienne reads and responds to emails personally, and your ideas could shape our next episode!

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 Timestamps
00: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 NicholsTakeaways
Human-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.

References
FDA 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 devices — The foundational blueprint for mapping out software hazard severity.
Etienne Nichols' LinkedIn: Connect with the host directly for full access to the original Purolea blog post breakdown and further MedTech compliance discussions.

MedTech 101 Section
Algorithmic Data Splitting: The "Final Exam" Analogy
To understand how machine learning models are validated without testing every infinite possibility, think of the process like preparing a medical student for a board certification exam:
Training Data (The Textbook): This is the information the AI studies. It looks at thousands of examples to learn what a pattern looks like.
Validation Data (The Practice Quizzes): This data is used during development to fine-tune the model, fix minor errors, and adjust its parameters. The student takes these quizzes to see where they need to study harder.
Test Data (The Final Exam): This is a completely hidden, clean set of data that the model has never seen before. True validation only happens here. If you test an AI on data it already saw during its training phase, it hasn't proven it can think—it has just proven it can memorize the answer key.

Sponsors
This episode is brought to you by Greenlight Guru. Navigating the intersection of automated engineering tools and strict regulatory expectations requires an unshakeable quality architecture. Greenlight Guru provides purpose-built Medical Device QMS (Quality Management System) and EDC (Electronic Data Capture) solutions designed to help MedTech companies maintain ironclad human oversight, compliant audit trails, and risk-proportionate validation pathways. Ensure your innovative tools enter a structured, defensive quality environment rather than a regulatory vacuum.
Feedback Call-to-Action
Did this episode change how you view your team's use of automated tools? Do you have a different take on how the QMSR handles machine learning validation? We want to hear from you. We read and personally respond to every listener message. Send your feedback, constructive pushback, or future episode topic suggestions directly to our production desk at podcast@greenlight.guru.

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 Timestamps
00: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 NicholsTakeaways
Regulatory & Submissions
Treat 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 subpopulation anomalies) using risk management standards like ISO 14971 and specialized guides like AAMI TIR34971.
Transition to Proactive Post-Market Surveillance: Traditional, reactive complaint handling is insufficient for adaptive algorithms. Quality systems must incorporate continuous, active real-world monitoring to detect and rectify algorithm drift before it compromises patient safety.

References
FDA AI/ML Action Plan (2021): The foundation document outlining the agency's five-part focus on software modification, PCCPs, good machine learning practices, patient-centered transparency, and real-world monitoring.
510(k) Considerations for AI/ML-Based SaMD Draft Guidance: Critical guidance emphasizing data splitting protocols, demographic representation, and algorithm transparency.
ISO 14971 & AAMI TIR34971: The essential consensus standard and technical information report mapping out the application of risk management principles specifically to machine learning and artificial intelligence.
Etienne Nichols' LinkedIn Profile: Connect directly with host Etienne Nichols on LinkedIn to share feedback, ask questions, and discuss the latest trends in MedTech regulatory affairs.

MedTech 101 Section
Software as a Medical Device (SaMD)
SaMD is software designed to perform medical functions—such as diagnosing, treating, or monitoring diseases—without being part of physical medical device hardware.
The Analogy: Think of a traditional medical device as a dedicated physical calculator sitting on a doctor's desk. SaMD is like a medical application downloaded onto a standard smartphone; the phone itself isn't the medical device, but the software running inside it is acting as one.

Locked vs. Adaptive Algorithms
A Locked Algorithm is an AI model that remains completely unchanged after it is cleared and deployed. It performs its function exactly the same way every time until the manufacturer manually pushes a controlled update. An Adaptive Algorithm is an AI model that continues to learn, retrain, and evolve on its own based on new real-world patient data after it is deployed.
The Analogy: A locked algorithm is like a physical cookbook printed on paper; the recipes never change unless the publisher prints a second edition. An adaptive algorithm is like a living chef who tastes every dish they make, continuously altering the recipe over time based on feedback from the diners.

Feedback Call-to-Action
We want to hear from you. Did this episode change how you look at your company's AI pipeline? Do you have questions about implementing a PCCP or structuring your design controls for machine learning?
We read every single message and love delivering personalized responses to our community. Send your thoughts, feedback, reviews, or topic suggestions for future episodes directly to our team at podcast@greenlight.guru.
Sponsors
This episode of the Global Medical Device Podcast is brought to you by Greenlight Guru.
Navigating the complex landscape of AI/ML regulations requires an airtight quality foundation. Greenlight Guru provides specialized Medical Device Success Platforms that unify your team’s efforts. By utilizing their dedicated QMS (Quality Management System) solutions, you can seamlessly build AI-specific design controls and map out risk management strategies under ISO 14971. Furthermore, their integrated EDC (Electronic Data Capture) solutions allow you to execute rigorous clinical data collection, helping you gather the high-quality, traceable real-world performance data required to monitor algorithm drift and satisfy total product lifecycle demands.
Discover how to scale your AI enabled innovation safely by visiting