FAQ

• Epic delivers value for everyone involved. As a health system that spans multiple geographies, patient demographics, and care teams, this single EHR will deliver:
  • Increased clinician satisfaction with an automation-driven process and seamless collaboration between care teams 
  • Enhanced patient safety with standardized protocols, workflows and tools 
    • Example: A single EHR will allow for continuous care coordination across multiple locations for patients served, standardizing care delivery and increasing visibility into patient diagnoses, treatment and follow-up. 
  • Improved care coordination through enterprise-wide integrated communications and patient record availability 
    • Example: Care teams will have access to all patient records for all visits across care facilities, streamlining care delivery and increasing visibility into the patient-care life cycle. 
  • Streamlined technical landscape by eliminating multiple data centers, more than 130 applications, and more than 260 system integrations 
    • Example: Standard Epic workflows and applications will eliminate the need for disparate third-party applications, allowing the care team to work from a single, core platform without excess.
  • One core platform for patients and clinicians to access information, scheduling, statements, and clinical resources 
    • Example: Patients can coordinate visits across all in-scope entities in one single platform, while the care team can coordinate follow-ups, appointments, and patient resources within a single system. 
  • More efficient research operations by using a seamlessly integrated solution with our existing clinical trial management system (OnCore) for optimized trial management and billing 
    • Example: Epic provides a robust billing protocol review process that will provide compliance while maximizing our research staff’s time.
  • Increased research opportunities via Epic Cosmos, including more than 260 million de-identified patient records to support research growth and clinical trials 
    • Example: Cosmos users can use data from many institutions to gain a better understanding of treatment outcomes across a broader population. 

• We are committed to aligning with over 90% of Epic’s Foundation System, meaning we will implement the standard Epic EHR and escalate decisions that require deviations from the Foundation System.  
  • See additional FAQs in the Epic Foundation System section. 

• Each entity will have representation in how Epic is built and configured, despite staggered launch (“go-live”) dates.
  • See additional FAQs in the Build Wave section. 

The entities in-scope for Epic include: 

From April 2025 to October 2025, Advisory Groups and Operational Workgroups will be making decisions that support the build and configuration of Epic’s Foundation System to meet the needs of each in-scope entity.

The Epic Journey phases include:

High-level training timelines are as follows and should be communicated to appropriate audiences as relevant:

• Epic’s Foundation System is the standard version upon which each in-scope entity will build the Epic EHR. It includes pre-defined settings, sample reports, and starter sets for clinical and specialty areas. This will be tailored to meet specific organizational needs and workflows.

• Our leaders have made the decision to align with more than 90% of Epic’s Foundation System, based on Epic-recommended best practices.

• The benefit is that Epic has been built to work for community and university-based medical centers similar to ours in size and function. 

• We are confident that the Foundation System will meet our needs but also understand certain workflows will need to be configured and personalized for individual, department, and specialty preferences.
  • See additional FAQs in the Build Wave section.

• For more information on Epic Foundation System principles and sources, click here.

Representatives from across all in-scope entities were nominated and appointed to Advisory Groups responsible for making decisions about the configuration (e.g., build) of the Epic EHR to meet the needs of our employees and patients. 

There are six different Advisory Group Workstreams guiding the build of Epic: 

• Analytics 
• Ambulatory 
• Physician and APP 
• Inpatient 
• Revenue Cycle 
• Technical 

There are 55 different Operational Workgroups, with representatives from across all in-scope entities, who are making key decisions about the build of Epic and validating the Foundation System, content, and workflows. Each Workgroup reports to an Advisory Group.

Operational Workgroup members are an extension of their specialty, role, and location. These members will solicit feedback from end-users on key decisions that need to be made outside of Epic’s Foundation System.

As necessary, Subject Matter Expert (SME) Groups will be activated to provide additional insight on the build of Epic. If you are selected as an SME, you will receive notification about your nomination, expectations of the role, a timeline for involvement, and desired outcomes.

Approximately 75% of the decisions being made about Epic will be discussed during Operational Workgroup meetings. These decisions impact the configuration of Epic’s Foundation System.

Approximately 15% of the decisions being made about Epic are brought to Advisory Groups who provide guidance to the executive teams and workgroups with expertise in their respective areas. These decisions tend to have an impact on budget and scope of the Epic Journey. 

The remaining ~10% of decisions about Epic are made at the Executive Sponsor and Executive Steering Committee levels and pertain to overall direction, timing, and strategy of the Epic EHR Implementation.