The HHVBP model just shifted a huge amount of weight onto OASIS based measures, close to 40 percent of the total performance score. If your coding strategy has not changed to reflect that, this is the year it will start to show up in your payment adjustments.

Here is what actually shifted and what to prioritize because of it.

What changed

HHVBP has always mixed claims based measures, OASIS based measures, and a patient survey component. The 2026 reweighting pushes significantly more of the total score toward the OASIS based measures specifically, things like functional improvement, discharge to community, and acute care hospitalization rates that are calculated straight from OASIS data.

That means the accuracy of your OASIS documentation is no longer just a coding compliance issue. It is now one of the biggest levers you have over your actual HHVBP score, and by extension, your payment adjustment for the year.

Why this matters more than it did last cycle

Under the old weighting, an agency with slightly inconsistent OASIS scoring could still land in a reasonable position if their claims based measures were strong. That cushion is smaller now. If your OASIS data is inconsistent, whether that is functional scoring drift, inconsistent risk adjustment documentation, or gaps in how discharge status gets captured, it now drags down a much larger share of your total score.

The flip side is also true. Agencies with genuinely accurate, well supported OASIS documentation have more room to improve their score than they did before, because the category they are already strong in now counts for more.

Where to focus first

Start with your functional scoring accuracy, particularly the GG items that feed directly into the functional improvement measures. If your scoring at SOC and discharge is not consistent, your measured improvement will not reflect what actually happened with the patient, and that shows up as a worse score even when your clinical care was solid.

Next, look at how consistently your risk adjustment documentation supports the diagnoses being coded. HHVBP measures get risk adjusted based on what is documented, so incomplete or inconsistent documentation can understate how complex your patient population actually is, which makes your outcomes look worse by comparison than they really are.

Finally, take a hard look at discharge documentation specifically. Discharge to community is one of the OASIS based measures getting more weight, and it depends on accurate, complete documentation at the end of the episode, which is often the point in a busy schedule where documentation quality naturally slips.

The coding strategy shift

This reweighting means OASIS accuracy needs to move from being treated as a compliance checkbox to being treated as a performance strategy. That is a real shift for a lot of agencies. It means QA review needs to happen closer to real time instead of catching issues months later, and it means your coding team needs visibility into which specific items are driving your HHVBP score, not just whether a chart passes a general accuracy check.

Agencies that treat this as a data integrity project this year, rather than waiting to see where their score lands, are the ones who will actually benefit from having more weight on a category they can control.

Get ahead of it

If you want a clear read on how ready your OASIS documentation is for the new weighting, Olli offers a low-risk pilot for you and your team for 30 days. See the speed and accuracy of our outputs along with the quality of our customer support first hand.