Root Cause Troubleshooting Basics

How to move past the first obvious failure, identify what actually caused it, and avoid fixing the same medical equipment problem over and over

A device comes into the shop with a blown fuse.

Published September 2, 2026 · Revised September 6, 2026

Back to Biomed Basics

What This Page Explains

This page covers:

The Simple Version

Separate three questions: what happened, what failed, and why it failed. The observed behavior is the symptom. The failed component or condition may be the immediate cause. The root cause is the underlying condition that produced that failure and, when corrected, should prevent the same problem from recurring for the same reason.

If a device will not power on because its internal fuse is open, replacing the fuse addresses only the immediate interruption. A shorted switching component, pinched cable, liquid intrusion, or overloaded output may have caused the excessive current. Evidence determines how far the investigation should go; not every isolated age-related failure needs a grand theory, but repeated or safety-relevant failures deserve a deeper look.

Worked Example: The Same Fuse Opens Again

If a replacement fuse opens during the same startup stage, stop replacing fuses and map what becomes energized at that moment. Inspect for damage and contamination, isolate approved downstream loads, and use the service procedure to check resistance, current, and power-supply behavior. The timing of the failure can connect the symptom to a particular motor, heater, board, or charging circuit.

Document conclusions at the strength the evidence supports. “Fuse opened twice when heater enabled; heater resistance below service limit” is defensible. “Bad design” is not, unless an approved investigation establishes it. When several factors contribute—such as a clogged filter, weak fan, and blocked installation clearance—record each corrective action rather than forcing the event into a single-cause story.

What Is a Root Cause?

A root cause is the underlying condition that produced the failure you observed.

It is the point in the chain where, if you correct that condition, the same failure should no longer continue for the same reason.

That sounds simple, but real equipment can have several contributing causes.

Root Cause Is Not Always One Thing

A failure may result from a combination of factors.

Example:

A monitor repeatedly overheats because:

Which one is the root cause?

Possibly all three contributed.

Real systems are not always neat enough to have one perfect answer.

Symptom, Cause, and Root Cause

These terms are worth separating.

Symptom

What the user or technician observes.

Example:

Device shuts down after 30 minutes.

Cause

The technical condition producing that symptom.

Example:

Power supply enters thermal protection.

Root Cause

Why that condition developed.

Example:

Cooling fan has failed, causing the power supply to overheat.

Now you have a much stronger repair story.

Another Example

Symptom:

Infusion pump reports repeated downstream occlusion.

Immediate cause:

Drive-force sensor sees excessive force.

Root cause:

Lead screw is contaminated and binding, increasing drive force even with an open fluid path.

If you simply adjust the occlusion sensor, you could make the equipment less safe while leaving the mechanical problem intact.

The First Bad Part May Only Be the Victim

This is one of the most useful root-cause concepts.

A failed component may be:

The cause

or:

The victim of another failure.

Example: Blown Fuse

Fuse is open.

You know:

Excessive current occurred.

You do not yet know why.

Possible causes include:

The fuse did its job.

It may not be the component that needs investigation.

Example: Burned Connector

You find a burned DC connector.

You could replace it.

But why did it burn?

Possible causes include:

If the mating connector is also damaged and you replace only one side, the failure may return.

Example: Dead Battery

Battery has poor capacity.

Replace it.

Done?

Maybe.

But if three new batteries fail early in the same device, start asking:

Why does this device keep killing batteries?

Possible causes include:

Root Cause Becomes More Important When Failures Repeat

A single battery reaching normal end of life may not justify a deep investigation.

Three batteries failing in six months probably does.

Repeated Failure Is Evidence

Suppose service history shows:

January:

Power supply replaced.

March:

Power supply replaced.

June:

Power supply replaced.

Do not automatically install a fourth one.

Ask what these repairs have in common.

Look for Shared Conditions

Possible shared factors include:

Work-Order History Is a Troubleshooting Tool

A CMMS should not only tell you:

What was replaced last time?

It can reveal patterns.

Example

Five repairs list:

NIBP pump replaced.

If the pump keeps failing, ask whether:

Do Not Confuse Repetition With Proof

If the same component repeatedly fails, that suggests an upstream condition.

It does not automatically prove one.

Gather evidence.

How Far Should You Go?

Not every repair requires finding the philosophical first cause of the universe.

You need enough investigation to make a safe, technically defensible repair.

Example

A ten-year-old fan develops noisy bearings.

You replace it.

Do you need to determine why the bearing eventually wore out?

Probably not.

That may simply be normal component aging.

Another Example

A fan less than a month old fails because its blades are rubbing against a cable installed during the previous repair.

Now the root cause matters.

Practical Root Cause Is the Goal

The useful question is:

Is there another unresolved condition likely to make this failure recur or create another safety problem?

If yes, investigate further.

Ask “Why?” More Than Once

A simple technique is repeatedly asking:

Why?

This is sometimes called the:

Five Whys.

You do not literally need exactly five.

The purpose is to keep moving beyond the first symptom.

Example

Why did the monitor shut down?

Because the internal temperature became too high.

Why?

Because the cooling fan stopped.

Why?

Because the fan connector was loose.

Why?

Because the locking tab was broken.

Now you have a repair target deeper than:

Unit overheated.

Do Not Force the Five Whys

Sometimes the evidence stops.

Do not invent explanations simply to reach another “why.”

Technical documentation should distinguish:

Root Cause Requires Evidence

Bad documentation:

Root cause was power surge.

Evidence:

None.

That is speculation.

Better Documentation

Input fuse open and power supply primary switching device shorted. No evidence available to determine why the power-supply component failed.

That is honest.

Sometimes Root Cause Remains Unknown

This is acceptable.

Your job is not to manufacture certainty.

Physical Root Causes

Common physical causes include:

Mechanical Wear

Example:

Syringe-pump drive develops excessive backlash.

Symptom:

Low-rate accuracy poor.

Immediate cause:

Plunger travel is inconsistent.

Underlying cause:

Drive nut is worn.

Loose Connection

Loose electrical connections can create:

The connector itself may later appear burned.

The looseness came first.

Fluid Intrusion

A board may fail electrically.

But if you see dried fluid around it, the board failure may be secondary to:

Fluid intrusion.

Replacing only the board may allow the problem to happen again if seals or enclosure damage remain.

Cleaning-Related Causes

Some failures follow:

The technical failure might be corrosion.

The underlying environmental cause may be cleaning exposure.

Be Careful With Blame

Your goal is not:

Prove nursing broke it.

Your goal is:

Identify what condition allowed the failure to occur and how recurrence can be reduced.

Environmental Causes

Equipment can be affected by:

Example: Repeated Overheating

Device:

Technically good.

Location:

Ventilation opening consistently blocked by cabinet.

The equipment problem may actually be an installation problem.

Facility Infrastructure

Possible root causes can exist outside the medical device.

Examples:

Example: Repeated Network Board Replacement

Device repeatedly loses network connection.

Boards replaced twice.

Eventually discovered:

Wall jack has intermittent pair.

The boards were never the cause.

Accessories Can Be Root Causes

Medical equipment rarely operates alone.

Accessories include:

Example

Patient monitor repeatedly reports:

SpO2 failure.

Monitor passes every bench test.

Original extension cable has intermittent conductor.

Replacing the monitor would never solve it.

Wrong Accessory

A device may fail because an accessory is:

The main equipment can be completely functional.

Software Root Causes

Modern medical devices are computers.

Software can cause:

Configuration vs Software Bug

These are not the same.

A device can fail because:

Software behaves incorrectly

or because:

Software is configured incorrectly.

Example

Monitor will not connect to central.

Network works.

Server works.

Device configured with old server address after a server migration.

Root cause:

Configuration not updated.

Updates Can Introduce Failures

Suppose several devices fail immediately after a software update.

That timing is useful.

Check:

But do not automatically assume the update caused it without evidence.

Network Root Causes

A networked failure may occur far from the bedside device.

Possible causes include:

Example

CT cannot retrieve worklist.

Local scanner functions normal.

Network link normal.

DICOM Echo to worklist server fails.

