The healthcare industry is undergoing a fundamental shift from a fee-for-service model to a value-based care (VBC) model. This shift means that provider reimbursement now depends on cost efficiency, quality standards, and patient outcomes rather than the number of visits. It emphasizes the importance of thorough, timely, and accurate clinical documentation. In this environment, virtual medical scribes are becoming a critical partner for clinicians. This development has a direct impact on both the quality of patient care and financial performance.
Medically and clinically reviewed by the ScribeRunner Clinical Documentation Team |
Why This Matters Now
Value-based care (VBC) no longer rewards providers simply for seeing patients it rewards them for proving, on paper, how sick those patients actually are and how well they were cared for. That proof lives entirely in clinical documentation.
2026 is a pivotal year for this conversation. It's the first full payment year under the CMS-HCC V28 risk adjustment model, which replaced the two-decade-old V24 framework. This isn't a minor coding update it directly changes how much practices get paid for the same patients. Based purely on how those patients are documented, whether captured through ambient clinical intelligence or traditional scribe support.
This article breaks down what changed. why documentation accuracy now matters more than ever under V28, and what practices can practically do about it from the people. Who review clinical charts for a living.
What Changed Under CMS-HCC V28
The CMS-HCC model is the formula Medicare Advantage uses to predict how costly a patient's care will be. Based on their documented chronic conditions and demographics. Practices treating sicker. More complex patients are supposed to be paid more but only if that complexity is actually captured in the chart.
Under V28, fully phased in for payment year 2026:
- The number of diagnosis codes that map to a Hierarchical Condition Category (HCC) dropped from roughly 9,800 to about 7,770.
- The number of HCC categories itself actually increased from 86 to 115, meaning conditions are now sorted more precisely.
- Roughly 2,300 diagnosis codes were removed from risk-scoring eligibility and around 270 new codes were added.
- Condition coefficients (the dollar-weight assigned to each HCC) were recalculated using more recent claims data.
The net effect: a condition that generated an HCC and therefore reimbursement credit under V24 may not qualify under V28. Even if it's the exact same diagnosis. Practices that don't update how they document chronic conditions are, in effect, taking a pay cut without anyone changing their patient panel.
Why Documentation Precision, Not Just Presence, Now Decides Reimbursement
Under the older model, simply listing a condition in the chart was often enough. V28 is built around clinical specificity vague or unsupported diagnoses are far more likely to be rejected during risk-score calculation.
This is where the MEAT standard (Monitor, Evaluate, Assess/Address, Treat). Has become the practical benchmark auditors and payers use to judge whether a documented condition is defensible:
- Monitor – Are symptoms, labs, or imaging related to the condition being tracked over time?
- Evaluate – Does the note show clinical judgment about the condition's status?
- Assess/Address – Is there a plan, referral, or medication change tied to it?
- Treat – Is an intervention documented, even if it's just medication continuation?
A condition mentioned once in a problem list without any of the above is increasingly treated as unsupported which means it contributes nothing to the risk score, regardless of how sick the patient actually is.
Where Practices Are Losing Reimbursement Without Realizing It
Based on patterns our clinical documentation specialists see across internal medicine, primary care, and specialty practices, three gaps consistently cost practices HCC-eligible revenue:
- Chronic conditions documented once a year, then forgotten. A condition captured at the annual wellness visit but never touched again all year has no MEAT support at the next risk-adjustment checkpoint.
- Combination codes left unspecified. V28's narrower code set often rewards specificity (e.g., diabetes with a documented complication) over generic diagnosis shorthand.
- Documentation completed after the encounter, from memory. Details that support Monitor/Evaluate/Assess/Treat are the first things lost when notes are written hours later instead of in real time a risk we cover in more depth in our guide to how live documentation compares to after-the-fact charting.
This kind of upcoding versus under-coding risk is also a compliance issue, not just a revenue one. Practices navigating V28 should also review how these documentation gaps intersect with audit exposure under AI scribe upcoding rules.
How Real-Time Documentation Support Closes the Gap
This is the specific, practical role a trained virtual medical scribe plays in a V28 environment not just typing faster, but structuring notes so they hold up under risk-adjustment review:
- Capturing comorbidities and status updates during the visit, while clinical detail is still fresh and specific
- Flagging when a chronic condition lacks a current-year MEAT trail, so the physician can address it before the visit ends
- Using consistent, audit-ready phrasing for chronic disease status rather than shorthand that gets rejected downstream
- Ensuring quality-measure documentation (screenings, counseling, follow-up scheduling) is captured in the same visit it happens, rather than reconstructed later
For a broader look at how this model works end-to-end from the AI-drafted first pass to physician sign-off see how Scribe EHR and EMR services improve medical documentation. And because risk-adjustment revenue is only half the reimbursement picture, practices often pair this with tighter insurance verification and prior authorization workflows to prevent revenue loss on the claims side as well.
None of this replaces physician judgment the physician still makes every clinical decision. The scribe's job is making sure that decision is captured completely enough to survive both a payer audit and an HCC review. Practices weighing whether this level of support is worth the cost can see a fuller breakdown in are virtual medical scribes worth the investment?
Frequently Asked Questions
Does V28 mean practices will get paid less overall?
Not necessarily CMS applies a coding-intensity adjustment across Medicare Advantage broadly. But at the individual-practice level, revenue depends entirely on whether documentation meets the new specificity bar. Practices with strong documentation habits are largely insulated; those relying on old shorthand are more exposed.
Is this only relevant to Medicare Advantage practices?
V28 specifically governs Medicare Advantage risk adjustment, but the underlying principle that documentation specificity drives reimbursement is spreading into commercial ACOs and Medicaid managed care risk models as well.
Can a virtual scribe actually understand HCC/MEAT requirements, or is that only a coder's job?
Coders remain responsible for final code assignment. A well-trained scribe's role is upstream of that making sure the clinical detail coders need is actually in the note, in the visit it happened, rather than coders having to query the physician afterward.
What's the fastest way for a practice to check its own exposure to V28?
Pull a sample of charts for patients with chronic conditions documented at the last annual visit and check whether each has a MEAT-supported touchpoint this calendar year. Gaps found this way are the most common early warning sign the same chart-level review process we describe in what hospital screening actually involves.
This article reflects CMS-HCC V28 policy as fully implemented for payment year 2026. Risk adjustment policy is subject to ongoing CMS rulemaking; practices should confirm current requirements with their compliance team or CMS guidance directly.