Veradigm's Strategic Shift: What Allscripts Customers Should Be Watching

Veradigm has been through a turbulent two years — financial restatements, leadership changes, divestitures, and shifts in product focus. For Allscripts Professional, Touchworks Ambulatory, and Sunrise Hospital customers, the practical question isn't whether Veradigm survives but whether the EHR roadmap they depend on continues to receive the investment it needs. Here are the hedges that protect customers regardless of how Veradigm's strategy evolves.

The three Veradigm products in scope

• Allscripts Professional EHR — small to mid-size ambulatory practices.
• Allscripts TouchWorks — larger ambulatory groups and multi-specialty.
• Allscripts Sunrise — hospital and integrated delivery network.

The three have different roadmap dynamics and different replacement options. Generalizing across them isn't useful.

Hedge 1: Externalize analytics from the EHR

The single most durable hedge. Quality, RCM, and population analytics built inside the Allscripts reporting modules become migration debt if the customer eventually moves to a different EHR. The same analytics built in a vendor-neutral layer migrate forward.

Vizier's Allscripts / Veradigm connector reads from all three product lines, so the analytics layer doesn't care which one you're on or which one you migrate to.

Hedge 2: Maintain data export rights

Confirm that your contract allows you to extract your data in a usable format on demand. If the contract is silent on this, escalate. Customers who need to migrate but lack documented data extraction rights pay 5-10x more in migration costs than those who exercise documented rights.

Hedge 3: Standardize on portable code systems

Some custom Allscripts implementations encode workflows in vendor-proprietary ways. Where possible, standardize on FHIR-compatible representations of clinical data, ICD-10/CPT/SNOMED for codes, and standard claim formats for billing. Portable representations migrate.

Hedge 4: Don't over-invest in deeply customized Allscripts modules

New 2026 investments in deeply custom Allscripts modules — especially analytics modules — should pass a pointed test: does this investment migrate to a non-Veradigm EHR if needed? If the answer is no, scrutinize whether the same value can come from a portable layer instead.

What this isn't

This isn't a recommendation to migrate off Allscripts. Migration is expensive and risky. The analytics-layer hedge above is meaningfully cheaper than migration and protects customers regardless of whether they ever migrate.

The pattern that's emerging

Several mid-size Allscripts customers have adopted the pattern: keep the EHR, add a vendor-neutral analytics layer, and reduce dependence on Allscripts-specific reporting modules. The cost is meaningful but predictable; the optionality it preserves is significant. See the healthcare BI buyer's guide for the layer options.