Nancy Knettell, Founder and Principal at Software510K, LLC, has over 30 years in combined Mechanical Design, Software Development, and Regulatory experience primarily in the Medical Device industry working with such major medical device companies such as Smith and Nephew, Philips Medical, CR Bard, Read more
The reliability of medical device software and the risk associated with it has become a key concern. One of the biggest risks you can face when submitting your software-enabled medical device for approval is finding out – after months of waiting – that the 510K has been denied because the software is noncompliant. You also face potential audit risk that might prevent you from selling your product if doesn’t have IEC62304 compliant software quality system.
Let’s face it: developing software for medical devices can be a challenge – especially if the device is complicated. You don’t know whether it’s safe enough, or tested enough – or whether the FDA will consider it suitable for a 510K. And if your software fails and harms someone, you don’t know whether you’re protected from liability. So what are your options?
Compliance to IEC62304 is the key to ensure that your software has been developed to the highest level of safety – and that your medical device is safe. It gives you a framework to ensure that you are developing and testing to consistent and stringent standard. Demonstrating compliance will be apparent in your submission – and one way to ensure acceptance by the FDA.
• The regulatory need for IEC62304 guidance
• What constitutes compliance to the standard?
• How IEC62304 fits in with a company's standard quality process
• What areas does the guidance address?
• What are the legal consequences if your company does not adhere to the guidance?
• One of the most common reasons for 510K denial
• What are the potential audit consequences if your company does not have an IEC62304 compliance quality system in place?
Why Should You Attend:
Join this webinar, where medical device expert Nancy Knettell will show you how to get 510K approval from the FDA for your software enabled medical devices. She will show you exactly what documentation to prepare – and how to prepare it correctly – so that the software portion of the submittal is in compliance to IEC62304. She will explain how IEC62304 differs from other compliance standards such as ISO13485, its benefits, the elements that constitute an IEC62304 compliant system – as well as the components of the software lifecycle, along with examples of major software products developed to the standard. You will know how to fit IEC62304 with your company’s standard quality process, the legal consequences of not adhering to the guidance, the most common reason for denial of 510K approval – and the potential audit consequences if your company does not have an IEC62304 compliance quality system in place.
After attending the webinar, you will you know how to confidently prepare for – and get – a 510K approval from the FDA for your software enabled medical devices.
• Why is having an IEC62304 compliant software quality system important to both developing your software for 510K approval and how you can be putting your company at risk post approval if you do not have a compliant system in place?
• What is IEC62304 and how does it differ from other compliance standards such as ISO13485?
• What are the elements that constitute an IEC62304 compliant system?
• What are the benefits of developing to IEC62304 standard?
• What are the components of the software lifecycle?
• What are the major software products developed to the standard?
What You Get:
• Training Materials
• Live Q&A Session with our Expert
• Participation Certificate
• Access to Signup Community (Optional)
• Reward Points
Who Will Benefit:
• Vice Presidents – Regulatory Affairs/Quality Assurance/Compliance
• Regulatory experts
• Compliance experts
• Medical device software engineers and managers
• Software compliance engineers
• Quality managers, engineers and assurance personnel