Electronic Health Record Software Project Plan For Mount Pleasant Hospital

Overview of the Electronic Health Record Project

1.Problem statement

• Installation of Electronic Health Record at Mount Pleasant Hospital

The hospital’s clinical redesign and the educational unit have appointed a manager at their premises. The hospital management has decided to upgrade the existing electronic health record software. Significant changes in the software has been planned to be made. There will be new software, so there will be software changes as well as hardware changes. A large change management is required.

The new functionality addresses some of the key requirements which include the cardiology as well as respiratory. New initiatives and new approaches have been planned to build within the EMR and this initiative will help to manage the stroke, cardiology and the hip fracture. The latest software build will be able to hold lots of information that are shared over the polyclinic and the community based service programs.

Mount Pleasant Hospital wants to implement the software and they desperately want to make the project successful. They will provide funding for the project. The project funding will be helpful for staff education, clinical pathways and other tasks that need to be carried out urgently.

The newly appointed project manager will have to develop the project plan. The project plan will consist of the important details about the project budget and the information that must be shared. The executive of the hospital will provide some excess data that will be helpful to start the project plan.

The hospital executive wishes to complete the project plan within three weeks. The project plan will contain the deliverables of the project that the project stakeholders will complete. The project deliverables will also include data how the project plan will be improved and how the project can be accomplished successfully.

The new software is being planned to start from May 2018 and the software will take 6 months to complete and it will end up installing at December 2018.

The project scope contains details the educational requirements. The quantification of the education requirements for the latest EMR release is within the scope of the project. The project scope also involves the size as well as cost of the change management process for the implementation. The project scope involves solutions identification as well as the approaches. The stages of the project and the milestones, ongoing IT/IS support requirements are within the scope of the project.

Project goal

The goal of the project is to develop the software that will help to treat the patients and the in turn the hospital can provide excellent services to the patients. The patients can communicate with the hospital and the doctors all the time and will get suitable advice. They will be provided care throughout day and night. The electronic health record system will keep record of every detail of the patients, doctors and the hospital. The management staff of the hospital can be able to track the hospital staff, in this way they can know how the hospital is getting operated, what can be done to improve the process of the hospital. The patients’ health records will be recorded in the database by the software. They can know the patients’ health, patients’ nature and can assess how they can be served better.  Thus the project plan has lots to offer. The goal of the project is to develop the electronic health record software that will enhance the business of the hospital.    

Project Objectives

Project Scope and Requirements Analysis

Specific

The electronic health record will give the hospital immense benefits. They can be able to track the employees. They can be to know how their business is running, how the business process can be improved.  The project managers and the management staff of the hospital are involved with this project. The stakeholders of the project are the project manager, the project sponsor, the coders, the testers and the trainers.

Measurable

The project will take almost 6 months to complete and the budget required to develop the new software will be under considerable budget.

Achievable

The coders are responsible to develop the software according to the needs of the doctors and the patients of the hospital. The tester will evaluate the software multiple times using several scenarios and will ultimately launch the product or the software.

Realistic

Mount Pleasant Hospital wants to enhance their business process. They want a system by which they can keep track of the employees; they want a system by which they can be able to know the behaviours of the patients or the customers

Time limited

The project must be completed within the given timeframe and the project must not be delayed. The project must be completed within stipulated budget. The project stakeholders assigned for the project must complete the project within stipulated deadline and budget.

Based on evidence of “what works”

The management staffs of the hospital decide to implement software by which they can be bale to track employees and can know the demands of the patients or the customers. The electronic health record system will surely improvise their business

Actionable

The project manager is in charge to take up the project activities. It is his responsibility to assign stakeholders based on their skills and expertise, the coders will develop the software, the tester will tests whether the software can bring them real benefits or them. Finally project manager will analyse whether the project is meeting the basic demands of the hospital or not.

Feasible

The business analyst is responsible to carry out the feasibility analysis. The feasibility analysis will help to know the risks associated with the project. The project must be completed after the risk analysis. The risk analysis is conducted and after that the risk mitigation procedures are initiated.

Sustainable

The risk mitigation procedures will help to implement a sustainable environment. The sustainable environment will ensure the project will be accomplished in timely manner with efficiency

Electronic Health Record Software Development and Testing

Able to address political and stakeholder issues

The stakeholder may have issues which must be taken into consideration. The coder may face issues to develop the electronic health record in time. The tester may face issues while testing and may find some bugs. The coder may have to modify the software again

Ethical

The electronic health record must be developed in such a way that the hospital can conduct the business operations smoothly. If the software contains some flaws then it will be disrupted. There may be chances of security breaches and the hospital can lose some of the confidential data

Selected because they have the highest impact

The software adaptation is of highest necessity. The software will provide the hospitals immense benefits

Deliverables

The project consists of analysis of project scope, after that come the analysis of the electronic health record project requirements. Designs of electronic health record system, development of the software testing of the software are the main aspects or the main deliverables of the project that needs to considered.

Work breakdown structure to detail tasks; schedule, sequencing and timeframe

WBS	Task Name	Duration	Start	Finish	Predecessors
0	Electronic Health Record Project Plan	187 days	Mon 28-05-18	Tue 12-02-19
1	Project Scope of the Software	11 days	Mon 28-05-18	Mon 11-06-18
1.1	Detailed Analysis of Project Scope	5 days	Mon 28-05-18	Fri 01-06-18
1.2	Selecting Resources for the Software Project	6 days	Mon 04-06-18	Mon 11-06-18	2
2	Electronic Health Record Project Requirements Analysis	27 days	Tue 12-06-18	Wed 18-07-18
2.1	Conducting Need Analysis of Electronic Health Record	8 days	Tue 12-06-18	Thu 21-06-18	3
2.2	Preview of Electronic Health Record Project Specifications	6 days	Fri 22-06-18	Fri 29-06-18	5
2.3	Draft Preparation for initial Electronic Health Record Specifications	7 days	Mon 02-07-18	Tue 10-07-18	6
2.4	Getting Approvals to Proceed Further	6 days	Wed 11-07-18	Wed 18-07-18	7
3	Electronic Health Record Project Design Specifications	13 days	Thu 19-07-18	Mon 06-08-18
3.1	Review of Electronic Health Record Project Specifications	6 days	Thu 19-07-18	Thu 26-07-18	8
3.2	Getting Approval for further Proceed	7 days	Fri 27-07-18	Mon 06-08-18	10
4	Electronic Health Record Software Development	27 days	Tue 07-08-18	Wed 12-09-18
4.1	Functional Specifications Detailed Review	4 days	Tue 07-08-18	Fri 10-08-18	11
4.2	Development Staff Assigning for the Project	5 days	Mon 13-08-18	Fri 17-08-18	13
4.3	Developing Code for the Software Project	6 days	Mon 20-08-18	Mon 27-08-18	14
4.4	Electronic Health Record Software Testing	4 days	Tue 28-08-18	Fri 31-08-18	15
4.5	Development of Unit Test Plans	8 days	Mon 03-09-18	Wed 12-09-18	16
5	Development of Integration Test Plans	49 days	Thu 13-09-18	Tue 20-11-18
5.1	Conduct Unit Testing	20 days	Thu 13-09-18	Wed 10-10-18
5.1.1	Detailed Testing of Component modules	10 days	Thu 13-09-18	Wed 26-09-18	17
5.1.2	Analysing Anomalies to SAP Project Specifications	10 days	Thu 27-09-18	Wed 10-10-18	20
5.2	Conducting Integration Testing	29 days	Thu 11-10-18	Tue 20-11-18
5.2.1	Assessing Test Module for Electronic Health Record Software Project	14 days	Thu 11-10-18	Tue 30-10-18	21
5.2.2	Integration of Test Module for the Electronic Health Record Software Project	15 days	Wed 31-10-18	Tue 20-11-18	23
6	Carrying Out Training	35 days	Wed 21-11-18	Tue 08-01-19
6.1	Carrying Out Usability Study for Electronic Health Record Project	14 days	Wed 21-11-18	Mon 10-12-18	24
6.2	Finalising Training Materials for the Electronic Health Record Project	14 days	Tue 11-12-18	Fri 28-12-18	26
6.3	Quality Checking Training	7 days	Mon 31-12-18	Tue 08-01-19	27
7	Preparing Documentation for Electronic Health Record Software Project	8 days	Wed 09-01-19	Fri 18-01-19	28
8	Software Deployment	8 days	Mon 21-01-19	Wed 30-01-19	29
9	Post Implementation Review	9 days	Thu 31-01-19	Tue 12-02-19	30

The risks associated with the project has been showcased below-

1. Lack of commitment from the hospital top level management-The project manager and his team must stay careful all the time.
2. Misinterpreting the requirements-The project manager may fail to understand the requirements and may fail to deliver the quality work. The project manager must communicate with the client and they must be clear with all the requirements.

iii. Not managing the change within the project in effective manner- There will be several changes in the project when it is undergoing. The project manager must take the responsibility and must update the project plan along with project report.

1. Real-time performance shortfalls- The project manager and his team will have to accomplish the task activities within stipulated deadline and the budget. They must adhere to the plan strictly.
2. Project resources required

Mount Pleasant Hospital Management staff, project manager, deployment team, tester, coder and the operational analysts are the stakeholder who will carry out the project.

Resource Name

Mount Pleasant Hospital Management Staff

Project Manager

Operations Analyst

Coder

Trainer

Deployment Team

Technical Communicators

Tester

Resource Name	Role
Mount Pleasant Hospital Management Staff	They are the sponsors of the project
Project Manager	Prepares project plan for development of electronic health record software
Operations Analyst	Conducts business operations
Coder	Develops software
Trainer	Provides training to the employees
Deployment Team	They will deploy the software
Technical Communicators	They will prepare the documentation
Tester	They will test the software on the basis of several cases

Task Name	Resource Names	Cost
Electronic Health Record Project Plan		$45,760.00
Project Scope of the Software		$3,320.00
Detailed Analysis of Project Scope	Mount Pleasant Hospital Management Staff	$1,400.00
Selecting Resources for the Software Project	Project Manager	$1,920.00
Electronic Health Record Project Requirements Analysis		$7,800.00
Conducting Need Analysis of Electronic Health Record	Mount Pleasant Hospital Management Staff	$2,240.00
Preview of Electronic Health Record Project Specifications	Mount Pleasant Hospital Management Staff	$1,680.00
Draft Preparation for initial Electronic Health Record Specifications	Mount Pleasant Hospital Management Staff	$1,960.00
Getting Approvals to Proceed Further	Project Manager	$1,920.00
Electronic Health Record Project Design Specifications		$3,120.00
Review of Electronic Health Record Project Specifications	Operations Analyst	$1,440.00
Getting Approval for further Proceed	Operations Analyst	$1,680.00
Electronic Health Record Software Development		$6,480.00
Functional Specifications Detailed Review	Coder	$960.00
Development Staff Assigning for the Project	Coder	$1,200.00
Developing Code for the Software Project	Coder	$1,440.00
Electronic Health Record Software Testing	Coder	$960.00
Development of Unit Test Plans	Coder	$1,920.00
Development of Integration Test Plans		$11,760.00
Conduct Unit Testing		$4,800.00
Detailed Testing of Component modules	Tester	$2,400.00
Analysing Anomalies to SAP Project Specifications	Tester	$2,400.00
Conducting Integration Testing		$6,960.00
Assessing Test Modue for Electronic Health Record Software Project	Tester	$3,360.00
Integration of Test Module for the Electronic Health Record Software Project	Tester	$3,600.00
Carrying Out Training		$7,840.00
Carrying Out Usability Study for Electronic Health Record Project	Trainer	$2,800.00
Finalising Training Materials for the Electronic Health Record Project	Trainer	$2,800.00
Quality Checking Training	Project Manager	$2,240.00
Preparing Documentation for Electronic Health Record Software Project	Technical Communicators	$1,280.00
Software Deployment	Deployment Team	$1,280.00
Post Implementation Review	Project Manager	$2,880.00

 This section contains information about the budget that is required for the project.  Full budget details and an appropriate cashflow should be provided in the appendix to the Project Plan.

Information	Receiver	Timing of Communication	Communication Method	Sender
Preparing Documentation (Draft)	Operations Analyst and Project Manager	As per requirement	Through email	Mount Pleasant Hospital Management Staff
Preparing Documentation (Approval)	Mount Pleasant Hospital Management Staff and Project Team	As per requirement	Through email	Business Analyst, Project Manager
Time, Hours and Detailed Usage	Operational Analyst	On weekly basis	Through email	Project Manager
Creation of Project Status Report	Operational Analyst	On monthly basis	Through email	Business Analyst
Changes in team status	Project Manager	On monthly basis	Meeting, Phone Calls	Project Manager
Detailed approval of project cost	Operational Analyst	As per requirement	Through email	Business Analyst
Internal Work Requests	Operational Analyst	As per requirement	Through email	Mount Pleasant Hospital Management Staff
External Work Requests	Operational Analyst	As per requirement	Through email, fax	Project Manager
Detailed Request for Review	Mount Pleasant Hospital Management Staff	As per requirement	Through email	Project Manager, Mount Pleasant Hospital Management Staff

