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

Start one
Contents

AcademyPublication Support

Regulatory guideEU and Germany

GDPR Article 9 and Manuscript Editing: Can You Send Patient Data to an Editor or an AI Tool?

Removing a patient’s name rarely makes a clinical manuscript anonymous. Before medical manuscript editing by a person or an AI tool, check identifiability, the lawful basis, the recipient’s role and the safeguards in place.

Dr. CharlieSenior Medical WriterPublishedLast checkedReading time7 minutesSources12
  • GDPR
  • Patient data
  • AI tools

At a glancePublication Support

Article 9
Health data is special-category data
You need
Article 6 lawful basis plus an Article 9(2) condition
Pseudonymised
Personal data for the controller
Editors and AI
Processor contract, security and transfer checks

Get secure manuscript editingDiscuss your project

Quick answer

  • Sharing identifiable patient data with an editor or AI tool is processing under the GDPR.
  • Health data needs both an Article 6 lawful basis and an Article 9(2) condition.
  • Pseudonymised data remain personal data for the controller; only genuine anonymisation takes data outside the GDPR.
  • Use an Article 28 contract for editors acting as processors, and check AI providers’ retention, training and transfer terms.

Why patient data protection matters in manuscript editing

During medical manuscript editing, drafts pass to language editors, translators, publishers and AI writing platforms. Each handover can disclose health information. Patient data protection and medical data privacy depend on whether patients remain identifiable, whether the processing is lawful and whether the recipient offers appropriate safeguards; case reports are a common example2.

What does GDPR Article 9 require?

GDPR Article 9 prohibits processing special-category personal data, including data concerning health, unless one of the conditions in Article 9(2) applies1. Diagnoses, histories, treatment records and genetic results all qualify, which is why sensitive health data under GDPR turns up even in routine manuscript details.

Article 9 never works alone. Processing needs a lawful basis under Article 6 and an Article 9(2) condition, such as explicit consent, health care, public health or scientific research under EU or national law1. Consent to join a study does not automatically cover later disclosure to an external editor or AI service, and the Article 5 principles of purpose limitation, data minimisation and security still apply.

Research provisions: Article 9(2)(j) and BDSG § 27

For research, the Article 9(2) condition is often scientific research under Article 9(2)(j). It is not a free-standing exemption: it needs a basis in EU or national law with suitable safeguards, which in Germany is mainly § 27 of the Federal Data Protection Act (BDSG)110.

Table 1. Research provisions that apply to health research manuscripts (summary; check the statutory text)

ProvisionWhat it providesWhy it matters for manuscripts
Art. 9(2)(a) GDPRException where the data subject gave explicit consent1Consent for research is not automatically consent to share with editors or tools
Art. 9(2)(j) and Art. 89(1) GDPRException for scientific research, but only on the basis of EU or Member State law that is proportionate and provides suitable safeguards, such as data minimisation and pseudonymisation1Supports research processing under a national law such as BDSG § 27, not unlimited onward sharing
BDSG § 27(1)German law permits processing of special categories for research without consent where necessary and the controller’s interests substantially outweigh the data subject’s, with specific protective measures10Applies to the research processing by the controller
BDSG § 27(3)Data must be anonymised as soon as the research purpose allows, unless the data subject’s legitimate interests preclude this; identifying features are stored separately until then10Strips identifiers before they travel
BDSG § 27(4)The controller may publish personal data only if the data subject has consented or publication is indispensable for presenting research findings on contemporary events10Identifiable details in a published manuscript generally need consent

These provisions legitimise research processing by the responsible organisation. Whether disclosing data to an external editor or a tool is covered is a separate question to assess with your data protection officer.

Editing a manuscript that contains patient data?

Pubrica’s medical manuscript editors improve clarity, grammar and readability while preserving scientific accuracy, under documented confidentiality and data-handling arrangements.

GDPR and manuscript editing: who is responsible?

In GDPR and manuscript editing arrangements, the party that decides the purposes and means of processing is the data controller: usually the researcher’s hospital, university or sponsor. An external editor handling personal data on the controller’s documented instructions is a data processor, and Article 28 then requires a contract, often called a data processing agreement, covering instructions, confidentiality, security and sub-processors1. A bare confidentiality clause does not replace it, and the recipient’s actual activities, not the label “editor”, decide its role.

An AI platform’s role likewise depends on what it does with content: whether it only provides the requested service, retains submissions, allows human review or uses them to train models.

Table 2. Key GDPR provisions for manuscript editing

GDPR provisionWhy it matters
Article 5Principles: purpose limitation, data minimisation, integrity and confidentiality
Article 6A lawful basis for any processing of personal data
Article 9Additional conditions for health and other special-category data
Article 28A binding contract when a processor acts for a controller
Article 32Appropriate technical and organisational security
Article 35A data protection impact assessment where processing is likely to be high risk
Chapter VRules for transfers of personal data outside the EEA

