Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one
Contents

Academy · Research Publication · Data protection in proposals

Writing the Data Protection and Human Protection Section of a Research Proposal under the GDPR

Reviewers do not assess this section on whether applicants promise compliance. They assess whether specific decisions have been made — who the controller is, what the legal basis is, who pseudonymises which data and where the key is held — and whether the commitments made are ones the design can honour. The most common failure is a paragraph of assurance where a set of answers was required.

Pubrica AcademyWritten by the medical writing and biostatistics teams Reviewed byPubrica biostatistics team Published9 October 2026 Last checked9 October 2026 Reading time13 minutes Sources30 peer-reviewed

The data-protection paragraph is often the last part of a proposal to be written and the first part a reviewer tests. It is also the only section of a proposal in which a single inaccurate sentence — that the data will be anonymised, or that consent is the legal basis — can commit the applicants to something the project cannot deliver and that an ethics committee will later have to correct. This article sets out what the section must state, in what order, and how to write it accurately when the underlying law differs between partner countries.

Learning objectives

  • What reviewers assess in this section, and the six statements they expect
  • How to name the controller, joint controllers and processors in a consortium before the agreement exists
  • How to state a legal basis without claiming unwarranted expertise or overstating the role of consent
  • Why “all data will be anonymised” is usually the most damaging sentence in a proposal
  • What an impact assessment commitment looks like, and when the project needs one
  • How to write a specific secondary-use plan instead of relying on broad consent

Common misconceptions

  • “Stating that the project complies with the GDPR is the point of the section.” A compliance assertion is unscoreable. The section exists to record decisions: roles, basis, minimisation, security, transfers, retention and reuse.
  • “Consent is our legal basis, so we will say so.” The GDPR provides six legal bases and the European Commission’s eleven questions and answers on the Clinical Trials Regulation concluded that consent will not be appropriate in most cases. The proposal should state who determined the basis, not that the participant’s signature supplies it.
  • “Promising anonymisation is the safe option.” The reverse is the case. Where the research question requires clinical granularity, anonymisation is unachievable and the commitment cannot be honoured; the proposal should describe pseudonymisation and state this explicitly.
  • “Broad consent will cover future work on the dataset.” The European Data Protection Board has pointed out that “broad consent” does not appear in the GDPR, and that the Regulation’s flexibility for research does not displace purpose specification.
  • “Data protection is a separate section from human protection.” Reviewers read them together, and a proposal that satisfies the Declaration of Helsinki while leaving the controller unnamed appears incomplete.

Criteria applied by reviewers

This section is not scored on sincerity. A reviewer with a clinical or methodological background assesses three matters, each of which can be answered from the text of the proposal.

Whether a competent person has already been consulted. A section stating that the legal basis was confirmed by the institution’s data protection officer, and naming the national implementing law, reads very differently from one that merely recites the Regulation. The former implies a process; the latter implies an internet search. Authors need not be lawyers to write this section well, but they must have consulted the appropriate legal adviser and recorded the answer.

Whether the project can honour its own commitments. Most sections fail at this point. The statement “All data will be fully anonymised” alongside a work package on deep phenotyping is a contradiction that a reviewer will identify immediately. The same applies to a promise of deletion on withdrawal in a study with regulatory retention obligations. Reviewers do not penalise complexity; they penalise commitments that the design makes impossible.

Whether roles are settled within a consortium. Multi-partner proposals routinely leave controllership undefined, so that no party can say who answers a participant’s access request or notifies a breach. Stating the intended allocation, and committing to a written agreement before recruitment, requires little effort and appears considerably more mature than silence.

The remainder of this article addresses those three judgements. The Pubrica grant writing guide addresses the remainder of the proposal, and the difference between a proposal and a protocol is relevant here, because the proposal establishes the commitment and the protocol operationalises it.

Six required statements

Written in this order, the section reads as a chain of decisions rather than a list of reassurances. Each block occupies two to four sentences in a typical proposal; none of them requires legal language.

