BUSI 611 Week 4 Discussion Board Forum 4 Example

Discussion Board Forum 4: Project Management in Health Care Operations

BUSI 611 Operations Management for Health Organizations, Discussion Board Forum 4

Thread by [Student Name]

The hospital, its new tower, its schedule and the classmates are composites; the textbook, Scripture and the peer-reviewed sources cited are real.

Our 260-bed community hospital will open a new 48-bed patient tower in eight months, moving two medical-surgical units and adding a 12-bed step-down unit. The board has announced the opening date publicly, the construction schedule is on track and a consultant built an activation plan with 1,400 tasks. When I reviewed the plan for our operations team, I found that testing the new space with staff appeared only in the final two weeks, as a single line labeled "simulation walk-throughs." Nothing in the schedule allowed time to fix what the walk-throughs might find. That is a classic project management mistake: treating testing as a box to check instead of an activity that generates work.

Langabeer and Helton (2016) describe project management as planning and controlling a temporary effort with a defined scope, schedule and budget, using tools such as a work breakdown structure, a network diagram that shows dependencies and the critical path that determines the earliest finish. They also emphasize managing risk by identifying what could go wrong, estimating its likelihood and impact and planning responses. Our tower has a clear scope and fixed date, so the critical path matters greatly. In the current plan, the path runs through construction completion, equipment installation, regulatory inspection and staff move-in. Testing sits off the path, which means a serious finding in the final two weeks would either delay the opening or be ignored.

Research on new facilities shows how much testing can find. Colman et al. (2019) ran simulation-based clinical systems testing in a newly built pediatric outpatient center before it opened, combining in situ simulations with failure mode and effects analysis. Over three months, 31 simulated scenarios in 15 clinics involving 150 participants and 151 observers identified 334 latent safety threats, classified as process and workflow, facility, resource or clinical performance problems, which were then ranked by risk. Kim et al. (2026) compared full-scale in situ simulation with process simulation before the opening of a new university hospital in Germany and found that, in both approaches, equipment problems were the most common threats, followed by team issues, room layout and accessibility. Participants rated the testing as highly useful before opening.

If a single outpatient building held more than 300 hazards, our tower will hold many too, and many will be equipment and layout problems that take weeks to correct, such as a missing oxygen outlet, a crash cart that does not fit through a doorway or a nurse call button out of a patient's reach.

I proposed three changes to the activation plan. First, schedule two rounds of simulation, the first at 90 days before opening, when rooms are finished but before equipment is final, and the second at 30 days. Second, add a fix window after each round, with an owner for each threat and a budget reserve for changes. Third, feed every finding into the project risk register, scored by likelihood and impact, and review the register weekly with the steering committee. The opening date can hold only if the plan leaves room to act on what testing finds. The added cost is modest, a few weeks of float and a small reserve, compared with the cost of opening a tower whose first patients discover the problems.

Luke explained that he had followed all things closely and decided to write an orderly account so that Theophilus might have certainty (English Standard Version Bible, 2001/2016, Luke 1:3-4). A project plan is an orderly account written in advance, and its value lies in the certainty it gives the people who will depend on the finished work. Patients entering the new tower deserve that certainty.

Reply to Renee

Renee, your thread described your hospital's plan to open a new emergency department wing, and you asked how to fit staff training and testing into a construction schedule that keeps slipping. Langabeer and Helton (2016) describe how delays on the critical path ripple through every dependent task, and construction delays are the most common reason testing gets squeezed. The answer is to tie simulation rounds to construction milestones rather than to calendar dates, so each round moves with the work it depends on.

Two studies show how this can be done. Kaba and Barnes (2019) describe process-oriented simulations used to test a new 300-bed facility before it opened, held in the actual care spaces before occupancy. The simulations examined the process of care rather than individual clinical skill, aiming to confirm that spaces matched staff needs and to find latent safety threats such as missing equipment, inefficient setup or insufficient room for procedures, and they doubled as part of the new site orientation. Geis et al. (2011) used simulation before opening a satellite hospital's pediatric emergency department, with 24 simulations over three months. Laboratory simulations first defined staff roles under a staffing model without residents or subspecialists, and later in situ simulations identified latent safety threats in the actual space. Workload measures showed the medication nurse carried the heaviest load during resuscitations, so the team changed how medications were delivered.

For your wing, I would suggest two milestone-based rounds. Hold laboratory simulations as soon as the staffing model is set, since role questions do not depend on construction, and hold in situ simulations once rooms reach substantial completion. If construction slips, the in situ round slips with it, but the role work is already done. Combining the simulations with orientation, as Kaba and Barnes describe, saves staff hours because each session both tests the space and teaches the team. It also means the staff who will work in the wing on opening day have already walked its hallways and found its supply rooms. Proverbs warns that haste leads to poverty while diligent plans lead to gain (English Standard Version Bible, 2001/2016, Proverbs 21:5), and tying tests to milestones is a careful plan that survives delay. Budget is the other piece. Each simulation round takes staff away from patient care for several hours, so the project budget should include backfill pay for participants, the cost of a simulation educator and a contingency for the fixes the rounds will reveal. Projects that omit those lines often cancel the second round when money runs short, which is exactly when the most serious threats tend to appear, because the second round tests the space with final equipment in place. Has your project team identified which construction milestone marks substantial completion for each area?

Reply to Tom

Tom, your thread presented a risk register for your clinic's move to a new building, listing ten risks such as moving day weather, phone lines not transferring and staff confusion about new workflows. I think your register is a good start, and Langabeer and Helton (2016) describe exactly this practice of listing risks and planning responses before they occur. I would suggest two improvements: scoring each risk by likelihood and impact so the team can rank them and adding categories of risk that simulation research shows are common but easy to overlook.

Research gives useful categories. Colman et al. (2019) classified the 334 threats they found in a new outpatient center into process and workflow, facility, resource and clinical performance issues and used failure mode and effects analysis to assign each a risk priority, so the team fixed the most dangerous problems first. Rule et al. (2017) used simulation before expanding an inpatient unit at a satellite hospital without an on-site intensive care unit, training 175 clinicians in 17 sessions and running in situ sessions before patients arrived. They identified 11 team-level knowledge deficits, 19 latent safety threats and 25 system-level issues, which led to changes in rapid response and code team staffing, including the use of intensive care physicians by telemedicine. Their categories, team knowledge, physical threats and system issues, map well onto a clinic move.

Applying those categories to your register, I would add risks such as emergency equipment that is not where staff expect it, a code response route that is longer in the new building and staff unsure who calls for help in a medical emergency. Each could be rated from one to five for likelihood and impact, with the product guiding priority. A short in situ simulation of a patient collapsing in the new waiting room would test several of these at once and would cost far less than learning the answers during a real emergency. Paul closed his instructions on public worship by asking that the church's gatherings proceed with decency and order (English Standard Version Bible, 2001/2016, 1 Corinthians 14:40), and a scored register brings that kind of order to a long list of worries. The register also needs owners and dates. Every risk should have one person responsible for its response and a date by which the response must be in place, and the project manager should review open risks at each weekly meeting until move-in. Risks that cannot be removed, such as a longer walk to the code cart, can be reduced by training or signage, and the register should record which approach was chosen and why. After the move, the team can close each risk or note what happened, which gives the organization a record to use the next time it opens a building. Would your team be willing to run a simulated emergency in the new space before the first patient visit?

References

Colman, N., Stone, K., Arnold, J., Doughty, C., Reid, J., Younker, S., & Hebbar, K. B. (2019). Prevent safety threats in new construction through integration of simulation and FMEA. Pediatric Quality & Safety, 4(4), e189. https://doi.org/10.1097/pq9.0000000000000189

English Standard Version Bible. (2016). Crossway. (Original work published 2001)

Geis, G. L., Pio, B., Pendergrass, T. L., Moyer, M. R., & Patterson, M. D. (2011). Simulation to assess the safety of new healthcare teams and new facilities. Simulation in Healthcare, 6(3), 125-133. https://doi.org/10.1097/SIH.0b013e31820dff30

Kaba, A., & Barnes, S. (2019). Commissioning simulations to test new healthcare facilities: A proactive and innovative approach to healthcare system safety. Advances in Simulation, 4, 17. https://doi.org/10.1186/s41077-019-0107-8

Kim, S., Schrader-Reichling, J., Lazarovici, M., Sandmeyer, B., & Trentzsch, H. (2026). A simulation-based clinical systems testing at the newly built LMU University Hospital: Comparison between in situ full-scale simulation and process simulation. Journal of Patient Safety, 22(4), 283-289. https://doi.org/10.1097/PTS.0000000000001471

Langabeer, J. R., II, & Helton, J. (2016). Health care operations management: A systems perspective (2nd ed.). Jones & Bartlett Learning.

Rule, A. R. L., Snider, J., Marshall, C., Kramer, K., Geis, G. L., Tegtmeyer, K., & Gosdin, C. H. (2017). Using simulation to develop care models for rapid response and code teams at a satellite facility. Hospital Pediatrics, 7(12), 748-759. https://doi.org/10.1542/hpeds.2017-0076