IHP 315 Module 4 Project One Example

Reviewed by Delia Ravenscroft, MSN, RN

This IHP 315 Module 4 Project One sample shows how to analyze a real kind of adverse event in systems language rather than blame language. It is written for SNHU IHP 315 (IHP-315), part of the BS Healthcare Administration program. At a composite community hospital, a 72-year-old woman received a heparin infusion at nearly twice the intended rate because her weight was recorded as 176 kilograms when she weighed 176 pounds, and she developed bleeding. The analysis reconstructs the event, then uses the SEIPS model from Carayon and colleagues to sort contributing factors across people, tasks, technology, environment and organization. Reason's distinction between active failures and latent conditions shows why several defenses failed together. Wu and colleagues' critique of root cause analysis warns against ending with retraining, so the paper ranks actions by strength and assigns owners and measures.

CourseIHP 315 Patient Safety Systems and Strategies
ModuleModule 4
Paper typeproject one adverse event analysis
LengthAbout 1,080 words, 6 pages
FormatAPA 7 student paper
SchoolSouthern New Hampshire University
ProgramBS Healthcare Administration
UpdatedSeptember 2026

Free sample paper for IHP 315 Module 4

1

Project One: Analysis of a Weight-Entry Heparin Dosing Error

[Student Name]

Southern New Hampshire University

IHP 315: Patient Safety Systems and Strategies

Project One

[Instructor Name]

[Date]

What this page is doingThe title names the event precisely, since the analysis depends on its specifics.
2

Project One: Analysis of a Weight-Entry Heparin Dosing Error

Heparin is a high-alert medication: when it is dosed wrongly, patients can bleed or clot with serious consequences. This project analyzes an event at Maple Grove, a composite community hospital, in which a heparin infusion started at nearly double the intended dose. The patient recovered, but the event exposed weaknesses at almost every step between admission and the infusion pump. The analysis reconstructs what happened, identifies contributing factors using a work system model, explains how the defenses failed and recommends actions ranked by their likely effectiveness. Names and details are changed.

What this page is doingThe introduction explains why heparin events matter and previews the analysis.
3

What Happened

A 72-year-old woman arrived in the emergency department on a busy Saturday evening with a blood clot in her leg. She could not stand on the department's scale, so the triage nurse asked her weight, and she said 176. The nurse typed 176 into the weight field, which accepted either pounds or kilograms depending on a drop-down menu that defaulted to kilograms. The physician ordered a weight-based heparin protocol, and the electronic record calculated a bolus and infusion rate for a 176-kilogram patient, about 80 kilograms more than her real weight of roughly 80 kilograms.

The pharmacist on duty, covering the emergency department and three inpatient units, verified the order. The dose was within the protocol's calculated range for the recorded weight, so no alert fired. On the medical unit, two nurses completed the required independent double check, comparing the pump settings with the order, which matched. The pump was run in basic mode rather than with its drug library because the library entry for heparin had been updated and nurses were unsure of the new profile. Six hours later, the patient's clotting test came back far above target, and she had blood in her urine. The infusion was stopped, the error discovered and the patient monitored. She recovered without lasting harm.

What this page is doingThe event is reconstructed step by step without assigning blame.
4

Contributing Factors: A Work System View

The SEIPS model of Carayon et al. (2006) was built to help health care organizations see how the parts of a work system, the people, the tasks, the tools and technology, the physical environment and the organization, interact to shape care processes and outcomes. Applied to this event, the model shows that no single factor caused the harm. The patient could not use the standing scale, and no bed or chair scale was available. The triage task required a weight quickly, under pressure. The electronic record allowed either unit, defaulted to kilograms and had no warning for an implausible weight. The pharmacist's dose check relied on the recorded weight, so a wrong weight produced a correct-looking dose. Nurses checked the pump against the order but never checked the order against the patient. The pump's safety library was bypassed. And the organization had staffed one pharmacist for four areas on a weekend evening.

Table 1. Contributing Factors by Work System Element

