The Question Nobody Asks During Procurement
When health plans evaluate risk adjustment platforms, the procurement process focuses on capabilities: what the system can do, how it integrates, what it costs, and how quickly it deploys. One question almost never appears in the RFP: what happens to our data if we need to leave?
Data portability isn’t a theoretical concern. Vendor relationships end. Contracts expire without renewal. Companies get acquired and their products change direction. Regulatory shifts make a vendor’s methodology incompatible with the plan’s compliance requirements. When any of these triggers occur, the plan needs to migrate its coding history, evidence trails, member data, and audit documentation to a new environment. If the platform doesn’t support clean data export, the migration becomes a multi-month project that puts active audit response at risk.
What’s at Stake During Migration
Risk adjustment data isn’t just operational records. It’s compliance evidence. Every coding decision, MEAT validation, quality review, and audit response the plan has produced lives in the platform’s database. That data is the plan’s defense in ongoing and future RADV audits. It’s the evidence trail that proves codes were submitted with adequate support. It’s the documentation that rebuttals are built on.
When a plan can’t cleanly export this data, it loses access to its own compliance history. A RADV audit notification that arrives during a platform migration creates an emergency: the evidence needed for audit response may be trapped in a system the plan is actively leaving. Even after migration completes, historical evidence trails may not transfer in formats that the new system can ingest, creating permanent gaps in the plan’s audit defense infrastructure.
CMS doesn’t pause audits for platform migrations. The five-month response window runs regardless of the plan’s technology transition status. Plans that lose access to evidence during migration face the same consequences as plans that never built the evidence in the first place: discrepant findings on codes they can’t defend because the documentation isn’t accessible.
What Portability Requires
Data portability provisions should be standard requirements in every platform contract. The plan should own its data explicitly, including all coding decisions, evidence trails, AI assessments, quality reviews, and audit records. Export formats should be open and documented, not proprietary. The vendor should provide complete data export within 30 days of termination notice, in formats that standard database and analytics tools can ingest.
Evidence trail continuity is the critical test. Can the exported data reproduce, in the new environment, the complete evidence package for any submitted code? If the export includes codes but not the MEAT mapping, or includes the mapping but not the clinical note references, the evidence trail has gaps that compromise audit defense.
The Procurement Addition
Plans selecting a risk adjustment platform should add data portability to their evaluation criteria alongside capabilities, integration, and cost. Ask the vendor to demonstrate a full data export. Verify that evidence trails are complete and in open formats. Include contractual provisions for data ownership, export timelines, and format specifications. The platform you choose today may not be the platform you use in five years. The data it holds is yours regardless, and protecting access to it is a compliance imperative, not just a procurement preference.
