What it is
The EHR Go-Live Readiness Checklist is the final gate a clinical organization walks before switching its electronic health record into production. Go-live is unforgiving because care doesn't stop while you change systems — patients keep arriving, orders keep being placed, and prescriptions keep being written. The checklist covers clinical workflow validation, template and order-set build sign-off, interface testing for labs, eRx and ADT, super-user and training readiness, the downtime contingency plan, the command center, and the explicit go/no-go decision gate.
Its defining strength is that it makes real clinicians walk every core workflow end to end — registration, rooming, charting, orders, results, discharge — rather than trusting that the build looks right. It deliberately pushes beyond primary-care defaults to validate specialty-specific workflows, confirms that charge capture and coding flow correctly with revenue cycle so encounters actually drop charges, and tests the patient portal and self-scheduling from the patient's perspective. These are the workflows that silently break on day one if they were only ever tested by the build team.
The checklist treats interfaces and people as first-class go-live risks. Lab orders and results must round-trip over HL7/FHIR with each lab; ePrescribing and EPCS must be tested including controlled substances and pharmacy routing; and ADT, immunization registry, and HIE interfaces must work end to end. On the human side it verifies role-based training completion, proficiency checks for high-risk roles like providers placing orders, and an adequate super-user ratio for at-the-elbow support — commonly around one super-user per eight to ten users at go-live. The downtime contingency plan and the formal go/no-go criteria turn readiness into a decision rather than a hope.
What it's used for
Organizations use this checklist in the weeks leading up to cutover and on go-live week itself, walking it with clinical, IT, and revenue-cycle leads so that no single function declares readiness on behalf of the others. It is the backbone of the go/no-go meeting.
- ✓ Validating every core clinical workflow end to end with real clinicians — registration, rooming, charting, orders, results, discharge — and not just with the build team.
- ✓ Confirming specialty-specific workflows work, since primary-care defaults rarely cover what a cardiology, behavioral health, or surgical clinic actually does.
- ✓ Signing off on template and order-set builds and confirming charge capture flows so encounters drop charges correctly and revenue cycle stays whole.
- ✓ Round-trip testing every interface — labs and results over HL7/FHIR, eRx and EPCS including controlled substances, ADT, immunization registry, HIE, and device/imaging feeds.
- ✓ Verifying training completion and proficiency checks for high-risk roles, and confirming the super-user ratio is adequate for at-the-elbow support across all shifts.
- ✓ Rehearsing the downtime and contingency plan — printed downtime forms stocked at each unit, read-only/BCA access to the legacy system, and manual order/results/meds processes.
- ✓ Running the formal go/no-go gate so leadership makes an explicit, criteria-based decision instead of drifting into a go-live nobody is ready for.
Who uses it
Go-live readiness is a shared declaration, and the checklist is structured so that clinical, technical, and financial leaders each own and sign off on their portion before the collective go/no-go decision.
Context & good to know
The reason go-live readiness deserves its own rigorous checklist is that an EHR cutover is one of the few IT changes where failure has immediate clinical and financial consequences. If a lab interface isn't filing results to the right encounter, a clinician may not see a critical value. If charge capture isn't flowing, the practice can lose weeks of revenue before anyone notices. And because care can't pause, every gap surfaces under live patient load. The checklist mitigates this by demanding end-to-end validation by the people who will actually do the work, not the people who built the system.
Interfaces and EPCS are where go-lives most often stumble. Lab orders and results must round-trip with each individual lab, because a sample message passing in a test harness is not the same as production-volume traffic filing to the correct chart. ePrescribing of controlled substances (EPCS) adds identity-proofing and two-factor requirements that have to be tested with real pharmacy routing, since a failed controlled-substance prescription at go-live is both a clinical and a regulatory problem. ADT, immunization registry, and HIE feeds round out the set, and device and imaging integrations must be confirmed to post to the correct encounter rather than floating unattached.
The human and contingency layers are what separate a smooth go-live from a chaotic one. Whether the organization is standing up Epic across a hospital or rolling eClinicalWorks across a multi-site ambulatory group, the super-user model — commonly around one per eight to ten users at go-live, trained beyond end-users on troubleshooting and escalation — is what keeps throughput from collapsing in the first days. And because something always goes wrong, the downtime contingency plan must be rehearsed in advance: printed downtime forms stocked at each unit, Business Continuity Access (BCA) read-only access to legacy history, manual processes practiced, and a defined back-loading process for anything captured on paper. The go/no-go criteria then force leadership to confirm all of this explicitly before committing.