| Course | BHA FPX 3004 Ensuring Patient Safety and Quality Improvement in Healthcare |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Root cause analysis |
| Length | About 1,100 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Health Care Administration |
| Updated | September 2026 |
Free sample paper for BHA FPX 3004 Assessment 1
Root Cause Analysis of a Heparin Infusion Overdose: The Timeline, Contributing Factors by Category, the Root Cause Defended, and Prevention Ranked by Strength
Student Name
Capella University
BHA FPX 3004: Ensuring Patient Safety and Quality Improvement in Healthcare
Instructor Name
Month Day, Year
The Event Told as a Timeline
The event is a composite case set at Parkview Hospital, a composite community hospital with 250 beds. A 72-year-old patient was admitted with a blood clot in the leg and was started on a weight-based heparin infusion. The timeline was reconstructed from the record, the infusion pump log, and interviews. Day 1, 14:10. Physician orders heparin by the hospital's weight-based protocol: bolus, then infusion at 18 units per kilogram per hour. Patient's weight recorded as 82 kilograms. 14:40. Pharmacy verifies the order and dispenses a premixed bag of heparin, 25,000 units in 250 milliliters. 15:05. Nurse programs the infusion pump. The pump's drug library includes heparin, but the nurse selects the "basic infusion" mode, which bypasses the library's dose limits, and enters the rate in milliliters per hour. The nurse calculates 1,476 units per hour, which at 100 units per milliliter is 14.8 milliliters per hour, but enters 148 milliliters per hour. 15:05 to 19:00. The infusion runs at ten times the intended rate. 18:30. A scheduled laboratory test shows a clotting time far above the target range. 19:00. The nurse receives the result, stops the infusion, and notifies the physician. The patient is monitored closely, receives a reversal agent, and has no lasting harm. Telling the event as a timeline shows not only what went wrong but when opportunities to catch it were missed.
Contributing Factors Sorted Into Categories
Vincent et al. (1998) proposed a framework that sorts factors contributing to clinical incidents into categories: patient, task and technology, individual staff, team, work environment, and organizational factors. Using it prevents the analysis from stopping at the individual. Patient factors: none significant; the patient's weight and condition were standard for the protocol. Task and technology factors: the pump allowed the nurse to bypass the drug library using basic mode; the rate was entered in milliliters per hour rather than as a dose; no independent double check of the programming was required for heparin at Parkview. Individual factors: the nurse was experienced but had worked three consecutive 12-hour shifts; the calculation was correct but the entry had a misplaced decimal. Team factors: the charge nurse was covering two patients herself and was unavailable to double-check; the handoff at 19:00 did not include a check of infusion rates against orders. Work environment factors: the unit was at full census with one nurse absent; the medication room was interrupted repeatedly. Organizational factors: drug library compliance had been reported at 71% hospital-wide for months without action; the high-alert medication policy did not require independent double checks for heparin, although it did for insulin. Sorting factors into categories reveals that the nurse's error happened inside a system that made it easy to make and hard to catch.
Working Past the Individual Error
It would be easy to conclude that the nurse made a calculation error and should be retrained. But the nurse's calculation was correct; the error was in entry, a type of slip that even careful, experienced people make, particularly when tired and interrupted. The more useful question is why a slip of this kind reached the patient. The answer lies in the system: the pump allowed bypassing its safety limits, no second person checked the programming, and the problem with drug library use had been known without action. The National Patient Safety Foundation (2015) emphasized that root cause analyses should focus on system vulnerabilities rather than individual blame, because blaming individuals leaves the same hazards in place for the next person.
The Root Cause Defended Against Rivals
The root cause is that infusion pumps at Parkview could be programmed for heparin without the drug library's dose limits, and nothing in the process required or verified library use. Two rival explanations were considered. The first is staffing: the nurse was tired and the unit short-staffed. Staffing contributed but is not the root cause, because a similar slip could occur on a fully staffed unit, and the drug library would have caught it regardless of staffing. The second rival is the lack of an independent double check. A double check would likely have caught the error, but double checks are less reliable than technology that enforces limits, since the second person may see what they expect to see. The drug library is the stronger point of prevention, which is why it is named as the root cause, with the missing double check as a contributing factor.
Prevention Ranked by Strength of Action
The action hierarchy used in patient safety ranks actions from stronger, those that change the system so that errors are prevented regardless of human performance, to weaker, those that rely on people remembering or following rules (National Patient Safety Foundation, 2015). Stronger actions: configure pumps so that heparin cannot be run in basic mode, forcing use of the drug library with hard dose limits; integrate pumps with the electronic record so that the ordered dose is sent to the pump, eliminating manual entry. Intermediate actions: require independent double checks for heparin infusions at initiation and rate changes; add infusion rate checks to shift handoff; reduce interruptions in the medication room with a no-interruption zone. Weaker actions: retrain nurses on pump programming; send a safety alert about the event. Parkview should implement the stronger actions first, supported by intermediate actions while pump configuration and integration are completed. Weaker actions may be used but should not be relied on alone. Ranking actions by strength directs resources to changes that make the error impossible rather than to reminders that depend on memory.
Measuring Whether Prevention Works
The hospital should measure drug library compliance weekly on each unit, with a target of at least 95%, and track the percentage of heparin infusions started with an independent double check. Pump logs will show whether basic mode is ever used for heparin after the configuration change. Heparin-related events and near misses will be reviewed by the medication safety committee monthly for a year.
Conclusion
The heparin overdose, told as a timeline, resulted from a slip in pump programming that reached the patient because pumps could bypass their safety limits and no process verified their use. Sorting factors into categories and testing rival explanations identifies the pump configuration as the root cause, and prevention actions are ranked by strength, with forced drug library use and pump integration first.
References
National Patient Safety Foundation. (2015). RCA2: Improving root cause analyses and actions to prevent harm.
Vincent, C., Taylor-Adams, S., & Stanhope, N. (1998). Framework for analysing risk and safety in clinical medicine. BMJ, 316(7138), 1154-1157. https://doi.org/10.1136/bmj.316.7138.1154
The Capella BHA FPX 3004 Assessment 1 instructions
BHA FPX 3004 opens with an investigation: a root cause analysis of one patient safety event. You describe the event in sequence, apply an analysis method such as the five whys or a fishbone diagram, identify contributing factors across categories like people, process, equipment and environment, determine the root cause, recommend prevention actions and explain how their effect would be measured. The event can be a composite or drawn from published cases. The analysis should look for system causes rather than individual blame. The Joint Commission's RCA2 guidance and the action hierarchy from the VA National Center for Patient Safety are useful sources. The event usually carries into the improvement plan and evaluation plan that follow.
Inside the BHA FPX 3004 Assessment 1 example
The example separates what happened from why it happened, and keeps them apart on the page. Section one is the event: a sequence with times and roles, written so a reader could reconstruct it without the analysis. Section two applies an analysis method by name, five whys carried to an actual system answer or a cause and effect breakdown across people, process, equipment, environment and policy, with each branch populated rather than listed. Section three states the root cause in one sentence and defends it against the two contributing factors that came closest. Section four proposes what would prevent recurrence, ranked by whether it removes the condition or merely reminds staff about it. Evidence from safety literature attaches to the mechanism being claimed. Headings mirror the criteria language so each one can be scored where it sits.
Reading the BHA FPX 3004 Assessment 1 scoring guide
Capella's scoring guide rates the event description, the analysis method, the contributing factors, the root cause, the prevention actions and the measurement. The event reaches Distinguished when told as a timeline with times and roles, separate from the analysis. The method scores higher when named and applied visibly. Contributing factors earn credit when sorted into categories. The root cause criterion rewards working past the individual error to a system cause and defending it against rival explanations. Prevention actions score highest when ranked by strength, since forcing functions such as pump drug library hard limits are stronger than retraining. Measurement shows follow-through. Writing and APA are graded.
BHA FPX 3004 Assessment 1 help from the desk
Students often stop at the individual error, such as the nurse programmed the pump wrong, which leaves the analysis unfinished in the eyes of the scoring guide. Another common mistake is mixing the event description with the analysis. The method is named but not shown. Contributing factors are listed without categories. Several root causes are named without choosing or defending one. Prevention relies on education and policy reminders, which are weak actions. Measures are missing. Using the action hierarchy to rank prevention steps shows faculty you understand which fixes actually hold.
Get a BHA FPX 3004 Assessment 1 example written to your instructions
Send the instructions and the scoring guide for BHA FPX 3004 Assessment 1 from your courseroom, with the event your section assigns or the one you plan to use. A custom example comes back in 24 to 48 hours, written to those criteria, with the timeline, the factor analysis and a system level root cause. The first one is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More BHA FPX 3004 papers and BS in Health Care Administration samples
- BHA FPX 3004 Assessment 2: Improvement Plan
- BHA FPX 3004 Assessment 3: Quality Evaluation Plan
- BHA FPX 3008 Assessment 1: Budget Analysis
- BHA FPX 3001 Assessment 1: System Analysis
- BHA FPX 3009 Assessment 1: Reimbursement Model Analysis
- BHA FPX 2110 Assessment 1: Process Analysis
BHA FPX 3004 Assessment 1 questions, answered
What kind of event should I analyze for Assessment 1?
One with a sequence you can lay out and system conditions worth naming. Medication administration errors, patient falls, wrong site procedures, specimen labeling failures and handoff communication breakdowns all work because each has documented contributing factors in the safety literature. Avoid events that reduce to one person deciding badly, since the analysis then has nowhere to go.
Can I use a real event from my workplace?
Only with the identifying details removed, and most sections say so explicitly. Describe roles instead of names, give the unit type rather than the facility, and shift dates. The example uses a described event for that reason. A published sentinel event summary or a case from an agency safety database is the safer route if your event is recent or still under review.
Should I use five whys or a fishbone diagram?
Either is accepted in most sections, and the choice matters less than finishing it. Five whys suits a single chain running back to one condition. A cause and effect breakdown suits an event with several independent factors that combined on the night. The example fills every branch it opens, since a partly populated diagram costs more marks than the method earns.
Where can I find a free BHA FPX 3004 Assessment 1 sample paper?
This page holds the full heparin overdose root cause analysis, with the timeline, categorized factors, the defended root cause and ranked prevention. A custom analysis is available free.
Which root cause method should I use for BHA FPX 3004 Assessment 1?
The five whys and the fishbone diagram are common. Show the method visibly, sort factors into categories and keep asking why until you reach a system cause the organization can change.