On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Barcode scanning failures caused by damaged labels, poor positioning, contamination, lighting, configuration, scanner-window damage, or meter communication problems.
Step-by-Step Troubleshooting
1. Protect Patient Identification
Do not allow a barcode problem to cause testing under the wrong patient or operator identity.
If the facility permits an approved alternate identification workflow, clinical staff may use it. Otherwise, move testing to another verified meter.
Expected outcome: Patient and operator identification remain accurate while troubleshooting proceeds.
2. Confirm Which Barcodes Fail
Determine whether the scanner fails with patient wristbands, operator badges, strip information, or all barcode types.
Record whether the scanner produces any illumination, tone, or response when activated.
Expected outcome: The failure is narrowed to one barcode source or the scanner function generally.
3. Inspect the Barcode
Check the label for wrinkles, moisture, blood, fading, abrasion, glare, printing defects, or physical damage.
Try another known-good barcode of the same type.
Expected outcome: A clean, readable barcode is available for testing.
If another barcode scans normally, the original label is the likely cause and meter troubleshooting can stop.
4. Clean and Inspect the Scanner Window
Inspect the scanner window for fingerprints, blood, disinfectant residue, scratches, clouding, cracks, or moisture.
Clean only using approved external methods.
Expected outcome: The scanner window is clean, clear, and undamaged.
If scanning returns to normal, perform final verification and stop.
5. Check Positioning and Lighting
Test the scanner at reasonable distances and angles using a known-good barcode.
Avoid severe glare or direct reflections that may interfere with scanning.
Expected outcome: The scanner reliably reads when presented with a clear barcode under normal conditions.
6. Test Several Barcode Types
When permitted, test known-good patient, operator, and applicable consumable barcodes.
Determine whether one barcode format fails while others work normally.
Expected outcome: The problem is isolated to either a specific barcode type or the scanner itself.
7. Verify Approved Configuration
Check only accessible, authorized configuration information related to barcode use.
Do not change symbologies, security settings, or other configuration merely to experiment unless directed by approved institutional or manufacturer documentation.
Expected outcome: The meter is configured for the barcode workflows intended by the facility.
8. Compare With Another Meter
Scan the same barcode using another verified StatStrip.
If the barcode also fails on the comparison meter, investigate the label or barcode-generation process rather than the suspect meter.
Expected outcome: The comparison identifies whether the problem follows the barcode or the meter.
9. Perform Final Functional Verification
After cleaning, barcode replacement, or approved configuration correction, scan several known-good barcodes and confirm that the resulting identification information is correct on the meter.
Expected outcome: Multiple barcodes scan consistently and populate the correct identification fields.
If successful, troubleshooting can stop.
10. Remove From Service for Persistent Scanner Failure
If known-good barcodes cannot be read despite a clean scanner window and correct approved configuration, remove the meter from service.
Expected outcome: A meter with unreliable patient-identification capability is prevented from clinical use.
If the Problem Persists
Common external barcode, contamination, lighting, and positioning problems have been ruled out. Remaining possibilities include scanner hardware failure, internal connection problems, configuration corruption, or an institutional barcode-format issue.
The meter should be:
- Removed from service when accurate identification cannot be assured.
- Labeled Out of Service.
- Sent for repair or bench evaluation.
- Evaluated using appropriate Nova Biomedical documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
- Verified for correct patient and operator barcode recognition before return to service.
Knowing when unreliable identification requires escalation is proper troubleshooting.
Clinical Use Tip
Never permit scanner failure to create uncertainty about which patient a glucose result belongs to.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Nursing reported that the StatStrip would not scan patient wristband barcodes."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found dried disinfectant residue obscuring the scanner window while known-good wristbands scanned normally after cleaning."
Resolution
What action was taken.
Example:
"The scanner window was cleaned using the approved method and multiple patient and operator barcodes were successfully verified before return to service."
Helpful Details to Include (If Known)
- Barcode type affected
- Whether scanner illumination occurs
- Label condition
- Scanner-window condition
- Known-good barcode results
- Comparison-meter results
- Lighting or glare conditions
- Configuration observed
- Correct identification verification
- Final device status
Final Thought
Protect patient identification first, verify labels and scanner-window condition before assuming hardware failure, compare against known-good barcodes and meters, and escalate when accurate identification cannot be assured.
That is successful troubleshooting.