Design verification can be a difficult stage for medical device companies to carry out effectively. This is especially true when quality engineers limit their testing activities to only take place during the research and development (R&D) process.

In this episode, Mike Drues of Vascular Sciences joins me to discuss the nuances of design verification, as it relates to quality and design controls.

Some of the highlights of the show include:
●The difference between design verification and design validation is whether you designed the product correctly vs. you designed the correct product.
●Conduct research prior to design verification to determine which questions to ask and tests to perform to solve the right problems.
●Trust but Verify: Never assume that users know what they really need. They may think they know the best solution, but that’s not always true.
●No-thought fallback position is testing according to standards or guidance documents as a design verification strategy.
●Present testing matrix as part of FDA pre-submission process. Avoid making design verification an afterthought.
●Plan, be proactive, and collaborate with regulatory bodies to prevent delayed product launches and loss of revenue.
●Quality engineers in R&D need to participate, prototype, iterate, and demonstrate/prove concepts before design verification to discover bad decisions.