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.
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.
Managers, Supervisors, Directors, and Vice-Presidents in the areas of:
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.
Managers, Supervisors, Directors, and Vice-Presidents in the areas of:
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 …
Updated Metro 2®, e-OSCAR and the New Tougher FCRA/CFPB Com…
Conquer Toxic People - Learn To Protect Yourself And Get Yo…
Introduction to Generative AI for Accountants
Dealing With Difficult People In Life & Work
Surviving and Thriving Organizational Change and Loss: The …
Impact Assessment and Risk Management for Change Control
How to Write Effective Audit Observations: The Principles f…
Excel Deep Dive: Advanced Tips & Techniques – A 3-hour Work…
FDA Regulation of Artificial Intelligence/ Machine Learning
Coming Soon - New Minimum Salary Levels for Exempt Employee…
Marijuana: Compliance and Safety in the Workplace
Stressed Out: How to Handle Conflict, Difficult People and …
2025 Top Employment Regulations That Will Impact Employers!
How to Handle Workplace Conversations Around Politics and R…
Data Integrity: Compliance with 21 CFR Part 11, SaaS-Cloud,…
How to Give Corrective Feedback: The CARE Model - Eliminati…
Improving Employee Engagement & Retention Through Stay Inte…
SOPs - How to Write Them to Satisfy those Inspectors
Why EBITDA Doesn't Spell Cash Flow and What Does
Marketing to Medicare or Medicaid Beneficiaries - What You …
With Mandatory Paid Leave Gaining Ground Is It Time To Do A…
Human Error Reduction Techniques for Floor Supervisors
Documenting Misconduct that Will Stand Up in Court
Tattoos, hijabs, piercings, and pink hair: The challenges …
Trial Master File (TMF)/eTMF, & FDAs Draft Guidance for Ele…
Project Management for Non-Project Managers - How to commun…
OSHA Requirements for Supervisors, Project Leaders & HR - W…
Unlock Employee Loyalty: Stay Interviews Will Keep Them Eng…
Sunshine Act Reporting - Clarification for Clinical Research
FFIEC BSA/AML Examination Manual: What Compliance Officers …
Female to Female Hostility @Workplace: All you Need to Know
Humane Layoffs: How to Let People Go with Compassion and De…
Onboarding is NOT Orientation - How to Improve the New Empl…
Managing Toxic & Other Employees Who Have Attitude Issues
Building GMP Excellence: A Guide to Implementing Compliant …
Excel Power Skills: Master Functions, Formulas, and Macros …