The Relationship Risk Nobody Measures
Risk adjustment programs depend on providers. Providers document patient conditions. That documentation becomes the clinical evidence that supports HCC codes. Without adequate provider documentation, no amount of coding technology or chart review volume produces defensible submissions. The relationship between the plan and its provider network is the foundation the entire program builds on.
Retrospective chart review, by its nature, introduces friction into that relationship. Plans request charts from providers, often in high volume. Coders identify diagnoses the provider documented but didn’t code, which can feel like a criticism of the provider’s work. Provider queries ask physicians to clarify or amend notes from visits that happened weeks or months ago, adding administrative burden to an already-strained workflow. Some programs pressure providers to accept coding recommendations they disagree with clinically.
The cumulative effect is provider abrasion: a gradual erosion of the provider’s willingness to cooperate with the plan’s risk adjustment activities. Abrasion doesn’t announce itself. Providers don’t send formal complaints. They just stop prioritizing record requests. They delay query responses. They push back on coding recommendations. Documentation quality, which the plan needs more than ever, declines because the provider sees risk adjustment as an administrative burden rather than a clinical collaboration.
How Abrasion Shows Up in Program Metrics
Provider abrasion is invisible in most program dashboards. Plans track charts processed, codes added, and RAF uplift. They rarely track provider response rates to record requests, query resolution timelines, or documentation quality trends by provider. When these metrics are measured, the pattern is often clear: a subset of providers with declining response rates, increasing query backlogs, and progressively thinner documentation, all correlated with heavy retrospective review activity.
The OIG’s February 2026 compliance guidance reinforced why this matters. The guidance warns about diagnoses generated through processes disconnected from patient care. When provider abrasion degrades documentation quality, the codes derived from that documentation become harder to defend. The plan’s coding technology may be excellent. But if the documentation feeding it is getting worse because providers are disengaged, the output degrades regardless of how good the AI is.
Reducing Abrasion Through Program Design
Programs that minimize abrasion share three design principles. First, they make provider interactions clinical, not administrative. Queries are framed as clinical questions (“Can you confirm current management of this patient’s CKD?”) rather than coding instructions (“Please add HCC 138 to this encounter”). The provider engages as a clinician rather than resisting as a data entry point.
Second, they invest in pre-visit intelligence that reduces the need for post-visit queries. When conditions are surfaced before the visit, the provider addresses them during the encounter. Documentation is generated naturally. No query is needed because the information was captured in real time.
Third, they provide specific, actionable feedback rather than volume-based requests. Instead of sending 50 generic queries per week, the program sends 10 targeted ones with clinical context. Provider response rates increase because each query is worth the provider’s time.
The Quality That Depends on the Relationship
Retrospective hcc coding programs that damage provider relationships are undermining the input their own technology depends on. The most sophisticated AI in the market can’t produce defensible coding from documentation that providers have stopped caring about. Plans that measure provider abrasion alongside coding metrics, and design their programs to maintain rather than erode provider cooperation, are protecting the documentation quality that determines whether their submitted codes survive audits.