Washington signals possible FDA regulation of mHealth

By: Brian Dolan | Feb 26, 2010        

Tags: | | | |  |

First, when electronic stuff directly impacts health, the folks at White Oak get interested. It’s really that simple. They take the public health very seriously, and any IT people new to the health industry need to appreciate that.

Second, when confronted by a situation such as this, FDA’s natural reaction is to interpret the scope of their authority very broadly, and then propose a tiered approach based on risk. So they want everything in the tent, but once in the tent they’re willing to make distinctions. A lot of people back in 2008 thought FDA’s proposed regulation on Medical Device Data Systems was expansive, but Dr. Shuren’s declaration that HIT software is a medical device is orders of magnitude broader in scope.

Third, FDA is not deterred simply because a regulatory task is complex or the technology is important to the point where speedy innovation is desirable. If that were the case, FDA would’ve abandoned regulating pacemakers long ago. Actually, high complexity and high public-health importance are archetypal circumstances for FDA to get involved.

Fourth, prior to yesterday, our orientation was to think about traditional medical devices as the stuff that touches the patient, and then to believe that the software and hardware that moves farther and farther away from that patient contact is less likely to be regulated. But the conclusion that FDA can even regulate the electronic health record (in many cases the point farthest from the patient) means that we now need to rethink the agency’s view on all the stuff that connects those two points. We must think about the various hardware and software tools used for the communication between those elements.

Fifth, from there, it is a short hop to looking at the hardware and software that typifies mHealth applications. If the sensor that collects the data from the patient is a medical device, which we always knew if the use was medical, and if the EHR that is the ultimate repository of that information might also be a regulated medical device, we need to seriously think about whether FDA intends to regulate cell phones that are anything other than generic communication instruments. In my first article, I described how FDA might indeed regulate cell phones based on the claims made about them. That was theory, which now seems more likely to materialize as reality. As I did in that article, I would argue that a phone for which the seller makes no special medical claims is not a medical device in the hands of that seller. But any move toward suggesting that the phone is a specialized tool useful for medical communication apparently means FDA might get interested.

Sixth, frankly I interpret Dr. Shuren’s comments as the beginning of a conversation. I did not hear him dogmatically say what the future will look like. Quite the opposite, I heard him reaching out to stakeholders for input. While he was fairly emphatic on the point that these software products are within their legal authority, he was expressly inviting comments on the degree of regulation required. I did hear him put a stake in the ground on the issue that something should be done, and I think industry needs to respond. The FDA public meeting on interoperability held during the last week of January similarly showed a willingness by FDA to collaboratively discuss the best approach.

And seventh, however the HIT and mHealth industries respond, as with anyone who participates in the health industry, the approach will need to meet one critical criterion. As a wise, old food and drug attorney once told me (please don’t tell my Dad I called him “old”), it all starts and ends with concern for the patient. Whatever approach emerges, whether it’s FDA regulation or a voluntary industry code that allows for self-regulation, it needs to have as its essence a focus on protecting the patient.

In my last article in this series, I will offer some views on specifically where I think the regulatory environment is going for mHealth. But before I get there, my next article will focus on FDA’s relationship with hospitals and other users of the technology. I’ll be examining what discretion users have to modify the stuff they buy. Hopefully you’ll find it useful.

Navigation: ( ←Previous | 1 2 3 | Next→ )

  • http://mhealthnews.wordpress.com/2010/03/01/washington-signals-possible-fda-regulation-of-mhealth/ Washington signals possible FDA regulation of mHealth « mHealth News Summary
  • http://www.telecareaware.com/ Steve Hards

    Bradley,

    I read this, and your previous article with interest and have referred them to several people. Especially for device manufacturers in the UK unfamiliar with the FDA and its approach, but who may have to deal with it, the explanations are clear and helpful. Is there any chance that when the series is complete Wireless Health will publish them all together as an ebook? I’d love to be able to direct Telecare Aware readers to it.

    Regards,
    Steve

  • http://mobihealthnews.com Brian Dolan

    Hi Steve,

    Bradley and the MobiHealthNews team have already discussed that and plan to republish the series as a downloadable PDF report or eBook as you described it. Look for it in the coming months!

    Brian

  • http://www.healthcare311.com Greg Judd

    Here’s hoping Brad means it when he says, in item 7 of his 7 observations,

    …it all starts and ends with concern for the patient. Whatever approach emerges, whether it’s FDA regulation or a voluntary industry code that allows for self-regulation, it needs to have as its essence a focus on protecting the patient.

    (my emphases)

    Why? Because people are people first, and only then, and not continuously in most cases, patients. So FDA regs dealing with, say, cellphones, will need to be particularly flexible to contend with users’ transitory statuses.

    And no, I do not anticipate that that will be easy :-)

  • jamadan

    Why would cellphones that receive and display medical data be considered a medical device any more than the Dell or HP Desktop is today? Does the FDA want to go back to the day where HIT vendors have branded, dedicated hardware (desktops and servers) that costs 10 times what it should in order to pass the FDA audit? Regulating software makes sense to me, because that’s where the logic is. But regulating hardware will drive up costs and drive out competitors. Not sure anyone really wants it or that it’s necessary from a patient safety perspective.

  • http://mobihealthnews.com/7322/will-the-fda-regulate-mhealth-care-providers/ Will the FDA regulate mHealth care providers? | mobihealthnews

    [...] and provided some background on what the regulatory framework looks like. In my last article, I noted that recent activity at FDA suggests the agency is preparing to expand its scope to most areas of HIT, and by implication into [...]

  • http://healthcare.zdnet.com/?p=3669 How will the FDA regulate health IT? | ZDNet

    [...] CompassX Group of Irvine, Calif. told the AMA a regulated device will cost three times more than an unregulated one to develop. The estimate seems reasonable. But pre-approval does not appear to be what Jeffrey Shuren (above, from the FDA), who heads the FDA’s device regulation unit, is looking at. [...]

  • http://mobihealthnews.com/8358/update-mhealth-regulatory-coalitions-first-meeting/ Update: mHealth Regulatory Coalition’s first meeting | mobihealthnews

    [...] 3. Software. FDA has a term for certain software called “standalone” software, which is software that is not acting as an accessory to the device. Part of this discussion is included in the MDDS proposal — systems of systems — that the FDA never made a final ruling on. The group is going to try to come up with an appropriate approach for which software gets regulated and what doesn’t. (more on FDA regulation of software) [...]