Why Switching Risk Adjustment Vendors Takes Twice as Long as Anyone Tells You

Your current risk adjustment vendor isn’t working out. You’ve decided to switch. The new vendor promises a smooth 90-day transition. Your procurement team budgets three months and moves forward.

Nine months later, you’re still not fully transitioned. You’re paying both vendors simultaneously. Your team is exhausted.

The problem isn’t that you picked the wrong new vendor. The problem is that nobody told you what switching actually involves.

The Data Migration Nightmare

New risk adjustment vendors promise seamless data migration. They’ll import your historical data, your coding decisions, your audit trails. It’ll take a few weeks.

That timeline assumes your data is clean, standardized, and well-organized. Your data isn’t. Your old vendor stored information in proprietary formats. Field names don’t match between systems. Historical notes are stored as images, not searchable text.

The new vendor’s migration team discovers these issues three weeks into the transition. They quote you an additional $40,000 for custom data transformation work. The work takes two more months.

Then you discover that some data didn’t migrate correctly. Member risk scores are off. Historical HCC assignments are missing. Audit trails are incomplete.

You spend another month validating the migration and fixing errors. That “few weeks” of data migration has become four months and cost you $60,000 more than quoted.

The Integration Rebuild

Your old vendor integrated with your EHR, claims system, chart retrieval vendor, and CMS submission platform. Those integrations took months to build and have been refined over years.

The new vendor says they have “standard integrations” with all these systems. What they mean is they have integration capabilities, not that your specific integration will work out of the box.

Your EHR is a customized instance with modified workflows. Your claims system is a legacy platform most vendors haven’t seen. Your chart retrieval process involves three different vendors.

The new vendor’s “standard integrations” don’t handle your complexity. They need to build custom connections. Your IT team needs to dedicate resources. Testing reveals bugs.

What you thought would be plug-and-play integration takes five months of IT effort and ongoing troubleshooting.

The Knowledge Transfer Gap

Your old vendor’s team knew your organization. They understood your provider documentation patterns, your coding philosophy, your organizational quirks. That knowledge was built over years.

The new vendor’s team doesn’t have this knowledge. They’re starting from scratch. They code charts based on general best practices, not your specific context.

This creates problems. They query providers for things your old vendor knew to handle differently. They apply coding logic that doesn’t match your risk tolerance.

You need to train the new vendor’s team on your organization. This training isn’t included in the transition plan. It happens reactively as problems surface.

By the time the new vendor’s team really understands your organization, six months have passed. During those six months, your coding quality has been inconsistent.

The Dual Vendor Cost

During transition, you’re paying both vendors. You can’t stop paying your old vendor until you’re confident the new vendor can handle the work.

The transition was supposed to take 90 days. That’s three months of dual vendor costs. But the actual transition takes nine months. That’s six additional months of paying both vendors simultaneously.

If your old vendor costs $150,000 annually and your new vendor costs $200,000 annually, you budgeted $87,500 in dual vendor costs. The actual dual vendor cost is $262,500. You’re $175,000 over budget.

The Productivity Drop

While transitioning between risk adjustment vendors, your team’s productivity drops. Coders are learning new systems. Workflows are disrupted. Time is spent in training sessions and troubleshooting.

I’ve seen coding productivity drop 40% during vendor transitions. If your coding team normally processes 1,000 charts per month and productivity drops 40%, you’re down to 600 charts per month.

That lost productivity has a dollar value. If each chart yields an average of $200 in incremental HCC capture, 400 fewer charts per month for nine months equals $720,000 in lost revenue opportunity.

What Actually Works

Organizations that successfully switch risk adjustment vendors do several things differently.

They budget twice the time the new vendor quotes. If the vendor says 90 days, budget 180 days.

They budget for unexpected costs. Data migration, custom integration work, and extended dual vendor periods all cost money beyond the base contract price. Budget an additional 30-40% for hidden costs.

They run parallel operations for at least 60 days. Both vendors code the same charts during overlap. Compare results. Use the comparison to train the new vendor’s team.

They assign dedicated internal resources to manage the transition. Someone needs to coordinate between vendors, resolve issues, validate data, and manage the process.

They document everything the old vendor did, even things that seem obvious. Your old vendor’s team had tribal knowledge that isn’t written down anywhere.

Switching risk adjustment vendors is expensive, disruptive, and time-consuming. Sometimes it’s necessary. But go in with realistic expectations. The 90-day transition timeline is a fiction. Plan for six to nine months and budget accordingly.

Leave a Comment