Back to the Index

The method behind the Index

The Go-Live Confidence Index isn't a marketing quiz. It grades two things that together decide whether complex healthcare change lands: the discipline to drive it, and the hard evidence to prove it's ready. The dimensions are drawn from the failure points I've seen across 2,000+ implementations and a 56-site integration — and aligned to recognized frameworks (ONC's SAFER Guides, the KLAS Arch Collaborative) and to the Gate-to-Go-Live (G0–G5) method.

Two pillars, gated — not averaged

Execution Discipline measures whether you can drive the work; Evidence & Data Readiness measures whether you can prove it's ready. The overall tier is gated by your weaker pillar — a fatal gap can't be averaged away by strength elsewhere (the standard caution against compensatory composite scores).

If you can't measure it, you're not ready

On the evidence pillar, “we don't track that” scores low on purpose. For a CIO or CMIO, the inability to show test results, reconciliation accuracy, downtime rehearsals, or proficiency rates is itself a readiness gap.

Aligned to recognized safety frameworks

Items map to ONC SAFER domains (downtime/contingency, CPOE with decision support, patient identification) and to KLAS Arch Collaborative success factors (shared-ownership governance, user mastery/training, ongoing support) — not just project hygiene.

A self-assessment that earns a real review

Self-assessments are a starting point, not an audit — and the least-ready teams tend to over-rate themselves. The value is where the result points you, and the Executive Readiness Review is where it gets verified.

The grading standard

A 4-level maturity model

Every signal is graded against the same scale, so your result is a defensible read against a standard — not a gut feel.

1
Ad-hoc

Reactive and undefined. Outcomes depend on individual heroics.

2
Emerging

Defined in places, but inconsistent and unproven under pressure.

3
Managed

Consistent, owned, and largely reliable.

4
Optimized

Disciplined and resilient — it holds when go-live pressure hits.

Pillar 1 · Execution Discipline

Can the organization drive this to a controlled landing?

Leadership, governance, change, and process — can the organization drive this to a controlled landing?

01A single accountable ownerG1 · Charter

Diffused ownership is the strongest single predictor of a missed date — decisions stall when no one is answerable.

02Truthful statusG1–G5 · Governance

“On schedule” is worthless if it isn't true; programs fail in the gap between reported status and real status.

03A validated critical pathG1–G2 · Charter & Mapped

A date set before the plan is a wish; only a dependency-mapped critical path tells you whether it's real.

04Change management & clinician adoptionG1–G5 · Adoption

Clinician resistance — especially physicians — is the most evidence-backed barrier to EHR success. Adoption is engineered, not assumed.

05Operational & clinical readinessG2 & G4 · Mapped & Go/No-Go

Most go-lives don't fail on the system — they fail on the workflow, training, and support around it.

06Scope & change controlG1 · Charter

Uncontrolled scope is how a committed date quietly becomes impossible.

07Vendor alignment with teethG2 · Mapped

Without leverage, the vendor's timeline silently becomes yours.

08Live RAID disciplineG0 & G2 · No-Surprises & Mapped

Untracked risk is risk that surfaces at the worst possible time.

09Executive governance & fast escalationG4 · Go/No-Go

Slow escalation is how small issues become date-killers; broad, well-staffed governance predicts adoption.

10Stabilization & support modelG4–G5 · Go-Live & Landed

Go-live is the start, not the finish; super-user and at-the-elbow support during stabilization strongly predicts success.

11Benefits realization & value trackingG1 & G5 · Charter & Landed

Without defined, tracked benefits, “success” can't be proven and value quietly leaks — the question a CFO and an investor ask first.

Pillar 2 · Evidence & Data Readiness

Can you prove it's ready — with data?

The objective, measurable proof of readiness — testing, data, safety, performance. If you can't show it, you're not ready. On this pillar, “we don't measure that” scores low — because the inability to show the data is itself a readiness gap.

01Integrated testing & defectsG3–G4 · Built & Go/No-Go

Measure: end-to-end test status; open critical/high defects.

02Data conversion & reconciliationG2–G3 · Mapped & Built

Measure: migration reconciliation accuracy %, signed off.

03Clinical safety: CPOE, CDS & medication safetyG3–G4 · Built & Go/No-Go

Measure: order sets, decision support & medication-safety validation (per ONC SAFER).

04Patient identification / MPI integrityG2–G4 · Mapped & Go/No-Go

Measure: duplicate-record rate; matching & ID controls.

05Interface & integration readinessG2–G3 · Mapped & Built

Measure: interfaces built / tested / validated in a prod-like env.

06Cutover rehearsalG4 · Go/No-Go

Measure: mock go-lives completed within the planned window.

07Downtime, business continuity & rollbackG4 · Go/No-Go

Measure: tested downtime procedures; rehearsed rollback/back-out plan.

08Performance & infrastructureG3–G4 · Built & Go/No-Go

Measure: load/performance tested at projected peak volumes.

09Schedule & cost performanceG1 & G4 · Charter & Go/No-Go

Measure: milestone hit-rate, SPI/CPI, budget variance.

10Cybersecurity, access & disaster recoveryG2–G4 · Mapped & Go/No-Go

Measure: security testing, identity/access controls, DR validated.

11Payer & parallel revenue-cycle testingG3–G4 · Built & Go/No-Go

Measure: claims / parallel billing tested end-to-end with payers.

The framework underneath

Gate-to-Go-Live

Every site clears six gates to a go-live you can put on a calendar. A practice or system enters with no structure and descends a controlled path to a stabilized handoff.

G0No-Surprises

Discovery — what's real and where the exposure lives: contracts, compliance, data, infrastructure.

G1Charter

Scope, owners, and the committed date — locked, not assumed.

G2Mapped

Data, contracts, infrastructure, and compliance, all accounted for.

G3Built

Configured and migrated against the map — not around it.

G4Go / No-Go

Cutover criteria met and verified. The date is earned, not hoped for.

G5Landed

Live, stabilized, and handed off to the people who run it every day.

See where your initiative stands.

Run the diagnostic — about four minutes, no PHI, and a graded report at the end.