On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Patient event marker button not registering, delayed inputs, or no event annotation during EEG recording due to connection, accessory, or software issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Do not troubleshoot while actively recording a critical study if event capture is required
- Pause or transition to a backup system if necessary
Expected: Patient monitoring continues safely without data loss risk
Why it matters: Missed event markers can impact diagnostic accuracy
Verify the Reported Issue
- Attempt to press the patient event marker and observe system response
- Check if event appears in EEG recording software
- Note delay, no response, or intermittent behavior
Expected: Event marker registers immediately in software
Why it matters: Confirms true failure vs user misunderstanding
Check Event Marker Connection (Most Common Cause)
- Ensure cable is fully seated in the correct input port
- Disconnect and reconnect firmly
- Inspect connector pins for damage or debris
Expected: Secure connection with no looseness
Why it matters: Loose or partially connected cables commonly cause input failure
Inspect Cable and Button Condition
- Check for frayed cable, cracked housing, or stuck button
- Press button multiple times to feel for mechanical response
Expected: Button has normal tactile feedback and cable is intact
Why it matters: Worn or failed accessories are a frequent external cause
Test with Known-Good Event Marker (If Available)
- Swap the event marker device with a working one
Expected: Replacement device functions normally
Why it matters: Quickly isolates accessory failure vs system issue
Verify Software Input Configuration
- Confirm correct input channel is assigned in software
- Ensure event marker feature is enabled
- Restart acquisition software if needed
Expected: Event marker input recognized and logged
Why it matters: Misconfiguration can mimic hardware failure
Restart the System (Basic Reset)
- Close acquisition software
- Reboot computer and relaunch system
Expected: Temporary communication issues are cleared
Why it matters: Software or driver glitches can interrupt input recognition
Check Input Port Functionality
- Test the same port with another compatible input device (if applicable)
Expected: Port accepts input from known-good device
Why it matters: Determines if failure is port-related vs accessory-related
If the Problem Persists
If all external causes have been ruled out, the issue is likely internal (input board, interface module, or software driver fault).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Knowing when to stop prevents unnecessary risk and saves troubleshooting time.
Clinical Use Tip
Do not rely on manual event recall if the marker is not functioning. Always move the patient to a fully operational system to ensure accurate event documentation.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Patient event marker not registering during EEG study."
Cause
What was observed during troubleshooting.
Example:
"Failed event marker cable with intermittent internal break."
Resolution
What action was taken.
Example:
"Replaced event marker device and verified proper event logging."
Helpful Details to Include (If Known)
- Event marker response (none, delayed, intermittent)
- Cable condition and connection status
- Test with known-good accessory
- Software restart performed
- Port functionality tested
- Final device status
Final Thought
Event marker failures are often simple accessory or connection issues, but they directly impact diagnostic data quality. Always rule out external causes first, prioritize patient safety, and escalate appropriately when needed. Clear documentation ensures continuity and accountability.
That is successful troubleshooting.