United States: Clinical Trials Part II: Privacy, Cybersecurity Risks, And Managing ePHI

The ongoing digitization of the drug and medical device industries continues, and, as a result, new considerations have come to the forefront for companies engaged in clinical trials. In Part 1 of this series, we described a new set of clinical trial registration and result reporting requirements the FDA is imposing as of 2018. These new requirements follow on the heels of, and go hand in hand with, a number of guidance documents issued by the agency on data privacy protections and security breaches, which this Part II will address.

Ultimately, there is a significant level of risk to sponsors of clinical trials related to the security of the data they possess. Health care entities are a primary focus of cybersecurity hackers on a yearly basis, with recent studies showing that health care entities account for a vast majority of ransomware attacks. This translates into a risk to clinical trial sites, typically hospitals and doctors' offices, and, therefore, accounting for this risk in the trial design should be a primary focus.

Although the FDA has become increasingly focused on data protection and cybersecurity risk, it has yet to address these concerns directly in the context of clinical trials. Clinical trial sponsors and sites can learn from the documents that the FDA has created on the issue of data security and cybersecurity risks. These documents to date are generally directed at software manufacturers and developers where the software is used in a health care setting and will process patient data. In many instances, these guidance documents address themselves to the software, which drives and is used in medical devices. However, the overriding concern of the FDA's take on data privacy/security and cybersecurity risks, although not directly pointing to clinical trials, is very relevant to the trials, patient data security and the risk exposure to sites and sponsors.

Finally, the risks to clinical trial sponsors and trial locations includes the potential for significant fines from the Department of Health and Human Services (HHS). HIPAA violations can result in fines in the millions of dollars.

In this blog post, Life Sciences Decoded will explore some of the cybersecurity concerns drug and device sponsors should keep in mind when operating clinical trials.

Controlling laws in the U.S.

There are several laws in the U.S. of which clinical trial sponsors must be aware. First, almost every state in the U.S. has passed a law dealing with what happens when a company encounters an incident where the security of an individual's personally identifiable information (PII) has been accessed by an unauthorized party. Although these laws vary greatly between states, only one state has passed a law laying out proactive requirements for data protection.

At the federal level, there are laws that apply to certain industries, but most important to sponsors of clinical trials is the Health Insurance Portability and Accountability Act, or HIPAA. When combined, HIPAA and its later amendment, HITECH, are the most comprehensive federal law addressing data privacy and cybersecurity in health care generally, including in the context of clinical trials. Generally, the HIPAA rules require that certain health-care-related entities have in place certain requirements for "protected health information" or "PHI." These rules are, generally:

  1. HIPAA Security Rule - National standards for the protection of an individual's PHI. These requirements include extensive responsibilities for establishing policies and procedures to protect electronic PHI (or ePHI). This includes data encryption, backup and password policies.
  2. HIPPA Privacy Rule - Controls the use and disclosure of an individual's PHI and sets standards for providing individuals with control over their PHI.
  3. Breach Notification Rule - A set of standards for notifying impacted individuals, as well as the Department of Health and Human Services, when PHI is accessed by unauthorized individuals.

These regulatory requirements are detailed and supply the foundational considerations for how PHI is managed in terms of minimizing the amount of PHI collected and minimizing access to that PHI to only those individuals and entities that require it.

Managing PHI

Managing the "flow" of PHI between entities during clinical trials is particularly important when ePHI is involved as it can be "touched" by many different participants in the clinical trial process.

When a sponsor establishes the processes and procedures related to a clinical trial, managing ePHI must be a focused on the security of data being collected and protecting the data from breach in light of these many "touches." Failure to manage and account for potential breaches in data security throughout the clinical trial process is likely to expose the sites and/or sponsor to liability.

The nature of clinical trials necessarily involves multiple parties, from the drug sponsor to trial locations and, potentially, contract research organizations (CROs) that manage the clinical trials for the sponsor. To simplify HIPAA compliance in the clinical trial context, a drug sponsor should determine which entities need access to ePHI and create study protocols to properly manage that access. This necessarily involves the proper identification of the role of the drug sponsor, CRO and trial sites under the HIPAA laws. There are two potential roles an entity can play:

  • Covered Entity: A Covered Entity is the primary entity in charge of PHI. Covered Entities include health care providers (hospitals, doctors, nursing homes, pharmacies, etc), health plans (health insurance companies, HMOs, etc.), and health care clearing houses (entities that process PHI between nonstandard to standard formats).
  • Business Associate: A business associate is an entity that performs certain functions or activities that involve PHI on behalf of a covered entity. This may include a claims administrator, a consultant that performs utilization reviews for a hospital, or an attorney who provides legal services to a health plan that necessitates access to PHI.

The responsibilities vary between the two, but generally both entities are required to have procedures and policies in place to protect ePHI according to the rules described above. However, the Covered Entity takes a primary role in compliance and managing ePHI access.

During a clinical trial, the study site will have the most extensive need to access PHI. On-site physicians and support staff must be able to properly treat patients and apply the study protocols in providing the study drug to those patients. Support staff will also be involved in managing PHI, collecting study data, collecting results and reporting those results to the CRO or sponsor. Study sites are also generally hospitals and physicians' offices that regularly handle PHI as a part of their practices. As a result, it is most likely that the study sites will be a covered entity under HIPAA.

HIPAA's requirements apply to PHI, that is, health information and information that can relate to an individual. PHI can be "de-identified" under HIPAA, meaning that the link between the health information and an identifiable person is broken. HHS has published a set of standards by which PHI can be de-identified through one of two approved methods:

  1. A formal determination by a neutral third party qualified expert; or
  2. The removal of certain special identifiers from the data and the lack of actual knowledge that the remaining information could be used, alone or with other available information, to identify individuals from the data in question.

Generally, CROs and sponsors do not need access to the actual individual identities (exceptions include protocol audits and special circumstances like adverse events). As a result, sponsors should employ processes to de-identify PHI to limit access to PHI to only those who must have it for the purposes of the study.

FDA and ePHI

The FDA has not addressed the protection of PHI in the same way as HIPAA, HITECH and the rules promulgated by HHS under those laws. Instead, the FDA has addressed the issue from the perspective of connected medical devices.

In the last several years, the FDA has created several rules that deal specifically with cybersecurity and the ability for device manufacturers, developers of mobile medical apps ("MMAs"), and operators of Medical Device Data Systems ("MDDSs") to secure their systems against unauthorized access. These devices include:

  • Connected Medical Devices: Generally, these are medical devices that have the capability to transfer data or otherwise be controlled through some other electronic device. These include networked devices, as well as devices with hardware ports.
  • Mobile Medical Apps: MMAs are apps for a phone, tablet or other mobile computer that turn the mobile computer into a medical device, including those that have additional hardware accessories. Some of the most popular such devices are apps with accessories for testing and tracking blood glucose. MMAs also include EMR software.
  • Medical Device Data Systems: MDDSs are software that passively handles, stores and makes available medical data, often for access and use by MMAs. An example is software that converts digital data from a sensor into a physical printout, without interpreting or manipulating the data in the process; or software that displays previously captured ECG data or X-ray imaging. MDDSs cannot be used in active patient monitoring.

The FDA has created a set of guidance documents that outline the agency's expectations for developers and users when it comes to ensuring that software and the device to which the software is associated with are secure. The most well-known and publicized issues are related to patient safety, such as a rug pump that could be compromised over an active network connection and be hacked to misdeliver drug doses. Such concerns are relevant to and can occur in a clinical trial setting. Clinical trial data not only includes patient information that is contained on a database but information related to the study drug itself. Protecting the integrity of trial data in a trial database is not only important to ensure study validity — study drug data may be impacted if patient data can be compromised and changed.

In addition, study databases contain more than just patient data. Confidential data such as drug formulations, dosing regimens, adverse event records and other sensitive information can be included in whole or in part in these study databases. Impaired or breached databases could lead to an inability to substantiate maximum tolerable dosing, efficacy and safety of the study drug. Therefore, it is critical for the developing drug sponsors to consider the security framework as outlined in the MMAs and MDDSs and understand that study databases must be designed to be secure, in addition to having a plan in place in the event of a security breach. Indeed the FDA has approached software and related systems as needing to be created and implemented with a "security by design" mentality.

FDA-regulated entities must be aware of the FDA's concerns and expectations surrounding cybersecurity, including the agency's reference to and application of the National Institute of Standards and Technology's (NIST's) cybersecurity framework. This document provides standards which the FDA is increasingly applying to more and more industries it regulates. Drug and device sponsors should be aware of the framework's standards and how they apply to the sponsor's practices.

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.

Emails

From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .

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.