Jaeger Medical Vyntus Series

Patient Interface Not Detected

On this page

Asset Type

Pulmonary Function Tester

Manufacturer

Jaeger Medical

Model

Vyntus Series

What This Guide Helps With

This guide assists Clinical Engineering in troubleshooting situations where a Jaeger Medical Vyntus pulmonary function testing system fails to detect the patient interface, such as a mouthpiece, mask, or flow sensor connection. Symptoms may include error messages on the screen, no flow signal during testing, or the system refusing to start measurements. Most issues are related to external connections, sensors, or consumables rather than internal device failures.

Step-by-Step Troubleshooting

Ensure Device Power and Boot Completion

Inspect the Patient Interface for Proper Seating

Check for the Correct Interface Type

Examine Flow Sensor / Interface Cable Connections

Swap with a Known-Good Interface or Flow Sensor

Restart the Device After Interface Check

Check for Software Prompts or Error Messages

If the Problem Persists

After confirming power, interface compatibility, cable integrity, and trying a known-good interface, the issue is likely internal.

Note: Attempting internal repairs beyond sensor/cable replacement is not recommended.

Clinical Use Tip

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
β€œThe Vyntus system does not detect the mouthpiece or mask when attempting spirometry.”

Cause

What was observed during troubleshooting.

Example:
Observed the interface was not seated properly; cable connections intact but device failed to recognize accessory.

Resolution

What action was taken.

Example:
Replaced with a known-good mouthpiece; confirmed detection; system now ready for patient testing.

Helpful Details to Include

Final Thought

Patient safety comes first: never force testing on a device that cannot detect its patient interface. Stepwise, logic-based troubleshooting reduces unnecessary internal repairs and ensures proper documentation. Escalation to service should be done promptly when external checks fail.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide