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 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 controlled documents …
California Meal and Rest Breaks: What You Dont Know Can Cos…
Responding to EEOC Discrimination Charges-What's Your Busin…
Implementing an Effective Human Error Reduction Program
Conflict Resolution - Prevent, De-escalate, Resolve
When Employees Travel: Wage and Expense Rules Employers Mus…
With Mandatory Paid Leave Gaining Ground Is It Time To Do A…
Female to Female Hostility @Workplace: All you Need to Know
Form 1099-MISC and 1099-NEC Compliance Update 2024
Validation Statistics for Non-Statisticians
The Totally Organized Professional Is All About Outcomes
Why EBITDA Doesn't Spell Cash Flow and What Does
GAMP5, Second Edition and Alignment with Computer Software …
Project Management for Non-Project Managers - Scheduling yo…
Sunshine Act Reporting - Clarification for Clinical Research
Understanding the Math of HR… So You Can Show How HR Impact…
FFIEC BSA/AML Examination Manual: What Compliance Officers …
How to Address ISO's New Climate Change Requirements
I-9 Audits: Strengthening Your Immigration Compliance Strat…
Re-imagine Finance & Accounting Made Simple. Three Webinars…
Stay Interviews: A Powerful and Low-Cost Employee Engagemen…
How To Conduct An Internal Harassment And Bullying Investig…
Effective Onboarding: How to Welcome, Engage, and Retain Ne…
Managing Toxic & Other Employees Who Have Attitude Issues
Analytical Method Validation Under Good Laboratory Practic…
Do's and Don'ts of Documenting Employee Behaviour, Performa…
Do's and Don'ts of Giving Effective Feedback for Performanc…
Onboarding New Hires: Leverage the Potential of Artificial …
Project Management for HR, Administrative Professionals, an…
Tattoos, hijabs, piercings, and pink hair: The challenges …
Using Behavior Based Interviewing for Finding the Best Matc…
How to Document Employee Discussions and Why it is Important
Stressed Out: How to Handle Conflict, Difficult People and …
Harassment, Bullying, Gossip, Confrontational and Disruptiv…
Best Practices for Working With Vendors and Suppliers
Understanding the Artificial Intelligence Landscape
Marketing to Medicare or Medicaid Beneficiaries - What You …
Accounting For Non Accountants : Debit, Credits And Financi…
Principles & Practices for the Cybersecurity of Legacy Medi…
Independent Contractor vs. Employee New Rule Issued by The …
Ultimate Persuasion Strategies! - Secret Influence Tools & …
Kicking your Employee Retention Efforts into Overdrive: Sta…