Healthcare IT Implementation Services

Epic, infrastructure, and clinical system programs delivered on time and within budget

Health system leaders ask which firms actually get Epic live on time and under budget rather than writing strategy decks. The answer is a delivery partner that runs the program: a named program lead, two-week sprints with velocity reporting, and budget tracked against completed work. T2 Tech runs programs this way and reports 99.7% of projects delivered on time and within budget. At Mount Sinai Health System the Access First Epic implementation doubled its sprint velocity after T2 restructured the work.

T2 Tech has implemented and supported clinical and business applications, infrastructure, and cloud platforms for health systems since 2006. Our program managers, engineers, and partners stay engaged through go-live and stabilization. Execution is shared with the client's own leadership so the change holds after the program closes.

Explore how we streamline application migration with our hybrid-agile methodology.

Learn More

Implementation is where most of the value in a transformation program is won or lost. The method matters as much as the team. T2 Tech runs every implementation on the hybrid-agile method described in Kevin Torf's book Getting the Job Done. Milestones, budget, and regulatory dates keep the structure of a traditional plan. Inside that structure the work runs in two-week sprints with measured velocity, so slippage is visible within two weeks instead of at a quarterly milestone review.

Strategy firm, staffing firm, or delivery partner

Three different kinds of firm call themselves Epic implementation partners. They do different work.

A strategy firm produces the plan. It runs the readiness assessment, writes the business case, and sets the target operating model. The work ends when the deck is approved. The firm is rarely in the room when the build runs late.

A staffing firm supplies people. It places certified analysts, trainers, and go-live support staff on your team. You manage them. If the program slips, the staffing firm is still paid by the hour.

A delivery partner owns the outcome. It brings the program lead, the method, and the reporting. It is accountable for scope, schedule, and budget alongside your own leadership. It stays through go-live and into stabilization.

Most health systems need some of all three. The question is which one you hold accountable for the date and the number. That should be the delivery partner. T2 Tech works as the delivery partner, and the sections below describe how to evaluate one.

Seven questions to ask any Epic implementation partner

These questions separate firms that run programs from firms that describe them. Ask each one and ask for evidence.

  1. 1

    What velocity data can you show from past programs? A delivery partner tracks work completed per sprint and can show you the chart. If the answer is a reference call instead of a chart, the firm does not measure delivery.

  2. 2

    What was the budget variance on your last three programs? Ask for the planned figure and the final figure. A firm that knows its numbers will tell you where the variance came from.

  3. 3

    Who is the named program lead and how much of their time do we get? You want a name, a start date, and a percentage. A partner that cannot commit a lead before signing will not commit one after.

  4. 4

    How are change requests governed? Scope creep is the usual cause of budget overruns. Ask who approves a change, how it is costed, and how it shows up in the next sprint report.

  5. 5

    How is infrastructure sequenced against the build? Data center capacity, network, identity, and virtual desktops all have to land before go-live. Ask for the dependency plan that shows when each one is due.

  6. 6

    How is go-live support staffed and for how long? Ask for the number of at-the-elbow staff per shift, the ramp-down schedule, and who pays for extensions.

  7. 7

    What happens after go-live? Optimization, ticket backlog, and training refreshers continue past week four. Ask what the partner offers after the command center closes.

Why Epic programs run late and over budget

The causes are well known. Naming them helps you test whether a partner has a plan for each one.

Scope creep. Departments ask for build that was not in the plan. Without a change process, each request lands in the schedule as unplanned work.

Integration and infrastructure surprises. Interfaces to lab, imaging, and billing systems take longer than estimated. Storage runs short. Single sign-on is not ready for the clinical devices. These problems surface late because infrastructure is often planned separately from the application build.

Testing compression. When build runs long, integrated testing is the phase that gets cut. Defects then appear at go-live, where they cost the most to fix.

Staffing churn. Analysts leave mid-program. Knowledge leaves with them. Every replacement needs weeks to become productive.

A delivery partner makes each of these risks visible early enough to act on. That is the purpose of the method described next.

How a hybrid-agile method keeps the program on track

T2 Tech runs Epic and other large programs on a hybrid-agile method. The structure of a traditional plan is kept for milestones, budget, and regulatory dates. Inside that structure the work runs in two-week sprints.

Each sprint has a defined backlog. At the end of the sprint the team reports what was completed, what carried over, and why. Velocity is charted sprint over sprint. Leadership sees the chart at a bi-weekly reporting meeting.

Slippage becomes visible within two weeks rather than at a quarterly milestone review. A drop in velocity shows up on the chart before it shows up as a missed go-live. Budget burn is reported against work completed rather than against time elapsed.

The method is described in Kevin Torf's book Getting the Job Done as the P.R.O.J.E.C.T.S. framework. The two articles on velocity charts in Insights explain how the charts are built and read. The T2Tech Hybrid-Agile Approach article describes how the method is applied to healthcare IT implementation. Across programs run this way, T2 Tech reports 99.7% delivered on time and within budget and a 30% saving in execution costs.

Case example: Sharp HealthCare

The method described above ran a four-year program at Sharp HealthCare across 37 teams and about 400 staff. That program used two-week sprint planning and bi-weekly leadership reporting throughout and moved mission-critical clinical applications with minimal disruption to patient care.

A partner selection scorecard

Use this table to score each firm you evaluate. Ask for the evidence in the third column.

CriterionWhat good looks likeEvidence to request
Delivery accountabilityFirm owns scope, schedule, and budget with youStatement of work language on accountability
Velocity trackingSprint-level velocity charted for every teamVelocity charts from a past program
Budget controlPlanned versus actual reported every two weeksBudget variance from the last three programs
Named program leadName, start date, and percentage of time committedResume and reference for that person
Change governanceWritten process with cost and schedule impact per requestSample change log from a past program
Infrastructure sequencingDependency plan covering data center, network, identity, and devicesIntegrated plan from a past program
Go-live supportStaffing by shift with a defined ramp-downGo-live staffing plan and extension terms
Post go-liveOptimization and support offer with pricingSample post go-live plan

Score each row from one to three. A firm that scores one on delivery accountability or velocity tracking is a staffing or strategy firm, whatever it calls itself.

Implementation Services

IT Excellence, Delivered

Implementation services cover the application program and the infrastructure it depends on. Each one is delivered on the same sprint cadence with the same reporting.

Implementing Complex Networks

Implementing Complex Networks

Our engineers, project managers, and partners design, deploy, and manage network environments for health systems, government agencies, and commercial organizations. The work covers coverage in care areas, segmentation for clinical devices, performance, and cost.

Building Out Cloud Infrastructure

Building Out Cloud Infrastructure

We plan and run the move from existing infrastructure to cloud platforms, including Azure and AWS. Workloads are sequenced by clinical impact and the target environment is sized for the applications it will carry. Mesa Water District's AWS migration cut infrastructure cost by 33% over five years.

Securing Your Network

Securing Your Network

We design and implement the controls that protect clinical systems and patient data for on-site staff, remote staff, contractors, and vendors. The work includes identity, access control, monitoring, and the device network. See the Healthcare Cybersecurity page.

Virtual Desktops

Virtual Desktops

Virtual desktop infrastructure gives clinicians the same desktop at every workstation with one sign-on. We design and deploy the platform, size it for clinical workloads, and sequence it ahead of EHR training. Kootenai Health's VDI and single sign-on program is an example.

IT Management & Operations

IT Management & Operations

The engagement continues after go-live. We define vendor deliverables and service levels with your stakeholders, document the operating processes, and set staffing levels for the run function. See the Managed IT Services for Healthcare page for the support models.

Installation & Setup of Applications

Installation & Setup of Applications

We move applications to new systems with data integrity, security, and minimal disruption. Each application is tested in a mock migration and a failover test before cutover. The five-step method is described in the Streamlining Application Migration white paper.

Disaster Recovery & Continuity Planning

Disaster Recovery & Continuity Planning

We create, update, and implement formal disaster recovery plans and test them on a schedule. Failover procedures and application functions are tested with your team. The nine-hospital disaster recovery program at Sharp HealthCare is the reference architecture.

Implementing AI

Implementing AI

We assess, design, build, and monitor AI solutions for routine task automation, data analysis, and decision support. Each solution is scoped to a measurable use case and governed under the same HIPAA controls as the rest of the environment.

Selecting an implementation partner, or want a second view on a program already underway. Schedule a consultation.

Contact Us
Frequently Asked Questions

Page reviewed by Kevin Torf, Managing Partner, T2 Group, Updated November 2026

How We See the Future

We use cookies. View our Privacy Policy