The Case for Remote Medical Device Programming

With the recent reports of hacking ICD's, especially when a skilled set of engineers stand within six inches of the device, we can see the next Tom Clancy story line:

"A famous head of state, lounging in the comfort of his home, suddenly is afflicted with a series of shocks from his defibrillator, then collapses to the floor. His aides, uncertain what just happen, attempt to revive him, to no avail. Meanwhile, in a country far, far away, the terrorists are exchanging high fives..."

These threats, as we can clearly see, are a Clear and Present Danger. (I know, not very original, but you get the drift.)

Not that security isn't important, it is. But should it be a show-stopper to innovation as we attempt to deliver care to our burgeoning patient population in the years ahead?

The reality on the ground is that doctors should have the ability to make adjustments to certain ICD programmed features remotely. The reality on the ground is that already we have non-medical personnel programming devices - even turning them off.

These devices need continuous follow-up, and a lot of it. For every device implanted, I would estimate that there are four times the number of patient visits made for these devices to a doctor's office that for patients without devices. Is this on-site follow-up burden sustainable? Currently, entire clinics are manned full-time by device nurses to manage the volume. Even with these clinics, devices must to reprogrammed at other times, like just before and after surgery, or de-activated when people reach the end of their life. With cost constraints limiting the number of personnel available for device management, we simply not have the number of individuals at all the geographic sites necessary to reprogram devices in person. So we've turned to industry representatives who hold no medical degree to make changes to programmed parameters on our behalf, many of which go undocumented. Physicians "oversee" these adjustments, of course (someone has to be legally responsible, right?), but the reality is is that people with medical degrees are not always the ones out there pushing the buttons.

This issue will only grow more dire as the baby boomers age and the number of devices continues to grow as we push to keep patients out of the hospital. For these reasons, and reasons of legal accountability, I foresee that the need for remote programming of devices will be all but inevitable.

And this isn't just for cardiac devices. Insulin pumps, neural stimulators, and a whole host of new innovative implantable devices will also need follow-up after their implantations.

Certainly, secure interlocks can be developed to assure safe remote reprogrammings - maybe even patient-and-physician hand-shake protocols, for instance. But in this era of increasingly wired health care delivery there should be no reason the FDA, in a brief moment of clarity, should discourage the development of carefully-developed protocols to modify device settings remotely.

What the heck are we waiting for?

-Wes