The point where a certified, tested ICT and low-voltage infrastructure stops being a construction deliverable and becomes a live clinical utility. This Article covers the readiness gate that authorizes go-live, the orchestrated cutover sequence that brings systems online, and the formal handover that transfers operational ownership to the health system's IT, biomedical, telecom, and facilities organizations.
Where the sibling Article on cable certification and system testing answers "does each system work and verify correctly?", this Article answers "is the whole infrastructure layer ready to carry patient care, and how do we switch it on and hand it over without harming continuity?" It addresses the ICT/low-voltage backbone specifically — the structured cabling, network core, wireless/DAS, nurse call, RTLS, security, and the integration fabric that ties them together. Device-level and end-user-computing activation, and the broader clinical operational-readiness (OR) and Day-1 activation program, are governed by the activation Domain and cross-link to the readiness gates defined here.
ICT go-live is not a single event. It is a phased ramp that begins weeks before patient occupancy and continues through the first days of live operation. The infrastructure layer must be live, stable, and proven before the clinical activation program can layer applications, devices, workflow validation, and staff training on top of it.
A typical sequencing for a new or expanded acute-care facility:
| Window (relative to first patient) | ICT/low-voltage milestone |
|---|---|
| T-minus 12–16 weeks | Telecom rooms (TR/ER) and data center energized, conditioned, and on permanent power; cabling certified (per sibling Article) |
| T-minus 8–12 weeks | Network core/distribution live; WLAN and DAS coverage validated; systems integration tested |
| T-minus 6–10 weeks | Low-voltage clinical systems (nurse call, RTLS, security, AV/PA) commissioned and integration-verified |
| T-minus 4–6 weeks | ICT infrastructure readiness gate — formal go/no-go for the infrastructure layer |
| T-minus 2–4 weeks | Application and device deployment onto the proven network; integration testing in production |
| T-minus 1–2 weeks | Integrated systems test / "day-in-the-life" simulation; clinical dress rehearsals |
| T-minus 0 to T-plus 14 days | Cutover, go-live, hypercare/command-center support, stabilization |
| T-plus 30–90 days | Punch closure, warranty transition, final operational handover and acceptance |
The infrastructure readiness gate is deliberately set ahead of the clinical-program gates so that any backbone defect surfaces while there is still schedule to recover. Compressing this buffer is the single most common cause of disrupted activations.
Readiness is a decision, made against objective evidence, not a status report. The gate is a structured go/no-go review chaired by the owner's activation/transition lead (or PMO), with the GC/CM, ICT contractor, commissioning agent (Cx), the health system's IT and biomedical leadership, clinical engineering, telecom, security, and infection prevention (for any spaces requiring barrier or air-quality conditions during the work) all represented.
The gate confirms that the infrastructure layer can carry care, that life-safety-adjacent systems are functional, and that an executable cutover and rollback plan exists. Evidence brought to the gate typically includes:
A readiness gate does not require zero open items. It requires that every open item is classified — a "must-resolve-before-go" defect, a "resolve-during-hypercare" item, or a "carry-to-punch" item — and that no must-resolve item is open. This classification discipline is what separates a defensible go decision from optimism.