On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide provides a structured Clinical Engineering approach when a CARESCAPE B850 monitor will not power on.
The focus is on logical, external, and easily verifiable checks before assuming internal failure. These steps rule out common power-related causes while maintaining patient safety and minimizing unnecessary escalation.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- If the monitor is in clinical use: transfer the patient to a functioning monitor first.
- Do not troubleshoot while the monitor is actively required for patient care.
- Confirm the device is safe to remove from service before proceeding.
Verify AC Power at the Outlet
- Confirm the monitor is connected to a known-working hospital-grade outlet.
- Test the outlet with a known-good device (lamp, outlet tester, etc.).
- If plugged into a power strip, isolation transformer, or UPS, verify that device is powered on and functioning.
- If available, try a different known-working wall outlet.
- Why this matters: Loss of upstream power is the most common and simplest cause of a “dead” monitor.
Inspect and Reseat the Power Cord
- Visually inspect the power cord for cuts, fraying, bent or damaged prongs, and loose connector ends.
- Reseat the cord firmly at the wall outlet and the rear AC inlet of the monitor.
- If available, swap with a known-good hospital-grade power cord and attempt to power on again.
- Why this matters: A loose or internally failed cord can mimic total device failure.
Confirm the Rear Power Switch Position
- Verify the rear power rocker switch is in the ON position.
- Then press the front power button.
- Do not assume the switch position without physically checking it.
Observe for Any Signs of Activity
- When attempting to power on, closely observe front LED indicators, brief screen flash, audible fan noise, or clicking sounds.
- Even minimal activity suggests partial power presence and helps narrow down whether the failure is complete or localized.
If the Problem Persists
- If the monitor shows no indicator lights, no fan noise, no display activity, and no response with known-good outlet and power cord, then common external causes have been ruled out.
- At this point, the issue is likely internal (power supply board, internal fuse, or power distribution failure).
- Remove the monitor from service, label clearly as Out of Service, and send for repair or bench evaluation.
- Knowing when to stop prevents unnecessary downtime and protects patient safety. Escalation after logical checks is proper troubleshooting.
Clinical Use Tip
- Never troubleshoot a non-powering monitor on an active patient.
- Always move the patient to a working monitor first, confirm monitoring continuity, then remove the failed unit from service.
- Patient monitoring continuity takes priority over equipment evaluation.
Work Order Documentation (CCR Method)
Complaint
What was reported by the clinical staff.
Example:
“Monitor will not power on.”
Cause
What was observed during troubleshooting.
Example:
“Unit does not power on with known-working outlet and known-good power cord. Rear switch verified ON. No indicator lights, fan noise, or display activity observed. Suspected internal power supply failure.”
Resolution
What action was taken.
Example:
“Removed from service and tagged Out of Service.”, “Sent to Biomed shop for bench evaluation.”, “Dispatched for vendor repair.”
Helpful Details to Include (If Known)
- Outlet tested (yes/no)
- Alternate outlet attempted
- Power cord swapped (yes/no)
- Rear switch position confirmed
- Indicator light behavior
- Fan noise present/absent
- Any unusual odor or heat
- Final device status (returned to service or sent for repair)
Final Thought
Effective troubleshooting starts with the simplest external checks and progresses logically. Ruling out power source and connection issues protects patient safety, reduces unnecessary part replacement, and supports accurate repair escalation.
A Clinical Engineer’s role is not just to fix equipment — it is to think systematically, document clearly, and know when escalation is appropriate.
That is successful troubleshooting.