What “Unable to Duplicate” Should Actually Mean

Published August 13, 2026 · Revised September 6, 2026

How to document and think about a problem you cannot reproduce

“Unable to duplicate.”

Back to Biomed Basics

What This Page Explains

This page covers:

The Simple Version

“Unable to duplicate” should mean that you made a reasonable, documented effort to recreate the reported problem under relevant conditions and the failure did not occur during that testing. It should never be shorthand for powering the device on once, seeing no obvious error, and sending it back without addressing the clinical complaint.

Record the exact complaint, accessories, modes, power sources, loads, durations, movements, environmental conditions, logs, and tests used. State what passed and what was not available to test. Then base the disposition on risk and evidence: extend observation, replace a suspect accessory, seek more clinical detail, escalate to the manufacturer, or return the device under the facility's policy with a clear record of the limitations.

Start With the Actual Complaint

Before you can say you could not duplicate something, you need to know what you were trying to duplicate.

Weak complaint:

Not working right.

Better complaint:

Monitor shuts off during transport.

Better still:

Monitor shut off twice while on battery during transport from ICU to CT.

Now you have something specific to test.

Translate the Complaint Into a Test

Complaint:

Shuts off during transport.

Test:

Complaint:

ECG cuts out when cart moves.

Test:

Complaint:

Pump alarms occlusion randomly.

Test:

Your test should resemble the complaint.

“Powers On” Is Not a Reproduction Attempt

This is one of the most common weak checks.

Complaint:

Device intermittently shuts down.

Bench test:

Device powers on.

Conclusion:

Unable to duplicate.

You did not really test the complaint.

You proved:

The device powered on once.

That is useful, but it is not enough.

Match the Power Source

If the complaint happened on battery, test on battery.

If it happened while plugged in, test AC.

If it happened during unplugging, test the transition.

AC and battery operation may use different parts of the power path.

A device can work perfectly on one and fail on the other.

Match the Runtime

If the problem occurs:

After three hours.

a ten-minute bench test has limited value.

Possible time-dependent causes include:

Run the device long enough to reasonably challenge the reported condition.

Match the Movement

Portable equipment experiences:

If the problem happens during transport, keep that in mind.

A perfectly still bench setup may never reveal a loose connection.

Use the Original Accessories When Appropriate

If the complaint involved:

those parts may be the cause.

If you immediately replace everything with known-good shop accessories, the problem may disappear before you learn anything.

Test the original setup first when safe and practical.

Then Use Known-Good Components

Once you understand the symptom, known-good substitution can help isolate the failure.

Example:

Original SpO2 sensor:

Intermittent dropout.

Known-good sensor:

Stable.

Original sensor on another monitor:

Dropout.

Now you reproduced and isolated the problem.

Check the Logs

If the device refuses to fail in front of you, its logs may still prove something happened.

Look for:

Compare timestamps with the reported incident.

Logs Can Turn “Unable to Duplicate” Into a Better Finding

Suppose you cannot reproduce a reboot.

But logs show:

Battery Communication Lost

at the time staff reported the shutdown.

Now you have evidence.

The device may still need further troubleshooting even though the failure did not recur.

Ask Whether the Complaint Is High Risk

Not every unable-to-duplicate complaint carries the same risk.

Compare:

Printer skipped one line.

with:

Defibrillator shut off during charging.

Both may be intermittent.

The second deserves a much higher level of confidence before return to service.

Risk changes how much testing is reasonable.

Low-Risk Example

Complaint:

One keypad button felt sticky.

You inspect.

Clean according to procedure.

Button operates normally through repeated testing.

No additional faults.

That may reasonably support return to service.

Higher-Risk Example

Complaint:

Ventilator rebooted during use.

You cannot reproduce it.

That may require:

A quick pass is not the same level of evidence.

“Unable to Duplicate” Is Not “No Problem Found”

These phrases are sometimes used interchangeably.

They should not always be.

Unable to duplicate means:

The reported symptom did not occur during testing.

No problem found may imply:

Testing found no fault at all.

But you may still have:

even if the exact complaint did not recur.

Use precise language.

Be Careful With “No Fault Found”

A device can have a real intermittent problem and pass every test while you have it.

That does not make the clinical complaint false.

Avoid framing the work order in a way that dismisses the user.

The correct conclusion may simply be:

Unable to reproduce reported shutdown during bench testing.

That is factual.

Ask Better Questions Before Testing

Useful questions include:

A five-minute conversation can save hours of blind testing.

Try to Reproduce the Failure More Than Once

If the complaint is intermittent, repeated cycles can help.

Examples:

One successful cycle does not prove reliability.

Test the Specific Function

Complaint:

NIBP sometimes reads wrong.

Do not just verify the module inflates.

Use appropriate analyzer testing.

Complaint:

Alarm did not sound.

Do not just verify the device powers.

Generate the alarm condition safely and verify notification.

Test the thing that was reported.

Change One Variable at a Time

If you cannot duplicate the problem and simultaneously:

then the device starts behaving, you may never know whether one of those changes fixed an intermittent condition.

Preserve diagnostic information where practical.

Do Not Reset Everything First

Factory reset.

Software reload.

Configuration restore.

These may erase the state that caused the complaint.

Start by understanding the current condition.

Resetting may be appropriate later.

Document the Conditions You Tested

This is what makes an unable-to-duplicate note useful.

Weak:

Checked unit. Unable to duplicate.

Better:

Reported intermittent shutdown during transport. Operated unit on battery under normal load for 90 minutes, moved cart through repeated transport cycles, flexed power connection, and transitioned between AC and battery ten times. Reviewed event log with no shutdown or power faults observed. Unable to reproduce reported condition.

Now the next technician knows what was actually done.

Include What You Found Even If It Was Not the Complaint

Example:

Unable to reproduce reported shutdown. Battery runtime measured 42 minutes against required 90-minute minimum.

That is not:

No problem found.

You found a problem.

It may or may not explain the original complaint.

Do Not Overstate the Conclusion

Do not write:

Device is fine.

unless you truly mean and can support that statement.

Better:

Reported symptom not reproduced. Device completed required functional verification with no additional faults observed.

That is specific and defensible.

Returning to Service

Whether equipment can return to service depends on:

There is no universal rule.

A minor intermittent cosmetic issue and an unexplained therapy interruption should not be treated identically.

Repeat History Matters

If the same device repeatedly comes back with:

Unable to duplicate.

pay attention.

First visit:

Maybe unusual.

Fourth visit for the same shutdown:

Pattern.

At that point, consider:

Repeated complaints are evidence.

Look Across the Fleet

If several identical devices have the same complaint, that matters too.

Possible common causes:

The fact that each individual unit passes on your bench does not erase the fleet pattern.

Real-World Example: Monitor Shutdown

Complaint:

Monitor shut off in hallway.

Basic test:

Powers normally on AC.

Not enough.

Better:

Run on battery.

Move cart.

Transition AC/battery.

Review logs.

Flex battery.

If nothing occurs after reasonable testing, you may document unable to duplicate with actual evidence behind it.

Real-World Example: ECG Cable Dropout

Complaint:

ECG disappears randomly.

On bench:

Stable initially.

Flex trunk cable.

Waveform drops.

Now it is no longer unable to duplicate.

You reproduced it.

That changes everything.

Real-World Example: Pump Occlusion Alarm

Complaint:

Pump gives random downstream occlusion alarms.

Analyzer test:

Occlusion threshold repeatedly within specification.

Original tubing set:

Kink found near clamp.

You may have identified a setup/accessory issue even though the pump itself passes.

Real-World Example: Defibrillator Shutdown

Complaint:

Device shut off during charge.

You run:

No failure observed.

Because of the seriousness of the complaint, additional escalation may still be appropriate.

“Unable to duplicate” does not automatically mean:

Return it immediately.

Common Mistakes

Writing UTD After Five Minutes

Test the actual complaint.

Ignoring Power Source

Battery and AC can behave differently.

Ignoring Movement

Intermittent connections may need motion.

Not Checking Logs

Historical evidence matters.

Dismissing Clinical Staff

They may have witnessed a real intermittent failure.

Calling It Fixed Without a Repair

If nothing changed, do not pretend you repaired it.

Returning High-Risk Equipment Too Quickly

Risk matters.

A Useful Question

Before writing:

Unable to duplicate.

ask:

What did I actually do to try to duplicate it?

If the answer is weak, test more intelligently.

Another Useful Question

Ask:

If this happens again tomorrow, will my work order show that I actually investigated the right condition?

That is a good documentation test.

What Did You Actually Prove?

Suppose you ran a device on battery for two hours without failure.

You proved:

The reported failure did not occur during two hours of battery operation under the conditions you tested.

You did not prove:

The failure can never occur.

That is the honest conclusion.

Final Thoughts for Biomeds

There is nothing wrong with being unable to duplicate a problem.

Intermittent failures exist.

Clinical environments are complicated.

You will not reproduce everything.

The quality of the work comes from what happened before you wrote those words.

Did you understand the complaint?

Did you recreate the conditions?

Did you test the right function?

Did you use the original accessories?

Did you check the logs?

Did you consider the risk?

If yes, then:

Unable to duplicate

can be a legitimate technical finding.

If all you did was power the device on and watch it for a few minutes, it is probably not enough.

The phrase should describe the result of troubleshooting.

It should never be a substitute for troubleshooting.

— Jake

Important Note

This page is an educational overview. Decisions involving unresolved intermittent medical equipment faults should follow current manufacturer guidance, facility procedures, equipment risk, required verification methods, and your authorized service scope. Serious or repeated unresolved failures may require additional evaluation or escalation before return to clinical use.

Related Biomed Basics

Back to Biomed Basics