EHR implementation and optimisation: the project manager's approach

The seven phases, and what the PM does in each

1. 1

   Initiation & governance

   2–3 months

   Agree why you are doing this, who decides, and what success means in clinical and financial terms.

   PM actions

   • Build a business case with measurable outcomes (e.g. days in A/R, medication-error rate, documentation time).
   • Stand up a governance structure: executive steering committee, clinical leadership council, and an operational decision group.
   • Name a physician champion (often the CMIO) and a nursing champion (CNIO) with real decision rights.
   • Sign the vendor contract with the PM at the table — scope, staffing and milestone payments drive your plan.

   Key deliverables: Project charter · Governance charter & RACI · Benefits register · Integrated master schedule (baseline)

   Phase gate: Charter signed by the CEO, CMO and CFO; go-live window agreed.

2. 2

   Planning & current-state assessment

   2–4 months

   Understand today's workflows, systems and data before anyone builds anything.

   PM actions

   • Inventory every application and interface the EHR will replace or connect to (labs, PACS, pharmacy, billing, devices).
   • Map current-state workflows by department with frontline staff, not managers alone.
   • Plan backfill: clinicians pulled into design sessions need their shifts covered — budget for it.
   • Build the RAID log early; dependencies on third-party interface vendors are the usual critical path.

   Key deliverables: Application & interface inventory · Current-state workflow maps · Resource & backfill plan · RAID log

   Phase gate: Scope freeze on in-scope departments, applications and interfaces.

3. 3

   Design & build

   6–10 months

   Configure the system to future-state workflows, using the vendor's model content wherever possible.

   PM actions

   • Run design sessions by workflow (e.g. ED arrival to admission), not by application module.
   • Enforce a 'foundation first' rule: adopt vendor defaults unless there is a safety, regulatory or revenue reason not to.
   • Track build progress weekly by percentage complete per application team, and escalate decisions stuck longer than 10 days.
   • Run a formal change-control board — every customisation adds testing, training and upgrade cost forever.

   Key deliverables: Future-state workflow designs · Decision log · Build tracker · Change requests

   Phase gate: Build complete; open decisions below an agreed threshold.

4. 4

   Testing

   3–4 months

   Prove the system works end to end — clinically, financially and technically.

   PM actions

   • Sequence testing: unit → application → integrated (patient journeys across modules) → interface → performance → revenue cycle.
   • Have clinicians execute integrated test scripts; they catch the workflow gaps analysts miss.
   • Classify defects by patient-safety impact, not just severity; no safety defects open at go-live.
   • Test downtime procedures — what happens when the system is unavailable at 3 a.m.

   Key deliverables: Test strategy & scripts · Defect log with safety triage · Test exit report

   Phase gate: Integrated testing passed; zero open patient-safety defects.

5. 5

   Training & readiness

   2–3 months (overlaps testing)

   Every user is trained, proficient and has hardware on the day they need it.

   PM actions

   • Make training role-based and mandatory — no training, no login. Get HR and medical staff office to enforce it.
   • Train super users (roughly 1 per 10 end users) early; they are your go-live support army.
   • Run go-live readiness assessments at 120, 90, 60 and 30 days with a red/amber/green score per department.
   • Complete technical dress rehearsals: devices, printers, scanners, badge taps and log-ins in every room.

   Key deliverables: Training plan & completion tracker · Super-user roster · Readiness scorecards · Cutover plan

   Phase gate: Training above ~90% per department; go/no-go approved by steering committee.

6. 6

   Cutover & go-live

   1–2 weeks of intensive support

   Switch over safely with the least possible disruption to patient care.

   PM actions

   • Run the cutover as an hour-by-hour plan: data conversion, pre-loading scheduled appointments and active orders, legacy lock-down.
   • Reduce clinic schedules (commonly 25–50%) for the first one to two weeks.
   • Staff a command centre 24/7 with clinical, technical and vendor leads; issues triaged by safety impact.
   • Hold twice-daily huddles and publish issue metrics so leadership sees the trend, not anecdotes.

   Key deliverables: Cutover runbook · Command-centre model · Issue tracker & daily reports

   Phase gate: Stabilisation criteria met: ticket volume falling, no open safety issues, revenue flowing.

7. 7

   Stabilisation & optimisation

   Ongoing — first 6–12 months matter most

   Turn a working system into one that delivers the benefits in the business case.

   PM actions

   • Move from ticket-fixing to a prioritised optimisation backlog within 60–90 days.
   • Measure adoption and burden: documentation time, after-hours 'pajama time', order-set usage, alert overrides.
   • Run department-level 'sprints' pairing analysts with clinicians at the elbow for a week.
   • Report benefits realisation to the steering committee against the original business case.

   Key deliverables: Optimisation backlog · Adoption dashboard · Benefits-realisation report

   Phase gate: Hand-off to operational ownership with a funded optimisation team.

Optimisation: where the benefits actually come from

Go-live makes the system work. Optimisation makes it worth the money. Run it as a prioritised backlog against these levers.

• Clinician burden

  Cut clicks and documentation time with smarter note templates, SmartPhrases, and removing duplicated fields. Measure time-in-notes per clinician before and after.

• Alert fatigue

  Review clinical decision-support alerts with override rates above ~90%; retire or retarget them with pharmacy and safety committees.

• Order sets & pathways

  Standardise evidence-based order sets for high-volume conditions; track usage and outcomes.

• Revenue cycle

  Tune charge capture, coding workflows and claim edits; track denial rates and days in A/R weekly.

• Interoperability

  Improve data exchange with HIEs, payers and affiliated practices; meet information-blocking and TEFCA expectations.

• Upgrades

  Stay current with vendor releases on a set cadence so new features arrive without a big-bang project.

Common pitfalls and how to prevent them

• Treating it as an IT project

  Clinical and operational leaders own decisions; IT builds. Make the governance charter say so.

• Over-customisation

  Default to vendor model content. Every exception needs a written safety, regulatory or revenue reason.

• Losing physician engagement

  Give physicians real decision rights, protected design time and visible wins like personalised templates.

• Interfaces discovered late

  Complete the interface inventory in planning; third-party interface vendors often sit on the critical path.

• Training too early or too thin

  Train within ~6 weeks of go-live, role-based, with proficiency checks.

• No money for optimisation

  Budget 10–15% of programme cost for the first year after go-live before the contract is signed.

Metrics to report to the steering committee

• Training completion and proficiency by department
• Go-live readiness score (red/amber/green) at 120/90/60/30 days
• Open patient-safety defects (target: zero)
• Command-centre ticket volume and time to resolution
• Days in A/R, denial rate and charge lag after go-live
• Clinician documentation time and after-hours EHR use

Frequently asked questions

How long does an EHR implementation take?

For a hospital or health system, 18–30 months from contract to go-live is typical, followed by 6–12 months of stabilisation and optimisation. Ambulatory-only clinics can move faster, often 6–12 months.

What does a project manager do on an EHR implementation?

The PM owns the integrated schedule, governance cadence, RAID log, readiness tracking and cutover plan. They coordinate application teams, vendors, clinical leaders and operations, and make sure decisions are made on time.

Big-bang or phased go-live?

Big-bang (all sites and modules at once) avoids painful temporary interfaces between old and new systems and is common with Epic. Phased roll-outs lower the risk per wave but stretch the programme and need interim workflows. Choose based on how connected your sites are.

What is EHR optimisation?

Optimisation is the continuous work after go-live to reduce clinician burden, improve safety alerts and order sets, tune revenue cycle and deliver the benefits in the business case. It should be a funded, ongoing programme, not a leftover ticket queue.