Negotiating the Tension Between Transparency and Privacy

by Pepper Hamilton LLP
Contact

Pepper Hamilton LLP

Making individual patient-level data available for other research presents companies with challenges, but researchers and companies can take steps to minimize the risks.

This article originally was published in the September 2018 issue of Drug and Medical Device, For The Defense, a publication of DRI – The Voice of the Defense Bar, and is republished with permission.

Many scientists in fields involving clinical research reacted with concern when then-U.S. Environmental Protection Agency (EPA) Administrator Scott Pruitt signed a proposed rule that would require individual patient-level data for studies pivotal to EPA actions to be publicly available. “The era of secret science at EPA is coming to an end,” Pruitt said. Press Release, EPA Administrator Pruitt Proposes Rule to Strengthen Science Used in EPA Regulations (April 24, 2018). Opponents noted that most of the largest epidemiological studies had been performed under informed consents that had not contemplated that individual patient-level data would be shared with third parties. See J. Eilperin & B. Dennis, Pruitt to Unveil Controversial Transparency Rule Limiting What Research EPA Can Use, The Washington Post (Apr. 24, 2018).

Pharmaceutical and medical device companies conducting clinical trials face similar calls to make data publicly available, similar allegations of “secret science,” and similar issues with regard to individual patient-level data and informed consent. Proponents for access argue that requiring disclosure of information about clinical trials prevents duplication of unsuccessful or unsafe trials. Moreover, they argue that systematic disclosure of results of all clinical trials eliminates the ability of sponsors, researchers, and manufacturers to release partial information selectively about the results of studies via scientific publications, abstracts, and press releases:

“Communities have expressed concern about the lack of publications from clinical trials (regardless of outcomes) and bias in the literature, which may be due to selective reporting by trial sponsors or by journals in response to manuscripts that they deem less interesting.”

Comments to 2016 HHS Rule, 81 Fed. Reg. at 64,985. Supporters of open access argue that open data mean better science.

At the same time, there has been growing recognition of the need to protect individuals’ private data. The identification of the alleged Golden State killer from a relative’s DNA sample provided a warning about the potential use of personal information; it showed that sharing one’s own DNA permits matching to relatives’ DNA — even from crime scenes. Here is another cautionary tale: the Harvard Personal Genome Project posts information about volunteers on the internet to help researchers gain new insight about human health and disease. Volunteers’ names do not appear, but the profiles list medical information, including illegal drug use, alcoholism, depression, sexually transmitted diseases, medications, and DNA sequences. Some of the volunteers provided ZIP codes, dates of birth, and gender information. Dr. Latanya Sweeney, director of the Data Privacy Lab at Harvard, was able to identify 42 percent of these individuals by combining those three pieces of data with information from public records. A. Tanner, Harvard Professor Re-Identifies Anonymous Volunteers in DNA Study, Forbes (Apr. 25, 2013). Sweeney performed earlier research showing that she could identify up to 87 percent of the U.S. population with just ZIP codes, birthdates, and gender information.

There are, of course, other numbers.

Around 1.13 million patient records were compromised in 110 health-care data breaches in the first quarter of 2018, according to data released on May 3 in the Protenus Breach Barometer Report. F. Donovan, 1.13M Records Exposed by 110 Healthcare Data Breaches in Q1 2018, Cybersecurity News (May 7, 2018).

Approximately 270,000 people used a Facebook app in 2014 to take a personality test for “academic research purposes,” which — because of Facebook’s terms of service and its application programming interface at the time — permitted the app’s developer to collect information about users’ Facebook friends. The app’s developer obtained data from up to 87 million users, which he shared with political consulting firm Cambridge Analytica. H. Tuttle, Facebook Scandal Raises Data Privacy Concerns, Risk Management Magazine (May 1, 2018).

These disturbing examples define the issues that data privacy is meant to address: The personal information of millions of individuals was collected or used in ways that they were not made aware of, did not consent to, and over which they had no control. These stories, and the European Union General Data Protection Regulation (GDPR), have increased public awareness of data risks, as well as calls for heightened privacy. The competing values of data transparency and data privacy can conflict, creating tension for parties conducting clinical trials. This article examines the momentum for, and the reach of, increasing transparency demands and the competing privacy obligations imposed on companies. It also discusses how these issues arise when clinical trial data are sought in litigation. The article concludes with suggestions that companies should consider in meeting these competing demands.

The Momentum for Transparency

Several circumstances have driven the momentum toward transparency. These include the call for information about clinical trials from patients, clinical trial registration expansion, and a movement toward open access to clinical trial results and data, among others.

Clinical Trial Registration

The U.S. clinical trial registry, ClinicalTrials.gov, was launched in 2000 to meet the Food and Drug Administration Modernization Act of 1997 requirement that the National Institutes of Health (NIH) create a public information resource on clinical trials to include information about clinical trials conducted under investigational new drug applications. At that time, with the country still in the throes of the AIDS crisis, the call for information about clinical trials was largely coming from patients, who advocated for an accessible resource to find clinical studies in which they might participate.

As views about the public need (or public right in the case of public-funded studies) for information about clinical trials evolved, the clinical trial registry became more focused on clinical trial results. In 2005, the International Committee of Medical Journal Editors (ICMJE) recommended that medical journals require trial registration on a public registry as a condition of publication, stating,

The purpose of clinical trial registration is to prevent selective publication and selective reporting of research outcomes, to prevent unnecessary duplication of research effort, to help patients and the public know what trials are planned or ongoing into which they might want to enroll, and to help give ethics review boards considering approval of new studies a view of similar work and data relevant to the research they are considering.

See ICMJE Recommendations, Clinical Trial Registration, 2005.

The Food and Drug Administration Amendments Act of 2007 (FDAAA) made registration of most prospective controlled clinical trials beyond Phase 1 trials mandatory. See 42 U.S.C. §282(j)(1)(A) (defining “applicable clinical trials”). The FDAAA also mandated disclosure of specific information for the registration, including the study’s primary purpose, the study’s design, the primary disease or condition being studied, and the study start and completions dates.

In 2016, the U.S. Department of Health and Human Services (HHS) and the NIH expanded the scope of trial registration. 42 C.F.R. §11.48(a). These rules require all qualifying investigators or sponsors that are conducting clinical trials either regulated by the FDA or funded partially or wholly by the NIH to file information and data about results on ClinicalTrials.gov — even when the studied product is not approved, licensed, or cleared by the FDA. In addition, the public registration must include the full protocol and statistical analysis plan for the trial.

In the 2017 changes to the Federal Policy for the Protection of Human Subjects (known as the “Common Rule”), the HHS mandated the posting of informed consent forms for federally funded trials to a public website, although final details regarding the requirement are unresolved. See Fed. Reg. Vol. 82, No. 12 (Jan. 19, 2017) (implementation delayed).

This push for more transparency is consistent with the policies of the European Medicines Agency. The European Medicines Agency has its own database, the European Clinical Trials Database (EudraCT), which includes information on clinical trials taking place in the European Union and clinical studies conducted worldwide in accordance with a pediatric investigation plan. A subset of the data is publicly accessible via the European Clinical Trials Register.

Clinical Trial Results and Data

As the clinical trial community was adjusting to trial registration, there was also a movement toward open access to clinical trial results and data. In 2003, the NIH concluded that data from NIH-supported research should be shared. While the precise mechanism for data sharing was not prescribed — it could be through publishing, investigator responses to data requests, availability in a controlled environment in which researchers could perform analyses using the data, data archives, or a mixture of the above — the rationale was clearly stated:

We believe that data sharing is essential for expedited translation of research results into knowledge, products, and procedures to improve human health. The NIH endorses the sharing of final research data to serve these and other important scientific goals. The NIH expects and supports the timely release and sharing of final research data from NIH-supported studies for use by other researchers.

Notice, NIH, “Statement on Sharing Research Data” (Feb. 26, 2003).

In addition to broadening the categories of clinical trials for which registration was required, the 2007 FDAAA required summary results for applicable clinical trials that began after September 2007 to be posted to ClinicalTrials.gov within one year after completion of the trial. Required information included tables of specified information (i.e., participant flow, baseline characteristics, outcome measures and statistical analyses, and adverse events information).

The movement toward making additional clinical trial data available continued. The 2016 HHS rule expanding the scope of trial registration also expanded the summary results obligations. Thus, for studies with primary completion dates on or after January 18, 2017, in addition to the results tables previously required, sponsors must submit three adverse event tables summarizing (1) all serious adverse events grouped by organ system, with the number and frequency of each event by arm; (2) all other adverse events that occurred with a frequency of five percent or more in any arm of the trial; and (3) all cause-mortality data by arm. 42 C.F.R. §11.48(a)(4). Adverse event tables must include information about events that occurred, regardless of whether the event was anticipated or unanticipated. 2016 Comment, 81 Fed. Reg. at 64983.

Similarly, posting clinical trial summary results in EudraCT became mandatory for sponsors as of July 2014. The European Medicines Agency’s policy on publication of clinical data, along with previously implemented policies, requires the submission of clinical overviews, clinical summaries, and clinical study reports, along with specific appendices, including protocol and protocol amendments, sample case report forms, and documentation of statistical methods, all of which will be posted.

In addition, European Medicines Agency’s Policy 70, adopted in 2014, mandates for data submitted to the agency in support of a marketing authorization that certain anonymized study-related documents (called “clinical reports”) will be made publicly available on EMA’s website. In the future, Policy 70 envisions that individual patient-level data for these studies will also be made available. Anonymized clinical reports are available for many products; the individual patient-level data publication process under Policy 70 has not yet begun.

Sharing Individual Patient-Level Data

Several clinical trial sponsors have pioneered the sharing of clinical trial data, including individual patient-level data, and advocacy in support of such sharing is growing. In an unprecedented step in data sharing, in 2011, Medtronic provided to Yale University’s Open Data Access Project de-identified individual patientlevel data from its sponsored clinical trials for rhBMP-2. In addition to providing a grant to Yale to permit two fully independent, third-party systematic reviews of these data, Medtronic made the individual patient-level data available to additional researchers through Yale’s defined registration process and website. Other companies also began making individual patient-level data available to researchers.

