The 510(k), IDE, Q-Sub, De Novo, and PMA Submission and Approval Process

Description

The majority of medical devices are cleared for marketing in the U.S. by the FDA under the 510(k) process. The FDA holds companies responsible for filing new 510(k)s when new products are to be marketed in the U.S., or when existing products and/or their Indications for Use are changed. What are the 21 mandatory elements? How is Substantial Equivalence determined, proved, documented? What about IDE's, De Novo's or PMAs? And how to initiate dialog with theAgency under the Q-Submission program.. What should be included, and what should only be referenced. What new concerns need to be addressed now? How can companies make such determinations? What approaches are required for product changes; for process changes? What about software "in-" or "as-product"? How does ISO 14971 Risk Management fit into the submission documentation process?

Why Should You Attend:

The U.S. FDA mandates that the traditional 510(k) submission address 21 basic requirements. The "Special" and "Abbreviated" 510(k)s must also address them, but in different ways. In addition, the FDA Task Force has identified several problem areas with the existing medical device 510(k) process, leading to the growing push by the Agency to strengthen the 510(k) process. What can companies do in proactively addressing these issues, to "put the reviewer's mind at ease" when reviewing a 510(k)? How can we use a similar format and rationale for IDE's, De Novo's, and even PMAs. Use of the Q-Sub to initiate dialog with the Agency.

Areas Covered in the Webinar:

• The 510(k) and its purpose.
• The 21 Required Elements in the 510(k) - A model
• Finding, Proving and Documenting Substantial Equivalence
• Addressing Product "With-" or "As-software" Issues
• Documenting Device Risk
• The Declarations
• The Q-Sub, IDE, De Novo, and PMA submissions
• U.S. FDA Device Clearance Process

Who Will Benefit:

Expectations for meaningful, results driven device submissions and documented product development activities are increasing among the U.S. FDA, as well as similar expectations by regulatory agencies world wide. Growing high-profile field problems indicate that design control and it’s effect on new/changed product and the submission review process is not as formal and rigorous as the FDA expects. How can a company maximize the data to prove compliance to the 21 FDA-defined requirements for a valid submission. For most companies, proactively addressing these concerns, spoken or unspoken, are not rocket-science. Proactive implementation in current device submissions can minimize wasted resources, assist the FDA reviewer to clear the submission, speed the entire process, and minimize the chance of unnecessary delays in the FDA's decision.

• Senior management
• Regulatory Affairs
• Quality Assurance
• Production
• R&D and Engineering
• All personnel involved in a U.S. FDA-regulated environment especially those involved in new product development, line extensions, and incremental product improvements, having to evaluate those changes to existing FDA-cleared / approved submissions, and then document their decisions in harmony with regulations.