Werfen GEM Premier 7000

Barcode Scanner or Patient ID Entry Failure

On this page

Asset Type

Blood Gas Analyzer

Manufacturer

Werfen

Model

GEM Premier 7000

What This Guide Helps With

Barcode or patient-identification problems caused by label quality, scanner obstruction, positioning, workflow, touchscreen entry, configuration, or interface issues.

Step-by-Step Troubleshooting

1. Protect Patient Identification

Do not proceed with testing if the patient cannot be positively identified through an approved workflow. Follow the facility's alternate patient-identification procedure or use another verified analyzer.

Never enter guessed or borrowed patient identifiers.

Expected outcome: Patient-to-result association remains accurate throughout troubleshooting.

2. Confirm the Exact Failure

Determine whether the scanner emits no response, reads intermittently, reads the wrong data, rejects a specific barcode, or whether manual patient ID entry is also unavailable.

Record any displayed message.

Expected outcome: The problem is isolated to scanning, manual entry, barcode acceptance, or broader software workflow.

3. Inspect the Barcode Label

Check the affected label for wrinkles, smearing, fading, moisture, glare, damage, incorrect printing, or partial obstruction.

Compare with another clearly printed barcode that is known to work within the facility workflow.

Expected outcome: The barcode presented to the scanner is clear, intact, and appropriate for the configured workflow.

If a known-good label scans normally, the original label or printing process is the likely external cause and troubleshooting can stop.

4. Verify Scanner Positioning

Present the barcode cleanly within the scanner's normal reading area and avoid excessive angle, movement, or glare.

Do not repeatedly sweep damaged labels in ways that increase identification risk.

Expected outcome: A valid barcode is detected consistently when positioned appropriately.

If correct positioning resolves the issue, confirm patient information is populated correctly and troubleshooting can stop.

5. Inspect and Clean the Scanner Window

Inspect the accessible scanner window or optical surface for fingerprints, dried material, dust, or obstruction.

Clean only with methods appropriate for the analyzer and scanner surface.

Expected outcome: The scanner window is clean and optically unobstructed.

If scanning resumes normally after cleaning, verify multiple successful reads and stop.

6. Test Manual Patient ID Entry

If the approved workflow allows it, determine whether patient identification can be entered manually through the touchscreen.

Confirm entered information appears accurately and remains associated with the intended test.

Expected outcome: Manual entry functions normally, helping isolate the issue to the scanner rather than the entire patient-identification workflow.

If manual entry is an approved temporary workflow and the scanner is scheduled for repair, follow facility policy regarding continued use.

7. Verify Configuration and Workflow

Confirm the analyzer is using the expected facility configuration for patient identification and that no recent authorized configuration change altered required barcode formats or entry rules.

Do not modify identification requirements merely to make an incompatible barcode scan.

Expected outcome: Patient-ID requirements match the approved facility workflow.

If an authorized configuration correction restores scanning, test multiple known-good labels before return to normal operation.

8. Perform Final Functional Verification

Scan appropriate known-good barcodes and confirm the correct patient ID is displayed without truncation or substitution. If manual entry was affected, verify that function as well.

Expected outcome: Patient identification is entered accurately and consistently through all required methods.

If achieved, troubleshooting is complete.

9. Escalate Persistent Scanner Failure

If multiple known-good labels fail and the scanner remains nonfunctional after external cleaning and configuration verification, stop troubleshooting.

Do not disassemble the scanner or internal display assembly.

Expected outcome: A probable scanner, interface, software, or internal connection problem is referred for qualified service.

If the Problem Persists

Label quality, scanner positioning, external cleanliness, manual-entry workflow, and approved configuration have been checked. Remaining causes may involve the scanner hardware, internal connections, touchscreen/software systems, or configuration requiring service-level access.

The analyzer should be removed from service if reliable patient identification cannot be maintained. If an alternate approved identification method permits continued use, follow facility policy and risk controls.

When removal is required, the analyzer should be:

Verify patient-ID entry and result association before return to service.

Knowing when an identification problem creates an unacceptable patient-safety risk is proper troubleshooting.

Clinical Use Tip

A technically valid blood gas result associated with the wrong patient is still an unsafe result; verify identity before every test.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the GEM Premier 7000 would not scan patient wristband barcodes."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found contamination on the scanner window while known-good barcodes and manual patient entry were otherwise valid."

Resolution

What action was taken.

Example:
"Cleaned the scanner window using the approved method, verified multiple correct patient barcode reads, and returned the analyzer to service."

Helpful Details to Include (If Known)

Final Thought

Patient identification is a safety function. Check label quality, scanning technique, cleanliness, manual entry, and workflow configuration before assuming hardware failure, then escalate any condition that prevents reliable patient-to-result association.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide