FDA Issues Guidelines On Wireless Medical Devices - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

03:54 PM

FDA Issues Guidelines On Wireless Medical Devices

FDA outlines risks such as lost signals and recommends stringent security measures -- but document is not the last regulatory word.

Remote Patient Monitoring: 9 Promising Technologies
Remote Patient Monitoring: 9 Promising Technologies
(click image for larger view)
The Food and Drug Administration (FDA) has released final guidelines on the design, testing and use of radio-frequency (RF) wireless medical devices. Although it doesn't promulgate legally enforceable responsibilities, the document is intended to guide both device manufacturers and healthcare providers toward the safe and secure use of wireless medical devices. Covered are devices "that are implanted, worn on the body or other external wireless medical devices intended for use in hospitals, homes, clinics, clinical laboratories, and blood establishments."

The FDA document has no relation to the impending guidance from the agency about how it will regulate apps that turn smartphones and tablets into medical devices. In fact, the draft guidance on RF wireless devices was issued in 2007, before smartphones and tablets became a factor in the industry. The FDA is focusing on the safety aspects of medical devices in hospitals, homes and other fixed-care settings.

[ What's coming in wearable devices? Read 10 Wearable Health Tech Devices To Watch. ]

For example, the guidance states, "Because there are risks associated with RF wireless systems, we recommend that you carefully consider which device functions should be made wireless and which device functions should employ wired connectivity." Among the issues that could compromise transmissions from wireless devices and potentially endanger patient safety, the FDA guidance says, are:

-- Poorly used wireless networks.

-- Lost, corrupted, or time-delayed transmissions.

-- Degradations in wireless transmissions that might be caused by competing wireless signals or electromagnetic interference.

-- Lack or compromise of wireless security.

-- Potential misuse of wireless devices because of lack of or inadequate instructions for use.

The document cautions that although a cellular phone network might be adequate for voice communication, "it might not be sufficient for certain medical functions. Connections lost without warning, failure to establish connections, or degradation of service can have serious consequences, especially when the medical device relies heavily on the wireless connection. Such situations can compromise the wireless transmission of high-priority medical device alarms, time-sensitive continuous physiological waveform data, and real-time control of therapeutic medical devices (such as wireless footswitches)."

The FDA document also addresses the security of wireless signals and data from medical devices. Wireless transmissions should be encrypted to safeguard not only the data but also hospital information systems, it says. Among the areas of vulnerability, it warns, are Bluetooth communications between devices and wireless networks.

The guidelines don't discuss the issue of hackers trying to take control of implanted devices such as pacemakers and defibrillators. Fears of that kind of cybercrime --which, so far, have proved baseless -- were sparked by a letter that the Information Security and Privacy Advisory Board, which advises the National Institute of Standards and Technology (NIST), sent to government agencies last year. The board suggested that FDA take this kind of threat into account in its regulation of monitoring devices.

The FDA statement also makes several "recommendations for premarket submissions for devices that incorporate RF wireless technology." The agency suggests how manufacturers should describe wireless devices in submissions to the FDA and directs them to provide information about any "risks and potential performance issues" associated with a device's wireless functions. In addition, the FDA wants device makers to describe the testing of their products for the range of risks described in the guidance.

The FDA notes that the Federal Communications Commission (FCC) also regulates wireless technology, so jumping through the FDA's hoops might not be sufficient to obtain approval for wireless medical devices.

Last September, for example, the FCC released its final rule for medical body-area networks (MBANs), which include wearable monitors that send data to wireless hubs in hospitals. The FCC allocated certain portions of the radio frequency band to MBANs, one for indoor and another for outdoor use.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
8/19/2013 | 11:12:45 PM
re: FDA Issues Guidelines On Wireless Medical Devices
I read the article regarding the threat of hackers on these sorts of wireless medical devices, and have to say its pretty scary. I am actually surprised that these guidelines dont focus that much on wireless security as that could be a potentially big aspect regarding wireless communication between devices. Not only is the access to these wireless devices a concern, but also the data that can be collected and where it is stored.

Jay Simmons
Information Week Contributor
10 Trends Accelerating Edge Computing
Cynthia Harvey, Freelance Journalist, InformationWeek,  10/8/2020
Is Cloud Migration a Path to Carbon Footprint Reduction?
Joao-Pierre S. Ruth, Senior Writer,  10/5/2020
IT Spending, Priorities, Projects: What's Ahead in 2021
Jessica Davis, Senior Editor, Enterprise Apps,  10/2/2020
White Papers
Register for InformationWeek Newsletters
2020 State of DevOps Report
2020 State of DevOps Report
Download this report today to learn more about the key tools and technologies being utilized, and how organizations deal with the cultural and process changes that DevOps brings. The report also examines the barriers organizations face, as well as the rewards from DevOps including faster application delivery, higher quality products, and quicker recovery from errors in production.
Current Issue
[Special Report] Edge Computing: An IT Platform for the New Enterprise
Edge computing is poised to make a major splash within the next generation of corporate IT architectures. Here's what you need to know!
Flash Poll