How a Regional Health System Moved from Shared EHR to Full Clinical and Financial Control
A full EHR transition—on time, on budget, and with the financial protections to prove it.
For years, a community hospital had operated on a platform it didn't own, couldn't fully configure, and couldn't scale to meet its clinical and financial goals. Patient safety capabilities had a ceiling. The tools available for revenue optimization fell short of the organization's needs, and the hospital lacked autonomous control over its EHR environment.
What made the status quo especially urgent: patient safety incidents had already been documented. Leadership knew a change was necessary, but they lacked a clear path forward and confidence that a transition of this magnitude could be executed without significant disruption to operations, staff, and patients.
Why is this a challenge?
- Transitioning off a shared instance carries complexity that a standard migration doesn't because data ownership, access continuity, and vendor cooperation are all in play simultaneously.
- The organization lacked the internal HIT resources to manage a full platform transition without outside leadership.
- The financial case had to be airtight before any commitment was made, and a rigorous evaluation framework, not a vendor relationship, needed to drive the decision.
- The market was limited: Epic was in contention but eliminated early due to cost, making a disciplined, structured evaluation process even more important to get right.
Acuvance Coker served as the full-lifecycle partner for this transition, entering at the earliest stage of the decision, before any vendor had been selected or any commitment made. That early presence, combined with the team's deep prior experience inside the Meditech platform, gave the client something most implementations don't have: a partner who could see around the corner before problems emerged, not after.
What set this engagement apart:
- Acuvance Coker led the full vendor evaluation, including an RFP process, structured evaluations, acceptance criteria development, demos, and customer site visits for hands-on validation. The resulting selection of Meditech Expanse was grounded in evidence, not familiarity.
- The team negotiated performance-based contract terms with Meditech, securing financial remedies the client could invoke if vendor performance fell short, a structural protection built in before a single line of implementation work began.
- Acuvance Coker's implementation team integrated directly with the client's internal resources, building collaborative workflows from day one and positioning the organization for self-sustainability after go-live.
Approach
- Step 1Assessment and Validation
Acuvance Coker conducted a current-state assessment to validate the challenges leadership had been navigating, confirming limitations in patient safety capabilities, revenue optimization tools, and autonomous EHR control. The assessment surfaced the manual workarounds that had become embedded in daily operations, building a clear case for change before any vendor conversations began. - Step 2Vendor Evaluation and Selection
The team went to market with a defined evaluation framework built around two objectives: moving up-market in capabilities while maintaining cost neutrality and, ideally, achieving measurable cost reduction. The process included a formal RFP, structured evaluations, acceptance criteria, product demos, and customer site visits. Epic was assessed and eliminated due to cost. That disciplined process led to the selection of Meditech Expanse, deployed as a SaaS model to eliminate the client's infrastructure management burden. - Step 3Contract Negotiation
Acuvance Coker negotiated performance-based contract terms with Meditech, securing financial remedies the client could invoke if vendor performance fell short of expectations. Those protections were structural (built into the agreement before implementation began), ensuring the client had recourse regardless of how the project unfolded. - Step 4Implementation and PMO Leadership
Acuvance Coker led the PMO office across every module of the Meditech build with a team of up to five resources from kickoff through go-live. The team brought 3–5 years of hands-on Meditech experience, which meant issues were resolved proactively rather than reactively. Working alongside the client's internal team throughout, Acuvance Coker built the collaborative workflows that set the organization up for self-sustainability after go-live. - Step 5Post-Go-Live Optimization
The engagement didn't end at go-live. Acuvance Coker remained engaged through the post-live stabilization period, supporting ongoing configuration, optimization, and performance improvements, reinforcing the self-sustainability that the client's internal team had built during implementation.
The transition gave this regional health system something it hadn't had before: full clinical and financial control over its own EHR environment. Manual workarounds were eliminated. Patient safety capabilities expanded. And a platform that had been a ceiling became a foundation.
What made this possible wasn't just the technology selection. It was the combination of structured vendor evaluation, disciplined contract negotiation, and an implementation team experienced enough to navigate the gap between what Meditech's SaaS deployment model promises and what it actually requires. Working side-by-side with the client's internal team from the start meant the organization left the engagement not just live on a new platform, but capable of running it independently.
One critical difference: Meditech's SaaS deployment model is positioned as a lower-lift implementation, but significant client-side resources are still required. Acuvance Coker identified this early and ensured the client was prepared, avoiding the resourcing gap that derails many implementations of this type.
For health system leaders considering a similar transition, the lesson is straightforward: the right partner doesn't just execute the implementation; they protect the organization at every stage before it begins.
From Shared Instance to Full Control With Financial Protection Built In
- $90KMonthly HIS cost reduction (transition to Meditech SaaS deployment model vs. prior platform — conservative estimate)
- $770KProjected year-one benefit (conservative pre-migration estimate)
- $2.3MProjected year-three benefit (conservative pre-migration estimate)
- $1.3MProjected total ROI (walk-away strategy analysis)
- Day 0Performance-based terms with financial remedies for vendor non-performance — negotiated before implementation began
- 360Full lifecycle — vendor evaluation through post-go-live optimization; team of up to 5 resources
- 5Workstreams covered, including clinical (acute + ambulatory), administrative, financial, revenue cycle, HR
