Most discussions around medical device quality stop at commercial launch. Once a product ships, teams tend to celebrate and move on to the next development cycle. However, the real engineering work often begins the moment a device leaves the manufacturing floor. In this episode of the Global Medical Device Podcast, host Etienne Nichols sits down with Shawnnah Monterrey, founder of Beanstalk Ventures and an FDA-accredited third-party reviewer with 25 years of medical device software experience, to explore what happens after product deployment.

Monterrey shares rare insights gained from evaluating FDA submissions and troubleshooting high-impact field issues across platforms ranging from glaucoma imaging at ZEISS to CTDNA cancer assays at Illumina. The conversation covers the often-overlooked requirements of manufacturing transfer, deployability, and software upgrade mechanisms. Monterrey explains how inadequate upstream characterization—such as neglecting physical shipping stresses or omitting subsystem-level DFMEAs—directly manifests as costly "dead on arrival" (DOA) failures and field complaints.

The discussion also dives deep into the mechanics of defect detection, comparing hardware tolerance stack-ups with complex software root cause analysis. Monterrey illustrates how robust unit testing, clear design documentation, and structural post-market surveillance prevent catastrophic field recalls. Finally, the episode highlights the critical need for open communication channels between R&D, manufacturing, and post-market complaint handling teams to feed field intelligence back into future product iterations.

Key Timestamps

• 00:00 - Introduction to Etienne Nichols and guest Shawnnah Monterrey, CEO of Beanstalk Ventures.
• 01:15 - Crucial pre-shipping checks that first-time medical device founders routinely miss.
• 02:05 - Software transfer to manufacturing, deployability, eStar submissions, and cybersecurity requirements.
• 03:10 - Root causes of "Dead on Arrival" (DOA) product deliveries and shipping reliability testing.
• 04:20 - The concept of injection detection: Why detecting bugs earlier in R&D saves exponential costs.
• 05:45 - Unanticipated failure modes, software-hardware interaction, and the necessity of bottom-up DFMEAs.
• 07:30 - Software defect isolation, unit testing vs. system-level troubleshooting, and simulating user environments.
• 08:15 - Case study: Class 1 ventilator recall, software algorithm flaws, and root cause analysis across 80,000 units.
• 10:40 - Field upgradeability, patchability in legacy firmware devices, and managing regulatory trade-offs.
• 12:15 - Transforming customer complaints from isolated fires into upstream process and product design improvements.
• 14:00 - Usability issues, off-label user behavior, and manufacturer liability regarding indications for use.
• 16:30 - Closing feedback loops: Structuring open communication between R&D, post-market teams, and field service.

Quotes

"The sooner a defect is injected into the product and the later you find it, the more expensive it is going to be to correct. You want to tighten that gap up as close as possible." - Shawnnah Monterrey

"A lot of defects manifest themselves in software, but they are actually electromechanical issues that the software didn't intend to catch." - Shawnnah Monterrey

Takeaways

• Prioritize Software Deployability Upstream: Under current FDA eStar submission standards and cybersecurity guidance, software deployment, upgrade mechanisms, and maintenance processes must be documented and tested well before shipping.
• Execute Bottom-Up DFMEAs: While FDA risk management emphasizes top-down system hazard analysis (ISO 14971), robust subsystem-level DFMEAs are essential to capture unexpected interaction defects between electromechanical hardware and software.
• Unit Testing Accelerates Root Cause Analysis: Simulating inputs via automated software unit tests allows engineering teams to reproduce obscure field defects instantly without needing to replicate complex human-patient variables.
• Design for Field Upgradeability: Building patchable, field-upgradeable firmware and software architectures protects device manufacturers from catastrophic physical recalls across large installed bases.
• Bridge R&D and Complaint Management: Companies must establish formal feedback channels between post-market complaint handling teams and R&D engineers to ensure real-world failure trends drive future design controls.

References

• Etienne Nichols LinkedIn Profile: https://www.linkedin.com/in/etiennenichols/
• FDA eStar Program: The FDA's electronic submission template used to streamline medical device 510(k) and De Novo review processes.
• ISO 14971: The international standard for the application of risk management to medical devices.
• Cardiac Arrest: Five Years as a CEO on the Fed's Hit List by Howard Root: Recommended book detailing off-label use, regulatory enforcement, and legal liability in MedTech.

MedTech 101 Section

