Project Management in Health Informatics
Case study of 3,000 words that presents a structured case study and academic evaluation of a health informatics project.
(IMPLEMENTATION OF DIGITAL DICTATION SYSTEM AT A HOSPITAL )
1-Abstract.
2-Introduction
2.1 Organisational context (Clear description of the project).
3-Mandating the project.
4-Aims
5-Obgectives.
6-Scope.
7-Boundaries.
8-Characteristics including those that make it interesting and relevant.
9-Highlighting the challenging faced and their root cause.
10-Methodology.
8.1 PRINCE 2 (Projects IN Controlled Environments). PINCE2 helps to identify the following. (Brief description)
1. Governance.
2. Business case.
3. Resource management.
4. Financial management.
5. Stakeholder engagement and benefits.
6. Risk assessment and risk management.
7. Communication delivery
8. Milestone
9. GANTT Chart
11-Result.
10.1-PRINCE2 Principle. Has been done during the project
Continued business Justification
Learn from experience
Define role and responsibilities
Managed by stages
Manage by expectation
Focus on Products
Tailor to suit project environment
10.2 PRINCE2 Theme. Has been done during the project
Business Case
Organisation
Quality
Plans
Risk
Change
progress
10.3 PRINCE2 Process Has been done during the project
Starting up a project
Directing a project
Initiating a Project
Controlling a Stage
Managing Project Delivery
Managing Stage Boundary
Closing a Project
10.4 Governance
Who is in project board Key roles
10.5 Business case
Product Title Business Case
Purpose
Description
Composition • Need for change
– Current situation
– Change drivers
• Vision
– Vision statement
– Outcomes
– Future Operating Model
• Delivery approach
– Programme scope
– Objectives
– Stakeholders
– Programme structure
– Governance
– Programme plan/timescales
– Links with other change initiatives
• Benefits
• Cost
• Risks
Input from
Used as an input to
Approved by
10.6 Roles and responsibilities of the project team
Project team Roles and responsibilities
10.7 Resource management.
Human
Building
Equipments
Supplies
Information
Tools and support team
10.7.1 Resource allocation
10.7.2 Task Effort (GANTT Chart).
10.8 Financial management.
Essential resources Cost categorized
Hardware
Software
Installation cost
Running cost
Maintenance
Security
Networking
Training cost
10.9 Stakeholder engagement and benefits
Stakeholders Internal to project team External to project team
Stakeholder benefits
NET BENEFITS BENEFITS BUT
FEW BENEFITS NET DISBENEFET
Communication plan and channels
Stakeholder Communication plan Communication channels
10.10Risk assessment and risk management.
Risk assessment and risk management
Code Description of the risk Likelihood Impact Priority Treatment Control
Risk management contingency plan
10.11 Buying off-shelf software feasibility assessment.
Technical Feasible
Economical Feasible
Opertaionally Feasible
Organisational Feasible
10.12 Quality criteria for the project.
10.13 Closing the project
Benefit planned
Benefit realised
Benefit not yet achieved
Value of the work
-Celebrate success
-Recognition of members
10.14Project Milestone.
11-Discussion ( Very important part) Please discuss in depth).
11.1 11.2 Has the digital dictation system failed or succeeded? Explain why.
11.2 Lessoned learned from the project.
12-Conclusion
13-Refrences