First, roles: who is controller, who are joint controllers, who are processors, and when the agreement recording that will be concluded. Second, legal basis: what basis and special-category condition the institution has identified, under which national law, and who confirmed it. Third, what is collected and why: the minimisation argument, made from the research question rather than asserted. Fourth, identifiability: pseudonymisation at what point, with the key held where and accessible to whom, and an accurate statement of whether the dataset is anonymous. Fifth, security, impact assessment and transfers: the infrastructure, whether a data protection impact assessment is required and when it will be done, and the mechanism for any transfer outside the European Economic Area (EEA). Sixth, retention and reuse: how long, who archives, what secondary uses are intended specifically, and what would require fresh approval.

A seventh block should be added where the funder requests it separately: participant-facing documents, meaning a one-line commitment that the information sheet will state the controller, purposes, basis, recipients, retention, rights and the data protection officer’s contact, and will not describe pseudonymised data as anonymous.

The six blocks, what to state, and what loses marks

BlockWhat to stateWhat reviewers mark down
1. RolesController; joint controllers and the agreement date; processors; who answers an access request and notifies a breachA consortium diagram with no controller named anywhere in the data section
2. Legal basisThe basis and special-category condition identified by the institution, the national implementing law, and who confirmed it; that research consent is not relied on as the basisAsserting consent as the basis, or reciting the Regulation instead of naming a decision
3. MinimisationEach identifying variable justified from the research question; the variables deliberately not collected; a free-text review step“Only necessary data will be collected” with no reference to the study’s own variables
4. IdentifiabilityPseudonymisation at what point; where the key is held and who can reach it; an explicit statement that the dataset is pseudonymised, not anonymous“All data will be anonymised” in a proposal whose design requires clinical granularity
5. Security, DPIA, transfersNamed infrastructure and access controls; whether an impact assessment is required and that it precedes recruitment; the mechanism for each non-EEA recipient“Stored securely on encrypted servers”; silence about a non-European partner
6. Retention and reuseRetention period and archive; when the key is destroyed; the specific secondary uses intended; what triggers fresh approvalOpen-ended future use justified by broad consent, which the EDPB notes is not a GDPR term

Blocks derived from the transparency and accountability requirements of the GDPR as interpreted in European Commission and EDPB guidance, with the review observations drawn from Pubrica’s own experience of proposal revisions. National implementing conditions differ; blocks 2 and 6 should be confirmed with the institution.

Stating the legal basis without overclaiming

Authors most often err on this sentence, and in both directions: either asserting a legal basis they are not in a position to determine, or omitting the question entirely because it is perceived as another party’s responsibility.

The structural facts are not in dispute. Christofidou and colleagues, in Frontiers in Medicine, note that the GDPR provides six legal bases for processing and that consent is only one of them. Health data additionally require a condition permitting the processing of a special category of data, and both the basis and the condition can be affected by national implementing law, because the Regulation expressly permits Member States to add conditions for health and genetic data 19. 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 European Data Protection Board addressed the same interplay in its Opinion 3/2019 12.

The implication for the proposal is a form of words rather than a legal position. The proposal should state that the institution, as controller, has identified the basis and the special-category condition; name the national law; and state that the data protection officer confirmed it, with a date where available. It should then add the sentence that prevents the most common downstream problem: that participants’ informed consent to the research is obtained as an ethical requirement and is not relied upon as the legal basis for processing. Gefenas and colleagues, in Medicine, Health Care and Philosophy, describe how easily these two consents are conflated, and a proposal that separates them signals that the team knows the difference 7.

Where partners are located in different countries, the proposal should state this and confirm that the basis has been confirmed per site. A reviewer with cross-border experience knows that this varies; a proposal that implies uniformity across the EU appears uninformed rather than confident.

Data minimisation as a design argument

Data minimisation is commonly written as a virtue — “only data necessary for the research objectives will be collected” — which is both unfalsifiable and uninformative. A statement that scores well is an argument tied to the study’s own variables.

The proposal should name the identifying variables being collected and justify each one from the research question. If date of birth is required rather than year, it should state which analysis requires it. If postcode is collected, it should state the purpose of that geographic resolution and the level at which it will be aggregated before analysis. If an item a reviewer might expect is not collected — full address, employer, national identifier — the proposal should say so, because a stated omission is evidence of a decision.

