Business Case Summary, Part 3
<Project Name> Version: <1.0> <Draft>
Healthcare Community Outreach
HealthCare Community outreach
project Management plan
Version 1.5
12/17/2018
<Project Name> Project Management Plan Version: <1.0> <Draft>
[Insert appropriate disclaimer(s)]
Revision Date: Error! Unknown document property name. Page 2 of 21
CDC_UP_Project_Management_Plan_Template_v1.1.doc
VERSION HISTORY
UP Template Version: 12/17/18
TABLE OF CONTENTS
1.1 Purpose of Project Management Plan 4
2 Executive Summary of Project Charter 4
3.1 Work Breakdown Structure 4
3.3 Change Control Management 4
12 Compliance Related Planning 6
Appendix A: Project Management Plan Approval 7
APPENDIX D: SUMMARY OF SPENDING 10
Introduction
Purpose of Project Management Plan
The purpose of the Project Management Plan (PMP) for the Community Healthcare Outreach is reaching out to the homeless and deprived, low income individuals. With the atmosphere and location for poverty-stricken people, it is almost impracticable and unbearable for them to uphold a detailed and straightforwardly available health care reports. Healthcare Community Outreach believes that personal health record (PHR) technology could help citizens have admission to their health record. A contributor has contributed ten thousand dollars for the project. Our panel has evaluated a diversity of options for PHR, identifying the achievement and management expenses and the controlled accessible financial plan. We have selected the greatest profitable technique towards supplying PHRs that is industrialized by the Veterans Affairs (VA) Health System. The anticipated audience of the Community Healthcare Outreach Project Management Plan is all project stakeholders as well as the project sponsor, senior leadership and the project team.
Executive Summary of Project Charter
This project is design to maximize the budget assigned and available resources already in place. We looking to deploy this project within business hours to minimize the use of overtime. With the exception of property management, we will not use any outside resources. Please see scope management and work break down
Assumptions/Constraints
The Personal Health Record is the electronic, universally available resource for the provision of health information which is maintained by the patients. The development of this project; web-based personal record, is done through the VA health systems. This project includes a list of assumptions for the purposes of documentation of the estimates which have been made, the schedule to the system, and at the same time the financial plan to the project. The system will also be using a single patient medical record across the enterprise and be responsible for the overseeing of any ongoing health records used for the related components. At the same time, will be implemented through the development of site-specific policies and procedures. The provider team for this project will not be able to have any capability of declining the implementation process for the project. On the other hand, the specifically assigned tasks for the system users will be provided through the members for the team in a timely manner having a lead time which is enough (Lafky & Horan, 2011). The implementation for the project by the management team should be completed through the tasks that relate with the timeline which has been specified timeline. The providers will also be able to have access to the system through a certain gateway from the location which has an internet access. The training process for the project is a requirement and the users should be given enough time for the training needs. Also, the emergency room personnel should be able to have access to the records of the clients of the system where there is a need. The system allows the view of information which is stored on the database when a patient does not have permission to access the system.
Some of the constraints or rather the problems which have been experienced through the management for this project range from the privacy and security issues, lack of its use and adoption problems. The process of data accuracy has been noted to arise. When the users of the system; who are the patients, enter their own records in health records for the purposes of updates, have raised a lot of concerns. The degree at which users should be able to have control access over the system is questioned to whether it should be a read-only access or whether it should be able to give full access to the system (Kaelber & Pan, 2008). Another most noticeable constraint for the implementation of PHRs is the issue of security and confidentiality breaches. In the system, not all parties which are involved are legal and follow the obligations with respect to the process of privacy for the system users. For example, a physician may be distressed on the reliability of the information which is held on the system, and this can lead to the question of the control system for the project. Through different literature analysis and the actual project implementation process, it can be said that a PHR threaten the control, the autonomy process, and the authority for the providers. Another major problem for this project is its adoption by the physicians. The system come through with the possibility of increasing the workload for the physicians. Through an evaluation process to the physicians, it has been concluded that the project is associated with an increased workload which one of the constraints that should be most addressed in this project. Lastly, it is the extent to which the system can be fully adopted and at the same time being held accountable for its content and the treatments which are performed and based on the information provided
Scope Management
To Design, plan, implement, and set measurement and controls of a personal health record (PHR) system that will help constituents have access to medical record anywhere and anytime. The organization has chosen to use the Veterans Affairs (VA) Health System that is available for free to anyone.
The Veterans Affairs (VA) Health System is free and is web base. This system does not require a network infrastructure to house or support. All the organization needs are available computers and mobile devices with access to the internet. The organization be capable of promoting, assisting and educating their constituents on the benefits and how to use the PHR system available. Therefore, personnel need to be trained in how to navigate the PHR website and how to guide new users that need registration
Work Breakdown Structure
1. My Health eVet Registration
1.1. Clinical staff
1.2. Service members
2. Training
2.1. How to use the online portal
2.1.1. Clinical staff
2.1.2. Service members
2.1.3. Existing Patients
2.1.4. New Patients
3. HIPPA Complains
3.1. Privacy Compliance documentation
3.1.1. Ensure clinical staff have read and agree to HIPPA regulations
3.1.2. Ensure service members have read and agree to HIPPA regulations
3.1.3. Provide Patient with HIPPA Compliance documentation
4. Computer access for the patient
4.1. Purchase
4.1.1. Interion privacy study Carrel Teak
4.1.2. Computers
4.1.3. Printers
4.2. Installation
4.2.1. Property management install the booths
4.2.2. IT helpdesk install the computer and printer
Deployment Plan
Deployment will start with registration of internal staff and training on the use of the PHR. We will also conduct HIPPA compliance refreshers. Also, private stations will be added to a designated area in the wait room to provide access for those with limited access to a computer. It will be two booths with computer and printers. Property management and helpdesk will need to get involve to set up such private booths.
Change Control Management
To major changes in control will happen in the project. First one will be the built of the privacy booth by property management. Second will be the installation of the computers and printer, with the necessary restriction for the user. Users will only have access to the Veterans Affairs (VA) Health System.
Schedule/Time Management
Establish a baseline within the first two weeks of the project and monitor progress against the baseline on a weekly basis. The Project Manager will be responsible for ensuring the project schedule is updated with the latest information and never more than three business days out of date.
Milestones
The table below lists the milestones for this project, along with their estimated completion timeframe.
|
Milestones |
Estimated Completion Timeframe |
|
My Health eVet registration |
2 days |
|
Training Clinical and Service staff |
5 days |
|
HIPPA Compliance Refresher |
5 days |
|
Purchase of privacy booths, computer and printers |
3 days |
|
Installation of privacy booth, computer and printer |
2 days |
Project Schedule
Refer to “Team B Healthcare Community Outreach Schedule and Budget Management” Excel document
Dependencies
There are three major dependencies. System is totally dependable on the Veterans Affairs Health system. Our organization does not control the system. Also, Information system department will install the computers and property management will install the privacy booths.
Cost/Budget Management
Refer to “Team B Healthcare Community Outreach Schedule and Budget Management” Excel document.
Quality Management
In most PHR implementation there is a level of requirements that the system has to meet. A very important requirement is for the system to be HIPPA compliance. For this project Veteran Affairs health system is an approved government regulated and HIPPA compliance application. Some other concerns in quality is the education standards and user computer privacy. There is a concern that a user walking away a computer may leave sensitive information unattended. For this we will require the helpdesk team to build a time out privacy screen that will pop up with a minute of no usage, asking the use to reenter their log in information.
Appendix A: Project Management Plan Approval
The undersigned acknowledge they have reviewed the PHR Veterans Affairs Health System Implementation Project Management Plan and agree with the approach it presents. Changes to this Project Management Plan will be coordinated with and approved by the undersigned or their designated representatives.
|
Signature: |
Carisma Smith |
Date: |
12/10/2018 |
|
Print Name: |
Carisma Smith |
|
|
|
Title: |
Project Manager |
|
|
|
Role: |
Project Team Lead |
|
|
|
Signature: |
Gemnot Cox |
Date: |
12/10/2018 |
|
Print Name: |
Gemmot Cox |
|
|
|
Title: |
Project Manager |
|
|
|
Role: |
Project Team Member |
|
|
|
Signature: |
Juan Hernandez |
Date: |
12/10/2018 |
|
Print Name: |
Juan Hernandez |
|
|
|
Title: |
Project Manager |
|
|
|
Role: |
Technology Support |
|
|
The following table summarizes the documents referenced in this document.
|
Document Name and Version |
Description |
Location |
|
A Research Agenda for Personal Health Records (PHRs) Version 15 |
The enrollment of the web-based site is completed within the username and a password. |
Kaelber, D. C., Jha, A. K., Johnston, D., Middleton, B., & Bates, D. W. (2008). A research agenda for personal health records (PHRs). Journal of the American Medical Informatics Association, 15(6), 729-736. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2585530/ |
|
The Value of Personal Health Record (PHR) Systems Volume 2008 |
Personal health records (PHRs) are a quickly increasing area of health information technology regardless of a absence of important appeal valuation. |
Kaelber, D., & Pan, E. C. (2008). The value of personal health record (PHR) systems. In AMIA Annual Symposium Proceedings (Vol. 2008, p. 343). American Medical Informatics Association. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2655982/pdf/amia-0343-s2008.pdf |
|
Glossary Volume Unknown |
CDC provides project plan terms |
Glossary(n.d.). Retrieved from https://www2.cdc.gov/cdcup/library/glossary/default.htm
|
|
Personal health records: Consumer attitudes toward privacy and security of their personal health information Volume 17 |
PHR systems creators strive to prepare the requirements of weakened and poorly individuals must check practical signs to comprehend the structure supplies entailed.
|
Lafky, D. B., & Horan, T. A. (2011). Personal health records: Consumer attitudes toward privacy and security of their personal health information. Health Informatics Journal, 17(1), 63-71. http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.820.5326&rep=rep1&type=pdf |
|
10 Examples of Milestones in Project Management Vol. Unknown |
Examples of Project Management |
10 Examples of Milestones in Project Management (2018). Retrieved from https://blog.teamweek.com/2018/07/project-milestones-examples/
|
The following table provides definitions for terms relevant to this document.
|
Term |
Definition |
|
Implementation Plan |
The Implementation Plan explains how the business merchandise will be established, arranged, and transitioned into the working atmosphere. |
|
Milestone |
An important fact or occasion in the plan. |
|
Stakeholder |
A person or business that is vigorously included in the project, which will influence the success of the project purposes |
APPENDIX D: SUMMARY OF SPENDING
[You may double-click on the table to edit it according to the information applicable to this project.]
1
Revision Date: Error! Unknown document property name.
Page 1 of 15
[Insert appropriate disclaimer(s)]
Budget ItemPY-1PYCYBYBY + 1BY + 2BY + 3BY + 4Total
Planning:
Budgetary Resources $ - $ - $ - $ -
$0.00
Outlays $ - $ - $ - $ -
$0.00
Development &
Implementation of
Project:
Budgetary Resources $ - $ - $ - $ -
$0.00
Outlays $ - $ - $ - $ -
$0.00
Total, sum of stages:
Budgetary Resources
$ - $ - $ - $ -
$0.00
Outlays
$ - $ - $ - $ -
$0.00
Operations &
Maintenance:
Budgetary Resources $ - $ - $ - $ -
$0.00
Outlays $ - $ - $ - $ -
$0.00
Total, all stages:
Budgetary Resources
$ - $ - $ - $ -
$0.00
Outlays
$ - $ - $ - $ -
$0.00
Government FTE cost $ - $ - $ - $ -
$0.00
Sheet1
| Budget Item | PY-1 | PY | CY | BY | BY + 1 | BY + 2 | BY + 3 | BY + 4 | Total |
| Planning: | |||||||||
| Budgetary Resources | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Outlays | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Development & Implementation of Project: | |||||||||
| Budgetary Resources | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Outlays | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Total, sum of stages: | |||||||||
| Budgetary Resources | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Outlays | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Operations & Maintenance: | |||||||||
| Budgetary Resources | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Outlays | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Total, all stages: | |||||||||
| Budgetary Resources | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Outlays | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 | ||||
| Government FTE cost | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $0.00 |