Hamilton C2

Tightness Test or Flow-Sensor Calibration Fails

On this page

Asset Type

Ventilator

Manufacturer

Hamilton

Model

C2

What This Guide Helps With

Troubleshoots failed tightness testing or flow-sensor calibration caused by circuit leaks, incorrect assembly, damaged accessories, moisture, or sensor connection problems.

Step-by-Step Troubleshooting

1. Protect the Patient and Maintain Ventilation

Do not troubleshoot a ventilator that is providing unreliable ventilation while a patient depends on it. Transfer the patient to another verified ventilator or provide an approved alternate ventilation method before testing.

Inspect the C2 for obvious damage, contamination, unusual odor, overheating, or evidence of fluid intrusion.

Expected outcome: The patient is supported by a reliable alternate method and the ventilator can be evaluated safely.

If patient support has been transferred and no unsafe condition is present, continue troubleshooting.

2. Confirm Which Test Is Failing

Repeat the appropriate preoperational check only when the ventilator is disconnected from the patient. Determine whether the failure occurs during the circuit tightness test, flow-sensor calibration, or both.

Record any displayed message exactly rather than assuming the failure source.

Expected outcome: The specific failed test and repeatability of the problem are confirmed.

If the test now passes and subsequent functional verification is satisfactory, troubleshooting can stop.

3. Inspect the Breathing Circuit for Leaks

Inspect the complete patient circuit, including tubing, connectors, humidification components, test lung connection, caps, adapters, and accessory ports.

Look for loose fittings, cracks, improperly seated components, open sampling ports, damaged tubing, or connections that are not fully engaged.

Expected outcome: The circuit is complete, correctly assembled, and free of obvious leakage.

If correcting a loose or leaking connection allows the test to pass consistently, perform final verification and stop troubleshooting.

4. Inspect the Flow Sensor and Connections

Verify that the correct compatible flow sensor is installed in the proper orientation and that its tubing or electrical connections, as applicable, are fully seated.

Inspect the sensor for contamination, moisture, cracks, bent connections, or physical damage.

Expected outcome: The flow sensor is clean, dry, undamaged, correctly installed, and securely connected.

If reseating or correcting the flow-sensor installation restores successful calibration, proceed to final functional verification.

5. Remove Moisture or Contamination From External Components

Check the breathing circuit and accessible sensor components for condensate or contamination that could alter pressure or flow measurements.

Replace contaminated disposable components rather than attempting unauthorized cleaning or modification.

Expected outcome: External measurement pathways and breathing-circuit components are dry and unobstructed.

If the calibration and tightness test pass afterward, troubleshooting can stop following final verification.

6. Substitute Known-Good External Components

When permitted by facility procedure, substitute a known-good compatible breathing circuit, flow sensor, or other suspect external component one at a time.

Repeat the failed test after each substitution.

Expected outcome: A defective external component is isolated or the failure remains with the ventilator.

If a known-good component corrects the problem, replace the defective accessory and complete return-to-service verification.

7. Verify Exhalation Valve Assembly

Inspect the externally accessible exhalation valve assembly for proper seating, correct assembly, contamination, moisture, or damage.

Do not disassemble internal pneumatic assemblies beyond approved user-removable components.

Expected outcome: The exhalation valve is properly seated and able to support a sealed breathing circuit.

If reseating or replacing an approved external valve component restores the test, complete final verification and stop.

8. Perform Final Functional Verification

Run the complete applicable preoperational checks with a known-good circuit and test lung. Verify that tightness testing and flow-sensor calibration complete successfully and that ventilation and alarms respond normally.

Expected outcome: All required checks pass repeatedly without leakage or calibration failure.

If all checks pass, the ventilator may be returned to service according to facility policy.

If the Problem Persists

If the tightness test or flow-sensor calibration continues to fail after the circuit, sensor, connections, moisture, and externally accessible valve components have been ruled out, the problem may involve an internal pressure/flow measurement pathway, pneumatic leak, internal valve function, or calibration/service issue.

The ventilator should be:

Stopping after external causes have been ruled out is proper troubleshooting.

Clinical Use Tip

Never place a C2 back into patient service after a failed breathing-system test unless the complete required preoperational verification subsequently passes.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Respiratory Therapy reported that the Hamilton C2 failed the tightness test during setup."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found a loose breathing-circuit connection creating an external leak."

Resolution

What action was taken.

Example:
"Reseated the circuit connection, repeated the tightness and flow-sensor checks successfully, and verified normal ventilation and alarm operation with a test lung."

Helpful Details to Include (If Known)

Final Thought

Patient safety comes first. Verify the breathing circuit, flow sensor, external connections, and other simple causes before suspecting internal pneumatic or measurement faults. Escalate when external troubleshooting no longer produces a safe, repeatable result, and document what was found and verified.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide