Keeping patient data local does not make an AI health claim causal
A peer-reviewed methods review maps how hospitals can estimate treatment effects without pooling patient records. Its central warning is practical: federation changes computation, not the assumptions needed for a causal conclusion or a real privacy guarantee.
The short version
- What happened
- The structured review separates three questions often blurred together: the treatment effect being estimated, the distributed-computation protocol and the privacy mechanism.
- Who it affects
- Federation may let more hospitals contribute evidence without exporting patient-level records, but patients can still be harmed by biased treatment estimates or vague privacy claims if clinical differences and threat models are ignored.
- What remains unproven
- Structured targeted review rather than a systematic review or meta-analysis; no reported count of screened and retained studies; no new patient data, pooled clinical outcome or comparative benchmark; several cited methods remain preprints.
Keep in mind
Structured targeted review rather than a systematic review or meta-analysis; no reported count of screened and retained studies; no new patient data, pooled clinical outcome or comparative benchmark; several cited methods remain preprints.
Source analysis · 1 linked source. Primary analysed source date: 17 October 2026.
Read the full report · 3 min The evidence, methods, implications and limitations
Three layers determine whether a result deserves trust
The review organises federated causal inference around an inferential target, a computation protocol and a privacy mechanism. That distinction matters: hospitals can exchange approved statistics or model updates without sharing raw records, yet still estimate the wrong treatment effect if sites define patients, treatments, outcomes or time zero differently.
The authors cover binary, continuous and time-to-event outcomes, comparing one-shot, iterative, personalised, peer-to-peer and model-decomposition strategies. They only describe a federated estimate as equivalent or close to pooled analysis when a cited method establishes that result under explicit conditions.[1]
Why local data is neither causal proof nor automatic privacy
A treatment-effect claim still needs a defined intervention and target population, adequate adjustment for confounding, compatible measurements, positivity and suitable handling of censoring. Averaging site estimates can target the wrong population, and a distributed Cox regression is not automatically a causal survival analysis.
Privacy is a separate test. Secure aggregation can hide each site’s contribution while revealing an approved total, but it does not limit everything inferable from the result. Differential privacy gives a quantified guarantee only under a specified neighbouring relation and privacy budget; merely sending gradients can still expose information.[1]
The distinction that matters
Three questions before trusting a federated health estimate
Distributed computation solves only one part of a multi-site causal study.
Target
Define treatment, outcome and population
Know which causal effect is being estimated
Compute
Exchange approved summaries or updates
Avoid centralising patient-level records
Protect
Specify secure aggregation or differential privacy
State what is protected and from whom
What changes for research teams and patients
Federated analysis can make some multi-hospital studies feasible where legal, governance or practical barriers prevent central pooling. Patients and clinicians still need the resulting estimate to match the decision at hand, and institutions need an explicit threat model rather than a generic claim that data stayed local.
The field needs realistic benchmarks with known treatment effects and cross-site differences, stronger tests of privacy–utility trade-offs, auditable software and validation under site inclusion, data drift and demographic heterogeneity. The review itself is structured and targeted, not systematic, and reports no new clinical effectiveness result.[1]