Natus NicoletOne

Network or Data Storage / Export Failure

On this page

Asset Type

EEG System

Manufacturer

Natus

Model

NicoletOne

What This Guide Helps With

Troubleshooting failed data saves, export errors, or network connectivity issues preventing EEG study storage, transfer, or retrieval.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Expected: Patient monitoring continues without interruption
Why it matters: Prevents loss of critical diagnostic data and maintains patient safety

Verify the Reported Issue and Behavior

Expected: Clear identification of when and where the failure occurs
Why it matters: Determines whether the issue is storage, network, or software related

Check Network Connectivity (Most Common Cause)

Expected: Stable network connection with valid IP
Why it matters: Loss of network prevents data transfer and remote storage

Verify Network Path or Server Availability

Expected: Network storage is accessible
Why it matters: Server downtime or permission issues can mimic device failure

Check Local Storage Capacity

Expected: Adequate free storage space available
Why it matters: Full drives prevent saving and exporting data

Test Export to Alternate Media

Expected: Successful export via alternate method
Why it matters: Helps isolate network vs software vs storage issue

Check Software Status and Restart Application

Expected: Normal operation restored
Why it matters: Clears temporary software faults or memory issues

Perform a Full System Reboot

Expected: Network and storage functions restored
Why it matters: Resolves OS-level communication or service issues

Check User Permissions and Login Credentials

Expected: Authorized access to storage locations
Why it matters: Permission issues commonly block data transfers

If the Problem Persists

If network connectivity, storage availability, and software behavior have all been verified, the issue is likely internal (hard drive failure, network interface failure, or software/database corruption).

Remove the device from service, label it Out of Service, and send for repair or bench evaluation.

Knowing when to stop prevents data loss and ensures proper escalation.

Clinical Use Tip

Never troubleshoot storage or export issues during an active EEG recording unless absolutely necessary. Always secure patient data first or complete the study before intervention.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"EEG system unable to export studies to network drive; export failed repeatedly."

Cause

What was observed during troubleshooting.

Example:
"Network connection lost due to disconnected Ethernet cable."

Resolution

What action was taken.

Example:
"Reconnected network cable and verified successful export to server."

Helpful Details to Include (If Known)

Final Thought

Data integrity is critical in EEG systems. Always start with simple connectivity and storage checks before assuming system failure. Escalating at the right time protects both patient data and device reliability. Proper documentation ensures traceability and supports future troubleshooting.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide