Study guide
14.1 Confirming the Surgical & Monitoring Plan
ABRET CNIM Neurophysiologic Intraoperative Monitoring Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Eligibility Pathways & Application 1.3 Scoring, Credential Validity & Retakes
2 Neuroanatomy & Clinical Terminology for IONM
2.1 CNS Overview & Spinal Cord Tracts 2.2 Peripheral Nerves & Plexuses 2.3 Cranial Nerves Relevant to IONM 2.4 Medical & Surgical Terminology for IONM
3 Neurophysiology & Instrumentation
3.1 Evoked Potential Principles (Near/Far Field, Latency, Amplitude) 3.2 Averaging, SNR & Digital Concepts 3.3 Differential Amplifier, Filters & Montages
4 Preoperative Assessment
4.1 Surgical Plan, Diagnosis & Imaging Review 4.2 Pre-existing Conditions Affecting Monitoring 4.3 Preoperative Neuroassessment 4.4 Modality Selection by Structures at Risk
5 Equipment & Patient Setup
5.1 Equipment & Supplies Selection 5.2 Stimulating/Recording Electrodes & Impedance 5.3 Site Preparation & Electrode Application
6 Anesthesia & Physiologic Effects
6.1 Volatile Agents & Cortical Responses 6.2 TIVA, Narcotics & Neuromuscular Blockade 6.3 BP, Temperature, Hematocrit & CO2 Effects
7 Somatosensory Evoked Potentials
7.1 SSEP Pathways & Generator Sites 7.2 Upper & Lower Extremity SSEP Technique 7.3 SSEP Alert Criteria & Surgical Correlation
8 Motor Evoked Potentials
8.1 Corticospinal Pathway & TcMEP Principles 8.2 TcMEP Technique & Anesthesia Optimization 8.3 MEP Alert Criteria & Troubleshooting
9 EMG & Cortical Mapping
9.1 Free-run & Triggered EMG Principles 9.2 Cranial Nerve & Pedicle Screw EMG 9.3 Cortical Mapping & Direct Cortical Stimulation
10 BAEP, EEG & VEP
10.1 BAEP Waveforms & Technique 10.2 BAEP in CPA & Brainstem Surgery 10.3 Intraoperative EEG & Visual Evoked Potentials
11 Signal Change Recognition & Troubleshooting
11.1 Impedance Checks & Pre-incision Baselines 11.2 Surgical vs Systemic Signal Changes 11.3 Artifact Identification & Systematic Troubleshooting
12 Surgery-Specific Monitoring Protocols
12.1 Spine Surgery Monitoring Protocols 12.2 Brain & Skull Base Monitoring 12.3 Vascular, Aortic & Peripheral Nerve Protocols
13 Postoperative Phase
13.1 Electrode Removal & Sharps Safety 13.2 Cleaning, Disinfection & Infection Control 13.3 Postoperative Neuroassessment & Outcome Correlation
14 Provider Communication
14.1 Confirming the Surgical & Monitoring Plan 14.2 Patient & Caregiver Communication 14.3 Reporting Pre-incision Baselines 14.4 Real-Time Alerts & Event Communication
15 Documentation Standards
15.1 Contemporaneous Annotation of Events 15.2 Report Writing, QA & Data Management 15.3 Multidisciplinary Handoff & Continuity
16 Patient & Electrical Safety
16.1 Electrical Safety in the OR 16.2 Sterile Field, Universal Precautions & Skin Safety 16.3 Equipment Inspection & Maintenance
17 Ethics & Professional Practice
17.1 ABRET Code of Ethics, Scope & HIPAA 17.2 Contraindications, Allergies & Professional Conduct
14.1 Confirming the Surgical & Monitoring Plan
Key Takeaways Explain This Topic AI
Confirm the operative procedure, structures at risk, and planned modalities with the surgical team before incision—preferably during the pre-incision briefing
Document surgeon-ordered variations from the usual modality set (additions, omissions, or special mapping requests) in the monitoring record
Use closed-loop communication: state the plan, invite confirmation, and read back acknowledgments so the team shares one mental model
The technologist prepares and executes the monitoring plan; the interpreting physician sets interpretation thresholds and clinical significance—do not invent facility-specific policies that are not published
Unresolved mismatches between imaging, diagnosis, and the proposed monitoring set must be escalated before critical surgical risk begins
Last updated: August 2026
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:
- Item Why it matters
- Procedure and approach Anterior vs posterior, levels, planned instrumentation, vascular clamping
- Structures at risk Cord, roots, plexus, cranial nerves, cortex, brainstem
- Modality set SSEP, TcMEP, free-run/triggered EMG, BAEP, EEG, VEP, mapping
- Special requests Pedicle stimulation thresholds, language mapping, D-wave, facial nerve monitoring
- Contraindications / limits Seizure history affecting TcMEP, pacemaker concerns, severe baseline deficits
- Interpreting coverage Who is providing remote or in-room interpretation for the case
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:
State the planned modalities and structures at risk.
Invite confirmation or correction from the surgeon (and anesthesia when agents or NMB will constrain MEPs).
Read back any change the surgeon orders (“Understood—adding facial EMG and BAEP; omitting lower-extremity MEPs per your request”).
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.