References

Birkhead, G. S. (2017). Successes and Continued Challenges of Electronic Health Records for Chronic Disease Surveillance.

Blumenthal, S. R., Castro, V. M., Clements, C. C., Rosenfield, H. R., Murphy, S. N., Fava, M., … & Smoller, J. W. (2014). An electronic health records study of long-term weight gain following antidepressant use. JAMA psychiatry, 71(8), 889-896.

Boyle, R., Solberg, L., & Fiore, M. (2014). Use of electronic health records to support smoking cessation. The Cochrane Library.

de Lusignan, S., Mold, F., Sheikh, A., Majeed, A., Wyatt, J. C., Quinn, T., … & Blakey, H. (2014). Patients’ online access to their electronic health records and linked online services: a systematic interpretative review. BMJ open, 4(9), e006021.

Fildes, A., Charlton, J., Rudisill, C., Littlejohns, P., Prevost, A. T., & Gulliford, M. C. (2015). Probability of an obese person attaining normal body weight: cohort study using electronic health records. American Journal of Public Health, 105(9), e54-e59.

Gkoulalas-Divanis, A., Loukides, G., & Sun, J. (2014). Publishing data from electronic health records while preserving privacy: A survey of algorithms. Journal of biomedical informatics, 50, 4-19.

Ho, J. C., Ghosh, J., & Sun, J. (2014, August). Marble: high-throughput phenotyping from electronic health records via sparse nonnegative tensor factorization. In Proceedings of the 20th ACM SIGKDD international conference on Knowledge discovery and data mining (pp. 115-124). ACM.

Mandel, J. C., Kreda, D. A., Mandl, K. D., Kohane, I. S., & Ramoni, R. B. (2016). SMART on FHIR: a standards-based, interoperable apps platform for electronic health records. Journal of the American Medical Informatics Association, 23(5), 899-908.

Miotto, R., Li, L., Kidd, B. A., & Dudley, J. T. (2016). Deep patient: an unsupervised representation to predict the future of patients from the electronic health records. Scientific reports, 6, 26094.

Nguyen, L., Bellucci, E., & Nguyen, L. T. (2014). Electronic health records implementation: an evaluation of information system impact and contingency factors. International journal of medical informatics, 83(11), 779-796.

Olier, I., Springate, D. A., Ashcroft, D. M., Doran, T., Reeves, D., Planner, C., … & Kontopantelis, E. (2016). Modelling conditions and health care processes in electronic health records: an application to severe mental illness with the Clinical Practice Research Datalink. PLoS One, 11(2), e0146715.

Payne, R. A., Abel, G. A., Avery, A. J., Mercer, S. W., & Roland, M. O. (2014). Is polypharmacy always hazardous? A retrospective cohort analysis using linked electronic health records from primary and secondary care. British journal of clinical pharmacology, 77(6), 1073-1082.

Stevenson, J. E., Israelsson, J., Nilsson, G. C., Petersson, G. I., & Bath, P. A. (2016). Recording signs of deterioration in acute patients: the documentation of vital signs within electronic health records in patients who suffered in-hospital cardiac arrest. Health informatics journal, 22(1), 21-33.

van Jaarsveld, C. H., & Gulliford, M. C. (2015). Childhood obesity trends from primary care electronic health records in England between 1994 and 2013: population-based cohort study. Archives of disease in childhood, archdischild-2014.

Weber, G. M., Adams, W. G., Bernstam, E. V., Bickel, J. P., Fox, K. P., Marsolo, K., … & Mandl, K. D. (2017). Biases introduced by filtering electronic health records for patients with “complete data”. Journal of the American Medical Informatics Association, 24(6), 1134-1141.

Xu, H., Aldrich, M. C., Chen, Q., Liu, H., Peterson, N. B., Dai, Q., … & Jiang, M. (2014). Validating drug repurposing signals using electronic health records: a case study of metformin associated with reduced cancer mortality. Journal of the American Medical Informatics Association, 22(1), 179-191.