What Is the Difference Between Fee-for-Service and Value-Based Care Documentation? 

A clinical note may support a fee-for-service claim but still fall short for a value-based care contract.

Consider a hypertension visit. The provider records the diagnosis, selects an E/M code, and adds the treatment plan. This may support the claim.

Yet the record may still lack the latest blood pressure result, follow-up date, care-gap status, medication review, or referral result.

That is the main difference between the two documentation approaches.

Fee-for-service documentation supports payment for a specific service. Value-based care records serve a wider purpose. They help show whether needed care was completed, how the patient responded, and what happened across several visits.

The difference is not simply the amount of documentation. Each payment model uses the record for a different purpose.

Key Takeaways

• Fee-for-service documentation focuses on the individual encounter, medical necessity, coding, coverage, and services provided.
• Depending on the contract, value-based care documentation may also support quality measures, care coordination, patient outcomes, risk adjustment, and population health reporting.
• Many US physician practices may need to support both approaches because fee-for-service and value-based payment models often operate together.
• Longer notes do not automatically produce better value-based care data. The information must be current, structured where necessary, and easy to report.

What Is Fee-for-Service Documentation?

Fee-for-service documentation is the clinical and administrative information used to support payment for an individual visit, test, treatment, procedure, or other covered service.

Under this model, providers are paid for the services they deliver. The record must show that the service took place and was medically necessary. It must also support the codes and claim details sent to the payer.

For E/M services, CMS says the record should show why the patient was seen, the main findings, the assessment or diagnosis, and the care plan. It should also include the service date and the identity of the person who completed the record.

The record must support the codes, modifiers, units, and other details sent on the claim.

Fee-for-service documentation commonly covers four areas:

• Clinical evidence: Symptoms, findings, diagnoses, medical decision-making, treatment, and follow-up
• Service evidence: Tests, procedures, medications, therapy, or other services delivered
• Billing evidence: Information supporting the codes and units reported on the claim
• Authentication: Service date, provider identity, credentials, and any required signature or electronic authentication.

The main question typically is simple: Does the medical record reflect the service that the provider is seeking to be reimbursed for?

If records are incomplete or inconsistent, claims may be denied, paid at a lower rate, may not be paid at all, or require the submission of more documentation. Patient records should also be complete, accurate, legible, and timely to meet CMS documentation guidance.

What Is Value-Based Care Documentation?

Value-based care documentation is a broad term for the records and data used to support a value-based contract. It builds on the clinical note but looks beyond one visit.

The practice may need to track care gaps, test results, patient goals, referrals, follow-up care, and changes in health. Claims, payer files, and program data often provide information about cost and healthcare use.

Care documentation requirements are not the same across every value-based program. Each contract may use different measures, reporting dates, patient groups, and data sources.

Fee-for-Service vs. Value-Based Care Documentation

Documentation Area	Fee-for-Service Documentation	Value-Based Care Documentation
Primary purpose	Support payment for a service	Track quality, results, care coordination, and contract performance. Payer data may be used to measure cost.
Main unit of review	Individual visit, test, or procedure	Patient group, care episode, or reporting period.
Payment evidence	Medical necessity, service details, coding, and coverage	In hybrid models, the record may support claims, quality measures, patient results, and coordinated care. Payer data may show cost results.
Time focus	Current encounter	Current encounter and care delivered over time
Coding focus	Support for applicable diagnosis codes, procedure codes, modifiers, and units.	Claim coding plus quality, risk, and reporting data.
Care plan	Explains the treatment provided	Tracks goals, interventions, responsibilities, and follow-up
Referrals	Referral order may support the immediate plan	Referral order, scheduling, completion, results, and follow-up may matter
Outcomes	Recorded when relevant to the encounter	Often measured through repeated assessments or defined clinical measures
Preventive care	Supports the preventive service delivered or addressed during the encounter.	Monitored across all eligible or attributed patients
Audit focus	Was the billed service supported?	Were services, diagnoses, quality results, and reported performance supported?
Data sources	Mainly encounter notes and claim records	EHR data, claims, lab results, registries, surveys, payer files, and outside records.

6 Main Documentation Differences

1. One Service vs. Overall Performance

Fee-for-service documentation asks whether the record supports the service reported on the claim.

