On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots wireless connectivity, data transfer, network access, external communication, configuration, and authorized software update problems without altering therapy functions.
Step-by-Step Troubleshooting
1. Separate the Connectivity Issue From Therapy Safety
Confirm whether the problem affects only data or software services or whether ventilation, alarms, or another therapeutic function is also impaired.
If therapeutic or alarm performance is affected, remove the VOCSN from patient use and troubleshoot that safety-critical problem separately.
Do not interrupt active patient therapy solely to troubleshoot nonessential connectivity.
Expected outcome: Clinical functions are confirmed safe, and the communication problem is isolated from therapy performance.
2. Identify the Failed Communication Function
Determine whether the complaint involves:
- Cellular communication
- Wi-Fi connectivity
- Data upload or synchronization
- External data service
- Software update download
- Software update installation
- Loss of previously working connectivity
Record the displayed status or message and when the problem began.
Expected outcome: The affected service and point of failure are clearly defined.
3. Verify Basic Device and Network Conditions
Confirm the VOCSN is fully powered and operating normally.
For wireless communication, verify the device is in an area where the expected network or cellular service is available. Compare with another known-working device when appropriate.
If facility Wi-Fi is involved, confirm there has not been a network outage, access-point failure, credential change, segmentation change, or security-policy change.
Expected outcome: Basic network availability and signal environment are confirmed.
If restoring facility connectivity resolves the problem, verify data transfer and troubleshooting can stop.
4. Inspect External Communication Accessories
If the communication method uses an external module, cable, accessory, or data interface, inspect connections for looseness, damage, or contamination.
Reseat removable external connections when permitted and compare with known-good accessories where available.
Expected outcome: External communication hardware is securely connected and physically intact.
5. Verify Approved Communication Configuration
Review only authorized user-accessible communication settings and confirm they match the institution's documented configuration.
Do not alter protected network, security, device identity, or service configuration without appropriate authorization.
Coordinate with hospital IT, cybersecurity, or the responsible respiratory device administrator when the problem involves managed network infrastructure.
Expected outcome: Device-side and infrastructure-side settings are consistent with the approved configuration.
6. Test Data Communication
Initiate the normal approved data-transfer or synchronization process and determine whether communication succeeds.
When possible, compare:
- Same VOCSN on another approved network location
- Another working VOCSN in the same location
- Current network service status
This can separate a device problem from a site-wide network problem.
Expected outcome: Data transfer either succeeds or the failure is narrowed to the device, network, or external service.
7. Evaluate Software Update Failure Safely
Confirm the update package, update method, device eligibility, prerequisites, and software version using current Ventec Life Systems documentation.
Do not force an update, interrupt an update already in progress, install unapproved software, or use undocumented recovery procedures.
If an update repeatedly fails or leaves the device in an abnormal state, remove it from clinical service.
Expected outcome: The update either completes through the approved process or the device is safely stopped for escalation without unauthorized intervention.
8. Perform Final Functional Verification
After communication is restored or an approved update completes, verify:
- Device starts normally
- Required therapies remain functional
- Alarm operation is normal
- Data communication works as intended
- Software version or update status is correct
- No new system messages are present
Expected outcome: Communication or update functionality is restored without affecting clinical operation.
If all applicable checks pass, the issue is resolved and troubleshooting can stop.
If the Problem Persists
If signal availability, network infrastructure, external connections, approved configuration, and authorized update procedures have been ruled out, the problem may involve internal communication hardware, stored configuration, software corruption, account or cloud-service provisioning, network security controls, or another service-level issue.
The VOCSN should be:
- Removed from service when the failure affects required functionality or leaves software state uncertain
- Labeled Out of Service when appropriate
- Sent for repair or bench evaluation when a device-side fault is suspected
- Evaluated using current Ventec Life Systems documentation
- Coordinated with hospital IT or cybersecurity when infrastructure is involved
- Updated or configured only by qualified and authorized personnel
Do not bypass security controls, install unofficial software, or use undocumented update methods. Following service or software changes, complete the applicable manufacturer checkout before return to service.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
Treat data connectivity and ventilation as separate paths: loss of data service does not automatically mean loss of therapy, but therapy and alarms must still be independently verified.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Respiratory Therapy reported that the VOCSN remained operational but would no longer connect to the facility wireless network for data transfer."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering and IT confirmed the device was attempting to connect through a facility wireless configuration that had recently changed."
Resolution
What action was taken.
Example:
"IT restored the approved network configuration, and Clinical Engineering verified successful VOCSN data communication and completed functional and alarm checks before return to normal use."
Helpful Details to Include (If Known)
- Cellular, Wi-Fi, or data function affected
- Exact connectivity or update message
- Current software version
- Network location
- Signal or network availability
- Whether other VOCSN devices are affected
- External communication accessory condition
- IT findings
- Data-transfer test result
- Update status
- Post-update functional checkout
- Final device status
Final Thought
Communication problems should be isolated methodically between the VOCSN, external accessories, network infrastructure, and remote services without compromising therapy or security. Verify clinical operation first, use only approved configuration and update processes, escalate unresolved failures, and document both the technical cause and final verification.
That is successful troubleshooting.