Despite 510(k) Software Guidance, US FDA's Hands May Still Be Tied
Executive Summary
While a recent final guidance when a 510(k) is needed for software changes is helpful, a key industry lobbyist says it doesn't do enough to address the bigger issue of allowing FDA more discretion to let software medical device-makers update their products quickly without burdensome agency oversight.
You may also be interested in...
US FDA Pilot Program Speeds Off-The-Shelf Software Validation
The Computer System Validation pilot program is exploring ways for device manufacturers to save time in implementing new information technology tools that support quality systems and other operational functions. One strategy under review: letting companies rely on software manufacturers’ own validation for low-risk functions. Also: A quality assurance manager at device-maker Zoll Medical weighs in on his company's participation in the pilot.
Global Medtech Guidance Tracker: October-November 2017
Stay current on regulatory guidelines from around the world with Medtech Insight's Guidance Tracker. Forty-four new guidance documents were posted to the tracker since its last update.
510(k) Modifications Guidance Shows FDA Focus On Least- Burdensome Principle, Routine Risk Tests
A final 510(k) modifications guidance released from US FDA contains at least nine changes in emphasis from an August 2016 proposal. It enunciates the agency's plan to abide by "the least burdensome principle" in evaluating sponsors submissions for changes, and it recommends that any decision by a company not to submit a new 510(k) after a device alteration be routinely verified and validated.