On this page
Asset Type
Manufacturer
Model
HemoSphere Advanced Monitoring System
What This Guide Helps With
Troubleshooting missing, unstable, or questionable cardiac output and advanced hemodynamic values caused by setup, sensor, cable, module, or signal issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Do not troubleshoot the HemoSphere system in a way that delays patient care or compromises active monitoring.
Action:
- Confirm whether the patient is actively depending on the displayed cardiac output, stroke volume, SVV, ScvO₂, or other advanced parameter values.
- If the values are missing, frozen, or clinically questionable, notify the clinical team and have them use alternate assessment methods or another monitor if needed.
- Do not disconnect invasive lines, catheters, or patient sensors without clinical approval.
Expected outcome: Patient care continues safely while Clinical Engineering evaluates the equipment side of the issue.
Why it matters: Advanced hemodynamic values may influence treatment decisions. Unreliable data should not be treated as accurate until verified.
Verify the Reported Problem
Confirm exactly which value is missing or unreliable.
Action:
Ask staff which parameter is affected, such as:
- Cardiac output
- Cardiac index
- Stroke volume
- SVV
- SVR
- ScvO₂
- Acumen / advanced decision support values
- Pressure-derived parameters
Check whether the issue is:
- No value displayed
- Dashed value
- Intermittent value
- Value present but clinically unrealistic
- Parameter grayed out
- Sensor or module not detected
- Value not updating
Expected outcome: The failure is narrowed to a specific parameter, module, cable, sensor, or setup path.
Why it matters: “Cardiac output not working” can be caused by several different external issues depending on which monitoring technology is being used.
Confirm the Correct Monitoring Setup Is Selected
Verify that the HemoSphere monitor is set up for the intended monitoring mode and connected technology.
Action:
- Check that the correct module, cable, or monitoring mode is selected for the clinical setup being used.
- Confirm that the expected parameter is supported by the connected sensor, cable, and module.
- Verify that the patient profile and monitoring configuration are active and not in a setup or paused state.
Expected outcome: The monitor is in the correct mode and capable of displaying the requested parameter.
Why it matters: Some advanced values only appear when the correct Edwards module, pressure cable, sensor, or oximetry setup is connected and configured.
Check the Patient Cable, Module, and Connector Seating
Inspect all external connections before assuming a monitor failure.
Action:
- Check the front and rear module connections.
- Disconnect and reconnect the appropriate Edwards cable or module if safe and approved by clinical staff.
Inspect connectors for:
- Bent pins
- Loose fit
- Cracked housing
- Fluid contamination
- Cable strain
- Damaged locking tabs
Expected outcome: The module and cable are fully seated and recognized by the monitor.
Why it matters: A loose or damaged cable can cause missing values, intermittent readings, or unreliable hemodynamic calculations.
Check for Sensor or Disposable Setup Issues
Confirm that the correct disposable sensor or patient connection is being used and properly connected.
Action:
- Verify that the FloTrac, Acumen IQ, pressure transducer, oximetry cable, or other connected sensor is appropriate for the intended parameter.
- Confirm the sensor is connected securely to the cable.
- Check for expired, damaged, wet, or previously used disposables if applicable.
- Have clinical staff confirm the invasive line or catheter setup is clinically appropriate and functional.
Expected outcome: The disposable sensor path is intact and suitable for measurement.
Why it matters: Many missing or unreliable values are caused by sensor setup, line condition, or disposable issues rather than the monitor itself.
Verify Pressure Waveform Quality If Pressure-Derived Values Are Affected
If cardiac output or advanced parameters are calculated from arterial pressure, confirm the waveform is usable.
Action:
- Observe the arterial pressure waveform on the monitor.
Look for:
- Flat waveform
- Dampened waveform
- Overly sharp waveform
- Excessive artifact
- Intermittent dropout
- Incorrect scale
- Questionable zero or leveling issue
- Have clinical staff verify the pressure line, transducer position, flush system, stopcock position, and zeroing.
Expected outcome: The pressure waveform is clean, stable, and clinically appropriate.
Why it matters: Pressure-derived cardiac output and advanced parameters depend on waveform quality. A poor waveform can produce missing or unreliable values.
If waveform correction resolves the issue, document the finding and stop.
Confirm Required Patient Data Is Entered Correctly
Some calculated values require accurate patient demographics or setup data.
Action:
Check that required patient information is entered correctly, such as:
- Height
- Weight
- Age
- Sex
- BSA-related fields
- Monitoring mode selections
- Correct any obvious setup omissions with clinical approval.
Expected outcome: The monitor has the required information to calculate indexed or advanced values.
Why it matters: Missing or incorrect patient data can prevent certain calculated values from appearing or can make displayed values unreliable.
Check Alarm, Message, and Status Notifications
Review any on-screen messages that explain why a value is unavailable.
Action:
- Look for displayed messages such as sensor not detected, poor signal quality, invalid waveform, setup incomplete, cable fault, module fault, or parameter unavailable.
- Record the exact wording of any message before clearing or power cycling the monitor.
Expected outcome: The displayed message identifies the likely affected accessory, module, sensor, or setup condition.
Why it matters: The monitor may already be identifying the failed portion of the measurement chain.
Swap External Accessories With Known-Good Parts
Use known-good external parts when available.
Action:
If clinically safe and approved, test with:
- Known-good Edwards cable
- Known-good module
- New compatible disposable sensor
- Known-good pressure cable
- Known-good oximetry cable if applicable
- Do not reuse patient disposables inappropriately.
Expected outcome: The issue follows a cable, module, or sensor, or remains with the monitor.
Why it matters: Controlled accessory swaps help separate monitor failure from external connection or disposable failure.
If a known-bad accessory is identified, remove it from service and stop.
Restart the Monitor Only When Clinically Safe
If the display is not updating, values appear frozen, or the system behavior is abnormal, perform a controlled restart only when patient monitoring can safely continue another way.
Action:
- Ask clinical staff whether monitoring can be interrupted.
- Move the patient to alternate monitoring if needed.
- Power cycle the HemoSphere monitor.
- Allow the system to fully boot.
- Reconnect the module and cables.
- Confirm whether the missing or unreliable values return.
Expected outcome: Temporary software or communication issues clear after restart.
Why it matters: A restart can correct a temporary system lockup, but it should never interrupt critical patient monitoring without a safe backup.
Check Power and Battery Status
Confirm the monitor has stable power.
Action:
- Verify the power cord is fully connected.
- Check the outlet or power strip if applicable.
- Confirm the monitor is not unexpectedly running on battery.
- Look for low battery, charging, or power-related warnings.
Expected outcome: The monitor has stable AC power and is not operating under a power-related fault condition.
Why it matters: Unstable power can contribute to system errors, unexpected shutdowns, or unreliable module communication.
Check Network or Data Export Only If the Values Are Present Locally
If the values appear correctly on the HemoSphere monitor but are missing in the EMR, central display, or data export system, separate the issue from bedside measurement.
Action:
- Confirm whether the value is present on the HemoSphere screen.
If present locally but missing elsewhere, check:
- Network connection
- Data export cable
- Docking or interface connection
- Bed assignment
- Interface status
- EMR mapping or connectivity queue
Expected outcome: The problem is identified as a connectivity/export issue rather than a measurement issue.
Why it matters: A value can be clinically valid on the monitor but still fail to export because of network or interface problems.
Perform a Basic Functional Check Off Patient
If the issue cannot be resolved at the bedside, remove the monitor from patient use and test it in a safe non-patient environment.
Action:
- Use known-good external accessories if available.
- Verify the monitor boots normally.
- Check whether modules are detected.
- Check whether expected screens, parameter selections, and status messages behave normally.
- Do not perform invasive patient-line troubleshooting on the bench.
Expected outcome: Clinical Engineering determines whether the issue is accessory-related, configuration-related, or likely internal to the monitor.
Why it matters: Bench evaluation prevents unnecessary patient disruption and supports better repair decisions.
If the Problem Persists
If the cardiac output or advanced parameter values remain missing, unstable, frozen, or clinically unreliable after checking setup, cables, modules, sensors, waveform quality, patient data, power, and restart behavior, the likely cause is internal monitor failure, module failure, software fault, or a problem requiring manufacturer-level service.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair, bench evaluation, or vendor support
Knowing when to stop is proper troubleshooting. Do not keep returning a monitor to patient use when advanced hemodynamic values cannot be trusted.
Clinical Use Tip
Do not troubleshoot missing or unreliable hemodynamic values on an active patient unless it is safe and clinically approved. If values are being used for treatment decisions, have staff move to another monitoring method or another HemoSphere monitor before equipment troubleshooting continues.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Edwards HemoSphere monitor was not displaying cardiac output and advanced hemodynamic values during patient monitoring."
Cause
What was observed during troubleshooting.
Example:
"Found arterial waveform quality was poor due to an external pressure setup issue, preventing reliable pressure-derived parameter calculation."
Resolution
What action was taken.
Example:
"Clinical staff corrected the pressure setup, waveform returned to normal, cardiac output and advanced parameter values repopulated, and monitor remained in service."
Helpful Details to Include (If Known)
- Exact missing or unreliable parameter
- Whether the value was absent, dashed, frozen, or intermittent
- On-screen error or status message
- Monitoring mode in use
- Module connected
- Cable or sensor type involved
- Whether waveform quality was acceptable
- Whether patient data was complete
- Whether the outlet or AC power was checked
- Whether cables or modules were swapped
- Alarm behavior
- Accessories swapped
- Power behavior
- Environmental factors
- Indicator lights
- Final device status
Final Thought
Troubleshooting missing or unreliable HemoSphere cardiac output values should follow the signal path from patient safety, setup, waveform quality, cables, modules, sensors, and power before assuming internal failure. If the data cannot be trusted after external causes are ruled out, remove the monitor from service and document the complaint, cause, and resolution clearly.
That is successful troubleshooting.