The US government’s Health Information Technology (HIT) Committee of the Office of the National Coordinator (ONC) has called on the US Food and Drug Administration (FDA) to work within its current regulatory frameworks to help spur the innovation of mobile health technologies, rejecting calls for an overhaul of current regulations.
As reported by Regulatory Focus, ONC’s report was specifically called for by the 2012 FDA Safety and Innovation Act, which called for a report to “offer a proposed strategy and recommendations for an appropriate risk-based Health IT regulatory framework that would include mobile medical applications and promotes innovation, protects patient safety, and avoids regulatory duplication.”
To facilitate the development of that report, FDA has been working with ONC and FCC in the form of a new group called the FDASIA Workgroup to assist ONC’s Health Information Technology (HIT) Policy Committee to provide recommendations.
ONC’s HIT is working to generate a proposal regarding the future of mobile health technologies, which are notably regulated by not one but three federal entities: FDA, ONC and the US Federal Communication Commission (FCC).
The overarching goal is to simplify this regulatory paradigm such that companies understand which agency’s requirements they will be expected to meet and how they can expect to meet them when they want to bring a new product to market.
ONC’s report was specifically called for by the 2012 FDA Safety and Innovation Act, which called for a report to “offer a proposed strategy and recommendations for an appropriate risk-based Health IT regulatory framework that would include mobile medical applications and promotes innovation, protects patient safety, and avoids regulatory duplication.”
Regulatory Focus notes three key areas related to these recommendations:
First, according to Federal Register notices, there are three types of recommendations:
- types of risk that may be posed by health IT that impact patient safety, the likelihood that these risks will be realized, and the impact of these considerations on a risk-based approach;
- factors or approaches that could be included in a risk-based regulatory approach for health IT that also promotes innovation and protect patient safety;
- approaches to avoid duplicative or overlapping regulatory requirements
Second, on September 4, 2013, the ONC group released a set of its recommendations. One report by its regulations subgroup broadly covered three main points:
- FDA can use its current regulatory framework to “clarify ambiguities” by establishing clear policies for how it would exempt lowest-risk HIT products and most Class I medical devices, exempting most HIT from good manufacturing practice regulations under 21 CFR 820, expedite guidance on mobile medical applications and other HIT, and educate the public on requirements.
- Agencies—FDA, FCC and ONC in particular—should do their best to work together to delineate authority and eliminate duplicity. Review processes should, to the extent possible, be coordinated.
- New frameworks should be considered, particularly for adverse event reporting, data gathering and industry self-regulation. ONC said models like the National Highway Traffic Safety Administration and the Aviation Safety Reporting System might be useful for reporting adverse events to ensure more timely reporting and better safety and performance data.
Third, in addition, the ONC report says that FDA needs to address four “main” issues now facing mobile health technologies:
- There is no clear distinction between general wellness and disease-related claims, particularly with respect to weight-related claims and obesity.
- Because many mobile devices come with accessories, FDA needs to define levels of risk for these accessories and determine which are worth regulating and which are worthy of enforcement discretion.
- Clinical support decision software needs to have a clear regulatory paradigm, as the agency “has never been clear on the contours of its regulation for this broad category of general health and medical software” despite many such devices being of low risk to patients.
- Some software is modular, and is intended to be used with other products. ONC said FDA needs to determine which modules are devices and which are simply general modules able to be incorporated into health-related software.
The Regulatory Focus story concludes: “Elsewhere in its report, the HIT Committee said FDA’s device regulations could be improved to clarify the regulatory considerations that come into effect when medical software is used on general devices, such as smartphones. Last year, legislators publicly pressed FDA to state if it believed smartphones would be regulated by the agency if they ran medical device software. FDA rejected that it would, though it considered that problems could occur if the software and device did not work properly together.
ONC also said that the FDA regulatory process is not well defined or easy to understand, and that more public outreach would be useful in educating stakeholders, many of whom have no prior experience in the regulated healthcare products space.”