Care Group Case

A little background information about CareGroup Case is that it was formed by the dedicated health care team via three way merger of hospitals providing tailored care services to the patients using broad range of available services. The main motto of merger was the contracting power that needed by the hospitals against the HMOs to providing quality of services while driving down the costs. There were few pros and cons of the merger. The pros of the merger did brought central leadership for the team with the financial stability against poor economy waves. Also the merger brought out cohesive technology system which formed the link for the entire group together. During 1998, John Halamka became the CIO of CareGroup, and meantime the remarkable event of ending of the century (Y2K) brought out worries among the several CIOs of many organizations about the system date problem of coming century into current ongoing system. Halamka decided to build the backup system in attempt to survive through this remarkable event. By the end of the 2003, CareGroup believed that they have most advanced system in healthcare industry.

There was another remarkable event/issue was arisen when one researcher was trying to build software to fix the Y2K problem for CareGroup which could copy information across the network automatically. A researcher had family issue arise and he had not get chance to set up the software to in its original configuration and left CareGroup without testing and implementing the software. The heavy load of information was automatically transferred by itself through the unexamined software to network by very next day which brought havoc to CareGroup. CareGroup appointed to Cisco to make the information transfer load stable and secure over the network. The result of Cisco highlight of issue were not considered the immediate threat to CareGroup.

The lesson to be learned from the case includes the need of frequently evolution