wikillm

Paper · 2022-11-15 · cs.LG, cs.AI, cs.CR, cs.DC

Federated Learning for Healthcare Domain - Pipeline, Applications and Challenges

Survey of federated learning (FL) for healthcare: the pipeline (centralized or decentralized communication, cross-silo or cross-device scale, horizontal, vertical and transfer data splits), privacy tools, aggregation methods, applications, challenges and frameworks. No experiments; its numbers are quoted from cited studies.

Federated learningVertical federated learningDifferential privacyHomomorphic encryptionsurveyfederated-learninghealthcareprivacy

arXivPDFMarkdown7 min read

AI-compiled by claude-haiku-5-5 on 2026-11-12, not yet reviewed by a human. Every claim cites its source; check it when a detail matters.

In plain words

Hospitals, clinics and labs each hold patient records that they cannot easily share, because of privacy law and patient consent. A model trained on only one site's records can be biased toward that site's patients and equipment. This survey looks at federated learning, a way to train one shared model while the records stay where they are: each site trains on its own data and sends only model updates to a coordinator, which combines them.

The paper walks through how such a system is built: who talks to whom, how the data is split across sites, how the updates are combined, and which privacy tools can be added on top. It then lists health applications (predicting how a patient will progress, diagnosing, supporting clinical workflow), the problems that remain open, and the software frameworks that exist for building such systems.

It is a literature review. It does not test a new method, so its numbers come from other papers.

TL;DR

A survey of federated learning for healthcare, from 2022, by three authors. It gives a pipeline view of FL systems (communication architecture, scale, server and client roles, data partitioning, privacy methods, the ML workflow), groups the challenges into privacy and attacks, data, and communication, and lists applications and eight frameworks. It has no experiments of its own and one equation (the FedAvg objective). Use it as a map of the field, not as a source of verified results.

Problem

Clinical data is sensitive, spread across institutions, and governed by laws such as GDPR and HIPAA, so pooling it for training is often not allowed §1. Training on a single source gives biased models, and training on pooled data is slow and costly §1. The paper asks what the federated approach offers the healthcare domain and which problems remain §1.

Method

The paper is a survey. It has no algorithm of its own. Its "method" is a taxonomy and a pipeline view of FL systems, summarised here in the paper's order. Section numbers count the LaTeX order (see Pitfalls).

  • Communication architecture §2.1. Centralized: a central server aggregates local models and sends back a new global model fig. 1. The paper cites Android keyboard training as an example §2.1.1. Decentralized: clients exchange updates with each other without a central server, which avoids a single point of failure fig. 2 §2.1.2.
  • Scale §2.2. Cross-silo: few organisations with large datasets and good compute, and lower stability. Cross-device: many clients (phones, IoT devices) with small datasets that join and leave §2.2.1 §2.2.2.
  • Model evaluation §2.2.3. Centralized metrics (accuracy, precision, recall) are not enough. Training speed, performance and transferred data volume are used. FedEval evaluates on five targets: accuracy, communication, time consumption, privacy and robustness.
  • Server §2.3. The server admits clients after a credential check and sets minimum and maximum client counts. Each round it collects updates, aggregates them and repeats until a maximum number of rounds. Aggregation rules named in the paper: FedAvg, FedMA, FedNAS, FedGKT, a secured weighted aggregation with homomorphic encryption and zero-knowledge proofs, secure matrix factorization (FedMF), a differentially private gradient-boosted tree system, and Federated Forest §2.3.
  • Client §2.4. Clients train on private data and send updates. Data is split as horizontal (same features, different samples), vertical (same samples, different features) or hybrid/transfer fig. 3 fig. 4 fig. 5 §2.4.1. Preprocessing needs medical domain knowledge §2.4.2.
  • Privacy §2.4.3. Cryptographic methods (homomorphic encryption, secret sharing), differential privacy (noise added to updates), and secure multi-party computation with input, computation and result parties.
  • ML pipeline §2.5 fig. 6. Model selection (CNNs for images, LSTM/CIFG for next-word prediction, tree models, linear models), training as a loop (train locally, share parameters, aggregate, update local models, repeat) §2.5.2, and tuning of learning rate, epochs, batch size and optimizer. Federated neural architecture search is mentioned §2.5.3.
  • Challenges §3 fig. 7. Privacy and attacks §3.1: adversarial examples, inference and poisoning attacks, evasion, gradient inversion, genomic privacy. Data §3.2: noise, annotation quality, bias, missing values, data leakage, patient variability. Communication §3.3: dropouts and stragglers, communication overhead, energy use on devices.
  • Applications §4. Prognosis §4.1, diagnosis §4.2 and clinical workflow §4.3, each with the studies the paper groups there.
  • Tools §5. TensorFlow Federated, FATE, PySyft, LEAF, PaddleFL, Clara Training Framework, FedML, IBM Federated Learning. The paper gives strengths and gaps for each.
  • Conclusion §6. Future work on FL in 5G/6G medical devices and services.

The generic training round, as the survey describes it §2.3 §2.5.2:

Pseudocode
# Federated training round as the survey describes it  [§2.3] [§2.5.2]
# Input:  clients (list), global_model, max_rounds
# Output: global_model after the last round

def federated_training(clients, global_model, max_rounds):
    # Server checks each client's credentials and admits it to the session
    # [§2.3]
    session = admit_clients(clients)
    for round_index in range(max_rounds):
        # Server sends the current global model to every session member
        # [§2.5.2]
        for client in session.members:
            client.set_model(global_model)
        # Each client trains locally on its own private data; only the
        # updated parameters leave the client [§2.3] [§2.4]
        local_updates = [client.train_locally() for client in session.members]
        # Server waits for all updates, then aggregates them into the new
        # global model; the paper's example rule is FedAvg [§2.3] [eq. 1]
        global_model = aggregate(local_updates)
    return global_model

