On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots failed wireless connectivity, device assignment, or EMR result transmission involving network access, workflow, configuration, infrastructure, or integration services.
Step-by-Step Troubleshooting
1. Protect the Patient and Preserve Clinical Documentation
Do not assume measurements have reached the medical record until transmission is verified.
If automatic result transmission is unavailable, notify clinical staff and use the facility's approved alternate documentation process. Do not allow failed connectivity to delay necessary patient monitoring or treatment.
Expected outcome: Patient monitoring continues and required results are documented through a reliable alternate process while troubleshooting proceeds.
2. Confirm the Exact Failure
Determine whether the reported problem is:
- Wi-Fi unavailable
- Wi-Fi connected but backend services unavailable
- Device cannot be assigned to a patient, room, or workflow
- Results remain pending
- Results fail to transmit
- Transmission appears successful but results do not reach the EMR
- One monitor is affected or multiple monitors are affected
Record exact messages and indicator states.
Expected outcome: The failure is categorized as wireless, assignment, transmission, or backend integration related.
3. Verify Local Monitor Operation
Confirm the Portrait VSM starts normally and can obtain vital-sign measurements locally.
Verify the touchscreen and workflow controls are responsive.
Expected outcome: The monitor can perform local monitoring even though networked functions are impaired. If local operation is also unstable, remove the monitor from service for broader evaluation.
4. Verify Wireless Status
Check the monitor's normal accessible network-status indicators.
Determine whether:
- Wi-Fi is enabled
- A wireless connection appears established
- Signal availability appears reasonable
- The connection repeatedly drops
- The problem occurs only in one room or area
Do not make unauthorized wireless security or network configuration changes.
Expected outcome: Wireless connectivity is stable. If reconnecting through an approved normal workflow restores communication, verify result transmission and troubleshooting can stop.
5. Check Location and Environmental Factors
Move the monitor within the approved clinical area or compare behavior with another working Portrait VSM nearby.
Determine whether the issue follows:
- The monitor
- A specific room
- A specific access-point area
- A particular floor or department
Expected outcome: The failure is isolated to either the device or the local wireless environment. If the monitor works normally elsewhere, escalate the location-specific network issue rather than replacing monitor hardware.
6. Compare With Another Known-Good Monitor
Test another properly configured Portrait VSM in the same area and workflow.
If the comparison monitor also fails, suspect shared infrastructure, authentication, backend service, or network conditions.
If only the original monitor fails, continue device-specific checks.
Expected outcome: The scope is narrowed to an individual monitor or a shared system problem.
7. Verify Device Assignment
Confirm that the Portrait VSM is assigned through the expected authorized workflow and that the displayed patient, room, bed, or device context is appropriate.
Do not force an assignment or change protected identifiers merely to bypass a transmission problem.
Expected outcome: The monitor is correctly associated with its intended clinical context. If correcting an authorized assignment restores transmission, verify the complete workflow and troubleshooting can stop.
8. Confirm Patient Identification Before Sending Results
Verify that the monitor is associated with the intended patient before attempting a test transmission.
Use approved non-patient or test data where available.
Incorrect patient association is a patient-safety issue and must be corrected before results are sent.
Expected outcome: The correct patient context is established before transmission testing.
9. Test the Result Transmission Workflow
Obtain or enter an approved test measurement and follow the normal transmission workflow.
Observe whether the monitor indicates:
- Pending transmission
- Successful transmission
- Failure
- Retry
- No response
Do not rely solely on a local "sent" indication if downstream confirmation is required by facility workflow.
Expected outcome: The test result successfully passes through the expected transmission process. If the EMR receives it correctly, troubleshooting can stop after final verification.
10. Verify the Downstream Result
When authorized, confirm with the receiving clinical system or appropriate support personnel that the transmitted test result reached the intended destination and patient context.
This distinguishes monitor-side transmission from downstream interface or EMR problems.
Expected outcome: The result is present in the correct receiving system. If so, the communication path is operational.
11. Check for a Shared Infrastructure Problem
If multiple Portrait VSM units fail, determine whether there has been:
- A wireless outage
- An integration-service outage
- An EMR interface interruption
- A recent network change
- A centralized configuration change
- An authentication or certificate-related service issue reported by IT
Clinical Engineering should gather evidence and escalate rather than independently changing enterprise network settings.
Expected outcome: Shared infrastructure failures are routed to the responsible IT, integration, network, or application team.
12. Reboot Only When Clinically Safe and Appropriate
If the monitor is not supporting active patient care and normal workflow permits, perform a controlled restart to clear a temporary communication or application state.
Do not use repeated reboots as a substitute for identifying a persistent fault.
Expected outcome: Network connection, assignment, and transmission recover after restart. If operation remains stable through repeated testing, troubleshooting can stop.
13. Perform Final End-to-End Verification
Before returning the device to normal clinical use, verify:
- Wi-Fi remains connected
- Correct device or location assignment is present
- Correct patient context can be established
- A test result can be transmitted
- The downstream system receives the result correctly
- No unexpected duplicate or misrouted result occurs
Expected outcome: The complete communication path works reliably from monitor to receiving system.
14. Escalate if Communication Still Fails
If device-specific external checks are complete and the failure remains, stop troubleshooting at the external level.
Expected outcome: The monitor or infrastructure issue is escalated to the appropriate service resource without unsafe configuration changes.
If the Problem Persists
Common external causes involving wireless availability, location, workflow, patient association, device assignment, and basic transmission steps have been ruled out.
The remaining issue may involve internal wireless hardware, monitor software, enterprise wireless infrastructure, authentication, centralized configuration, middleware, interface engines, device-management services, or the EMR.
For a failure isolated to one monitor, the device should be:
- Removed from service if reliable required connectivity cannot be assured
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate GE Healthcare documentation and approved test equipment
- Repaired or configured only by qualified personnel
For a multi-device or location-wide problem, escalate to the responsible network, integration, application, or vendor support team.
After correction, verify the complete path from patient/device assignment through result transmission and receipt in the intended clinical system before return to normal use.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
A local "sent" indication is not enough when connectivity is in question; confirm the result reached the correct patient and receiving system.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Portrait VSM obtained vital signs normally but would not transmit results to the EMR."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found that the monitor had lost its expected wireless connection in the affected care area while another Portrait VSM showed the same condition."
Resolution
What action was taken.
Example:
"Escalated the shared wireless issue to network support, then verified restored Wi-Fi connectivity, correct device assignment, and successful end-to-end test-result transmission after service was restored."
Helpful Details to Include (If Known)
- Exact network or transmission message
- Wi-Fi status
- Area or room where failure occurred
- Whether the issue followed the monitor
- Whether other Portrait VSM units were affected
- Device-assignment status
- Patient-association status
- Transmission status shown on the monitor
- Whether the receiving system received the result
- Known infrastructure outage or recent change
- Results before and after restart
- End-to-end verification results
- Final device status
Final Thought
Maintain patient monitoring and documentation first, separate device problems from shared network and integration failures, verify the complete communication path before assuming hardware failure, escalate to the correct service group, and document both the technical findings and final end-to-end verification.
That is successful troubleshooting.