IT discovers firewall rule was removed.

Root cause is network infrastructure, not scanner hardware.

Human Factors

Some failures are related to workflow.

That does not automatically mean:

User error.

Poor Interface Design

If multiple clinicians make the same mistake, ask whether:

The root cause may be larger than one person's action.

Example

Pump repeatedly reported as:

Not charging.

Staff consistently plug AC adapter into a nearby accessory connector because the two ports look similar.

You could call this user error.

A better response might include:

Repair-Induced Root Causes

Previous service can create future failures.

Examples:

Never Assume Previous Repair Was Correct

Approach the evidence objectively.

Example

Device develops intermittent shutdown after battery replacement.

Inspection finds battery connector latch never fully engaged.

The new battery is not bad.

The installation is.

Replacement Part Quality

Not every replacement component is equivalent.

Repeated early failures can come from:

Wrong Fuse Example

Original design:

Time-delay fuse.

Replacement:

Fast-acting fuse with same current rating.

Device repeatedly blows fuse during normal inrush current.

Same amperage does not mean equivalent part.

Shared Root Cause

When multiple unrelated symptoms appear at once, look for a common subsystem.

Example

Device simultaneously shows:

Could three components have failed simultaneously?

Possible.

But a shared:

may be more likely.

Follow What the Failures Share

Ask:

What do these failed functions have in common?

That is one of the strongest troubleshooting questions you can ask.

Root Cause and Calibration

Calibration is especially dangerous when used to hide a hardware problem.

Example

Pressure sensor reads low.

You adjust calibration.

A week later it is low again.

Eventually you discover:

You calibrated around a changing physical failure.

Drift vs Failure

Small predictable drift may be corrected through authorized calibration.

Large or unstable drift suggests something else.

Root Cause and Error Codes

An error code identifies what the device detected.

Example:

Fan RPM Low.

That does not automatically mean:

Fan motor failed.

Possible causes include:

Ask What Measurement Generated the Error

This often reveals the actual troubleshooting path.

Root Cause and Self-Tests

Self-tests often check chains.

Example:

Command valve open.

Pressure does not change.

Device reports:

Valve Test Failed.

Possible causes include:

The root cause lies somewhere in the chain.

Root Cause and “No Problem Found”

Intermittent failures are especially difficult.

If a device repeatedly returns with the same complaint but passes bench testing:

Do not let every ticket exist in isolation.

Review the pattern.

Example

Three work orders:

Random shutdown during transport.

Bench testing:

Pass.

Eventually you learn all events occur while crossing a threshold into the elevator.

Controlled movement reproduces intermittent battery contact.

The pattern revealed what individual bench tests missed.

Ask What Changed

One of the most valuable root-cause questions is:

What changed before the problem began?

Changes may include:

Correlation Is Not Causation

If the problem began after:

Software update,

the update is a suspect.

It is not automatically guilty.

Confirm the Relationship

Can you:

Evidence matters.

Root Cause and Verification

A root-cause repair should address both:

The failed condition

and:

The underlying cause.

Example

Burned connector replaced.

Also repair:

Loose mating contact that created the heat.

Then verify:

Return-to-Service Testing

Once the repair is complete, verify the actual clinical function.

Do not stop because:

The bad-looking part is gone.

Example

Ventilator flow sensor replaced because water contamination damaged it.

Before return:

Also verify:

Root Cause May Require Process Change

Sometimes the correct response is not another component.

It may involve:

Example

Repeated fan failures caused by severe lint accumulation in one environment.

Replacing fans addresses each failure.

A shorter filter-cleaning interval may reduce recurrence.

Trending Helps

If your CMMS shows:

that may justify broader investigation.

One Device vs Fleet Problem

One failure:

Maybe individual equipment.

Twenty identical failures:

Think systemic issue.

Fleet-Level Root Causes

Possible causes include:

Safety Notices and Recalls

Repeated unexpected failures across a model may also justify checking for:

Use current manufacturer and regulatory information when applicable.

Do Not Over-Root-Cause Routine Wear

Root cause thinking can also go too far.

A battery lasts its expected service life and loses capacity.

Root cause:

Probably normal aging.

You do not need an investigation into why lithium-ion chemistry ages.

Match Effort to Risk

Investigate more deeply when:

Root Cause Analysis After Serious Incidents

A serious patient event may require a formal investigation beyond routine biomed troubleshooting.

That can involve:

Follow facility procedure.

Preserve Evidence

Do not casually:

on incident equipment before the appropriate process allows it.

Formal RCA vs Everyday Root-Cause Thinking

A formal Root Cause Analysis may be a structured organizational process.

Routine troubleshooting is different.

But the underlying reasoning overlaps:

What happened?

Why?

What conditions allowed it?

What prevents recurrence?

Document Facts First

A good corrective-maintenance note should distinguish what you:

Observed

from what you:

Concluded.

Weak Note

Device failed because nursing dropped it.

Better Note

Enclosure cracked and internal mounting bracket displaced. Staff reported device had fallen from cart immediately before failure.

Now the evidence is clear.

Weak Root-Cause Note

Bad power supply.

Better Note

Unit intermittently rebooted under NIBP load. 5 V rail dropped below specification when pump activated. Replaced power supply; voltage remained stable during repeated NIBP cycles and extended functional test.

You have a defensible cause-and-verification chain.

When You Cannot Prove the Root Cause

Say so.

Example:

Replaced failed power supply. Cause of component failure could not be determined. No evidence of fluid intrusion, overheating, or external damage noted.

That is technically stronger than inventing a story.

Common Mistakes

Replacing the First Failed Component and Stopping

Ask whether anything caused it to fail.

Confusing Symptom With Cause

“Won't power on” is not a diagnosis.

Calling Every Failure “User Error”

Look at the system and workflow.

Calibrating Around Hardware Problems

Fix changing physical conditions first.

Ignoring Work-Order History

Repeated failures are evidence.

Inventing a Root Cause Without Proof

Unknown is better than wrong.

Looking Only Inside the Device

Infrastructure and accessories can be the root cause.

Investigating Forever

Stop when you have enough evidence to make a safe and defensible decision.

A Useful Root-Cause Framework

Start with:

What exactly failed?

Then ask:

What component or subsystem produced that failure?

Then:

Why did that component or subsystem fail?

Then:

Is there an unresolved condition that could cause it to happen again?

Finally:

Did the repair eliminate both the failure and the underlying condition?

Another Useful Framework

Think:

Symptom

↓

Failed Function

↓

Failed Component or Condition

↓

Contributing Cause

↓

Verification

That keeps the investigation grounded in evidence.

What Did You Actually Prove?

Suppose a device repeatedly shuts down.

You replace the battery.

The shutdown stops.

What did you prove?

You proved:

The known-good battery corrected the symptom under the conditions you tested.

If the original battery also fails an independent capacity test:

Now you have stronger evidence the battery was defective.

But if the original battery is only six weeks old:

You may still ask:

Why did it fail so early?

If charging voltage is wrong:

Now you have found a deeper cause.

That is the difference between:

Replacing what failed

and:

Understanding why it failed.

Final Thoughts for Biomeds

Root cause troubleshooting does not mean making every repair complicated.

It means knowing when to ask one more:

Why?

A failed fuse may be the problem.

Or it may be protecting you from the problem.

A failed battery may simply be old.

Or the charger may be damaging every battery installed.

A network card may appear dead.

Or the wall connection may be intermittent.

Your goal is not to create the longest possible explanation.

Your goal is to identify enough of the failure chain that you can make a repair that is:

Sometimes the root cause is obvious.

Sometimes it requires more testing.

Sometimes it remains unknown.

That is fine.

Just do not confuse the first thing you find with the deepest thing you have actually proven.

— Jake

Important Note

Formal root-cause analysis requirements, incident investigations, equipment quarantine, reporting responsibilities, and corrective-action processes vary by healthcare organization and event severity. Serious patient-safety events should be handled according to facility incident-response and evidence-preservation procedures in addition to normal technical troubleshooting.

Related Biomed Basics

Back to Biomed Basics