ElementContributing factor
PersonPatient unable to stand; weight stated rather than measured
TaskWeight needed quickly during busy triage
TechnologyWeight field accepts pounds or kilograms, defaults to kilograms, no plausibility alert; pump library bypassed
EnvironmentNo bed or chair scale in the emergency department
OrganizationOne pharmacist covering four areas; double-check policy compares pump to order only

Note. Factors are drawn from interviews and record review.

What this page is doingThe SEIPS model organizes contributing factors across the work system.
5

How the Defenses Failed

Reason (2000) described safety defenses as layers, each with weaknesses, and argued that harm occurs when those weaknesses line up. He contrasted the slips people make at the point of care with deeper flaws planted by earlier design and management choices, flaws that can lie dormant until an active failure exposes them. In this event, the active failure was entering 176 without switching the unit. Every other layer, the dose check, pharmacist verification, double check and smart pump, should have caught it, and each failed because of a latent condition: a check that trusted the weight, a double check aimed at the wrong comparison and a safety library that staff avoided. Blaming the triage nurse would leave all of those conditions in place for the next patient.

What this page is doingReason's model explains how multiple defenses failed together.
6

Avoiding Weak Fixes

Wu et al. (2008) reviewed how root cause analysis is used in medicine and found little evidence that it reliably prevents recurrence. They noted that analyses often end with weak actions, such as reminders, education and new policies, that depend on people remembering to do better, and that recommendations frequently go unimplemented. They urged organizations to favor stronger actions that change systems and to track whether actions are completed and effective. This analysis therefore ranks recommendations by strength, preferring forcing functions and standardization over training.

What this page is doingThe critique of root cause analysis shapes how recommendations are chosen.
7

Recommendations Ranked by Strength

Top-ranked actions make the slip nearly impossible to repeat. The record should accept weights only in kilograms throughout the hospital, with a hard stop requiring confirmation for adult weights above 150 kilograms or below 35. The smart pump drug library should be mandatory for heparin, with the basic mode locked for high-alert drugs. Moderate actions standardize and simplify: bed and chair scales should be placed in the emergency department so weights are measured rather than stated, and the double-check form should require comparing the order's weight with the patient's measured weight. Weaker but still useful actions include a pharmacist workload review for weekend evenings and brief education on the updated heparin library.

Each action has an owner. Informatics owns the weight field change within sixty days, pharmacy owns the pump library lock within thirty, the emergency department manager owns scale purchase and nursing education owns the revised double-check form.

Table 2. Actions, Strength and Owners

ActionStrengthOwner
Kilogram-only weight entry with plausibility hard stopStrongInformatics
Mandatory pump library for heparinStrongPharmacy
Bed and chair scales in emergency departmentModerateEmergency department manager
Double check includes weight verificationModerateNursing education
Weekend pharmacist workload reviewWeakerPharmacy director

Note. Strength reflects how little each action depends on memory or vigilance.

What this page is doingActions are ranked by strength, and each is given an owner and deadline.
8

Measuring Whether Actions Work

The patient safety office will track completion of each action by its deadline. Afterward, informatics will report monthly how often the weight hard stop fires and how often weights are corrected, pharmacy will report the share of heparin infusions run through the drug library, targeting 100%, and the emergency department will audit twenty records a month for measured versus stated weights. Any heparin dosing error will receive rapid review to see whether it slipped past the new defenses.

What this page is doingMeasures track both completion and effectiveness of actions.
9

Conclusion

A single typing slip passed through four defenses because each was built with a hidden weakness. Retelling the event as a system story shows that the fixes belong to informatics, pharmacy, equipment and policy, not to one nurse, and ranking actions by strength gives the hospital a better chance of preventing the next event.

What this page is doingThe conclusion restates the system story and the value of strong actions.
10

References

Carayon, P., Schoofs Hundt, A., Karsh, B.-T., Gurses, A. P., Alvarado, C. J., Smith, M., & Flatley Brennan, P. (2006). Work system design for patient safety: The SEIPS model. Quality and Safety in Health Care, 15(Suppl. 1), i50-i58. https://doi.org/10.1136/qshc.2005.015842

