DEVELOPING A SMALL INFORMATICS PROJECT FOR YOUR ORGANIZATION, PART 2: IMPLEMENTATION
paysprincess
RubricWeek9Assignment.docx|
NURS_8210_Week9_Assignment_Rubric |
||||||
|
Criteria |
Ratings |
Pts |
||||
|
All documents from Part 1 are included in the Part 2 submission. |
|
150 pts |
||||
|
Is the project staying within scope? |
|
40 pts |
||||
|
Were all of the gaps identified? |
|
20 pts |
||||
|
Is the project following the timeline? |
|
40 pts |
||||
|
If you had a budget, is it on track? |
|
40 pts |
||||
|
Were all of the work activities correctly assigned? |
|
20 pts |
||||
|
Are team members responsible? |
|
20 pts |
||||
|
Did the project start on time, inline to meet due dates? |
|
40 pts |
||||
|
Are you holding weekly status meetings and documented all activities? Are all team members in attendance and communicated with? |
|
20 pts |
||||
|
Are all changes approved and documented? |
|
20 pts |
||||
|
Are all risks identified, prioritized, assigned an owner, and mitigation plan developed? |
|
20 pts |
||||
|
A final summary that includes complete evaluation of the full project and lessons learned: what went well and what needs updated and revised. |
|
55 pts |
||||
|
Expression and Formatting - Paragraph Development and Organization: Paragraphs make clear points that support well-developed ideas, flow logically, and demonstrate continuity of ideas. Sentences are carefully focused—neither long and rambling nor short and lacking substance. A clear and comprehensive purpose statement and introduction is provided which delineates all required criteria. |
|
5 pts |
||||
|
Written Expression and Formatting - English writing standards: Correct grammar, mechanics, and proper punctuation |
|
5 pts |
||||
|
Written Expression and Formatting - The paper follows correct APA format for title page, headings, font, spacing, margins, indentations, page numbers, parenthetical/in-text citations, and reference list. |
|
5 pts |
||||
|
Total Points: 500 |
NURS_8210_Week9_Assignment_Rubric
SWOT ANALYSIS
|
STRENGTH · Reduces medical errors · Alerts significant lab results · Make health information available
|
WEAKNESSES · Risk of violating privacy · Outdated data, if not updated · Alert fatigue on Staff |
|
OPPORTUNITIES · Expand software testing · Increase the usability of EHR software · Reducing clinically irrelevant warning
|
THREATS · Lack of computer skills · Unfamiliarity with the system · Technical glitches |
Gantt Chart
|
Activity |
Timeline |
|
|
|
|
|
|
|
|
|
|
April |
May |
June |
July |
August |
4/26 |
5/1 |
6/8 |
7/15 |
|
Creating core team |
|
|
|
|
|
|
|
|
|
|
Developing project plan and timeline for selection and implementation |
|
|
|
|
|
|
|
|
|
|
Identifying EHR critical components and requirements. |
|
|
|
|
|
|
|
|
|
|
Develop the Request for Implementation |
|
|
|
|
|
|
|
|
|
|
Identifying and evaluating vendors |
|
|
|
|
|
|
|
|
|
|
Complete EHR demos for identified vendors
Finalize the contract and continue with EHR implementation.
|
|
|
|
|
|
|
|
|
|
Communication Plan
The communication strategy should set a communication network based on the project team’s organizational structure. The network should connect every organization horizontally and vertically and feature formal and informal communication channels.
|
Communication |
Method |
Frequency |
Goal |
Owner |
Audience |
|
Project Status Report |
|
Weekly |
Review project status & discuss possible issues. |
Project Manager |
Project Team & Sponsor |
|
Team Standup |
Meeting |
Daily |
Discuss each team member’s responsibilities |
Project Manager |
Project Team |
|
Project Review |
Meeting |
At milestones |
Project deliveries were examined, and feedback was gathered for the next meeting. |
Project Manager |
Project Team & Sponsor |
|
Postmortem Meeting |
Meeting |
At the end of the project |
Evaluating what worked and what did not work. |
Project Manager |
Project Team |
|
Task progress Updates |
Team Gantt |
Daily |
Share daily progress |
Project Manager |
Project Team |
Risk Management Plan
Various risks can occur during implementation hence the need for a risk management plan. The process that will be used to reduce the occurrence of risks during implementation includes:
Identifying all potential risks that may impact the project is essential. The risks can easily be identified through brainstorming a possible solution
Risk assessment: It is essential to assess an identified risk to determine its possible impact in case it occurs. Also, evaluating risk will enable the team to determine its potential to occur.
Monitoring risk: lastly, monitoring the identified risks throughout is essential to ensure they are controlled effectively.
Risk Management Plan
Controlling the risk: The team will develop control measures to reduce the chances of it occurring. Some control helps to eliminate the threat.
