On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots network and image-transfer failures caused by connectivity, wireless coverage, destination availability, configuration, patient data, or infrastructure problems.
Step-by-Step Troubleshooting
1. Protect Patient Care and Preserve the Examination
Do not allow a DICOM or PACS transfer problem to delay urgent clinical care. Complete imaging as clinically appropriate and preserve images locally if the system allows and local storage is reliable.
Confirm an alternate workflow with clinical staff if images cannot immediately reach PACS.
Expected outcome: Patient care and image preservation are maintained while connectivity is investigated.
2. Confirm the Exact Transfer Failure
Determine whether the Venue Go has no wireless connection, cannot reach a configured destination, fails only when sending images, cannot retrieve a worklist, or fails for one specific destination.
Record any exact on-screen message without paraphrasing it.
Expected outcome: The failed part of the communication path is identified.
3. Verify Basic System Network Status
Check normal user-accessible network indicators and confirm the system is connected to the intended network.
Do not change security settings, wireless credentials, IP configuration, or protected network parameters without authorization.
Expected outcome: The system shows the expected network connection. If it is disconnected, correct only approved accessible connection issues.
4. Check Wireless Location and Signal Conditions
Move the Venue Go within the approved clinical environment to a location known to have reliable wireless coverage.
Observe whether communication changes with location.
Expected outcome: The failure is separated from a coverage or local wireless infrastructure issue. If transfers work in a known-good area, escalate the coverage issue to the appropriate network team.
5. Confirm Scope of the Problem
Determine whether other networked devices in the same area are experiencing similar problems and whether the PACS or DICOM destination is known to be available.
Avoid changing the ultrasound configuration if multiple devices are simultaneously affected.
Expected outcome: A device-specific problem is distinguished from an infrastructure or destination outage.
6. Verify Patient and Exam Data
Confirm that required patient and examination fields are populated appropriately for the intended workflow.
Do not alter clinical identifiers simply to force a transmission.
Expected outcome: The exam contains the information normally required for transfer. Data-entry issues are corrected through the approved workflow when identified.
7. Retry a Controlled Test Transfer
Using an approved test exam or other permitted workflow, attempt transmission to the configured destination.
Observe whether the transfer begins, queues, completes, or fails immediately.
Expected outcome: Successful test transmission confirms the communication path. If transfers complete normally after correcting an external connectivity issue, troubleshooting can stop.
8. Compare Other Configured Destinations When Appropriate
If the system legitimately has more than one configured destination, determine whether the failure occurs with one destination or all destinations.
Do not create, edit, or delete DICOM destinations without authorization.
Expected outcome: A destination-specific failure is differentiated from a device-wide connectivity problem.
9. Verify End-to-End Receipt
When a transfer reports success, confirm with the receiving workflow that the image or approved test study is actually available at the intended destination.
A successful send indication alone does not verify the complete communication path.
Expected outcome: The test image is present at the receiving system. Troubleshooting can stop when normal transfers are confirmed end to end.
10. Escalate Network or Configuration Problems
If the Venue Go remains unable to connect or transfer after wireless coverage, destination availability, local data, and approved settings have been checked, stop external troubleshooting.
Expected outcome: The problem is escalated to the appropriate Clinical Engineering, PACS, networking, or vendor support team without unauthorized configuration changes.
If the Problem Persists
Common external device, wireless, workflow, destination, and data-entry causes have been evaluated. Remaining causes may involve network infrastructure, firewall or routing policy, wireless authentication, DICOM configuration, PACS availability, software, or service-level system configuration.
The Venue Go should be removed from service for the affected network-dependent workflow if reliable image transfer is required and no approved alternate process exists. Label it Out of Service when the device itself is suspected.
Use appropriate GE Healthcare documentation, approved network diagnostic methods, and coordination with PACS or IT personnel. Configuration changes should be made only by qualified and authorized personnel.
Before return to normal workflow, verify a complete test transmission from acquisition through receipt at the intended destination.
Knowing when a connectivity issue belongs with infrastructure or application support is proper troubleshooting.
Clinical Use Tip
Always verify the complete path to the receiving PACS or clinical system rather than assuming a successful local send means the images arrived.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Staff reported Venue Go examinations would save locally but would not transfer to PACS from one treatment area."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering confirmed the ultrasound transferred successfully in another known-good wireless area, isolating the problem to local network coverage rather than the device."
Resolution
What action was taken.
Example:
"Clinical Engineering escalated the wireless coverage issue to the network team and verified successful end-to-end PACS transfer after connectivity was restored."
Helpful Details to Include (If Known)
- Exact displayed network or transfer message
- Wireless connection status
- Location where failure occurs
- Whether other devices are affected
- Worklist versus image-send behavior
- Destination involved
- Local exam save status
- Test transfer result
- Receiving-system confirmation
- Final device status
Final Thought
Preserve patient care and images first, verify connectivity and the complete communication path before changing configuration, separate device problems from infrastructure failures, escalate to the correct support group, and document both send and receipt verification.
That is successful troubleshooting.