How to Use Equipment History During Troubleshooting

How previous work orders, repeat failures, replaced parts, PM findings, and service patterns can help you stop treating every repair like it is the first time the device has ever failed

A medical device rarely fails in a vacuum.

Back to Biomed Basics

What This Page Explains

This page covers:

The Simple Version

Before you troubleshoot a difficult or repeat failure, review the history.

Look for:

You are trying to answer:

Is this really a new failure, or is it the latest version of an old one?

CMMS History Is More Than Administrative Data

A CMMS is often treated as:

The place where we close work orders.

That is a waste of one of its most useful functions.

Good service history can act like a long-term diagnostic log.

It tells you what happened when you were not there.

What Makes History Useful

The value depends on the quality of previous documentation.

A note that says:

Checked unit. Works fine.

gives you almost nothing.

A note that says:

Reported intermittent shutdown during transport. Unable to duplicate during 90-minute battery operation. Battery passed capacity test. AC-to-battery transitions normal. No reset events in logs.

is useful.

Now you know what was already tested.

Start With the Complaint

Search the recent history for the same symptom.

Example:

Current complaint:

Reboots randomly.

Look for previous work orders containing:

Clinical language and technical language may differ.

Different Words Can Describe the Same Failure

One work order may say:

Screen went blank.

Another:

Monitor shut off.

Another:

Unit rebooted.

Those may or may not be the same issue.

Read the details.

Frequency Matters

One complaint over five years may be noise.

Five complaints in six months are a pattern.

Repeat Failure Changes the Decision

A first-time complaint may justify:

A repeated complaint may justify:

Example: Repeated Battery Replacement

History:

January: battery replaced.

April: battery replaced.

July: battery replaced.

That is not normal unless the batteries themselves are poor quality or the usage is extreme.

Ask:

Why are batteries failing early?

Possible causes include:

Parts History Can Reveal Misdiagnosis

Suppose the device has had:

and the same reboot complaint continues.

That tells you something important:

The original diagnosis may not have been correct.

Do Not Repeat Failed Repair Logic

One of the worst habits is:

They replaced the board last time, so I'll replace it again.

Previous part replacement is evidence.

It is not proof that the part was the cause.

Ask Whether the Previous Repair Actually Held

Look at the timeline.

If board replaced and same complaint returned two days later:

Strong evidence the board may not have been root cause.

If complaint returns five years later:

That is different.

Time Between Failures Matters

A repair that lasts years may have been legitimate.

A repair that lasts hours probably was not.

Previous “No Problem Found” Work Orders

Multiple NPF work orders can be especially valuable.

Example:

January:

Unable to duplicate.

March:

Unable to duplicate.

June:

Unable to duplicate.

Current complaint:

Same symptom.

Do not treat this as another isolated NPF.

Repeated NPF Is a Pattern

It suggests the failure may depend on:

Example

Three notes mention:

Failure during transport.

That may be the most important clue in the history.

PM Findings

Preventive-maintenance records can also provide troubleshooting evidence.

Look for trends such as:

Trend vs Single Point

One PM result may not mean much.

A pattern over several PMs can.

Example

Infusion pump flow test:

Year 1: 100.2 mL/hr

Year 2: 99.1 mL/hr

Year 3: 96.0 mL/hr

Year 4: 94.8 mL/hr

That trend may suggest wear before a hard failure occurs.

Calibration History

Repeated calibration drift can point toward an underlying issue.

If the same parameter constantly needs adjustment:

Ask why.

Example

Pressure channel adjusted at every PM.

That may indicate:

rather than normal drift.

Vendor History

OEM service reports can contain clues not captured in the CMMS.

Review:

Do Not Record “Sent to Vendor” and Stop There

When the device returns, capture:

Otherwise the history becomes incomplete.

Firmware and Software Changes

Modern equipment failures can follow:

Look at when the issue began relative to those events.

Correlation Is Not Proof

If complaints start after version 4.2:

That is worth investigating.

It does not automatically prove 4.2 caused them.

Location Patterns

The equipment history may reveal that failures happen only in:

Example

Monitor has three Wi-Fi complaints.

All occurred:

During transport to CT.

That points you toward:

not necessarily monitor hardware.

Compare With Fleet History

Do not look only at the one asset.

Ask:

Are other devices of the same model having the same issue?

Fleet Pattern

If ten units show the same failure:

Think systemic.

Possibilities include:

One Device Only

If one device has repeated issues while twenty identical units do not:

Think local.

Asset Age

Older equipment naturally accumulates more repairs.

That does not mean every failure is age-related.

But age helps interpret the repair history.

Service Intensity

Two devices of the same age may have very different histories.

One in a busy ED may have:

Usage matters.

Runtime and Cycle Counts

Some devices track:

These can be more meaningful than calendar age.

Accessory History

Sometimes the repeat failure is not the main device.

Review whether the same:

has followed the asset.

Example

Monitor repeatedly loses power.

Same mobile stand has damaged power adapter.

Device hardware was never the problem.

External Infrastructure

History can expose infrastructure patterns.

Example:

Several devices in same OR show intermittent network loss.

