Contents
On this page
- Concurrent application of two regulatory regimes to a single trial
- Protocol design: decisions that cannot be made retrospectively
- Recruitment: the dual function of the information sheet
- Trial conduct: minimisation, pseudonymisation and transfer
- Withdrawal, erasure and the conflict with retention requirements
- Secondary use and the problem of broad consent
- Publication and data sharing
- Variation by national implementing law
- Key points
- Application to your study
- Frequently asked questions
Academy · Research Publication · GDPR across trial stages
The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research
Data protection is not a publication formality to be addressed at the end of a trial. It applies from protocol design, when the controller and the legal basis for processing must be determined, and European guidance is consistent that consent to take part in the trial is not that legal basis. The obligations that follow differ at each stage, and those most often misapplied by authors concern withdrawal, retention and secondary use.
Most trial teams encounter the GDPR on two occasions: once as a paragraph inserted into the participant information sheet, and once as an obstacle when a collaborator requests the dataset. Both encounters occur too late. The decisions that determine whether a trial is lawful under data-protection law are taken at the protocol stage, often in the absence of those responsible for data protection, and the most common error — treating the participant’s consent to join the study as the legal basis for processing their data — creates problems that emerge years later at withdrawal, at archiving and when individual participant data are shared.
Learning objectives
- Why trial consent and a General Data Protection Regulation (GDPR) legal basis are distinct, and the consequences of conflating them
- The data-protection decisions that belong at protocol design and cannot be made retrospectively
- The content required in the participant information sheet, and three commitments it should never make
- The interaction between withdrawal from a trial and retention of trial records and the right to erasure
- Why “broad consent” for future research is contested, and the position stated by the European Data Protection Board (EDPB)
- The areas that depend on national implementing law rather than on the Regulation
Common misconceptions
- “The participant consented; therefore a GDPR legal basis exists.” The GDPR offers six legal bases and consent is only one. The European Commission’s eleven questions and answers on the interplay between the Clinical Trials Regulation and the GDPR concluded that consent will not be the appropriate legal basis in most cases.
- “Withdrawal requires deletion of the participant’s data.” Withdrawal from a trial stops further data collection. It does not generally require deletion of data already collected, and a promise of deletion in the information sheet creates a commitment that the sponsor cannot honour.
- “The data are anonymous because they are coded.” Coded data held with a key are pseudonymised, not anonymous, and remain personal data. Mostert and colleagues, in the European Journal of Human Genetics, set out why the consent-or-anonymise model fails in this respect.
- “Broad consent covers future use.” The EDPB’s February 2021 health research document states that “broad consent” does not appear in the GDPR, and that the flexibility in Recital 33 does not permit navigating around the purpose-specification principle.
- “Data protection is the sponsor’s responsibility, not the investigator’s.” In multi-centre research the site is frequently also a controller, and the allocation of roles must be documented before recruitment begins.
Concurrent application of two regulatory regimes to a single trial
A clinical trial in Europe is governed simultaneously by research-ethics requirements and by data-protection law, and these ask different questions with different consequences. Research ethics asks whether it is acceptable to enrol this person in this study: that is the territory of the WMA Declaration of Helsinki, revised in October 2024 (its 2013 revision was published in JAMA), of the CIOMS guidelines, and of the relevant ethics committee 18,24. Data-protection law asks a narrower question: on what ground is this organisation processing this person’s health information, and has it informed the person accordingly.
The two regimes use the same word for different concepts, which is the source of most of the confusion. Informed consent in research ethics is a condition of enrolment and an expression of autonomy. Consent under the GDPR is one of six available legal bases for processing, with its own requirements, and, importantly, it is freely withdrawable in a way that would make a trial dataset unusable. Gefenas and colleagues, in Medicine, Health Care and Philosophy, describe informed consent as standing at a cross-road between the two regimes, and Vlahou and colleagues, in Hypertension, argue that law and research ethics require harmonisation in this area rather than reconciliation case by case 7,9.
European guidance has resolved the practical question in one direction. The European Commission issued eleven questions and answers on how the Clinical Trials Regulation interacts with the GDPR and concluded that consent will not be the appropriate legal basis in most cases; the European Data Protection Board addressed the same interplay in its Opinion 3/2019, issued in January of that year 12,14. The working assumption for a trial should therefore be that the legal basis is something other than consent, that the ethics consent sits alongside it, and that the information sheet must describe both without confusing them.
The same trial, two sets of obligations, stage by stage
| Stage | What research ethics asks | What data-protection law adds | Who has to decide |
|---|---|---|---|
| Protocol design | Scientific justification, risk–benefit, ethics committee submission | Controller identity, legal basis and special-category condition, retention, transfers, planned reuse | Sponsor and site institutions, advised by their data protection officers |
| Recruitment | Informed consent to participate, voluntariness, comprehension | Transparency information: purposes, basis, recipients, retention, rights, DPO and authority contacts | Controller drafts; ethics committee reviews the combined document |
| Conduct | Protocol adherence, safety reporting, GCP monitoring | Minimisation, pseudonymisation at source, access control, breach notification, transfer mechanisms | Sponsor and site, operationally |
| Withdrawal | The participant may stop at any time, without reason or penalty | Further collection stops; erasure of data already collected is generally not required, and regulatory retention continues | Controller, with the DPO, on the facts of the request |
| Secondary use | Whether the new purpose falls within what participants agreed to | Purpose specification; the EDPB states that “broad consent” does not appear in the GDPR | Controller and ethics committee, and in some cases the participants again |
| Publication and sharing | Complete and honest reporting; registration; ethics statement | No residual identifiers; sharing normally under controlled access rather than open deposit | Authors, with the controller’s sign-off on any data release |
Research-ethics column from the Declaration of Helsinki (2013 revision), CIOMS and the ICMJE Recommendations. Data-protection column described from the GDPR as interpreted in the European Commission’s questions and answers on the Clinical Trials Regulation and the EDPB’s Opinion 3/2019 and February 2021 health research document. National implementing laws add further conditions that differ between Member States; this table is an orientation, not a compliance determination.
Protocol design: decisions that cannot be made retrospectively
Four matters must be settled before the first participant is approached, because each determines the content of documents that participants will sign.
Who is the controller. In a sponsor-led multi-centre trial the sponsor is usually the controller, but sites often process data for their own purposes as well, which can make them controllers in their own right or joint controllers. The allocation determines who responds to a participant’s access request, who notifies a breach, and who is accountable to a regulator. The allocation should be documented in the protocol and in the site agreement rather than identified during an audit.
What the legal basis is. Health data need both a legal basis for processing and an additional condition permitting the processing of a special category of data 19. Which combination applies depends on national implementing law and on whether the processing is for the trial itself, for safety reporting, or for future research. This is the institution’s determination, taken with its data protection officer.
What is collected and why. Data minimisation is not merely a reporting principle but a design constraint: each variable must be justified by the protocol’s objectives 19. A case report form that collects the full date of birth where the year of birth would suffice creates an avoidable identifiability problem for the whole study. The same principle applies to free-text fields, in which identifiers tend to accumulate unnoticed.
What happens afterwards. Retention periods, archiving arrangements, transfers outside the European Economic Area (EEA), and whether the dataset will be shared or reused must all be described to participants at the outset. Deciding them later requires a return to the ethics committee and, in some cases, to the participants. The Pubrica notes on the clinical study protocol describe where each of these belongs in the document.
Recruitment: the dual function of the information sheet
The participant information sheet is where the two regimes meet in a single document, and where they are most often confused. It must obtain informed consent to participation in the research and, separately, provide the transparency information that data-protection law requires: who the controller is, why the data are being processed and on what basis, who else will have access to them, how long they will be kept, what rights the participant has and how to exercise them, and how to contact the data protection officer and the national supervisory authority 10,19.
Three commitments recur in the information sheets that Pubrica is asked to review, and none of them should be included. The first is that the data are anonymous: in a trial with a code key and a monitoring trail, they are not, and such a statement misleads the participant and misstates the sponsor’s obligations 15,17. The second is that consent is the legal basis for processing, which contradicts the Commission’s own conclusion and makes the dataset vulnerable to withdrawal 14. The third is that all of a participant’s data will be deleted on withdrawal, which is a commitment the sponsor usually cannot honour and should not make.
Our page on the informed consent form covers the ethical content of the document; the following section addresses the data-protection paragraph specifically, in a problematic version and in an appropriate version.
The data-protection paragraph of a participant information sheet
Three commitments that cannot be honoured
By signing this form you consent to the processing of your personal data in accordance with the General Data Protection Regulation. All information collected about you will be kept strictly confidential and anonymous. You may withdraw your consent at any time, at which point all of your data will be permanently deleted from the study.
It makes consent the legal basis. European Commission guidance concluded that consent will not be the appropriate basis in most trials, and framing it in this way makes the dataset vulnerable to withdrawal.
It calls coded data anonymous. Data held with a linking key are pseudonymised and remain personal data; the sentence misleads the participant and misstates the sponsor’s duties.
It promises deletion on withdrawal. Regulatory retention obligations and the integrity of the analysis mean that this commitment usually cannot be honoured, so the information sheet creates a conflict for whoever receives the request.
It names no controller, no DPO and no authority. The transparency information that the Regulation requires is absent.
It conflates two consents. A participant reading this paragraph cannot determine what they are agreeing to or what they can withdraw.
Accurate, and still readable
The study sponsor is the data controller and is responsible for looking after your information. We process health information for this study because the research is carried out in the public interest; your agreement to take part is recorded separately as your informed consent to the research, and is not the legal ground on which we process your data. Your records will carry a study code and will be held separately from your name, so the research team can identify you but people outside it cannot; this is not the same as being anonymous. You can stop taking part at any time, without giving a reason and without any effect on your care. If you stop, we will not collect any further information about you, but information already collected will be kept and included in the analysis, both because removing it would make the results unreliable and because we are required to keep the trial records for a defined period. You can ask for a copy of your information or ask us to correct it, you can contact our data protection officer, and you can complain to the national data protection authority.
The controller is named and the legal basis is stated as something other than consent, with the ethics consent kept visibly separate.
Pseudonymisation is described in plain language, and the information sheet states explicitly that it is not anonymity.
Withdrawal is described accurately: collection stops, existing data are retained, and the two reasons are given.
The rights that apply are listed, with routes to the data protection officer and the supervisory authority.
No commitment is made that the sponsor would be unable to honour.
The second version is approximately eighty words longer and removes four separate ways in which the first can fail — at an ethics committee, at a withdrawal request, at an audit, and at the point at which a participant realises that their data were described as anonymous when they were not. It also informs the participant accurately about withdrawal before the information is needed, which is the only point at which that statement can be made honestly. The exact legal basis and retention period should be confirmed with the relevant controller before any wording of this kind is used.
Trial conduct: minimisation, pseudonymisation and transfer
Once recruitment is under way, the obligations become operational rather than documentary, and they overlap substantially with the requirements of good clinical practice (GCP). Data should be pseudonymised at source: the participant identification code is held separately from the identity file, with access restricted to named individuals. The linking key should be kept under a different access control from the research dataset, because the two held together constitute identifiable data. Access should be logged, as both GCP monitoring and data-protection accountability require.
Free text is a persistent hazard. Adverse event narratives, protocol deviation notes and investigator comments are where names, dates, place names and relationships tend to appear, and they are the fields least likely to be reviewed before a dataset leaves the sponsor. A free-text review step should be built into data cleaning rather than deferred to the publication stage.
Transfers are the other recurring issue. Sending data to a coordinating centre, a central laboratory, a statistical group or a sponsor outside the EEA requires a transfer mechanism, and this is a question for the controller’s legal function rather than for the trial statistician. The practical requirement for an investigator is to establish which mechanism is in place before agreeing to send any data, and to keep the answer on file. Chassang, writing in ecancermedicalscience, and Rumbold and Pierscionek, in the Journal of Medical Internet Research, both anticipated that cross-border research collaboration would be the area in which the Regulation had the greatest impact, and this has broadly been borne out 15,16.
Withdrawal, erasure and the conflict with retention requirements
Withdrawal is the stage at which a well-intentioned information sheet can cause considerable harm. A participant who withdraws from a trial is exercising a right under research ethics: they stop receiving the intervention and no further data are collected about them. Whether their existing data must be erased is a separate question, and the answer is usually no — because the trial sponsor is under regulatory obligations to retain trial records, because removing data already in a locked analysis dataset would compromise the integrity of the results, and because the right to erasure under the GDPR is qualified rather than absolute and does not apply where processing rests on a basis other than consent and is necessary for a public-interest or research purpose 19.
The European Commission’s questions and answers address this intersection directly, and their conclusion is a practical one: withdrawal of consent to trial participation is not the same event as withdrawal of a data-protection consent, and the regulatory retention requirements continue to apply 14. The consequence for the information sheet is that it must inform the participant accurately in advance — that stopping means no further collection, that information already collected will be kept and analysed, and why.
Where the position is unsettled, this should be acknowledged rather than presented with false certainty. National implementing laws differ in how they frame the research exemptions, and an institution in one Member State may take a materially different view from one in a neighbouring state. This page does not constitute legal advice, and a withdrawal accompanied by a specific erasure request should be referred to the data protection officer on the same day.
Secondary use and the problem of broad consent
Most contemporary protocols seek to allow future research on the same dataset or samples, and “broad consent” is the term usually invoked. Its legal basis is weaker than most protocols assume. The EDPB’s February 2021 document on health research states, at paragraphs 25 to 26, that the term “broad consent” does not appear in the GDPR at all, and that the flexibility offered by Recital 33 does not permit navigating around the purpose-specification principle 10. That is a narrower reading than the research community had anticipated, and it has not been definitively tested 10.
The alternatives are discussed in the academic literature but do not yet have an operational standard. Christofidou and colleagues, in Frontiers in Medicine, screened 6,780 records, removed 415 duplicates and included 60 publications, identifying 13 distinct consent models for the reuse of health data 6. Dynamic consent was the model most often favoured, with 15 references, followed by meta-consent with 6, while broad consent remained contested 6. Kaye and colleagues set out dynamic consent in the European Journal of Human Genetics and Ploug and Holm set out meta-consent in the BMJ; both require infrastructure that most trials lack.
Participant preference, by contrast, diverges from regulatory caution. Christofidou and colleagues cite a study reporting that up to 98% of participants favoured broad consent for secondary use of their data, and Richter and colleagues, in the European Journal of Human Genetics, asked whether research use of clinical data without consent is not only legal but also acceptable to patients, and found greater acceptance than the regulatory debate suggests 13. The question therefore remains open: the law, the ethics literature and participant opinion have not converged, and a protocol should describe the future use it intends in specific terms rather than relying on an open-ended permission.
Source: Christofidou M, Arvanitis TN, Kalra D, Lea N, Shabani M, Coorevits P. Data altruism and the ‘consent’ question: a study into the ‘consent’ models used under the GDPR. Frontiers in Medicine.
Publication and data sharing
By the manuscript stage, the data-protection work should already be complete, and the remaining tasks concern reporting. The ethics approval and the registration should be stated in the Methods: the ICMJE requires that research conform to the Declaration of Helsinki, most recently revised in October 2024, that approval by an independent ethics committee or institutional review board be stated, and that trials be registered in a public registry at or before the time of first patient enrolment 1,27. Retrospective registration at submission does not satisfy that policy, and no degree of data-protection diligence compensates for its absence.
Individual participant data sharing is a further point at which the two regimes conflict. A journal or funder data-availability requirement does not override data-protection law, and the resolution is normally controlled access under an agreement rather than an open deposit 9,19. The statements in the protocol and information sheet about sharing determine what is possible, which is the strongest practical argument for settling the matter at the design stage. Vlahou and colleagues, in Hypertension, argue that sharing and the Regulation require harmonisation at the policy level because individual teams cannot resolve the tension on their own.
Within the manuscript itself, the text should be checked for residual identifiers before submission: free-text adverse event descriptions, small-cell subgroup tables, verbatim quotations in qualitative components, and figure axes that reveal recruitment dates by site. The Pubrica reporting guidelines hub covers the CONSORT items that interact with this, and the ICH guidelines guide covers the GCP side of record retention.
Variation by national implementing law
The GDPR is a Regulation rather than a Directive, which is often taken to imply uniformity. For health research it does not. The Regulation expressly permits Member States to maintain or introduce further conditions for processing health and genetic data and to legislate derogations for scientific research purposes, and they have done so differently 19. Crowhurst and colleagues, in Nurse Researcher, examine the implications for retrospective reviews of patients’ data and reach a conclusion that is necessarily country-specific 11. The practical effect is that a multinational trial can face materially different requirements at different sites for the same protocol.
The commentary also differs on the magnitude of the effect. Casali’s European Society for Medical Oncology position paper in Annals of Oncology warned that the Regulation posed substantial risks to clinical research, while Rumbold and Pierscionek, in the Journal of Medical Internet Research, reached a more measured assessment 15,23. Both were written before the operational guidance had been established, and neither has been decisively confirmed.
The practical implication for a research team is straightforward. The data-protection section of the protocol should be treated as a set of questions for the institution rather than a passage to be drafted from the Regulation; the answers should be obtained in writing, and the national implementing law applied at each site should be recorded. The companion Pubrica page on writing the data-protection section of a proposal describes how to present those answers to a funder, and the regulatory framework for research with human participants places the data-protection requirements in the wider ethical context.
Key points
Key points
Data-protection obligations in a trial are determined at the protocol stage and frequently become apparent only at withdrawal. Four matters should be settled before recruitment: the identity of the controller, the legal basis and special-category condition, the data collected, and the subsequent handling of the data. It should be assumed that the legal basis is not consent — the European Commission’s questions and answers concluded that consent will not be appropriate in most cases — and the ethics consent should be kept visibly separate from it in the information sheet. Anonymity should never be promised for coded data, nor deletion on withdrawal. Secondary use should be treated as a specific plan rather than a broad permission, because the EDPB has stated that “broad consent” does not appear in the GDPR at all.
Application to your study
Application to your study
- The controller should be identified in the protocol at the outset. The protocol should name the controller and state whether sites are processors, controllers or joint controllers before any site agreement is signed.
- The legal basis and the special-category condition should be obtained in writing from the data protection officer, and the national implementing law applied at each site should be recorded.
- The case report form should be audited for over-collection. Every variable should map to a protocol objective; full dates of birth should be replaced with years where the analysis permits.
- The data paragraph of the information sheet should be revised. Any claim of anonymity, any statement that consent is the legal basis and any promise to delete data on withdrawal should be removed.
- A free-text review step should be added to data cleaning, covering adverse event narratives, deviation notes and investigator comments, rather than relying on identifiers being detected at publication.
- The transfer mechanism should be confirmed before data are sent outside the European Economic Area (EEA), including to a central laboratory or statistical group, and the confirmation should be retained on file.
- Intended secondary use should be described specifically in the protocol rather than relying on a broad permission, together with a statement of what would require fresh approval.
- The trial should be registered at or before first enrolment and the ethics, consent and registration statements should be written into the Methods while the details remain readily available.
Frequently asked questions
Usually not. The GDPR provides six legal bases, of which consent is one; the European Commission’s eleven questions and answers on the interplay between the Clinical Trials Regulation and the GDPR concluded that consent will not be the appropriate legal basis in most cases, and the EDPB addressed the same interplay in its Opinion 3/2019. The practical reason is that GDPR consent must be freely withdrawable, which would make trial datasets unusable. Research-ethics informed consent remains an absolute requirement for enrolment; it fulfils the ethical function rather than the data-protection one. The basis that applies to a given trial is a determination for the institution as controller.
Generally no, although the answer depends on the national implementing law and on what the information sheet promised. Withdrawal from a trial means that no further data are collected. Data already collected are normally retained, because sponsors are under regulatory obligations to keep trial records, because removing records from a locked analysis dataset would compromise the results, and because the right to erasure is qualified rather than absolute and is limited where processing rests on a basis other than consent. The principal consequence is prospective: all of this should be stated in the information sheet before the participant signs, rather than the conflict being discovered when the request arrives.
The EDPB’s February 2021 health research document states, at paragraphs 25 to 26, that the term “broad consent” does not appear in the GDPR, and that the flexibility in Recital 33 does not permit navigating around the purpose-specification principle. That is a narrow reading and it has not been settled by litigation, so further developments are likely. Christofidou and colleagues, in Frontiers in Medicine, identified 13 distinct consent models across 60 included publications, with dynamic consent favoured in 15 references and meta-consent in 6, and broad consent contested. At present, protocols should describe the intended secondary use in specific terms and state what would require fresh approval.
Yes. Coded data held alongside a linking key remain personal data under the GDPR, and describing them as anonymous in a participant information sheet is both inaccurate and a misstatement of the sponsor’s obligations. Mostert and colleagues, in the European Journal of Human Genetics, set out why the familiar choice between obtaining consent and anonymising data breaks down for rich clinical datasets: the clinical detail that survives coding is frequently sufficient for re-identification. Anonymisation is a high threshold that most trial datasets do not meet, particularly in small populations, and pseudonymisation is the accurate description of what nearly all trials do.
It depends on the arrangement, and it must be decided in advance. In sponsor-led trials the sponsor is typically the controller, but sites often process participant data for their own clinical and governance purposes as well, which can make them controllers in their own right or joint controllers with the sponsor. The allocation determines who answers an access request, who notifies a breach, and who is accountable to a supervisory authority. It should be documented in the protocol and the site agreement. Where sites are located in different Member States, different implementing conditions may apply to each of them for the same protocol.
Neither overrides the other, which is why the matter must be addressed at the design stage rather than resolved at submission. A funder or journal requirement to make individual participant data available does not create a lawful basis for releasing identifiable data, and data-protection law does not exempt authors from providing a data-availability statement. In practice, the workable solution is controlled access under a data-sharing agreement, with a statement explaining the access route. What is possible is determined by what the protocol and the information sheet told participants about sharing, so the matter should be decided at the design stage. Vlahou and colleagues, in Hypertension, argue that this requires resolution at the policy level rather than by individual teams.
No, and this is the most common misconception about it. Although it is a Regulation rather than a Directive, it expressly allows Member States to maintain or introduce further conditions for processing health and genetic data, and to legislate derogations for scientific research. They have done so differently, so a multinational trial can face materially different requirements at different sites for one protocol. Crowhurst and colleagues, in Nurse Researcher, examine the implications for retrospective reviews of patient data and reach a country-specific conclusion. The national law applied at each site should be recorded, and the position confirmed with each site’s data protection officer.
No. This page describes the nature of the obligations and the published guidance that interprets them, and it is explicit about where national implementations differ and where the position is unsettled. It cannot determine which legal basis applies to a given trial, what the retention period is, or whether a specific erasure request must be honoured, because all three depend on the jurisdiction, the institution’s role and the national implementing law. These questions should be sent in writing to the data protection officer or ethics committee, the answers kept in the trial master file, and this page used to identify which questions to ask.
References
- International Committee of Medical Journal Editors. Recommendations for the Conduct, Reporting, Editing, and Publication of Scholarly Work in Medical Journals. ICMJE. 2026. read 9 October 2026. icmje.org
- Tam NT, Huy NT, Thoa TB, Long NP, Trang NT, Hirayama K, et al. Participants' understanding of informed consent in clinical trials over three decades: systematic review and meta-analysis. Bulletin of the World Health Organization. 2015;93:186-198H. doi:10.2471/BLT.14.141390 read 9 October 2026. doi.org/10.2471/BLT.14.141390
- International Committee of Medical Journal Editors. The New ICMJE Recommendations (August 2013). ICMJE. 2013. read 9 October 2026. icmje.org
- World Health Organization. Standards and Operational Guidance for Ethics Review of Health-Related Research with Human Participants. WHO. 2011. read 9 October 2026. equator-network.org
- Committee on Publication Ethics. Core Practices. COPE. read 9 October 2026. equator-network.org
- Christofidou M, Arvanitis TN, Kalra D, Lea N, Shabani M, Coorevits P. Data altruism and the 'consent' question: a study into the 'consent' models used under the GDPR and how the data altruism mechanism can act as a potential solution for the research community in the reuse of health data. Frontiers in Medicine. 2025;11:1489925. doi:10.3389/fmed.2024.1489925 read 9 October 2026. doi.org/10.3389/fmed.2024.1489925
- Gefenas E, Lekstutiene J, Lukaseviciene V, Hartlev M, Mourby M, Cathaoir KO. Controversies between regulations of research ethics and protection of personal data: informed consent at a cross-road. Medicine, Health Care and Philosophy. 2022;25:23-30. doi:10.1007/s11019-021-10060-1 read 9 October 2026. doi.org/10.1007/s11019-021-10060-1
- DeTora LM, Toroser D, Sykes A, Vanderlinden C, Plunkett FJ, Lane T, Hanekamp E, Dormer L, DiBiasi F, Bridges D, Baltzer L, Citrome L. Good Publication Practice (GPP) Guidelines for Company-Sponsored Biomedical Research: 2022 Update. Annals of Internal Medicine. 2022;175(9):1298-1304. doi:10.7326/M22-1460 read 9 October 2026. doi.org/10.7326/M22-1460
- Vlahou A, Hallinan D, Apweiler R, Argiles A, Beige J, Benigni A, et al. Data sharing under the General Data Protection Regulation: time to harmonize law and research ethics? Hypertension. 2021;77:1029-1035. doi:10.1161/HYPERTENSIONAHA.120.16340 read 9 October 2026. doi.org/10.1161/HYPERTENSIONAHA.120.16340
- European Data Protection Board. Document on response to the request from the European Commission for clarifications on the consistent application of the GDPR, focusing on health research. EDPB. 2021. read 9 October 2026. ejprarediseases.org
- Crowhurst N, Bergin M, Wells J. Implications for nursing and healthcare research of the General Data Protection Regulation and retrospective reviews of patients' data. Nurse Researcher. 2019;27(1):45-49. doi:10.7748/nr.2019.e1639 read 9 October 2026. doi.org/10.7748/nr.2019.e1639
- European Data Protection Board. Opinion 3/2019 concerning the Questions and Answers on the interplay between the Clinical Trials Regulation and the GDPR. EDPB. 2019. read 9 October 2026. lw.com
- Richter G, Borzikowsky C, Lieb W, Schreiber S, Krawczak M, Buyx A. Patient views on research use of clinical data without consent: legal, but also acceptable? European Journal of Human Genetics. 2019;27:841-847. doi:10.1038/s41431-019-0340-6 read 9 October 2026. doi.org/10.1038/s41431-019-0340-6
- European Commission, Directorate-General for Health and Food Safety. Questions and Answers on the interplay between the Clinical Trials Regulation and the General Data Protection Regulation. European Commission. 2019. read 9 October 2026. research.uci.edu
- Rumbold JMM, Pierscionek BK. The effect of the General Data Protection Regulation on medical research. Journal of Medical Internet Research. 2017;19(2):e47. doi:10.2196/jmir.7108 read 9 October 2026. doi.org/10.2196/jmir.7108
- Chassang G. The impact of the EU general data protection regulation on scientific research. ecancermedicalscience. 2017;11:709. doi:10.3332/ecancer.2017.709 read 9 October 2026. doi.org/10.3332/ecancer.2017.709
- Mostert M, Bredenoord AL, Biesaart MC, van Delden JJ. Big data in medical research and EU data protection law: challenges to the consent or anonymise approach. European Journal of Human Genetics. 2016;24:956-960. doi:10.1038/ejhg.2015.239 read 9 October 2026. doi.org/10.1038/ejhg.2015.239
- Council for International Organizations of Medical Sciences. International Ethical Guidelines for Health-related Research Involving Humans, 4th edition. CIOMS. 2016. read 9 October 2026. equator-network.org
- European Union. Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 (General Data Protection Regulation). Official Journal of the European Union. 2016. read 9 October 2026. frontiersin.org
- Kaye J, Whitley EA, Lund D, Morrison M, Teare H, Melham K. Dynamic consent: a patient interface for twenty-first century research networks. European Journal of Human Genetics. 2015;23:141-146. doi:10.1038/ejhg.2014.71 read 9 October 2026. doi.org/10.1038/ejhg.2014.71
- Battisti WP, Wager E, Baltzer L, Bridges D, Cairns A, Carswell CI, Citrome L, Gurr JA, Mooney LA, Moore BJ, Pena T, Sanes-Miller CH, Veitch K, Woolley KL, Yarker YE. Good Publication Practice for Communicating Company-Sponsored Medical Research: GPP3. Annals of Internal Medicine. 2015;163(6):461-464. doi:10.7326/M15-0288 read 9 October 2026. doi.org/10.7326/M15-0288
- Ploug T, Holm S. Meta consent: a flexible and autonomous way of obtaining informed consent for secondary research. BMJ. 2015;350:h2146. doi:10.1136/bmj.h2146 read 9 October 2026. doi.org/10.1136/bmj.h2146
- Casali PG; European Society for Medical Oncology. Risks of the new EU Data protection regulation: an ESMO position paper endorsed by the European oncology community. Annals of Oncology. 2014;25:1458-1461. doi:10.1093/annonc/mdu218 read 9 October 2026. doi.org/10.1093/annonc/mdu218
- World Medical Association. Declaration of Helsinki: ethical principles for medical research involving human subjects. JAMA. 2013;310:2191-2194. doi:10.1001/jama.2013.281053 read 9 October 2026. doi.org/10.1001/jama.2013.281053
- Gagnier JJ, Kienle G, Altman DG, Moher D, Sox H, Riley D. The CARE guidelines: consensus-based clinical case reporting guideline development. Journal of Medical Case Reports. 2013;7(1):223. doi:10.1186/1752-1947-7-223 read 9 October 2026. doi.org/10.1186/1752-1947-7-223
- Schulz KF, Altman DG, Moher D. CONSORT 2010 statement: updated guidelines for reporting parallel group randomized trials. Annals of Internal Medicine. 2010;152:726-732. read 9 October 2026. care-statement.org
- Steinbrook R. Public registration of clinical trials. New England Journal of Medicine. 2004;351:315-317. doi:10.1056/NEJMp048191 read 9 October 2026. doi.org/10.1056/NEJMp048191
- Antes G, Chalmers I. Under-reporting of clinical trials is unethical. Lancet. 2003;361:978-979. read 9 October 2026. ismpp.org
- National Commission for the Protection of Human Subjects of Biomedical and Behavioral Research. The Belmont Report: Ethical Principles and Guidelines for the Protection of Human Subjects of Research. US Department of Health, Education, and Welfare. 1978. read 9 October 2026. frontiersin.org
Every source above is a peer-reviewed article, a publisher’s record of one, or a standard issued by the body that owns it. Each carries the date it was last read. Where a standard moves, this article is revised rather than left up with a note.
How to cite this article
Pick your referencing style and copy it. Your university or target journal may vary the punctuation — check its guide if it has one.
Pubrica Academy. (2026, October 9). The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research. Pubrica. https://pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/
Pubrica Academy. “The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research.” Pubrica, 9 Oct. 2026, pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/.
Pubrica Academy (2026) The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research. Pubrica. Available at: https://pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/ (Accessed: 15 October 2026).
Pubrica Academy. “The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research.” Pubrica. October 9, 2026. https://pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/
Pubrica Academy, ‘The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research’ (Pubrica, 9 October 2026) <https://pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/> accessed 15 October 2026.
Pubrica Academy. The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research. [Internet]. Pubrica; 2026 Oct 9 [cited 2026 Oct 15]. Available from: https://pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/
Pubrica Academy, “The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research,” Pubrica, Oct. 9, 2026. [Online]. Available: https://pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/
@misc{how_scientific_paper_published_on_the__2026,
author = {{Pubrica Academy}},
title = {The GDPR in Clinical Trials: Data-Protection Obligations at Each Stage of Clinical Research},
howpublished = {Pubrica},
year = {2026},
month = {oct},
url = {https://pubrica.com/academy/research/how-scientific-paper-published-on-the-stages-of-clinical-research-impacted-by-the-gdpr/},
note = {Accessed: <span data-cite-acc="iso">2026-10-15</span>}
}This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.
Protocol-stage data-protection questions to send your DPO
This list should be sent to the institution’s data protection officer before recruitment opens, and the reply filed in the trial master file. Each question corresponds to an element that must appear in the protocol or the participant information sheet, and none of them can be answered reliably from the text of the Regulation alone.
DATA PROTECTION QUESTIONS FOR THE TRIAL MASTER FILE
Study: ______________________ Sponsor: ______________________
Sites and countries: ______________________
1. ROLES
1.1 Who is the controller for this study?
1.2 Are the participating sites processors, controllers, or joint controllers?
1.3 Which agreement records that allocation, and is it signed?
1.4 Who answers a participant access request, and at which address?
2. LEGAL BASIS
2.1 What is the legal basis for processing participants' personal data?
2.2 What is the additional condition relied on for health data as a special
category?
2.3 Which national implementing law applies at each site?
2.4 Is a separate basis relied on for safety reporting? For future research?
3. INFORMATION SHEET WORDING
3.1 Please confirm the wording for: controller identity, purpose, legal basis,
recipients, retention period, rights, DPO contact, authority contact.
3.2 Please confirm the withdrawal wording -- specifically that collection
stops and existing data are retained, and the stated reason.
3.3 Please confirm that no sentence describes the data as anonymous.
4. DATA HANDLING
4.1 Where is the identity-to-code key held, and under whose access control?
4.2 What is the retention period for the dataset, and for the trial master file?
4.3 What is the breach notification route and the internal deadline?
4.4 Is a data protection impact assessment required for this study?
If yes, who completes it and by when?
5. TRANSFERS
5.1 Which recipients sit outside the EEA (central lab, CRO, statistics,
sponsor affiliate)?
5.2 What transfer mechanism is in place for each?
5.3 Is any further documentation needed before the first transfer?
6. SECONDARY USE AND SHARING
6.1 What future research does the protocol intend, described specifically?
6.2 What would require a fresh approval or a fresh approach to participants?
6.3 If the journal or funder requires individual participant data sharing,
what access route is acceptable, and who signs off a release?
7. SIGN-OFF
Answered by: ______________________ Role: ______________________
Date: __________ Filed in TMF section: __________ Pubrica AcademyWritten and maintained by Pubrica’s subject matter experts. Articles are revised when the underlying standards change, and each article states the date on which it was last reviewed.
How Pubrica can help
Pubrica’s regulatory and medical writing teams draft the protocol and information sheet sections in which these two regimes intersect, so that an ethics committee and a data protection officer can both approve the same document. Pubrica does not issue legal opinions; it converts the institution’s determinations into wording that is accurate about pseudonymisation, transparent about withdrawal and specific about secondary use, and it identifies the questions that remain unanswered before recruitment opens.