In July 2013, the European Federation of Pharmaceutical Industries and Associations (EFPIA) and the Pharmaceutical Research and Manufacturers of America (PhRMA) jointly endorsed principles for responsible clinical trial data sharing. Under these principles, member pharmaceutical companies agreed to dramatically increase the amount of information available to researchers, patients and members of the public by committing to the following:

Patient-level clinical trial data, study-level clinical trial data, full clinical study reports, and protocols from clinical trials in patients for medicines approved in the United States and European Union will be shared with qualified scientific and medical researchers upon request and subject to terms necessary to protect patient privacy and confidential commercial information.

Press Release, EFPIA-PhRMA Rules for Clinical Trial Data Sharing Active (Jan. 1, 2014). According to a 2016–2017 survey of their members, “98 percent of EFPIA and PhRMA member companies share clinical trial data beyond any legal or regulatory requirements.” Press Release, EFPIAPhRMA Principles Successfully Enable Responsible Clinical Trial Data Sharing (Nov. 29, 2017).

In June 2017, the ICMJE issued a statement on data sharing for clinical trials that expressed the belief that “there is an ethical obligation to responsibly share data generated by interventional clinical trials because trial participants have put themselves at risk.” D. B. Taichman, Data Sharing Statements for Clinical Trials: A Requirement of the International Committee of Medical Journal Editors, N. Eng. J. Med. 376:2277–2279 (June 8, 2017).

As a result, ICMJE requires, as a condition of any consideration for publication of a clinical trial report, that (1) as of July 1, 2018, manuscripts submitted to ICMJE journals must contain a datasharing statement and (2) clinical trials for which enrollment starts after January 2019 must include a data-sharing plan in the trials’ registration.

Id. The data-sharing statements must indicate (1) whether de-identified individual patient-level data will be shared; (2) which data will be shared; (3) whether additional documents, such as the study protocol and statistical analysis plan, will be available; (4) when the data will be available; and (5) under which access criteria data will be shared. Id.

This article focuses on data privacy and consent issues in sharing clinical trial information. Data sharing raises additional issues, including potential exposure of competitively sensitive information, misuse of data, and significant costs of data de-identification. These issues are beyond the scope of this article, though we note that many vehicles for data sharing contain measures to address them. Both ClinicalTrials.gov and the European Medicines Agency website, for example, provide some protections for commercially sensitive information. Data-use agreements contain limitations and conditions for obtaining and using data; some require submission of a scientific protocol and a statement of intent to publish any results from data analysis. Data-sharing sites generally permit companies to refuse certain requests, including, as the PhRMA/EFPIA principles suggest, a competitor’s request for proprietary information. Data-sharing sites can also help address cost because they provide infrastructure for handling requests and for data hosting.

The Evolving Obligation to Protect Private Information

As computers and personal devices have revolutionized the way that records and data are collected, stored, and shared, countries have passed vigorous laws to protect data privacy and security. In discussing these evolving laws, we focus on developments in the United States and the European Union. Countries outside the United States and European Union have their own privacy laws, which also have been strengthened to meet increasing privacy and security concerns. For example, in Canada, many federal, provincial, and territorial privacy statutes govern the protection of personal information, including the Personal Information Protection and Electronic Documents Act and a comprehensive data-breach notification statute, effective November 2018.

Health Insurance Portability and Accountability Act (HIPAA)

HIPAA was enacted on August 21, 1996, with the dual goals of making health care delivery more efficient through use of electronic health records and expanding health insurance coverage. HIPAA also mandated the development of nationwide security standards and safeguards for the use of electronic health care information as well as the creation of privacy standards for protected health information (PHI). See HIPAA Privacy Rule (Privacy Rule), codified at 45 C.F.R. §§160, 164. The primary purpose of the Privacy Rule is to protect individuals’ privacy while allowing necessary but controlled access to their PHI.

The Privacy Rule generally prohibits the unauthorized use or disclosure of PHI by “covered entities,” including health care providers, pharmacies, health insurers, and health-care clearinghouses and their business associates acting on behalf of covered entities that use or transmit PHI for any HIPAA-related transaction. Under the Privacy Rule, a covered entity or business associate may not use or disclose PHI unless the individual provides written authorization, including a description of the nature of the information collected and how it will be used or disclosed. Authorization for the disclosure of PHI for research purposes must also identify a specific research study and must contain certain core elements and required statements, such as the right to revoke authorization and that the patient’s PHI may no longer be protected once it is disclosed by the covered entity.

The Privacy Rule permits research to continue without an individual’s authorization if the PHI has been de-identified by removing all 18 HIPAA identifiers, or through an expert’s statistical analysis when the expert confirms that there is a “very small” risk of re-identification, and there is no actual knowledge that the individual could be identified. Alternatively, an Institutional Review Board (IRB) may grant an authorization waiver when (1) the research cannot practically be conducted without the disclosure of the PHI, and (2) there is minimal privacy risk. Another exception to requiring an authorization involves a limited data set, where limited types of indirect identifiers (e.g., date of birth, dates of treatment) may be accessed by a researcher as long as the researcher and the covered entity sign a data-use agreement that describes the permitted uses and disclosures. Finally, use and disclosure without authorization is permitted if required by law or for public health reasons, such as adverse-event reporting to the product’s sponsor or the FDA.