These provisions work together. A contract with an editor does not, on its own, establish a lawful basis.

Does your manuscript contain personal data?

Personal data in a manuscript is not limited to names. Check every part of the package before it leaves your organisation.

Table 3. Typical personal-data risks in manuscript files

Manuscript itemRiskAction before sharing
Aggregate results tablesLow, unless cells are very smallCheck small cell counts
Case report text and imagesHigh: age, dates, place, rare findings and images can identify a personRemove identifiers; the ICMJE says identifying information should not be published unless it is essential for scientific purposes and the patient gives written informed consent for publication12
Raw or supplementary datasetsHigh: row-level health dataRemove direct identifiers; share only what is needed
File properties, comments, tracked changes, file namesHidden names, emails or patient codesInspect and clean the document
Pseudonymised dataPersonal data for you as controller1Treat as personal data unless your data protection officer concludes otherwise

Anonymisation and pseudonymisation: what is the difference?

Health data anonymisation means no one is identifiable by any means reasonably likely to be used; genuinely anonymous data fall outside the GDPR (Recital 26)1. Pseudonymisation of patient data replaces direct identifiers with codes and keeps the key separately. It lowers risk, but pseudonymised data remain personal data for you as controller (Article 4(5), Recital 26): a safeguard, not an exemption13. The EDPB’s Guidelines 02/2026 on anonymisation are still a draft open for consultation until 30 October 20264.

Since September 2025, the position for recipients is more nuanced. In EDPS v SRB, the Court of Justice held that pseudonymised data are not personal data in every case and for every person: for a recipient without reasonable means of re-identifying individuals, they may not be. The controller’s duties still apply before the transfer11. Unless your data protection officer concludes otherwise, treat pseudonymised manuscript data as personal data.

Clinical manuscripts are hard to anonymise because identification is often indirect: a rare diagnosis, exact age, treatment date, small locality or distinctive sequence of events, plus images, captions, supplementary files and document metadata. De-identification lowers but does not remove re-identification risk: it is very low in secure research environments5, but de-identified notes still leak information that a less controlled setting can exploit6. Review the whole package and generalise unnecessary detail while keeping the scientific meaning.

Can you upload patient data to an AI tool?

AI-assisted manuscript editing may be possible, but combining AI tools and patient data needs a deliberate assessment. Uploading personal data is processing, so it needs the same lawful basis, Article 9 condition and safeguards as any other disclosure. A provider’s promise not to train on your content does not by itself make the processing lawful. Ask:

  • Is identifiable information necessary? Grammar and style correction rarely needs names, exact dates or hospital numbers.
  • What happens to submitted content? Check retention, deletion, human access, reuse and model training terms.
  • Who can access it, and where? Consider sub-processors, locations and whether transfer rules apply.
  • Has the institution approved the tool? Research agreements and publisher policies may restrict external AI services.
  • Is a DPIA needed? A data protection impact assessment under Article 35 may be required for high-risk processing.

The European Data Protection Supervisor’s guidance on generative AI is useful reading, but it is addressed to EU institutions under Regulation (EU) 2018/1725, not to every hospital, university or commercial provider7.

Table 4. Common manuscript-sharing scenarios

ScenarioPractical approach
The manuscript is genuinely anonymousOutside the GDPR, but confidentiality, ethics, contract and journal duties still apply
Names replaced with codes; a key existsPseudonymised personal data: assess lawful basis, Article 9 condition and safeguards
Case report with a rare condition and detailed timelineAssess whether combined details identify the patient; generalise what is not needed
AI tool to edit identifiable patient materialDo not upload until lawfulness, terms, security, retention and transfers are assessed
External editor processes personal data for a controllerConfirm the editor’s role and put an Article 28 contract in place

GDPR international data transfers, security and patient confidentiality

GDPR international data transfers arise when an editor or AI provider accesses personal data from outside the EEA; the provider’s headquarters alone does not settle it. Under Chapter V, a transfer can rely on an adequacy decision or safeguards such as standard contractual clauses, set out in Commission Implementing Decision (EU) 2021/9148. The right module and any transfer assessment depend on the parties’ roles. Proportionate security includes restricted access, encryption, secure transfer, controlled retention and a data breach response plan.

GDPR compliance does not replace clinical confidentiality, ethics approvals, data-sharing agreements or journal rules, and consent to publish an identifiable case report is separate from the lawful basis for editing. Responsible sharing of clinical data also needs governance and clear conditions for reuse9.

A practical checklist before sharing a manuscript

Use this GDPR compliance checklist before sending a manuscript to an editor, translator or AI platform.

Before you share

  • Identify direct and indirect identifiers in text, tables, figures, images, supplements and metadata.
  • Remove details the editing task does not need, without compromising scientific accuracy.
  • Assess whether what remains could identify a patient when combined with available information.
  • Where personal data remain, record the Article 6 lawful basis and the Article 9 condition.
  • Check the recipient’s role, privacy terms, retention, security and reuse of content.
  • Put an Article 28 contract and confidentiality terms in place where required.
  • Confirm whether Chapter V applies and which transfer mechanism is used.
  • Check institutional, ethics, professional and publisher requirements, and document the decision.

