United States: Health Hackers: Problems In Applying Traditional Products Liability Theories To Latent Cyber-Vulnerabilities In Medical Devices

Last Updated: October 21 2015
Article by M. Ryder Lee

October is National Cyber Security Awareness Month (yes, that's a thing), so it seems fitting to write about an unprecedented alert recently released by the FDA to health care providers that warned of a medical device's vulnerability to cyber-attack. The subject device was a now-discontinued infusion pump system made by Hospira that was capable of communicating with the health care provider's network. As such – by definition, really – it could be hacked (though evidently with greater ease than usual here). Interestingly, though, the FDA warning read a lot like an FDA response to a verified product defect. Perhaps that makes sense. But should cyber-security vulnerabilities really be treated the same as design defects under traditional products liability law? While government-issued medical-device security standards from FDA and Department of Homeland Security appear inevitable and necessary, cyber-vulnerabilities seem distinguishable from conventional design defects in the medical products liability context for several reasons.

First, regardless of the plaintiff's theory of liability, the entire cause of action against the device manufacturer would be predicated on a targeted intentional tort committed by a third party. In fact, the cyber-attack giving rise to the claim would also constitute a criminal act in most cases. But if not pursued or prosecuted by law enforcement, it is very unlikely that the parties to any litigation arising out of the act will have the resources or sophistication to identify the hacker. From a causation standpoint, then, this unnamed but clearly-at-fault party is the elephant in any jury room.

Second, even if a device has its own firewall, security key or other built-in feature, in theory those measures could all be circumvented by an authenticated user on the health care provider's network. So if a hospital's main network were to be compromised by a hacker masked as a user authorized to access the device, the device's self-contained security apparatuses may be moot anyway. In a defective design suit that followed such an incident, liability would therefore need to be apportioned between: 1) the health care provider under a negligence or malpractice theory for failing to maintain a secure network; 2) the device manufacturer under a strict-liability or negligence theory, and 3) the hacker. That comparative fault schema becomes even more convoluted where the patient's device is communicating to a health care provider via a mobile wireless carrier or via the patient's home network (which may be unsecured altogether).

In addition to these difficult design defect issues, an injured medical device plaintiff will almost certainly throw in a failure-to-warn claim against the manufacturer as well; which begs the related questions of who has that duty to warn of a cyber-vulnerability and how the learned intermediary doctrine factors in as a defense. Most of these devices are not marketed directly to the public. So are the physicians supposed to be the learned intermediaries for relaying this new species of risk? I hope not: I know some superb physicians who can't set up email on their iPhones, much less assess and explain to a patient the potential risk of a cyber-attack on a networked procedure or device. That's just not necessarily in a physician's skill set. I suppose the hospital's IT staff could always visit the patient as the "learned intermediary" to assess the risk and give the option of an air-gapped or offline procedure (if that's even possible) to take some heat off the manufacturer. But regardless of who is deemed competent to give an informed warning here, any given risk analysis is inherently arbitrary and speculative because the occurrence of the adverse event depends entirely on the intentional tort (and, likely, sophistication) of a third-party malicious hacker.

Finally, there is the glaring question of whether the gravity of this particular threat really warrants the magnitude of the response and the cost to the both the public and private sectors. While extra-stringent cyber-security precautions might be practical for patients who require personal security in general (such as high-ranking government officials, dignitaries, or others subject to a specific personal threat), the average patient is generally not a target. And, as a whole, it's probably safe to say that the sick and infirm are not a top-priority population for this kind of terroristic activity. So, other than imposing some basic government-issued standards for user-authentication and firewalls on all networked medical devices, would the benefits of heightened security measures beyond that really justify the costs? Consider this question not only from a common-sense policy standpoint, but from the standpoint of a jury performing a risk-benefit analysis in a traditional design defect claim. Would the state of the art require that every networked device be implemented with hardware-based security measures (e.g., data diodes) as if it were part of a critical infrastructure network like the bulk-power grid or military defense systems? And at what point would the manufacturer's liability be measured in this context? Network and device security standards can evolve quickly; so a device that was perfectly secure at the time of manufacture and that is otherwise still useful in saving lives might be junked because its processor or physical memory can't handle the new firmware update or software security patch. And what if the required update can be installed, but doing so may tax the device's core CPU to the point of potential hardware failure? The point is that the monetary and transactional costs of disproportionately high cyber-security standards for networked medical devices will often outweigh the benefits, especially in light of the slight risk of a targeted attack.

So what's the solution? If traditional design-defect-type responsibility does ultimately rest with the manufacturer under strict liability, then the liability question should begin and end with the manufacturer's compliance with published FDA and DHS security standards at the time of manufacture. Manufacturers might also be required to initially disclose the expected capabilities of the device's hardware to handle any future security software and firmware upgrades that might be required. This limitation on strict products liability makes sense because it encompasses the scope of the manufacturer's control over the device. As for further liability under theories sounding in negligence, the government-published regulations should serve to establish a bright-line standard of care for both manufacturers and defendant health care providers for actions claiming inadequate cyber-security leading to harm. To remain compliant and avoid liability, the manufacturers should only be required to develop and issue software security updates as necessary to meet the minimum published standards (up to the device's maximum capability) and the health care providers would undertake the sole duty of implementing them within a reasonable set period of time. Any higher (or murkier) bar would seem to be untenable in this arena, as inclined hackers will likely find a workaround to the newest government standards as soon as (if not before) they are even published.

And one last thought on the semantics at play here with regard to patient warnings. The putative warning: "it's possible that a hacker could infect your device" – when said to a particularly tech-illiterate patient who only associates the word "hack" with its machete or meat-cleaver meaning in the traditional vernacular context, and the word "infect" with its associative meaning in the immediate medical context – might be cause for undue alarm. Arguably, though, these two contexts are analogous from a legal and proximate cause standpoint: that is, whether a malicious third-party actor manipulates a medical device from a coffee shop in Jakarta vis-à-vis the Internet, or he physically gains unauthorized access to a hospital room in Springfield to manually sabotage a device, the legal effect of either act to a regulatory-compliant manufacturer should be the same...no liability.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.