In January 2013, the Health Information Technology for Economic and Clinical Health Act, 42 U.S.C. §300jj et seq., expanded the reach of the HIPAA Privacy and Security Rules by extending HIPAA liability directly to business associates to whom PHI is disclosed, more broadly defining “business associate” to include subcontractors of business associates, adding mandatory new data breach rules reducing the threshold for reporting HIPAA breaches, and increasing noncompliance penalties. 42 U.S.C. §17921 et seq. Failure to comply with HIPAA can result in civil and criminal penalties.

GDPR

In 1996, the European Union promulgated the Data Protection Directive, 95/46/EC, which established basic principles for privacy legislation for EU member countries. The directive was based on recommendations of the Organisation for economic Cooperation and Development. Unlike HIPAA, the Data Protection Directive broadly defined personal data to be protected as all information related to an identifiable person, not just health-care data.

While the directive sought to protect personal data for individuals in the European Economic Area, because it was adopted as an EU directive, each EU member state had significant leeway in implementing its own national data protection law. The result was a patchwork of inconsistent obligations relating to personal data across the European Union. To address these and other issues with the directive, in 2016, the European Union adopted a new data privacy regulation, the General Data Protection Regulation (GDPR), Regulation (EU) 2016/679 (now adopted by all 31 European Economic Area member nations).

The highly publicized GDPR — which replaces the Data Protection Directive — took effect on May 25, 2018. The GDPR applies not only to businesses located within the European Union, but also to businesses outside the European Union if they process personal data of individuals in the European Union. It therefore applies to U.S. pharmaceutical and medical device companies with clinical research subjects in the European Union. The GDPR provides the following rights for individuals: (1) the right to be informed; (2) the right of access; (3) the right to rectification; (4) the right to erasure; (5) the right to restrict processing; (6) the right to data portability; (7) the right to object; and (8) rights in relation to automated decision making and profiling. Companies subject to the GDPR need to have processes in place to ensure that when data are handled the data remain protected, either through encryption; anonymization, which is the removal of identifiable information; or pseudonymization, where data components are anonymized and separated. To ensure compliance with the GDPR, companies need, among other things, a data protection officer, who is responsible for overseeing data security strategy and GDPR compliance, if they process or store large amounts of EU citizen data, process or store special personal data, regularly monitor data subjects, or are a public authority. The GDPR also mandates reporting of data breaches within 72 hours. The Fortune 500 companies, including major pharmaceutical and device companies, were expected to spend at total of $7.8 billion complying with the GDPR, according to a recent Ernst & Young survey. Failure to comply with the GDPR carries significant penalties, up to a maximum of the greater of 4 percent of global revenue or €20 million. Indeed, the Facebook incident has led to a cottage industry of commentators estimating Facebook’s presumptive liability had the GDPR been in effect when the data harvesting occurred.

California Privacy Act

In June of this year, California joined the drive to broaden protection of individual’s privacy rights to the global standard, thus setting the new US data privacy high watermark by enacting a Privacy Act (the CA Privacy Act), which will become  effective in January 2020. The CA Privacy Act provides several GDPR-style individual rights to consumers, and applies to qualifying businesses worldwide that sell in the California market. Qualifying businesses are for-profit entities (a) with annual gross revenues over $25 million that collect consumers’ personal information, or on whose behalf consumers’ personal information is collected, or (b) that obtain the personal information of at least 50,000 consumers annually. The CA Privacy Act requires businesses to safeguard consumer’s personal information and permits a private right of action and statutory damages if a consumer’s unredacted or unencrypted personal information is subject to unauthorized access and exfiltration, theft or disclosure as a result of a business’s violation of the duty to secure that data. It also imposes a duty on qualifying businesses to ensure supply-chain compliance, to require their service providers to delete the personal information of any consumer whose personal information was deleted at the consumer’s request.

Effect of Informed Consent on Data Sharing

While data privacy is not the first thing that most people think of when they hear the words “informed consent,” consent must address how a study participant’s privacy will be protected. Any public access to clinical trial data must be compliant with principles governing informed consent, including principles that apply to de-identified data.

As data sharing becomes more common, informed consent should include a discussion of the parties’ desire to retain the participant’s data after the study is completed for possible use in future projects by the investigator or others. The consent form should state that identities might be removed; note that de-identified information may be used for future research; and advise the participant of what will happen if he or she revokes consent at a later date.

Historically, informed consent forms did not discuss future use of data, let alone the possibility that unknown third parties might be permitted access to data. Indeed, seeking to comply with regulations and ensure that subjects were informed about the various entities that might access their data, traditional sponsor-drafted informed consents frequently named the specific entities (e.g., the sponsor, FDA, and IRBs) with which data may be shared. See, e.g., 21 C.F.R. §50.20 (FDA requires informed consents to include statements describing the confidentiality of the information collected during the clinical trial, how records will be kept, and the possibility that FDA and others outside the study may review the records). Some consents implicitly or even explicitly limited the disclosure to these entities.

