This course is essential for Medical Device companies interested in submitting software enabled medical Devices or Software as a Medical Device to the FDA for 510K approval. One of the biggest risks most company's face when submitting their device for approval is finding out after seven or more months of waiting that the 510K has been denied because the software portion of the submittal is inadequate and not compliant. They also face potential audit risk which might prevent them from selling their approved product if they have been found to not have an IEC62304 Compliant Software Quality System.
This course will ensure that Device companies will know exactly what documentation needs to be prepared. They will also know how to ensure the documentation is prepared correctly so the software portion of the submittal will be in compliance preventing delays of the 510K approval. Companies can also face potential audit risks and serious findings post submittal that can block their ability to ultimately sell their product successfully. This course will ensure that you know what is expected to have in place for compliance for your company during the preparation of a 510K to prevent this risk.
WHY SHOULD YOU ATTEND?
Developing software for medical devices can be a challenge especially if the device is complicated. You do not know if it is safe enough. You do not know if it tested enough. You do not know if the FDA will consider it for suitability for a 510K. Should your software cause harm to someone you don't know if you are protected from liability should your software fail.
Compliance with IEC62304 is key to ensure your software has been developed to the highest level of safety. Developing software based on the standard shows one way to indicate an intent to ensure the safety of your product. Gives you a framework to ensure you are developing and testing to consistent and stringent standard. Demonstrating compliance with the standard will be apparent in your submission and will be one way to ensure acceptance by the FDA.
LEARNING OBJECTIVES
- 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?
- Benefits of developing to an IEC62304 standard
- What are the components of the Software Lifecycle
- What are the major Software Work Products developed to the standard?
- How it fits in with a Company's Standard Quality Process
- What are the legal consequences for the company with the submittal if the company does not adhere to the Guidance
- One of the most common reasons that a Software Enabled Medical Device is denied a 510K is because the Guidance has not been followed
- What are the potential audit consequences if the Company does not have an IEC62304 Compliance Quality System in place
- Understand the regulatory need for IEC 62304 Guidance as it relates to submitting a 510K for Software Enabled Medical Devices
- What constitutes compliance with the Standard
- What areas does the Guidance Address
- What are the legal consequences for the company with the submittal if the company does not adhere to the Guidance
WHO WILL BENEFIT?
Managers, Supervisors, Directors, and Vice-Presidents in the areas of:
- Regulatory
- Quality
- Vice President of Compliance and Regulatory
- Compliance Expert
- Software Engineer
- Software Engineering Manager
- Software Compliance Engineer
- Medical Device Software Engineer
- Quality Assurance
- Design Assurance
- Design Engineers
Developing software for medical devices can be a challenge especially if the device is complicated. You do not know if it is safe enough. You do not know if it tested enough. You do not know if the FDA will consider it for suitability for a 510K. Should your software cause harm to someone you don't know if you are protected from liability should your software fail.
Compliance with IEC62304 is key to ensure your software has been developed to the highest level of safety. Developing software based on the standard shows one way to indicate an intent to ensure the safety of your product. Gives you a framework to ensure you are developing and testing to consistent and stringent standard. Demonstrating compliance with the standard will be apparent in your submission and will be one way to ensure acceptance by the FDA.
- 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?
- Benefits of developing to an IEC62304 standard
- What are the components of the Software Lifecycle
- What are the major Software Work Products developed to the standard?
- How it fits in with a Company's Standard Quality Process
- What are the legal consequences for the company with the submittal if the company does not adhere to the Guidance
- One of the most common reasons that a Software Enabled Medical Device is denied a 510K is because the Guidance has not been followed
- What are the potential audit consequences if the Company does not have an IEC62304 Compliance Quality System in place
- Understand the regulatory need for IEC 62304 Guidance as it relates to submitting a 510K for Software Enabled Medical Devices
- What constitutes compliance with the Standard
- What areas does the Guidance Address
- What are the legal consequences for the company with the submittal if the company does not adhere to the Guidance
Managers, Supervisors, Directors, and Vice-Presidents in the areas of:
- Regulatory
- Quality
- Vice President of Compliance and Regulatory
- Compliance Expert
- Software Engineer
- Software Engineering Manager
- Software Compliance Engineer
- Medical Device Software Engineer
- Quality Assurance
- Design Assurance
- Design Engineers
Speaker Profile
Jose Ignacio Mora
Jose Mora is a Principal Consultant specializing in Manufacturing Engineering and Quality Systems. For over 30 years he has worked in the medical device and life sciences industry specializing in manufacturing, process development, tooling, and quality systems. Prior to working full time as a consulting partner for Atzari Consulting, José served as Director of Manufacturing Engineering at Boston Scientific and as Quality Systems Manager at Stryker Orthopedics, where he introduced process performance, problem solving, and quality system methodologies.During that time he prepared a white paper on the application of lean manufacturing methods to the creation and management of …
Upcoming Webinars
Maximizing Productivity with ChatGPT: AI Solutions for HR, …
Excel - Pivot Tables - The Key To Modern Data Analysis and …
New EEOC Report: Workplace Harassment Prevention Not Workin…
Human Error Reduction Techniques for Floor Supervisors
21 CFR Part 11 - Compliance for Electronic Records and Sign…
Form W-9 Compliance to Avoid Penalties: TIN Verification, B…
Transforming Change and Conflict into Diverse-Inclusive-Col…
Re-imagine Finance & Accounting Made Simple. Three Webinars…
Navigating 2025 Employment Laws: What Every Employer Needs …
Managing Difficult Employee Conversations
ChatGPT and Project Management: Leveraging AI for Project M…
Future Of Forecasting And Budgeting With Rolling Forecast
Handbook Overhaul 2026: Compliance, OBBB Act & Beyond
Internal Controls in Accounts Payable
The FMLA - An Employer's Guide to Compliance and Employee A…
Excel Power Skills: Master Functions, Formulas, and Macros …
Develop People Intelligence: Is Your Communication Style as…
The Impact of Artificial Intelligence on Your Workforce
AI in Everyday Work – help with Microsoft products
How to Document Employee Discussions and Why it is Important
Construction Lending And Real Credit Administration: Evalua…
The Anti-Kickback Statute: Enforcement and Recent Updates
Navigating FDA Inspections: From SOP to 483
2025 EEOC & Employers: Investigating Claims of Harassment …
2-Hour Virtual Seminar on DeepSeek R1 for Business and Mark…
Risk Analysis in the Medical Device Design Process
Introduction to Microsoft Power BI Dashboards
How To Get Control of Your Day, Life & Career - Time Manage…
AI Across the Business: Practical Use Cases for Founders an…
6-Hour Virtual Seminar on Learning the Highlights of Excel …
Female to Female Hostility @Workplace: All you Need to Know
Writing Effective 483 and Warning Letter Responses
FDA Recommendations for Artificial Intelligence/Machine Lea…
Language is Code - Intro to AI - Generative AI - ChatGPT an…
Understanding EBITDA – Definition, Formula & Calculation