A reviewer may ask three questions. Was the service medically necessary? Was the code correct? Was the record complete and authenticated as required?

Value-based care adds another layer. The organization may also need proof that the patient was included in the measure, received the required care, or met the defined result.

For example, recording that a depression screening occurred may support the immediate service. A quality measure may also require the screening tool, score, date, follow-up plan, and evidence that the follow-up occurred within a defined period.

2. One Visit vs. Care Over Time

Fee-for-service payment is often tied to separately billed visits, tests, procedures, or other covered services. Value-based care looks across several visits, providers, and care settings. One note rarely tells the full story.

A value-based record may need to connect the initial diagnosis with medication changes, follow-up assessments, referrals, hospital use, outreach, and later outcomes. This allows the care team to see what has been completed, what remains open, and who is responsible for the next action.

3. Completed Services vs. Open Care Gaps

A fee-for-service workflow normally begins when the patient receives a service. Documentation is created to support that service and its claim.

A value-based workflow should also help identify those patients who are not receiving recommended care. This can include patients who have not had their blood pressure checked, cancer screenings, or diabetes screenings on time. It can also include patients requiring a behavioral health review, medication check, and/or post-discharge visit.

The record should show what happened. Was the patient contacted? Was the service completed elsewhere? Did the patient meet a valid exclusion or exception?

A patient decline does not automatically close every care gap. The result depends on the measure rules. Without this information, the organization may perform outreach and coordination work without receiving credit for it.

4. Written Notes vs. Data That Can Be Reported

A detailed paragraph may be clinically useful but difficult for an EHR or quality-reporting system to measure.

Consider the statement: “The patient reports that symptoms have improved since the previous appointment.”

That sentence may help another clinician. However, it may not support a measure that requires the tool name, first score, later score, date, and level of improvement.

Value-based care often relies on set fields, codes, and dated results. Written notes still matter. However, key measure data should not appear only in free text.

CMS publishes detailed measure specifications that explain which patients count, what data is required, and how performance is measured. Practices must follow the specifications that apply to their program or contract.

5. Diagnosis Coding vs. Supported Risk Information

Diagnosis coding matters under both models. Risk-adjusted contracts also need current and accurate condition data. The medical record must support each reported condition.

A diagnosis should not be reported for risk purposes simply because it appears on an old problem list. The current record should show the provider’s assessment of the condition and how it affects monitoring, treatment, or the care plan.

In Medicare Advantage, CMS uses Risk Adjustment Data Validation audits to check whether submitted diagnoses are supported by medical records. Unsupported diagnoses may result in the recovery of overpayments.

The record should show whether the condition is active and how it affects current care. It should also show the provider’s assessment, treatment, monitoring, and next steps.

Risk documentation must remain clinically accurate. Providers should never add unsupported diagnoses or alter clinical decisions only to increase a risk score.

6. Ordered Care vs. Closed-Loop Care

In a traditional encounter workflow, documenting that a referral was ordered may be enough to explain the provider’s immediate plan.

Value-based care may require the practice to track the full referral. Was it sent? Did the patient make an appointment? Was the visit completed? Did the result return to the referring provider?

This is called closing the referral loop.

The same idea applies to laboratory tests, imaging orders, behavioral health referrals, medication changes, hospital follow-ups, and preventive services. Value-based documentation should capture the result of an action, not only the original order.

Does Value-Based Care Replace Fee-for-Service Documentation?

Not always. In many US physician practices, value-based care requirements are added to existing fee-for-service workflows rather than replacing them.

Many value-based arrangements still use fee-for-service claims. Some add shared savings, quality bonuses, or care-management payments. Others use bundled, episode-based, prospective, or capitated payments.

AMA survey results show why hybrid documentation remains important. In 2024, 82.8% of physicians said their practices received some fee-for-service revenue. On average, 67.7% of practice revenue came from FFS. The AMA also noted that many alternative payment models are built on top of fee-for-service payments.

As a result, one patient record may need to support the claim, diagnosis coding, quality measure, care plan, outcome, and audit process at the same time.

The better approach is to avoid separate and disconnected documentation workflows. Even when different payer or reporting systems are required, the underlying clinical information should remain consistent and reusable. 

Practices should create one connected workflow that captures accurate information during care and reuses it for billing, quality reporting, care coordination, and population health management.

A Practical Documentation Example

The items below are examples, not a standard checklist. The exact data needed will depend on the payer, contract, measure, and care setting.

Consider a patient receiving care for type 2 diabetes.

Fee-for-Service Documentation	Additional Value-Based Documentation
Reason for the visit	Most recent HbA1c value and test date
Current symptoms and findings	Blood pressure control status
Diabetes assessment	Kidney health testing status
Medication review	Medication adherence concerns
Medical decision-making	Open or closed care gaps
Treatment plan	Nutrition and self-management goals
Follow-up instructions	Referral completion
Diagnosis and E/M code support	Hospital use, outreach, and follow-up outcomes

The fee-for-service record explains the service delivered during the encounter. The value-based data helps the practice manage the patient over time and measure performance across all eligible patients.

Behavioral Health Documentation Example

The items below are examples. The exact assessment tools and reporting dates depend on the payer, contract, and measure.

A value-based behavioral health contract may require more than the visit note. The practice may record initial and follow-up PHQ-9 or GAD-7 scores. It may also track symptoms, medication use, missed visits, referrals, and progress toward patient goals.

Value-Based Documentation Does Not Mean Writing Longer Notes

One of the most common mistakes is treating value-based care as a request for more text.

A long note may still fail. Key details may be missing, copied from an older visit, saved in the wrong field, or hard to report.

These healthcare documentation best practices focus on accurate, current, and usable records rather than longer notes.

Better value-based documentation is:

• Clinically relevant and current
• Specific to the patient’s condition and care
• Structured when reporting requires structured data
• Connected across providers and care settings
• Easy to retrieve, validate, and audit

Repeated text, unchecked templates, outdated care plans, and copied problem lists can increase note length without improving clinical quality or reporting accuracy.

What Practices Should Record Under Both Models

A hybrid documentation workflow should cover the following areas:

Area	What the Record Should Show
Encounter	The reason for the visit, key findings, assessment, care plan, date, and provider.
Billing	The medical need for the service and support for the codes billed.
Condition care	The current condition, treatment, monitoring, and next steps.
Quality	Required measure values, dates, exclusions, and completed care.
Care coordination	Care team actions, referrals, care transitions, and follow-up.
Outcomes	The starting result, later result, patient response, and progress toward goals.
Risk	Current conditions that are clearly supported by the medical record.
Record history	The source, author, date, and any later updates to the record.

How to Prepare an EHR for Value-Based Care Documentation

1. Review Each Contract Separately

Start with the payer contract and the official measure rules. Identify which patients are included and which measures apply. Then confirm the reporting dates, exclusions, data sources, submission method, and payment terms.

A general value-based care checklist cannot replace contract-specific requirements. Two contracts may use different measurement periods or definitions even when they appear to address the same condition.

2. Map Each Measure to a Workflow

Every measure should be connected to an actual clinical or administrative workflow.

Decide who collects each item and where it is saved. Assign one person to check missing data and follow up on open care needs.

3. Use Structured Fields Where Reporting Requires Them

Important values should be placed in structured fields when the EHR or reporting system needs to calculate them.

Examples include screening scores, laboratory results, blood pressure readings, medication reconciliation status, referral status, care-gap status, and measure exclusions.

Narrative documentation can provide clinical context, but it should not be the only location for information that must be counted or exchanged.

4. Reduce Duplicate Data Entry

Staff should not enter the same detail in the progress note, registry, spreadsheet, and payer portal.

A better workflow captures the detail once, checks it, and reuses it for care, claims, reports, and patient outreach.

Reducing repeated entry also lowers the risk of conflicting information across systems.

5. Build Care-Gap and Follow-Up Workflows

The EHR should help the team identify patients who need action before the performance period closes.

This may include care-gap queues, recall lists, referral tracking, discharge alerts, medication reconciliation tasks, repeat assessment reminders, and care-plan review dates.

The workflow should also show who owns each task and whether it was completed.

6. Validate Data Before Submission

Practices should not wait until the end of the reporting year to identify missing documentation.

Review the data every month or quarter. Compare the EHR with claims, lab results, payer files, registry reports, and sample records.

Look for missing values, duplicate patients, old diagnoses, unsupported exclusions, and incomplete follow-up.

