I know of other local hospitals that don't have monthly Epic downtimes like we do, only during major Epic upgrades. It seems to me that it is a lot of work to go down for at least an hour each time and we have to enter everything when we are back online. Why do we have a system downtime every month for our Epic system? Can these downtimes be reconsidered for patient safety?
Thank you for raising your concerns, which I’ve shared with our information technologies leadership. Rick McCarthy, our chief information officer, reports our Epic downtimes, normally under 45 minutes, are among the shortest as reported by Epic when compared to other Epic organizations. Additionally, a significant side benefit is exercising our downtime process and procedures, which is vital preparedness for when we face an unplanned outage. Given this, there is no plan to move away from our monthly downtime activities at this time.
It’s also important to understand, the technical environment, including what other systems are linked to Epic, can vary greatly from organization to organization. As Rick explains, our monthly downtime allows us the critical offline time to apply updates, changes, patches and other needed adjustments not only to Epic but other critical systems to ensure we have high-performing solutions. This important work enables us to deliver a highly stable architecture working at top performance levels while ensuring minimal unplanned outages/issues for a staff as well as our patients.
Thank you for the question, and the opportunity to provide this perspective and offer a glimpse of all that goes on in the background to ensure we are equipped with reliably performing technology and tools to do our work efficiently and safely.