Chronic Care Management Under Medicare Advantage

The One-Line Answer: CCM Billing Mechanics Don’t Change Under MA

Chronic Care Management is billable for Medicare Advantage enrollees on the same eligibility and documentation basis as traditional fee-for-service Medicare. Two or more chronic conditions, a completed initiating visit, a comprehensive care plan, minimum monthly coordination time. Nothing about the CPT codes themselves (99490, 99439, 99487, 99491) changes because a patient is enrolled in an MA plan instead of Original Medicare.

What changes is everything sitting one layer above the claim: how the plan that’s paying you actually makes money, and why that gives you a second, non-obvious reason to get your CCM documentation right.

Where It Actually Diverges: Capitation and Risk Adjustment

Original Medicare pays fee-for-service. Bill a code, get paid the code’s rate, done. Medicare Advantage plans work differently at the plan level: CMS pays MA plans a capitated amount per enrollee per month, and that capitation is risk-adjusted through Hierarchical Condition Category (HCC) coding, which converts documented diagnoses into a Risk Adjustment Factor (RAF) score for each member.

To make this concrete: a healthy 70-year-old enrollee with no chronic conditions might carry a RAF score around 0.3-0.5, translating to a lower monthly capitation payment. A 70-year-old with documented diabetes with complications, chronic kidney disease stage 3, and heart failure could carry a RAF score above 2.0, several times higher, because the documented condition burden is several times higher. The dollar difference in monthly capitation between those two RAF scores, multiplied across a panel of several hundred or several thousand MA enrollees, is the actual financial stake behind documentation completeness.

A higher RAF score, driven by more complete documentation of a patient’s actual chronic conditions, means a higher capitated payment to the plan for that patient. This isn’t a hidden mechanism. It’s the entire design principle behind MA’s payment model: pay more for sicker, more complex patients, less for healthier ones, so plans aren’t incentivized to avoid enrolling people with real chronic disease burden.

The practical consequence for anyone running CCM inside an MA-heavy panel: your CCM documentation isn’t just supporting your own CCM claim anymore. It’s also, incidentally, the same clinical evidence an MA plan needs to code HCC categories accurately. Two different payment systems, reading the same chart, for two different reasons.

Why HCC Coding Completeness Becomes a Second Reason to Get CCM Documentation Right

Here’s the specific mechanism. A comprehensive CCM care plan already requires documenting every active chronic condition, its current status, and the interventions addressing it, because that’s what CMS requires for CCM eligibility and audit defense. HCC coding requires exactly the same underlying clinical specificity: not “diabetes,” but the ICD-10 code that reflects whether it’s controlled, with complications, or without, because that specificity is what maps to a given HCC category and its associated RAF weight.

A CCM program that documents chronic conditions loosely (vague problem list entries, missed annual re-documentation of conditions that don’t have an acute visit that year) is very likely also under-coding HCC categories for the same patients, which understates the plan’s RAF score and, by extension, understates the capitation the plan receives for that member. Under risk-sharing or value-based arrangements between a provider group and an MA plan, that understatement can flow directly back to the provider group’s own revenue, not just the plan’s.

This is why a hospital or practice group with a substantial MA panel has a real, quantifiable reason to treat CCM documentation completeness as a dual-purpose asset: audit defense for the CCM claim itself, and coding completeness for the plan’s risk-adjustment submission, both served by the same structured care plan, done once, done well.

The Practical Workflow Difference for a Mixed FFS/MA Panel

Most hospitals and practices don’t run a pure FFS or pure MA panel. They run a mix, and the CCM workflow needs to handle both without creating two parallel documentation standards.

The workflow difference is subtle but real: for FFS patients, the care plan needs to satisfy CCM’s own audit criteria and nothing more. For MA patients, the same care plan should also carry the ICD-10 specificity that supports accurate HCC coding, which in practice means capturing condition status and complications at a level of detail that a minimally-compliant FFS-only CCM workflow might skip. A platform or process built only to the FFS bar will pass a CCM audit for MA patients too, but it will systematically under-document HCC-relevant detail that has real financial consequences for the plan relationship, consequences that never show up in a CCM-specific audit because that’s not what a CCM audit checks for.

What This Means for Software, Not Just Billing Policy

A CCM platform that treats every patient’s documentation the same way, regardless of payer type, is missing a real operational lever. The technical fix isn’t complicated: flag payer type (FFS vs. MA) at the patient level, and for MA patients, prompt for the additional condition-status specificity that HCC coding rewards, as a normal part of the same care-plan workflow the coordinator is already doing for CCM compliance. This isn’t a separate process bolted on. It’s the same documentation step, done to a slightly higher specificity bar, for the subset of patients where that specificity has a second payoff.

Platforms built as a single generic layer on top of “the EHR” in the abstract tend to miss this distinction entirely, because payer-type-aware documentation prompts require actually knowing which plan a patient is enrolled in and what that plan’s coding needs are, not just tracking CCM minutes in general.

The Compliance Angle: Two Audiences for the Same Documentation

CCM documentation already has one audience: CMS auditors checking eligibility, consent, and time logs, with Chronic Care Management specifically named in the Office of Inspector General’s 2026 Work Plan. For an MA-heavy panel, there’s a second audience: the MA plan’s own Risk Adjustment Data Validation (RADV) process, which periodically reconciles submitted HCC codes against the medical record to confirm the diagnoses were actually documented and supported at the time of service, not inferred or carried forward from a prior year without a current-year encounter that supports them.

The two review processes look for different things but reward the same underlying discipline. A CMS CCM audit wants proof that coordination time was real and that consent and eligibility were properly established. A RADV review wants proof that a diagnosis code submitted for risk adjustment was actually documented, with clinical specificity, during a face-to-face or otherwise qualifying encounter in the relevant payment year. A care plan that’s vague on condition status (“diabetes, stable”) passes neither test well. One that’s specific (“Type 2 diabetes mellitus with diabetic chronic kidney disease, stage 3b, managed with insulin and ACE inhibitor, reviewed this visit”) supports both.

A care plan built well enough to survive a CCM audit and a RADV review, using the same underlying documentation, is a meaningfully stronger asset than one built to satisfy only the first. Getting there requires the specificity discussed above baked into the workflow, not reconstructed after the fact when a plan’s coding team comes asking for supporting documentation on a patient months later.

How Mindbowser Approaches This

We build CCM platforms that know the difference between a Medicare FFS patient and a Medicare Advantage patient at the workflow level, not just the billing level. That means condition-documentation prompts that adjust based on payer type, structured care plans that carry ICD-10 specificity sufficient for both CCM audit defense and HCC coding support, and a single documentation workflow that serves both purposes instead of asking care coordinators to think about two different standards depending on which plan a patient happens to be enrolled in.

This sits inside the same custom CCM platform work we do for organizations building or fixing a CCM program from the ground up, and it’s the kind of detail that a generic, EHR-agnostic CCM tool typically doesn’t handle, because it requires knowing both CCM’s audit requirements and HCC’s coding logic well enough to build a workflow that satisfies both at once. CarePlan AI is one of the accelerators that shortens this build, generating structured care plans from clinical data with the specificity level configured per payer type rather than a single generic template.