The core networking team will be performing a code upgrade of the network gear in Tukwila on Sunday, October 20, 2019, starting at 1:30 a.m. (PT).
What does this mean for you?
There is an existing Epic downtime window approved by leadership for that morning (Sunday, Oct. 20). Working with the Epic release and BCA teams, we are developing a plan to leverage this window for work in the Tukwila datacenter affecting the core network fabric. This will result in a downtime of many services in the Tukwila datacenter including systems such as OnBase, Corepoint, and many others. We are anticipating this extended outage taking up to 30 minutes, but we are allocating an hour of time out of an abundance of caution.
Our work will be lined up with this Epic downtime to minimize impact to caregivers.
Following this hard downtime of services in the Tukwila datacenter, there will be further work over an additional two-hour window that will create the potential for brief interruptions in connections to applications in the Tukwila datacenter.
From an Epic perspective, currently the databases supporting our OR/CA, WA/MT, and legacy Swedish Epic systems reside in the Quincy datacenter, along with the front-end Epic applications and Citrix servers providing access to Hyperspace.
The intended plan for Epic users on Oct. 20 is as follows:
1:30 – 2:30 a.m. (PT) – Epic downtime window. Users will be removed from the production Epic systems and instructed to use the Read-Only Epic systems as per standard Epic downtime procedures.
This will align with our hard downtime of the Tukwila datacenter network fabric and largest expected application impact.
2:30 – 4:30 a.m. (PT) – Users will be able to access production Epic systems however they may experience intermittent interruptions when using third-party applications and receiving data over some interfaces. Application teams will be online and available, monitoring these systems and performing any restoration that is needed.
4:30 a.m. (PT) and onward – No further impact is expected.
Questions
Please contact Ryan Moore, director of network operations, with any questions.