Background on CareGroup
CareGroup, described as “a team of health-care professionals dedicated to providing the best quality care to patients in a personalized manner,” was a product of the 1996 merger of three prominent eastern Massachusetts hospitals. This merger was driven by the competitive environment in the medical community as two of the largest hospitals in Boston, Massachusetts merged and became the holding-company Partners in 1994. In order to compete, CareGroup was formed to have more contracting power against health maintenance organizations. By 2002, many of the CareGroup hospitals had either been spun off or reorganized, however these hospitals still used CareGroup for their IT Support. CareGroup’s IT organization was run by CIO …show more content…
This situation showed the need for verification and second opinions. Practicing this lesson will help avoid similar situations of overlooked bugs, errors, and poor system organization.
3. Keep your working knowledge current:
Keeping up with current technology trends and making sure that working knowledge is up-to-date is something that should always be kept in mind. This is part of the software development life cycle during the maintenance and quality assurance step.
4. Beware of users armed with just enough knowledge to be dangerous:
There should always be steps in place and contingency plans for all possible attacks on a system or network. It is good that this lesson was learned sooner rather than later so that the IT team stays vigilant and supervises experimental software among other threats.
5. Institute rigorous network change control:
Establishing formal and consistent procedures for changes is a good use of a lesson learned. Taking control of their previous faults and spinning it to create greater organizational processes shows how much CareGroup has taken away from the situation.
6. Adapt to …show more content…
I would add an additional lessons learned that was not properly covered; Listen to Experts. Some collapse causing factors could have potentially been avoided had CareGroup implemented the advice of Cisco who came in to study the network months prior. Although modernizing the network would have not eliminated the collapse, the modernization would have taken care of the dated software and hardware (a factor that played a role in the collapse) and may have lessened the severity of the
CareGroup, described as “a team of health-care professionals dedicated to providing the best quality care to patients in a personalized manner,” was a product of the 1996 merger of three prominent eastern Massachusetts hospitals. This merger was driven by the competitive environment in the medical community as two of the largest hospitals in Boston, Massachusetts merged and became the holding-company Partners in 1994. In order to compete, CareGroup was formed to have more contracting power against health maintenance organizations. By 2002, many of the CareGroup hospitals had either been spun off or reorganized, however these hospitals still used CareGroup for their IT Support. CareGroup’s IT organization was run by CIO …show more content…
This situation showed the need for verification and second opinions. Practicing this lesson will help avoid similar situations of overlooked bugs, errors, and poor system organization.
3. Keep your working knowledge current:
Keeping up with current technology trends and making sure that working knowledge is up-to-date is something that should always be kept in mind. This is part of the software development life cycle during the maintenance and quality assurance step.
4. Beware of users armed with just enough knowledge to be dangerous:
There should always be steps in place and contingency plans for all possible attacks on a system or network. It is good that this lesson was learned sooner rather than later so that the IT team stays vigilant and supervises experimental software among other threats.
5. Institute rigorous network change control:
Establishing formal and consistent procedures for changes is a good use of a lesson learned. Taking control of their previous faults and spinning it to create greater organizational processes shows how much CareGroup has taken away from the situation.
6. Adapt to …show more content…
I would add an additional lessons learned that was not properly covered; Listen to Experts. Some collapse causing factors could have potentially been avoided had CareGroup implemented the advice of Cisco who came in to study the network months prior. Although modernizing the network would have not eliminated the collapse, the modernization would have taken care of the dated software and hardware (a factor that played a role in the collapse) and may have lessened the severity of the