Chrome Extension
WeChat Mini Program
Use on ChatGLM

Fusion computed tomography-magnetic resonance imaging scans for pre-operative staging of congenital middle-ear cholesteatoma.

The Journal of laryngology and otology(2023)

Cited 0|Views3
No score
Abstract
OBJECTIVE:To evaluate if fusion computed tomography-diffusion-weighted magnetic resonance imaging may have a role in the pre-operative assessment of congenital middle-ear cholesteatoma. METHODS:A retrospective chart review of surgically treated congenital middle-ear cholesteatoma patients over a 2-year timespan was conducted. Pre-operative staging was performed on computed tomography and fusion computed tomography-diffusion-weighted magnetic resonance imaging based on extension of the disease according to the ChOLE classification system and the Potsic classification system. Intra-operative staging was compared to imaging findings to evaluate accuracy of the two imaging modalities in predicting congenital middle-ear cholesteatoma extent. RESULTS:Computed tomography was able to correctly predict congenital middle-ear cholesteatoma extent in three out of six cases according to the ChOLE classification system, all of which were staged as Ch1a and Ch1b on pre-operative computed tomography. Cases in which computed tomography was not able correctly to determine congenital middle-ear cholesteatoma extent were staged as Ch3 on pre-operative computed tomography. Fusion scans correctly determined congenital middle-ear cholesteatoma extent in all cases according to the ChOLE classification. CONCLUSIONS:Fusion computed tomography-diffusion-weighted magnetic resonance imaging may be helpful in cases of congenital middle-ear cholesteatoma where pre-operative computed tomography shows mastoid and antrum opacification, in which computed tomography alone may overestimate cholesteatoma extension beyond the level of the lateral semi-circular canal.
More
Translated text
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined