GE Healthcare AMX Series

Image Transfer, Cassette/Detector, or Workstation Communication Failure

On this page

Asset Type

Mobile X-Ray System

Manufacturer

GE Healthcare

Model

AMX Series

What This Guide Helps With

Image transfer, cassette/detector recognition, or workstation communication issues preventing images from reaching review or PACS systems.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Do not troubleshoot image transfer or detector communication problems during an active patient exam if repeat exposure risk is present.

Action:

Expected outcome: Patient care continues without unnecessary delay or avoidable repeat radiation exposure.

Why it matters: Communication failures can lead to missing images, repeated exposures, delayed diagnosis, or incomplete exam documentation.

Verify the Reported Problem

Confirm exactly where the failure occurs.

Action:

Expected outcome: The issue is narrowed to detector connection, image acquisition, workstation transfer, or network/PACS communication.

If the problem is only with PACS transfer but images are stored locally, do not assume the detector or generator failed.

Confirm the Correct Detector or Cassette Is Being Used

Verify that the detector, cassette, or image receptor belongs with the unit and is approved for that system configuration.

Action:

Expected outcome: The AMX system is being used with the correct detector or cassette.

If the wrong detector was used, return the correct detector to the unit, repeat detector recognition if required, and stop if communication is restored.

Check Detector Power and Battery Status

For wireless detector configurations, confirm the detector has adequate battery charge.

Action:

Expected outcome: The detector powers on and becomes available to the mobile unit.

If the detector reconnects after battery replacement or reseating, document the battery condition and stop.

Inspect Detector or Cassette for Physical Damage

Check for obvious external damage before continuing.

Action:

Expected outcome: No visible physical damage is present.

If damage is found, remove the detector from service and send it for repair evaluation. Do not continue using a damaged detector for patient imaging.

Verify Detector Seating, Docking, or Cable Connection

If the AMX configuration uses a docking bay, tether, reader, or cassette interface, check all external connections.

Action:

Expected outcome: The detector/cassette is recognized by the system.

If reseating or cable replacement resolves the issue, document the failed connection or cable and stop.

Restart the Image Acquisition Application

A software session may be frozen even when the mobile unit itself is powered.

Action:

Expected outcome: The acquisition workstation reconnects to the detector and resumes normal workflow.

If the detector or image queue returns after restarting the application, verify image transfer with a test or non-patient workflow and stop.

Power Cycle the Mobile X-Ray Unit Safely

If the detector and connections appear normal, perform a controlled restart.

Action:

Expected outcome: The unit boots normally and communication is restored.

If the issue clears after restart, document it as an intermittent communication/software lockup and monitor for recurrence.

Check Local Image Storage or Exam Queue

Determine whether images are being captured but not transferred.

Action:

Expected outcome: You can tell whether acquisition failed or transfer failed after acquisition.

If images are stored locally but not sending, focus on network, destination, AE title, worklist, or PACS communication rather than detector hardware.

Verify Network Connection

Mobile X-ray units often depend on wireless or wired network connection for worklist and image transfer.

Action:

Expected outcome: The AMX has active network connectivity.

If transfer works in another area, document possible wireless coverage or network access issue and notify IT/PACS support as needed.

Confirm Worklist and Patient Data Communication

If the issue involves missing patients or failed worklist lookup, separate worklist communication from image transfer.

Action:

Expected outcome: Worklist communication is confirmed or identified as failed.

If worklist is unavailable but image transfer still works manually, document the issue as a worklist communication problem rather than detector failure.

Check Destination or PACS Transfer Status

If images acquire locally but do not reach PACS, verify destination communication.

Action:

Expected outcome: The failure is identified as local device communication or downstream PACS/network issue.

If multiple imaging devices are affected, escalate to IT/PACS rather than treating the AMX as the primary failure.

Check for Date, Time, or System Identification Issues

Incorrect system time or identification can interfere with worklist matching, image routing, and exam reconciliation.

Action:

Expected outcome: The unit has correct time, identity, and exam routing behavior.

If configuration appears incorrect, escalate to imaging IT, PACS administrator, or service support.

Test With a Known-Good Detector or Workflow

If available, use a known-good detector, cassette, battery, or test workflow to isolate the fault.

Action:

Expected outcome: The issue follows either the detector/cassette, the mobile unit, or the network/workstation path.

If the fault follows the detector, remove the detector from service.

If the fault stays with the AMX unit, remove the unit from service for bench evaluation.

If the fault follows network location or routing, escalate to IT/PACS.

Review Error Messages and Logs Without Deep Service Action

Record any displayed communication, detector, workstation, image transfer, or DICOM errors.

Action:

Expected outcome: Repair, PACS, or vendor support has useful details for troubleshooting.

Do not perform deep internal service, board replacement, or configuration changes unless trained and authorized for that GE AMX configuration.

If the Problem Persists

If detector power, cassette seating, external cables, software restart, network status, worklist behavior, and PACS transfer status have been checked, common external causes have been ruled out.

The problem is likely related to an internal detector interface, acquisition workstation, wireless communication module, software/database issue, DICOM configuration, or internal system communication fault.

The device should be removed from service, labeled Out of Service, and sent for repair, bench evaluation, imaging IT review, or vendor support as appropriate.

Knowing when to stop is proper troubleshooting. Continuing to force imaging attempts can create repeat exposure risk, lost images, incomplete exams, and clinical delays.

Clinical Use Tip

Do not troubleshoot image transfer problems while a patient is waiting on the same unit if another mobile X-ray system is available. Move the exam to a known-working unit first, especially when repeat imaging may increase radiation exposure or delay care. Maintain therapy and imaging continuity by using a backup device before troubleshooting continues.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the GE AMX mobile X-ray system completed exposure but images did not transfer to the workstation/PACS."

Cause

What was observed during troubleshooting.

Example:
"Troubleshooting found the detector was recognized locally, but completed studies remained in the failed send queue due to network/PACS communication failure."

Resolution

What action was taken.

Example:
"Verified detector battery, reseated external connections, restarted the acquisition workstation, confirmed local image storage, documented failed transfer behavior, and escalated to PACS/IT while removing the unit from service pending verification."

Helpful Details to Include (If Known)

Final Thought

Image transfer and detector communication failures should be handled logically. Start with patient safety, then verify the detector, battery, cassette, cables, software session, network connection, and PACS/worklist path. If external causes are ruled out, remove the unit from service and escalate with clear CCR documentation so repair, PACS, or IT support can act quickly.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide