14.1 Confirming the Surgical & Monitoring Plan

14.1 Confirming the Surgical & Monitoring Plan

Quick Answer: Before incision, confirm the procedure, structures at risk, and modality set with the surgical team; document any surgeon-ordered variations; and use closed-loop read-back so everyone shares one plan. The technologist executes monitoring; the interpreting physician owns clinical interpretation thresholds.

Domain IV (Communication & Documentation) carries 27% of the 2026 CNIM outline—more weight than any single technical domain. Confirmation of the surgical and monitoring plan is the first high-stakes communication task of the case. If the team disagrees about what is being monitored, later alerts become noise.

---

Why Plan Confirmation Is a Safety Step

IONM only protects the pathways it is actually set up to watch. A lumbar decompression with planned pedicle screws needs free-run and triggered EMG plus the SSEPs/MEPs appropriate to the levels; a CPA tumor needs BAEP and cranial-nerve EMG that a thoracic scoliosis case does not. Confirming the plan converts preoperative chart review into a shared intraoperative contract.

Plan confirmation also surfaces surgeon-ordered variations. Surgeons may request additional mapping, omit a modality for a documented reason (prior amputation, severe neuropathy, contraindication to TcMEP), or ask for a nonstandard montage. Those decisions are clinical orders for the case; they must be acknowledged and recorded, not silently absorbed into habit.

---

What to Confirm With the Surgical Team

Use the pre-incision briefing (or an equivalent focused conversation if the facility’s workflow differs) to verify:

Speak in plain clinical language the surgeon and anesthesiologist recognize. Prefer “bilateral upper and lower SSEPs plus TcMEPs and free-run EMG for L4–S1 pedicle work” over unexplained acronyms alone.

---

Closed-Loop Confirmation

Closed-loop communication means the sender states the message, the receiver restates or clearly acknowledges it, and the sender verifies that the acknowledgment matches intent. In plan confirmation:

1. State the planned modalities and structures at risk.
2. Invite confirmation or correction from the surgeon (and anesthesia when agents or NMB will constrain MEPs).
3. Read back any change the surgeon orders (“Understood—adding facial EMG and BAEP; omitting lower-extremity MEPs per your request”).
4. Document the confirmed plan and the variation in the monitoring record.

Without read-back, a mumbled “okay” can hide a critical mismatch. Closed-loop is especially important when the booked procedure changed overnight, when a fellow opens while the attending is scrubbing late, or when remote interpretation is joining after induction.

---

Documenting Surgeon-Ordered Variations

Variations ordered by the surgeon are part of the medical record of monitoring. Typical examples:

• Adding triggered EMG for screw testing that was not on the original request
• Omitting TcMEP because of a documented relative contraindication after team discussion
• Requesting intermittent rather than continuous MEP testing during a delicate microdissection window
• Expanding cranial-nerve EMG coverage for an unexpected tumor extension

Document who ordered the change, what changed, and when. Do not invent a facility policy name or form number that is not part of your published local procedure—exam answers expect professional practice principles, not unpublished hospital SOPs. If your site uses a specific checklist, follow it; if the exam asks for the principle, the principle is: confirm, read back, and record.

---

Technologist vs Interpreting Physician Roles

Clarify role boundaries during plan confirmation so later alerts are not mis-owned:

• Technologist (CNIM role): Selects and applies electrodes, acquires data, recognizes technical problems, applies agreed alert criteria as data thresholds, communicates objective changes, and documents events.
• Interpreting physician / supervising neurophysiologist: Sets or confirms interpretation strategy, judges clinical significance of changes, and collaborates with the surgeon on surgical implications.

When confirming the plan, you may say that alert criteria will follow the interpreting physician’s guidance for the case (for example, the commonly cited ~50% amplitude / ~10% latency SSEP change framework, or institutionally agreed MEP rules). You should not announce an independent “diagnosis threshold” as if you were the interpreting physician. If the interpreting physician has not yet joined, confirm how and when they will be contacted for baseline review and alerts.

---

Resolving Mismatches Before Incision

Escalate early when:

• Imaging or diagnosis implies risk to a pathway that is not in the planned modality set
• Anesthesia plans dense neuromuscular blockade while TcMEP is essential
• Prior surgery or deficits make a “standard” montage unusable without adaptation
• The booked case and the consent/whiteboard procedure do not match

Escalate to the surgeon and the interpreting physician—not by arguing preference, but by stating the mismatch and the monitoring consequence. Example: “Imaging shows a high thoracic lesion; the current request lists only lower-extremity SSEPs. Do you want upper-extremity SSEPs and MEPs added before incision?”

---

Practical Pre-Incision Script (Principle, Not Policy)

A concise confirmation might sound like:

“For T10–L2 posterior fusion with pedicle screws, we plan bilateral upper and lower SSEPs, TcMEPs, and free-run plus triggered EMG for the instrumented levels. Any additions or omissions before we lock baselines?”

If the surgeon replies “skip MEPs today,” closed-loop continues: “Confirming—no TcMEPs for this case per your order; continuing SSEP and EMG. I’ll document that and notify the interpreting physician.”

That sequence—confirm, accept ordered variation, document, notify interpretation—is the core of Section 14.1.

---

Link to Later Communication Tasks

Plan confirmation feeds every later Domain IV task. Patient explanations should match the confirmed modality set. Baseline reporting should reference the same structures at risk. Real-time alerts should be judged against the plan the team actually agreed to monitor. A vague plan produces vague alerts; a confirmed plan produces actionable communication.