Inferensys

Glossary

FedPer

A federated architecture that keeps base layers synchronized across the network while allowing personalization in the final classification layers, addressing structural data heterogeneity among clients.
Data scientist building training data pipeline on laptop, data preprocessing visible, technical workspace.
Federated Personalization Architecture

What is FedPer?

A federated learning architecture that synchronizes base layers across a network while allowing clients to maintain unique, personalized classification layers to address structural data heterogeneity.

FedPer is a federated learning architecture that partitions a neural network into shared base layers and personalized classification layers. The base layers, responsible for learning a universal feature representation, are aggregated and synchronized globally across all clients. Simultaneously, the final classification layers remain local and are never shared, allowing each client to maintain a unique decision boundary tailored to its specific data distribution.

This architectural separation directly addresses structural data heterogeneity, where clients possess data with the same feature space but different label distributions. By keeping the personalization in the top layers, FedPer avoids the client drift problem common in standard Federated Averaging, enabling robust global feature extraction while preserving the statistical nuances of individual silos without centralizing raw data.

ARCHITECTURAL PERSONALIZATION

Key Features of FedPer

FedPer introduces a structured approach to personalization by partitioning a neural network into shared base layers and personalized classification heads, directly addressing the challenge of structural data heterogeneity in federated healthcare networks.

01

Layer-Wise Partitioning Strategy

FedPer divides the neural network architecture into two distinct segments: base layers (feature extractors) and personalization layers (classification heads). The base layers, typically comprising convolutional or early dense layers, learn generalizable representations from the aggregated knowledge of all clients. The final classification layers remain local and are never shared with the central server. This structural separation allows each clinical site to maintain a site-specific decision boundary while benefiting from a globally robust feature space.

02

Handling Structural Data Heterogeneity

Unlike statistical heterogeneity (differences in data distribution), structural heterogeneity refers to differences in the feature space or label space across clients. In healthcare, this manifests as:

  • Varying label granularity: Hospital A classifies diseases at a coarse level, while Hospital B uses fine-grained sub-types.
  • Different diagnostic criteria: Institutions may use distinct clinical coding standards. FedPer resolves this by allowing each client to maintain a personalized classification layer tailored to its specific label ontology, while the shared base layers learn universal medical imaging features.
03

Communication Efficiency

By transmitting only the base layer parameters during federated aggregation rounds, FedPer significantly reduces communication overhead. The personalized classification heads, which can be substantial in networks with many output classes, never leave the local client. This design is particularly advantageous in bandwidth-constrained hospital environments where large model uploads may disrupt critical clinical network operations. The reduction in transmitted parameters directly correlates with faster round times and lower infrastructure costs.

04

Mitigation of Catastrophic Forgetting

In standard federated learning, aggressive global aggregation can overwrite locally specialized knowledge, a phenomenon known as catastrophic forgetting. FedPer's architecture inherently protects local expertise by isolating the personalized layers from the aggregation process. The base layers converge on a universal feature representation that generalizes across sites, while the frozen local heads preserve site-specific diagnostic nuances. This dual structure ensures that a model trained to detect rare conditions at a specialized clinic does not lose that capability after global synchronization.

05

Algorithmic Training Procedure

The FedPer training loop operates in distinct phases:

  • Local Phase: Each client performs full forward and backward passes, updating both base and personalization layers using its private data.
  • Communication Phase: Only the updated base layer weights are transmitted to the central server.
  • Aggregation Phase: The server applies a standard aggregation algorithm, such as Federated Averaging (FedAvg), to the received base layers.
  • Distribution Phase: The aggregated base layers are broadcast back to all clients, where they are recombined with the unchanged local personalization heads for the next round.
06

Comparison with Full Model Personalization

Unlike Local Fine-Tuning, which adapts the entire model post-federation and risks overfitting to small local datasets, FedPer constrains personalization to the final layers. This provides a regularization effect that prevents the model from diverging too far from the globally learned features. Compared to Multi-Task Federated Learning, FedPer does not require explicit task relationship modeling. The shared base layers implicitly learn a task-agnostic representation, making the architecture simpler to implement and tune in production clinical environments.

FEDPER EXPLAINED

Frequently Asked Questions

Clear, technical answers to the most common questions about the FedPer architecture, its mechanisms, and its role in personalized federated learning for healthcare.

FedPer (Federated Learning with Personalization Layers) is a federated architecture that partitions a neural network into base layers and personalization layers. The base layers are synchronized across all clients via standard federated aggregation, learning a universal feature representation from decentralized data. The personalization layers—typically the final classification head—remain local to each client and are never shared with the server. This structural separation allows each institution to maintain a unique classifier tailored to its local patient demographics and label distributions while still benefiting from a globally shared feature extractor trained across the entire network. The architecture directly addresses structural data heterogeneity, where the input feature space is consistent but the output label distributions vary significantly between sites.

ARCHITECTURAL COMPARISON

FedPer vs. Other Personalization Strategies

Comparing FedPer's base-layer sharing and personal-head approach against alternative personalization strategies in federated learning.

FeatureFedPerLocal Fine-TuningClustered FLMulti-Task FL

Personalization Mechanism

Personalized classification head

Full model retraining on local data

Group-specific global models

Shared layers with task-specific heads

Shared Representation

Communication Overhead

Low (head only)

None (post-training)

Medium (full model per cluster)

Medium (full model)

Handles Non-IID Data

Catastrophic Forgetting Risk

Low (base frozen)

High

Low (within cluster)

Medium

Global Knowledge Retention

Strong (base layers shared)

Weak (full local override)

Moderate (cluster-level)

Moderate (shared backbone)

Computation Cost per Client

Medium (train head)

High (full fine-tune)

Medium (full local training)

High (multi-head training)

Suitable for Small Local Datasets

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.