On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots parameter failures involving sensors, cuffs, tubing, sampling accessories, patient connection, module detection, settings, or external accessory faults.
Step-by-Step Troubleshooting
1. Maintain Required Patient Monitoring
If NIBP, SpO2, or CO2 monitoring is clinically required and the DEFIGARD Touch 7 cannot obtain a dependable reading, provide the parameter using another verified monitor before troubleshooting.
Do not rely on intermittent or unreliable parameter data.
Expected outcome: Required monitoring remains available throughout evaluation.
2. Identify the Affected Parameter
Determine whether the problem involves:
- NIBP.
- SpO2.
- CO2.
- Multiple parameters simultaneously.
Record any displayed message and whether the parameter is detected but not producing a value.
Expected outcome: The failure is isolated to one monitoring path or identified as a broader device problem.
3. Inspect the Patient Accessory
For the affected parameter, inspect the external accessory:
NIBP
- Cuff condition.
- Correct tubing connection.
- Kinks.
- Leaks.
- Damaged connectors.
SpO2
- Sensor condition.
- Cable connection.
- Contamination.
- Damaged optical surfaces.
- Excessive ambient light or motion.
CO2
- Sampling line.
- Airway adapter.
- Water trap or moisture-management accessory, when present.
- Kinks or blockages.
- Loose connections.
Expected outcome: The accessory path is intact and correctly connected.
4. Replace Disposable or Easily Substituted Accessories
Use an approved known-good cuff and hose, SpO2 sensor, or CO2 sampling accessory as applicable.
Change one component at a time when practical.
Expected outcome: If the reading returns with a known-good accessory, remove the failed accessory from service and proceed to final verification.
5. Verify Module or Parameter Detection
Confirm the parameter is shown as available by the DEFIGARD Touch 7 and that no obvious module-disconnected or sensor-disconnected condition remains.
Reconnect any approved external module or accessory connection that is intended to be user-removable.
Expected outcome: The parameter is recognized and ready to acquire data.
6. Check Patient and Environmental Factors
When troubleshooting a clinical report, consider external causes such as:
- Patient motion.
- Poor perfusion affecting SpO2.
- Incorrect cuff placement or size selection.
- Loose CO2 sampling connection.
- Condensation or secretion blockage.
- External light interference.
Use a simulator or analyzer for technical verification rather than relying solely on a patient comparison.
Expected outcome: Patient-dependent factors are separated from equipment performance.
7. Verify User-Accessible Settings
Confirm that normal parameter settings and monitoring modes have not unintentionally disabled the measurement or prevented acquisition.
Do not change protected configuration without authorization.
Expected outcome: The parameter is enabled and configured appropriately for testing.
8. Test With Approved Simulation Equipment
Remove the unit from clinical use and use appropriate approved test equipment for the affected parameter, such as:
- NIBP simulator/analyzer.
- SpO2 simulator when compatible with the installed technology.
- CO2 simulator or gas source approved for the test method.
Expected outcome: The parameter acquires and displays a stable test value according to the applicable verification procedure.
9. Compare With Known-Good Accessories or Configuration
If available, compare the suspect parameter using known-good accessories from another verified compatible system.
Avoid changing protected hardware configuration solely for troubleshooting.
Expected outcome: The fault is isolated to the accessory or remains with the DEFIGARD Touch 7.
10. Perform Final Functional Verification
Repeat the measurement several times as appropriate for the parameter and confirm stable acquisition without disconnect or error indications.
Expected outcome: The affected parameter produces repeatable, reliable readings. If so, document the correction and return the device to service.
If the Problem Persists
Accessories, patient-interface factors, connections, settings, and approved simulator testing have been addressed. The remaining problem may involve the parameter module, connector interface, pneumatic system, sampling system, sensor electronics, or another internal service-level fault.
The device should be:
- Removed from service if the affected parameter is required for its assigned clinical use.
- Labeled Out of Service.
- Sent for repair or bench evaluation.
- Evaluated using appropriate manufacturer documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
Complete parameter-specific verification and overall functional testing before return to service.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Use a known-good accessory and an appropriate simulator to separate patient conditions and disposable-accessory problems from an actual parameter-module failure.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Staff reported that the DEFIGARD Touch 7 SpO2 parameter detected the sensor but would not display a saturation reading."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found that the SpO2 sensor produced no reading on the device while a known-good compatible sensor operated normally."
Resolution
What action was taken.
Example:
"Replaced the defective SpO2 sensor and verified stable parameter acquisition and display during functional testing."
Helpful Details to Include (If Known)
- Parameter affected.
- Exact message displayed.
- Accessory type and condition.
- Connections inspected.
- Known-good accessory result.
- Patient or environmental factors observed.
- Simulator or analyzer result.
- Whether multiple parameters were affected.
- Results before and after correction.
- Final device status.
Final Thought
Start with the external patient-accessory path, then use known-good accessories and appropriate analyzers to isolate the problem before assuming a module failure. Maintain alternate monitoring whenever readings are unreliable and document the verified correction or escalation clearly.
That is successful troubleshooting.