On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots barcode, LIS, and network failures caused by labels, cables, ports, connectivity, interface status, configuration, or external infrastructure.
Step-by-Step Troubleshooting
1. Protect Patient Identification and Result Reporting
Do not rely on automated specimen identification or result transmission when barcode, LIS, or network communication is unreliable.
Use approved laboratory downtime procedures for patient identification, order entry, result verification, and result reporting.
Determine whether the issue affects:
- Barcode reading only
- Incoming orders
- Outgoing results
- Worklist retrieval
- All network communication
- One specimen or all specimens
Expected outcome: The communication failure is clearly scoped and patient-result integrity is protected.
2. Check the Barcode and Specimen Label
For barcode-specific problems, inspect the label for:
- Wrinkles
- Smearing
- Poor print quality
- Damage
- Incorrect placement
- Excessive overlap
- Curvature or obstruction
Compare with a known-good specimen label.
Expected outcome: The barcode is readable and correctly positioned. If a corrected or known-good label reads normally, troubleshooting can stop after verifying normal workflow.
3. Verify the Analyzer's Local Operation
Confirm the ACL TOP 750 LAS itself is otherwise operating normally.
Check whether:
- Samples can be loaded
- The interface is responsive
- The analyzer is in a normal operational state
- Only network-dependent functions are affected
Expected outcome: The problem is isolated to identification or communication rather than a general analyzer failure.
4. Inspect External Network Connections
Check accessible network cabling and connectors for:
- Loose connection
- Damaged cable
- Disconnected patch cable
- Recently moved equipment
- Obvious port damage
Do not move cables between network ports unless the correct port assignment is known.
Expected outcome: The analyzer is physically connected to the intended network path.
5. Check Network and Interface Indicators
Review normal user-accessible status indicators for network or LIS connectivity.
Determine whether there was:
- A recent network outage
- Switch work
- VLAN change
- Interface-engine maintenance
- LIS downtime
- Planned IT maintenance
Coordinate with laboratory IT or integration support when infrastructure is involved.
Expected outcome: The communication path and any wider infrastructure outage are understood.
6. Compare with Other Devices
Determine whether other laboratory analyzers or workstations using the same LIS or network are also affected.
If multiple systems are offline simultaneously, suspect shared infrastructure before the ACL TOP 750 LAS.
Expected outcome: The issue is isolated to the analyzer or identified as a broader LIS/network problem.
7. Verify Communication Configuration Without Changing It
Review user-accessible communication status and confirm the analyzer appears to be using its expected configuration.
Do not alter:
- IP settings
- Interface destinations
- Ports
- Protocol configuration
- Host definitions
- Validated LIS settings
unless the change is authorized, documented, and coordinated with the appropriate support team.
Expected outcome: No unauthorized or unexplained configuration change is identified.
8. Perform End-to-End Verification
After connectivity is restored, verify the complete workflow using approved test data or laboratory procedure:
- Barcode reads correctly
- Order is received if applicable
- Sample is associated with the correct patient/order
- Result transmits
- Result appears at the intended LIS destination
Expected outcome: The complete communication pathway works correctly. Troubleshooting can stop.
If the Problem Persists
If barcode quality, local analyzer operation, cables, network availability, and basic communication status have been verified but communication still fails, common external causes have been ruled out.
The remaining cause may involve the barcode reader, analyzer network interface, interface engine, LIS configuration, network switching or routing, firewall rules, software services, or another infrastructure or service-level issue.
The analyzer or automated interface should be:
- Removed from automated patient-result workflow when identification or transmission cannot be trusted
- Labeled Out of Service as appropriate
- Evaluated by Clinical Engineering, laboratory IT, interface support, or Werfen support as appropriate
- Tested using authorized documentation and approved tools
- Configured only by qualified personnel under controlled change procedures
Do not assume successful network link status means the entire LIS pathway is functioning.
Return automated reporting to service only after end-to-end communication is verified.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Verify the entire path from specimen identification through LIS receipt; a successful barcode read alone does not confirm correct result routing.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Laboratory staff reported that ACL TOP 750 LAS results were not transmitting to the LIS."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the analyzer network cable was loose at the external connection point."
Resolution
What action was taken.
Example:
"Clinical Engineering secured the network connection and verified successful order and result communication through the LIS before restoring automated workflow."
Helpful Details to Include (If Known)
- Exact communication symptom
- Barcode-specific or LIS-wide issue
- One sample or all samples affected
- Label condition
- Network cable and port condition
- Analyzer communication status
- Other devices affected
- Recent network or LIS changes
- Order-receipt test result
- Result-transmission test result
- Final communication status
Final Thought
Protect patient identification and reporting first, verify labels and the physical communication path before changing configuration, and escalate shared network or LIS problems to the proper support team.
That is successful troubleshooting.