Internet of Things
IoT Viewpoints explore the IoT opportunity in 2018 and beyond. Download our latest e-book to get our newest collection of thought leadership articles on the emerging IoT trends, technologies and opportunities.
In February 2015, the US Food and Drug Administration (FDA) issued a regulatory update for mobile medical applications to replace its earlier guidance issued in 2013. The update was overdue, considering the explosion in the number of mobile devices and applications since 2013. Much to the relief of health tech developers, the FDA has taken the practical approach of enforcing its regulatory oversight only for mobile apps that qualify as medical devices. In other words, the FDA distinguishes between functionality and platform, which determines whether a mobile application qualifies as a medical device.
This move is significant, as the new guidance exempts smartphones and tablets as long as the apps used on these devices do not perform medical device functions. However, the FDA will use its discretion to regulate functionalities that could pose a risk to patients if they fail to function as intended. The guidance here fails to draw a clear boundary between regulated apps, unregulated apps, and apps for which the FDA will exercise “enforcement discretion.”
The guidance is generally deregulatory, and it indicates that the FDA is focused on reducing the classification of, or exempting, mobile devices and applications that do not pose a risk to patient safety. It is a positive step, considering that it deals with a challenging subject with broad implications. The FDA has provided a large number of app examples, although the list is not exhaustive. More importantly, the agency is committed to addressing questions on uncertain areas such as apps under enforcement discretion, which will result in future updates. Examples of mobile devices and apps that will not warrant regulatory oversight are smartphones, tablets, apps used for tracking health metrics, health and wellness apps, and mobile platforms developed for population health management.
Although the FDA has provided a large number of app examples, the guidance lacks a clear framework to differentiate between unregulated apps, regulated apps, and apps for which it will exercise enforcement discretion. This will lead to uncertainties and result in contradicting interpretations by vendors. The FDA could rapidly increase the number of app categories for which it exercises enforcement discretion, which means vendors have to decide whether or not to incur the ongoing costs of supporting enforcement-discretion-related quality systems. The guidance also lacks clarity on whether mobile apps for clinical decision support and interoperability will qualify as medical devices.
The new guidance provides the industry and the FDA with a good starting point for discussions, and it reduces baseline uncertainties and inconsistencies that existed prior to the update. Although there are some pain points related to the application of the guidance in key areas such as clinical decision support, interoperability, and accessory policies, which need to be resolved, the industry is better off with the guidance than without it.
“FDA clearance of Dexcom’s continuous glucose monitoring mobile apps should strengthen its position,” IT0011-000346 (January 2015)
“FDA medical mobile app regulation will create challenges for developers,” IT011-000217 (August 2011)
Srikanth Venkataraman, Analyst, Healthcare Technology
Service Provider Markets
ByMike Roberts 01 Oct 2018
Verizon 5G Home is a milestone in the telecoms market because it is the first large-scale commercial launch of broadband services based on 5G technologies, albeit not on a fully standardized version of those technologies.
ByEvan Kirchheimer 26 Apr 2018
Service provider interest in justifying 5G investment through its potential to open new revenue streams from the enterprise segment is growing ever greater.
Europe, Middle East & Africa team - +44 (0) 207 017 7700
Asia-Pacific team - +61 (0)3 960 16700
US team - +1 646 957 8878
Already an Ovum client? Login to the Knowledge Center now