FDA CDRH 510(k) Requirements During Recalls

“510(k) Requirements During Firm-Initiated Recalls ” 11/21/95This document defines 510(k) requirements for changes to fix problems that resulted in recalls. A key concept is that if the change restores the device to its original specifications, rather than altering the device, then a 510(k) may not be required. The relevant excerpt from the guidance is provided below and the full guidance is attached:

“During a recall action, OC’s case officer will review the firm’s recall strategy to determine if the firm’s corrective actions include a proposed modification to the device. In making this determination, OC’s case officer will consider whether a correction alters the device rather than just restoring it to its original specifications. If the correction just restores the device to its original specifications (e.g., a correction involving good manufacturing practices), OC’s case officer will determine that the recall does not involve a modification to the device. In this case, no 510(k) issue is involved and OC’s case officer will process the recall accordingly. On the other hand, if the firm’s recall strategy includes a correction that may alter the device, OC’s case officer will ask the appropriate ODE division to assess whether the proposed modification requires a 510(k) submission”

A flowchart is provided at the end of the document to summarize this process entitled: 510k Requirements for Proposed Fixes to Devices Undergoing Recall “

SoftwareCPR Training Courses:

Being Agile & Yet Compliant (Public)

Our SoftwareCPR unique approach to incorporating agile and lean engineering to your medical device software process training course is now open for registration!

  • Agile principles that align well with medical
  • Backlog management
  • Agile risk management
  • Incremental and iterative software development lifecycle management
  •  Frequent release management
  • And more!

3 days virtual (Zoom) with group exercises, quizzes, examples, Q&A.

Lead Instructor: Mike Russell

Next public offering: Dec 3, 4, & 5, 2024 – 12:00 pm to 5:00 pm CET

Register Now


 

IEC 62304 and other emerging standards for Medical Device and HealthIT Software

Our flagship course for preparing regulatory, quality, engineering, operations, and others for the activities and documentation expected for IEC 62304 conformance and for FDA expectations. The goal is to educate on the intent and purpose so that the participants are able to make informed decisions in the future.  Focus is not simply what the standard says, but what is meant and discuss examples and approaches one might implement to comply.  Special deep discount pricing available to FDA attendees and other regulators.

3-days onsite with group exercises, quizzes, examples, Q&A.

Instructor: Brian Pate

Next public offering:  TBD

Call or email now to schedule a private, in-house class. The fall schedule is filling up!

Email training@softwarecpr.com to request a special pre-registration discount.  Limited number of pre-registration coupons.

Registration Link:

TBD

 


 

Medical Device Cybersecurity (Public or Private)

This course takes a deep dive into the US FDA expectations for cybersecurity activities in the product development process with central focus on the cybersecurity risk analysis process. Overall approach will be tied to relevant standards and FDA guidance documentation. The course will follow the ISO 14971:2019 framework for overall structure but utilize IEC 62304, IEC 81001-5-1, and AAMI TIR57 for specific details regarding cybersecurity planning, risk characterization, threat modeling, and control strategies.

2-days onsite with group exercises, quizzes, examples, Q&A.

Instructor: Dr Peter Rech, 2nd instructor (optional)

Next public offering:  TBD

Corporate Office

15148 Springview St.
Tampa, FL 33624
USA
+1-781-721-2921
Partners located in the US (CA, FL, MA, MN, TX) and Canada.