Free text warrants a separate sentence. Adverse event narratives, interview transcripts and investigator comments are where identifiers accumulate, and they are rarely mentioned in proposals. A commitment to a structured free-text review step before any dataset leaves the collecting site is concrete, inexpensive and seldom offered. Chassang, writing in ecancermedicalscience, and Rumbold and Pierscionek, in the Journal of Medical Internet Research, both identified data handling at the point of transfer as where the Regulation would create the most friction for research, and such a review step is a practical response to that concern 15,16.

Pseudonymisation and its distinction from anonymisation

The sentence “all data will be anonymised” appears in a large share of proposals and is accurate in very few of them. Coded data held with a linking key are pseudonymised and remain personal data 15. Mostert and colleagues, in the European Journal of Human Genetics, set out why the familiar choice between obtaining consent and anonymising data breaks down on rich clinical datasets: the detail that survives coding is frequently sufficient to re-identify, particularly in small or rare populations 17.

An accurate description carries no cost with reviewers and provides two forms of protection. It protects the project from a commitment it cannot keep, and it protects the participant-facing documents from a misleading claim. The wording should be specific: pseudonymisation at the recruiting site at the point of data entry; the identity-to-code key held on named institutional infrastructure, under access control separate from the research database, accessible to a stated number of named individuals; the research dataset distributed to partners without the key; and an explicit statement that the dataset is pseudonymised rather than anonymous, with one clause explaining why the research question precludes anonymisation.

Where a derived output is genuinely anonymous — an aggregate table, a model without case-level data — this should be stated separately for that output. Precision about the status of each artefact indicates a team that has considered the question.

Impact assessment, security and transfers

Three commitments belong in this block, each stated in one or two sentences.

The impact assessment. The Regulation requires a data protection impact assessment where processing is likely to result in a high risk to individuals, and processing health data on a large scale is among the situations expressly flagged 19. Most substantial health research projects therefore require one. The proposal should state whether the project requires one, who will complete it, and that it will be completed before the first participant is approached. Reviewers check this timing in particular, because an assessment finished in month eighteen cannot have informed any design decision.

Security. The proposal should name the infrastructure rather than describe it with adjectives. “Encrypted at rest and in transit on the institution’s managed research environment, with role-based access, logged access and multi-factor authentication” is scoreable; “stored securely” is not. The breach notification route and the internal deadline for reporting to the data protection officer should also be included, because that is the control a reviewer can envisage being tested.

Transfers. The proposal should list the recipients located outside the EEA — a central laboratory, a statistical partner, a sponsor affiliate, a cloud region — and state the mechanism relied on for each, and whether it is already in place or remains to be concluded. A proposal that names a non-European partner in the consortium diagram and is silent about transfers in the data section has a visible gap.

A specific secondary-use plan

Funders increasingly expect a dataset to have a life beyond the project, and proposals often respond by promising broad consent for future research. That commitment is weaker than it appears. The European Data Protection Board has observed that the term “broad consent” does not appear in the GDPR at all, and that the flexibility the Regulation allows for research purposes does not permit working around the requirement to specify a purpose 10. The question has not been definitively resolved in litigation, and the position may continue to evolve; a proposal that relies on broad consent as though the matter were settled is relying on the weaker interpretation.

The alternatives are supported by a substantial literature but little operational infrastructure. 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; dynamic consent was favoured in 15 references and meta-consent in 6, while broad consent remained contested 6. Kaye and colleagues describe dynamic consent in the European Journal of Human Genetics and Ploug and Holm describe meta-consent in the BMJ 20,22. Where a project proposes to build such infrastructure, this is a strength worth stating; where it does not, the proposal should not imply otherwise.

Participant preference, however, diverges from regulatory caution. Christofidou and colleagues cite a study reporting up to 98% of participants favouring broad consent for secondary use, 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 more acceptance than the regulatory debate suggests 13. The defensible position in a proposal is to state that the evidence on acceptability and the regulatory guidance currently point in different directions, to list the secondary uses actually intended, and to commit to fresh ethics approval for anything outside that list. Such a section is stronger than an open-ended permission, and reviewers are likely to regard it as such.

6legal bases for processing under the GDPR; consent is one of them
13distinct consent models identified across 60 included publications
98%of participants in one cited study favoured broad consent for secondary use

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. The 98% figure is from a study cited within that review.

Two versions of the data protection paragraph compared

The same project is described twice below. The first version is typical of the drafts Pubrica receives; the second contains no legal expertise that the first lacks, only decisions that were taken and recorded. It is longer by design: every added clause answers a question that a reviewer or an ethics committee would otherwise ask.

The data-protection paragraph of a research proposal

Assurance

All personal data will be handled in full compliance with the General Data Protection Regulation. Participants will provide written informed consent, and all data will be anonymised and stored securely on encrypted servers with access restricted to the research team. The project adheres to the highest ethical standards and approval will be sought from the relevant ethics committee before the study begins.

Who is the controller? Not stated, so nobody can say who answers an access request or reports a breach.

What is the legal basis? Not stated, and the sentence structure implies consent supplies it.

“All data will be anonymised” is a promise the design cannot keep, and it contradicts the study’s own objectives.

“Stored securely on encrypted servers” describes nothing specific enough to assess or to audit.

No impact assessment, no transfer mechanism, no retention period, no reuse plan. Four required decisions are simply absent.

“The highest ethical standards” names no standard. The ICMJE asks for conformity with the Declaration of Helsinki, most recently revised in October 2024.

Decisions

The coordinating institution will act as data controller. The three recruiting hospitals will act as joint controllers under a written agreement to be concluded before recruitment opens, and the statistical partner will act as processor under a data processing agreement. The coordinating institution’s data protection officer has identified the legal basis for processing and the condition relied upon for health data under the applicable national implementing law, confirmed per site; participants’ written informed consent is obtained as a requirement of research ethics and is not relied upon as the legal basis. Records will be pseudonymised at the recruiting site at the point of data entry, with the identity-to-code key held on institutional infrastructure separate from the research database and accessible to two named individuals per site; partners receive the coded dataset without the key. We describe the dataset as pseudonymised rather than anonymous, because the phenotypic granularity the research question requires precludes anonymisation. A data protection impact assessment will be completed before the first participant is approached, as the project involves large-scale processing of health data. The non-EEA analysis partner will receive data under the transfer mechanism already in place at the coordinating institution. Data will be retained for the period specified by the sponsor’s archiving policy, after which the key will be destroyed. The secondary uses we intend are listed in the data management plan; any purpose outside that list will require fresh ethics approval, and we do not rely on broad consent.

Controllership, joint controllership and processing are allocated, with a commitment on when the agreement will exist.

The basis is attributed to the people who determined it, under named national law, and the two kinds of consent are separated in one clause.

Identifiability is described accurately, with the key’s location, the access limit and a one-clause reason why anonymisation is impossible.

The impact assessment is committed to before recruitment, which is the only timing that influences design.

Transfers, retention and key destruction are each given a sentence.

Secondary use is specific, with a stated trigger for fresh approval, and broad consent is explicitly not relied on.

The second version contains no legal expertise that the first lacks. Every difference is a decision that was taken and written down, or a question that was put to a competent person and answered. This is what makes it scoreable: a reviewer can test each clause against the rest of the proposal, which is not possible with an assurance. The second version also never states which legal basis applies, only who determined it. That is the honest limit of what an applicant can write, and reviewers familiar with this area regard it as a sign of competence rather than evasion.

Integration of human protection and data protection

Many funders ask for one section covering both, and reviewers read them together in any case. The two need to be adjacent without being merged, because they answer different questions: whether it is acceptable to involve these participants, and on what ground their information is processed.

