mmmmm dd, yyyy
Part A: The Project Meeting
Green Cross Hospital has agreed to be the beta client for the new health care management system product. The new product is considered “feature complete” (Lee, 2013) at 90% and in exchange for a free purchase, PROVISION is allowed to correct defects within the project.
Stakeholders
Hospital IT Manager
He/she manages the IT staff that will assist in the infrastructure and systems development of the systems that will be installed in each of the clinics
He/she will work with purchasing to manage the IT vendors for this project
Hospital Administration Manager
He/she manages the admin staff that will be responsible for the transcription, data input and testing for the systems
He/she will provide the facilities that will house and support the infrastructure for the system
Hospital Head of Nurses / Head of Medical Services / Head of Technical Services He/she manages the personnel that will test and use the system
Hospital Director of FinanceHe/she will explain the financial benefits of the project.
Project TeamThey will be ones who will build the system
Director of Product DevelopmentHe will explain the vision and functionalities of the product.
Potential Conflicts
The administration heads may table objections for the project since there are already manual systems that are working. The Director of Finance will be asked to explain the financial benefits that the hospital can enjoy once the project is implemented
The users (doctors, nurses, admin and technical staff) may find the system difficult to use. The Director of Product Development will describe the user training program.
The users may object to the disruptions in the hospital operations may suffer during the project. The project manager will explain the role of representatives for each of the user groups.
The hospital and satellite clinics are currently using manual systems using varied simple information systems. Questions on the migration of these old semi-automated systems will be raised. The project manager will report on the technical feasibility already conducted.
Part B: Project Charter
Project Inputs
Data input
Patient’s personal information
Patient’s insurance information
Diagnostics prescribed
Diagnostics results
Doctors’ diagnosis (doctors from different fields)
Treatment services delivered in-patient
Medicines used during in-patient treatment
Migration
Existing patient records from various services
Patient billing records
Project Charter
Success Drivers
The general cooperation of all hospital staff is basic but it will be the competency of the group representatives which will matter. The project manager has the prerogative to ask for replacements if he is not satisfied.
The current state of the facilities of the hospital will determine if the installation of the infrastructure will have difficulties.
Measures of Success
For new data, all the users must be able to report that they were able to input and acquire output from the system within 3 seconds per request. The output must be complete, correct and printable. Users must be able to state that the new system is easy to use and has made their “working live” better (Jones, 2013).
For the migrated data, the new system output and reports must match correctly with the old records.
Part C: Project Plan
Deliverables:
Database with old records and test data
Installed system product with custom parameters
Correct screen outputs and printed reports
Activity Plan:
Risks:
Hospital facilities might not be ready for infrastructure
Hospital staff may not be enough to input all records
Hospital might not be ready with its parameters.
References
Lee, J. (2013, October 3). What Does “Beta Software” Really Mean?. makeuseof. Retrieved April 19, 2016 from http://www.makeuseof.com/tag/what-does-beta-software-really-mean/
Hospital Information Systems (HIS). (2013, August 21). Retrieved April 20, 2016 from http://www.emrconsultant.com/emr-education-center/emr-selection-and-implementation/hospital-information-systems-his/
Jones, S. (2013, April 26). How to measure the success of a new IT system. alphr, software. Retrieved April 20, 2016 from http://www.alphr.com/realworld/381451/how-to-measure-the-success-of-a-new-it-system
