The FDA recently issued a draft guidance titled “Deciding When to Submit a 510(k) for a Change to an Existing Device.” At the same time, the FDA issued a similarly titled draft guidance addressing how to decide when to file a 510(k) for modifications to the software of existing devices.
Regular readers of these Alerts may recall that in 2011 the FDA issued a draft guidance as an update to its 1997 guidance on the same topics. The 2011 version created such an uproar that, in the FDA Safety and Innovation Act, Congress ordered the FDA to withdraw it and start over. The FDA states that this latest iteration “preserves the basic format and content of the  original [version], with updates to add clarity.”
Modifications to Existing Devices
The draft guidance documents are intended to “aid manufacturers of medical devices subject to premarket notification requirements who intend to modify a 510(k)-cleared device or a pre-amendments device subject to 510(k) (also referred to together as “existing devices”) during the process of deciding whether the modification exceeds the regulatory threshold of 21 CFR 807.81(a)(3) for submission and clearance of a new 510(k).”
The draft guidance on modifications to existing devices spans 73 pages and regulatory professionals at device companies will need to become intimately familiar with most, if not all, of it. The gist, however, is presented in the following five flowcharts from the FDA draft guidance:
Figure 1 – Main Flowchart
Figure 2 – Flowchart A
Figure 3 - Flowchart B
Figure 4 - Flowchart C
Figure 5 - Flowchart D
Note that the charts interrelate to a certain extent; i.e., they are not stand-alone charts. A copy of the draft guidance, containing the full-size charts, can be found here.
When Modifications to Software Require a New 510(k)
The draft guidance issued on software changes defines “software” as “the set of electronic instructions used to control the actions or output of a medical device, to provide input to or output from a medical device, or to provide the actions of a medical device.” The draft guidance spans 32 pages, but the heart of it is presented in the following flow chart:
For example, the chart shows that if a change is made solely to strengthen cybersecurity, the manufacturer has to document the reasons for its decision but does not have to file a new 510(k). Conversely, if the software is modified and introduces a new cause of a hazardous situation that could result in significant harm and this is not effectively mitigated by the most recently cleared device, then the manufacturer must file a new 510(k).
A copy of the draft guidance on software changes can be found here.
The FDA has scheduled a webinar on August 25 to discuss both draft guidance documents (Registration is not necessary). The information to access the webinar is:
Date: August 25, 2016
Time: 1:00-2:30 p.m., Eastern Time.
NOTE: You must dial-in to hear the presentation and ask questions:
Dial: 888-606-7035, passcode: 6372193
International Callers Dial: 1-517-308-9367
View the slide presentation during the webinar
Conference Number: PW8727223
For more information, please contact the Barnes & Thornburg LLP attorney with whom you work or one of the following attorneys in the firm’s Food, Drug & Device Group: Lynn Tyler at (317) 231-7392 or firstname.lastname@example.org; or Alicia Raines Barrs at (317) 231-7398 or email@example.com.
Visit us online at www.btlaw.com/food-drug-and-device-law-practices.
© 2016 Barnes & Thornburg LLP. All Rights Reserved. This page, and all information on it, is proprietary and the property of Barnes & Thornburg LLP. It may not be reproduced, in any form, without the express written consent of Barnes & Thornburg LLP.
This Barnes & Thornburg LLP publication should not be construed as legal advice or legal opinion on any specific facts or circumstances. The contents are intended for general informational purposes only, and you are urged to consult your own lawyer on any specific legal questions you may have concerning your situation.
Visit us online at www.btlaw.com and follow us on Twitter @BTLawNews.