Bradley Merrill Thompson, a Member of the Firm in the Health Care and Life Sciences practice, in the Washington, DC, office, was quoted in an article titled "mHealth Oversight Suggestions Nearing End of the Beginning."

Following is an excerpt:

The long and winding road to federal regulation or oversight of mHealth still has some ground to cover, but a key Food and Drug Administration Safety Innovation Act sub-workgroup has tentative suggestions that are about three organizational layers removed from the FDA.

After a July 19 meeting, the FDSIA subgroup on regulations is sending a batch of tentative recommendations to the FDSIA Workgroup for consideration on the last Friday of July — before those and other ideas go to the ONC's HIT Policy Committee and then the FDA.

The issues being considered by the regulation subgroup — chaired by Epstein Becker Green attorney Bradley Thompson and Partners HealthCare System's biomedical engineering director Julian Goldman, MD — have been so complex and potentially impactful to the blossoming mHealth industry, that the exact language of recommendations are still being finalized amid subgroup member debate.

Tentatively, though, as Thompson said, HIT and mHealth "should not be subjected to FDA pre-market requirements," except "those areas where it would potentially justify premarket requirements."

Those exceptions, as most of the subgroup agreed to, would be medical device data systems (which the FDA subjects to low-risk Class 1 regulation requiring mostly just registration and adverse event reporting), medical device accessories that could be added to smartphones say for diagnostic uses, and "certain forms of high risk" clinical decision support software or apps.

That suggestion is generally following a recommendation by the FDASIA taxonomy subgroup — to classify all of mHealth and HIT as "unregulated" by the FDA but subject to "enforcement discretion," with those several exceptions.

From a legal perspective, though, some members had qualms about how the "unregulated" and "discretion" portions of the suggestions would be worded.

But, as Thompson said, the charter of the FDASIA Workgroup and its subgroups is "not to design the regulatory system but to define the objectives that the agencies should consider when they design the regulatory system in the fall."

If the legal questions get so murky, it could be the federal courts determining the FDA's regulatory scope of HIT, Thompson said. "But we can determine oversight," he said, per Congress's instructions in the Food and Drug Administration Safety Innovation Act, enacted last July. "The ultimate question is should the FDA actively oversee HIT?"

Jump to Page

Privacy Preference Center

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.

Strictly Necessary Cookies

These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.