Some departments change their purpose without changing their name, budget, or reporting structure. The work evolves beneath an unchanged org chart, and familiar weekly numbers can hide the shift for a while.
Medicare Advantage risk adjustment offers one example of why review teams may need to change how they work. Insurers receive payments adjusted for enrollees’ health needs, and submitted diagnoses must be supported by medical records. A review function that once focused on finding omitted conditions may also need to identify diagnoses that lack documentation.
The original job
Medicare Advantage payments account for reported health status. Diagnosis codes are drawn from clinical records, and accurate coding matters both for appropriate payment and for ensuring that claims reflect the patient’s documented conditions.
A retrospective review team may look for genuine conditions that were not captured in prior records. Each finding can affect payment, so organizations may build tools, contracts, staffing, and performance measures around identifying additional diagnoses.
The job changed. The department did not.
The control objective is not simply to find more diagnoses. It is to make sure each submitted diagnosis is supported by the relevant medical record and applicable program rules.
Federal oversight reviews have found substantial documentation problems in selected high-risk diagnosis codes. In one 2026 review of 97 sampled enrollees with acute stroke codes, none of the submitted codes was supported by the associated records. That sample concerns a specific high-risk category and should not be read as a rate for all Medicare Advantage diagnoses.
This kind of review illustrates why a team may shift from revenue identification toward a broader risk-control role. The staffing and reporting line may remain the same even as the team’s responsibility expands.
Why this transition is harder than it sounds
Three forces can make the shift difficult, and they apply across industries.
The tools may support only one direction. Review software designed to surface potential diagnoses may not make it easy to flag unsupported submissions or route them for correction. The team needs a way to identify both missing and unsupported information.
The incentives may run the wrong way. Contracts priced by the number of findings can reward volume, even when the updated objective is accuracy. Renegotiating those arrangements takes time, and leaders may be reluctant to replace a metric that has risen for years.
Identity can also get in the way. When one measure defines success for a long time, it can become part of the department’s purpose. Leaders need to explain which responsibilities remain valuable and what the new priority requires.
What the shift looks like in practice
The function does not disappear; its work becomes more balanced. A review can identify a documented condition that was missed, flag a code that lacks support, and route both outcomes to the accountable team for action.
This technical change has a broader organizational consequence: a team able to report an unfavorable finding needs a clear destination for it, an owner responsible for acting, and a measure that rewards accuracy rather than volume alone.
The transferable question
These questions are useful for any business function built around one measure:
- Has the standard for success changed while the department kept its original structure?
- Can the function surface a result leaders may not want to hear, and is there a route for that result?
- Are suppliers still paid for behavior that now creates risk?
A department whose purpose has changed while its incentives remain fixed may not be underperforming. It may be measured against work it was never designed to do.