Personalized Aggregation (pFedMe) is a federated learning framework that uses Moreau envelopes to decompose the optimization objective into a global model and personalized local models, allowing each client to learn a distinct model tailored to its local data distribution while still benefiting from collaborative training. Unlike standard Federated Averaging (FedAvg), which enforces a single global model, pFedMe explicitly optimizes for personalization by solving a bi-level problem where local models are regularized toward the global model through a proximity penalty term controlled by a hyperparameter λ.
Glossary
Personalized Aggregation (pFedMe)

What is Personalized Aggregation (pFedMe)?
An optimization framework that decouples personalized model learning from global model aggregation using Moreau envelopes, enabling fine-grained adaptation to heterogeneous local clinical data distributions.
The framework employs an alternating direction method of multipliers (ADMM)-style optimization, where the global model is updated on the server via standard aggregation while each client solves a local subproblem to find its personalized model that minimizes empirical loss plus a Moreau envelope regularization term. This decoupling mitigates the client drift caused by statistical heterogeneity in non-IID clinical datasets, enabling superior performance on site-specific patient populations without sacrificing the statistical strength gained from multi-institutional collaboration.
Key Features of pFedMe
pFedMe uses Moreau envelopes to decouple personalized model optimization from global model learning, enabling fine-grained personalization on local clinical data.
Moreau Envelope Formulation
pFedMe reformulates the federated learning objective using Moreau envelopes, a mathematical tool from convex optimization. This creates a bi-level optimization problem where each client optimizes a personalized model in the inner loop while the server aggregates global knowledge in the outer loop. The Moreau envelope acts as a smooth approximation of the local loss function, allowing the personalized model to stay close to the global model while adapting to local data distributions. This decoupling is critical for handling statistical heterogeneity across clinical sites.
L2 Regularization for Personalization
The personalization mechanism in pFedMe is driven by an L2 regularization term that penalizes the distance between the local personalized model and the global model. This penalty is controlled by a hyperparameter λ that balances two competing objectives:
- Small λ: Allows the local model to deviate significantly, capturing site-specific patterns in clinical data
- Large λ: Keeps the local model close to the global consensus, leveraging shared knowledge across institutions This provides a tunable knob for clinical informatics directors to control the degree of personalization.
Nesterov Accelerated Gradient Descent
pFedMe employs Nesterov accelerated gradient descent in the inner optimization loop to solve each client's personalized subproblem efficiently. Nesterov acceleration provides a look-ahead mechanism that computes gradients at a projected future position rather than the current position, achieving an optimal convergence rate of O(1/k²) for smooth convex functions. This reduces the number of local computation rounds required per communication round, directly lowering the computational burden on resource-constrained clinical edge devices.
Communication-Efficient Design
pFedMe achieves communication efficiency through its decoupled optimization structure. Unlike FedAvg, which requires frequent synchronization of model weights, pFedMe allows clients to solve their personalized subproblems to high accuracy locally before communicating. This reduces the total number of communication rounds needed for convergence. The algorithm transmits only the global model parameters between server and clients, while personalized parameters remain local, further minimizing bandwidth overhead in bandwidth-constrained hospital networks.
Theoretical Convergence Guarantees
pFedMe provides rigorous convergence guarantees under realistic federated conditions. The algorithm provably converges for both strongly convex and non-convex loss functions, which covers most practical deep learning architectures used in medical imaging and EHR analysis. The convergence analysis accounts for:
- Statistical heterogeneity (non-IID data across hospitals)
- System heterogeneity (varying compute capabilities of clinical devices)
- Partial client participation (only a subset of hospitals available per round) These guarantees are essential for regulatory compliance in healthcare AI deployments.
Comparison with FedAvg and FedProx
pFedMe offers distinct advantages over baseline aggregation algorithms:
- vs FedAvg: FedAvg produces a single global model that may perform poorly on outlier clinical populations. pFedMe generates personalized models per site while still benefiting from collaborative learning.
- vs FedProx: FedProx adds a proximal term to stabilize training but still optimizes for a single global model. pFedMe's Moreau envelope formulation provides stronger theoretical guarantees and explicit personalization.
- vs Fine-tuning: Unlike naive fine-tuning of a global model on local data, pFedMe's bi-level optimization prevents catastrophic forgetting of globally learned features.
Frequently Asked Questions
Clear, technical answers to the most common questions about the pFedMe algorithm, its Moreau envelope formulation, and how it achieves state-of-the-art personalization in heterogeneous clinical environments.
Personalized Federated Learning with Moreau Envelopes (pFedMe) is a bi-level optimization framework that decouples personalized model optimization from global model learning using Moreau envelopes as a regularized loss function. Unlike standard Federated Averaging (FedAvg), which forces all clients toward a single global consensus model, pFedMe allows each client to pursue its own personalized model while remaining tethered to the global model through an L2 penalty term. The key mathematical insight is that pFedMe optimizes the Moreau envelope of the local loss function, defined as:
codeF_i(θ) = min_{w_i} { f_i(w_i) + (λ/2) ||w_i - θ||² }
where θ is the global model, w_i is the personalized local model, f_i is the local empirical loss, and λ is a regularization hyperparameter controlling the personalization-globalization trade-off. This formulation enables fine-grained personalization where each client can deviate significantly from the global model when local data distributions diverge, while still benefiting from collaborative learning. Empirically, pFedMe achieves up to 20-30% higher accuracy than FedAvg on heterogeneous non-IID data partitions, particularly in healthcare settings where patient populations vary dramatically across institutions.
pFedMe vs. Other Federated Aggregation Algorithms
Comparing pFedMe's Moreau envelope-based decoupling approach against standard aggregation methods for handling statistical heterogeneity in clinical federated learning deployments.
| Feature | pFedMe | FedAvg | FedProx | FedDyn |
|---|---|---|---|---|
Personalization Mechanism | Moreau envelope decoupling with L2-norm regularization | None (single global model) | Proximal term constrains local divergence | Dynamic regularizer aligns stationary points |
Handles Non-IID Clinical Data | ||||
Local Model Personalization | ||||
Convergence Speed on Heterogeneous Data | Fast (bi-level optimization) | Slow (client drift) | Moderate (stabilized local updates) | Fast (aligned stationary points) |
Communication Overhead | Standard (full model exchange) | Standard | Standard | Standard |
Computational Cost per Client | Higher (inner optimization loop) | Low | Moderate (proximal term computation) | Moderate (gradient accumulation) |
Global Model Quality Preservation | Maintained via global subproblem | Prioritized over personalization | Balanced via μ hyperparameter | Maintained via dynamic penalty |
Hyperparameter Sensitivity | Moderate (λ regularization weight) | Low | High (μ proximal term weight) | Moderate (α learning rate) |
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
Explore the core aggregation algorithms and related frameworks that enable personalized model optimization in decentralized healthcare networks.

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