Contingency Planning
Contingency Planning
Section titled “Contingency Planning”Overview
Section titled “Overview”A contingency plan is required to enable the continuation of critical business processes while operating in other-than-normal conditions. This procedure details how this requirement is met.
1.0 Procedure
Section titled “1.0 Procedure”1.1. Business Functionality
Section titled “1.1. Business Functionality”In a situation where the primary datacenter or systems within the primary datacenter are unavailable, the following business functionality will be available within the contingency site:
a) Patient Remedi Portal is available and functional
b) Credit Balance Portal is available and functional
1.2. DR Environment
Section titled “1.2. DR Environment”The contingency site will exist in the Microsoft Azure infrastructure.
Contingency Systems:
a) Domain Controller: FRHCDR01SDCG01
b) Database Server (PR): FRHCDR01SSQL02
c) Database Server (CB): FRHCDR01SSQL01
d) Web Server (PR): FRHCDR01SWEB01
e) Web Server (CB): FRHCDR01SWEB05
f) Application Server (PR): FRHCDR01SAPP01, FRHCDR01SAPP03, FRHCDR01SAPP04
g) Application Server (CB): FRHCDR01SAPP02
h) SFTP Server: FRHCDR01SFTP01
1.3. Code/Data Maintenance
Section titled “1.3. Code/Data Maintenance”Web site and application code and database schema updates will be made to the respective DR servers within a week of updating the primary servers.
1.4. Bringing DR Environment On-Line
Section titled “1.4. Bringing DR Environment On-Line”Steps to implement DR:
-
Create and turn on the virtual servers in the following sequence:
a. Domain Controller: FRHCDR01SDCG01
b. Database Servers: FRHCDR01SSQL01 and FRHCDR01SSQL02
c. Web Servers: FRHCDR01SWEB01 and FRHCDR01SWEB05
d. Application Servers: FRHCDR01SAPP01, FRHCDR01SAPP02, FRHCDR01SAPP03, and FRHCDR01SAPP04
e. SFTP Server: FRHCDR01SFTP01
-
Restore OneProduction Databases (for both CB and PR) with full backup
-
Test Patient Remedi Portal: https://DR-one.frhc.com
-
Test Credit Balance Portal: https://DR-cb.frhc.com
2.0. Revision Tracking
Section titled “2.0. Revision Tracking”| Rev | Description | Date | Approved |
|---|---|---|---|
| - | Original Document | September 2018 | M Machin |
| 1.0 | Updated and approved for 2019 | October 2019 | M Machin |
| 2.0 | Added SFTP to server mix | 2020 | M Machin |
| 3.0 | Updated and approved for 2022 | October 2022 | WSI |
| 4.0 | addition of APP03 and APP04 for app servers | January 2023 | WSI |
| 5.0 | Updated and approved for 2024 | July 2024 | WSI |
| 6.0 | Updated and approved for 2025 | August 2025 | M Machin |