Injection Detection Think of building a medical device like baking a cake from a recipe. If you accidentally add salt instead of sugar at the start (injecting a defect), it is easy and cheap to toss out the flour and start over. But if you don't taste the cake until after it is baked, frosted, packaged, and delivered to a customer's party, fixing that mistake requires shipping a whole new cake, apologizing to the buyer, and paying for delivery. In MedTech software and hardware, "injection detection" means testing early and often so you catch design "bugs" while they are still in the mixing bowl rather than after thousands of devices are in patients' hands.

Design Failure Mode and Effects Analysis (DFMEA) Imagine examining every individual part of a car engine—from the biggest piston down to the smallest rubber seal—and asking: "How could this specific part break, and what happens to the driver if it does?" A DFMEA is a systematic, bottom-up engineering blueprint where teams evaluate each component or software line to predict failures before the device is ever built.

Feedback Call-To-Action

What post-market challenges has your medical device team encountered after product launch? We want to hear your thoughts, topic requests, and guest suggestions. Send your feedback directly to [email protected]. Every message is reviewed personally by our team to help shape future episodes.

Sponsors

This episode is brought to you by Greenlight Guru.

Navigating medical device quality from early-stage R&D through post-market surveillance requires tools built specifically for the MedTech industry. Greenlight Guru offers an all-in-one Medical Device Success Platform combining modern Quality Management System (QMS) and Electronic Data Capture (EDC) solutions. Whether you are preparing software documentation for an eStar submission or connecting customer complaint signals back to upstream design controls, Greenlight Guru helps you scale compliance, streamline clinical data, and bring safe devices to market faster. Learn more by visiting www.greenlight.guru.

Navigating the regulatory landscape for combination products requires understanding how primary modes of action (PMOA) dictate oversight pathways. In this episode, host Etienne Nichols sits down with Jim Fentress, Director of Regulatory Affairs at Galero (a Santa Group company), to unpack the structural differences and hidden pitfalls when medical device and pharmaceutical worlds collide. They discuss how the FDA handles lead agency designation across CDRH and CDER using interagency agreements and official Requests for Designation (RFD).

A central theme of the discussion is managing quality management systems under 21 CFR Part 4. The pair explore the friction that occurs when pharmaceutical companies act as lead applicants for drug-led combination products, requiring them to incorporate device design controls (ISO 13485 / QMSR) and CAPA systems into their existing CGMP framework. Jim explains the practical realities of integrating Part 210/211 elements—such as calculation of yield and stability testing—into a single, operational QMS without overcomplicating procedures.

Finally, the conversation delves into critical execution details: risk management under AAMI TIR105 (ISO 14971 vs. ICH Q9), labeling classifications (single entity, co-packaged, and cross-labeled), and strict change control protocols. Jim highlights how post-market design changes to a device constituent part can impact the pharmaceutical partner's NDA or baseline regulatory filings, underscoring the necessity of transparent cross-industry communication from initial development through full commercial release.

Key Timestamps

• 00:00 – Introduction to combination products and guest Jim Fentress.
• 00:48 – Understanding Primary Mode of Action (PMOA) and regulatory pathways (FDA vs. European authorities).
• 01:57 – FDA interagency agreements (CDRH and CDER) and Requests for Designation (RFD).
• 03:00 – 21 CFR Part 4 quality system integration (CGMP Part 210/211 and QMSR/Part 820).
• 05:22 – Navigating the communication gap between pharma companies and device manufacturers.
• 07:44 – Calculation of yield in drug manufacturing vs. medical device production.
• 09:05 – Risk management for combination products (AAMI TIR105: evaluating device-on-drug and drug-on-device risks).
• 12:15 – Bridging ISO 14971 and ICH Q9 framework structures in registration files.
• 13:16 – Design controls, user needs, and human factors validation (Module 5 / Section 3.2.R ECTD filings).
• 15:06 – Labeling pathways: Single Entity (Integral), Co-Packaged, and Cross-Labeled products.
• 18:18 – Change control risks: How minor device modifications affect drug application filings (NDAs, CBER/CDER supplements).
• 20:41 – Advice for device manufacturers partnering with pharma: Alignment on risk, documentation depth, and cleanroom requirements.

Standout Quotes

"There's four aspects of risk that you need to take into account: what is the risk of the drug alone, the risk of the delivery system alone, the risk of the drug on the device, and the risk of the device on the drug." — Jim Fentress

"Before you even think about making a change, you need to talk to your pharmaceutical partners because now what's represented as the co-packaged device constituent element is changing, and they need to inform the FDA." — Jim Fentress

Actionable Takeaways

