Confidential

Document1
Last printed on 5/11/2014 10:25:00 PM

3BC EHR Consulting
Project Status Report

Project Name: Funny Bone Memorial Hospital
Department: Emergency Department
Focus Area: EHR
Product/Process: Implementation of selected products

Prepared By:
Document Owner(s) Project/Organization Role
Denise Benally Processor
Janet Bragg Team lead
Sharon Burnes Author
Janis Cousino Systems engineer





Project Status Report

Confidential Page 2 5/11/2014



TABLE OF CONTENTS
1 PROJECT STATUS REPORT PURPOSE .................................... 2
2 PROJECT STATUS REPORT ...................................................... 3
2.1 Project Status Report Details ............................................... 3
2.2 Project Status Report Template ........................................... 4
3 PROJECT STATUS REPORT APPROVALS ............................... 8
4 APPENDICES .............................................................................. 9
4.1 Document Guidelines ........................................................... 9
4.2 Project Status Report Sections Omitted ............................... 9


PROJECT STATUS REPORT PURPOSE
We strive to provide customized planning and technical assistance services and
offers meaningful use support that improves operational processes, information,
and technology. Thorough and effective planning provides the foundation to help
our clients develop the strategies and road map necessary for the successful
deployment and adoption of their IT.

The Project Status Report is a document that Project Managers may use as a
means of formal regular reporting on the status of a project to key project
stakeholders, including the Steering Committee, Project Sponsor, and Senior
Manager.



Project Status Report

Confidential Page 3 5/11/2014


1 PROJECT STATUS REPORT
1.1 Project Status Report Details
1.2 Our mission is to create a high quality, fully integrated, EHR system that connects
all aspects of patient health record information across all departments and
specialties to promote faster and more complete patient care at the point of care.
1.3 On Schedule Processes
o EHR implementation in ER -- Phase 1
o Milestone Deliverables for the last reporting period are: to sign off on
implementation
o Project impact of success or failure of milestone deliverables for the remaining
period of the project.
Budget ReportWrite with respect to planned expenditure, actual expenditure and
deficit/surplus:

Risk Management ReportSpecify any changes to the major risks identified since
the previous report and modification to the strategies put in place to manage them, if
appropriate:

Issues Reportareas of concern, specific problems, and any action/decision that
needs to be taken by the Steering Committee: We can anticipate a 30% to 50%
dropoff in productivity in the first 3 months after going live with EHR system
Double check requirements and get pre-authorizations



Project Status Report

Confidential Page 4 5/11/2014


1.4 Project Status Report
Project Name
Prepared By:
[Name] Sharon Burnes
Date:
05/05/2014
Reporting Period:
6/01/2014 to 12/24/2014
Project Overall Status: Running on schedule on most projects
We are a little behind on Work flow redesign, Network creation, Software configuration,
Entering old data, and Inputting paper data
Project Summary:
Stakeholders are content with progress of performance and will be updated periodically
Milestone Deliverables performance reporting over first period
Milestone Deliverables Due Date
%
don
e Deliverable Status

Milestone 1
Phase 1 Start up 6/06/2014 100% [On Schedule]
Work flow analysis 6/16/2014 100% [Ahead of Schedule]
Work flow redesign 6/29/2014 30% [Behind Schedule]

Milestone 2
Hardware Selection 7/22/2014 60% [On Schedule]
Procedural Manuals 7/22/2014 100% [Ahead of Schedule]
Network creation 7/17/2014 3% [Behind Schedule]

Project Status Report

Confidential Page 5 5/11/2014


Milestone Deliverables scheduled for completion over next period

Milestone Deliverables Due Date
%
Completed Deliverable Status
Milestone 3
Facility modification 7/06/2014 25% [On Schedule]
Hardware installation 7/27/2014 75% [Ahead of Schedule]
Software configuration 9/08/2014 1% [Behind Schedule]

Milestone 4
Developing a backup plan 9/21/2014 60% [On Schedule]
Forms/Bar code creation 9/20/2014 55% [Ahead of Schedule]
Clarifying details 7/03/2014 % [On Schedule]
Clarifying roles,
responsibilities
7/09/2014 % [On Schedule]

Milestone 5

Super User Mgr. Developing 9/15/2014 50% [Ahead of
Schedule]
Create a Training
Environment
8/27/2014 5% [On Schedule]
Entering old data 10/09/2014 1% [Behind Schedule]
Inputting paper data 11/11/2014 0% [Behind Schedule]

Project Status Report

Confidential Page 6 5/11/2014



Milestone 6
Staff Training 11/09/2014 0% [On Schedule]
Mock Live 10/18/2014 0% [On Schedule]
Work flow analysis 10/17/2014 0% [On Schedule]
Go live 11/19/2014 0% [On Schedule]
Milestone 7
Work flow re-analysis 11/09/2014 0% [On Schedule]
Details 12/08/2014 0% [On Schedule]
24 hour Team Support &
Edu.
12/22/2014 0% [On Schedule]
Sign off 12/23/2014 0% [On Schedule]
Celebration 12/24/2014 0% [On Schedule]


Project impact of milestone success or failure for project remainder
Testing and after
implementation changes that
may need to be modified
Not applicable at this time

Project Budget/Financial Status
Budget Item Planned Budget
Actual
Cost Variance/Explanation
Added licenses $50. $100
More WOW stations
$1299.00 $1299.00 One more needed


Project Status Report

Confidential Page 7 5/11/2014



Project Issue Management Status
Issue and
Description
Project
Impact
Target Due
Date Issue Status Issue Resolution
Software input
Input wrong
Output
wrong

[High/Med
ium/Low]
07/14/2014 [Open/Closed]
[Description]
Running
hardware
Too little
wire
Wrong wire
used
[High/Med
ium/Low]
06/28/2014 [Open/Closed]
[Description]

Project Recommendations
Steering Committee, Project Sponsor, or Senior Manager: consider for
endorsement. The questions to consider for review with key project stakeholders
are:
Will the project be completed on time and on budget?
Will the project deliverables be completed within acceptable quality levels?
Are scope change requests being managed successfully?
Are project issues and risks being addressed successfully and mitigated?
Are all customer concerns being addressed successfully?
Objectives for Next Project Status Review
Expectations of project as expected by stakeholders, manager, and staff; and are up
for review again in 30 days
Expectations of budget are as expected by stakeholders
Project Status Report

Confidential Page 8 5/11/2014


2 PROJECT STATUS REPORT APPROVALS
Prepared by __________writer________________________

Project Manager

Approved by __________team lead____________________

Project Sponsor

__________________________________
Executive Sponsor

__________________________________
Client Sponsor



Project Status Report

Confidential Page 9 5/11/2014
3 APPENDICES
3.1 Document Guidelines

3.2 Project Status Report Sections Omitted
None