Project Universal Patient

Prof. Belton, MPM CIPM

Christian Gonzalez, PMTamika Roland, Project CoordinatorTeria Edwards, Quality Manager

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

Table of Contents

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.

Project Overview

Project Management Strategy

Effective Project Management, pg22

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

Organizational ChartITMCDavid Belton

Christian GonzalezProject Manager

Tamika RolandProject Coordinator

Teria EdwardsQuality Manager

TEAM MEMBER/BACK-UP SCOPE QUALITY RISK COMM HUMAN

RESOURCES TECHNICAL COST

Christian Gonzalez/Tamika Roland R I C R I A R

Teria Edwards/ Chris Gonzalez I R A C R C I

Tamika Roland/ Teria Edwards I I R R A R C

R = RESPONSIBLE, A = ACCOUNTABLE, C = CONSULT, AND I = INFORM

RACI

Communication Communication Type

Objective of Communication

Medium Frequency Audience Owner

Kickoff Meeting Introduce the project team and the project. Review project objectives and management approach.

Face to Face Once Tamika Roland

Teria Edwards

Christian Gonzalez

Project Team Meetings

Review status of the project with the team.

Face to Face Conference

Call

Weekly Tamika Roland

Teria Edwards

Christian Gonzalez

Technical Design Meetings

Discuss and develop technical design solutions for the project.

Face to Face As Needed Tamika Roland

Teria Edwards

Christian Gonzalez

Weekly Project Status Meetings

Report on the status of the project to management.

Face to Face Conference

Call

Weekly Prof. Belton John Allen

Christian Gonzalez

Project Status Reports

Report the status of the project including activities, progress, costs and issues.

Email Weekly Prof. Belton Chris

Gonzalez Tamika

Roland Teria

Edwards

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.

Scope

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

Objectives

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

Exclusions

RBSRequirements Breakdown Structure

Universal Record Ststem

Database(Cloud)

Store Patient Records

HIPPA Compliance

Universal Patient Record

FormatStandard Security

Compliance

FIPS 140.3

Maximum security

Tier based Levels

Encrypted Systems

Server LocksKeystroke

Logger

Timed User Logouts

Up-to date Security

RequirementsExceeds HIPPA

Standards

HIPPA ISO 27001

Technical

IT Architecture

Establish Levels of

Authorization (Tiers)

Establish Authorized Certificates

Processing Environment

Hardware Requirements

Additional Security

Software Requirements

Additional Security

Verification of User

Future Expansion

Store New Patient Records

FIPS 140.3

HIPPA

ISO 27001

Standards

Measures of Project SuccessThe metrics determined for the project is a 0-5 number scale.

5-Excellent4-Above Average3-Moderate2-Poor1-Incomplete

Project Milestones; creation of the database passing the SAS 70 audit integration of patient records implementation of the cloud database

Quality

8.3.1.2 Perform Quality Control

Risk breakdown structure

Risk ID Risk Description Probability Impact Score01 Security Unauthorized personnel access the

database .80 .90 .72

Project Impact: Breach of patient information, lawsuits Mitigation: tier base security levels, encrypted servers with locks, Certified access certificates, location based access onlyOwner: Tamika Roland

Project risks

02 Scope creep The project diverts from its baseline .60 .90 .54Project Impact: loss of project time, additional costs, Mitigation: Weekly scoping meetings, monitor scope & work

throughout projectOwner: Christian Gonzalez

03 HR The human resources give out their database pass code .60 .90 .54

Project Impact: Lawsuit against the hiree and cost for assisting patients

Mitigation: Certified access certificate, location based access only

Owner: Teria Edwards

05 Schedule The 23 week schedule is insufficient.40 .80 .32

Project Impact: Delay while request additional time is processed, Failed project

Mitigation: Research and retrieve SME’s for launching phase

Owner: Christian Gonzalez

04 Standards The new HIPPA standards change the requirements of the project. .60 .80 .42

Project Impact: Delay in the project to add the new requirements Mitigation: Meet FIPS 140.3 standards and pass SAS 70 inspection

Owner: Christian Gonzalez

Cost Activity Cost

Activity 1(WBS 1.0)

Research

$60,000

Activity 2(WBS 2.0)

Cloud Creation

-Includes materials and labor

$13,950,000

Activity 3(WBS 3.0)

Additional Security

-Includes materials and labor

$50,000

Activity 4(WBS 4.0)

Quality Testing(COQ)

-Includes materials and labor

$725,000

Activity 5(WBS 5.0)

Database Setup

-Includes materials and labor

$4,300,000

Activity 6(WBS 6.0)

Monitor Performance

-Includes materials and labor

$775,000

Activity 5(WBS 7.0)

Closing

-Payoff open accounts and client acceptance

$140,000

TOTAL $20,000,000

EVM & S-Curve

7.3.2.1 Control Cost

WBS

Schedule

Record Scanning & Transferring

Uploading Certificates

Creating & Documenting Logins

HR

1 2 3 4 5 6 7 8

PlannedActual

Labor Chart

9.1.3.1 Develop HR Plan

Training Outline(COQ)

Rental fee◦ $1,000 per month

Certificate cost◦ $1,400

Login fee◦ Begins at $200

Return On Investment

Approximately 90,500 offices and clinics with 3 nurses and 2 doctors

Return On Investment

3 nurses2 doctors

$200 x 3=$600$600 x 2=$1,200Total =$1,800

Texas90,500 x $1,800=$162,900,000

National Implementation$162,900,000 x 50= $8.15 Billion

Sample

http://www.ihs.gov/adminmngrresources/hipaa/ http://searchsmbstorage.techtarget.com/feature/Understanding-cloud-storage-s

ervices-A-guide-for-beginners http://www.clouddip.com/healthcare/ http://www.hipaa.com/2011/08/get-ready-now-for-toughened-hipaahitech-act-pri

vacy-and-security-rules-and-enforcement-and-big-noncompliance-fines/ http://www.ehow.com/facts_5082801_hipaa-electronic-health-records.html

Work Cited

Peer evaluation