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.
Glossary
FedPer

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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
FedPer vs. Other Personalization Strategies
Comparing FedPer's base-layer sharing and personal-head approach against alternative personalization strategies in federated learning.
| Feature | FedPer | Local Fine-Tuning | Clustered FL | Multi-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 |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Key concepts and algorithms that situate FedPer within the broader landscape of personalized federated learning, addressing structural data heterogeneity through layer-wise personalization strategies.
FedRep: Shared Representation Learning
A closely related algorithm that also partitions the neural network into shared base layers and personalized head layers. Unlike FedPer, which only personalizes the classifier, FedRep alternates training between learning a global feature extractor and local heads over multiple local epochs, often leading to better representation quality in highly heterogeneous vision tasks.
Partial Model Personalization
A generalization of the FedPer concept that systematically determines which layers to personalize and which to keep global. Strategies include:
- Personalizing batch normalization layers to handle domain shift
- Selecting layers based on Fisher information sensitivity
- Dynamic layer selection based on local data size This approach reduces communication overhead compared to full-model personalization while maintaining accuracy.
Local Fine-Tuning
The post-aggregation process where a globally trained model is further adapted on a specific client's local dataset. FedPer formalizes this by architecturally designating the final classification layers as local, ensuring that fine-tuning occurs only in a controlled subset of parameters. This prevents the catastrophic forgetting of global features while allowing site-specific decision boundaries.
Non-IID Data Handling
FedPer directly addresses label distribution skew—a core non-IID challenge where different hospitals have varying proportions of disease classes. By keeping base layers synchronized to learn universal medical feature extractors and allowing local heads to calibrate to site-specific class priors, FedPer mitigates the weight divergence that plagues standard FedAvg in heterogeneous clinical environments.
Federated Transfer Learning (FTL)
FTL addresses scenarios where clients have different feature spaces or different label spaces. FedPer complements FTL by providing a structural template: the shared base layers can be transferred across institutions with overlapping feature modalities (e.g., chest X-rays), while the personalized head accommodates institution-specific diagnostic label sets without requiring a unified global taxonomy.
Model Interpolation
A personalization technique that mixes the parameters of a local model and a global model to find an optimal balance point. FedPer can be viewed as a hard structural interpolation where the interpolation weight is 1.0 for the head layers and 0.0 for the base layers. More flexible interpolation methods like APFL learn a continuous mixing coefficient per layer, offering a spectrum between FedAvg and FedPer extremes.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us