FDA Reveals Final Mobile Health App Guidelines

Agency's tiered approach puts regulatory emphasis on high-risk apps.

Alex Kane Rudansky, Associate editor for InformationWeek Healthcare

September 23, 2013

3 Min Read

Remote Patient Monitoring: 9 Promising Technologies
Remote Patient Monitoring: 9 Promising Technologies (click image for larger view)

The Food and Drug Administration issued final guidelines for mobile health apps Monday, outlining the apps that the regulations will affect and the requirements those apps must meet to achieve FDA approval.

The FDA's tailored approach focuses on regulating apps that carry significant risks if they aren't operated correctly, such as apps intended to be used as an accessory to a regulated device or apps that transform a mobile platform into a regulated medical device.

For example, regulated apps are ones that allow a physician to make a diagnosis via smartphone or tablet, or apps that turn a smartphone into an electrocardiography machine to detect abnormal heart rhythms.

The guidelines come at a time of unprecedented growth in the mobile health app space, and a time when many developers are looking for regulatory guidance to make a successful product. President Obama signed legislation last July allowing the FDA to continue developing mobile health regulations. The guidelines were based on previous regulatory drafts.

[ Check out these mobile health apps from the government: 10 Mobile Health Apps From Uncle Sam. ]

The two categories of apps that won't be regulated are apps that aren't medical devices, and apps that might meet the definition of a medical device but pose a low risk to the public. Apps that will not be regulated include apps that:

-- help patients manage their disease or conditions without providing specific treatment;

-- provide patients with simple tools to organize and track their health information;

-- provide easy access to information related to patients' health conditions or treatments;

-- help patients document, show or communicate potential medical conditions to healthcare providers;

-- automate simple tasks for health care providers; or

-- enable patients or providers to interact with personal health record or electronic health record systems.

The regulatory criterion for whether an app qualifies as a "device" is intended use, as revealed by labeling claims, advertising materials or statements by manufacturers. The app is considered a "device" if its intention is to diagnose, treat or prevent disease, or affect the function of the body.

Apps that are an extension of medical devices, such as the remote display of data from bedside monitors or the display of medical images, are subject to regulation.

Class I, or low-risk, apps must include adequate design controls, registration, device listing, adverse event reporting, and corrections and removals. These apps are used as a secondary display to a regulated medical device and are not intended to provide primary diagnosis or treatment decisions. Class II requires more specific control and Class III requires pre-market approval.

The FDA has cleared about 100 medical apps over the past decade, with about 40 of those cleared in the past two years.

"Some mobile apps carry minimal risks to consumers or patients, but others can carry significant risks if they do not operate correctly," said Jeffrey Shuren, director of the FDA's Center for Devices and Radiological Health. "The FDA's tailored policy protects patients while encouraging innovation."

About the Author(s)

Alex Kane Rudansky

Associate editor for InformationWeek Healthcare

Alex Kane Rudansky is an associate editor for InformationWeek Healthcare. Her work has appeared in The Washington Post, the Chicago Sun-Times, The Boston Globe and The Miami Herald, among others. She is a graduate of Northwestern University's Medill School of Journalism.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights