On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies external causes of patient interface detection issues such as loose connections, damaged sensors, incorrect accessories, or improper setup.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the device is not actively in use on a patient.
- Move testing to another spirometer if needed.
Expected Outcome:
Safe environment for troubleshooting without affecting patient care.
Verify Error Message and System Status
- Confirm the exact “patient interface not detected” message.
- Attempt to reconnect and observe if the message clears.
Expected Outcome:
Consistent error confirms a true detection issue.
Why:
Rules out temporary communication glitches or user workflow interruption.
Check Patient Interface Connection
- Inspect the connection between the flow sensor/patient interface and the device:
- Fully inserted
- No looseness
- Proper orientation
- Disconnect and firmly reconnect.
Expected Outcome:
Device recognizes the interface and clears the error.
Why:
Loose or partially connected interfaces are the most common cause.
Inspect Cable and Connector Condition
- Check for:
- Bent or damaged pins
- Frayed or kinked cable
- Debris in connectors
- If damage is found, replace the cable or interface.
Expected Outcome:
Restoring a good connection allows proper detection.
Why:
Physical connection integrity is required for device recognition.
Verify Correct Patient Interface / Sensor Type
- Ensure the correct BD-compatible flow sensor or patient interface is being used.
Expected Outcome:
Using the correct accessory restores functionality.
Why:
Incorrect or incompatible accessories may not be recognized by the system.
Inspect Flow Sensor for Contamination or Moisture
- Check for:
- Condensation
- Debris or residue
- Blockage
- Replace or clean per facility protocol if needed.
Expected Outcome:
Clean sensor allows proper detection and operation.
Why:
Contamination can interfere with sensor recognition and performance.
Power Cycle the Device
- Turn the unit off, wait 10–15 seconds, then power back on.
- Reconnect the patient interface after reboot.
Expected Outcome:
System resets and properly detects the interface.
Why:
Clears temporary software or communication faults.
Try a Known Good Patient Interface
- Swap with a confirmed working flow sensor/interface.
Expected Outcome:
- Works → original interface is faulty
- Still fails → device-side issue likely
Why:
Quickly isolates accessory vs device problem.
If the Problem Persists
If all external causes have been ruled out, the issue is likely internal (sensor port, internal connection, or system board).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Never troubleshoot with a patient connected.
Always move the patient to another spirometer to avoid delays in respiratory assessment.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Unit reports “patient interface not detected” when attempting spirometry testing."
Cause
What was observed during troubleshooting.
Example:
"Failed flow sensor interface due to damaged connector pins."
Resolution
What action was taken.
Example:
"Replaced patient interface with known good unit; device returned to service and verified operational."
Helpful Details to Include (If Known)
- Interface reseated
- Cable condition inspected
- Alternate sensor tested
- Error message behavior
- Indicator lights or prompts
- Device reboot performed
- Final device status
Final Thought
Start with simple connection and accessory checks before assuming device failure. Maintaining a logical approach protects patient care, reduces downtime, and avoids unnecessary repairs. Proper documentation ensures clarity and accountability.
That is successful troubleshooting.