MedElevator Войти в исследования
← Поиск публикаций

DOI 10.2500/ajr.2008.22.3121

Медицинская библиотека · American journal of rhinology · 2008

Orbital exenteration: A dilemma in mucormycosis presented with orbital apex syndrome.

Songu Murat, Unlu H Halis, Gunhan Kivanc, Ilker S Sami, Nese Nalan

СтатьяПеревод пока не подготовлен

Аннотация

BACKGROUND

Mucormycosis is an uncommon, rapidly progressive, commonly fatal, opportunistic, fungal paranasal sinus infection. The most critical decision in the management of rhino-orbital mucormycosis is whether the orbit should be exenterated. The literature fails to provide a broad base of information of how physicians determine the need for exenteration in daily practice. The decision for exenteration often depends on the judgment of the treating otolaryngologist. The authors report their experience and outline that orbital exenteration may not be mandatory in all cases of rhino-orbital mucormycosis.

METHODS

The medical records from Celal Bayar University Medical Faculty Department of Otorhinolaryngology/Head and Neck Surgery were retrospectively searched from 1995 to 2007 for three cases with rhino-orbital mucormycosis, treated without orbital exenteration.

RESULTS

All patients with rhino-orbital mucormycosis who were treated without exenteration survived.

CONCLUSION

The favorable outcome was attributable to rapid correction of the underlying medical condition; wide local excision and debridement of all involved and devitalized sinonasal and periorbital tissue, while establishing adequate sinus and orbital drainage; daily endoscopic assessment with multiple sinus debridement when necessary; daily irrigation of the involved areas; and high-dose i.v. amphotericin B.

Для цитирования: Songu Murat, Unlu H Halis, Gunhan Kivanc, Ilker S Sami, Nese Nalan. Orbital exenteration: A dilemma in mucormycosis presented with orbital apex syndrome.. American journal of rhinology. 2008. DOI: 10.2500/ajr.2008.22.3121.

Предметные рубрики MeSH

Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Загрузка состояния…

История · было → стало

Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.

Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.