IHP 640 Module 6 Milestone Two Example

Reviewed by Delia Ravenscroft, MSN, RN

This IHP 640 Module 6 Milestone Two sample analyzes a year of operating room data to find what drives delays. It is written for SNHU IHP 640 (IHP-640), the MS Healthcare Administration course on measurement, analysis and models for performance improvement. At the composite hospital's 14-room suite, 1,610 first cases started late and 13% of turnovers exceeded an hour. A control chart confirms the baseline is stable, following Mohammed, Worthington and Woodall. A Pareto analysis shows three causes, patients not ready, surgeons arriving late and incomplete anesthesia evaluations, account for 70% of late starts. Logistic and linear regression identify service changes between cases, large instrument sets and short environmental services staffing as the strongest predictors of long turnovers, with model size tested against Peduzzi and colleagues' simulation findings. Wachtel and Dexter's findings on schedule effects shape the interpretation.

CourseIHP 640 Measurement, Analysis, & Models for Performance Improvement
ModuleModule 6
Paper typegraduate milestone analyzing operational delay data
LengthAbout 1,000 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMS Healthcare Administration
UpdatedSeptember 2026

Free sample paper for IHP 640 Module 6

1

Milestone Two: What the Data Say About Delays in Highland Valley's Operating Rooms

[Student Name]

Southern New Hampshire University

IHP 640: Measurement, Analysis, & Models for Performance Improvement

Module Six Milestone Two

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe title promises findings from data rather than opinion.
2

Milestone Two: What the Data Say About Delays in Highland Valley's Operating Rooms

Milestone One recorded many suspected causes of delay, each group blaming another. This milestone tests those claims with twelve months of operating room data: 3,500 weekday first cases, of which 1,610 started late, and 8,700 turnovers between consecutive cases. It uses control charts to confirm the baseline, Pareto analysis to rank first-case delay reasons and regression to identify what predicts prolonged turnovers.

What this page is doingThe opening sets out the data and methods.
3

Confirming a Stable Baseline

Before looking for causes, it helps to know whether performance is stable or shifting. Following the tutorial by Mohammed et al. (2008), limits come from a baseline period, and any point beyond them or any unusual run marks a special cause. A p chart of the monthly first-case on-time rate, averaging 54% with about 290 first cases a month, gives limits of roughly 45% to 63%. All twelve months fell within those limits with no runs, so the problem is a stable feature of the current system rather than the result of a few bad months.

What this page is doingControl chart analysis establishes a stable baseline.
4

Coding Delay Reasons

Circulating nurses record a delay reason for every late first case from a standard list. The analyst reviewed 100 randomly chosen late cases against chart notes and found the recorded reason matched the evidence in 83%, with most mismatches recorded as other when a specific reason applied. Those were recoded before analysis.

What this page is doingData quality is checked before analysis.
5

Pareto Analysis of Late First Cases

A Pareto chart ranks causes by frequency to show where effort will pay off most. Three causes accounted for 70% of late first cases: patients not ready in preoperative holding, most often because of missing consent or history and physical documents, at 34%; surgeons arriving after the scheduled start at 22%; and incomplete anesthesia evaluations at 14%. Instrument and equipment problems, rooms not ready and transport delays together made up 24%.

Table 1. Causes of Late First Cases, Twelve Months

CauseLate casesShareCumulative share
Patient not ready (documents, consent)54734%34%
Surgeon arrived late35422%56%
Anesthesia evaluation incomplete22514%70%
Instruments or equipment17711%81%
Room not ready1137%88%
Transport976%94%
Other976%100%

Note. Composite data for 1,610 late weekday first cases.

What this page is doingPareto analysis ranks first-case delay causes.
6

Patterns by Day and Service

Late starts were more common on Mondays, 61%, than on Thursdays, 42%; a chi-square test across weekdays gave p below 0.001. Monday first cases more often involved patients whose preoperative testing was completed the previous Friday, leaving documents unfiled over the weekend. Orthopedic first cases ran late more often than other services, largely because of consent and site-marking delays.

What this page is doingSubgroup patterns point to specific process failures.
7

Why the Schedule Matters

Wachtel and Dexter (2009) showed that lateness grows as the day goes on and depends heavily on schedule construction, including whether case durations are estimated accurately. At Highland Valley, scheduled durations underestimated actual times by a median of 11 minutes for orthopedic cases, meaning later cases in those rooms started late even when the first case began on time. Improving duration estimates is therefore part of the solution.

What this page is doingResearch connects tardiness to schedule accuracy.
8

Modeling Prolonged Turnovers

To learn which turnovers become prolonged, the analyst fit a logistic regression with prolonged turnover, over 60 minutes with no scheduled gap, as the outcome. Candidate predictors were chosen in advance from staff interviews: whether the next case involved a different surgeon or service, the number of instrument sets required, whether the turnover occurred after noon, whether environmental services had fewer than three staff assigned to the suite and whether the next case was orthopedic.

What this page is doingThe modeling approach is specified in advance.
9

Is the Model Stable?

Peduzzi et al. (1996) used simulation to show that logistic models lose reliability once outcome events per predictor drop into single digits. With 1,131 prolonged turnovers and five predictors, this model has more than 200 events per predictor, well above that threshold.

What this page is doingModel stability is checked against published guidance.
10

What Predicts Long Turnovers

A change of surgeon or service between cases more than doubled the odds of a prolonged turnover. Needing more than three instrument sets and short environmental services staffing each raised the odds by about 70% to 80%. Afternoon turnovers and orthopedic next cases had smaller effects. A companion linear regression on turnover minutes, limited to turnovers under 60 minutes, found similar patterns: a service change added about 10 minutes and short environmental services staffing about 5.

Table 2. Logistic Regression of Prolonged Turnovers

PredictorOdds ratio95% CIp
Change of surgeon or service2.41.9 to 3.0<0.001
More than three instrument sets1.81.5 to 2.2<0.001
Environmental services under three staff1.71.4 to 2.1<0.001
Afternoon turnover1.51.2 to 1.8<0.001
Orthopedic next case1.41.1 to 1.70.004

Note. Composite analysis of 8,700 turnovers; 1,131 prolonged.

What this page is doingRegression results identify the strongest drivers.
11

Testing the Blame Stories

The data support some claims and refute others. Nurses' view that surgeons cause most late starts is partly supported, at 22%, but patient readiness is a larger cause. Anesthesia's view that sterile processing drives turnovers finds some support in the instrument set result, but staffing and service changes matter as much. No single department owns the problem.

What this page is doingFindings are used to replace blame with evidence.
12

Limitations

Delay reasons are recorded by nurses and may reflect their perspective; the audit reduced but did not eliminate this bias. The regression shows associations, not proof that changing a predictor will change turnover, and unmeasured factors such as case complexity may confound results. Recovery room holds were not coded in this data set and are examined in the capacity modeling paper.

What this page is doingLimitations are stated.
13

Implications for Improvement

The analysis points to four targets: getting documents and consent completed before the day of surgery, especially for Monday cases; surgeon arrival expectations; completing anesthesia evaluations in advance; and, for turnovers, grouping cases by service, preassembling instrument sets and aligning environmental services staffing with the afternoon peak. Each target has a clear owner among the departments involved, which should make accountability easier than in past efforts.

What this page is doingTargets for Milestone Three are identified.
14

Conclusion

A stable baseline, a clear Pareto pattern and consistent regression results show that Highland Valley's delays arise from a few specific, fixable process failures spread across several departments. That evidence gives the improvement plan focus and gives every group a shared picture of the problem. The next step is to design changes aimed at each target and test them on a small scale.

What this page is doingThe conclusion summarizes the analytic findings.
15

References

Mohammed, M. A., Worthington, P., & Woodall, W. H. (2008). Plotting basic control charts: Tutorial notes for healthcare practitioners. Quality and Safety in Health Care, 17(2), 137-145. https://doi.org/10.1136/qshc.2004.012047

Peduzzi, P., Concato, J., Kemper, E., Holford, T. R., & Feinstein, A. R. (1996). A simulation study of the number of events per variable in logistic regression analysis. Journal of Clinical Epidemiology, 49(12), 1373-1379. https://doi.org/10.1016/S0895-4356(96)00236-3

Wachtel, R. E., & Dexter, F. (2009). Influence of the operating room schedule on tardiness from scheduled start times. Anesthesia & Analgesia, 108(6), 1889-1901. https://doi.org/10.1213/ane.0b013e31819f9f0c

What the IHP 640 Module 6 instructions ask for

Milestone Two in IHP 640 generally asks you to analyze data on the problem you framed, using tools matched to your questions. Plan on four to six APA 7 pages. Confirm whether performance is stable, check the quality of coded data, rank causes with a Pareto analysis and use statistical tests or regression where appropriate, checking model assumptions. Present results in tables, interpret them in operational terms, compare them with what stakeholders believed and state the limitations before naming improvement targets. IHP 640 graders notice clean headings in IHP 640 papers. IHP 640 names and dates need checking before IHP 640 submission. IHP 640 prompts vary by term, so recheck IHP 640 directions. Use tables for each analysis so graders can check your numbers.

How this IHP 640 Module 6 milestone two example is built

This milestone analyzes a year of data from a composite 14-room surgical suite. A p chart following Mohammed, Worthington and Woodall confirms a stable baseline, and a Pareto table shows three causes behind 70% of late first cases. Logistic regression, checked against Peduzzi and colleagues' events-per-variable guidance, finds service changes, large instrument sets and short environmental services staffing predict prolonged turnovers. Wachtel and Dexter link tardiness to schedule accuracy, and four improvement targets close the milestone. IHP 640 students can reuse this structure for IHP 640 work. IHP 640 claims here trace to cited IHP 640 sources. IHP 640 readers can adapt each section to IHP 640 data. The limitations of coded delay reasons are acknowledged.

Where the IHP 640 Module 6 rubric puts the points

Data analysis milestones in IHP 640 are typically evaluated on appropriate methods for each question, checks of data quality and baseline stability, correct statistical work, clear tables, operational interpretation, honest limitations, scholarly support and APA 7. The best submissions pre-specify predictors, check model stability and use results to replace assumptions with evidence. Marks fall when a tool is applied without explaining why, when statistical output is presented without interpretation or when correlation is treated as proof. IHP 640 marks favor careful formatting across IHP 640 sections. IHP 640 citations keep every IHP 640 argument credible. IHP 640 instructors weigh evidence heavily in IHP 640 grading. Confidence intervals beside odds ratios are expected.

IHP 640 Module 6 help: the mistakes that cost points

Analysis milestones in this course often jump to regression without first checking stability or data quality, report p-values without effect sizes and never translate results into operational meaning. Another common gap is choosing predictors after seeing the data. Confirm the baseline, audit the data, use Pareto analysis for causes, pre-specify and check models and explain what each finding means for the process. Share your data and the IHP 640 prompt so the analysis fits your project. IHP 640 drafts start well from a IHP 640 outline. IHP 640 feedback already received guides IHP 640 revisions. IHP 640 rubrics posted in Brightspace clarify IHP 640 expectations. Keep a short appendix of variable definitions.

Get IHP 640 Module 6 written to your instructions

Send the IHP 640 Milestone Two prompt and your data. The milestone will confirm baseline stability, audit data quality, rank causes with a Pareto analysis, fit and check regression models and translate results into improvement targets, 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 640 papers and related MS Healthcare Administration samples

IHP 640 Module 6 questions, answered

Where can I find a free IHP 640 Module 6 Milestone Two sample?

IHP 640 Module 6 is written out in full as a Pareto analysis of first-case delays and regression models of prolonged operating room turnovers.

What does a Pareto analysis show?

It ranks causes by frequency and shows the cumulative share, highlighting the few causes that account for most of a problem.

Why check baseline stability before analyzing causes?

A stable baseline shows the problem is built into the current system, while shifts may point to specific events.

When should I use logistic regression?

When the outcome is yes or no, such as whether a turnover exceeds 60 minutes, and you want to estimate the effect of several predictors.

How large a sample does a turnover model need?

Enough outcome events for each predictor; with over 1,100 prolonged turnovers and five predictors, this model is comfortably large.