GE DASH 5000 Series Patient Monitor

Invasive Pressure Calibration / Drift Problems

On this page

Asset Type

Patient Monitor

Manufacturer

GE Healthcare

Model

DASH 5000 Series

What This Guide Helps With

This guide assists Clinical Engineering in troubleshooting DASH 5000 monitors when invasive arterial or central venous pressure readings drift, fail to calibrate, or show inconsistent values. Symptoms include slow baseline drift, sudden spikes, or readings that do not correlate with a reference transducer. The guide focuses on external and easily verifiable causes before assuming internal device failure.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Verify Zeroing and Calibration Procedure

Check Transducer Position and Level

Inspect Pressure Tubing and Connections

Verify Transducer Integrity

Check Monitor Configuration and Settings

Assess Electrical and Environmental Factors

Perform a Known-Reference Test

If the Problem Persists

If baseline drift or calibration issues continue after all external checks:

Remember: Proper troubleshooting includes knowing when to escalate.

Clinical Use Tip

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“Invasive pressure readings drifting and failing calibration during patient monitoring.”

Cause

What was observed during troubleshooting.

Example:
Observed baseline drift despite zeroing; tubing had microbubbles, transducer not properly leveled.

Resolution

What action was taken.

Example:
Flushed line, leveled transducer correctly, replaced with a known-good transducer; monitor calibrated successfully.
If issue persists, monitor removed from service for bench evaluation.

Helpful Details to Include

Final Thought

Clinical troubleshooting of invasive pressure should prioritize patient safety, start with simple external checks, and escalate appropriately when internal failure is suspected. Accurate documentation ensures continuity of care and supports maintenance tracking.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide