Haemonetics TEG 6s

Touchscreen, Software Freeze, or Startup Self-Test Failure

On this page

Asset Type

Viscoelastic Hemostasis Analyzer

Manufacturer

Haemonetics

Model

TEG 6s

What This Guide Helps With

Troubleshoots unresponsive controls, frozen software, abnormal startup, and self-test failures using power, accessories, environment, and restart checks first.

Step-by-Step Troubleshooting

1. Protect Patient Testing

Do not troubleshoot an unstable or frozen analyzer while it is being relied on for patient testing.

Move required coagulation testing to another verified analyzer or approved alternate method.

Expected outcome: Patient testing continues independently of the affected analyzer.

2. Confirm the Exact Failure

Determine whether:

Record the exact screen condition or message.

Expected outcome: The failure is clearly characterized.

3. Check for External Touchscreen Obstruction

Inspect the screen for:

Clean and dry the screen using approved methods.

Expected outcome: The touchscreen surface is clean, dry, and unobstructed. If normal response returns, troubleshooting can stop after verification.

4. Disconnect Nonessential External Accessories

If permitted, disconnect nonessential externally connected USB or peripheral accessories that could be contributing to startup or software instability.

Do not disconnect required infrastructure during active testing.

Expected outcome: The analyzer starts or operates normally without the suspect accessory. If so, evaluate that accessory separately.

5. Verify AC Power

Check:

Use a known-good outlet or approved power check when needed.

Expected outcome: Reliable AC power is confirmed.

6. Perform a Controlled Restart

When no assay is active, perform a normal shutdown and restart using the intended controls.

Avoid repeated rapid power cycling.

Expected outcome: The analyzer completes startup and reaches a stable ready screen.

7. Observe Startup Behavior

Watch for:

Expected outcome: Startup completes normally without recurring error or freeze.

8. Verify Touchscreen Function Across the Interface

After startup, test normal navigation across several screen areas without entering or changing protected settings.

Expected outcome: Touch inputs are accurate and consistent across the required user interface.

9. Perform Functional Verification

Confirm:

Use an approved non-patient verification process.

Expected outcome: The analyzer remains stable and responsive through repeated basic operation. Troubleshooting can stop if all required verification passes.

10. Escalate Recurrent Freeze or Self-Test Failure

If the analyzer repeatedly freezes, fails startup, or reports a recurring self-test failure, remove it from service.

Expected outcome: The unreliable analyzer is prevented from use until qualified technical evaluation is completed.

If the Problem Persists

External touchscreen contamination, accessories, AC power, and normal restart have been ruled out. Remaining categories may involve touchscreen hardware, internal electronics, storage, operating software, startup diagnostics, or another service-level condition.

The device should be:

Perform complete startup, user-interface, functional, and required QC verification before return to service.

Knowing when to stop external troubleshooting is proper troubleshooting.

Clinical Use Tip

Intermittent software or touchscreen operation is not acceptable simply because the analyzer eventually restarts; reliability must be demonstrated before clinical use.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Laboratory staff reported that the TEG 6s touchscreen became unresponsive during setup and the analyzer appeared frozen."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found cleaning residue and moisture on the touchscreen surface, while the analyzer completed startup normally after the screen was cleaned and dried."

Resolution

What action was taken.

Example:
"Cleaned and dried the touchscreen using approved practices, verified normal touch response and stable operation through repeated navigation, and returned the analyzer to service."

Helpful Details to Include (If Known)

Final Thought

Protect testing continuity, check the display surface and external conditions before assuming software or hardware failure, verify stable operation after correction, and escalate recurring startup or interface problems.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide