How to Ask Clinical Staff Better Troubleshooting Questions

How better questions turn vague equipment complaints into useful technical clues before you ever open the device

A large percentage of biomed work starts with a complaint like:

Published August 20, 2026 · Revised September 6, 2026

Back to Biomed Basics

What This Page Explains

This page covers:

Why the original work-order complaint is often incomplete

How to ask useful follow-up questions

How to separate symptom from interpretation

Questions for intermittent problems

Questions for accessories and disposables

Questions for power problems

Questions for network and integration problems

Questions for alarms

Questions after serious clinical events

What not to ask

How to document what staff actually observed

The Simple Version

Ask the user to walk through what they were trying to do, what actually happened, and what the device displayed or sounded. Then identify what still worked, what accessories and network connections were present, whether the problem repeats, and what changed before it began. These questions reconstruct the operating conditions instead of asking staff to diagnose the component.

Use neutral wording. “What did you see next?” preserves observations better than “Did the battery fail?” Capture exact alarm text, settings, patient connection state, time, room, and any workaround. A two-minute conversation at the device can prevent hours of testing under the wrong conditions.

Worked Example: “The Pump Stopped”

Ask whether the display went blank, delivery paused, or an alarm stopped the infusion. Ask for the exact alarm, programmed rate, tubing and channel, power source, door state, and what staff did next. “Downstream occlusion after the patient repositioned” leads to a different bench test than “screen went black when the power cord moved.”

Repeat the complaint back in technical but neutral language and document who observed it and when. Do not dismiss a symptom because it cannot be reproduced immediately; clinical context may identify an intermittent accessory, setup, environmental, or network condition that the empty bench lacks.

Start With What They Actually Saw

Ask:

That is much better than:

You want observations.

Examples:

These are useful symptoms.

Avoid Leading Questions

Do not start with:

Now you have introduced your theory into the conversation.

Ask:

Let the evidence come first.

Symptom vs Interpretation

Clinical staff may say:

The battery is bad.

What they may actually mean is:

It shuts off when we unplug it.

Those are not the same statement.

Document the observed symptom.

Ask What They Were Trying to Do

Equipment behaves differently depending on mode and workflow.

Ask:

Examples:

A device may fail only during one function.

Example:

Monitor works normally until NIBP starts.

Then it reboots.

That points you toward a load-dependent power problem much more quickly than:

Monitor randomly restarts.

Ask Whether It Happens Every Time

This separates:

Ask:

or:

Does it happen every time you do that?

If It Is Intermittent

Ask:

Intermittent does not mean random.

Ask What the Screen Said

Error messages are valuable.

Ask:

Try to get the exact wording.

"Some battery message" is less useful than:

Battery communication lost.

Ask About Alarm Sounds

Ask whether the device:

Different alarm behavior can tell you how far the system got before failing.

Ask What Still Worked

This is one of the best questions.

If a patient monitor loses SpO2 but:

that is very different from the whole monitor shutting down.

Shared vs Isolated Failure

If one function fails:

Think local subsystem.

If everything fails at once:

Think shared component.

Examples:

Accessories are common failure points.

Ask:

Example:

Monitor repeatedly reports:

SpO2 Sensor Off.

Only happens with one reusable sensor.

Known-good sensor works.

You may have just avoided pulling the monitor apart.

Ask Whether They Tried Another Accessory

This can be useful if they already performed a swap.

But verify what they mean by:

We tried another one.

Was it actually compatible and known good?

Ask Where It Happened

Location matters.

Ask:

This is especially useful for:

If two known-good devices fail in the same location:

Think infrastructure.

Failure Follows Device

If the same device fails in multiple known-good locations:

Think device or configuration.

Ask If Anything Changed

A very useful question is:

Possible changes include:

Timing matters.

"It Started After..."

That phrase can be extremely valuable.

It does not prove cause.

But it gives you a strong place to investigate.

Power Problem Questions

For a device that shuts off or will not power on, ask:

Did the screen go dark instantly or shut down normally?

Instant Shutdown vs Normal Shutdown

Instant black screen may suggest:

A controlled shutdown may suggest:

Different clue.

Charging Problem Questions

Ask:

These questions separate:

Instead of:

NIBP doesn't work.

Ask:

Now think:

rather than no-power condition.

SpO2 Questions

Ask:

These separate recognition from signal quality.

ECG Questions

Ask:

Ask:

That immediately moves you away from patient measurement and toward communication.

Integration Problem Questions

If data is not reaching the EMR, ask:

The goal is to determine where the data stops.

Alarm Complaint Questions

If staff says:

Alarm isn't working.

Ask:

If visual alarm works but speaker does not:

That is very different from alarm logic not detecting the condition.

Printer Complaint Questions

Ask:

Again, isolate the function.

Touchscreen Complaint Questions

Ask:

A single dead zone suggests something different from full UI lockup.

Intermittent Complaint Questions

For intermittent problems, ask:

If the problem happens after 45 minutes, a five-minute bench test proves very little.

Try to recreate the conditions.

Serious Event Questions

If the device was involved in a serious patient-care event, the approach changes.

Do not casually manipulate or erase evidence.

Gather:

Then follow facility incident and preservation procedures.

Do Not Clear Logs First

In a serious event, logs may be important evidence.

Do not reboot, update, or reset unnecessarily before following the required process.

Ask Who Saw It

Sometimes the person dropping off the device did not witness the event.

Ask:

That can prevent secondhand descriptions from becoming distorted.

Firsthand vs Secondhand Information

Document when a complaint is:

That matters when the description is unclear.

Ask for Timing

