Implementation Of Electronic Medical Record: This Has To Be

Implementation Of Electronic Medical Record This Has To Be Completed

Implementation of Electronic Medical Record. This has to be completed in MS Project. Due Week 4: Work Breakdown Structure and Network Diagram According to the PMBOK, "the WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team, to accomplish the project objectives and create the required deliverables." In other words, it lists the tasks, the sub-tasks, the sub-sub-tasks, etc., for the project. For this phase, you will create a Work Breakdown Structure (WBS) for the project you selected during Phase One. Remember that the WBS starts with your major deliverables (that you stated in your Scope Management Plan) at the highest level.

The lower levels have the tasks required to complete those deliverables. You should have at least three tasks under each deliverable, but you may have as many tasks as needed to ensure that the deliverables are complete. Review the textbook (and the PMBOK, if you have it) for some suggestions on how best to create a WBS. From your work breakdown structure, develop a project task list with dependencies. Add durations.

Then submit a network diagram (using MS Project) and a project schedule. Develop the Work Breakdown Structure Your WBS should have a minimum of 25-30 tasks and be three subtasks deep. Make sure to use verb/object task names (for example, "Develop software"). Enter tasks in MS Project. Create the predecessor relationships to create a network diagram.

DO NOT LINK SUMMARY TASKS! In the Gantt Chart Tools tab, check the box marked "Outline Number" in the Show/Hide group. Deliverables: In MS Project, print the following: Gantt Chart Entry Table on no more than three pages [View > Tables > Entry] Include Task Name, Duration, Start, Finish, and Predecessor columns with Gantt Chart. Schedule Table on one page [View > Tables > Schedule] Include only the default columns (Task Mode, Task Name, Start, Finish, Late Start, Late Finish, Free Slack, Total Slack) and do not include the Gantt Chart. Make sure that all columns are wide enough to read completely.

Network Diagram on one page [Task tab > View group > Network Diagram] Highlight Critical Path and Circle Milestones. Justify why you chose your milestones. (Hint: use milestones from the scope statement or look for key merge or burst activities.) Also print out the network diagram on two to three pages so that task information can be read. Using the Resource Sheet (View > Resource Sheet) develop and print a list of resources required for your project. Include Max.Units and Costs (Std. Rate, Ovt.

Rate, Cost/Use). If working in a group, include a statement of participation, describing how each person contributed to this project deliverable. Please have each person sign the statement. DO NOT ASSIGN RESOURCES AT THIS TIME!

Paper For Above instruction

The implementation of an Electronic Medical Record (EMR) system is a complex and multi-faceted project that requires meticulous planning, detailed task management, and coordinated execution. Developing a comprehensive Work Breakdown Structure (WBS) forms the backbone of effective project planning by delineating all deliverables and activities required to successfully deploy the EMR system. This paper discusses the process of creating a WBS, developing task dependencies with durations, and illustrating the project schedule and network diagram, all within MS Project, as guided by the PMBOK framework.

Understanding the Work Breakdown Structure (WBS)

According to the Project Management Body of Knowledge (PMBOK), a WBS is a hierarchical decomposition of project deliverables and work packages that enables project teams to organize and quantify their tasks systematically (PMI, 2017). For the EMR implementation, the WBS begins with high-level deliverables such as System Analysis, Software Development, Hardware Deployment, and Staff Training. Each of these deliverables is further broken down into sub-deliverables and work packages until at least 25-30 tasks are identified, with a minimum of three tasks under each major deliverable, and the structure extends three levels deep.

Creating the WBS requires identifying key activities that are essential for the completion of each deliverable. For example, System Analysis can include requirements gathering, stakeholder interviews, and system design. Software Development might encompass coding, testing, and documentation. Hardware Deployment involves procurement, installation, and configuration, while Staff Training involves curriculum development, training sessions, and user support. These tasks need to be clearly verb/object-based to ensure clarity and actionable outcomes.

Developing Tasks, Dependencies, and Durations

Once the WBS is established, the next step is to translate each work package into distinct tasks within MS Project. Each task must have an estimated duration based on historical data, expert judgment, or analogous projects. For example, Requirements Gathering might take 10 days, Coding could take 30 days, and Training sessions might require 15 days. Dependencies between tasks are then established to define the sequence of activities—some tasks are sequential, while others can occur concurrently.

Creating dependencies involves setting predecessors in MS Project, indicating which tasks must be completed before subsequent ones can begin. For instance, Coding cannot start until System Design is finished, and user Acceptance Testing depends on the completion of Coding. Critical tasks that influence the project's completion date are identified during this process.

Constructing the Network Diagram and Schedule

The project schedule visually illustrates task sequences and dependencies, highlighting the critical path—the longest sequence of dependent tasks that determine the project's duration (Kerzner, 2017). Using MS Project's Network Diagram view, project managers can interpret process flows, identify critical activities, and recognize milestones—key points such as System Go-Live or Final Acceptance.

Milestones are selected based on scope statements and key deliverables—these are points where significant progress or decision-making occurs. Milestones might include completion of installation, successful system testing, and staff training completion, justified by their importance in ensuring project success and stakeholder approval.

Highlighting the critical path helps project managers focus on tasks that need close monitoring to prevent delays, while milestones provide checkpoints for progress assessment. Justifying milestones involves aligning them with project goals, scope, and stakeholder expectations.

Resource Planning and Cost Estimation

The Resource Sheet in MS Project allows for listing required resources—such as project team members, hardware, and software licenses—with information on maximum utilization (units) and associated costs (hourly rates or per-use charges). Resource allocation can be deferred until after task scheduling, but the resource list provides a basis for budgeting and cost control. Collecting resource data ensures readiness for project execution and provides visibility into budget requirements.

Conclusion

Creating a detailed WBS, developing task dependencies with durations, and establishing a project schedule are critical steps in the successful implementation of an Electronic Medical Record system. These activities enable project teams to visualize the project timeline, identify critical tasks, and allocate resources effectively. Utilizing MS Project in conjunction with PMBOK guidelines ensures a structured, transparent, and manageable approach, ultimately facilitating a smooth deployment aligned with organizational objectives and stakeholder expectations.

References

  • Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
  • PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.
  • Meredith, J. R., & Mantel, S. J. (2014). Project Management: A Managerial Approach. Wiley.
  • Schwalbe, K. (2015). Information Technology Project Management. Cengage Learning.
  • Heldman, K. (2018). PMP Project Management Professional Exam Study Guide. Sybex.
  • Taylor, J. E. (2018). Managing Large-Scale Projects. Routledge.
  • Gray, C. F., & Larson, E. W. (2020). Project Management: The Managerial Process. McGraw-Hill.
  • Wysocki, R. K. (2014). Effective Project Management. Wiley.
  • Heldman, K., & Casanueva, D. (2020). Project Management JumpStart. Wiley.
  • Mulcahy, R. (2018). PMP Exam Prep. RMC Publications.

Related Assignments