On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies external causes of failed EMR transmission such as network disconnection, incorrect configuration, software issues, or interface engine communication problems.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
- Confirm no active test is in progress
- Ensure all results are saved locally
- Move testing to another spirometer if needed
2. Verify Network Connection (Physical and Status)
- Check Ethernet cable is fully seated at both ends
- Verify link lights are active at the port
- If wireless, confirm Wi-Fi connection is active
3. Confirm PC or Device Network Access
- Attempt to access hospital network drives (if applicable)
- Open a web browser to an internal site
4. Verify EMR / Interface Software Status
- Ensure spirometry software and interface applications are open and responsive
- Look for error messages or disconnected status
- Restart the application if needed
5. Check Patient Data Transmission Workflow
- Attempt to send a test record manually
- Observe for immediate failure, delay, or error messages
6. Verify Correct Configuration Settings
- Confirm correct EMR destination/server
- Verify proper IP address or hostname
- Check correct port settings
- Do not modify settings unless verified
7. Check Date and Time Settings
- Verify system date and time are accurate
8. Restart System and Reinitialize Connection
- Restart the spirometry device or PC
- Restart associated software
9. Check for Network or EMR Downtime
- Confirm with IT or clinical staff if EMR is down
- Check if interface engine is offline
- Verify if scheduled maintenance is occurring
If the Problem Persists
All common external causes have been ruled out. The issue is likely related to internal software configuration, interface engine integration, or network infrastructure.
Remove the device from service if required, label it Out of Service, and escalate to IT or vendor support for further evaluation.
Clinical Use Tip
Do not troubleshoot while connected to an active patient. Always ensure test data is saved before attempting reconnection or restarting the system.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Spirometry results not transmitting to EMR."
Cause
What was observed during troubleshooting.
Example:
"Network cable found loose at workstation causing intermittent connection loss."
Resolution
What action was taken.
Example:
"Reseated Ethernet cable and verified successful transmission to EMR."
Helpful Details to Include (If Known)
- Network cable condition and connection status
- Network access verification results
- Software and interface engine status
- Error messages observed
- Transmission test results
- Date and time accuracy
- Final device status
Final Thought
Effective troubleshooting starts with simple network and software checks before assuming system failure. Always protect patient data, verify connectivity, and escalate appropriately when external causes are ruled out.
That is successful troubleshooting.