| Course | IHP 435 Performance Improvement Measurement and Methodologies |
|---|---|
| Module | Module 7 |
| Paper type | project two performance improvement plan |
| Length | About 1,040 words, 6 pages |
| Format | APA 7 student paper |
| School | Southern New Hampshire University |
| Program | BS Healthcare Administration |
| Updated | September 2026 |
Free sample paper for IHP 435 Module 7
Project Two: Getting the First Case Started on Time
[Student Name]
Southern New Hampshire University
IHP 435: Performance Improvement Measurement and Methodologies
Project Two
[Instructor Name]
[Date]
Project Two: Getting the First Case Started on Time
Cedar Point's six operating rooms book the day's opening cases for 7:30 each morning. Across the last quarter, only 54% started within five minutes of that time, and the median delay for late starts was eighteen minutes. A late first case pushes every later case back, extends overtime, frustrates surgeons and patients and sometimes causes cancellations at the end of the day. This project plans an improvement: it describes the problem and its causes, sets an aim, selects a method, lays out changes to test, addresses the context that will shape success and defines a complete set of measures.
Understanding the Causes
For one month, circulating nurses recorded a delay reason for every first case that started late, using a list of standard codes. Of 64 late starts, 22 involved a missing or incomplete consent or history and physical, 17 involved the surgeon arriving after 7:30, 11 involved the patient not being ready because preoperative tasks such as IV placement or lab results were incomplete, 8 involved anesthesia evaluation delays and 6 involved equipment or room issues. A Pareto chart showed that the first three causes accounted for about three quarters of delays. A process walk revealed why: consent forms were often signed in the surgeon's office but not scanned into the record, preoperative nurses started at 6:00 a.m. with too many patients arriving at once and there was no shared expectation that surgeons be present by 7:15 for the final check.
Aim
The aim is to increase the percentage of first cases starting within five minutes of schedule from 54% to 85% within six months, without increasing preoperative staff overtime or the rate of cases canceled on the day of surgery.
Choosing a Method
The causes are mainly problems of flow, preparation and coordination, the kinds of waste Lean is designed to remove: waiting for documents, batching of patient arrivals and unclear standard work. Surveying the Lean literature across health care, D'Andreamatteo et al. (2015) found that operating rooms and surgical services were among the settings where Lean was most often applied, with many studies reporting shorter delays and better use of time. They also noted that the evidence consisted largely of case studies and that success depended on moving beyond tools to organizational change. The project therefore uses Lean principles, standard work, flow and visual management, with each change tested through small PDSA cycles.
Changes to Test
Four changes target the main causes. First, a pre-surgery readiness check two business days before surgery, in which a scheduler confirms that consent and history and physical are in the record, escalating gaps to the surgeon's office. Second, staggered patient arrival times, with first-case patients arriving at 5:45 a.m. and others later, so preoperative nurses can prepare first cases fully. Third, a standard expectation, agreed by the surgery department, that surgeons arrive by 7:15 for the preoperative huddle, with arrival times posted. Fourth, a visual board in the preoperative area showing each first-case patient's readiness steps in real time. Each change will start with one or two rooms for two weeks before spreading.
Table 1. Changes, Causes, Owners and First Tests
| Change | Cause addressed | Owner | First test |
|---|---|---|---|
| Readiness check two days before | Missing consent or history and physical | Surgical scheduling manager | Two surgeons' patients, two weeks |
| Staggered arrival times | Incomplete preoperative preparation | Preoperative nurse manager | First cases in rooms 1-2 |
| Surgeon arrival by 7:15 | Late surgeon arrival | Chief of surgery | Orthopedic service first |
| Visual readiness board | Poor coordination | Perioperative director | Preoperative area, all rooms |
Note. Each test is expanded only after its PDSA review.
The Context for Success
Kaplan et al. (2010) systematically reviewed research on the context of quality improvement and identified factors associated with success. Among the most consistent were leadership support from senior management, an organizational culture supportive of improvement, the maturity of data systems, physician involvement and the leadership and experience of the improvement team itself. They concluded that context can matter as much as the method.
The plan addresses these factors directly. The chief of surgery and the chief nursing officer co-sponsor the project and will attend monthly reviews. Two surgeons, one orthopedic and one general, serve on the team to lead peer conversations about arrival times. The quality department provides a daily automated report of first-case start times from the operating room system, so data do not depend on manual collection. And the team is led by the perioperative director, supported by a quality coach with Lean experience.
Measures
The main process measure, the share of first cases starting within five minutes of schedule, is tallied daily and charted weekly. Supporting process measures are the percentage of patients passing the two-day readiness check and median surgeon arrival time. The outcome measure is operating room overtime hours for scheduled staff, reflecting the day-long effect of on-time starts. A structure measure is the presence of the visual board and staggered schedule. Balancing measures are preoperative staff overtime and day-of-surgery cancellations, since early arrival times or stricter checks could shift burdens elsewhere.
Reading Progress Over Time
Perla et al. (2011) show how run charts, plotting data over time around a median with simple probability rules, help teams tell real improvement from chance. The team will plot weekly on-time start percentages beginning with twelve weeks of baseline and will annotate each chart when a change is introduced. A shift of six or more weeks above the baseline median after a change would indicate a real improvement. Balancing measures will be charted the same way so any unintended effects become visible early.
Timeline and Sustainability
Month one covers baseline data, team formation and the process walk. Months two and three test the readiness check and staggered arrivals. Months three and four test the surgeon arrival standard and visual board. Months five and six spread successful changes to all rooms and build them into standard work. Sustainability measures include adding the readiness check to scheduling job descriptions, reviewing on-time starts at the monthly surgical committee and keeping the visual board as part of daily routines.
Conclusion
First-case delays at Cedar Point come mainly from missing documents, preparation bottlenecks and late arrivals. Lean changes tested through PDSA, supported by leaders and surgeons and tracked with a full measure set on run charts, give the hospital a realistic path from 54% to 85% on-time starts.
References
D'Andreamatteo, A., Ianni, L., Lega, F., & Sargiacomo, M. (2015). Lean in healthcare: A comprehensive review. Health Policy, 119(9), 1197-1209. https://doi.org/10.1016/j.healthpol.2015.02.002
Kaplan, H. C., Brady, P. W., Dritz, M. C., Hooper, D. K., Linam, W. M., Froehle, C. M., & Margolis, P. (2010). The influence of context on quality improvement success in health care: A systematic review of the literature. The Milbank Quarterly, 88(4), 500-559. https://doi.org/10.1111/j.1468-0009.2010.00611.x
Perla, R. J., Provost, L. P., & Murray, S. K. (2011). The run chart: A simple analytical tool for learning from variation in healthcare processes. BMJ Quality & Safety, 20(1), 46-51. https://doi.org/10.1136/bmjqs.2009.037895
What the IHP 435 Module 7 instructions ask for
Project Two in IHP 435 usually asks you to develop a complete performance improvement plan: the problem with data, root causes, an aim, a justified method, changes to test, context and stakeholders, a full measure set and a timeline. Expect five to seven APA 7 pages. Use data to identify causes, write an aim with a number, a date and balancing conditions and match your method to the problem's character. Tie each change to a cause, plan small tests, address the context that shapes success and define process, outcome, structure and balancing measures displayed over time. Instructors look for coherence from causes to changes to measures. IHP 435 graders notice clean headings in IHP 435 papers. IHP 435 names and dates need checking before IHP 435 submission.
How this IHP 435 Module 7 project two example is built
This plan targets operating room first cases that start on time only 54% of the time at a composite hospital. A month of delay codes and a Pareto chart show missing consents, late surgeons and incomplete preparation cause about three quarters of delays. The aim is 85% within six months without more overtime or cancellations. D'Andreamatteo and colleagues support Lean for surgical flow, and four changes, from a two-day readiness check to a visual board, are tested through PDSA. Kaplan and colleagues' context factors shape sponsorship and surgeon involvement, and a full measure set is charted following Perla and colleagues. IHP 435 students can reuse this structure for IHP 435 work. IHP 435 claims here trace to cited IHP 435 sources.
Where the IHP 435 Module 7 rubric puts the points
Improvement plans in IHP 435 are commonly scored on data-based diagnosis of causes, a well-formed aim, justified method selection, changes tied to causes, small-scale testing, attention to context, a complete and correctly classified measure set, display over time, a realistic timeline, scholarly support and APA 7. Strong plans read as one chain of logic in which every change answers a cause and every measure answers a question. Plans lose points when causes are guessed, when the aim lacks numbers or dates, when context is ignored or when balancing measures are missing. A Pareto analysis of causes is often credited. IHP 435 marks favor careful formatting across IHP 435 sections. IHP 435 citations keep every IHP 435 argument credible.
IHP 435 Module 7 help: the mistakes that cost points
In IHP 435, final plans commonly drop points when they list changes without linking them to causes, for aims without balancing conditions, for measure sets missing process or balancing measures and for timelines that spread everything at once. Another common gap is ignoring physician involvement and leadership support. Diagnose with data, write a complete aim, match the method, tie changes to causes, plan tests, address context and measure over time. If your project addresses a different problem, add its data to your IHP 435 notes so the plan is shaped to that problem. IHP 435 drafts start well from a IHP 435 outline. IHP 435 feedback already received guides IHP 435 revisions.
Get IHP 435 Module 7 written to your instructions
Send the IHP 435 Project Two guidelines and your problem and data. The plan will diagnose causes, write a complete aim, justify the method, tie changes to causes, address context and define a full measure set shown over time, within 24 to 48 hours, free the first time. The paper above is an original model document written by our desk, not a submitted student paper and not an official Southern New Hampshire University document.
More IHP 435 papers and related BS Healthcare Administration samples
- IHP 435 Module 1 Discussion: Three Questions Every Improvement Effort Answers
- IHP 435 Module 2 Measurement Short Paper: A Family of Measures for Emergency Department Waits
- IHP 435 Module 3 PDSA Short Paper: Why PDSA Cycles Often Fail and How to Run Them Properly
- IHP 435 Module 4 Project One: Choosing Lean for a Door-to-Provider Problem
- IHP 435 Module 5 Six Sigma Short Paper: Six Sigma for Variable Laboratory Turnaround
- IHP 435 Module 6 Data Display Short Paper: Reading Run Charts and Control Charts
- IHP 435 Module 8 Discussion: What Makes Improvement Stick
- IHP 410 Module 5 Final Project Milestone Three
- IHP 330 Module 2 Measures of Disease Frequency Paper
- IHP 200 Module 7 Project Two: A Community Walking Program for a Neighborhood Clinic
- HCM 345 Module 4 Prospective Payment Case Analysis
IHP 435 Module 7 questions, answered
Where can I find a free IHP 435 Module 7 Project Two sample?
The complete plan is published here: improving operating room first-case on-time starts from delay causes through Lean changes, context and measures.
What should a performance improvement plan include?
Problem data, root causes, an aim, a justified method, changes tied to causes, small tests, context, a full measure set and a timeline.
What causes operating room first-case delays?
Common causes include missing consents or histories, late surgeons, incomplete preoperative preparation and anesthesia or equipment issues.
What context factors affect improvement success?
Research highlights senior leadership support, supportive culture, data systems, physician involvement and strong improvement team leadership.
What is a Pareto chart?
A ranked bar chart of causes, largest first, that makes the handful driving most delays easy to spot.