A Real-Life IONM Story That Could Have Ended Very Differently
It’s a normal weekend in the OR. The lights are bright, the monitors are humming, and a middle-aged man lies motionless on the table, fresh from a high-speed motor vehicle accident. He’s already intubated and ventilated, and no one knows yet how much damage the crash did to his spinal cord. The surgical plan is big: an anterior cervical discectomy and fusion at C4–C6, followed by a posterior spinal fusion from C2 down to T6. It’s going to be a long, complex day on an already unstable cervical spine.
The intraoperative neuromonitoring (IONM) team is in place. Baseline signals look textbook perfect. Somatosensory evoked potentials (SSEPs) are strong and symmetric in both upper and lower extremities. Motor evoked potentials (MEPs) are crisp in every monitored muscle group. Train-of-four (TOF) is a solid 4/4, EEG is continuous and symmetrical, and spontaneous electromyography (sEMG) is quiet. Everything is exactly as it should be before the first incision.
Then, right before the surgeon even picks up a scalpel, the IONM technologist’s screen changes. All the MEP responses—every single one—disappear.
The technologist in this case doesn’t hesitate to say something. The loss is reported immediately to the surgeon and confirmed with the remote reader in seconds. No one has touched the spine yet, so at first it doesn’t make sense.
The surgeon turns, understandably surprised. “I haven’t done anything yet,” he says. “Are you sure the alert is real?”
The tech stays calm and methodical, the way only an experienced IONM clinician can. While the anesthesia team and surgeon wait, she begins running through the checklist out loud, voice steady: “Technical side is clean…corkscrew electrodes are secure on the scalp, stimulation parameters are unchanged, and we’re still getting reproducible patient movement with every stimulation train.”
Anesthesia chimes in right away and confirms patient is stable, vitals are unchanged.
So the tech asks the one question that often cracks these cases wide open: “Has anything changed with the patient in the last few minutes…positioning, headrest, anything at all?”
Ah! Anesthesia had replaced the gel donut headrest. They wanted to gently increase neck extension for better anterior access. It seemed like such a small, routine adjustment of the soft, yellow gel pad that had been cradling the patient’s head since he rolled into the room.
“That’s the only change we’ve had. Let’s put the donut back exactly as it was,” the tech requests.
The IONM team has earned trust through clear communication and data, so the entire OR agrees to the readjustment and to wait to see what happens. It really is the only variable that has changed.
The original gel donut slides back under the patient’s head and the neck position returns to the exact baseline alignment. About five minutes later, the MEPs come roaring back in full force. Every muscle group returns to baseline amplitude and latency, crisp and reliable, exactly as they had been at setup.
The room lets out a collective breath. The case proceeds. Eight hours later, the patient wakes up neurologically intact, without any new deficits or tragic surprises. A potential spinal cord injury had been caught and reversed before the first cut.
Why This Case Matters
Most people picture the big threats in spine surgery as the obvious ones: misplaced screws, over-retraction, hypotension, or too-deep anesthesia. Those are real, of course. But this story is a masterclass in the “silent” threats that can often hide in plain sight and cause massive issues.
A simple gel headrest and a slight change in neck extension in a trauma patient with an already compromised cervical spine, that tiny shift was enough to compress the cord just enough to silence the motor pathways completely. That tiny angle change triggered a sudden, total MEP dropout.
And it’s all because the IONM tech, with all her experience, had the wherewithal to take command of that room while she followed a disciplined troubleshooting process:
- Rule out technical issues first (electrodes, stimulation, equipment).
- Confirm anesthesia stability (MAP, agents, depth).
- Ask the team the right question at the right time.
- Identify the single recent change.
- Recommend a targeted fix and stand by the data.
That systematic approach turned a potential disaster into a non-event.
What If?
What if motor evoked potentials hadn’t been ordered for this case? Some surgeons still skip them, even in high-risk cervical trauma. The patient would have gone under the knife with no one knowing his spinal cord was being quietly compromised from the very first positioning tweak and would have stayed that way for all 8 hours.
What if the alert hadn’t been communicated clearly and validated instantly? A few extra minutes of doubt could have turned five minutes of reversible compression into hours of irreversible damage.
What if the baselines hadn’t been rock-solid and reproducible? A subtle change might have been dismissed as “just a little drift.”
What if the team hadn’t asked the right questions or trusted the data? Critical thinking and calm collaboration are what separate good IONM from average monitoring.
And the hardest question of all: What if nothing had been done? After eight hours of surgery with ongoing cord compression, what would this patient’s neurological outcome have looked like? Quadriparesis? Complete loss of function below the injury level? A lifetime of dependency?
This is why great IONM is not just monitoring, it is a critical real-time clinical partnership between all parties in an OR. It gives the surgeon, anesthesiologist, and entire OR team a window into the nervous system while the patient is asleep and unable to speak. It turns potential tragedy into teamwork. It turns “I haven’t done anything yet” into “thankfully, we caught it in time.”
So the next time you see that unassuming little gel donut sitting on the headrest cart—neonatal, infant, pediatric, adult regular, or adult large—remember this case.
Never underestimate the head donut.
This very real story from the OR was shared by an IntraNerve IONM CNIM technologist who wished to remain annonymous.