Depending on their wording, these “traditional” informed consents may present barriers to data sharing from studies to which they applied. Under U.S. law, if information privacy risks to U.S. subjects are minimized, an IRB can waive the need for any additional consent to share data. The Common Rule, which applies to human research performed under the HHS (but does not directly apply to research performed with FDA approval), has long permitted a researcher to seek waiver of informed consent for “minimal risk” research — that is, when the research involves no more than minimal risk to the subjects. 45 C.F.R. §46.116(d). In July 2017, the FDA announced in guidance that because it plans to promulgate new regulations to permit waiver for minimal risk studies, it would not object to IRBs’ waiving informed consent for studies performed under FDA approvals. Therefore, when an informed consent is silent pertaining to whether there may be future use of the data, IRBs may approve waivers for minimal risk studies using de-identified patient-level data.

If the informed consent implicitly or explicitly limits access to the data, however, IRBs (or the company itself) may not be able to permit access. A September 2016 EFPIA and PhRMA survey showed that for their members with systems in place to share de-identified individual patientlevel data, a leading reason for refusing to share data in specific instances was that the informed consent for the clinical trial did not allow data sharing.

Data Access in Litigation

Plaintiffs asserting product liability claims against drug and medical device manufacturers often seek all clinical trial data relating to the involved drug or device. Allegations purporting to require these data range from claims of hidden clinical data to misreporting of results. In some cases, plaintiffs have gone so far as to seek individual patient-level data. In doing so, they not only argue that full disclosure of individual patient-level data is required to ensure that the study was accurately reported, but also that permitting them access to individual patient-level data will create better science (or “is compelled by public health”) by allowing their experts to perform their own analyses.

All of the difficulties of individual patient-level data production, including de-identification, still apply in the context of litigation. Despite arguments to the contrary, properly de-identifying individual patient-level data is costly and time-consuming. The increased public awareness of the implications of privacy breaches may help courts understand the importance of data de-identification. Defendants should also educate courts about the burdens of de-identifying data and should use proportionality arguments when available. See Fed. R. Civ. P. 26(b)(1). In addition, defendants should propose shifting of the cost of de-identifying data to plaintiffs if individual patient-level data production is required.

Finally, as for plaintiffs’ arguments that their experts must be permitted to adjudicate the science “in the public interest,” litigation is a poor avenue for such a venture. Even organizations at the forefront of open access generally support access to the data for scientific research purposes — but not for litigation experts. See, e.g., ICMJE Data Sharing Statement, NEJM 376:2277-2279 (June 8, 2017) (discussing sharing for research purposes); Press Release, EFPIA-PhRMA Rules for Clinical Trial Data Sharing Active (Jan. 1, 2014) (data will be shared “with qualified scientific and medical researchers upon request and subject to terms necessary to protect patient privacy and confidential commercial information”).

Best Practices for Sharing De-Identified Patient-Level Clinical Trial Data

As the above demonstrates, there are competing obligations imposed on parties responsible for clinical trials to make data publicly available but also to comply with the multiple privacy statutes or regulations, some of which carry significant penalties for noncompliance. The growing expectation for more organic data at the patient level will only increase the challenge. Companies conducting clinical trials should consider the following.

For future trials: Consent for the future use of de-identified data should be included in informed consents and should be unambiguous. Subjects should be told of their right to revoke consent for this use and the consequences of revocation.

For existing trials: If a company is seeking to share individual patient-level data from trials with informed consents that do not address data sharing, and if the participants are all in the United States, the company can satisfy HIPAA by removing all 18 HIPAA identifiers, or through an expert’s statistical analysis when the expert confirms that there is a “very small” risk of re-identification. Under recent FDA guidance, a company can also seek an IRB waiver for additional use of the data as presenting minimal risk of harm to the participant (including his or her privacy). For study participants in the European Union, a company must consider whether there are similar options to share individual patient-level data collected in earlier trials.

Consider the vehicle for data sharing. There are several established sites for sharing and using data from clinical trials and other scientific research. Most are controlled sites, where researchers who seek access to individual-level data are required to enter into a data-sharing agreement. Data-sharing agreements generally include requirements to protect participants’ privacy and data confidentiality, and they may prohibit the recipient from transferring the data to other users or require that the data be used for research purposes only, or both. Many prohibit a researcher from trying to use the data to “re-identify” subjects. Established sites include the following:

  • ClinicalStudyDataRequest.com: A consortium of 14 major pharmaceutical companies that facilitates access to patient-level data from clinical studies
  • Yale Open Data Access Project: A university-based organization that facilitates access to clinical trial program data for pharmaceutical and medical device companies
  • Supporting Open Access for Researchers (SOAR): A university-based collaboration to facilitate access to patient-level data from clinical studies.

Use data-sharing agreements to address additional concerns. Data-sharing agreements can include additional restrictions beyond privacy. For example, the European Medicines Agency’s clinical data website permits a user access only upon agreement that data will not be used for commercialization purposes. Other sites require submitting a protocol to a gatekeeper, who reviews it for scientific merit.

