GDPR in Clinical Research: 5 Lessons from a €7 Million Fine

GCP Certification

A recent €7 million fine imposed by the Italian Data Protection Authority has brought the handling of patients’ health data into focus. The case concerned a database containing health information relating to approximately one million patients, used for studies commissioned by organisations including pharmaceutical companies.

The investigation identified several GDPR infringements. These included processing health data without an appropriate legal basis, providing inadequate information to patients, failing to establish appropriate data retention periods, not carrying out a data protection impact assessment and implementing insufficient security measures.

One finding deserves particular attention: the data had been described as anonymous, but the authority concluded that patients could still potentially be identified.

For organisations involved in clinical research, the case raises important questions about how personal data is collected, processed, protected and shared. Here are five lessons worth considering.

1. Removing Identifiers Does Not Necessarily Make Data Anonymous

Anonymisation is an important part of protecting personal data in research, but removing names and other obvious identifiers is not always enough.

In this case, each patient had a persistent identifier that allowed their information to be linked over time. Combined with detailed information such as age-related data, sex, diagnoses, symptoms, prescriptions and location data, this could make it possible to single out individuals and potentially identify them using reasonably available means.

This illustrates the difference between anonymised and pseudonymised data.

  • Anonymous data cannot be used to identify an individual, taking account of the means reasonably likely to be used.
  • Pseudonymised data has been processed so that individuals cannot be identified without additional information, which is kept separately. It remains personal data under the GDPR.

Pseudonymisation can be a valuable safeguard in clinical research, but it does not remove the need to comply with data protection requirements.

When assessing whether data is genuinely anonymous, organisations need to consider the information available alongside it, the ability to link records and the possibility of re-identification. The assessment should reflect the actual data and processing arrangements, rather than relying on the removal of direct identifiers alone.

2. A Valid Legal Basis Is Essential

Health data is a special category of personal data under the GDPR and receives additional protection.

Organisations processing health data need to identify an appropriate legal basis under Article 6 of the GDPR and satisfy an applicable condition under Article 9. Both requirements must be met, alongside any other applicable legal obligations.

The correct approach will depend on the purpose of the processing, the parties involved and the circumstances in which the data is collected and used.

For clinical research professionals, this means that consent should not automatically be assumed to be the legal basis for every processing activity. The legal basis for processing personal data under the GDPR is also distinct from informed consent to participate in a clinical trial.

These are related but separate considerations, and confusing them can lead to gaps in compliance.

Organisations should be able to explain why personal data is being processed, which legal provisions support that processing and whether the arrangements remain appropriate when data is used for additional purposes or shared with other organisations.

3. Participants Need Appropriate Information About How Their Data Is Used

Transparency is another fundamental GDPR requirement.

Participants and other individuals whose health data is processed need to receive appropriate information about how their personal data is used. Depending on the circumstances, this may include the purposes of processing, the legal basis, who receives the data, how long it will be retained and what rights individuals have.

Clinical research can involve several organisations, including sponsors, investigators, healthcare providers, laboratories and specialist service providers. This can make it particularly important to establish who is responsible for providing information and how the relevant arrangements work in practice.

Privacy notices should reflect the actual processing activities. They should not simply be treated as standard documents that are prepared once and left unchanged.

If the purpose of processing changes, additional data is collected or information is shared in a new way, organisations should consider whether their transparency arrangements need to be updated.

Clear information helps individuals understand what happens to their data and enables organisations to demonstrate that their obligations have been considered.

4. Data Retention and Security Need Active Management

The Italian authority also identified shortcomings relating to retention periods and security measures.

These are practical issues that can be overlooked when organisations focus primarily on the collection and initial use of data.

Under the GDPR’s storage limitation principle, personal data should not be kept in an identifiable form for longer than necessary for the purposes for which it is processed, subject to applicable exceptions and legal requirements.

Clinical research records may need to be retained for extended periods to meet regulatory, contractual or other legal obligations. However, this does not mean that every dataset can be retained indefinitely without a documented justification.

Organisations should establish appropriate retention periods, understand the requirements that apply to different categories of records and ensure that arrangements for archiving, deletion or further processing are clearly defined.

Security also needs to be proportionate to the risks. Depending on the circumstances, this may involve access controls, appropriate technical safeguards, secure data transfers, staff training and arrangements for detecting and responding to incidents.

Where data is shared with external service providers, the relevant responsibilities and safeguards should be established and maintained throughout the relationship.

5. Data Protection Impact Assessments Should Not Be an Afterthought

A data protection impact assessment (DPIA) helps organisations identify and assess risks to individuals arising from proposed processing activities.

Under Article 35 of the GDPR, a DPIA is required where a type of processing is likely to result in a high risk to the rights and freedoms of individuals. The assessment should take place before the relevant processing begins.

Processing health data on a large scale can raise significant data protection risks, making it important to assess carefully whether a DPIA is required.

A useful assessment should consider the nature, scope, context and purposes of processing, identify potential risks to individuals and establish measures to address those risks.

It should also be reviewed when changes to the processing could affect the risks identified.

For clinical research organisations, a DPIA can help bring data protection considerations into the planning of a study or data processing activity, rather than leaving them to be addressed after arrangements have already been implemented.

It is also important to establish the respective responsibilities of controllers and processors. Contractual arrangements, practical responsibilities and the way data is actually processed should be consistent with the applicable GDPR requirements.

What Should Clinical Research Organisations Review?

The findings in this case provide a useful opportunity to review existing data protection arrangements. Organisations may wish to consider the following questions.

  • Anonymisation and pseudonymisation: Have we assessed whether individuals could still be identified from the data we hold, including when records are linked or combined with other information?
  • Lawful processing: Have we documented an appropriate legal basis and condition for processing health data for each relevant purpose?
  • Transparency: Are our privacy notices accurate, clear and consistent with the way data is actually used?
  • Retention: Have we established and documented appropriate retention periods for different categories of personal data?
  • Security: Are our technical and organisational measures appropriate for the risks associated with the data and processing activities?
  • DPIAs: Have we assessed whether a DPIA is required, and are existing assessments reviewed when circumstances change?
  • Third parties: Are responsibilities for data protection clearly defined and understood by the organisations involved?

These questions can be considered as part of routine compliance monitoring, supplier oversight, data protection reviews and the preparation of new research activities.

They are also relevant to staff training. Policies and procedures are important, but the people responsible for implementing them need to understand what those requirements mean for their own work.

GDPR Knowledge Matters Across Clinical Research

Data protection is not solely the responsibility of a data protection officer or legal team. Depending on their roles, clinical operations, data management, quality assurance, investigators and external service providers may all have responsibilities that affect how personal data is handled.

A recent enforcement decision involving a €7 million fine demonstrates the importance of getting the fundamentals right, from establishing a lawful basis for processing to ensuring that data described as anonymous really is anonymous.

Regular training can help staff understand the requirements relevant to their responsibilities, recognise potential risks and know when to seek further advice.

Need to Refresh Your Team’s GDPR Knowledge?

Our online GDPR in Clinical Trials course covers the data protection requirements relevant to clinical research, helping learners understand key principles and how they apply to their work.

Whether you are refreshing existing knowledge or supporting colleagues who need a clearer understanding of GDPR in clinical research, the course provides a practical way to build that knowledge.

Explore our GDPR in Clinical Trials course

You Might Also Like: