On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where a Jaeger Medical Vyntus pulmonary function testing system cannot communicate with the hospital network or Electronic Medical Record (EMR). Symptoms may include failed patient record uploads, inability to retrieve patient demographics, or communication errors within the pulmonary testing software.
Because these systems rely heavily on PC software, network configuration, and interface engines, many failures are caused by simple connection or configuration issues rather than hardware faults.
Step-by-Step Troubleshooting
1. Verify the System Is Powered and the Software Is Running
- Confirm the Vyntus PC workstation and pulmonary software are fully powered on and functioning normally.
- Look for: software error messages, frozen application windows, delayed system response.
- If the software is not functioning normally, restart the workstation and reopen the Vyntus software before continuing.
2. Confirm the Network Connection on the PC
- Check that the PC connected to the Vyntus system has an active network connection.
- Verify: Ethernet cable is securely connected, network port indicator lights are active, the PC shows a valid network connection in Windows.
- If the network connection is lost, reconnect the cable or move to a known working network port.
3. Verify the PC Has a Valid IP Address
- Open the network settings or command prompt and confirm the workstation has a valid IP address assigned by the hospital network.
- Look for: valid IP address, proper subnet, default gateway.
- An invalid or missing IP address may indicate a network configuration or DHCP issue.
4. Confirm EMR Interface Settings in the Vyntus Software
- Open the configuration settings within the pulmonary testing software and verify the interface settings.
- Check: EMR interface enabled, correct interface server address, correct port configuration, correct protocol settings (HL7 or other interface).
- Incorrect settings may prevent communication with the hospital integration engine.
5. Verify Communication With the Interface Engine
- Many Vyntus systems communicate with the EMR through an integration engine such as Cerner Connectivity Engine or similar middleware.
- Check for: interface connection status within the software, interface error logs, failed message queues.
- If possible, attempt a test message or patient record transmission.
6. Confirm Patient Demographic Import Function
- If the system normally retrieves patient data from the EMR, attempt a patient lookup.
- Observe: whether the lookup function works, any returned error messages, slow response from the system.
- Failure here often indicates a server communication issue rather than a device problem.
7. Restart the Vyntus Software and Workstation
- If communication appears intermittent, restart the system.
- Steps: close the pulmonary testing software, restart the workstation, reopen the application and attempt communication again.
- This clears temporary network or software interface faults.
8. Verify the Hospital Network Is Operational
- Check with IT or verify another networked workstation in the same room.
- Confirm: other devices on the network function normally, no current network outage, no recent network configuration changes.
- Network outages frequently appear as device communication failures.
If the Problem Persists
If all external network and configuration checks have been completed and communication with the EMR still fails, the issue is likely related to: software interface configuration, integration engine issues, server-side interface failures, PC software corruption.
At this point the device should be:
- Removed from clinical use if patient records cannot be reliably stored
- Labeled Out of Service
- Escalated to IT, interface support, or manufacturer service for further investigation
Recognizing when the issue is outside the device itself is an important part of effective troubleshooting.
Clinical Use Tip
Never troubleshoot EMR communication issues while a patient test is actively being performed. Allow the clinical staff to complete or cancel the test first and ensure patient data has been safely documented before restarting software or network connections.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Pulmonary lab reported that the Vyntus system could not upload test results to the EMR and patient demographics were not importing.”
Cause
What was observed during troubleshooting.
Example:
“Network cable at the workstation was found partially disconnected, causing intermittent network communication.”
Resolution
What action was taken.
Example:
“Reseated the Ethernet cable and verified network connectivity. Confirmed successful patient lookup and test result upload to the EMR.”
Helpful Details to Include
- Network connection status
- IP address verified
- Software error messages observed
- Interface engine connection status
- Cable condition and port tested
- Workstation reboot performed
- Test message or patient lookup result
- Final device status
Final Thought
Many EMR communication problems originate from network connectivity, software configuration, or interface engine issues rather than hardware failure. Clinical Engineering troubleshooting should always begin with simple external checks before escalating. Ensuring accurate documentation and knowing when to involve IT or vendor support helps maintain both system reliability and patient data integrity.
That is successful troubleshooting.