Fetal oxygen saturation monitors

Philips FSpO2: troubleshooting and error codes

The ServiceForge knowledge base holds 11 documented symptoms for the Philips FSpO2, with 20 ranked causes, 15 diagnostic checks with test points and expected values, and 0 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

Sensor resterilization or reuse causes safety hazards patient safety

Factory-sterilized FS-14 sensors should not be resterilized or reused; doing so risks bacterial/viral contamination, measurement inaccuracy from damage, ethylene oxide toxicity, and pyrogenic reactions.

Ranked causes

1. Inadequate resterilization allowing bacterial or viral contamination (common)
2. Sensor damage during cleaning, disinfection or resterilization (common)
3. Ethylene oxide residuals from resterilization (occasional)
4. Pyrogenic reactions from foreign proteins (occasional)

Inaccurate saturation readings due to optical shunting patient safety

Erroneous fetal saturation values caused by light from sensor emitter reaching photodetector without passing through tissue, disrupting normal sensor operation and affecting reading accuracy.

Ranked causes

1. Vernix or meconium present on fetal skin (common)
2. Lightly colored hair between sensor and fetal skin (occasional)
3. Excessive sensor force causing skin blanching (occasional)

First check

Inspect fetal skin surface for vernix, meconium, or debris

Test point: Fetal skin under sensor contact area
Expected: Clean skin without vernix, meconium, or excess material

2 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Calibration: N-400 fetal oxygen saturation monitor patient safety

Factory calibration procedure for establishing accuracy of the N-400 system by comparing instrument readings to actual arterial oxygen saturation values using controlled hypoxia studies and hemoximeter analysis.

Ranked causes

1. Accuracy establishment required for clinical use (common)
2. Precision and reproducibility verification (common)

First check

Obtain arterial blood samples from human volunteer subjects under controlled hypoxia

Test point: Arterial blood
Expected: Samples analyzed by laboratory hemoximeter

2 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Inaccurate measurements due to caput or hair at sensor site

Presenting crown application sites with caput or hair prevent accurate reflectance sensor measurements through shunting and light absorption.

Ranked causes

1. Caput causing blood shunting through edematous area (common)
2. Hair preventing sensor contact with fetal scalp or absorbing light (common)

First check

Inspect fetal scalp at intended sensor site for caput or significant hair

Test point: presenting crown or alternative application site
Expected: skin clear of caput; minimal hair present

Sensor not contacting tissue patient safety

Front-panel indicator on monitor notifies clinician that sensor optical components are not touching fetal tissue; occurs when conductive contacts are immersed in amniotic fluid rather than touching wet tissue

Ranked causes

1. Sensor immersed in amniotic fluid (common)
2. Conductive contacts coated with vernix or solid material (occasional)

First check

Verify sensor is contacting tissue via impedance measurement

Test point: Contact electrodes on sensor
Expected: High impedance when contacting wet tissue; low impedance when immersed in amniotic fluid

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Signal not from fetal arterial source patient safety

Measured signal is not of fetal and arterial origin; potential interfering signals include maternal pulses or rhythmic motion artifact

Ranked causes

1. Optical components facing uterus instead of fetal face (occasional)
2. Rhythmic motion artifact (unknown)

First check

Verify N-400 pulse qualification algorithm confirms fetal arterial signal

Test point: Monitor display
Expected: N-400 confirms signal is of fetal and arterial origin

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Excessive sensor temperature during operation patient safety

LED operation at maximum current may elevate sensor temperature; thermal safety was validated in worst-case nonperfused tissue scenario.

Ranked causes

1. LEDs driven at maximum current in nonperfused tissue (rare)

First check

Measure temperature increase on sensor during maximum LED current operation

Test point: sensor surface
Expected: less than or equal to 3.0°C above baseline, ≤ 3.0°C

Inaccurate measurements at scalp with caput patient safety

Significant shunting through edematous area reduces measurement accuracy when caput is present on fetal scalp

Ranked causes

1. Caput (scalp swelling) present at application site (common)

First check

Inspect fetal scalp for caput (swelling/edema)

Test point: Presenting crown and application site
Expected: No significant caput present

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Inaccurate measurements at scalp with hair patient safety

Dark hair prevents sensor contact with scalp and absorbs light, causing shunting and signal loss

Ranked causes

1. Dark hair at application site prevents sensor contact (common)

First check

Inspect application site for hair coverage and color

Test point: Presenting crown and scalp area
Expected: Minimal or light-colored hair for good sensor contact

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Loss of saturation readings during contractions

Fetal oxygen saturation values not reported during labor contractions due to loss of local pulsatile activity under compressed sensor.

Ranked causes

1. Sensor compression during forceful contractions (common)

First check

Verify sensor position relative to pelvic bone and fetal anatomy

Test point: Sensor placement on fetal scalp
Expected: Sensor positioned on prominent area not between fetal head and hard surface

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Reduced signal amplitude from hair and caput

Signal quality degraded by interference from fetal hair or caput succedaneum at non-preferred sensor placement sites

Ranked causes

1. Sensor placed on area with hair or caput (occasional)

First check

Verify sensor placed on cheek or temple area

Test point: Fetal face location
Expected: Sensor on cheek or temple area as shown in Figure 5

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Community

0 fixes logged by technicians through their AI, with outcomes, for this model.

ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.