• Establish Cross-Disciplinary Risk Management Early: Adopt frameworks like AAMI TIR105 to integrate traditional device risk protocols (ISO 14971) with pharmaceutical risk management (ICH Q9). Ensure assessment of cross-interaction hazards (e.g., drug interactions with delivery plastics, viscous drug effects on ejection times).
• Define Clear Part 4 QMS Interfaces: If operating primarily under device rules (QMSR/ISO 13485), build project-specific addenda to account for drug CGMP requirements such as stability testing, container-closure assessments, and calculation of yield limits.
• Align Post-Market Change Control Protocols: Establish explicit notification procedures between the device supplier and the NDA holder. Simple component material updates or geometry changes to a constituent part may require formal NDA supplements or changes-being-effected (CBE) filings with CDER.
• Scope Document Deliverables Upfront: Clarify whether the pharmaceutical partner requires high-level summary reports or the complete device master record (DMR) and design history file (DHF) to populate Section 3.2.R of their eCTD submission.
• Validate Cleanroom and Sterility Assumptions: Discuss cleanroom requirements early to avoid unnecessary cost structures; verify if an ISO 8 or ISO 7 environment is scientifically required for the assembly of non-sterile device constituents before adopting conservative pharma-grade aseptic norms (ISO 5).

Essential References

• 21 CFR Part 4: Regulation governing current good manufacturing practice (CGMP) requirements for combination products.
• AAMI TIR105: Technical Information Report providing guidance on the application of risk management to combination products.
• ICH Q9: International Council for Harmonisation guidelines for Quality Risk Management in pharmaceutical manufacturing.
• eCTD Section 3.2.R: Regional information section of the Electronic Common Technical Document where medical device constituent data is filed.
• Host Contact: Connect with Etienne Nichols on LinkedIn.

MedTech 101

Primary Mode of Action (PMOA)

The primary mode of action is the single mechanism that provides the primary therapeutic effect of a combination product.

Think of a drug-eluting stent:

• The main goal is to physically prop open a blocked artery (a mechanical action performed by the stent device).
• The drug baked into the metal coating slowly releases to prevent scar tissue from re-blocking the artery (an ancillary chemical action).

Because the physical propping open is the primary therapeutic mechanism, the FDA classifies the product as a device-led combination product under CDRH. Conversely, an epinephrine auto-injector's main therapeutic outcome comes from the epinephrine drug working in the bloodstream; the plastic casing and needle are auxiliary delivery mechanisms, making it a drug-led combination product overseen by CDER.

Feedback & Community

We want to hear from you! Have questions about combination product regulatory strategies, or want to suggest a topic for a future episode?

Email us directly at [email protected]. Every message is reviewed personally by our team to help shape upcoming content.

Sponsor Integration

This episode is sponsored by Greenlight Guru.

Navigating the blurred lines of 21 CFR Part 4 between drug CGMPs and device design controls requires dynamic, interconnected quality tools. Greenlight Guru provides purpose-built Quality Management Software (QMS) and Electronic Data Capture (EDC) solutions designed specifically for MedTech teams. Whether you are managing complex design controls, tracking supplier changes, or managing clinical trial data for combination products, Greenlight Guru helps you bring safe, compliant devices to market faster.

Discover how to streamline your regulatory files and risk matrix at www.greenlight.guru.

Many early-stage medical device founders face a major dilemma: how do you prove regulatory maturity to investors and partners before you actually hold a final CE mark or FDA approval? Waiting until the end of a long development cycle creates significant commercial risk. By treating regulatory readiness as a continuous maturity process rather than an all-or-nothing milestone, startups can build trust early and avoid costly late-stage surprises.

In this episode, host Etienne Nichols sits down with Malte Knowles Schmidt, Global Portfolio Lead for Medical Device Software, AI, and Cybersecurity at TÜV SÜD. Drawing from his background as an ICU nurse, an R&D product leader for Class III cardiac implantables at Biotronik, and now a notified body leader, Malte breaks down how startups can step out of their silos. He emphasizes that notified bodies and medical device companies must both "leave the ivory tower" to establish practical, real-world communication long before a formal audit occurs.

The conversation explores concrete strategies for demonstrating regulatory maturity during development, including standing up an enterprise Quality Management System (eQMS), securing partial ISO 13485 certification for core design processes, and leveraging external testing as strategic "breadcrumbs." Malte also cautions founders against chasing "Pyrrhic certifications"—winning regulatory approval at the cost of commercial viability—and shares practical guidance on when and how to initiate early structured dialogues with notified bodies.

Key Timestamps

