By admin 
Risk Adjustment Left the Back Office
Five years ago, risk adjustment technology decisions were made by coding directors and VP-level operational leaders. The CFO signed the budget. The CIO approved the security review. But the strategic decision, which platform to use and how to structure the program, sat with the operational team that managed the day-to-day coding workflow.
That’s no longer appropriate for the risk involved. DOJ settlements exceeding $670 million from two organizations established that risk adjustment program design creates potential federal liability. MedPAC’s $76 billion overpayment finding put MA risk adjustment at the center of congressional and regulatory attention. Credit agencies are flagging risk adjustment as a profitability constraint for MA-heavy organizations. The strategic and financial exposure of these programs now warrants C-suite engagement in technology and methodology decisions.
A coding director choosing between platforms based on coder productivity metrics is making a different decision than a CFO evaluating platforms based on defensibility, audit readiness, and settlement risk. Both perspectives matter. But in a market where the wrong technology choice can generate nine-figure liability, the financial and compliance perspective needs to be at the table.
What Each C-Suite Role Needs to See
The CFO needs defensibility metrics: what percentage of submitted codes have strong MEAT evidence, what’s the plan’s deletion rate, and how would revenue projections change if the weakest 10% of codes were removed? These numbers drive financial forecasting, credit conversations, and board reporting. A platform that can’t produce them leaves the CFO reporting revenue without quantified risk.
The CIO needs AI governance assurance: is the platform’s AI explainable? Can the compliance team audit its reasoning? Does it meet data security standards? Is it architected to prevent shadow AI workarounds by coders using unauthorized tools? The CIO’s concern is that ungoverned technology making clinical coding decisions creates both security and regulatory risk.
The Chief Compliance Officer needs methodology validation: does the platform support two-way coding? Does it produce evidence trails that meet CMS audit standards? Does it flag high-risk diagnosis categories for enhanced validation? The CCO’s concern is that the technology itself, through its design and default behaviors, either creates or reduces compliance exposure.
The COO needs operational efficiency that doesn’t sacrifice quality: can the platform handle both retrospective and prospective workflows? Does it reduce the vendor fragmentation that slows audit response? Does it integrate with the EHR and existing data infrastructure without requiring parallel systems?
Why Platform Decisions Carry Board-Level Consequences
The combined settlement amounts from recent DOJ enforcement actions exceed the annual technology budget of most MA organizations by orders of magnitude. A platform that enables add-only coding, doesn’t produce evidence trails, or uses opaque AI creates the conditions for the same enforcement outcomes that generated those settlements. The technology choice isn’t just an operational preference. It’s a risk management decision with financial consequences that boards have fiduciary obligations to understand.
Board members don’t need to evaluate software interfaces. They need to know that the platform the organization selected supports two-way coding, produces audit-ready evidence trails, uses explainable AI, and can demonstrate defensibility across the plan’s submitted code population.
Elevating the Decision
Plans that keep risk adjustment technology decisions at the operational level alone are making board-level risk decisions without board-level oversight. A Risk Adjustment Platform selected with input from the CFO, CIO, CCO, and COO, evaluated on defensibility and compliance architecture alongside operational efficiency, produces a stronger compliance posture than one selected on coding speed alone. The enforcement environment made this a C-suite decision. The plans that treat it that way are the ones building programs that boards can defend.