Reason, J. (2000). Human error: Models and management. BMJ, 320(7237), 768-770. https://doi.org/10.1136/bmj.320.7237.768

Wu, A. W., Lipshutz, A. K. M., & Pronovost, P. J. (2008). Effectiveness and efficiency of root cause analysis in medicine. JAMA, 299(6), 685-687. https://doi.org/10.1001/jama.299.6.685

What the IHP 315 Module 4 instructions ask for

Project One in IHP 315 usually asks you to analyze an adverse event, either a case your instructor provides or a published one you choose. Expect to reconstruct the event, identify contributing factors, explain how safety defenses failed and recommend prevention strategies, in roughly four to six pages in APA 7 with scholarly sources. Tell the story neutrally, then organize causes with a model such as SEIPS or a fishbone diagram. Separate frontline actions from the latent conditions behind them, rank your recommendations by strength and give each one an owner and a way to measure whether it worked. Keep the event narrative brief so the analysis has room. Protect identities throughout.

How this IHP 315 Module 4 project one example is built

This project analyzes a heparin infusion started at nearly double the intended dose after a patient's weight of 176 pounds was entered as 176 kilograms. The Carayon SEIPS model sorts contributing factors, from a patient who could not stand on the scale to a weight field that defaulted to kilograms, a double check aimed at the wrong comparison and a bypassed pump library. Reason's model explains how four defenses failed together. Wu and colleagues' critique of root cause analysis leads to recommendations ranked by strength, led by kilogram-only entry with a hard stop and a mandatory pump library, each with an owner, deadline and measure. The patient recovered, and the paper says so plainly.

Where the IHP 315 Module 4 rubric puts the points

Adverse event analyses in IHP 315 are generally graded on an accurate, neutral reconstruction of the event, identification of contributing factors at the system level, application of safety concepts, the strength and feasibility of recommendations, measures of effectiveness, scholarly support and APA 7. Strong papers use a model to organize causes, explain why each defense failed and prefer forcing functions and standardization over education. Papers lose points when the narrative dominates, when the analysis stops at the person who made the error or when recommendations are limited to retraining and reminders. Owners and deadlines make recommendations believable and are often decisive for the top grade. A table of actions by strength helps.

IHP 315 Module 4 help: the mistakes that cost points

In IHP 315, Project One often loses points for blame-centered conclusions, for long retellings with short analysis, for weak actions and for no plan to measure results. Another common gap is naming contributing factors without explaining how each let the error through. Keep the story tight, use a model to find system causes, trace each defense's failure, rank actions by strength and attach owners and measures. If your instructor assigned a specific event or wants a particular template, such as a fishbone diagram, include it in your IHP 315 notes and the analysis will follow it. Send the event summary if you have one, and we will work from it.

Get IHP 315 Module 4 written to your instructions

Send the IHP 315 Project One guidelines and the event you are analyzing. The paper will reconstruct the event neutrally, organize contributing factors with a model, explain each failed defense and rank recommendations by strength with owners and 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 315 papers and related BS Healthcare Administration samples

IHP 315 Module 4 questions, answered

Where can I find a free IHP 315 Module 4 Project One sample?

The whole analysis is available here: a heparin dosing error traced through system factors and failed defenses, with ranked actions and owners.

How do I analyze an adverse event for IHP 315?

Reconstruct the event neutrally, organize contributing factors with a model, explain how each defense failed and recommend strong, measurable system fixes.

How do frontline slips differ from hidden system flaws?

Active failures are frontline slips or mistakes; latent conditions are hidden weaknesses in design, staffing or policy that let those slips cause harm.

What makes a prevention strategy strong?

It changes the system so the error is hard or impossible to make, such as a hard stop or forcing function, rather than relying on memory.

Why is root cause analysis criticized?

Reviews find it often ends with weak actions like retraining, and recommendations are frequently not implemented or measured.