Direct answer
How should an enterprise transition from fee-for-service to value-based care?
Treat the move as an operating change, not only a contracting change. CMS value-based programs link payment to quality and, in some models, spending across a population. Build the recurring workflows first: annual assessment, post-discharge follow-up, and chronic care management. Each has a defined Medicare fee-for-service pathway and can also support the data, follow-up, and accountability that value-based arrangements use.
The transition stalls in operations, not in strategy
CMS currently operates multiple value-based programs that link payment to quality. Its Innovation Center's 2025 strategy also calls for aligning financial incentives with health outcomes, increasing independent-provider participation in value-based payment, and improving program administration. That policy direction supports continued experimentation, but it does not prescribe one enterprise operating model.
What stalls is the operational layer beneath the contract. An organization signs a value-based agreement, then finds that the work the agreement pays for, the outreach, the follow-up, the documentation, and the closing of care gaps, has no queue, no owner, and no reliable source of truth. The contract changes what gets rewarded. It does not create the workflow that earns the reward.
This is the gap worth planning for. Treating the transition only as a finance project can leave the operating work, data ownership, and human accountability unresolved.
What actually changes when payment moves to value
Under fee-for-service, the unit of payment is the service. Revenue follows completed, documented encounters, and the operating question is throughput.
Value-based arrangements vary. CMS value-based programs generally link payment to quality, while some arrangements also account for spending or shared savings across a defined population. The operating question therefore expands beyond throughput: which people may need an approved action, has it happened, and can the organization show it.
- Work moves between the visits. Outreach, post-discharge follow-up, recurring chronic care contact, and unresolved care gaps become the work that matters.
- The denominator expands. Encounter reporting shows what was done. Population-based reporting also needs to show which people may still need action, using the definitions and attribution rules of the specific arrangement.
- Documentation becomes load-bearing in both models. At population scale, systematic gaps can distort measurement, work queues, and reports.
Annual assessment: the intake that populates everything else
A structured annual assessment can produce a current picture of a patient's risks, conditions, and gaps. CMS defines the Annual Wellness Visit as a covered preventive service with a specified component list, including a health risk assessment and a personalized prevention plan. Under some value-based arrangements, current assessment data may also support care-gap review and population reporting.
The operational difficulty is rarely the visit itself. It is identifying who is eligible and due, reaching them, and preparing the visit so the clinician is not assembling context during the encounter.
This is the job the Swasth AWV Agent is designed for: building AWV work queues from authorized enterprise data, surfacing missing inputs, and organizing outreach for accountable human review. It does not perform the visit, determine coverage, or decide eligibility.
Transitions of care: the window where handoffs fail quietly
The period after a discharge carries concentrated clinical risk and operational urgency. CMS defines transitional care management as a covered coordination service under fee-for-service. Under value-based arrangements, readmissions and unresolved handoffs may affect quality or spending measures, depending on the contract.
The operational difficulty is that discharge information arrives from many sources in inconsistent shape, and the follow-up window is short. Handoffs fail quietly, and the organization often learns which ones failed only when an outcome forces the question.
This is the job the Setu TOC Agent is designed for: assembling post-discharge follow-up queues from authorized discharge data, making unresolved handoffs visible with provenance and timestamps, and routing them to accountable owners. It does not make clinical decisions or create billing evidence.
Chronic care management: the workflow that has to last
CMS defines chronic care management as a covered service for qualifying patients with multiple chronic conditions and describes a comprehensive care plan, ongoing evaluation, and care coordination. Under value-based arrangements, care management is one of several capabilities that may support quality and cost goals; any effect depends on the population, intervention, contract, and enterprise evidence.
The operational difficulty here is durability. Chronic care management requires reliable recurring work, care-plan currency, and documented effort, sustained over years rather than a quarter.
This is the job the Saathi CCM Agent is designed for: creating recurring CCM work queues from authorized care-plan and clinical data, tracking what remains outstanding, and keeping human responsibility explicit. It does not replace the care team or guarantee that any program requirement is met.
Why this sequence is unusually robust
The most common transition mistake is treating value-based readiness as a separate investment that only pays once enough contracts convert. That framing makes the business case fragile and the sequencing political.
None of these three workflows is limited to value-based arrangements. CMS publishes Medicare fee-for-service coverage or payment guidance for AWV, TCM, and CCM, each with program-specific requirements. Building reliable operations around them may therefore support current services while developing capabilities relevant to some value-based contracts.
That sequencing can reduce dependence on a single conversion forecast, but it does not establish reimbursement, savings, or return on investment. Each enterprise still needs its own financial, clinical, legal, and operational evaluation.
Where patient understanding fits
Organizations should account for language and health literacy when providing instructions. Current CMS AWV guidance explicitly tells practitioners to consider communication with people who speak different languages and people with varying health literacy.
Sahara is Synodha's customer-facing product in development for translating medication information into a language a person can understand, while keeping the original label and approved patient information visible and directing people to a clinician or pharmacist for clarification. It is a consumer product, not an enterprise workflow component, and it does not prescribe, diagnose, or change medication recommendations.
A staged sequence
- Establish the data contract before the workflow. Define authorized sources, field definitions, refresh intervals, provenance, patient matching, permissible use, and behavior when a value is missing or conflicting.
- Start with one population and one workflow, choosing where the current gap is most visible and the data is most reliable. Resist starting with the largest opportunity if it also has the weakest data.
- Make human review an explicit step rather than an assumption. Define who approves what, where exceptions queue, and what happens when nobody acts.
- Instrument the operational layer first. Queue completeness, time to follow-up, exception aging, and unresolved handoffs are attributable to the workflow and available immediately.
- Expand by workflow, not by population size. Adding a second workflow on a proven population is a smaller step than holding one workflow constant across a much larger population.
What to measure, and what not to conclude
Measure what the workflow controls: how many people met enterprise-approved candidate criteria, how many were reached, how quickly follow-up happened after discharge, how much recurring chronic care work was completed on schedule, how many exceptions aged past threshold, and how many handoffs went unresolved. Define each metric's denominator, source, time window, and owner before running it.
Do not convert those operational counts into claims about clinical outcomes, reimbursement, billing accuracy, quality scores, or return on investment. Operational throughput and financial or clinical results are separated by case mix, contract terms, coding, and factors no workflow controls. Establishing a link between them requires a study designed for that purpose, run by the enterprise on its own data. Anyone offering that link as a product claim is describing something they have not measured.
Limitations
Swasth, Setu, and Saathi are in development. Synodha does not claim a production integration, EHR endorsement, compliance status, billing accuracy, reimbursement eligibility, autonomous clinical decision-making, or clinical outcome improvement. They are designed to be EHR-agnostic, operating over authorized existing data through APIs, governed feeds, warehouses, or an enterprise integration layer defined with each organization.
They organize operational work and surface missing inputs. They do not make clinical decisions, determine coverage or eligibility, guarantee billing accuracy or reimbursement, establish regulatory compliance, or replace the health system's systems of record or its clinicians.
Program requirements change. Verify current requirements against CMS directly rather than against any vendor summary, including this one.
Primary sources and scope
These sources establish the current program and health IT context used for this checklist. They do not endorse Synodha or establish that any product or deployment is compliant.
- CMS Innovation Center: 2025 strategic direction
- CMS: Value-Based Programs
- CMS: Medicare Shared Savings Program
- CMS: Annual Wellness Visit components and health risk assessment guidance
- CMS: Transitional Care Management Services
- CMS: Chronic Care Management and complex conditions
- ONC: 2025 SAFER Guides for organizational responsibilities and system management
- HHS: HIPAA Minimum Necessary Requirement guidance
Related Synodha resources
Frequently asked questions
What is the difference between fee-for-service and value-based care?
Fee-for-service pays for covered services under applicable payment rules, so revenue follows completed and documented care. CMS value-based programs generally link payment to quality; some arrangements also include spending, shared savings, or population-based accountability. The practical difference is that an enterprise may need to manage both encounter-level work and population-level gaps, using the definitions of each contract.
How should an enterprise transition from fee-for-service to value-based care?
Treat it as an operating change rather than only a contracting change. Define the data contract first, start with one population and one approved workflow, and make human review explicit. AWV, TCM, and CCM each have Medicare fee-for-service guidance and can also develop data, follow-up, and accountability capabilities that may be useful under some value-based arrangements.
Can AWV, transitional care management, and chronic care management be furnished under Medicare fee-for-service?
CMS publishes Medicare fee-for-service coverage or payment guidance for AWV, TCM, and CCM. Each has its own patient, service, documentation, timing, and billing requirements, and payment is not automatic. Coverage, eligibility, documentation, coding, and billing determinations remain the enterprise's responsibility.
Why do value-based care transitions stall?
They can stall when a contract changes what is measured or rewarded without assigning the underlying outreach, follow-up, documentation, and exception work to reliable queues, accountable owners, and authorized data sources.
What operational capabilities does value-based care require?
Reliable identification of who in a population needs something, a way to reach them, follow-up that completes within a defined window, current documentation of conditions and care plans, visible exceptions with accountable owners, and measurement of coverage rather than throughput alone.
Where should a health system start with value-based care operations?
With one population and the single workflow where the current gap is most visible and the underlying data is most reliable. Starting with the largest opportunity is tempting, but a first workflow built on weak data teaches the organization the wrong lesson about whether the approach works.
Can a workflow agent guarantee shared savings or quality scores?
No. Operational workflow and financial or clinical results are separated by case mix, contract terms, coding, and factors no workflow controls. A workflow agent can make the operational work visible and consistent. Establishing that this moved a financial or quality result requires a study the enterprise designs and runs on its own data.