Privacy Leakage in Federated Learning in Radiology Reports: A Comparative Evaluation of Tokenizer-Driven Privacy Risks
Summary
A study quantifies privacy leakage in federated learning (FL) applied to radiology reports, specifically evaluating the role of tokenizer design. Six FL clients trained a GPT-2-style transformer on public radiology corpora, including 368,751 diagnostic reports and 98,206 discharge summaries, using GPT-2, RadBERT, and LLaMA-2 tokenizers at batch sizes of 64, 128, and 256. The research found that exact sentence reconstruction from FL gradients ranged from 31% to 44% across tokenizers, with RadBERT yielding the highest reconstruction fidelity (42.3% at batch size 64) and recovering the most clinical terms (18.1%). Despite using domain-specific tokenizers and larger batch sizes, substantial portions of report text were recoverable, indicating that tokenizer design significantly influences leakage severity but does not prevent it.
Key takeaway
For NLP Engineers or AI Security Engineers deploying federated learning on clinical text, particularly radiology reports, you must recognize that gradient inversion poses a substantial privacy risk. Even with domain-specific tokenizers like RadBERT, exact sentence reconstruction can exceed 40%. You should prioritize implementing robust safeguards such as secure aggregation and differential privacy to meet HIPAA and GDPR compliance, as tokenizer choice alone is insufficient to prevent sensitive data leakage.
Key insights
Federated learning gradients in radiology reports allow substantial text reconstruction, with tokenizer choice influencing leakage severity.
Principles
- Gradient inversion can reconstruct sensitive data from FL updates.
- Tokenizer design impacts FL privacy leakage severity.
- Domain-specific tokenizers do not prevent FL data leakage.
Method
Quantified gradient-based text reconstruction in FL by comparing GPT-2, RadBERT, and LLaMA-2 tokenizers on a GPT-2-style transformer across public radiology corpora (368,751 diagnostic reports, 98,206 discharge summaries, 1,500 MIMIC-CXR free-text reports).
In practice
- Evaluate tokenizer privacy implications alongside utility.
- Implement secure aggregation in FL for clinical text.
- Apply differential privacy to meet HIPAA/GDPR in FL.
Topics
- Federated Learning
- Privacy Leakage
- Radiology Reports
- Tokenizer Design
- Gradient Inversion
- HIPAA
- GDPR
Best for: CTO, VP of Engineering/Data, Director of AI/ML, AI Scientist, AI Security Engineer, NLP Engineer
Related on AIssential
See Counsel's argued verdicts on the open AI decisions leaders are weighing →
Editorial summary, takeaway, and curation by AIssential. Original article published by Computation and Language.