Value-Based Care Revenue Models: How VBC Changes the Revenue Cycle (2026)

The VBC Revenue Reality in 2026

Let's start with where things actually stand, not where conference keynotes say they stand. Value-based care has been "the future of healthcare payment" for over a decade. In 2026, the transition is real but incomplete, and the operational gap between organizations that have figured out VBC revenue and those still treating it as an experiment is wider than ever.

On the Medicare side, CMS now has more than 13.4 million beneficiaries in accountable care relationships through the Medicare Shared Savings Program (MSSP) across roughly 480 ACOs. ACO REACH, the successor to the Direct Contracting model, serves approximately 2.5 million beneficiaries through 103 participating entities. The MSSP generated $4.1 billion in gross savings in performance year 2024, with 75% of participating ACOs earning shared savings payments. These are not pilot program numbers. This is a multi-billion-dollar payment system operating at national scale.

The mandatory side is expanding rapidly. CMS launched the Transforming Episode Accountability Model (TEAM) in January 2026, requiring bundled payments for surgical episodes in approximately 25% of U.S. hospital markets. TEAM is not voluntary. If your hospital is in a selected market and performs qualifying procedures, you are in the program whether you built the infrastructure or not. The Making Care Primary (MCP) model is rolling out across eight states, restructuring primary care payments with prospective per-patient-per-month payments layered on top of reduced FFS rates.

On the commercial side, the penetration story is more nuanced. Large national and regional payers have expanded their VBC contract offerings, and roughly 60% of commercial payer contracts now include some form of quality incentive or shared savings component. But "some form" does a lot of heavy lifting in that statistic. Many commercial VBC arrangements are what I call "VBC lite": pay-for-performance bonuses layered on top of standard FFS rates, with quality thresholds set low enough that most participants earn the bonus without meaningfully changing care delivery. Truly at-risk commercial contracts, where the provider bears downside risk on total cost of care, remain concentrated among large health systems and sophisticated physician groups.

Medicaid is the other major frontier. State Medicaid programs have accelerated VBC adoption through managed care organization (MCO) contracts that pass value-based risk down to provider groups. Over 30 states now require their Medicaid MCOs to move a percentage of provider payments into VBC arrangements, with targets ranging from 30% to 60% of total medical spend by 2027. For organizations serving Medicaid populations, particularly behavioral health providers and FQHCs, this means VBC contract participation is increasingly a condition of network inclusion rather than an optional growth strategy.

The employer market adds another layer. Large self-insured employers are contracting directly with provider groups through models like direct primary care (DPC), centers of excellence for high-cost procedures, and total cost of care arrangements administered through third-party administrators. These commercial VBC contracts often have more favorable terms than Medicare programs because the employer is motivated to reduce trend and willing to share savings generously to achieve that goal. The catch is that employer contracts are less standardized. Every deal is bespoke, and the revenue cycle infrastructure must adapt to contract-specific attribution rules, quality measures, and reconciliation timelines.

The bottom line: if you are a healthcare organization of any meaningful size, some portion of your revenue already flows through value-based arrangements, and that portion is growing. The question is not whether to engage with VBC but whether your revenue cycle infrastructure can handle it without hemorrhaging margin.

VBC Payment Model Taxonomy

Not all value-based contracts are created equal, and treating them as interchangeable is one of the most common mistakes I see organizations make. Each payment model carries different risk profiles, cash flow characteristics, and revenue cycle requirements. Understanding the taxonomy is prerequisite to building the right operational infrastructure.

The critical insight from this taxonomy is that revenue cycle complexity increases non-linearly as you move from left to right. Shared savings with upside-only risk adds a modest reporting burden to your existing FFS revenue cycle. Global capitation essentially requires you to build a parallel financial operating system. Most organizations underestimate this complexity gradient, and many that fail in VBC do so not because their clinical programs were inadequate but because their revenue cycle operations could not handle the financial mechanics.

One pattern I have seen repeatedly: organizations sign a two-sided risk contract because the savings share is higher, without fully appreciating that two-sided risk requires real-time cost monitoring, financial accruals, stop-loss procurement, and the organizational discipline to intervene when costs trend above benchmark mid-year. Upside-only shared savings is forgiving. Two-sided risk is not.

There is also a progression dynamic that organizations need to understand. CMS has been systematically pushing MSSP ACOs from upside-only tracks toward two-sided risk. Under current rules, ACOs entering MSSP can remain in upside-only risk (the BASIC track, levels A through C) for a limited period before they must advance to two-sided risk (BASIC levels D and E, or the ENHANCED track). The timeline depends on revenue and agreement period, but the direction is clear: CMS views upside-only as a training-wheels arrangement, not a permanent home. Your VBC revenue cycle strategy should be built for the risk level you will eventually need to operate at, not the one you start with.

Commercial payers are following the same progression. Many start provider relationships with pay-for-performance bonuses, then move to upside-only shared savings, then to two-sided risk, and eventually to partial or global capitation. Each step increases both the financial opportunity and the revenue cycle complexity. Organizations that build their infrastructure for the current contract without planning for the next tier end up rebuilding systems and workflows every 18 to 24 months, which is expensive and disruptive.

How VBC Fundamentally Changes Revenue Cycle Operations

Fee-for-service revenue cycle operations follow a linear, transactional model: schedule a patient, verify insurance, provide a service, document it, code it, bill it, collect it, manage denials, repeat. The core competency is claim throughput. The faster and more accurately you can convert encounters into paid claims, the better your revenue cycle performs.