The exact approximate time can help match:

Example:

is weak.

Around 02:15 during transport

is much more useful.

Ask What Happened Immediately Before the Failure

Examples:

This can identify the trigger.

Ask What Happened Immediately After

Did the device:

Recovery behavior is useful.

Ask Whether Staff Already Tried Anything

Find out what was changed.

Examples:

This can provide useful evidence.

But Be Careful With the Result

If they say:

We rebooted it and it worked.

You proved:

It worked after a reboot.

You did not prove:

Software caused the problem.

Ask One Question at a Time

Avoid firing ten questions in one breath.

Staff may be busy.

Start with the highest-value questions.

A Good First Five Questions

For many complaints:

That alone may get you most of what you need.

Use Their Language First

If a nurse says:

you do not need to correct them with:

You mean the NIBP pneumatic subsystem failed to generate cuff pressure.

Translate it mentally.

Get the information first.

Do Not Make Staff Feel Tested

The goal is not to quiz clinicians on device theory.

They should not need to know:

Ask about what they observed.

Bad Question

Did the expiratory valve fail?

They may have no idea.

Better Question

Was pressure staying high between breaths?

Now they can answer from what they saw.

Ask for Photos When Appropriate

If an intermittent error disappears before the device reaches biomed, a photo of:

can be extremely useful.

Ask Staff Not to Recreate Unsafe Conditions

Do not ask someone to repeat a dangerous event just to prove it happened.

Use logs, controlled bench testing, and safe reproduction.

Clarify "Not Working"

That phrase can mean:

Always translate it into an actual symptom.

Clarify "Dead"

"Dead" might mean:

Do not assume.

Clarify "Keeps Disconnecting"

Disconnecting from what?

Patient cable?

Wi-Fi?

Central station?

Power?

The noun matters.

Clarify "It Was Fine Yesterday"

Ask:

Sometimes the answer is:

Ask Whether Another Device Had the Same Problem

This is especially useful for infrastructure issues.

If several devices fail similarly at once:

Think shared cause.

Ask Whether Another Device Worked There

This gives you a comparison.

Example:

Original monitor cannot connect.

Replacement monitor also cannot connect.

Now think room/network.

Ask If It Was Patient-Specific

Some measurement complaints only occur on certain patients.

If the device works on:

the equipment may be fine.

Patient Conditions Can Affect Measurement

Examples include:

Do not automatically diagnose a device failure from one difficult measurement.

Ask If It Was Accessory-Specific

If a problem only occurs with:

the main device may not be the issue.

Ask About Cleaning

If a problem started after cleaning:

Ask whether:

Cleaning-related damage is common.

Ask About Drops and Impacts

Staff may say:

It just stopped working.

Ask:

Physical events matter.

Do Not Accuse

Phrase it neutrally.

You are looking for technical history, not assigning blame.

Ask About Transport

Some failures happen only during movement.

Examples:

Ask whether failure occurred:

Was the device:

Context can matter.

Ask for the Exact Accessory

If there are multiple compatible-looking accessories, note:

A wrong accessory can create a legitimate complaint.

What Not to Ask

Avoid:

That is defensive and usually unhelpful.

Better:

Can you walk me through what was happening when it failed?

Same information, better interaction.

Avoid Immediate Blame

Do not begin with:

IT problem.

or:

User error.

You have not proven either yet.

Avoid Diagnosing Before Reproducing

A complaint can sound obvious and still be misleading.

Gather enough evidence before deciding.

Document the Complaint Accurately

A good work order might say:

Nursing reports monitor intermittently shuts off immediately when AC power is removed despite battery icon showing approximately 80%.

That is much more useful than:

Battery issue.

Separate Reported From Observed

A strong note may distinguish:

Reported: Device shut down twice during transport.

Observed: Unable to reproduce during 45-minute battery test.

That preserves the evidence honestly.

Do Not Rewrite Staff's Complaint Into Your Diagnosis

If staff says:

do not document:

until you prove it.

Useful Work-Order Language

Use phrases like:

These distinguish evidence levels.

Example

Staff reports: Intermittent ECG lead-off during patient movement.

Observed: Reproduced RA lead-off by flexing lead wire near connector.

Now the complaint and your finding connect clearly.

A Useful Troubleshooting Conversation

Start with:

Then:

Then:

Then:

Then:

Then:

Then:

That is a very efficient sequence.

What Did You Actually Prove?

If staff says:

you proved:

Staff believes the complaint involves the battery.

You did not prove:

Battery is defective.

If staff says:

It shut off every time we unplugged AC,

you now have a specific reproducible symptom.

If you reproduce that behavior yourself and a known-good battery corrects it:

Now you have much stronger evidence.

The quality of your troubleshooting depends heavily on the quality of the original symptom.

Final Thoughts for Biomeds

Clinical staff do not need to diagnose the equipment for you.

They need to tell you what happened.

Your job is to turn:

into something like:

Device operates normally on AC but shuts down immediately when unplugged, only with Battery A, and no error appears before shutdown.

That is troubleshootable.

Ask about:

And do not lead the conversation toward the answer you already suspect.

Good questions save time.

They prevent unnecessary parts replacement.

They help with intermittent problems.

And they give you better evidence before the device ever reaches the bench.

The goal is not to ask more questions.

It is to ask the questions that help you answer:

For equipment involved in patient harm, serious safety events, or other reportable incidents, follow facility incident-response and evidence-preservation procedures before performing routine troubleshooting, rebooting, clearing logs, changing configuration, or otherwise altering the device.

Related Biomed Basics

Back to Biomed Basics