• 00:00 - 02:15 | Introduction to the "Regulatory Ivory Tower"
• Etienne introduces guest Malte Knowles Schmidt and sets up the challenge of proving regulatory maturity early in the startup lifecycle.
• 02:16 - 05:04 | Why Communication Gap Exists Between Startups & Notified Bodies
• Malte discusses why structured dialogues often feel too abstract for founders and why concrete examples are needed to make early engagement approachable.
• 05:05 - 08:30 | Defining Regulatory Maturity & The Agile QMS
• Exploring how investors view regulatory progress, why build-measure-learn mindsets belong inside a QMS, and how an eQMS acts as a foundational framework.
• 08:31 - 12:10 | Unlocking Value Through Partial ISO 13485 Certification
• A breakdown of how certifying core design and development processes early builds commercial credibility and attracts investor funding before full scope audits.
• 12:11 - 16:45 | Leveraging External Testing & Avoiding "Pyrrhic Certifications"
• How penetration testing and biocompatibility act as evidence breadcrumbs, plus the trap of sacrificing commercial viability just to get a certificate.
• 16:46 - 20:30 | When and How to Initiate Contact with a Notified Body
• Practical advice for founders on overcoming the fear of reaching out, preparing essential homework (intended purpose, risk classification), and taking the first step.

Quotes

"A Pyrrhic certification comes from a Pyrrhic victory, where you win the battle, but the losses are so great that the victory is basically meaningless... startups make the certification their core goal and not the commercial success." - Malte Knowles Schmidt

"If you're asking yourself the question, 'Should I be talking to a notified body?'—then stop right there, because the answer is yes." - Malte Knowles Schmidt

Key Takeaways

• Establish Early Regulatory Breadcrumbs: Investors want to see continuous progression. Utilizing an eQMS, conducting third-party testing (e.g., penetration or biocompatibility testing), and mapping regulatory roadmaps provide tangible proof of maturity long before final approval.
• Consider Partial ISO 13485 Certification: Startups do not need to wait for full scope certification. Certifying core design and development processes first demonstrates organizational discipline and can unlock major funding rounds.
• Avoid the Pyrrhic Certification Trap: Do not sacrifice your core business model or reduce critical product capabilities solely to make certification easier. Always align regulatory strategy with ultimate commercial viability.
• Treat Your QMS as an Agile System: Quality management is not a static set of restrictive rules; it is an iterative framework that should evolve alongside your product and team processes.
• Initiate Dialogue Early: Notified bodies are accessible for preliminary discussions. Reaching out early helps validate your intended purpose, risk classification, and submission assumptions before sinking capital into the wrong pathway.

References

• White Paper: Leaving the Regulatory Ivory Tower: How Early Notified Body Dialogues Reduce Business Risk by Malte Knowles Schmidt (TÜV SÜD).
• ISO 13485 Standard: Quality management systems requirements for regulatory purposes in the medical device sector.
• Host LinkedIn: Etienne Nichols on LinkedIn

MedTech 101 Section

• Pyrrhic Certification: Named after King Pyrrhus of Epirus, whose army won a battle against the Romans but suffered devastating losses in the process. In MedTech, a Pyrrhic certification occurs when a company successfully gets a medical device certified, but had to compromise so many features, intended uses, or commercial claims during the process that the resulting product has no real value in the market.
• Notified Body: An independent organization designated by an EU member state to assess whether a medical device complies with applicable regulatory standards (such as EU MDR) before it can be placed on the European market. Think of them as accredited referee agencies that verify safety and performance.
• Partial ISO 13485 Certification: Instead of waiting until an entire company, manufacturing line, and distribution network are fully operational to get audited, a company can undergo a certified audit specifically for a limited scope—such as its initial design and development processes.

Feedback Call-to-Action

We love hearing from our listeners! Did this episode change how you view early engagement with notified bodies? Do you have questions about implementing an eQMS or navigating partial ISO certification?

Send your thoughts, topic requests, or guest recommendations directly to [email protected]. We read every message and respond personally to our community!

Sponsors

This episode of the Global Medical Device Podcast is brought to you by Greenlight Guru.

Navigating the regulatory landscape requires a solid foundation built on quality and clear clinical evidence. Greenlight Guru provides the only dedicated eQMS (Quality Management System) and EDC (Electronic Data Capture) platform purpose-built for medical device and software-as-a-medical-device (SaMD) companies. Whether you are aiming for partial ISO 13485 certification, setting up your first design controls, or running clinical trials to collect vital regulatory breadcrumbs, Greenlight Guru helps you scale efficiently while keeping you audit-ready. Learn more about how Greenlight Guru's modern QMS and EDC solutions can accelerate your path to market at www.greenlight.guru.