Ensure data de-identification. Data de-identification is not an easy process. Both direct and indirect identifiers need to be considered. Direct identifiers include information such as a participant’s name, initials, email address, and postal code. Indirect identifiers include information such as demographic, biological, and geographic data that if combined, might lead to identification. Consider reducing the risk by hiring a consultant who can perform a statistical analysis to confirm there is a very small risk of re-identification.

Recognize that there are instances in which data cannot be shared. There may be instances in which data simply cannot be shared, including these:

  • When data cannot be sufficiently anonymized to safeguard patient privacy, particularly when there are small clinical trials, such as rare disease trials
  • When the obtained informed consents explicitly preclude data sharing.

Conclusion

Data transparency is highly valued; it permits researchers to have faith in clinical trial results. Making individual patientlevel data available for other research, however, presents companies with challenges — including potential data privacy risks to clinical trial subjects and the costs of ameliorating that risk. There are steps being taken to ease some of these challenges for future trials: new informed consent forms are being debated and designed, and best practices for de-identification are being developed. At the same time, caution suggests that more powerful computer technology and larger databases will increase the risk of re-identification of research subjects, and we receive daily reports of data privacy breaches. Sponsors of clinical trials remain at the intersection of these forces.

 

Written by:

Pepper Hamilton LLP
Contact
more
less

Pepper Hamilton LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
- hide

JD Supra Privacy Policy

Updated: May 25, 2018:

JD Supra is a legal publishing service that connects experts and their content with broader audiences of professionals, journalists and associations.

This Privacy Policy describes how JD Supra, LLC ("JD Supra" or "we," "us," or "our") collects, uses and shares personal data collected from visitors to our website (located at www.jdsupra.com) (our "Website") who view only publicly-available content as well as subscribers to our services (such as our email digests or author tools)(our "Services"). By using our Website and registering for one of our Services, you are agreeing to the terms of this Privacy Policy.

Please note that if you subscribe to one of our Services, you can make choices about how we collect, use and share your information through our Privacy Center under the "My Account" dashboard (available if you are logged into your JD Supra account).

Collection of Information

Registration Information. When you register with JD Supra for our Website and Services, either as an author or as a subscriber, you will be asked to provide identifying information to create your JD Supra account ("Registration Data"), such as your:

  • Email
  • First Name
  • Last Name
  • Company Name
  • Company Industry
  • Title
  • Country

Other Information: We also collect other information you may voluntarily provide. This may include content you provide for publication. We may also receive your communications with others through our Website and Services (such as contacting an author through our Website) or communications directly with us (such as through email, feedback or other forms or social media). If you are a subscribed user, we will also collect your user preferences, such as the types of articles you would like to read.

Information from third parties (such as, from your employer or LinkedIn): We may also receive information about you from third party sources. For example, your employer may provide your information to us, such as in connection with an article submitted by your employer for publication. If you choose to use LinkedIn to subscribe to our Website and Services, we also collect information related to your LinkedIn account and profile.

Your interactions with our Website and Services: As is true of most websites, we gather certain information automatically. This information includes IP addresses, browser type, Internet service provider (ISP), referring/exit pages, operating system, date/time stamp and clickstream data. We use this information to analyze trends, to administer the Website and our Services, to improve the content and performance of our Website and Services, and to track users' movements around the site. We may also link this automatically-collected data to personal information, for example, to inform authors about who has read their articles. Some of this data is collected through information sent by your web browser. We also use cookies and other tracking technologies to collect this information. To learn more about cookies and other tracking technologies that JD Supra may use on our Website and Services please see our "Cookies Guide" page.

How do we use this information?

We use the information and data we collect principally in order to provide our Website and Services. More specifically, we may use your personal information to:

  • Operate our Website and Services and publish content;
  • Distribute content to you in accordance with your preferences as well as to provide other notifications to you (for example, updates about our policies and terms);
  • Measure readership and usage of the Website and Services;
  • Communicate with you regarding your questions and requests;
  • Authenticate users and to provide for the safety and security of our Website and Services;
  • Conduct research and similar activities to improve our Website and Services; and
  • Comply with our legal and regulatory responsibilities and to enforce our rights.

How is your information shared?

  • Content and other public information (such as an author profile) is shared on our Website and Services, including via email digests and social media feeds, and is accessible to the general public.
  • If you choose to use our Website and Services to communicate directly with a company or individual, such communication may be shared accordingly.
  • Readership information is provided to publishing law firms and authors of content to give them insight into their readership and to help them to improve their content.
  • Our Website may offer you the opportunity to share information through our Website, such as through Facebook's "Like" or Twitter's "Tweet" button. We offer this functionality to help generate interest in our Website and content and to permit you to recommend content to your contacts. You should be aware that sharing through such functionality may result in information being collected by the applicable social media network and possibly being made publicly available (for example, through a search engine). Any such information collection would be subject to such third party social media network's privacy policy.
  • Your information may also be shared to parties who support our business, such as professional advisors as well as web-hosting providers, analytics providers and other information technology providers.
  • Any court, governmental authority, law enforcement agency or other third party where we believe disclosure is necessary to comply with a legal or regulatory obligation, or otherwise to protect our rights, the rights of any third party or individuals' personal safety, or to detect, prevent, or otherwise address fraud, security or safety issues.
  • To our affiliated entities and in connection with the sale, assignment or other transfer of our company or our business.

