Skip to content
AI in Healthcare

News

NEJM AI: swarm learning matches centralized training for surgical-video AI across six international centers

Saldanha et al. show that a decentralized, privacy-preserving pipeline combining weakly supervised deep learning with Swarm Learning produces patient-level predictions on laparoscopic appendectomy videos that are on par with centralized training — across three disease staging tasks, six institutions, and jurisdictions with incompatible data-sharing regimes. A meaningful proof point that clinical-AI training does not require pooling raw patient data in one place.

NEJM AI By AI in Healthcare Editorial Source dated
  • NEJM
  • research
  • surgery
  • federated-learning
  • privacy

Directly relevant to the argument health systems and payers keep having about “we can’t train AI on our data because of privacy.” The paper does not eliminate the argument — it does, however, remove the “swarm learning is just theory” version of it.

The specific claim matters: Saldanha and colleagues show that a decentralized, privacy-preserving pipeline combining weakly-supervised deep learning with Swarm Learning produces patient-level predictions on laparoscopic appendectomy videos that are on par with centralized training — across three disease-staging tasks, six institutions, and jurisdictions with incompatible data-sharing regimes. No pooling of raw patient video was required.

For anyone building surgical-video AI, ambient AI scribes, or any clinical-AI product where PHI-scale training data has been a bottleneck, this is a clean proof point that the federated / swarm approach can reach centralized-training performance on real clinical tasks. Prior federated-learning demonstrations in healthcare AI often carried a performance-tax caveat: the paper’s contribution is showing there is no meaningful tax under a well-implemented swarm-learning setup for at least this class of task.

The paper does not solve every “we can’t train on our data” problem — governance, model-card provenance, incident traceability, and PHI-handling under a BAA all still apply. But it substantially lowers the technical objection. Expect the argument to shift from “privacy blocks distributed training” to “we still need governance around who trains what on whose data, even if the pipe is federated” — which is the correct place for the debate to be.

Related coverage: medical imaging AI topic, health-system copilots topic.

Primary source: Read the full original on NEJM AI ↗