On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where a Siemens RAPIDPoint 500 or 500e blood gas analyzer fails to aspirate a sample or reports clot detection errors. These issues are commonly caused by external factors such as sample handling problems, clogged sampling probes, improper cartridges, or fluid pathway restrictions. The guide focuses on simple and safe checks before assuming internal system failure.
This problem often shows up during urgent blood gas testing when a sample is presented but the analyzer either fails to pull the specimen, stops partway through aspiration, or rejects the sample due to suspected clotting. In many cases, the analyzer is not failed — the issue is related to syringe handling, sample age, dried blood at the probe, or a fluid path restriction after repeated testing.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Never troubleshoot a blood gas analyzer while it is actively being used for patient testing. Ensure clinical staff have access to another functioning analyzer before beginning troubleshooting or maintenance.
Verify the device is powered on and fully initialized
- Confirm the analyzer has completed startup and is not in standby, calibration, or maintenance mode. Sample aspiration will not occur if the instrument is performing automated processes.
Confirm the sample type and container are correct
- Verify that the syringe or capillary tube used is compatible with the RAPIDPoint sampling system. Improper containers or adapters may prevent proper aspiration.
Inspect the sample for clots or improper mixing
- Blood gas samples must be properly mixed after collection. Small clots or inadequate mixing can trigger clot detection or block aspiration. Gently roll the syringe if the sample appears separated.
Fresh heparinized samples should be mixed before testing, especially if the syringe has been sitting during transport from the bedside or respiratory area. Even small clots can create intermittent aspiration failures that seem device-related but only occur with certain samples.
Check the sample probe area for visible contamination or obstruction
- Inspect the probe tip and sample port for dried blood, debris, or residue that could restrict sample uptake.
Pay close attention to dried blood around the sample inlet, since buildup at the entry point can cause weak aspiration, partial draws, or repeated clot detection messages even when the sample itself appears acceptable.
Perform the analyzer’s automated probe cleaning function
- Use the system’s maintenance menu to run a probe rinse or cleaning cycle. This often clears minor buildup within the probe.
Verify cartridge installation and status
- Confirm the reagent cartridge is correctly installed and not expired. Some aspiration errors occur when the cartridge fluid pathway cannot support proper sample flow.
Some aspiration errors occur when the cartridge fluid pathway cannot support proper sample flow. If the analyzer appears to have a broader fluid movement issue, see the related guide on sample path blockage or fluidics pump failure.
Check waste and fluid levels
- Ensure the waste container is not full and that system fluids (wash or reagent fluids) are available. Improper fluid levels can interrupt aspiration cycles.
Run a quality control (QC) test
- Running QC can help determine if the aspiration pathway is functioning normally. If QC samples aspirate successfully, the issue may be related to the patient sample. If QC cannot complete or the analyzer remains locked out, see the related guide on calibration failure or QC lockout.
Inspect tubing and sample pathway connections (external areas only)
- Without opening the analyzer, visually check accessible tubing and connections for kinks, disconnections, or leaks that may affect sample flow.
Restart the analyzer
- A controlled reboot can reset fluid handling routines and clear temporary aspiration or sensor errors.
If the Problem Persists
If the analyzer continues to report aspiration failures or clot detection errors after external checks and cleaning procedures, common user and environmental causes have likely been ruled out.
At this point, the issue may involve:
- Internal pump or valve malfunction
- Internal probe obstruction
- Fluid pathway component failure
- Internal clot detection sensor malfunction
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for Clinical Engineering bench evaluation or manufacturer service
Recognizing when internal service is required is an important part of proper troubleshooting.
Clinical Use Tip
Never troubleshoot sample aspiration issues while the analyzer is being used for active patient testing. Ensure clinical staff have access to another functioning blood gas analyzer before performing maintenance or troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
Example:
“Staff reported Siemens RAPIDPoint 500 / 500e would not aspirate patient samples and intermittently displayed clot detection errors during testing.”
Cause
Example:
“Found dried blood residue at the sample inlet/probe area. Sample handling review also identified poorly mixed syringe samples that may have contributed to clot detection.”
Resolution
Example:
“Cleaned accessible sample probe area, performed analyzer probe cleaning cycle, verified cartridge/waste status, and confirmed successful QC/sample aspiration. Unit returned to service.”
Helpful Details to Include (If Known)
- Outlet tested and power confirmed
- Cartridge installation and expiration verified
- Probe cleaning cycle performed
- Waste container checked
- QC testing results
- Visible contamination near probe
- Any alarms or error messages displayed
- Final device status (returned to service or removed from service)
Final Thought
Blood gas analyzers rely heavily on clean fluid pathways and proper sample handling. Many aspiration failures are caused by external issues such as clotted samples or minor probe contamination rather than internal hardware failure. Logical troubleshooting that starts with the sample and external components protects patient testing workflows and reduces unnecessary service calls while maintaining patient safety.
That is successful troubleshooting.