{"href":"http://player.captivate.fm/services/oembed?url=http%3A%2F%2Fplayer.captivate.fm%2Fepisode%2F788f00ca-edb0-42e2-bdb0-016d2d2614f9","version":"1.0","provider_name":"Captivate.FM","provider_url":"https://www.captivate.fm","width":600,"height":200,"type":"rich","html":"","title":"Why Design Verification Matters in Medical Device Design and Development","description":"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.\n\nIn this episode, Mike Drues of Vascular Sciences joins me to discuss the nuances of design verification, as it relates to quality and design controls.\n\nSome of the highlights of the show include:\n\u25cf\tThe difference between design verification and design validation is whether you designed the product correctly vs. you designed the correct product.\n\u25cf\tConduct research prior to design verification to determine which questions to ask and tests to perform to solve the right problems.\n\u25cf\tTrust but Verify: Never assume that users know what they really need. They may think they know the best solution, but that\u2019s not always true.\n\u25cf\tNo-thought fallback position is testing according to standards or guidance documents as a design verification strategy.\n\u25cf\tPresent testing matrix as part of FDA pre-submission process. Avoid making design verification an afterthought.\n\u25cf\tPlan, be proactive, and collaborate with regulatory bodies to prevent delayed product launches and loss of revenue.\n\u25cf\tQuality engineers in R&D need to participate, prototype, iterate, and demonstrate/prove concepts before design verification to discover bad decisions.","thumbnail_width":300,"thumbnail_height":300,"thumbnail_url":"https://artwork.captivate.fm/4cade977-259e-40fb-84e1-cebd94fc533d/6bc54bd8-8d5f-4d7b-9328-04f992d08fc9.jpg"}