On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Unresponsive touchscreen or keypad inputs, delayed response, or inability to navigate menus due to external, environmental, or accessory-related issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Remove the device from patient use and obtain a functioning meter before troubleshooting.
- Expected: No delay in patient testing
- Why it matters: Prevents interruption in glucose monitoring and patient care
Inspect Screen for Contamination or Damage
- Check the touchscreen for dirt, dried solution, glucose residue, or cracks.
- Clean screen using approved disinfectant wipe
- Dry thoroughly
- Expected: Screen is clean and free of residue
- Why it matters: Contamination can block touch sensitivity or cause false inputs
Check for Glove or User Interaction Issues
- Verify the type of gloves being used (if applicable).
- Try operating with clean, dry gloves or bare finger (per facility policy)
- Expected: Device responds normally
- Why it matters: Some gloves or moisture interfere with capacitive touch response
Restart the Device (Soft Reset)
- Power cycle the meter.
- Hold power button until device shuts down
- Restart and test responsiveness
- Expected: Screen responds after reboot
- Why it matters: Temporary software freezes are common and often resolved with reboot
Check Battery Charge and Docking Status
- Low power can affect screen responsiveness.
- Verify battery level
- Place meter in dock and confirm charging indicator
- Expected: Device has adequate charge
- Why it matters: Low voltage conditions can cause erratic behavior
Inspect Docking Station and Contacts
- Poor docking connections may prevent proper charging or communication.
- Check docking pins for damage or contamination
- Try a known-good dock
- Expected: Device charges reliably
- Why it matters: Charging issues can lead to intermittent functionality
Observe for Screen Lag or Partial Response
- Determine if the issue is complete failure or partial responsiveness.
- Attempt multiple areas of the screen
- Note if certain areas respond while others do not
- Expected: Uniform response across screen
- Why it matters: Partial response may indicate digitizer failure rather than software issue
Check for Software Lock or Login Screen Freeze
- Ensure the device is not stuck on a login or QC lock screen.
- Verify prompts on screen
- Attempt navigation or login
- Expected: Device transitions between screens
- Why it matters: Perceived unresponsiveness may be due to workflow restrictions
Swap with a Known Good Device
- Compare behavior with another meter.
- Expected: Known-good device functions normally
- Why it matters: Confirms issue is device-specific and not environmental
If the Problem Persists
If all external causes have been ruled out and the touchscreen or keypad remains unresponsive, the issue is likely internal (digitizer, display assembly, or control board).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Clinical Use Tip
Never troubleshoot a glucose meter while it is actively needed for patient testing. Always transition care to a functioning device first.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Touchscreen not responding to user input during patient testing"
Cause
What was observed during troubleshooting.
Example:
"Touchscreen unresponsive after cleaning and reboot; likely internal digitizer failure"
Resolution
What action was taken.
Example:
"Removed device from service and sent to vendor for repair evaluation"
Helpful Details to Include (If Known)
- Screen condition (clean/damaged)
- Battery level and charging status
- Dock tested with known-good unit
- Response behavior (none, delayed, partial)
- Any visible cracks or fluid exposure
- Final device status (removed from service)
Final Thought
Touchscreen issues are often caused by simple external factors like contamination or power problems. A structured approach ensures patient safety while avoiding unnecessary repairs. Knowing when to escalate is just as important as fixing the issue, and proper documentation supports long-term reliability and tracking.
That is successful troubleshooting.