Project Universal Patient

1. Project Universal Patient Prof. Belton, MPM CIPM Christian Gonzalez, PM Tamika Roland, Project Coordinator Teria Edwards, Quality Manager

2. Table of Contents • Background • Project Overview • Project management Strategy • Organizational Chart • RACI • Communication • Scope • Objectives • Exclusions • Requirement Breakdown Structure • Project Standards • Quality • Risk Breakdown Structure • Project Risk • Cost • EVM & S-Curve • WBS • Schedule • HR • ROI • ROI • Work Cited

3. Background • Over your lifetime, you will experience situations in which you will seek out medical services outside of your primary doctor. • Each time, you will be asked for your medical history, and often, you will have to either arrange with your primary doctor to release and transfer your records or pick them up yourself and give them to them to your new doctor. • In an emergency, it would be great if a doctor can access your medical history right away, which can prove to be lifesaving. • The purpose of this project is to research and develop design for solution that will provide a standard set of tools for hospitals, doctors’ offices, and other healthcare providers to share patient records to ensure the timeliest data is available when a patient needs care. • This project is aimed at developing a design for a secure universal patient record system that might influence a pool of accurate customer records and data processing, coupled with hospital or doctor record keeping.

4. Project Overview

5. Project Management Strategy • What business situation is being addressed? • Correcting the problem of lack of comprehensive readily available patient records • What do we need to do? • Elicit a clear and complete statement of the problem to be solved and then provide a clear statement of how we intend to solve • What will we do? • Decide what can be done • How will you know you did it? • Make a plan then another do some work and then plan some more • How well did you do? • Did it meet client requirements, is the record system we produced of quality Effective Project Management, pg22

6. Organizational Chart

7. RACI

8. Communication

9. Scope • Innovators Contractor’s will provide real-time access to a complete secure universal patient record database system that will allow the doctors, researchers, academics, and other healthcare professionals to give their patients higher quality care. The system will meet the Health Insurance Portability and Accountability Act (HIPAA) standards. The design of the technical architecture of this project will be defined and delivered in a 23-week time frame and within a 20 million dollar budget.

10. Objectives • The cloud database will store all the patient information according to the patient’s identification number in the database. Information needed about the patients’ history must be easily extracted by medical professionals no matter their location • Compliance to HIPPA standards is a requirement in order to launch the database. • Cisco hardware will be some of the hardware being procured and installed to keep the database secure and create the platform for the database. • Atop of the standard Cisco security that complied with HIPPA standards there will be additional security integrated into the cloud such as encrypted servers, tier base security levels, and certified certificates that all the users must procure in order to enter the database. • To meet the requirement for future expansion some space will be integrated into the cloud alongside the additional hardware that made it possible

11. Exclusions Work that has been excluded from the project scope and will not be provided by innovative contractors is; • Will not create an application(app) to assist in entering the system. • Will not hire permanent human resources to monitor the database. • Will not incorporate an email system into the database • Will not allocate human resources globally to retrieve patient records • Will not globally integrate patient records into the database • Will not maintain or save hard copy patient records • Will not destroy hard copy patient record files

12. RBS

13. Standards FIPS 140.3 HIPPA ISO 27001

14. Quality Measures of Project Success The metrics determined for the project is a 0-5 number scale. • 5-Excellent • 4-Above Average • 3-Moderate • 2-Poor • 1-Incomplete Project Milestones; • creation of the database • passing the SAS 70 audit • integration of patient records • implementation of the cloud database 8.3.1.2 Perform Quality Control

15. Risk breakdown structure

16. Project risks

17. Cost

18. EVM & S-Curve 7.3.2.1 Control Cost

19. WBS

20. Schedule

21. HR Training Outline(COQ) 9.1.3.1 Develop HR Plan

22. Return On Investment • Rental fee • $1,000 per month • Certificate cost • $1,400 • Login fee • Begins at $200

23. Return On Investment • Approximately 90,500 offices and clinics with 3 nurses and 2 doctors 3 nurses 2 doctors $200 x 3=$600 $600 x 2=$1,200 Total =$1,800 Texas 90,500 x $1,800=$162,900,000 Sample National Implementation $162,900,000 x 50= $8.15 Billion

25. Work Cited • http://www.ihs.gov/adminmngrresources/hipaa/ • http://searchsmbstorage.techtarget.com/feature/Understanding-cloud-storage-services-A-guide-for-beginners • http://www.clouddip.com/healthcare/ • http://www.hipaa.com/2011/08/get-ready-now-for-toughened-hipaahitech-act-privacy-and-security-rules-and-enforcement-and-big-noncompliance-fines/ • http://www.ehow.com/facts_5082801_hipaa-electronic-health-records.html

26. Peer evaluation