A Partner for Mary Washington: Glide with Cerner or Chart a New Path with Epic (A) Custom Case Solution & Analysis

Evidence Brief: Mary Washington Healthcare EHR Assessment

Financial Metrics

Metric	Value or Status	Source
Annual Operating Revenue	Approximately 600 million dollars	Case Narrative Section 1
Estimated Epic Implementation Cost	80 million to 100 million dollars over 10 years	Exhibit 4 and Financial Forecasts
Mary Washington Hospital Capacity	451 licensed beds	Case Introduction
Stafford Hospital Capacity	100 licensed beds	Case Introduction
Operating Margin Pressure	Declining due to shift from volume to value based care	Financial Overview Paragraph 4

Operational Facts

System Fragmentation: The inpatient facilities use Cerner while ambulatory clinics use a mix of NextGen and athenahealth.
Market Geography: Located in Fredericksburg, Virginia, positioned between major health systems in Richmond and Washington DC.
Competitive Landscape: Major regional competitors including Inova, UVA, and VCU have already transitioned to the Epic platform.
Physician Network: Includes a mix of employed physicians and independent practitioners who require seamless data access across settings.

Stakeholder Positions

Dr. Travis (SVP and CMO): Advocates for a unified platform to improve clinical quality and physician satisfaction.
Fred Kniffin (CEO): Balances the need for clinical modernization against the significant financial risk of a large capital project.
Community Physicians: Express frustration with current system toggling and favor the Epic platform used by neighboring systems.
CFO and Finance Committee: Concerned about the debt load and the impact on the credit rating of the organization.

Information Gaps

Specific cost projections for the Cerner Millennium upgrade relative to the Epic migration.
Detailed physician turnover data directly attributed to electronic health record dissatisfaction.
Projected revenue loss if independent physicians shift referrals to competitors using Epic.

Strategic Analysis: The Integration Imperative

Core Strategic Question

Should Mary Washington Healthcare undertake a high cost migration to the Epic platform to ensure regional clinical integration, or should it pursue a lower cost upgrade of its incumbent Cerner system at the risk of physician defection and market isolation?

Structural Analysis

Bargaining Power of Suppliers: High. The electronic health record market is a duopoly. Switching costs are extreme, creating significant vendor lock in.
Bargaining Power of Buyers: High. Physicians act as the primary gatekeepers for patient volume. Their preference for a specific tool directly impacts the referral pipeline.
Competitive Rivalry: Intense. Competitors with Epic systems create a network effect that threatens to pull independent physicians away from the Mary Washington network.

Strategic Options

Option 1: Full Migration to Epic. This involves replacing all existing inpatient and outpatient systems with a single Epic instance.
Rationale: Aligns with regional standards and eliminates internal data silos.
Trade-offs: High capital expenditure and significant operational disruption during the multi year rollout.
Resource Requirements: 100 million dollars in capital and a dedicated internal implementation team.

Option 2: Cerner Millennium Consolidation. This involves upgrading the inpatient system and migrating all ambulatory clinics to the Cerner outpatient module.
Rationale: Lower immediate capital outlay and utilizes existing vendor relationships.
Trade-offs: Does not solve the external interoperability gap with Epic using competitors.
Resource Requirements: Moderate capital and training for ambulatory staff.

Option 3: Maintain Status Quo with Middleware. This involves keeping disparate systems and using third party software to bridge data gaps.
Rationale: Preserves capital in an uncertain reimbursement environment.
Trade-offs: Fails to address physician burnout and creates long term technical debt.
Resource Requirements: Low capital but high ongoing maintenance costs.

Preliminary Recommendation

Mary Washington Healthcare must proceed with the Epic migration. The strategic risk of physician alienation and loss of referrals to neighboring Epic enabled systems outweighs the financial burden. Clinical integration is no longer a luxury but a requirement for survival in a value based care environment.

Implementation Roadmap: Transition to a Unified Platform

Critical Path

Phase 1: Financial Finalization (Months 1 to 3). Secure board approval for debt financing and finalize the contract with Epic.
Phase 2: Governance and Design (Months 4 to 8). Establish physician led workgroups to design clinical workflows. This ensures the system supports clinical needs rather than dictating them.
Phase 3: Technical Build and Data Migration (Months 9 to 18). Execute the data transfer from Cerner, NextGen, and athenahealth into the new environment.
Phase 4: Training and Go Live (Months 19 to 24). Conduct mandatory training for all staff followed by a phased hospital and clinic launch.

Key Constraints

Capital Availability: The project consumes a large portion of the debt capacity of the organization, limiting other facility investments.
Physician Bandwidth: The time required for design and training will temporarily reduce clinical productivity and revenue.
IT Talent Acquisition: Finding and retaining staff with Epic certification in a competitive market is a primary hurdle.

Risk Adjusted Implementation Strategy

The plan incorporates a 20 percent buffer in the timeline to account for data migration errors. A specialized physician champion program will be deployed to mitigate resistance. Success depends on the ability to maintain current patient volumes during the transition period.

Executive Review and BLUF

Bottom Line Up Front

Mary Washington Healthcare must migrate to Epic immediately. The current fragmented technology state is a structural weakness that threatens the referral base. While the 100 million dollar cost is high, the cost of inaction is the gradual erosion of the physician network to regional competitors. This is a survival move, not an IT project. Success requires absolute focus on clinical workflow design to prevent burnout. Delaying this decision increases the risk of a forced transition under weaker financial conditions later.

Dangerous Assumption

The analysis assumes that the regional network effect of Epic is irreversible. If national interoperability standards improve significantly in the next three years, the competitive advantage of being on the same platform as neighbors might diminish, leaving the organization with high debt and no unique differentiation.

Unaddressed Risks

Financial Rating Downgrade: The high debt to equity ratio following the Epic purchase may lead to a credit downgrade, increasing the cost of future borrowing for essential facility maintenance.
Operational Productivity Loss: A projected 15 percent drop in patient throughput during the first six months post launch could create a liquidity crisis if not managed with cash reserves.

Unconsidered Alternative

The team did not fully explore a joint venture or shared instance model with a larger neighbor like Inova or UVA. This could reduce the capital requirement and maintenance costs while still providing the connectivity benefits of the Epic platform.