Accreditation preparation in healthcare is a process of making sure the organization can demonstrate what it claims to be doing. For most clinical and operational programs, that means reviewing policies, confirming that procedures match what is written, and ensuring that staff can articulate what they would do in a given scenario. Downtime preparedness is no different, except that it involves a specific technology infrastructure that needs to actually work, not just be described correctly in a policy document.
The gap between having a downtime policy and being prepared to demonstrate downtime readiness to a Joint Commission surveyor or CMS reviewer is where most organizations run into trouble. A downtime audit, conducted proactively before the accreditation visit, is the most effective way to close that gap. It identifies the specific areas where documentation, technology, and staff practice are not aligned before a surveyor does.
What Accreditation Reviewers Actually Evaluate
Understanding what surveyors look for is the starting point for a useful downtime audit. The Joint Commission’s Information Management standards require that healthcare organizations have defined processes for maintaining information access during system downtime, that those processes are tested, and that staff are trained on them. CMS Conditions of Participation require documented emergency preparedness procedures that address technology failures as a category of operational emergency.
State health department surveyors vary in their specific focus areas but generally evaluate whether downtime procedures are documented, realistic, and current. A common surveyor approach is to ask a staff member, often a nurse or registration clerk, what they would do if the EHR went offline right now. The answer that staff member gives reflects the real state of downtime preparedness far more accurately than any policy document.
Specifically, surveyors look for evidence of:
- A written downtime policy that has been reviewed and updated within a defined timeframe, typically within the past year
- Department-level downtime procedures that are posted or otherwise accessible to staff at the point of care
- Documentation of downtime drills or tests, including dates, participating departments, and outcomes
- Training records demonstrating that staff have been oriented to downtime procedures
- A functional technology infrastructure that can actually support the workflows described in the policy
- Evidence of how data collected during downtime is reconciled into the EHR after recovery
What a Downtime Audit Should Cover
A downtime audit conducted in preparation for accreditation should evaluate each of the areas surveyors review, from the perspective of an objective reviewer rather than an insider who may have blind spots about existing gaps. The audit should cover:
- Policy review: Is the downtime policy current, complete, and consistent with how the organization actually operates? Does it address all of the components a surveyor would expect to see, including activation protocols, department-level procedures, data integrity, and recovery steps?
- Technology review: Is the downtime solution functional? Are workstations powered on and syncing? Is the HL7 feed current? Is the forms library up to date and reflective of current workflows?
- Physical accessibility review: Are department-level downtime procedures posted at the point of care, not just in the policy management system? Are downtime workstations located where staff expect them to be? Is the downtime binder or reference packet at each workstation current?
- Staff knowledge review: Can staff in each department articulate what they would do during a downtime event? Do they know where the downtime workstations are? Have they used the system recently enough to be comfortable with it?
- Testing documentation review: Is there documented evidence of downtime drills within the past year? Do the drill records include outcomes and identified gaps? Were gaps addressed and documented?
- Recovery process review: Is there a documented process for reconciling downtime-collected data into the EHR after recovery? Is it understood by both IT and clinical staff? Has it been tested?
How dbtech’s Downtime Audit Assessment Works
dbtech’s complimentary Downtime Audit Assessment evaluates each of these areas in a structured format designed specifically for healthcare organizations preparing for accreditation or seeking to improve their overall downtime readiness. The assessment includes a review of the organization’s current downtime infrastructure, a gap analysis that identifies specific areas of risk, and recommendations for addressing each gap in priority order.
For organizations using dbtech’s technology, the audit also confirms that the HL7 integration is functioning correctly, that the forms library is current, and that workstations are syncing and accessible. For organizations that have not yet implemented a dedicated downtime solution, the audit provides a clear picture of the exposure a surveyor would identify and a roadmap for addressing it.
Turning Audit Findings into Accreditation Readiness
A downtime audit is only useful if the findings are acted on before the accreditation visit. The most effective approach is to treat audit findings as a prioritized work list rather than a comprehensive to-do list that needs to be completed all at once:
- Address immediate compliance risks first: These are the gaps that a surveyor would cite in a finding, such as missing training documentation, procedures that are not posted at the point of care, or a HL7 integration that has stopped feeding current data
- Address operational risks second: These are gaps that may not generate a survey finding but would cause real problems during an actual outage, such as a forms library that reflects outdated workflows or staff who have not practiced with the downtime system in over a year
- Address strategic improvements third: These are enhancements that would strengthen the program beyond the minimum required standard, such as expanding workstation coverage to additional departments or implementing Managed eForms to reduce the ongoing maintenance burden
Documenting the audit findings, the remediation steps taken, and the dates of completion creates an evidence trail that is directly useful during the accreditation visit. If a surveyor asks about downtime preparedness, the organization can present not just the current state of the program but a documented history of how it has been maintained and improved over time.
The Timing of the Audit
For accreditation preparation purposes, a downtime audit should be conducted at least 60 to 90 days before the anticipated survey window. That timeframe provides enough runway to address the findings that require technology configuration changes, policy updates, or staff training without rushing. Audits conducted closer to the survey window may identify gaps that cannot be remediated in time.
For organizations on a continuous accreditation cycle or subject to unannounced surveys, annual downtime audits built into the accreditation preparation calendar provide ongoing assurance that the program remains compliant. To schedule a downtime audit or learn more about how dbtech supports accreditation preparation, contact our team or request a demo.