CareGroup was established in 1996 from a three-way merger of several hospitals in the eastern Massachusetts area. The merger was driven by the intense financial pressure and competitiveness in the healthcare community. CareGroup was the second largest hospital group in the area, and was a force to be reckoned with in the war of medical costs that included healthcare providers and employers.
On Nov 13, 2002, a researcher executed an application without terminating it, which caused huge data communication traffics and led to a network crash. The network crash could not be fixed internally and the CIO at CareGroup had to call experts from Cisco for help the next day. While Cisco engineers were fixing the problem, CareGroup employees resorted back to paper based forms as a costly and unorganized replacement to their networked computers. The network was restored five days after the crash and post-crash repairing commenced to help recovery and further potential crashes.
The source of the collapse was an "out of spec" network. CareGroup integrated its multiple operating systems into a state-of-the-art IT system. However, not well managed were the incremental changes to the network. This lack of control compromised the paths over which data flowed. That, combined with an experimental application that had been left unmonitored in a production environment, were the underlying causes for the network failure. CareGroup lacked a standardized operational flow to streamline, control, monitor, and document activities of users and researchers. There was little control and IT governance on common users to access or make changes to the network configuration. Right after the outage, several changes were made by various users without synchronization and documenting, which worsened the outage situation.
The following are the proposed options to help solve the aforementioned problem: 1.
CareGroup can implement a...
Please join StudyMode to read the full document