In this episode, host Etienne Nichols sits down with Ali Samiian, founder and managing principal of Popular Access Advisors, to demystify the critical and often misunderstood world of MedTech reimbursement. Far too many early-stage medical device companies treat reimbursement as a secondary, post-launch paperwork exercise, only to find that their brilliant, FDA-cleared technology fails because no one has figured out who will pay for it. Ali draws on his 20-plus years of experience in market access, health economics, and executive leadership to explain why reimbursement must be treated as a core product strategy long before submission.

The conversation explores how commercialization pathways are inherently dictated by the site of care—whether inpatient, outpatient, or home use. Ali highlights common and costly pitfalls, such as designing clinical trials solely for FDA clearance while neglecting the specific evidence endpoints that insurance payers demand. Payers do not just look at safety and efficacy; they look at long-term clinical value, accessibility, durability, and standard-of-care comparisons. Using practical, real-world examples, Ali demonstrates how simple adjustments to product design and clinical study lengths can proactively align a device with existing or novel code requirements.

Finally, the episode highlights the shifting regulatory landscape and new initiatives designed to accelerate market access for breakthrough innovations. Etienne and Ali discuss the FDA’s Total Lifecycle Product Advisory (TAP) program and the emerging CMS Regulatory Alignment for Predictable and Immediate Device (RAPID) program. By understanding these frameworks and embedding payer-relevant outcomes into early-stage research, innovators can significantly compress their revenue cycles, avoid product redesigns, and successfully deliver life-changing technologies into the hands of patients.

Key Timestamps

• 00:03 - Introduction to MedTech reimbursement and guest Ali Samiian.
• 01:46 - The difference between clearing the FDA bar and achieving commercial success.
• 02:16 - Case Study: How product design and classification categories impact commercialization.
• 03:45 - The risk of ignoring durable medical equipment (DME) requirements during design.
• 05:22 - Categorizing sites of care: Inpatient, outpatient, ASCs, and home use (DMEPOS).
• 06:15 - Mistake #1: Postponing reimbursement strategy until after FDA approval.
• 07:35 - Mistake #2: Designing clinical studies for the FDA without considering payer-relevant endpoints.
• 09:02 - Understanding standard of care, durability data, and minimizing study bias for payers.
• 10:30 - Exploring the FDA's TAP program and the new CMS RAPID program for breakthrough devices.
• 12:15 - Mistake #3: Rushing regulatory pathways without assessing commercial and price-point implications.
• 13:50 - Identifying stakeholders and understanding the oblique nature of CMS and payer regulations.
• 14:38 - Deconstructing how to build new codes and establish premium pricing from scratch.

Quotes

"Clearing the FDA bar is not really what gets us to commercialization. We need to have product and clinical differentiation... A lot of reimbursement is actually more of a strategy exercise." - Ali Samiian

"The FDA basically looks at is the product safe and effective? Payers look at is there value and is there accessibility for the product?" - Ali Samiian

Takeaways

• Incorporate Payer Endpoints Early: MedTech innovators should involve a reimbursement advisor during clinical trial design to incorporate payer-relevant endpoints (like durability and standard-of-care comparisons), avoiding the need for an expensive second study.
• Align Design with Code Descriptors: Ensure product features and testing durations match the strict regulatory definitions of your target site of care (e.g., verifying a home-use device meets the three-year durability testing threshold for DME classification).
• Evaluate Pathways Holistically: Assess regulatory pathways (510(k) vs. De Novo vs. PMA) not just by upfront cost or speed to market, but by their long-term implications on pricing, coding, and time-to-reimbursement.
• Leverage Breakthrough Programs: Companies with breakthrough device designation should actively follow and align with collaborative initiatives like the FDA's TAP and CMS's RAPID programs to secure immediate coverage upon clearance.

References

• FDA TAP Program: The Total Lifecycle Product Advisory program designed to provide early, strategic communication with senior FDA leadership for breakthrough devices.
• CMS RAPID Program: Regulatory Alignment for Predictable and Immediate Device program, an initiative aimed at accelerating coverage pathways for breakthrough innovations.
• Etienne Nichols: Connect with the host on LinkedIn.

MedTech 101 Section

