Downtime preparedness in most healthcare organizations lives on the IT team’s agenda. There are reasonable historical explanations for this. The EHR is a technology system. When it fails, IT fixes it. The downtime solution is also a technology system. IT implements and maintains it. The policy that governs downtime procedures is written by IT and reviewed by compliance. The budget for the downtime solution is in the IT budget.
This ownership structure produces a specific and predictable failure pattern. The technology works. The policy exists. And when a downtime event actually occurs, the clinical team, which was never really in the room during the planning, manages the response in ways that reveal exactly how much the program was designed for IT’s needs rather than theirs. Forms that do not match clinical workflows. Activation protocols that assume the charge nurse knows something they were never told. Post-event reconciliation processes that make sense from a data management perspective but create enormous work for nursing staff who are already managing a full patient load.
The solution is genuine co-ownership, where clinical leadership is not a stakeholder that IT consults but a co-owner that shapes the program from the beginning and maintains accountability for the clinical dimensions of preparedness over time.
Why Clinical Co-Ownership Produces Better Outcomes
The case for clinical co-ownership is not primarily about organizational politics. It is about program quality. Clinical leaders bring three things to downtime preparedness that IT teams, however skilled and well-intentioned, cannot provide on their own.
They know what clinical staff actually need during an outage. The workflows that break down most severely during a downtime event, the information access gaps that create the highest patient safety risk, and the documentation requirements that cannot be deferred until the EHR is restored are all dimensions of the problem that clinical leaders understand from direct experience. A downtime forms library designed by IT without clinical input will be missing forms that clinical staff need and will include forms configured in ways that make sense from a data structure perspective but create friction for the nurses completing them under pressure.
They have the organizational credibility to make the training culture stick. Staff compliance with downtime training requirements is significantly higher when the CNO or the nursing director owns the training mandate than when it is owned by IT. Clinical staff take downtime preparedness seriously as a clinical competency when clinical leadership treats it as one. The same training, delivered as an IT requirement, is often treated as a compliance checkbox.
They provide the governance accountability that keeps the program funded and prioritized over time. A downtime program that is owned exclusively by IT will lose resources whenever the IT budget is under pressure, because IT has other competing priorities and downtime preparedness does not have a clinical advocate making the case for sustained investment. A downtime program that the CNO co-owns is more likely to be defended in budget discussions because it has an executive sponsor who understands the clinical consequences of inadequate preparedness and can articulate them in terms that resonate with the CFO and the board.
How to Bring Clinical Leadership Into Genuine Co-Ownership
Genuine co-ownership is different from consultation. Consultation means IT presents the downtime plan to clinical leaders, receives their feedback, and incorporates some of it. Co-ownership means clinical leaders are involved in the design of the program from the beginning, own specific program components, and are accountable for the clinical dimensions of preparedness in the same way that IT is accountable for the technical dimensions.
The transition from consultation to co-ownership typically requires a specific conversation that reframes the downtime preparedness program as a clinical quality issue rather than an IT issue. The framing described in our post on the case for treating downtime preparedness as a clinical quality initiative rather than an IT function provides the conceptual foundation for this conversation. The evidence that downtime events increase adverse event rates, affect medication safety, and create patient experience problems that are clinical in nature makes it difficult for clinical leaders to maintain that downtime preparedness is someone else’s problem.
The practical mechanism for establishing co-ownership once the conceptual case is made is a governance structure that formally assigns clinical ownership to specific program components. The structure that works most consistently assigns:
Technical infrastructure ownership to IT, covering the HL7 integration, workstation deployment and maintenance, and vendor relationship management.
Clinical preparedness ownership to the CNO or a designated clinical leader, covering training requirements for clinical staff, drill participation standards, department-level procedure currency, and the clinical dimensions of the post-event after-action process.
Forms library clinical governance to a clinical informatics or health information management leader, covering the review and approval of form content, the clinical validation of new forms before deployment, and the ongoing assessment of whether the eForms library reflects current clinical workflows.
Program governance joint ownership between the CIO and CNO, with shared accountability for the annual program review, the budget request, and the reporting to executive leadership and the board.
Making the Relationship Work in Practice
Governance structure on paper does not produce genuine co-ownership in practice unless the relationship between the IT team and the clinical leaders who co-own the program is actively maintained. The practical elements that make the co-ownership relationship function include:
Regular joint meetings between the IT downtime program owner and the clinical co-owner that cover the current state of the program, upcoming events that require coordination, and any issues that need input from both perspectives. Monthly or quarterly depending on the program’s current state and the volume of active initiatives.
Joint participation in downtime drills and planned maintenance window reviews, where both IT and clinical leadership observe the event and conduct the debrief together. The debrief that includes both technical and clinical perspectives produces findings that neither would identify alone.
Mutual visibility into each other’s program metrics. IT should see the clinical metrics, including training completion rates, drill performance by department, and staff knowledge assessment results. Clinical leadership should see the technical metrics, including workstation sync status, HL7 integration health, and forms library currency. Shared visibility produces shared accountability.
A defined escalation path that goes to the joint governance structure when issues require decisions above the operational level. Clinical and technical issues that cannot be resolved at the program level should have a clear path to the CIO-CNO governance structure rather than defaulting to whichever leader has more organizational authority at the moment.
To discuss how dbtech supports the development of IT-clinical co-ownership models for downtime preparedness programs, contact our team or request a demo.