The HealthConnect project for Kaiser Permanente is intended to assess the existing information systems technology and make the necessary hardware acquisitions and upgrades to support the implementation of the HealthConnect system, as well as providing training and production support in phases to the various groups that will be using the systemùclerical, administrative, and users. The project will have met its objectives when all of the hardware is in place and running effectively, all employees who will be using the system are trained, and all three user groups are using the system in production. Since the system will store highly sensitive patient information, the project cannot be considered complete, however, without testing to ensure that the data is safe from hackers and that no flaws exist in the system that could corrupt or expose the data. Therefore, the project should not formally be ended until extensive testing has taken place. A system security review should be conducted, and testing specifically aimed at determining whether the system can be breached either internally or externally by unauthorized individuals should be conducted. Specialists in testing information system and network security should be employed to conduct the testing, and upon their report that the system is secure, the project can then be terminated.
In any project, there is a possibility of changes in the project conditions. New requirements can arise, technology can be superseded, and any number of issues can force the project leader to regroup and take a new tack. To prepare for this eventuality, a contingency plan should be developed specifying how such issues will be handled. In the case of the HealthConnect system, the contingency plan should specify that any issue which threatens the security of the data will mandate the delay of the plan to go live until that issue is resolved. Issues that involve technolo
...