The only equation in the paper is the FedAvg objective §2.3:

f(w) = \sum_{k=1}^{K} \frac{n_k}{n} F_k(w), \quad F_k(w) = \frac{1}{n_k} \sum_{i \in P_k} f_i(w) eq. 1

Here K is the number of clients, P_k the indices of the data points on client k, n_k = |P_k|, n the total number of data points and w the model parameters. The paper does not define f_i (see Pitfalls).

Hyperparameters

The survey runs no training, so it reports no values. Each entry below says what the paper names and whether it gives a value.

NameValueWhereNotes
number of clients Knot stated§2.3 eq. 1only the symbol appears
min and max clients per sessionnot stated§2.3the server "decides" the numbers; none given
number of roundsnot stated§2.3"maximum number of rounds" with no value
local epochsnot stated§2.3 §2.5.3chosen by client devices; no value
learning rate, mini-batch size, optimizernot stated§2.5.3named as tunable; no values
FedAvg weightingdata-share weights n_k/n§2.3 eq. 1the update rule itself is not written out

Results

No experiments. The paper reports no results of its own. Its one table, tab. 1, lists 35 studies on FL in healthcare, each with title, citation key, year, category (for example "Survey", "Diagnosis", "Learning Systems") and a one-sentence summary. The table is titled "since 2015". Four rows are labelled "Survey".

Numbers the survey quotes from other work (author-reported, not checked here):

SettingMetricBaselineQuoted valueSource
FedGKT vs FedAvg, edge computeedge computing resourcesFedAvg9 to 17 times less§2.3 (FedGKT item)
FedGKT vs FedAvg, accuracyaccuracyFedAvgsame or slightly higher (claim)§2.3 (FedGKT item)
Federated transfer learning, EEG BCI, subject-adaptiveclassification accuracynot stated2% better§2.4.1
Privacy-preserving deduplication (Yigzaw 2017)run timenot stated45 s for one million virtual documents across 20 custodians§2.4.1
Ten-university FL on medical data (Sheller 2020)model qualitynot stated99 percenttab. 1

Paper vs code

No official code. The paper has no code link, its abstract and arXiv metadata have none, and it is a survey with no method to implement. A GitHub repository search for "federated learning healthcare survey" returned only a questionnaire project by an unrelated owner (FabioLiberti/Questionnaire_FL), not an author repository.

No code is involved, so the discrepancies noted under Pitfalls are between the paper's own text and its section numbering.

Pitfalls

  • Nothing to reproduce. The card covers a literature review. Every number comes from another paper and has not been checked against it. Use the original works before relying on any value.
  • Section numbering disagrees with the text. The paper's introduction says "Section 2 discusses the challenges" and "Section 3 concludes with ... applications and tools". The LaTeX order is 1 Introduction, 2 Pipeline, 3 Challenges & Issues, 4 Application, 5 Tools, 6 Conclusion. This card uses the LaTeX order, counted by hand, since the source has no compiled PDF to check against.
  • Citation keys are reused. In the body, Ju2020 is cited for FedHealth (wearables) and for the EEG federated transfer learning work §2.4.1 §2.4.2. The bibliography entry with that key has a different title (federated prediction for stroke prevention). In the table, FedHealth is keyed Chen2020, which is also the key for a different row. Check each source by title before citing it.
  • Table years do not always match the key. The LoAdaBoost row is keyed Huang2020 with year 2018. The Dou et al. row is keyed Dou2021 with year 2019. Use the year in the original paper.
  • FedAvg equation is incomplete. f_i is never defined, the update rule is not written, and "Where P_k the set of indexes" is missing a verb in the source. The sentence says FedAvg was tested on "five different architectures, four kinds of datasets". That is a claim about the original paper, not a result here §2.3.
  • The paper calls FedAvg the first FL algorithm §2.3. This is the survey's claim and is not verified here.
  • Privacy claims are vague. The paper says differential privacy "may not help much" for participant-level protection with small pools and that its utility cost depends on the setting, with no numbers §2.4.3.
  • Evaluation section gives no procedure. Measures such as training speed and data transferred are named §2.2.3, but not how to measure them.
  • Pipeline step count is ambiguous. The text says the lifecycle has "8 primary steps" §2.5 fig. 6. The list reads as seven or eight items, depending on whether "versioning testing deployment and termination" is split.
  • Figure alt text is a placeholder. The source gives every figure the same alt text, about a woman and a girl in a car, which does not match the figures. Do not use it. No figure is reproduced on this card.
  • Mixed claims in the same paragraph. Federated transfer learning is said to need no common feature or sample space §2.4.1, and in the next paragraph to work only for two clients. Both are the survey's wording.
  • Unused source file. text.tex in the source archive is a stray table fragment. The paper does not include it, so it is not part of this card.

Lineage

  • Builds on: FedAvg (McMahan et al. 2017, key McMahan2017) §2.3.
  • Surveys the paper cites for context: Kairouz et al. 2021, "Advances and Open Problems in Federated Learning" (key kairouz2021advances) §2.4.1 §3.2; Lyu, Yu and Yang 2020, "Threats to Federated Learning: A Survey" (key lyu2020threats) §3.1.
  • Compared against: not applicable (no experiments).
  • Superseded by: not stated.

Source and license

Adapted from “Federated Learning for Healthcare Domain - Pipeline, Applications and Challenges” by Madhura Joshi, Ankit Pal, Malaikannan Sankarasubbu (arXiv:2211.07893), used under CC BY 4.0. Changes: condensed and restructured for implementation, with tables, equations and algorithms taken from the paper and its code, each cited to its source. Not affiliated with or endorsed by the authors.