The human-protection half should state the ethical framework specifically. The WMA Declaration of Helsinki, revised in October 2024, sets out ethical principles for medical research involving human participants; its 2013 revision was published in JAMA. The Declaration is the standard reference, and the ICMJE requires conformity with it 1,24. Where participants may be vulnerable, the CIOMS International Ethical Guidelines in their fourth edition, issued in 2016, are the instrument to cite — and CIOMS asks for an analysis of what specifically makes these participants susceptible in this study rather than the naming of a category 18. The proposal should also identify the committees to which applications will be made, in which countries, and the sequencing relative to recruitment. Where the project involves a clinical trial, it should state that registration will be completed at or before the enrolment of the first participant, as the ICMJE requires, because reviewers who have seen that deadline missed will look for it 1.

The two halves are joined by a single sentence that warrants careful drafting: that the informed consent participants give is their research consent under the ethical framework, and that the legal basis for processing their data has been determined separately by the controller. That sentence achieves more than any amount of compliance language. The companion Pubrica pages on the regulatory framework for human participants research and on data-protection obligations across the trial lifecycle cover each half in more depth, and the informed consent form page addresses the document that the proposal commits the team to produce.

A final caution: none of this constitutes legal advice, and a proposal is not the place to resolve a legal question. Its purpose is to show that the appropriate questions were put to the appropriate people and that the answers shaped the design. Where an answer is not yet available, the proposal should state that the determination is being sought and from whom; this is accurate and remains scoreable, unlike a confident assertion that later proves incorrect.

Key points

Key points

This section is scored on decisions rather than assurances, and it should state six things: the controller, joint controllers and processors; the legal basis and special-category condition identified by the institution, the applicable national law, and who confirmed them; the identifying variables collected and the reason for each; where pseudonymisation occurs and where the key is held, with an accurate statement that the data are not anonymous; the security arrangements, impact assessment timing and transfer mechanisms; and the retention period, with a specific list of intended secondary uses. A proposal should never promise anonymisation that the design cannot deliver, present participants’ research consent as the legal basis, or rely on broad consent as though it were a settled GDPR concept. Where an answer is not yet available, the proposal should state whose answer is awaited.

Application to your study

Application to your study

  1. Write the roles sentence first. Name the controller, say which partners are joint controllers and which are processors, and commit to a date for the written agreement.
  2. Consult the data protection officer in writing before drafting the section, requesting the legal basis, the special-category condition and the national implementing law for each site. Quote the reply rather than the Regulation.
  3. Search the draft for the word “anonymised” and replace it with an accurate description of pseudonymisation, plus one clause on why the research question precludes anonymisation.
  4. Justify each identifying variable individually. For variables such as full date of birth, postcode and recruitment date, state which analysis requires each, and name the variables deliberately not collected.
  5. Add a free-text review step covering narratives, transcripts and investigator comments before any dataset leaves the collecting site.
  6. Commit the impact assessment to a point before first participant approach, and name who completes it.
  7. List every non-EEA recipient in the consortium and state the transfer mechanism for each, including cloud regions, not only named partners.
  8. Replace any broad-consent sentence with a specific list of intended secondary uses and an explicit trigger for fresh ethics approval.

Frequently asked questions

Six blocks, in this order. Roles: controller, joint controllers, processors, and when the agreement will be concluded. Legal basis: the basis and special-category condition the institution identified, under which national implementing law, and who confirmed it. Minimisation: each identifying variable justified from the research question, together with the variables deliberately not collected. Identifiability: where pseudonymisation happens, where the key is held and who can access it, and an explicit statement that the data are pseudonymised rather than anonymous. Security, impact assessment and transfers. Retention and a specific secondary-use plan. Each block is two to four sentences, and none requires legal language.

Such a statement is permissible but will not score. A compliance assertion is unfalsifiable and tells a reviewer nothing about whether the questions were asked. What distinguishes a strong section is attribution and specificity: that the institution’s data protection officer identified the basis, that the key is held on named infrastructure accessible to a stated number of people, that the impact assessment will be complete before the first participant is approached. Reviewers also test consistency, so a compliance paragraph next to a work package that contradicts it is worse than a shorter, accurate one. Where an answer is not yet available, the proposal should state whose answer is awaited.

Only if they genuinely will be anonymised, which is not the case for most clinical research. Coded data held with a linking key are pseudonymised and remain personal data. Mostert and colleagues, in the European Journal of Human Genetics, explain why the consent-or-anonymise model breaks down on rich clinical data: the detail that survives coding often re-identifies, especially in small or rare populations. Promising anonymisation commits the project to something it cannot deliver and introduces an inaccurate claim into the participant information sheet. The proposal should give the accurate description, add one clause on why the research question precludes anonymisation, and state separately whether a particular derived output is genuinely anonymous.

Almost certainly not, and the proposal should say so explicitly. The GDPR provides six legal bases and 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 Opinion 3/2019. The sentence that prevents the most downstream difficulty is a short one: participants’ written informed consent is obtained as a requirement of research ethics and is not relied upon as the legal basis for processing. The actual basis should then be attributed to the institution that determined it.

Probably, if it processes health data at any scale. The Regulation requires an impact assessment where processing is likely to result in a high risk to individuals, and large-scale processing of special-category data including health data is among the situations expressly flagged. The determination rests with the controller, so the appropriate course is to ask and then state the answer. Reviewers particularly check timing: an assessment completed before the first participant is approached can still change the design, whereas one delivered as a mid-project milestone cannot. The proposal should name who will complete it and when.

Specifically, and without reliance on broad consent. The EDPB has observed that “broad consent” does not appear in the GDPR and that the research flexibilities do not displace purpose specification, so an open-ended permission represents the weaker reading of a genuinely unsettled area. The proposal should list the secondary uses actually intended, state what would fall outside that list and therefore require fresh ethics approval, and describe the access route — normally controlled access under an agreement rather than open deposit. If dynamic-consent or meta-consent infrastructure is being built, this should be stated; Christofidou and colleagues found 13 consent models in the literature and no operational standard.

It depends on the arrangement, and the proposal’s job is to state the intended allocation rather than to leave it open. Typically the coordinating institution is controller, recruiting sites that also process participant data for their own purposes are joint controllers, and analysis or service partners are processors. What matters to a reviewer is that someone is named, that the agreement recording the allocation has a committed date before recruitment, and that the proposal says who answers a participant’s access request and who notifies a breach. Where partners sit in different Member States, note that the basis and conditions have been confirmed per site, because national implementing law differs.

Applicants require their institution’s answers, which are not the same as their own legal opinion. The proposal’s purpose is to demonstrate that the appropriate questions went to the appropriate people and that the answers shaped the design. Nothing on this page constitutes legal advice, and no general guide can determine which basis applies to a given processing operation, what the retention period is, or whether a transfer mechanism covers a particular partner, because all three depend on national implementing law and the institution’s role. The questions should be sent to the data protection officer and ethics committee in writing, the replies retained, and the section written from them.

References

  1. 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
  2. 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
  3. International Committee of Medical Journal Editors. The New ICMJE Recommendations (August 2013). ICMJE. 2013. read 9 October 2026. icmje.org
  4. 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
  5. Committee on Publication Ethics. Core Practices. COPE. read 9 October 2026. equator-network.org
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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
  26. 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
  27. von Elm E, Altman DG, Egger M, Pocock SJ, Gotzsche PC, Vandenbroucke JP; STROBE Initiative. The Strengthening the Reporting of Observational Studies in Epidemiology (STROBE) statement: guidelines for reporting observational studies. BMJ. 2007;335:806-808. read 9 October 2026. care-statement.org
  28. Stern JM, Simes RJ. Publication bias: evidence of delayed publication in a cohort study of clinical research papers. BMJ. 1997;315:640-645. read 9 October 2026. ismpp.org
  29. Easterbrook PJ, Berlin JA, Gopalan R, Matthews DR. Publication bias in clinical research. Lancet. 1991;337:867-872. read 9 October 2026. ismpp.org
  30. 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). Writing the Data Protection and Human Protection Section of a Research Proposal under the GDPR. Pubrica. https://pubrica.com/academy/research/an-overview-of-gdpr-complying-eu-laws-in-writing-a-research-proposal-for-human-protection/

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.