• Reimbursement vs. FDA Clearance: Think of FDA clearance as getting a driver's license—it proves your device is safe to be on the road. Reimbursement is like getting a toll pass; it determines who is actually going to pay for the journey so you can keep driving.
• Durable Medical Equipment (DME): This is a category of medical equipment used in the home that can withstand repeated use. Think of it like a sturdy pair of boots—if it isn't designed and tested to last a specific number of years (usually three), payers won't classify it as DME, even if it works perfectly.
• The "Cup" Analogy for Coding: Payers view similar items as identical commodities. A cup is a cup, whether it holds coffee or tea, and they want to pay one standard price for it. To get paid more, an innovator must prove their "cup" has unique technology that provides a fundamentally different, meaningful clinical outcome—like a cup that mechanically prevents spills for patients with tremors.

Feedback Call-to-Action

We love hearing from our community of MedTech innovators! Do you have thoughts on this episode, questions about market access, or suggestions for future topics? Reach out to us directly at [email protected]. Every email is read by our team, and we look forward to providing you with a personalized response.

Sponsors

This episode is brought to you by Greenlight Guru, the only dedicated medical device success platform. Moving from product development to commercial adoption requires absolute precision in data and compliance. Greenlight Guru helps medical device teams smoothly bridge the gap between regulatory approval and commercialization. By integrating both Quality Management Software (QMS) and Electronic Data Capture (EDC) solutions, Greenlight Guru ensures your clinical trial data is flawlessly captured to satisfy the FDA, while keeping your quality systems audit-ready for commercial scaling. Learn more at www.greenlight.guru.

Artificial intelligence has officially entered the mainstream cultural zeitgeist, creating a wave of excitement—and a fair share of fatigue—across the medical device industry. In this episode, host Etienne Nichols sits down with Tyler Harmon, biomedical engineer and CEO of Iaso Automated Medical Systems, to cut through the marketing buzzwords. Together, they explore the technical realities behind the technology stack, shifting the conversation away from generic AI toward specific, actionable engineering frameworks.

The discussion highlights a critical distinction between traditional machine learning models and consumer-oriented Large Language Models (LLMs). Harmon explains that while technologies like convolutional neural networks (CNNs) have successfully processed medical imaging for years, modern LLMs introduce an intentional element of randomness to mimic human conversation. This lack of predictability presents unique challenges for medical device developers who operate in a deterministic, safety-critical environment where reproducibility is paramount.

Looking toward practical deployment, the episode addresses how companies can responsibly govern these tools both within their software architectures and their internal Quality Management Systems (QMS). From classifying external AI models as Software of Unknown Provenance (SOUP) under IEC 62304 to leveraging machine learning for early detection of Acute Respiratory Distress Syndrome (ARDS) in the ICU, this conversation serves as an essential guide for innovators looking to build the next generation of safe, compliant, and effective medical technologies.

Key Timestamps

• 00:05 – Introduction to the dual nature of AI in MedTech: embedded clinical algorithms versus internal process optimization.
• 02:14 – Demystifying the math: Breaking down artificial intelligence into linear and non-linear algorithmic transformations.
• 04:30 – The Turing Test, Markov chains, and why consumer LLMs are mathematically designed to be unpredictable.
• 07:15 – Real-world success stories: How convolutional neural networks (CNNs) revolutionized emergency stroke triage.
• 09:42 – Inside Iaso Automated Medical Systems: Using non-LLM machine learning to identify Acute Respiratory Distress Syndrome (ARDS) in critical care.
• 12:10 – AI Governance in the QMS: Designing specialized Standard Operating Procedures (SOPs) and Machine Learning Management Systems (AIMS).
• 15:35 – Evaluating recent FDA 510(k) clearances for LLM-adjacent technologies and managing third-party stacks as SOUP.

Quotes

"If we as innovators can't explain things to a more general audience, we generally don't understand them ourselves. And if you can't do that, it's probably not the best idea to be implementing it into your products." - Tyler Harmon

"I am probably going to be the biggest advocate you'll ever talk to about 'doctors need enablement, not replacement.' We need to give them the tools, the force multipliers to tackle the challenges they're going to face this century." - Tyler Harmon

Takeaways

• Classify External AI as SOUP: Treat third-party language models and external tech stacks as Software of Unknown Provenance (SOUP) under IEC 62304 frameworks, implementing rigorous risk management boundaries to isolate the core medical device logic.
• Engineer Out Randomness: Recognize that consumer LLMs purposefully integrate randomness layers to maximize user engagement. For clinical safety, developers must utilize architectural harnesses or alternative machine learning methods (like CNNs or random forests) to force more deterministic outcomes.
• Establish an AI Management System: Expand your organizational compliance beyond standard Quality Management Systems (QMS) and Information Security Management Systems (ISMS). Implement specific AI standard operating procedures and work instructions to govern internal token usage and data handling.
• Prioritize Clinical Enablement Over Automation: Focus clinical software engineering on clearing workflow bottlenecks and flagging early-stage critical conditions (such as ARDS) to allow bedside clinicians to deploy their hands-on expertise faster.

References

• Berlin Criteria: The formal, quantitative medical classification standard used by clinicians to diagnose and grade the severity of Acute Respiratory Distress Syndrome.
• IEC 62304: The international standard governing medical device software lifecycle processes, specifically detailing the management of Software of Unknown Provenance (SOUP).
• Connect with Etienne Nichols on LinkedIn to stay updated on the latest episodes and industry insights.

MedTech 101 Section

Understanding Non-Linear Math and LLMs

Think of a traditional medical device software algorithm like a standard thermometer tracking a fever. It follows a straight, predictable line: if the temperature input increases by one degree, the reading on the screen changes by exactly one degree. This is a linear system.

Modern AI, like Large Language Models (LLMs), works more like a seasoned doctor trying to diagnose a complex case by listening to a patient's story. The human brain doesn't just look at variables in a straight line; it connects random pieces of past experiences, reads between the lines, and notes subtle shifts in tone. To replicate this mathematically, software engineers introduce non-linearity.

Instead of a straight line, the math behaves like a web of thousands of intersecting pathways. To make the system feel even more human, creators add a controlled "randomness layer" (similar to a digital coin flipper) so the software doesn't always choose the most obvious, predictable word next. While this makes chatting with a computer feel incredibly natural, it presents an engineering challenge for medical device developers who require identical, reproducible results every single time.

Feedback Call-to-Action

We love hearing from our community of MedTech professionals. Do you have thoughts on how AI governance should evolve, or is there a specific industry topic you want us to tackle next? We read every message and pride ourselves on providing personalized responses to our listeners. Share your feedback, reviews, and topic suggestions directly with our production team at [email protected].

Sponsors

This episode is brought to you by Greenlight Guru, the only dedicated medical device success platform. When building cutting-edge technologies like software as a medical device or machine learning platforms, having an isolated, fragmented tech stack can slow your path to market.

Greenlight Guru seamlessly connects your engineering and quality operations by offering both a comprehensive Quality Management System (QMS) to manage your compliance governance, SOPs, and design controls, alongside robust Electronic Data Capture (EDC) solutions for optimizing your clinical data collection. By integrating your quality workflows with actual clinical data capture, Greenlight Guru helps you scale safely from research and development straight through to successful commercialization.

The medical device industry functions as a highly complex ecosystem where diverse niches—including regulatory affairs, quality assurance, marketing, and reimbursement—must seamlessly interconnect to bring life-saving technologies to life. In this episode, host Etienne Nichols sits down with Sean Smith, a 25-year B2B marketing veteran, journalist, and founder of the weekly LinkedIn newsletter MedTech Leading Voices. Together, they peel back the curtain on why traditional, corporate-centric marketing strategies often fail within the specialized medical device space, exploring instead how service providers, consultants, and experts can effectively communicate their value without losing their human touch.

As generative AI tools begin to saturate digital platforms with automated content, the landscape of B2B marketing has grown increasingly crowded and noisy. Sean discusses the critical paradigm shift required to cut through this digital "slop," emphasizing that true marketing success is rooted in foundational human behavior rather than algorithm hacking or perfect websites. He challenges the standard corporate playbook, pointing out the futility of over-polished taglines and unread online case studies, and explains how authentic storytelling and real-world problem-solving serve as the primary mechanisms for earning industry trust.

Looking toward the future of professional expertise, the conversation addresses the long-game nature of organic visibility and the rising importance of specialized professional networks. Sean outlines actionable strategies for medical device experts to transition their buried, day-to-day insights into public thought leadership by focusing on what truly drives human behavior: helping peers make money or keeping them out of trouble. Ultimately, the episode serves as a powerful reminder that robust, human-centric communities are the ultimate safeguard for safeguarding one's livelihood and career longevity in an automated world.

Key Timestamps

• 00:05 – Introduction of guest Sean Smith and the interconnected MedTech ecosystem.
• 01:52 – The origin story of MedTech Leading Voices and the challenges of navigating LinkedIn's closed platform.
• 03:11 – How the B2B marketing landscape has changed since 2022 with the rise of AI-generated content.
• 04:15 – Core philosophical pillars of modern marketing: Being human first and showing genuine interest in others.
• 06:22 – Debunking the B2C vs. B2B crossover myth and the trap of corporate website redesigns.
• 07:54 – How MedTech experts can unlock hidden value by documenting their day-to-day problem-solving.
• 09:41 – Repackaging technical content (webinars, articles, infographics) for different audience attention spans.
• 11:15 – The ultimate human motivators in professional spaces: Making money and staying out of trouble.
• 12:55 – Journalism principles in marketing: The critical value of expert attribution over anonymous AI output.
• 14:38 – Tactful visibility tricks for LinkedIn and the hidden power of a postscript (P.S.) in email communications.
• 15:52 – Etienne's "accidental" conference moderation strategy for gaining immediate executive access.
• 17:15 – Tactical advice for vendors: Building advisory boards and dropping the constant hard pitch.
• 18:50 – Leveraging free platforms like Substack to establish niche authority through consistency.
• 21:04 – Redefining "community" as an existential shield against automated AI displacement.
• 22:20 – Benchmarking success on social platforms: Shifting from vanity metrics to aggregate long-term trends.
• 23:45 – Case Study: How focusing on a niche topic like CAPA can generate a massive, passionate industry following.

Quotes

"First be human. First be a human being... I think that it's very difficult to humanize the kind of in-depth regulatory, quality, risk discussions that we have... and so we're trying to make this information accessible, understandable, and keep it at a human scale." - Sean Smith

"The European audience wants the same thing that everybody wants. They want to know how to make more money and how to stay out of trouble. Those are the only two things that motivate human beings. So if you can tether the story that you're telling to one of those two things... people don't like making mistakes." - Sean Smith

Takeaways

Regulatory & Quality Assurance

• Commoditization of "How-To" Content: Baseline regulatory explanations (e.g., standard steps to file a 510(k)) are rapidly becoming digitized and automated by LLMs. True value lies in sharing your unique perspective, industry misconceptions, and nuanced edge cases rather than boilerplate text.

Medical Device R&D

• Document the Daily Defenses: Engineers and developers provide value continuously through emails, internal PowerPoint presentations, and custom proposals. Capture these unique problem-solving workflows systematically to build a library of narrative proof points.

Marketing & Sales

• Drop the Pitch-Slap: Avoid aggressive, transactional sales messaging on professional networks. Instead, build visibility naturally by forming advisory committees, interviewing industry peers, and positioning your personal brand as a collaborative resource rather than a persistent salesperson.
• Consistency Trumps Virality: You don't need daily viral hits to grow a business. Select an achievable publishing cadence—whether a monthly Substack newsletter or quarterly standard breakdown—and commit to it for at least six to twelve months to escape the "crickets" phase.

References

• MedTech Leading Voices: A weekly LinkedIn newsletter curated by Sean Smith that spotlights standout thought leaders, insights, and conversations within the medical technology landscape.
• Let's Talk Risk: A specialized Substack publication focused on medical device risk management, referenced by Sean as a prime model of hyper-niche, community-driven authority.
• Connect with Etienne Nichols on LinkedIn

MedTech 101 Section

B2B vs. B2C Marketing

Think of B2C (Business-to-Consumer) marketing like a commercial for a sports drink or a makeup tutorial on TikTok. The goal is to capture short attention spans, leverage emotional impulses, and push for a quick, high-volume purchase.

B2B (Business-to-Business) marketing, especially in MedTech, is more like dating with the intention of marriage. You are selling complex services to teams of engineers, regulatory officers, and executives. They aren't buying on impulse; they are buying based on systemic trust, risk mitigation, and long-term relationships. This is why B2C tactics like flashy taglines or giant logos don't translate effectively into medical device consulting.

Feedback Call-to-Action

What are your thoughts on humanizing the technical side of the medical device industry? Have you had success building an authentic personal brand on LinkedIn, or are you struggling to cut through the AI noise? We love reading your thoughts and respond to our listeners directly with personalized insights. Send your feedback, guest suggestions, or burning MedTech marketing questions over to [email protected].

Sponsors

This episode is brought to you by Greenlight Guru, the only dedicated medical device success platform. When you're trying to prove your expertise and build an industry community, you need an infrastructure that mirrors that commitment to excellence. Greenlight Guru's connected Quality Management Software (QMS) and Electronic Data Capture (EDC) solutions help you seamlessly document your engineering breakthroughs, manage strict regulatory frameworks, and safely collect clinical data. Elevate your quality processes from a simple compliance exercise into a true competitive advantage by visiting 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 Kivett

Takeaways

• 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 [email protected].

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 Dolphin

Takeaways

• 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 [email protected]—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 Nichols

Takeaways

• 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 [email protected]. 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 Nichols

Takeaways

• 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 [email protected].

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 Nichols

Takeaways

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 [email protected].

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 www.greenlight.guru.