Pubrica team verdict

GDPR Article 9 does not ban editors or AI tools for medical manuscripts; it demands a lawful basis, an Article 9 condition and safeguards for health data. Strip what the task does not need, treat pseudonymised data as personal data and check every recipient’s role, terms and data location before you share.

Frequently asked questions

Only with a lawful basis, an Article 9 condition and, where the editor acts as a processor, an Article 28 contract. Removing unnecessary identifiers first is the safer default.

For you as controller, yes. Since the 2025 EDPS v SRB judgment, pseudonymised data may not be personal data for a recipient who cannot reasonably re-identify anyone, but your duties apply before you share, so treat them as personal data unless your data protection officer concludes otherwise.

No. It is a useful safeguard, but you still need a lawful basis, an Article 9 condition, security and transfer checks.

Under BDSG § 27(4), personal data may be published only with the data subject’s consent or where publication is indispensable for presenting research findings on contemporary events, so identifiable details normally need consent.

Sources

Sources were checked on 12 November 2026. Requirements and guidance may change after that date; confirm the current version with the issuing body.

  1. 1Regulation (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;L119:1–88. https://eur-lex.europa.eu/eli/reg/2016/679/oj
  2. 2Roguljić M, Ščepanović R, Rees M. Writing case reports, consent for publication and General Data Protection Regulation (GDPR). Case Rep Womens Health. 2020;27:e00204. https://doi.org/10.1016/j.crwh.2020.e00204
  3. 3European Data Protection Board. Guidelines 01/2025 on pseudonymisation, version 1.0 (adopted for public consultation 16 January 2025). EDPB; 2025. https://www.edpb.europa.eu/system/files/2025-01/edpb_guidelines_202501_pseudonymisation_en.pdf
  4. 4European Data Protection Board. Guidelines 02/2026 on anonymisation, version 1.0 (adopted for public consultation 7 July 2026). EDPB; 2026. https://www.edpb.europa.eu/system/files/2026-09/edpb_guidelines_202602_anonymisation_v1_en_0.pdf
  5. 5Ford E, Pillinger S, Stewart R, et al. What is the patient re-identification risk from using de-identified clinical free text data for health research? AI Ethics. 2025;5:4441–4454. https://doi.org/10.1007/s43681-025-00681-0
  6. 6Sarkar AR, Chuang YS, Mohammed N, Jiang X. De-identification is not enough: a comparison between de-identified and synthetic clinical notes. Sci Rep. 2024;14:29669. https://doi.org/10.1038/s41598-024-81170-y
  7. 7European Data Protection Supervisor. Generative AI and the EUDPR: orientations for ensuring data protection compliance when using generative AI systems, version 2. EDPS; 28 October 2025. https://www.edps.europa.eu/system/files/2025-10/25-10_28_revised_genai_orientations_en.pdf
  8. 8European Commission. Commission Implementing Decision (EU) 2021/914 on standard contractual clauses for the transfer of personal data to third countries. Official Journal of the European Union. 2021;L199:31–61. https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj
  9. 9Ohmann C, Banzi R, Canham S, et al. Sharing and reuse of individual participant data from clinical trials: principles and recommendations. BMJ Open. 2017;7(12):e018647. https://doi.org/10.1136/bmjopen-2017-018647
  10. 10Bundesdatenschutzgesetz (BDSG) § 27: Datenverarbeitung zu wissenschaftlichen oder historischen Forschungszwecken und zu statistischen Zwecken [Data processing for scientific or historical research purposes and for statistical purposes]. Federal Ministry of Justice; 2017 (as amended). https://www.gesetze-im-internet.de/bdsg_2018/__27.html
  11. 11Court of Justice of the European Union. Judgment of 4 September 2025, European Data Protection Supervisor v Single Resolution Board, Case C-413/23 P. https://curia.europa.eu/juris/liste.jsf?num=C-413/23
  12. 12International Committee of Medical Journal Editors. Protection of research participants. In: Recommendations for the conduct, reporting, editing, and publication of scholarly work in medical journals. ICMJE; 2026. https://www.icmje.org/recommendations/browse/roles-and-responsibilities/protection-of-research-participants.html

GDPR Article 9patient data protectionmedical data privacyGDPR and manuscript editingAI tools and patient datasensitive health data under GDPR

How to cite this article

Pick your referencing style and copy it. Your university or target journal may vary the punctuation, so check its guide if it has one.

Dr. Charlie. (2026, October 24). GDPR Article 9 and Manuscript Editing: Can You Send Patient Data to an Editor or an AI Tool?. Pubrica. https://pubrica.com/academy/publication-support/gdpr-article-9-patient-data-manuscript-editing/

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.

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.