External downtime assessments have real value, particularly the objectivity that comes from having someone evaluate the program who was not involved in building it. But external assessments also have a cost in both time and money that is not always available when a gap is identified mid-cycle or when the organization wants to run a quick self-check between formal assessments.
An internal downtime preparedness audit that is honestly designed and honestly executed can surface most of the same gaps that an external assessment reveals. The key word in that sentence is honestly. The design of the internal audit has to specifically counteract the organizational instinct to evaluate the program against what it was supposed to do rather than what it actually does. And the execution has to involve the kind of direct observation and verification that produces real findings rather than the kind of documentation review that confirms what the policy says.
This is a practical guide for building and running that kind of audit.
The Three Temptations to Avoid in Internal Audit Design
Before getting into the audit structure, it is worth naming the three design choices that most commonly convert a useful internal audit into a comfortable exercise that produces no actionable findings:
Evaluating documentation rather than operations. A policy review that confirms the downtime policy is current and complete tells you about the policy, not about whether the organization can execute it. The internal audit should evaluate whether the procedures described in the policy are actually being followed, which requires observing operations rather than reading documents.
Selecting the best conditions for the audit. An audit conducted during a high-volume period with experienced permanent staff produces very different findings than one conducted during a low-volume period with a favorable staffing mix. The audit conditions should reflect realistic operational circumstances, not the best-case scenario.
Assigning the audit to the team that owns the program. The IT team that manages the downtime solution is not well-positioned to objectively assess the gaps in the downtime solution they manage. The internal audit should involve at least one evaluator who does not have primary responsibility for the program: a clinical quality officer, a compliance staff member, or a department lead from an area that uses the downtime system without managing it.
The Internal Audit Structure
A useful internal downtime preparedness audit has four sequential components, each of which produces specific findings that feed into the final gap report.
Component 1: Document Review
This is the component most organizations over-invest in and where the useful finding rate is lowest. Keep it brief and specific. The document review should confirm: the downtime policy has been reviewed within the past 12 months, the policy references the specific technology currently in use rather than a legacy system, department-level procedures exist for every priority department and are posted at the point of care rather than only in the policy management system, and there is documented evidence of at least one downtime test or drill within the past 12 months. If any of these four things are not true, flag them as findings and move on. Do not spend more than two hours on the document review.
Component 2: Technology Verification
This component requires physical verification of each downtime workstation rather than assuming that dashboard data tells the complete story. The technology verification checklist for each workstation should confirm:
- The workstation is powered on and displays a login screen without requiring any intervention
- A staff member can log in using current credentials within 60 seconds
- The patient census displayed on the workstation contains patients who were admitted or updated within the past two hours, confirming that the HL7 data feed is current
- The top three forms most commonly used during a downtime event load correctly and reflect current clinical workflows
- The wristband printer connected to the workstation prints a test label correctly
Document the verification result for each workstation individually, including the workstation location, the date of verification, and the result of each check. Any workstation that fails a check is a finding.
Component 3: Staff Knowledge Assessment
This is the component most internal audits skip and the one that produces the most valuable findings. The staff knowledge assessment involves brief, unannounced interviews with a random sample of staff from each clinical and administrative department. The sample should include at least one charge nurse or department lead and at least one staff member who has been in the role for less than six months.
The interview is brief, five minutes maximum, and asks four specific questions:
- If the EHR went offline right now, what would be the first thing you would do?
- Where is the downtime workstation for this department?
- When did you last use the downtime workstation?
- If a new patient arrived while the EHR was offline, how would you register them?
Document the responses verbatim rather than summarizing them. The specific language staff use, including the hesitations, the incorrect answers, and the moments of genuine uncertainty, is the finding. An answer of I think the workstation is over there but I am not sure it works is a more useful finding than noting that training records show the staff member completed downtime orientation.
Component 4: Process Walkthrough
The final component is a timed walkthrough of the downtime activation process conducted by the audit team rather than observed from a distance. The walkthrough simulates a downtime event activation for a single representative department, with the audit team observing every step from the moment they announce a simulated outage to the moment the department’s downtime workflow is fully operational.
Time every step. The time from announcement to first workstation login, from first login to patient census display, from census display to first completed eForm, and from eForm completion to printed wristband are all measurable and meaningful. These times reveal whether the activation protocol works at the speed it needs to work rather than whether it works in theory.
Compiling the Findings into an Actionable Gap Report
The findings from all four components should be compiled into a gap report that has the same structure as a formal external assessment: specific findings, root cause for each finding, and a prioritized remediation recommendation with an assigned owner and a deadline.
Findings should be classified by urgency using a simple three-tier system. Immediate findings are gaps that would create patient safety risk or regulatory citation risk during an actual event if not addressed before the next event. High-priority findings are gaps that would significantly degrade the quality of the downtime response without creating immediate patient safety risk. Improvement-priority findings are gaps that represent the difference between an adequate program and a strong one.
The gap report should be reviewed by the downtime program owner, the IT director, and the CNO or clinical quality officer. The review meeting should produce a commitment to specific remediation steps with named owners and deadlines, not a general agreement to improve things.
Running the Audit on a Regular Cadence
An internal audit run once produces a point-in-time assessment. An internal audit run annually and tracked against the previous year’s findings produces the improvement trend data that demonstrates whether the program is getting better over time. The second and third year of internal audits are more valuable than the first, because they reveal whether the remediation commitments made after the previous audit were actually completed and whether the program has improved as a result.
For organizations that want to supplement the internal audit with periodic external validation, dbtech’s Downtime Audit Assessment is specifically designed to complement an internal program review rather than replace it. To discuss how the internal and external audit approaches work together, contact our team or request a demo.