Providers Aren’t Coding Resources. Stop Building Tools That Treat Them That Way.

The Encounter Advantage
There’s a simple hierarchy in risk adjustment defensibility: a diagnosis documented during a face-to-face clinical encounter is harder to challenge than one discovered during a retrospective chart review months later. CMS knows this. OIG knows this. And the February 2026 Industry-wide Compliance Program Guidance made it explicit by flagging diagnoses from health risk assessments that were never considered in patient care.
Encounter-based coding creates defensibility by design. The provider sees the patient. The provider documents findings in real time. The codes emerge from that clinical interaction. Every element auditors look for, a qualified provider, a dated encounter, clinical evidence of active management, exists because the care actually happened. There’s no interpretation gap between a historical chart and a coder’s judgment months later.
That doesn’t mean retrospective review is illegitimate. It means the safest, most audit-proof codes are the ones born from real clinical encounters. And that makes prospective coding the growth path for any plan serious about long-term defensibility.
Why Previous Prospective Programs Failed
The concept isn’t new. Plans have tried provider-facing risk adjustment tools for years. Most underperformed. The reason wasn’t the technology. It was the approach.
Early programs treated providers as coding extensions. They bombarded clinicians with pop-up alerts during patient visits. They generated lengthy HCC checklists unrelated to the reason for the encounter. They created pressure to “close gaps” that had nothing to do with the clinical question in front of the provider. Physicians pushed back. Documentation quality dropped. Some programs generated codes that auditors found suspicious because they didn’t align with the clinical context of the visit.
Research published in the Annals of Internal Medicine found that primary care physicians spend nearly two hours on EHR work for every hour of direct patient care. Tools that add to that burden fail. Tools that reduce it succeed. The distinction between decision support and documentation coercion is the difference between a program providers adopt and one they sabotage.
The lesson for any plan building a prospective program: if providers hate the tool, the tool is the problem, not the providers.
The Three-Phase Approach That Works
Effective prospective programs operate across three phases without overwhelming the provider at any single point. Before the visit, AI reviews the patient’s clinical history and surfaces conditions that need attention based on prior documentation, lab results, and medication records. The provider gets clinical context, not a revenue wish list.
During the visit, decision support highlights documentation gaps rather than dictating codes. If a patient has CKD Stage 3 with no recent GFR lab in the record, the system flags it as a clinical consideration. The provider decides how to respond. The tool informs. It doesn’t instruct.
After the visit, post-encounter review catches mismatches between documentation and coding. If the provider documented thorough diabetes management but the corresponding HCC wasn’t captured, the system flags the gap. If a code was assigned without adequate MEAT support in the note, it gets flagged for review before submission. Three checkpoints. None of them require the provider to do coding work during the patient encounter.
Where the Industry Is Heading
CMS’s regulatory trajectory points clearly toward encounter-based documentation as the standard for defensible risk adjustment. Retrospective review will always have a role in reconciliation and cleanup, but the codes that carry the least audit risk and the highest defensibility are the ones generated during clinical care.
Plans investing in Prospective Risk Adjustment Coding are building their programs around that reality. Every code starts with a clinical encounter. Every diagnosis is supported by contemporaneous documentation. Every submitted HCC has a clear evidence trail that connects coding to care. That’s the structural advantage that compounds over time, and it’s the approach regulators are explicitly encouraging.


