On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoot unavailable wireless connectivity, patient identification, or EMR result transmission caused by network, workflow, assignment, or integration problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety and Preserve Clinical Documentation
Confirm that vital signs can still be measured reliably.
If automatic transmission is unavailable, notify clinical staff to use the approved manual documentation process.
Do not assume that a displayed or locally saved measurement has reached the patient's electronic record.
Expected outcome: Clinical measurements remain available and documentation continues without relying on failed transmission.
2. Identify the Exact Failure Point
Ask staff whether the monitor:
- Cannot connect to Wi-Fi.
- Connects but cannot retrieve patient information.
- Displays an incorrect patient assignment.
- Accepts measurements but does not transmit them.
- Reports a transmission error or pending result.
Record the exact displayed status.
Expected outcome: The problem is narrowed to wireless connectivity, patient identification, or downstream result delivery.
3. Verify Basic Monitor Operation
Confirm that the monitor powers on, displays vital signs correctly, and responds to its controls.
Check the displayed date and time for obvious discrepancies.
Do not change time synchronization or protected network settings without authorization.
Expected outcome: The monitor functions normally apart from the reported communication issue.
4. Check Wireless Connection Status
Review the monitor's available wireless status indicators.
Confirm whether the device reports a connection to the expected approved clinical network.
Check for obvious environmental factors such as operation in an area with poor wireless coverage.
Expected outcome: The monitor reports an appropriate network connection or provides a specific connection failure indication.
5. Compare With Another Monitor
Check whether another approved Connex Spot Monitor in the same area can complete the intended workflow.
If multiple devices fail in the same location, consider wireless infrastructure or application availability.
If only one monitor fails, consider its assigned configuration, wireless interface, or device-specific registration.
Expected outcome: The comparison helps distinguish a local device issue from a broader infrastructure problem.
6. Verify Patient Identification and Assignment
Using approved test data or an authorized workflow, confirm that the correct patient and encounter can be selected.
Check for mismatched patient identifiers, missing encounters, or incomplete device assignment.
Do not transmit test results into an actual patient chart.
Expected outcome: The intended patient identification workflow completes without mismatched records.
7. Verify Result Transmission
Use an approved test environment or coordinated clinical integration test.
Confirm whether the result leaves the monitor, reaches the receiving system, and appears in the intended record.
Coordinate with IT or the interface team when downstream confirmation is required.
Expected outcome: The complete communication path is verified, not merely the monitor's local transmission indication.
If successful transmission is confirmed and the issue no longer occurs, troubleshooting can stop.
8. Escalate Network or Integration Problems
Provide the appropriate IT, clinical informatics, or vendor support team with the device identifier, location, timestamps, and observed messages.
Do not independently modify managed wireless settings, certificates, interface destinations, or enterprise configuration packages.
Expected outcome: The responsible support team receives enough information to isolate the remaining failure.
If the Problem Persists
Common device-level and external workflow causes have been ruled out. Remaining possibilities include wireless infrastructure problems, authentication or certificate issues, patient-assignment mismatches, interface engine failures, or authorized device configuration problems.
Remove the monitor from connected clinical service, label it Out of Service, and arrange bench evaluation or coordinated service review when its required workflow cannot be supported. Any temporary use for local measurements must be separately authorized under facility policy.
Qualified personnel should use manufacturer documentation, approved test equipment, and authorized IT procedures. Confirm end-to-end patient identification and result delivery before returning the connected workflow to service.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
A successful Wi-Fi connection does not confirm that a vital signs result reached the correct patient chart.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Connex Spot Monitor collected vital signs but would not transmit results to the EMR."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering and IT confirmed that the monitor was operating in an area with insufficient approved wireless coverage."
Resolution
What action was taken.
Example:
"Coordinated wireless coverage correction with IT and verified successful test-result transmission to the intended receiving record."
Helpful Details to Include (If Known)
- Exact connection or transmission message.
- Device identifier and affected location.
- Wireless connection status.
- Patient-ID or encounter behavior.
- Date and time of failed transmission.
- Comparison with other monitors.
- IT or integration findings.
- End-to-end verification results.
- Final connected-service status.
Final Thought
Connected monitoring requires both accurate measurements and reliable documentation. Verify the monitor, network, patient assignment, and receiving system in logical order, avoid unauthorized changes, escalate infrastructure failures, and record the confirmed resolution.
That is successful troubleshooting.