7. Protect Clinical Accuracy

Documentation should always describe the care that was actually delivered.

Staff should not select diagnoses, results, exclusions, or quality values simply because they improve performance. Every reported item should be traceable to valid clinical or administrative evidence.

Common Documentation Mistakes

Practices moving into value-based care commonly experience the following problems:

• Quality information is stored only in free text
• A screening is documented without the score or follow-up plan
• A referral is ordered but never tracked to completion
• Old diagnoses remain active without current assessment
• Problem lists and encounter diagnoses conflict
• Care plans do not identify patient goals or responsibilities
• Outreach occurs but is not recorded
• Measure exclusions lack supporting evidence
• External hospital and laboratory data never reach the patient record
• Different locations use different fields for the same information
• Reports are not tested until the submission deadline
• Copied notes carry outdated findings into later encounters

These issues may not prevent an individual claim from being paid. However, they can reduce quality scores, weaken risk accuracy, increase audit exposure, and prevent the organization from earning value-based incentives.

What Changed for Value-Based Care Documentation in 2026?

Value-based care continues to grow across Medicare, but fee-for-service remains widely used. This means many practices must support both payment models at the same time.

CMS reported 511 Shared Savings Program ACOs for the 2026 performance year. These ACOs serve 12.6 million people with Traditional Medicare.

For performance year 2026, Shared Savings Program ACOs must report five measures in the APP Plus set using electronic CQM, MIPS clinical quality measures, Medicare clinical quality measures, or a combination of these collection types.

ACOs must also administer the CAHPS for MIPS Survey unless they do not meet CMS’s minimum beneficiary sampling requirement. CMS calculates two administrative claims-based measures. Each measure has its own rules for eligible patients, required data, exclusions, and reporting.

Final Takeaway

Fee-for-service documentation shows that a specific service was needed, delivered, and supported for payment. Value-based care documentation looks beyond that service. It also helps track care gaps, quality measures, patient results, risk, referrals, and follow-up across time.

Practices that use both payment models should avoid separate and disconnected documentation processes. The better approach is to capture the right information once, place it in usable fields, and reuse it for care, billing, quality reporting, and follow-up.

The exact requirements will still depend on the payer contract, measure specifications, patient group, and reporting period.

Move From Longer Notes to Better Documentation

Supporting fee-for-service and value-based care should not mean adding more manual work for your providers.

Vozo EHR helps practices bring charting, patient information, scheduling, and follow-up into one connected workflow. Capture important details during care, reduce repeated entry, and maintain clearer records for billing and ongoing patient management.

Frequently Asked Questions

1. What are best practices for Fee-for-Service documentation?

Fee-for-service documentation should be complete, accurate, timely, and tied to the service billed. Record the reason for the visit, relevant findings, diagnosis or assessment, care plan, medical necessity, date, provider identity, and support for applicable codes, modifiers, and units. Well-designed medical documentation templates can help teams capture required details consistently.

2. What are the challenges in Fee-for-Service documentation?

Common challenges include missing medical-necessity details, unsupported codes, unsigned records, copied text, inconsistent problem lists, and documentation completed too late. 

Practices may also struggle when clinicians, coders, and billing teams use different workflows. These gaps can trigger claim denials, payment reductions, additional record requests, or repayment demands.

3. How does Value-Based Care affect physician reimbursement?

Value-based care can link part of physician payment to quality, outcomes, patient experience, cost, or care coordination rather than service volume alone. Some arrangements add bonuses, shared savings, or care-management payments to fee-for-service claims, while others use bundled, prospective, or capitated payments. The exact financial effect depends on the contract.

4. How is Fee-for-Service documentation different from Value-Based Care documentation?

Fee-for-service documentation mainly shows that a specific service was medically necessary, delivered, coded correctly, and supported for payment. Value-based care documentation may also track quality, care gaps, outcomes, risk, and follow-up across time. Clear records also help when insurance auditors review medical necessity.

5. Does Value-Based Care documentation require longer clinical notes?

No. Value-based care does not automatically require longer clinical notes. It requires the right information to be current, consistent, and available for reporting. Structured fields may be needed for scores, care gaps, referrals, and outcomes, while narrative notes provide clinical context. Requirements still depend on the payer, program, and measure.