Show Summary Details
Page of

Principles of Invasive EEG 

Principles of Invasive EEG
Chapter:
Principles of Invasive EEG
Author(s):

Samden D. Lhatoo

, Nuria Lacuey

, and Philippe Ryvlin

DOI:
10.1093/med/9780198714668.003.0002
Page of

PRINTED FROM OXFORD MEDICINE ONLINE (www.oxfordmedicine.com). © Oxford University Press, 2016. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Medicine Online for personal use (for details see Privacy Policy and Legal Notice).

date: 23 October 2019

The growing requirement for invasive EEG in presurgical evaluation of intractable focal epilepsy has been driven largely by the increasing complexity of epilepsy surgery cases. Extratemporal surgeries now exceed anterior temporal lobe resections for mesial temporal sclerosis, and the proportion of patients undergoing invasive EEGs has significantly increased. Half of all patients undergoing stereotactic EEG (SEEG) evaluations are MRI-negative (usually with focal cortical dysplasia type 1 or 2) and a third are reoperations for failed resective or palliative surgery. Certain principles guide the decision to use invasive EEG and the choice of invasive EEG technique. SEEG has distinct advantages, as do subdural grid evaluations and intraoperative corticography. The consequences of loose hypotheses in the decision to invasively evaluate a patient, and of inappropriate choice of technique, include poor seizure outcomes after surgery, morbidity, and mortality. This chapter discusses the guiding principles for invasive studies of the human epileptic brain.

Access to the complete content on Oxford Medicine Online requires a subscription or purchase. Public users are able to search the site and view the abstracts for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.