Risk Adjustment Is a Program-Level System
A perspective from Gentry Consulting
Introduction
Risk Adjustment discussions often focus on functions. Coding, chart review, provider engagement, analytics, compliance, and encounter operations all play important roles. Every health plan depends on these activities to some degree. Yet organizations with similar resources, similar vendors, similar staffing models, and similar initiatives often produce very different results.
A common explanation is that one organization simply executes better than another. That may be true in some cases. Another possibility is that Risk Adjustment is frequently viewed through the wrong organizational lens. While the work is organized through functions, many of the outcomes leaders care about may emerge elsewhere.
Risk Adjustment is often discussed as a collection of functions. It may be more useful to understand it as a program-level system.
The Wrong Question
Many leadership conversations begin with questions such as:
• How is coding performing?
• How is chart review performing?
• How is provider engagement performing?
• How is encounter operations performing?
These are reasonable questions. However, they may not be the questions that explain overall program performance.
An organization can improve coding productivity, expand chart review activity, increase provider participation, and enhance reporting—all while remaining uncertain about whether the overall program is becoming more effective. Individual functions may improve while the broader program remains difficult to understand.
When that happens, the explanation is not always found within a single department. It often emerges through the interaction of departments.
Organizations Are Structured Around Functions, but Outcomes Often Emerge Through Interactions
Departments exist because specialization is necessary. Programs exist because outcomes require coordination.
Risk Adjustment outcomes do not originate entirely within coding, compliance, analytics, finance, provider engagement, or operations. They emerge through the interaction of those functions. Information moves between teams. Responsibilities shift. Decisions create downstream consequences. Dependencies develop.
This distinction is easy to overlook because organizations are naturally structured around functions. Accountability is assigned to departments. Performance is measured by teams. Reporting is organized around operational activities.
However, many outcomes are shaped by what happens between those functions rather than within them.
That does not diminish the importance of functional ownership. Functional ownership is necessary. The question is whether functional performance alone provides sufficient understanding of overall program performance.
The Space Between Functions
Significant challenges frequently emerge at organizational boundaries rather than within them.
The issue is not necessarily that coding failed. It may not be that operations failed, compliance failed, or provider engagement failed. Instead, the issue may be that no one is looking closely at how those functions interact.
As organizations become more sophisticated within individual disciplines, they can unintentionally become less aware of what is happening between disciplines. A program may appear healthy when viewed department by department but behave very differently when viewed as a whole.
This observation suggests a different way of thinking about performance. Organizations are typically structured around functions, but outcomes are often shaped by relationships, dependencies, handoffs, and interactions. Problems that seem difficult to explain at the functional level frequently become easier to understand when viewed through the lens of the broader program.
Why Similar Interventions Produce Different Results
One of the more interesting realities in Risk Adjustment is that organizations often implement similar interventions and experience dramatically different outcomes.
The same vendor.
The same technology.
The same chart review strategy.
The same provider engagement model.
The same operational initiative.
Very different results.
A function-centered perspective naturally asks:
Did the intervention work?
A program-level perspective asks a different question:
What system did the intervention enter?
The surrounding environment matters. Governance matters. Accountability matters. Information flow matters. Decision-making matters.
A well-designed intervention entering a poorly understood system may produce disappointing results. Conversely, a relatively modest intervention entering a well-managed system may create substantial value.
The intervention itself is only part of the story.
From Functional Management to Program Leadership
Viewing Risk Adjustment as a program-level system changes the leadership conversation.
The question shifts from:
How is coding performing?
to:
How is the program performing?
Those questions are not interchangeable.
The first evaluates activity. The second evaluates outcomes.
The first focuses on functions. The second focuses on interactions.
The first examines components. The second examines the system.
Leaders need both perspectives. However, they support different forms of understanding and different kinds of decisions.
Looking Beyond Activity Metrics
Most organizations have access to operational reporting. Activity metrics are not usually the challenge. The larger challenge is understanding what those metrics mean when viewed together.
Where is risk accumulating?
Where does uncertainty exist?
Where do dependencies create exposure?
Where do relatively small issues become larger organizational problems?
Where are outcomes being shaped before they ever appear in a report?
These questions rarely belong to a single department. They belong to the program.
Understanding the difference between activity and system behavior may become increasingly important as organizations seek greater accountability, stronger governance, and more reliable decision-making.
A Different Way to Think About Risk Adjustment
Organizations need strong coding teams, strong analytics, strong compliance oversight, strong provider engagement, and strong operational execution. None of those functions become less important under a program-level perspective.
The difference is that performance is no longer viewed primarily as the sum of independent activities. It is viewed as the result of a connected system.
This distinction may help explain why organizations that appear similar on paper often produce very different outcomes in practice. It may also explain why some problems remain resistant to otherwise reasonable interventions.
Risk Adjustment will always involve functions. The more important question may be whether those functions are being understood as components of a larger program—or simply managed as separate parts.
That is more than an organizational distinction.
It is a different way of understanding where performance actually comes from.