Puritan Bennett 840

Alarm: ↑fTOT Respiratory rate exceeds set limit

On this page

Asset Type

Ventilator

Manufacturer

Puritan Bennett

Model

840

What This Guide Helps With

This guide addresses the ↑fTOT alarm indicating total respiratory rate above the set limit, which may reflect patient distress, ventilator auto-triggering, or improper settings that can impact safe and effective ventilation.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

2. Verify the Reported Alarm and Behavior

3. Check Patient Condition (Most Critical First Step)

4. Check Ventilator Trigger Sensitivity and Settings

5. Inspect Patient Circuit for Leaks or Instability

6. Review Alarm Limits and Ventilator Mode

7. Run System Self Test (SST)

8. Run Extended Self Test (EST)

If the Problem Persists

If the ↑fTOT alarm continues after all external and clinical checks:

Remove the ventilator from service, label it “Out of Service,” and send for repair or further evaluation.

Clinical Use Tip

Never troubleshoot while relying on the ventilator for an unstable patient. Always transition the patient to a backup device before continuing troubleshooting.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Ventilator alarming ↑fTOT with elevated respiratory rate during patient use."

Cause

What was observed during troubleshooting.

Example:
"Patient exhibiting tachypnea and possible auto-triggering due to minor circuit leak."

Resolution

What action was taken.

Example:
"Assessed patient, corrected circuit leak, adjusted trigger sensitivity, and verified normal operation. Removed from service if issue persisted."

Helpful Details to Include (If Known)

Final Thought

High respiratory rate alarms are commonly driven by patient condition rather than device malfunction. Always prioritize patient assessment and external checks before suspecting internal failure. Proper escalation and documentation ensure safe and effective troubleshooting.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide