IHP 645 Module 6 Milestone Two Example

Reviewed by Delia Ravenscroft, MSN, RN

This IHP 645 Module 6 Milestone Two sample presents a root cause analysis of a sentinel event in which a patient's deterioration went unrescued. It is written for SNHU IHP 645 (IHP-645), the MS Healthcare Administration course on regulatory compliance, accreditation and patient safety culture. At the composite 240-bed hospital, a man recovering from bowel surgery showed rising heart rate, falling blood pressure and confusion for six hours before a rapid response was called; he died two days later. The analysis rebuilds the timeline, finds causes in vital sign monitoring, an unwritten escalation rule, night staffing and resident coverage and ranks corrective actions by strength. Ghaferi and colleagues showed that failure to rescue drives differences in surgical mortality, Chan and colleagues found rapid response teams cut arrests outside intensive care and Peerally and colleagues warn against analyses that end in weak actions.

CourseIHP 645 Regulatory Compliance, Accreditation and Promoting a Patient Safety Culture
ModuleModule 6
Paper typegraduate milestone presenting a root cause analysis
LengthAbout 1,120 words, 7 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramMS Healthcare Administration
UpdatedSeptember 2026

Free sample paper for IHP 645 Module 6

1

Milestone Two: Six Hours on 4 West, a Root Cause Analysis

[Student Name]

Southern New Hampshire University

IHP 645: Regulatory Compliance, Accreditation and Promoting a Patient Safety Culture

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 names the window of missed opportunity at the center of the analysis.
2

Milestone Two: Six Hours on 4 West, a Root Cause Analysis

Milestone One found that Pinecrest Regional Medical Center's analysis of a recent sentinel event was incomplete. This milestone completes it. It describes the event, the team and methods, the timeline, the causes identified and the actions proposed, ranked by their likely strength, with measures to show whether they work.

What this page is doingThe opening explains the milestone's purpose.
3

The Event

A 68-year-old man was admitted to 4 West after an elective bowel resection. On his second night, beginning around 11:00 p.m., his heart rate rose from 92 to 128, his blood pressure fell from 124/76 to 94/58, his breathing quickened and he became confused. The nurse paged the covering surgical resident at 1:10 a.m. and again at 3:40 a.m. and was advised to give fluids and continue monitoring. A rapid response was called at 5:05 a.m. when he became unresponsive. He was found to have an anastomotic leak with septic shock, was transferred to intensive care and died two days later.

What this page is doingThe event is described factually without blame.
4

Why Failure to Rescue Matters

Ghaferi et al. (2009) compared hospitals with high and low mortality after major surgery and found that complication rates were similar; the difference lay in failure to rescue, the rate of death after a complication occurred. High-mortality hospitals were less successful at recognizing and responding to complications. This event fits that pattern exactly: the complication itself was not preventable with certainty, but the delay in recognizing and treating it was.

What this page is doingResearch frames the event as a rescue failure.
5

Team and Methods

The review team included a surgeon and a nurse from another unit, a hospitalist, a pharmacist, a patient safety specialist and a former patient advisor, with no one directly involved in the event. The team interviewed eight staff, reviewed the record and monitor data, walked the unit at night and built a cause-and-effect diagram, asking repeatedly why each step happened as it did. Its charter was to find system causes, not to judge individuals.

What this page is doingThe team's composition and methods are described.
6

Timeline

The timeline shows four missed opportunities: vital signs at 11:00 p.m. that met sepsis screening criteria but were not scored, a first page at 1:10 a.m. that did not prompt a bedside evaluation, a second page at 3:40 a.m. that again resulted in phone advice and a period between 3:40 and 5:05 a.m. in which the nurse, caring for six patients, considered but did not call a rapid response.

Table 1. Timeline of the Event

TimeObservation or actionMissed opportunity
11:00 p.m.Heart rate 118, systolic 102, new confusion documentedNo early warning score; sepsis screen not triggered
1:10 a.m.Nurse pages resident; fluids ordered by phoneNo bedside evaluation
3:40 a.m.Heart rate 128, systolic 94; second pagePhone advice again; no escalation to attending
3:40-5:05 a.m.Nurse caring for six patients; considers rapid responseUnwritten approval rule discourages call
5:05 a.m.Patient unresponsive; rapid response calledRescue begins about six hours after first signs

Note. Composite reconstruction from records, monitor data and interviews.

What this page is doingMissed opportunities are identified.
7

Cause One: Monitoring Without Scoring

4 West recorded vital signs every four hours but had no early warning score to combine them into a single signal of risk, and the electronic record's sepsis screen was not active on surgical units. Each abnormal value was noticed, but no system translated the pattern into a mandatory response.

What this page is doingThe first system cause is described.
8

Cause Two: An Escalation Culture

Hospital policy allows anyone to call a rapid response, but interviews revealed an unwritten expectation on 4 West that nurses first obtain physician agreement. Two nurses described being criticized for calling without approval. The culture survey's 32% positive safety climate on 4 West reflects this pattern.

What this page is doingThe second cause reflects culture.
9

Cause Three: Night Staffing and Coverage

The nurse cared for six patients, above the unit's target of five, because of a call-out. One surgical resident covered three floors and about 110 patients overnight and was managing an emergency admission during both pages. There was no expectation that residents evaluate patients at the bedside after a second call about the same concern, and no clear route for escalating to the attending surgeon.

What this page is doingThe third cause concerns workload and coverage.
10

What Rapid Response Teams Can and Cannot Do

Chan et al. (2010) reviewed studies of rapid response teams and found that they were associated with a reduction in cardiopulmonary arrests outside intensive care units in adults, but not with a significant reduction in overall hospital mortality. Rapid response teams help only when they are called early. Pinecrest's team was available and effective once summoned; the failure lay upstream, in recognizing deterioration and triggering the call.

What this page is doingEvidence shows why earlier triggering matters.
11

Root Cause Statements

The team agreed on three root cause statements. The absence of an early warning score with mandatory triggers allowed a deteriorating pattern to go without a required response. An unwritten norm requiring physician approval delayed rapid response activation. Overnight resident coverage and nurse assignments left no one with the time and authority to evaluate the patient at the bedside.

What this page is doingRoot causes are stated in system terms.
12

Ranking the Actions

Peerally et al. (2017) argued that root cause analyses in health care often produce weak actions, such as reminders and retraining, fail to follow up and can drift toward blame. The team therefore ranked actions by strength. Stronger actions change systems, such as automated triggers; intermediate actions standardize processes or add resources; weaker actions rely on education and policy alone.

What this page is doingActions are ranked to avoid a common weakness.
13

Corrective Actions

The strongest action is an automated early warning score in the electronic record that pages the rapid response team directly when a threshold is crossed, without requiring nurse or physician approval. Intermediate actions include a rule that a second call about the same concern requires a bedside evaluation within thirty minutes or escalation to the attending, a night nurse float to protect assignments from call-outs and adding a second overnight surgical provider. Weaker, supporting actions include written reaffirmation that anyone may call a rapid response and simulation training on recognizing sepsis.

Table 2. Corrective Actions Ranked by Strength

ActionStrengthOwnerDue
Automated early warning score with direct rapid response pagingStrongerChief nursing informatics officer90 days
Bedside evaluation or attending escalation after second callIntermediateChief of surgery30 days
Night float nurse to cover call-outsIntermediateChief nursing officer60 days
Second overnight surgical providerIntermediateChief medical officer6 months
Reaffirm open rapid response policy; sepsis simulationWeaker (supporting)Patient safety officer30 days

Note. Composite action plan approved by the quality committee.

What this page is doingActions are specified by strength.
14

Measures

Outcome measures are failure-to-rescue deaths after surgery and cardiac arrests outside intensive care. Process measures are time from first early warning trigger to rapid response evaluation, the rate of rapid response activations on surgical floors and the share of second calls followed by bedside evaluation. The review team will report at 90 days and six months.

What this page is doingMeasures follow the actions.
15

Conclusion

The patient's death followed a complication that could not be fully prevented but was recognized far too late. The causes lay in monitoring without scoring, a culture that delayed escalation and coverage stretched too thin. Actions that change systems, backed by measures and follow-up, give Pinecrest its best chance of rescuing the next patient.

What this page is doingThe conclusion restates causes and remedies.
16

References

Chan, P. S., Jain, R., Nallmothu, B. K., Berg, R. A., & Sasson, C. (2010). Rapid response teams: A systematic review and meta-analysis. Archives of Internal Medicine, 170(1), 18-26. https://doi.org/10.1001/archinternmed.2009.424

Ghaferi, A. A., Birkmeyer, J. D., & Dimick, J. B. (2009). Variation in hospital mortality associated with inpatient surgery. New England Journal of Medicine, 361(14), 1368-1375. https://doi.org/10.1056/NEJMsa0903048

Peerally, M. F., Carr, S., Waring, J., & Dixon-Woods, M. (2017). The problem with root cause analysis. BMJ Quality & Safety, 26(5), 417-422. https://doi.org/10.1136/bmjqs-2016-005511

What the IHP 645 Module 6 instructions ask for

Milestone Two in IHP 645 generally asks you to analyze a sentinel event or serious safety problem using root cause analysis. Plan on four to six APA 7 pages. Describe the event factually, explain the team and methods, build a timeline that identifies missed opportunities and trace causes to systems rather than individuals. Write clear root cause statements, rank corrective actions by strength with owners and due dates and define measures that will show whether the actions work. IHP 645 graders notice clean headings in IHP 645 papers. IHP 645 names and dates need checking before IHP 645 submission. IHP 645 prompts vary by term, so recheck IHP 645 directions. Include a patient or family perspective where possible.

How this IHP 645 Module 6 milestone two example is built

This milestone analyzes a composite hospital's failure-to-rescue death after bowel surgery. A timeline table shows four missed opportunities over six hours, and causes are traced to monitoring without scoring, an unwritten escalation rule and stretched night coverage. Ghaferi, Birkmeyer and Dimick frame failure to rescue, Chan and colleagues explain rapid response limits and Peerally and colleagues guide the ranking of actions, led by automated early warning paging. IHP 645 students can reuse this structure for IHP 645 work. IHP 645 claims here trace to cited IHP 645 sources. IHP 645 readers can adapt each section to IHP 645 data. Measures and follow-up dates close the milestone.

Where the IHP 645 Module 6 rubric puts the points

Root cause milestones in IHP 645 are usually evaluated on factual event description, a credible team and method, a clear timeline, causes traced to systems, precise root cause statements, actions ranked by strength with owners and deadlines, meaningful measures, scholarly support and APA 7. Stronger analyses avoid blame, rely on system-level actions and plan follow-up. Marks are lost when the root cause is a person, when actions are mostly education or when no one is responsible for follow-up. IHP 645 marks favor careful formatting across IHP 645 sections. IHP 645 citations keep every IHP 645 argument credible. IHP 645 instructors weigh evidence heavily in IHP 645 grading. Clear timelines that show each missed opportunity are valued.

IHP 645 Module 6 help: the mistakes that cost points

Root cause analyses in this course often stop at human error, list retraining as the main fix and skip measures or follow-up. Another frequent gap is a team made up of people involved in the event. Describe the event without blame, build a timeline, keep asking why until you reach systems, write root cause statements, rank actions by strength and name owners and measures. Send a stripped-down account of the event, with names and dates removed, along with the IHP 645 instructions. IHP 645 drafts start well from a IHP 645 outline. IHP 645 feedback already received guides IHP 645 revisions. IHP 645 rubrics posted in Brightspace clarify IHP 645 expectations.

Get IHP 645 Module 6 written to your instructions

Send the IHP 645 Milestone Two prompt and a de-identified description of the event. The milestone will build a timeline, trace system causes, write root cause statements, rank actions by strength and define measures, 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 645 papers and related MS Healthcare Administration samples

IHP 645 Module 6 questions, answered

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

The whole IHP 645 Module 6 analysis can be read on this page: a failure-to-rescue death traced through a timeline to system causes and ranked corrective actions.

What is failure to rescue?

Death after a complication that might have been survived with timely recognition and treatment.

Do rapid response teams reduce hospital deaths?

A meta-analysis found fewer cardiac arrests outside intensive care but no significant drop in overall hospital mortality.

What makes a corrective action strong?

It changes the system, such as automation or forcing functions, rather than relying on training or reminders.

Who should be on a root cause analysis team?

People with relevant expertise who were not directly involved, often including a patient or family advisor.