How We Protect Your Information

JD Supra takes reasonable and appropriate precautions to insure that user information is protected from loss, misuse and unauthorized access, disclosure, alteration and destruction. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. You should keep in mind that no Internet transmission is ever 100% secure or error-free. Where you use log-in credentials (usernames, passwords) on our Website, please remember that it is your responsibility to safeguard them. If you believe that your log-in credentials have been compromised, please contact us at privacy@jdsupra.com.

Children's Information

Our Website and Services are not directed at children under the age of 16 and we do not knowingly collect personal information from children under the age of 16 through our Website and/or Services. If you have reason to believe that a child under the age of 16 has provided personal information to us, please contact us, and we will endeavor to delete that information from our databases.

Links to Other Websites

Our Website and Services may contain links to other websites. The operators of such other websites may collect information about you, including through cookies or other technologies. If you are using our Website or Services and click a link to another site, you will leave our Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We are not responsible for the data collection and use practices of such other sites. This Policy applies solely to the information collected in connection with your use of our Website and Services and does not apply to any practices conducted offline or in connection with any other websites.

Information for EU and Swiss Residents

JD Supra's principal place of business is in the United States. By subscribing to our website, you expressly consent to your information being processed in the United States.

  • Our Legal Basis for Processing: Generally, we rely on our legitimate interests in order to process your personal information. For example, we rely on this legal ground if we use your personal information to manage your Registration Data and administer our relationship with you; to deliver our Website and Services; understand and improve our Website and Services; report reader analytics to our authors; to personalize your experience on our Website and Services; and where necessary to protect or defend our or another's rights or property, or to detect, prevent, or otherwise address fraud, security, safety or privacy issues. Please see Article 6(1)(f) of the E.U. General Data Protection Regulation ("GDPR") In addition, there may be other situations where other grounds for processing may exist, such as where processing is a result of legal requirements (GDPR Article 6(1)(c)) or for reasons of public interest (GDPR Article 6(1)(e)). Please see the "Your Rights" section of this Privacy Policy immediately below for more information about how you may request that we limit or refrain from processing your personal information.
  • Your Rights
    • Right of Access/Portability: You can ask to review details about the information we hold about you and how that information has been used and disclosed. Note that we may request to verify your identification before fulfilling your request. You can also request that your personal information is provided to you in a commonly used electronic format so that you can share it with other organizations.
    • Right to Correct Information: You may ask that we make corrections to any information we hold, if you believe such correction to be necessary.
    • Right to Restrict Our Processing or Erasure of Information: You also have the right in certain circumstances to ask us to restrict processing of your personal information or to erase your personal information. Where you have consented to our use of your personal information, you can withdraw your consent at any time.

You can make a request to exercise any of these rights by emailing us at privacy@jdsupra.com or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

You can also manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard.

We will make all practical efforts to respect your wishes. There may be times, however, where we are not able to fulfill your request, for example, if applicable law prohibits our compliance. Please note that JD Supra does not use "automatic decision making" or "profiling" as those terms are defined in the GDPR.

  • Timeframe for retaining your personal information: We will retain your personal information in a form that identifies you only for as long as it serves the purpose(s) for which it was initially collected as stated in this Privacy Policy, or subsequently authorized. We may continue processing your personal information for longer periods, but only for the time and to the extent such processing reasonably serves the purposes of archiving in the public interest, journalism, literature and art, scientific or historical research and statistical analysis, and subject to the protection of this Privacy Policy. For example, if you are an author, your personal information may continue to be published in connection with your article indefinitely. When we have no ongoing legitimate business need to process your personal information, we will either delete or anonymize it, or, if this is not possible (for example, because your personal information has been stored in backup archives), then we will securely store your personal information and isolate it from any further processing until deletion is possible.
  • Onward Transfer to Third Parties: As noted in the "How We Share Your Data" Section above, JD Supra may share your information with third parties. When JD Supra discloses your personal information to third parties, we have ensured that such third parties have either certified under the EU-U.S. or Swiss Privacy Shield Framework and will process all personal data received from EU member states/Switzerland in reliance on the applicable Privacy Shield Framework or that they have been subjected to strict contractual provisions in their contract with us to guarantee an adequate level of data protection for your data.

California Privacy Rights

Pursuant to Section 1798.83 of the California Civil Code, our customers who are California residents have the right to request certain information regarding our disclosure of personal information to third parties for their direct marketing purposes.

You can make a request for this information by emailing us at privacy@jdsupra.com or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

Some browsers have incorporated a Do Not Track (DNT) feature. These features, when turned on, send a signal that you prefer that the website you are visiting not collect and use data regarding your online searching and browsing activities. As there is not yet a common understanding on how to interpret the DNT signal, we currently do not respond to DNT signals on our site.

Access/Correct/Update/Delete Personal Information

For non-EU/Swiss residents, if you would like to know what personal information we have about you, you can send an e-mail to privacy@jdsupra.com. We will be in contact with you (by mail or otherwise) to verify your identity and provide you the information you request. We will respond within 30 days to your request for access to your personal information. In some cases, we may not be able to remove your personal information, in which case we will let you know if we are unable to do so and why. If you would like to correct or update your personal information, you can manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard. If you would like to delete your account or remove your information from our Website and Services, send an e-mail to privacy@jdsupra.com.

Changes in Our Privacy Policy

We reserve the right to change this Privacy Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our Privacy Policy will become effective upon posting of the revised policy on the Website. By continuing to use our Website and Services following such changes, you will be deemed to have agreed to such changes.

Contacting JD Supra

If you have any questions about this Privacy Policy, the practices of this site, your dealings with our Website or Services, or if you would like to change any of the information you have provided to us, please contact us at: privacy@jdsupra.com.

JD Supra Cookie Guide

As with many websites, JD Supra's website (located at www.jdsupra.com) (our "Website") and our services (such as our email article digests)(our "Services") use a standard technology called a "cookie" and other similar technologies (such as, pixels and web beacons), which are small data files that are transferred to your computer when you use our Website and Services. These technologies automatically identify your browser whenever you interact with our Website and Services.

How We Use Cookies and Other Tracking Technologies

We use cookies and other tracking technologies to:

  1. Improve the user experience on our Website and Services;
  2. Store the authorization token that users receive when they login to the private areas of our Website. This token is specific to a user's login session and requires a valid username and password to obtain. It is required to access the user's profile information, subscriptions, and analytics;
  3. Track anonymous site usage; and
  4. Permit connectivity with social media networks to permit content sharing.

There are different types of cookies and other technologies used our Website, notably:

  • "Session cookies" - These cookies only last as long as your online session, and disappear from your computer or device when you close your browser (like Internet Explorer, Google Chrome or Safari).
  • "Persistent cookies" - These cookies stay on your computer or device after your browser has been closed and last for a time specified in the cookie. We use persistent cookies when we need to know who you are for more than one browsing session. For example, we use them to remember your preferences for the next time you visit.
  • "Web Beacons/Pixels" - Some of our web pages and emails may also contain small electronic images known as web beacons, clear GIFs or single-pixel GIFs. These images are placed on a web page or email and typically work in conjunction with cookies to collect data. We use these images to identify our users and user behavior, such as counting the number of users who have visited a web page or acted upon one of our email digests.

JD Supra Cookies. We place our own cookies on your computer to track certain information about you while you are using our Website and Services. For example, we place a session cookie on your computer each time you visit our Website. We use these cookies to allow you to log-in to your subscriber account. In addition, through these cookies we are able to collect information about how you use the Website, including what browser you may be using, your IP address, and the URL address you came from upon visiting our Website and the URL you next visit (even if those URLs are not on our Website). We also utilize email web beacons to monitor whether our emails are being delivered and read. We also use these tools to help deliver reader analytics to our authors to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

Analytics/Performance Cookies. JD Supra also uses the following analytic tools to help us analyze the performance of our Website and Services as well as how visitors use our Website and Services:

  • HubSpot - For more information about HubSpot cookies, please visit legal.hubspot.com/privacy-policy.
  • New Relic - For more information on New Relic cookies, please visit www.newrelic.com/privacy.
  • Google Analytics - For more information on Google Analytics cookies, visit www.google.com/policies. To opt-out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout. This will allow you to download and install a Google Analytics cookie-free web browser.

Facebook, Twitter and other Social Network Cookies. Our content pages allow you to share content appearing on our Website and Services to your social media accounts through the "Like," "Tweet," or similar buttons displayed on such pages. To accomplish this Service, we embed code that such third party social networks provide and that we do not control. These buttons know that you are logged in to your social network account and therefore such social networks could also know that you are viewing the JD Supra Website.

Controlling and Deleting Cookies

If you would like to change how a browser uses cookies, including blocking or deleting cookies from the JD Supra Website and Services you can do so by changing the settings in your web browser. To control cookies, most browsers allow you to either accept or reject all cookies, only accept certain types of cookies, or prompt you every time a site wishes to save a cookie. It's also easy to delete cookies that are already saved on your device by a browser.

The processes for controlling and deleting cookies vary depending on which browser you use. To find out how to do so with a particular browser, you can use your browser's "Help" function or alternatively, you can visit http://www.aboutcookies.org which explains, step-by-step, how to control and delete cookies in most browsers.

Updates to This Policy

We may update this cookie policy and our Privacy Policy from time-to-time, particularly as technology changes. You can always check this page for the latest version. We may also notify you of changes to our privacy policy by email.

Contacting JD Supra

If you have any questions about how we use cookies and other tracking technologies, please contact us at: privacy@jdsupra.com.

- hide

This website uses cookies to improve user experience, track anonymous site usage, store authorization tokens and permit sharing on social media networks. By continuing to browse this website you accept the use of cookies. Click here to read more about how we use cookies.