Universal Patient Record System

Project Management Capstone: Integration

Professor Garza

Christian Gonzalez, Project Manager Tamika Roland, Project Coordinator Teria Edwards, Quality Manager

Project Requirements Survey Management Strategy Technical Structure Control Chart Scope WBS Project Milestones Risk Register Scope Validation Project Closing Work Cited

Benefits The completed system will adequately assist the health care providers, doctors, and nurses look up patient records in a single location. This project will be successful in reducing waiting time for assisting other patients thus increasing profit. A secure system that can store confidential patient information Success Criteria

Understanding of the project

Completion of the Cloud database Compliance of HIPPA standards Completion of the project within schedule and under budget Client satisfaction

The system should create a common record to store patient records.

The system should meet HIPPA requirements. Define technical architecture, the processing environment, and hardware and software requirements. The system should be expandable for future business.

Questions
Do you have to get authorization to get or give patient records often? Does it take long? Can waiting on authorization exceed 48 hours turnaround time? Have a patient almost lost their life while going through authorization process? Do you feel that establishing a universal patient record system should be developed? Do you feel that you will benefit from the system? Do you feel that patients will benefit from the system? If a secure universal system is developed will you trust it and use it?

Yes/No

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

Nurses, EMT
Health Care Providers Doctors

Tier based access levels Encrypted servers Server locks Login access Certified certificates for location access only Timed access login Key stroke log Database Management Systems (DBMS Entity Relationship Modeling (ERM)

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.

Risk ID

Risk

Elements

Priority Ranking

Examined

Responsible

Likely

Actions

Approved

Sign Off

SECURITY

RISK MANAGEMENT, HR MANAGEMENT PMP, COMMUNICATION MANAGEMENT SCOPE MANAGEMENT HR MANAGEMENT, RISK MANAGEMENT Time Management, Risk & Cost Management Quality Management, Risk Management

HIGH

CLOSED

EVERYONE

0.8

MONITOR & CONTROL

YES

PS

SCOPE CREEP

HIGH

CLOSED

TAMIKA ROLAND

0.6

COMMUNICATE

YES

PM

HR

HIGH

CLOSED

TERIA EDWARDS

0.6

MONITOR & CONTROL

YES

PC

Schedule

HIGH

CLOSED

Chris Gonzalez

0.4

Monitor & Control

YES

PS

Standards

HIGH

CLOSED

Teria Edwards

0.6

Implement & inspect

YES

PM

Budget

Cost and Risk Management

HIGH

CLOSED

Chris Gonzalez

0.5

Monitor & Control

YES

PS

The important aspects of closing out a project by describing the following aspects: Scope Verification Contract Closeout Administrative Closeout Lessons Learned Historical Records Final Report Celebrating Success

http://www.hipaa.com/2011/08/get-ready-now-for-toughenedhipaahitech-act-privacy-and-security-rules-and-enforcementand-big-noncompliance-fines/

http://www.aicpa.org/InterestAreas/FRC/AssuranceAdvisorySer
vices/Pages/SORHome.aspx

http://www.journalofaccountancy.com/Issues/2010/Aug/20103 009.htm