← Latest papers
🤖 machine learning

Federated Concept-Based Models: Interpretable models with distributed supervision

This paper introduces Federated Concept-based Models (F-CMs), a novel framework that enables the training of interpretable deep learning models across distributed institutions by aggregating concept-level information and dynamically adapting architecture to evolving supervision sets while preserving data privacy.

Original authors: Dario Fenoglio, Arianna Casanova, Francesco De Santis, Gabriele Dominici, Johannes Schneider, Pietro Barbiero, Giovanni De Felice, Marc Langheinrich, Martin Gjoreski

Published 2026-05-12
📖 5 min read🧠 Deep dive

Original authors: Dario Fenoglio, Arianna Casanova, Francesco De Santis, Gabriele Dominici, Johannes Schneider, Pietro Barbiero, Giovanni De Felice, Marc Langheinrich, Martin Gjoreski

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to teach a group of doctors from different hospitals how to diagnose a complex illness. Each doctor has seen different patients and knows different symptoms (concepts). However, there are two big problems:

  1. Privacy: They cannot share their patient files with each other.
  2. Incomplete Knowledge: No single doctor knows all the symptoms. One might know about "fever," another about "rash," and a third about "cough."

Usually, to build a smart AI that explains why it makes a diagnosis (an "interpretable" model), you need a massive list of all possible symptoms and how they relate to each other. But getting that list is expensive and hard to find in just one hospital.

This paper introduces a new method called Federated Concept-based Models (F-CMs). Think of it as a "Smart Team-Up" that solves the privacy and knowledge gaps without anyone ever seeing the raw patient data.

Here is how it works, using a simple analogy:

The Problem: The "Fixed Blueprint" Trap

Imagine the doctors are trying to build a giant, shared machine to diagnose patients.

  • Old Way (Standard Federated Learning): They agree on a fixed blueprint for the machine before they start. If a new doctor joins later who knows about a symptom the blueprint didn't include (like "swollen lymph nodes"), the machine can't learn it. It's like trying to add a new room to a house that was built with a rigid, unchangeable floor plan.
  • The Issue: In the real world, doctors (clients) join and leave, and they discover new symptoms over time. A fixed blueprint fails here.

The Solution: The "Lego" Machine (F-CMs)

The authors propose a machine built like Lego blocks. Instead of a fixed blueprint, the machine is made of interchangeable modules, where each block represents a specific symptom (concept) or the final diagnosis.

Here are the three magic steps the system takes every time a new doctor joins:

1. The "Consensus Map" (Graph Aggregation)

Every doctor draws a rough sketch of how the symptoms they know relate to each other. Some sketches might be messy or wrong because they only saw a few patients.

  • What happens: The central server (the "Team Leader") collects all these sketches. Instead of picking one, it looks for the most common connections. If 9 out of 10 doctors say "Fever leads to Rash," the server draws that line. If a doctor says "Fever leads to Rain," the server ignores it because no one else agrees.
  • Result: A single, high-quality "Master Map" of how symptoms connect, built from everyone's partial knowledge.

2. The "Modular Expansion" (Dynamic Architecture Adaptation)

This is the paper's biggest innovation.

  • Scenario: A new doctor joins who knows about a symptom called "Swollen Lymph Nodes" that no one else knew about.
  • Old Way: You would have to tear down the whole machine and rebuild it from scratch to add this new part. This is slow and wastes all the knowledge you already learned.
  • F-CM Way: The system looks at the Master Map, sees the new "Swollen Lymph Nodes" block, and snaps a new Lego block onto the machine. It only builds the specific part needed for that new symptom. The rest of the machine (the parts for "Fever" and "Rash") stays exactly as it was, preserving all the previous learning.
  • Benefit: The machine grows organically without needing a total reboot.

3. The "Specialized Training" (Module-Specific Optimization)

Now, the doctors start training the machine.

  • The Rule: A doctor only gets to touch the Lego blocks they understand. If a doctor knows about "Fever" but not "Swollen Lymph Nodes," they can only update the "Fever" block. The "Swollen Lymph Nodes" block stays frozen (unchanged) for that doctor.
  • Result: The server collects updates only for the blocks that were touched. It averages them out to make that specific block smarter. This ensures that doctors don't accidentally "break" parts of the machine they don't understand.

Why This Matters (The Results)

The authors tested this on medical imaging (like X-rays) and simulated medical data. They found:

  • It's as accurate as having all the data in one place: Even though the data was split up and private, the final machine performed just as well as if they had pooled all the data together.
  • It handles new information: When new doctors with new symptoms joined, the F-CM system adapted quickly and kept learning. The old "fixed blueprint" systems got stuck and performed poorly.
  • It's efficient: Because it only updates the specific blocks that need changing, it saves a massive amount of computing power compared to rebuilding the whole model every time.
  • It works on "invisible" concepts: Even if a specific hospital never saw a certain symptom, the system can still make predictions about it because it learned the concept from other hospitals.

In a Nutshell

F-CMs is like a living, breathing team of experts that builds a shared knowledge base. Instead of forcing everyone to agree on a rigid plan before starting, it allows the plan to evolve. As new experts join with new ideas, the system simply adds new pieces to the puzzle, keeping the old pieces intact, all while keeping everyone's private data locked in their own safes.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →