On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting Capnostream 35 data export, EMR communication, wireless connection, or Vital Sync connectivity problems.
Step-by-Step Troubleshooting
Ensure Patient Safety First
If the Capnostream 35 is actively monitoring a patient, do not interrupt monitoring, power cycle the device, remove network accessories, or change communication settings unless clinical staff confirm it is safe.
Move the patient to another approved monitor if monitoring must continue during troubleshooting.
Expected outcome: Patient monitoring continues without interruption.
Why it matters: Connectivity problems should not create a gap in EtCO2, respiration rate, SpO2, pulse rate, or alarm monitoring.
Verify the Reported Connectivity Problem
Confirm what issue was reported:
- Data is not exporting
- Patient data is not reaching the EMR
- Wireless connection is unavailable
- Vital Sync is not receiving data
- Data is delayed, intermittent, or associated with the wrong patient
- USB export is failing
- Network connection drops during use
Expected outcome: The exact failure mode is identified before changing settings.
Why it matters: “Not connecting” can mean several different problems, including network access, configuration, patient association, server communication, or export media failure.
Check Whether Bedside Monitoring Is Still Working
Confirm the Capnostream 35 is still displaying patient parameters correctly, including EtCO2, respiration rate, waveform, SpO2, pulse rate, and alarms if in use.
Expected outcome: The monitor itself is still functioning clinically.
Why it matters: A communication issue is different from a monitoring failure. If monitoring values are missing or unreliable, troubleshoot that clinical function first.
Check Power and Startup Status
Confirm the monitor is powered on normally, not in a low battery condition, and not displaying system errors that could affect communication.
Connect to AC power if battery level is low.
Expected outcome: The monitor is fully powered and stable.
Why it matters: Low battery, unstable power, or startup faults can interrupt communication or prevent export functions from completing.
Confirm the Correct Patient and Location Information
Verify that the patient information, bed/location, department, or device association is correct according to the site workflow.
If the Capnostream 35 is sending data through Vital Sync or an EMR interface, confirm the device is assigned to the correct patient or room before assuming a device failure.
Expected outcome: Data is linked to the correct patient/location.
Why it matters: EMR and middleware issues are often caused by patient association, location mapping, or workflow errors rather than hardware failure.
Check Physical Connections
If the connection uses a cable, inspect the network cable, communication cable, adapter, dock, or export cable for loose connections, damage, bent pins, or strain.
Reseat the cable at both ends if safe to do so.
Swap with a known-good cable if available.
Expected outcome: The connection is secure and communication resumes.
If this resolves the issue, stop troubleshooting and document the cable or connection problem.
Check the Network Port or Wall Jack
If using wired network communication, connect the cable to a known-good network port approved for medical device use.
Confirm link lights if available on the port, adapter, or network device.
Expected outcome: The monitor has a valid physical network connection.
Why it matters: A bad wall jack, inactive port, or disconnected patch cable can look like a monitor failure.
Check Wireless Availability
If using wireless communication, confirm the wireless function is enabled according to site policy and that the monitor is in an area with expected wireless coverage.
Compare with another known-working device in the same location if possible.
Expected outcome: Wireless service is available in that area.
Why it matters: Wireless dead zones, access point issues, or network changes can cause intermittent EMR or Vital Sync communication problems.
Check for Recent Network or IT Changes
Ask whether there were recent changes to:
- Wireless network settings
- VLANs
- IP addressing
- Certificates
- Firewall rules
- Vital Sync server configuration
- EMR interface settings
- Device replacement or room reassignment
Expected outcome: Recent system changes are identified.
Why it matters: Connectivity failures often occur after IT changes, server updates, certificate expiration, or interface changes.
Compare With Another Capnostream 35
If another Capnostream 35 is available, test whether it communicates correctly from the same location using the same workflow.
Do not swap devices on an active patient unless clinical staff approve.
Expected outcome: The issue is narrowed to one monitor, one location, or the network/interface system.
Why it matters: A comparison test helps separate device failure from network, EMR, or Vital Sync issues.
Check Data Export Media
If the issue involves exporting data to USB or removable media, confirm the media is approved by site policy, properly formatted, not full, and not physically damaged.
Try a known-good approved USB drive if permitted.
Expected outcome: Data export completes successfully or the media is identified as the cause.
If this resolves the issue, stop troubleshooting and document the failed export media.
Restart Only When Safe
If the device is not actively monitoring a patient, power cycle the Capnostream 35 and allow it to fully restart.
After restart, recheck network, export, EMR, or Vital Sync communication.
Expected outcome: Temporary communication faults clear after restart.
Why it matters: Some communication sessions can hang and recover after a controlled restart.
Check Site Configuration Settings
Review communication settings only within the limits allowed by your facility and service process. Confirm the device is configured for the correct connection method, network profile, server destination, or export workflow.
Do not randomly change IP, wireless, EMR, or server settings without approved configuration information.
Expected outcome: Settings match the approved site configuration.
Why it matters: Incorrect settings can break communication or send data to the wrong destination.
Escalate to IT, Interface Team, or Vendor Support When Needed
If the monitor appears functional but data is not reaching Vital Sync or the EMR, involve the appropriate IT/network/interface team.
Provide them with the device serial number, asset number, room/location, connection type, time of failure, and whether other devices are affected.
Expected outcome: Network or interface-side causes are investigated.
Why it matters: Clinical Engineering can verify the device and external setup, but EMR routing, server logs, wireless authentication, and interface engines often require IT support.
If the Problem Persists
If power, patient association, cables, network ports, wireless coverage, export media, restart, and approved configuration checks do not resolve the issue, common external causes have been ruled out.
Remove the Capnostream 35 from service if communication is required for clinical use or if the device cannot reliably support the required workflow.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair, bench evaluation, or vendor/network escalation as appropriate
Knowing when to stop is proper troubleshooting. Do not perform deep internal repair or unsupported configuration changes while the device is needed for patient monitoring.
Clinical Use Tip
Do not troubleshoot EMR, wireless, or Vital Sync communication on an active patient if the work could interrupt monitoring. Move the patient to another monitor first, or confirm with clinical staff that bedside monitoring can safely continue while connectivity is being evaluated.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Capnostream 35 was monitoring at the bedside but patient data was not transferring to Vital Sync/EMR."
Cause
What was observed during troubleshooting.
Example:
"Verified bedside monitoring was functional; found the device connected to an inactive network port in the patient room."
Resolution
What action was taken.
Example:
"Moved the network cable to a known-good approved port, confirmed communication restored, and returned the monitor to service."
Helpful Details to Include (If Known)
- Whether bedside monitoring was working
- Exact reported issue: EMR, Vital Sync, wireless, wired network, or USB export
- Patient/location association checked
- AC power status
- Battery status
- Network cable inspected or swapped
- Network port tested
- Wireless coverage compared with another device
- USB/export media tested
- Any error messages or connection indicators
- Whether other monitors were affected
- IT/interface team ticket number if escalated
- Final device status
Final Thought
Connectivity troubleshooting should be handled logically and safely. Confirm the Capnostream 35 is still monitoring correctly, rule out simple external causes, verify the network or export path, and escalate when the issue moves beyond the device. Good CCR documentation protects patient safety, supports IT/vendor follow-up, and makes repeat failures easier to identify.
That is successful troubleshooting.