#468: SaMD Issues, Defects & Detection | Shawnna Monterrey

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 Shawnna 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 Shawnna 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." - Shawnna Monterrey

"A lot of defects manifest themselves in software, but they are actually electromechanical issues that the software didn't intend to catch." - Shawnna 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 podcast@greenlight.guru. 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.