Data protection and human protection section skeleton

The bracketed fields should be completed from the institution’s written answers, inapplicable text deleted, and the order retained. The blocks are sequenced so that each one answers the question the previous one raises. Every bracket should be replaced; an unreplaced bracket is a clear signal that the section was written in haste.

DATA PROTECTION AND HUMAN PROTECTION

1. ROLES
[Coordinating institution] will act as data controller for the study.
[Sites / partners] will act as joint controllers under a written joint
controller agreement to be concluded before recruitment opens.
[Partner] will act as processor under a data processing agreement.
Participant access requests and breach notifications will be handled by
[named role / office] at [institution].

2. LEGAL BASIS
The data protection officer of [institution] has identified the legal basis for
processing and the condition relied upon for the processing of health data as a
special category, under [national implementing law], confirmed on [date].
Where partners are established in other Member States, the basis and condition
have been confirmed per site, as national implementing conditions differ.
Participants' written informed consent is obtained as a requirement of research
ethics and is NOT relied upon as the legal basis for processing.

3. WHAT IS COLLECTED, AND WHY
Identifying variables collected: [list], each required because [reason per item].
Deliberately not collected: [list].
Free text (adverse event narratives / transcripts / investigator comments) will
be reviewed for identifiers before any dataset leaves [collecting site].

4. IDENTIFIABILITY
Records will be pseudonymised at [site] at [point in the workflow].
The identity-to-code key will be held on [named infrastructure], under access
control separate from the research database, accessible to [n] named individuals.
Partners receive the coded dataset without the key.
The dataset is PSEUDONYMISED, not anonymous, because [reason the research
question precludes anonymisation]. [If applicable: the aggregate outputs in
WP[n] are anonymous.]

5. SECURITY, IMPACT ASSESSMENT AND TRANSFERS
Infrastructure: [named environment], encrypted at rest and in transit,
role-based access, access logging, multi-factor authentication.
Breach route: report to [role] within [hours]; notification decision by [role].
A data protection impact assessment [is / is not] required; it will be completed
by [who] before the first participant is approached.
Recipients outside the EEA: [list]. Transfer mechanism for each: [mechanism],
[already in place / to be concluded by date].

6. RETENTION AND SECONDARY USE
Retention: [period] after [milestone], archived by [institution].
The identity-to-code key will be destroyed at [point].
Intended secondary uses: [specific list].
Anything outside that list will require fresh ethics approval. We do not rely on
broad consent. Access by third parties will be via [controlled access route].

7. HUMAN PROTECTION
The study will be conducted in accordance with the Declaration of Helsinki as
revised in October 2024. [Where participants may be vulnerable: the specific features
making these participants susceptible in this study are [analysis], addressed by
[protections], following the CIOMS International Ethical Guidelines, 4th edition
(2016).]
Ethics approvals will be sought from [committees, per country] before
recruitment at each site.
[For trials: the study will be registered in [registry] at or before enrolment of
the first participant.]

8. PARTICIPANT-FACING DOCUMENTS
The information sheet will state the controller, the purposes, the legal basis,
recipients, retention period, participants' rights, and contacts for the data
protection officer and the national supervisory authority. It will describe the
data as pseudonymised rather than anonymous, and will state that withdrawal
stops further collection while data already collected are retained, with the
reason given.

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 this section from the institution’s own determinations, so that every clause is attributable rather than asserted. The teams identify commitments a proposal cannot honour — anonymisation claims, deletion-on-withdrawal commitments, undisclosed non-EEA partners — and replace them with language that withstands scrutiny at review and again at the ethics committee. Pubrica does not provide legal opinions; it specifies precisely what to ask the data protection officer and writes the section around that officer’s reply.

Find something else

Search the Pubrica Academy

Access is free and requires no account. Enter a topic, or open the full library to filter by category, sub-topic or resource type.

Pubrica can review a draft section and the consortium list and identify the decisions that remain outstanding.

A scoping assessment is free and takes two business days. It provides a written assessment of what the work requires and which specialist would undertake it.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.