<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.nitrc.org/themes/nitrc3.0/css/rss.xsl.php?feed=https://www.nitrc.org/export/rss20_forum.php?forum_id=6889" ?>
<?xml-stylesheet type="text/css" href="https://www.nitrc.org/themes/nitrc3.0/css/rss.css" ?>
<rss version="2.0"> <channel>
  <title>NITRC News Group Forum: functional-mri-in-seven-borderline-cochlear-implant-candidates--a-preliminary-research-study.</title>
  <link>http://www.nitrc.org/forum/forum.php?forum_id=6889</link>
  <description>
	&lt;table border=&quot;0&quot; width=&quot;100%&quot;&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;/&gt;&lt;/tr&gt;&lt;/table&gt;
        &lt;p&gt;&lt;b&gt;Functional MRI in seven borderline cochlear implant candidates: A preliminary research study.&lt;/b&gt;&lt;/p&gt;          
        &lt;p&gt;Clin Otolaryngol. 2016 Dec 08;:&lt;/p&gt;
        &lt;p&gt;Authors:  Wagner F, Weder S, Caversaccio MD, Federspiel A, Wiest R, Senn P&lt;/p&gt;
        &lt;p&gt;Abstract&lt;br/&gt;
        The indications for cochlear implants (CIs) are constantly expanding, as are the numbers of patients who are not ideal or classical CI candidates. For these patients, a careful decision-making process is needed to minimize the risk of poor outcomes. Preoperatively, it may be unclear whether they will benefit from an implantation. As conventionally performed hearing tests (i.e. subjective and electrophysiological examinations, stapedial reflex testing) have limitations, further objective and effective methods for assessment of the central auditory pathway (CAP) are required [1-3]. This article is protected by copyright. All rights reserved.&lt;br/&gt;
        &lt;/p&gt;&lt;p&gt;PMID: 27930861 [PubMed - as supplied by publisher]&lt;/p&gt;
    </description>
  <language>en-us</language>
  <copyright>Copyright 2000-2026 NITRC OSI</copyright>
  <webMaster></webMaster>
  <lastBuildDate>Wed, 06 May 2026 6:18:29 GMT</lastBuildDate>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>NITRC RSS generator</generator>
 </channel>
</rss>
