The Acquisition Risk Nobody Models
Health plan technology vendors get acquired. It happens regularly in healthcare IT. A private equity firm buys a risk adjustment company, merges it with a portfolio company, and restructures the product roadmap to optimize returns. A larger technology company acquires a smaller coding platform to add capabilities to its suite and eventually sunsets the original product. A vendor runs into financial difficulty and sells to a competitor whose platform replaces the one the plan was using.
In every scenario, the plan’s risk adjustment data, including coding decisions, evidence trails, MEAT validations, quality reviews, and audit documentation, sits inside a system whose future is now controlled by an entity the plan didn’t choose, didn’t evaluate, and may not trust.
Most plans don’t model this risk during procurement. They evaluate the vendor’s current capabilities, negotiate the contract, and begin implementation. The possibility that the vendor itself changes ownership, direction, or existence during the contract term rarely appears in the evaluation framework. When it happens, the plan discovers how dependent it is on a system it no longer controls.
What Changes After an Acquisition
Product roadmaps shift. The acquirer has its own strategic priorities that may not align with features the plan depends on. A two-way coding capability that was on the development roadmap may get deprioritized. A RADV response module the plan was counting on may get cut. The AI model may be retrained on the acquirer’s data rather than maintained on the original training set, changing its recommendation patterns.
Support quality changes. The original vendor’s implementation team, the people who understand the plan’s configuration and workflows, often leave after acquisition. Replacement staff work from documentation rather than institutional knowledge. Response times increase. Customizations that the original team maintained break and take longer to fix.
Data access becomes uncertain. During ownership transitions, systems may experience downtime, migration issues, or access disruptions. If the plan is mid-RADV response when the acquisition closes and systems transition, the evidence needed for audit defense may be temporarily or permanently inaccessible.
Pricing changes. Post-acquisition pricing typically increases as the new owner seeks to recover its investment. The plan faces a choice between absorbing the increase or migrating to a new platform, both of which carry costs that weren’t in the original budget.
Contractual Protections That Matter
Plans can’t prevent vendor acquisitions. They can contractually protect themselves. Data ownership clauses should specify that all coding decisions, evidence trails, and audit documentation belong to the plan regardless of ownership changes. Export provisions should guarantee complete data extraction in open formats within 30 days of any change-of-control event. Source code escrow arrangements should ensure the plan can access the system if the vendor ceases to operate.
Transition assistance provisions should require the vendor (or its successor) to provide 12 months of operational support following any change of control, at existing pricing and service levels. This gives the plan time to evaluate the new owner’s direction and, if necessary, migrate without emergency timelines.
Planning for the Unplanned
Vendor acquisition is a when, not an if, in a consolidating healthcare IT market. Plans selecting a risk adjustment platform should evaluate not just the vendor’s current capabilities but the plan’s position if the vendor changes hands. Contractual protections, data portability provisions, and transition assistance clauses convert an uncontrollable event into a manageable one. Plans without these protections are betting their risk adjustment infrastructure, including active audit evidence, on the continuity of a vendor relationship they can’t guarantee.