Value-based care breaks this model. Revenue is no longer solely a function of claim volume and collection efficiency. It is a function of population health outcomes, cost management, quality measure performance, risk adjustment accuracy, and the ability to track and influence the total cost of care for a defined population over a performance period that can span an entire year.

Here are the new operational capabilities your revenue cycle must develop:

Attribution Management

In FFS, you bill whoever walks through the door. In VBC, you are accountable for a defined population of patients who are "attributed" to your organization based on claims patterns or prospective alignment. Attribution is the foundation of everything in VBC, and it is surprisingly volatile. In our DCE, we saw 8% to 12% quarterly churn in our attributed population. Patients switch PCPs, move out of the service area, become dual-eligible and shift to a different program, or simply stop showing up. Every patient who leaves your attribution takes their benchmark dollars with them.

Your revenue cycle needs a dedicated attribution management workflow. This includes monthly reconciliation of attribution files against your active patient panel, outreach to patients at risk of dis-attribution (those who have not had a qualifying visit within the lookback period), and tracking of voluntary alignment versus claims-based attribution. In ACO REACH and its successors, the distinction between voluntary alignment and claims-based attribution has real financial consequences because voluntarily aligned beneficiaries count toward your minimum population threshold and tend to have more stable attribution.

Attribution also determines which patients' costs count against your benchmark. If a high-cost patient who uses your ED three times per year is not attributed to your organization, their costs do not affect your performance. If they are attributed, every dollar spent on their care counts. Understanding your attributed population's cost profile, not just its size, is essential. We built a monthly attribution report that tracked total attributed lives, new attributions, dis-attributions, and the average RAF score and historical cost for each cohort. This report became one of the most important financial documents in our DCE because it provided early warning of benchmark exposure changes before they showed up in financial reconciliation.

Quality Measure Tracking

In most VBC contracts, the quality score is not just a report card. It is a revenue multiplier. In MSSP, your quality performance determines the percentage of savings you actually receive. Score in the top decile, and you keep a larger share of the savings pool. Score poorly, and your savings share is reduced or eliminated entirely, even if you achieved cost savings. This means quality measure performance is a direct revenue cycle function.

Revenue cycle teams need real-time visibility into quality measure gaps: which patients are due for a diabetic eye exam, an annual wellness visit, a colorectal cancer screening, or a depression screening follow-up. These are not clinical abstractions. Each missed measure reduces your quality score, which reduces your revenue. We tracked 33 quality measures in our DCE. Each one required a data pipeline, a gap identification workflow, a patient outreach process, and a documentation capture protocol.

The quality measure landscape itself is shifting. CMS has moved toward all-payer, electronic clinical quality measures (eCQMs) sourced from EHR data rather than claims-based measures. This means your EHR must be configured to capture the data elements required for measure calculation, and your revenue cycle team must understand which clinical documentation fields feed which quality measures. A provider who documents a blood pressure reading in a free-text note rather than in the structured vital signs field may have clinically assessed hypertension control but failed the quality measure because the EHR cannot extract the data for measure calculation. These are revenue cycle problems disguised as clinical documentation problems.

The financial impact of quality performance is substantial and direct. In MSSP, the quality score can reduce your shared savings by up to 100%. An ACO that generates $5 million in gross savings but scores in the bottom quartile on quality may receive only $2 million to $3 million after the quality adjustment, or in extreme cases, nothing at all. In ACO REACH, quality performance similarly gates access to savings and can reduce the capitation rate. We estimated that each 5-point improvement in our composite quality score was worth approximately $800,000 in additional shared savings revenue. That made quality measure tracking one of the highest-ROI revenue cycle investments we made.

Risk Adjustment Coding (HCC)

Risk adjustment is where clinical documentation and revenue cycle converge in VBC. The Hierarchical Condition Category (HCC) model assigns a Risk Adjustment Factor (RAF) score to each patient based on their documented diagnoses. This RAF score directly determines the spending benchmark against which your performance is measured. If your patients are sicker than average but your documentation does not capture that acuity, your benchmark will be set too low, and you will appear to be overspending when you are actually providing appropriate care to a complex population.

I will go deeper on HCC coding in its own section below, but the revenue cycle implication is straightforward: every encounter is a risk adjustment capture opportunity. Your coders, your providers, and your documentation improvement specialists need to understand that in VBC, a diagnosis that is documented but not coded is revenue left on the table. Not because it generates a claim payment, but because it raises the benchmark against which your total cost of care is measured.

Care Management Documentation

VBC contracts often reimburse care management activities that generate no revenue in FFS. Chronic Care Management (CCM), Transitional Care Management (TCM), care coordination calls, medication reconciliation, and social determinant interventions all have VBC value because they reduce downstream utilization. But they only reduce downstream utilization if they actually happen, and they only count for quality reporting if they are documented in structured, reportable formats.

Revenue cycle teams must build documentation workflows for these non-visit-based activities. In FFS, if a nurse spends 30 minutes coordinating a patient's discharge plan, that work is invisible to the revenue cycle. In VBC, that same 30 minutes might prevent a readmission that would cost $15,000 against your benchmark. The revenue cycle needs to capture, document, and value these activities.

There is also a direct billing opportunity that many VBC organizations miss. CCM (CPT 99490, 99491), TCM (CPT 99495, 99496), and Principal Care Management (CPT 99424, 99425) are billable under FFS in addition to their VBC value. A well-structured care management program generates FFS revenue through these codes while simultaneously reducing total cost of care against the VBC benchmark. We generated approximately $840,000 in annual CCM and TCM billing revenue from our care management program, on top of the utilization reductions that contributed to our shared savings. Organizations that treat care management as a pure cost center in their VBC financial models are leaving money on the table.

Financial Reconciliation

FFS reconciliation is straightforward: you compare expected payments to actual payments and pursue the difference. VBC reconciliation is a multi-layer process that happens on different timescales. You need to track attributed patient costs against the benchmark on a monthly or quarterly basis, model projected year-end performance, reconcile interim capitation or care management payments against actual costs, and account for quality score adjustments that may not be finalized until months after the performance year ends.

In our DCE, the final reconciliation statement from CMS arrived 14 months after the end of the performance year. That means we were making operational decisions in January 2025 based on financial performance data from a performance year that ended in December 2023. Your revenue cycle finance team needs to become comfortable operating with this level of temporal ambiguity, and your CFO needs to understand that VBC financial results are inherently backward-looking.

Building the VBC Revenue Cycle Tech Stack

Fee-for-service revenue cycle technology is mature and well-understood: an EHR for documentation, a practice management system for scheduling and claim submission, a clearinghouse for electronic claim routing, a denial management platform, and a patient payment solution. These tools optimize the linear claim-to-cash workflow.

VBC requires a fundamentally different technology stack layered on top of (not replacing) the FFS infrastructure. Here is what you need and why:

Population Health Management Platform

This is the operating system for VBC. A population health platform aggregates clinical, claims, pharmacy, lab, and social determinant data across your attributed population to create a unified patient registry. It powers patient risk stratification, care gap identification, quality measure tracking, and utilization trend analysis. Without it, you are flying blind.

The leading platforms, such as Epic Healthy Planet, Arcadia, Innovaccer, and Lightbeam Health Solutions, vary significantly in their data integration capabilities, analytics depth, and workflow automation. The key evaluation criteria for a VBC revenue cycle are: Can it ingest multi-source data (claims, clinical, ADT feeds, HIE data)? Can it generate actionable care gap worklists? Does it provide real-time financial performance dashboards? And critically, does it integrate with your existing EHR and billing system, or does it sit as an isolated island?

Risk Stratification Engine

Risk stratification assigns each patient to a risk tier based on clinical complexity, utilization history, and social factors. This drives care management resource allocation: your most expensive resource (dedicated care managers) should be focused on the patients most likely to generate avoidable high-cost events. Most population health platforms include risk stratification functionality, but the sophistication varies. Basic platforms use simple rules (e.g., number of chronic conditions plus ED visits). Advanced platforms use predictive models that incorporate claims trajectories, medication adherence patterns, and social vulnerability indices.

From a revenue cycle perspective, risk stratification directly impacts financial performance. If you deploy care management resources based on gut instinct rather than data-driven risk scores, you will over-invest in stable patients and under-invest in the rising-risk patients who drive the majority of avoidable spending.

HCC Coding and Risk Adjustment Tools

These tools analyze clinical documentation and encounter data to identify risk adjustment coding opportunities, meaning documented conditions that are not being captured in claims or conditions that lack the specificity required for accurate HCC mapping. Products like Episource, Vatica Health, and CodaMetrix use natural language processing and claims analysis to surface suspected conditions, flag documentation gaps, and generate provider queries. The ROI on these tools is among the highest of any VBC technology investment because each additional HCC code captured directly increases your benchmark, improving your savings opportunity without changing a single clinical intervention.

Care Gap Closure Workflow

Care gap closure is where quality measure tracking translates into patient outreach and intervention. Your technology needs to identify patients who are overdue for preventive services, screenings, or chronic disease management milestones, and then route those gaps into actionable workflows: automated outreach (text, email, portal messages), staff-driven phone campaigns, and provider-facing alerts at the point of care. The gap between "knowing a patient needs a screening" and "actually getting that screening completed and documented" is where most VBC quality performance is won or lost.

Quality Measure Dashboards

Your revenue cycle team needs real-time visibility into quality measure performance at the organization, practice site, and individual provider level. The dashboard must show current performance rates against targets, gap closure trends over time, projected year-end quality scores, and the estimated financial impact of quality performance on shared savings or bonus payments. This is not a clinical quality reporting tool, though it serves that purpose too. In VBC, it is a financial performance tool.

Financial Reconciliation and Modeling

This is the most underinvested area of the VBC tech stack. You need tools that can ingest claims data, attribution files, and benchmark information to project your financial performance throughout the year. The best tools allow scenario modeling: What happens to our projected savings if we reduce readmissions by 2 percentage points? What if 500 patients dis-attribute? What is our exposure if the catastrophic case stop-loss does not kick in?

Many organizations try to do this in Excel. It works, barely, for a small shared savings program. It fails catastrophically for two-sided risk or capitation arrangements where real money is at stake. Purpose-built VBC financial platforms like Signify Health (now part of CVS), Aledade's internal tools, or Evolent Health's analytics suite provide the reconciliation infrastructure that complex VBC contracts require.

Data Integration Layer

Underneath all of these tools sits the data integration challenge that is arguably the hardest technical problem in VBC. Your population health platform needs data from your EHR (clinical data), your practice management system (visit and billing data), CMS or payer claims feeds (total cost data for your attributed population including services delivered by other providers), pharmacy benefit managers (medication adherence data), health information exchanges (ADT feeds for hospital admissions and ED visits), and potentially labs, social service agencies, and community health workers.

Each data source has its own format, latency, and quality issues. CMS claims data arrives 60 to 90 days after the service date. ADT feeds are real-time but often incomplete. EHR data is rich but unstructured. Getting all of this data into a single platform, deduplicated, normalized, and linked to the correct patient, is a data engineering project that most organizations underestimate by a factor of three to five. Budget 20% to 30% of your VBC technology investment for data integration alone, and expect the first six months after platform deployment to be consumed primarily by data quality remediation.

Lessons from Building a Direct Contracting Entity

I spent two years building and operating a Direct Contracting Entity under the original GPDC model, which later became ACO REACH. We started with a network of 47 primary care providers across 12 practice sites, attributed roughly 14,000 Medicare beneficiaries, and took on professional capitation with a total cost of care benchmark. What follows are the operational lessons that no consultant or CMS webinar will teach you, because they only become visible when you are the one signing the participation agreement and managing the bank account.

Attribution Volatility Will Surprise You

CMS provides quarterly attribution alignment files. Each file can change your attributed population by 5% to 12%. In our first year, we started with 14,200 attributed beneficiaries in January, dropped to 13,400 by June, and recovered to 14,800 by December. That is a variance of 1,400 patients across the year, each carrying roughly $12,000 to $14,000 in annual benchmark value. The financial swing from attribution changes alone was over $10 million in benchmark exposure.

The causes of attribution churn include beneficiaries switching PCPs, moving out of the service area, entering nursing facilities (which shifts attribution to the facility's affiliated provider), becoming dual-eligible and moving to a D-SNP plan, or dying. You cannot prevent all of these, but you can mitigate them. We implemented a dedicated attribution management function that tracked beneficiaries at risk of dis-attribution (no qualifying visit in 6+ months) and triggered outreach to schedule annual wellness visits or chronic care management encounters. This single workflow stabilized our attribution and added an estimated $3.2 million in benchmark value over the year.

Benchmark Methodology Is a Black Box

The spending benchmark that determines whether you earned savings or owe losses is set by CMS using a methodology that incorporates historical spending, regional cost trends, risk adjustment, and various normalization factors. The methodology is documented in the participation agreement and operating manual, but understanding how changes in your patient population, coding patterns, or regional spending trends will affect next year's benchmark requires actuarial expertise that most provider organizations do not have in-house.

We hired a consulting actuary to model our benchmark projections and still found that CMS's final calculations differed from our projections by 3% to 5%. On a $180 million benchmark, a 3% discrepancy is $5.4 million. That is the difference between celebrating shared savings and writing a repayment check. The lesson: budget for professional actuarial support, build conservative financial projections that assume a negative variance on the benchmark, and never count shared savings as revenue until the final reconciliation statement arrives.

Cash Flow Timing Is the Silent Killer

In our capitated arrangement, CMS made monthly capitation payments based on a prospectively set rate. These payments were designed to cover the cost of professional services for our attributed population. The actual reconciliation against the total cost of care benchmark happened annually, with the final settlement arriving approximately 14 months after the end of the performance year. This means we were operating with a 14-month lag between financial performance and financial settlement.

The cash flow implications were significant. Our monthly capitation payments covered approximately 25% of our attributed patients' total cost of care (the professional services portion). The remaining 75%, covering hospital, specialist, post-acute, and ancillary services, was paid by CMS directly to those providers through standard FFS claims. Our financial performance depended on the total spending across all of these providers, but we received settlement based on that performance more than a year later.

We needed operating reserves to cover the period between making care management investments (which cost money upfront) and receiving the savings those investments generated (which arrived over a year later). Without adequate reserves, a DCE can be operationally successful, generate real savings, and still face a cash crisis because the savings payment has not arrived yet. We budgeted 3% of projected benchmark as operating reserves. I would recommend 5% for any new entrant.

The cash flow challenge is compounded by the accounting treatment of VBC revenue. Under ASC 606, shared savings that have not been confirmed by the payer cannot be recognized as revenue. They may be disclosed as contingent assets, but they do not appear on the income statement until the reconciliation is final. This means your organization's GAAP financial statements may show a loss during a year when you are actually generating significant VBC savings that simply have not been confirmed yet. Lenders, investors, and board members unfamiliar with VBC accounting may misinterpret this as operational underperformance. Proactive financial communication is essential: explain the timing mismatch before it shows up in the financials, not after.

Quality Bonus Structure Rewards Consistency, Not Heroics

The quality scoring methodology in Direct Contracting and ACO REACH rewards sustained performance across a broad set of measures, not exceptional performance on a handful. We made the mistake early on of focusing our quality improvement resources on the three measures where we had the largest gaps. This improved those specific measures dramatically but left other measures stagnant. The overall quality score barely moved because the scoring methodology weights consistency across the full measure set.

The better strategy, which we adopted in year two, was to identify the measures where we were closest to the next performance threshold and focus resources there. Moving a measure from the 29th percentile to the 31st percentile (crossing a threshold) had a larger impact on our quality bonus than moving a measure from the 45th to the 65th percentile. Revenue cycle teams tracking quality performance should think about quality improvement in terms of threshold proximity, not absolute gap size.

Provider Engagement Is the Rate-Limiting Step

You can build the most sophisticated attribution management, quality tracking, and risk adjustment infrastructure in the world. None of it matters if your providers are not on board. Providers in our DCE network ranged from enthusiastic early adopters who embraced population health to skeptics who viewed VBC as an administrative burden layered on top of an already overwhelming workload. The skeptics were not wrong about the burden. They were wrong about whether the burden was worth it.

We learned that provider engagement requires three things. First, transparency: providers need to see their own panel data, including attributed patient lists, quality measure performance, RAF scores, and cost benchmarks. Showing a provider that 340 of their 400 attributed patients had an annual wellness visit but 60 did not, and that closing those 60 gaps would add $45,000 in quality bonus revenue, creates actionable motivation. Second, simplicity: the workflows you ask providers to adopt must integrate into their existing encounter patterns, not add steps. Pre-visit planning sheets that highlight HCC recapture opportunities and quality gaps for the day's scheduled patients were our most effective provider tool. Third, financial alignment: in our DCE, we distributed 30% of shared savings directly to participating providers based on their individual quality and cost performance. Providers who saw direct financial benefit from VBC participation invested in the workflows. Providers whose compensation was unaffected by VBC performance treated it as optional.

Regulatory and Compliance Overhead Is Real

Operating a DCE under CMS involves continuous compliance obligations that absorb significant administrative resources. We maintained a compliance committee that met monthly, conducted annual training for all staff on fraud and abuse, filed quarterly compliance attestations, maintained beneficiary notification protocols (including the required CMS-mandated mailing to all attributed beneficiaries), managed data use agreements, and prepared for potential CMS audits. Our legal and compliance costs ran approximately $280,000 annually, and our compliance officer spent roughly 60% of their time on DCE-related matters. These costs are real, they are recurring, and they must be included in any VBC financial model.

The Dual Revenue Cycle Challenge

Unless your organization has gone 100% capitated (and almost none have), you are running two revenue cycles simultaneously. Your FFS revenue cycle continues to generate the majority of your cash flow through claim submission, denial management, and patient collections. Your VBC revenue cycle operates in parallel, tracking attributed populations, quality measures, risk adjustment, and benchmark performance against a settlement that arrives months or years later. This duality creates operational complexity that is easy to underestimate.

Parallel Workflows

Every patient encounter generates obligations in both revenue cycles. The FFS side needs accurate charge capture, clean claim submission, and timely denial follow-up. The VBC side needs risk adjustment coding completeness, quality measure documentation, care gap closure, and attribution-eligible encounter documentation. In theory, these workflows are complementary. In practice, they compete for the same staff time, the same provider attention, and the same technology bandwidth.

The most common failure mode is prioritizing FFS workflows because they generate immediate, tangible cash flow, while VBC workflows are deferred because their financial impact is delayed and less visible. A coder who spends an extra five minutes ensuring every chronic condition is captured at HCC-appropriate specificity is generating VBC value, but that five minutes might delay FFS claim submission. Without explicit organizational prioritization, FFS always wins the attention competition because the cash register is louder than the benchmark model.

Staff Training for Mixed Models

Revenue cycle staff trained in FFS billing think in transactions: encounters, claims, payments, denials. VBC requires them to think in populations: panels, cohorts, risk tiers, quality measures. This is a fundamentally different cognitive framework. You cannot achieve it with a one-hour training session and a new process document.

We found that the most effective training approach was to create dedicated VBC revenue cycle roles rather than asking existing FFS staff to add VBC responsibilities. Our attribution analyst, quality measure coordinator, and risk adjustment coding specialist were purpose-hired positions, not additional duties assigned to existing billers. The investment in headcount was significant, roughly $350,000 annually for a three-person VBC revenue cycle team, but trying to distribute VBC responsibilities across the existing FFS team was demonstrably less effective. The work either did not get done or was done poorly.

Reporting Across Two Systems

Your CFO and board need financial reporting that integrates FFS and VBC revenue into a coherent picture. This is harder than it sounds. FFS revenue is booked monthly based on claim payments. VBC revenue, particularly shared savings, is uncertain until the final reconciliation. How do you present the financial health of the organization when 15% of projected revenue exists as a contingent receivable that will not be confirmed for 14 months?

The answer requires a reporting framework that separates guaranteed revenue (FFS collections, capitation payments received) from projected revenue (estimated shared savings, quality bonuses) with explicit confidence intervals. We reported projected VBC revenue at three levels: conservative (25th percentile of our financial model), expected (50th percentile), and optimistic (75th percentile). The board quickly learned to focus on the conservative estimate for budgeting and the expected estimate for strategic planning.

Financial Modeling for Mixed-Model Organizations

The financial model for a mixed FFS/VBC organization needs to capture the interaction effects between the two revenue streams. For example, improving care management reduces avoidable utilization, which improves VBC performance. But reduced utilization also means fewer FFS encounters and less FFS revenue. If 80% of your revenue is FFS and 20% is VBC, reducing an avoidable admission by $15,000 costs you $12,000 in lost FFS revenue and gains you only a portion of that $15,000 in shared savings. The net financial impact depends on your FFS/VBC revenue mix, your savings share rate, your quality score, and whether the avoided admission would have been denied anyway.

This is the fundamental tension of the FFS-to-VBC transition: doing the right thing clinically (reducing avoidable utilization) can hurt financially until the VBC portion of revenue is large enough to offset the FFS loss. Your financial model must quantify this crossover point and inform the pace of your VBC engagement.

To illustrate: assume an organization with $50 million in annual FFS revenue and $10 million in VBC benchmark exposure (shared savings, 50% share rate). If care management reduces avoidable hospitalizations by $2 million, the FFS impact is negative $2 million in lost inpatient revenue (assuming owned or affiliated hospitals), while the VBC impact is positive $1 million in shared savings ($2 million in savings times 50% share rate). Net financial impact: negative $1 million. The organization loses money by doing the right thing until VBC revenue grows large enough to change the equation. At a 50% savings share rate, VBC benchmark exposure needs to reach at least twice the FFS revenue at risk from utilization reduction for the math to break even. Most organizations are nowhere near this crossover point, which is why the transition is slow and why running the dual revenue cycle well is a competitive advantage rather than a temporary inconvenience.

Risk Adjustment and HCC Coding

If there is one revenue cycle capability that separates successful VBC organizations from struggling ones, it is risk adjustment coding. The HCC model is the foundation of the benchmark methodology in MSSP, ACO REACH, and most commercial VBC contracts. Get it right, and your benchmark accurately reflects your patient population's acuity. Get it wrong, and you are held to a benchmark set for a healthier population than you actually serve. The financial difference can be enormous.

Why RAF Scores Matter

Every Medicare beneficiary has a Risk Adjustment Factor (RAF) score calculated from their documented and coded diagnoses. The average Medicare beneficiary has a RAF score of 1.0. A healthy 65-year-old with no chronic conditions might have a RAF score of 0.4. A 78-year-old with diabetes, COPD, CHF, and depression might have a RAF score of 2.8. The RAF score determines the expected cost of caring for that patient, which directly sets the spending benchmark.

Here is the math that matters: If your attributed population has an average RAF score of 1.2 when it should be 1.4 based on actual patient acuity, your benchmark is set approximately 14% too low. On a $180 million benchmark, that is a $25 million undershoot. Your organization would need to generate $25 million in actual cost savings just to break even, all because of incomplete diagnosis coding. I have seen organizations turn from shared losses to shared savings purely by improving risk adjustment coding accuracy, without changing a single clinical intervention or care management program.

Documentation Requirements for HCC Capture

HCC capture requires more than simply coding diagnoses. It requires specificity, clinical support, and annual recapture. The most common documentation gaps include:

• Lack of specificity. Coding "diabetes" (E11.9, unspecified type 2 diabetes) does not map to an HCC. Coding "type 2 diabetes with diabetic chronic kidney disease, stage 3" (E11.22 + N18.3) maps to two HCCs. The clinical documentation must support the specific, complicated diagnosis for the code to be assigned.
• Failure to recapture chronic conditions annually. HCC codes must be documented and coded at least once every calendar year to count toward the RAF score. A patient with COPD diagnosed three years ago who comes in for a wellness visit still needs COPD documented in that visit's assessment if you want the HCC to carry forward. Many providers assume historical diagnoses persist automatically. They do not.
• Missing comorbidities during focused visits. A patient presenting for a knee injury who also has atrial fibrillation, major depression, and morbid obesity needs all four conditions documented and coded if the visit touches on them in any way. The problem list should be reviewed and updated at every encounter. In FFS, there is no financial incentive to code the depression during a knee visit. In VBC, there is.
• Insufficient clinical support for high-value diagnoses. CMS audits risk adjustment coding, and diagnoses that lack clinical support in the documentation are subject to recovery. You cannot simply list conditions on the problem list. The documentation must show that the provider assessed the condition, noted its current status, and either continued, modified, or acknowledged the treatment plan.

Common High-Value HCC Coding Gaps

Based on our DCE experience and industry data, the diagnoses most frequently undercoded in primary care VBC settings include:

• Major depression (HCC 59). Prevalence in Medicare populations exceeds 15%, but primary care coding rates are often below 8%. Many providers treat depression with medications but do not consistently document the diagnosis as active at each encounter.
• Chronic kidney disease stages 3-5 (HCC 138/137/136). Lab data frequently shows eGFR below 60, indicating CKD, but the condition is not documented or coded. A simple lab-to-diagnosis reconciliation can surface these gaps.
• Morbid obesity (HCC 22). BMI over 40 is captured in vitals but the associated diagnosis of morbid obesity is often not coded. This is one of the easiest HCCs to capture with structured workflow.
• Diabetes with complications (HCC 18/17). Providers code unspecified type 2 diabetes (E11.9) when documentation supports diabetes with specific complications like neuropathy, nephropathy, or retinopathy. The unspecified code does not map to an HCC; the complication-specific codes do.
• Protein-calorie malnutrition (HCC 21). Common in elderly Medicare beneficiaries but rarely coded in outpatient settings. Screening tools and nutritional assessments can identify and document this condition systematically.
• Vascular disease (HCC 108). Peripheral vascular disease and atherosclerosis are frequently present on problem lists but not coded as active conditions at annual encounters.

Building a Risk Adjustment Coding Program

An effective risk adjustment program includes four components. First, retrospective chart review where certified coders review completed encounters to identify missed HCC opportunities, typically focusing on annual wellness visits and chronic care management encounters where multiple conditions should be addressed. Second, prospective provider education through regular sessions that teach providers which documentation patterns support HCC capture, using real examples from their own charts. Third, suspected condition identification using claims data, pharmacy data, and lab results to identify conditions that are likely present but not documented, such as a patient on metformin without a diabetes diagnosis coded in the current year. Fourth, pre-visit planning where care teams review patient records before scheduled visits to identify HCC recapture opportunities and quality measure gaps, ensuring the visit addresses both the presenting complaint and the risk adjustment priorities.

The annual wellness visit (AWV) is the single most important encounter for risk adjustment capture. During an AWV, the provider is expected to review the complete problem list, assess the status of all chronic conditions, update preventive care, and address care gaps. A well-structured AWV encounter template that prompts the provider to assess each active condition and document its current status can capture 80% to 90% of a patient's HCC profile in a single visit. In our DCE, we achieved 78% AWV penetration in year one and 86% in year two. Each percentage point of AWV improvement translated to approximately 0.02 improvement in average RAF score across the attributed population, which represented roughly $360,000 in additional benchmark value.

Compliance Guardrails

Risk adjustment coding optimization walks a fine line between legitimate documentation improvement and upcoding. CMS has intensified its scrutiny of risk adjustment through the Risk Adjustment Data Validation (RADV) audit program, and the False Claims Act creates significant liability for organizations that systematically overcode diagnoses to inflate RAF scores.

The guardrails you need include: coding only diagnoses that are documented, assessed, and clinically supported in the encounter note; never adding diagnoses solely from the problem list without provider assessment during the encounter; auditing a statistically significant sample (at minimum 5% to 10%) of risk-adjusted encounters quarterly; maintaining a compliance officer with authority to override revenue-driven coding pressure; and training providers on the difference between complete documentation (capturing everything that is clinically present) and inflated documentation (suggesting conditions that are not clinically justified). The standard I applied in our DCE was simple: would this documentation survive a RADV audit? If the answer was anything other than an unqualified yes, the code did not get submitted.

Financial Modeling for VBC Contracts

Before signing any VBC contract, you need a financial model that tells you whether the contract is worth taking. Not every VBC arrangement is a good deal. Some benchmarks are set too aggressively, some quality measures are misaligned with your capabilities, some patient populations have too much cost variability to manage within the contract's risk parameters, and some contracts simply do not include enough lives to achieve actuarial stability.

Here is the framework I use to evaluate VBC contracts:

Benchmark Analysis

The benchmark is the spending target against which your performance is measured. Your first question should be: Is the benchmark set at a level that gives us a realistic path to savings? You need to understand the benchmark methodology (historical trending vs. regional rate setting vs. prospective adjustment), the risk adjustment methodology (CMS-HCC vs. a proprietary model), and how the benchmark will change over time (trend factor, rebasing, convergence to regional rates).

Pull at least three years of claims data for the patient population in question. Calculate the historical cost trend. Compare the benchmark to your actual cost of care. If the benchmark is set at or below your current cost, you need a credible plan to reduce costs by a quantifiable amount within the performance period. "We will reduce readmissions" is not a plan. "We will deploy transitional care management for all high-risk discharges, which based on published evidence should reduce readmissions by 15% to 20%, saving $X per avoided readmission across Y at-risk patients" is a plan.

Stop-Loss and Risk Mitigation

In any two-sided risk or capitated arrangement, you need stop-loss protection. Patient-level stop-loss (also called individual stop-loss or specific stop-loss) caps your exposure for any single patient, typically at $50,000 to $150,000 annually. Aggregate stop-loss caps your total exposure across the entire attributed population, typically at 5% to 10% above expected costs. Without stop-loss, a single catastrophic case, a bone marrow transplant at $800,000, a premature infant in the NICU for four months, can eliminate an entire year of savings.

Price stop-loss into your financial model before you calculate expected returns. Stop-loss premiums for Medicare VBC arrangements typically run 1% to 3% of the total benchmark, depending on the attachment point and the population's risk profile. This is a non-negotiable cost of doing business in risk-bearing VBC.

Minimum Lives Threshold

Actuarial stability requires a minimum population size. The smaller your attributed population, the more volatile your per-patient cost distribution, and the more likely that a handful of high-cost cases will dominate your financial results regardless of your care management efforts. The general rules of thumb:

• Shared savings (upside only): 5,000 lives minimum, 10,000+ preferred.
• Shared savings/shared risk: 10,000 lives minimum, 20,000+ preferred.
• Bundled payments: 200+ episodes per bundle type annually for meaningful experience.
• Partial capitation: 5,000 lives minimum for the capitated service category.
• Global capitation: 15,000 lives minimum, 25,000+ preferred. Below 15,000, cost variance is too high for reliable financial performance.

If a payer offers you a global capitation contract for 3,000 lives, the answer should be no, regardless of how attractive the capitation rate appears. The actuarial math does not support it.

Break-Even Calculation

Your break-even analysis must account for all incremental costs of participating in the VBC contract. These include:

Sum these costs and compare them to your projected savings. If your projected savings at the conservative estimate (25th percentile of your financial model) do not exceed your incremental VBC costs, the contract is not worth taking unless you have a strategic rationale that justifies the investment, such as building capabilities for future, larger contracts. I have seen organizations take VBC contracts that were mathematically guaranteed to lose money because they wanted "experience in value-based care." Experience is valuable, but not at the cost of financial viability.

A useful heuristic: for a shared savings contract to break even, you generally need to generate 2% to 4% gross savings on the benchmark after accounting for the minimum savings rate (the threshold below which no savings are shared, typically 2% for one-sided risk in MSSP). If your care management and risk adjustment investments can credibly generate 4%+ gross savings, the contract is likely worth taking. If your best-case projection is 2% savings, you are betting on precision that VBC financial models rarely deliver.

Scenario Modeling: The Three Cases

Every VBC financial model should run three scenarios. The base case assumes your care management programs achieve the utilization reductions supported by your internal data or published evidence, risk adjustment coding improves at a moderate pace, and attribution remains relatively stable. The downside case assumes care management achieves 50% of projected impact, risk adjustment improvement is minimal, and you experience adverse attribution changes such as losing healthier patients while retaining complex ones. The upside case assumes all programs exceed targets and favorable attribution dynamics.

The critical question is not "what does the base case show?" It is "what does the downside case show?" If your downside scenario still generates enough savings to cover your incremental VBC costs and avoid shared losses, the contract has an acceptable risk profile. If the downside scenario shows shared losses that exceed your stop-loss coverage and operating reserves, you are taking on more risk than the opportunity justifies.

I run a simple sensitivity analysis on three variables: attributed population size (plus or minus 10%), average cost per beneficiary (plus or minus 5%), and quality score (plus or minus 10 points on the composite). The combination of worst-case values on all three variables defines your maximum downside exposure. If that number is larger than your organization is willing or able to absorb, the contract terms need to change or the contract should not be signed.

Multi-Year Contract Economics

VBC contracts are not single-year financial propositions. The first year almost always has the highest costs (infrastructure buildout, staff hiring, technology implementation) and the lowest returns (programs are ramping, data is incomplete, workflows are immature). Year two typically shows significant improvement as programs mature, and year three is where most organizations reach steady-state VBC financial performance.

Your financial model should project across the full contract term, typically three to five years. A contract that loses $200,000 in year one, breaks even in year two, and generates $1.5 million in year three has a positive cumulative return. An organization that evaluates the contract based solely on year-one performance would walk away from a profitable long-term arrangement. Conversely, a contract that requires three years of losses before reaching breakeven assumes a level of organizational patience and financial reserves that many providers do not have. Match the contract timeline to your organization's financial runway.

Frequently Asked Questions

What is the difference between shared savings and capitation in value-based care?

Shared savings is a retrospective model where providers continue billing fee-for-service but receive a percentage of any savings generated below a spending benchmark at the end of a performance year. Capitation is a prospective model where providers receive a fixed per-member-per-month payment to cover all or some services for attributed patients, regardless of actual utilization. Shared savings carries lower financial risk because FFS revenue serves as a floor, while capitation transfers insurance-like risk to the provider but offers higher upside when care is managed efficiently. Most organizations start with shared savings and gradually progress toward capitation as their population health infrastructure, data analytics capabilities, and organizational risk tolerance mature. The transition typically takes three to five years of progressive risk assumption.

How many lives do you need to make a value-based care contract financially viable?

The minimum viable population depends on the contract type and risk level. For shared savings models like MSSP, CMS requires a minimum of 5,000 assigned beneficiaries, though most successful ACOs operate with 15,000 to 30,000 or more to achieve actuarial stability. For commercial shared savings, 3,000 to 5,000 lives is a practical minimum. For capitated arrangements, you generally need at least 10,000 to 15,000 lives to achieve predictable cost variance, and global capitation typically requires 20,000 or more. Below these thresholds, a single high-cost patient event such as a transplant or extended ICU stay can eliminate an entire year of savings, making financial performance more a function of luck than management competence.

What technology do I need to run a value-based care revenue cycle?

Beyond standard billing and practice management systems, VBC revenue cycle operations require a population health management platform for patient registries and care gap tracking, a risk stratification engine that scores patients by clinical and utilization risk, an HCC coding and risk adjustment tool for accurate RAF score capture, attribution management software to track which patients are assigned to your organization, quality measure dashboards aligned to CMS and commercial payer metrics, financial reconciliation tools for modeling benchmark performance throughout the year, and care management workflow software to document interventions and coordinate across providers. The total technology investment typically ranges from $100,000 to $500,000 annually depending on population size and platform sophistication. Leading platforms include Epic Healthy Planet, Arcadia, Innovaccer, and Lightbeam Health Solutions.

How does risk adjustment coding differ from standard medical coding?

Standard medical coding focuses on documenting the reason for a specific encounter to support claim payment. Risk adjustment coding focuses on capturing every chronic condition a patient has, whether or not it is the reason for the visit, because the complete diagnostic profile determines the patient's RAF score used to set spending benchmarks and capitation rates. In VBC, failing to code a patient's diabetes, COPD, or depression during a visit for a sprained ankle means your benchmark is set as if that patient were healthier than they actually are, reducing your savings opportunity. Risk adjustment coding requires annual recapture of all chronic conditions, specificity in diagnosis documentation including type and complications, and compliance with CMS RADV audit standards to avoid upcoding allegations. Organizations with mature risk adjustment programs typically see a 0.1 to 0.3 improvement in average RAF score, translating to 7% to 20% higher benchmarks.

Can you run fee-for-service and value-based care billing simultaneously?

Yes, and most organizations do. Running parallel FFS and VBC revenue cycles is the norm during the transition period, which for most organizations lasts years rather than months. This requires maintaining standard claims submission and denial management for FFS revenue while simultaneously tracking attributed populations, quality measures, risk adjustment, and financial performance against VBC benchmarks. The same patient encounter generates both an FFS claim and VBC quality and utilization data. Organizations need workflows that capture both without duplicating effort, dedicated VBC revenue cycle roles separate from FFS billing staff, integrated financial reporting that separates FFS collections from VBC shared savings or capitation revenue, and a financial model that accounts for the interaction between the two revenue streams, since reducing utilization improves VBC performance but reduces FFS volume.

Editorial Standards

Last reviewed: February 19, 2026

Methodology

• VBC participation and savings data sourced from CMS MSSP and ACO REACH program performance reports
• Financial modeling frameworks based on first-hand experience operating a Direct Contracting Entity with 14,000 attributed Medicare beneficiaries
• Risk adjustment and HCC coding guidance informed by CMS Risk Adjustment Data Validation (RADV) audit standards and HHS-HCC model documentation
• Technology platform analysis based on direct evaluation of population health management vendors serving VBC organizations

Primary Sources

• CMS Shared Savings Program Performance Data
• CMS ACO REACH Model Overview
• CMS HCC Risk Adjustment Model
• HFMA Value-Based Care Resources