Featured Product
This Week in Quality Digest Live
FDA Compliance Features
Graham Freeman
What can we learn from the organizational cultures of different industries?
Dirk Dusharme @ Quality Digest
In this episode: China trade and a demo of web-based management system software
Mike Richman
Three great guests
Dirk Dusharme @ Quality Digest
ISO vs. FDA audits, Baldrige winners, and what we can learn from GE
Ryan E. Day
How BioBridge Global leverages a digital QMS in the heavily regulated world of regenerative medicines

More Features

FDA Compliance News
Creates adaptive system for managing product development and post-market quality for devices with software elements
VQIP allows for expedited review and importation for approved applicants that demonstrate safe supply chains
An invite from Alcon Laboratories
Intended to harmonize domestic and international requirements
The FDA wants medical device manufactures to succeed, new technologies in supply chain managment
Pharma quality teams will have performance-oriented objectives as well as regulatory compliance goals
Strategic investment positions EtQ to accelerate innovation efforts and growth strategy
The FDA’s RMAT designation goes live

More News

Russ King

FDA Compliance

FDA’s 510(k) Guidance Emphasizes Software-as-Device Factor

New guidance is more specific about acceptance criteria for software

Published: Thursday, September 24, 2015 - 11:15

The path to medical device commercialization requires FDA approval, which most often means filing a premarketing notification, also known as a 510(k). The FDA has specific criteria for accepting a 510(k), and it just released its new acceptance policy. This new standard, which will be effective Oct. 1, 2015, replaces the old FDA Refuse to Accept Policy for 510(k) Guidance of 2012.

The purpose of this guidance is to explain the FDA’s procedures and criteria in assessing whether a 510(k) submission meets a minimum threshold of acceptability and should be accepted for further review. Using the premarket notification, or 510(k) process, the FDA evaluates whether the submission demonstrates substantial equivalence to a predicate device and that the device is as safe and effective as its predicate.

Interestingly, the old 2012 Guidance mentions “software” only 18 times. The new 2015 Guidance uses the word “software” 33 times. Additionally, the new guidance is more specific about the acceptance criteria for software. There is now an entire section (section H) dedicated specifically to device software. This section covers:
• Whether the device includes software or firmware
• Whether the device requires software or firmware
• The level of concern created by the software
• Software documentation based on the level of concern as described in Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices

In only three years’ time, the new guidance has dramatically increased its focus on software, indicating the FDA’s growing concerns around medical device software. As the FDA gets a handle on software-dependent medical devices, manufacturers will be faced with a quality framework that addresses FDA’s concerns. We’re already seeing this with 21 CFR Part 11, IEC 60601-1, PEMs, and IEC 62304. I foresee additional regulations emerging as the FDA further seeks to meet the challenges of software as a medical device, increased communications between hospital networks and devices, devices that increasingly rely on software for Basic Safety and Essential Performance, and the constantly growing challenges to cybersecurity.

Keeping a finger on the pulse of these changing regulations is going to be critical. What potential challenges do you see as the industry becomes more technology dependent? Comment below or feel free to email me directly at rking@methodsense.com.

First published Sept. 14, 2015, on the AssurX blog.

Discuss

About The Author

Russ King’s picture

Russ King

Russ King is president of Methodsense, a consulting firm that helps clients deliver medical and technological breakthroughs by effectively meeting the requirements needed to bring their products to market.