Different models.

Same network drop.

That is valuable.

Use History to Build Better Hypotheses

Suppose current complaint is:

Device shuts off.

Without history, possibilities are broad.

History shows:

Now battery contact becomes a strong hypothesis.

History Narrows the Search Space

That is its biggest value.

Do Not Let History Create Confirmation Bias

This is important.

If previous technician wrote:

Bad battery,

you may be tempted to assume battery again.

Test it.

History Should Guide, Not Dictate

Use it as evidence.

Do not let it override current findings.

Example

Previous three complaints were battery-related.

Current unit does not power on even on AC.

This may be different.

Look for What Was Never Tested

Previous work orders may reveal gaps.

Example:

Three shutdown complaints.

Each note says:

Tested on AC, passed.

Nobody tested on battery.

That is a clue in itself.

Look at Repair Depth

Was the device:

The difference matters.

“Replaced Battery” Is Not Enough

Did they verify:

Maybe not.

Build a Timeline

For complex recurring failures, a simple timeline can be extremely useful.

Example:

January 5 — first shutdown complaint

January 7 — NPF

February 18 — battery replaced

March 2 — shutdown again

March 3 — battery contacts cleaned

April 10 — shutdown again during transport

Now you can see the story.

Patterns Are Easier to See Chronologically

CMMS screens often show work orders individually.

Mentally convert them into a sequence.

Ask Whether the Failure Is Getting Worse

Example:

First complaint:

Once per month.

Now:

Once per day.

That progression may indicate degradation.

Ask Whether the Failure Changed

Maybe the original problem was:

Short runtime.

Now:

Unexpected shutdown.

These may share a battery cause but are not identical.

Repair Decisions Should Consider History

A device with:

is different from one with:

Even if the current failure is technically repairable.

Reliability Matters

Repeated failures cost more than parts.

They create:

History and Replacement Planning

Service history can support capital replacement decisions.

Instead of:

This thing is old.

you can say:

Unit has required five corrective repairs in 12 months, including two main-board replacements, and parts availability is limited.

That is a stronger argument.

History and Escalation

OEM technical support will often ask:

Have that ready.

Build a Useful Escalation Package

Do not make the vendor rediscover the history.

Give them:

Documentation Quality Compounds Over Time

Good notes make future repairs faster.

Bad notes make each repair start at zero.

That is why documentation matters beyond billing or compliance.

Real-World Example: Random Reboot

Current complaint:

Monitor randomly reboots.

History:

Now test the power rail during NIBP activation.

You find voltage collapse.

History pointed you toward the real trigger.

Real-World Example: Repeated NIBP Error

Pump replaced three times.

History shows complaints continue.

Current inspection finds contaminated hose causing excessive load.

The pump may have been the victim, not the cause.

Real-World Example: Network Drop

One monitor repeatedly loses central connection.

History shows every complaint occurred in same room.

Second monitor in same room also has issue.

Now infrastructure becomes much more likely.

Real-World Example: Touchscreen

Touchscreen replaced twice.

Complaint returns.

History shows failures always after aggressive cleaning.

Inspection reveals fluid intrusion around bezel.

Replacing displays did not address the environmental cause.

Common Mistakes

Not Reading the History

You may repeat work already done.

Trusting the Previous Diagnosis Too Much

Previous technicians can be wrong.

Looking Only at the Last Work Order

Patterns may span years.

Ignoring NPF History

Repeated inability to duplicate is itself useful information.

Failing to Capture Vendor Repair Details

The next technician loses context.

Treating Every Complaint as Independent

Some are clearly related.

A Useful Equipment-History Framework

Before troubleshooting a difficult problem, ask:

Has this happened before?

Then:

What was done last time?

Then:

Did the repair hold?

Then:

What conditions repeat across the failures?

Then:

What has never been tested?

Then:

Is this one asset or a fleet pattern?

Another Useful Question

Ask:

What would I conclude if I saw all of these work orders at once instead of one at a time?

That question often reveals the pattern.

What Did You Actually Prove?

If the previous work order says:

Battery replaced,

you proved only that a battery was replaced.

You did not prove the battery caused the original failure.

If the note says:

Original battery failed capacity test, known-good battery eliminated shutdown, and unit passed 2-hour battery operation,

now you have much stronger evidence.

History is only as strong as the evidence captured in it.

Final Thoughts for Biomeds

Every medical device tells a story over time.

The CMMS is where that story should live.

Use it.

Before replacing the same board again, ask:

Has this already been tried?

Before calling a failure random, ask:

Has it happened under the same conditions before?

Before deciding a device is unreliable, look at the actual repair pattern.

Good troubleshooting happens in the present.

Great troubleshooting also uses the past.

And sometimes the most important clue is not inside the device at all.

It is buried in a work order from six months ago.

— Jake

Important Note

CMMS structure, service-history requirements, asset-management practices, vendor documentation, and retention policies vary by healthcare organization. Service history should support troubleshooting and lifecycle decisions, but current equipment condition, manufacturer guidance, facility policy, and direct testing should remain the primary basis for technical conclusions.

Related Biomed Basics

Back to Biomed Basics