LACRIMAL SYSTEM OBSTRUCTION AFTER RADIOIODINE THERAPY IN DIFFERENTIATED THYROID CARCINOMAS: A PROSPECTIVE COMPARATIVE STUDY.

LACRIMAL SYSTEM OBSTRUCTION AFTER RADIOIODINE THERAPY IN DIFFERENTIATED THYROID CARCINOMAS: A PROSPECTIVE COMPARATIVE STUDY.

Thyroid. 2016 Aug 26;

Authors: da Fonseca FL, Yamanaka PK, Kato JM, Matayoshi S

Abstract
BACKGROUND: Radioiodine therapy (RIT) is an established treatment for differentiated thyroid carcinomas and is widely used throughout the world, given the increasing incidence of this malignancy. Although serious adverse effects are infrequent, complications such as dry mouth, sialadenitis and dysphagia have been described. The involvement of the eyes and adnexa is not commonly discussed, despite dry eye, keratoconjunctivitis and lacrimal system obstruction (LSO) being reported, especially after high cumulative doses of radiopharmaceuticals. The incidence of LSO is not well established.
OBJECTIVES: To determine the frequency of lacrimal system obstruction (LSO) in patients undergoing RIT at 2, 4, 6 and 12 months after treatment.
METHODS: Patients with differentiated thyroid carcinoma undergoing (Group 1) and not undergoing (Group 2) RIT were evaluated in the preoperative and postoperative periods and 2, 4, 6 and 12 months post-surgery or post-RIT. Patients underwent tear film evaluation and lacrimal system probing and irrigation.
RESULTS: Group 1 (n = 44, 88 Eyes) had 3 patients (4 eyes) with LSO, corresponding to an incidence of 4.55% (4 events in 88 eyes) or 6.8% (3 cases in 44 patients). Group 2 (n = 43, 86 eyes) did not present any cases of LSO.
CONCLUSIONS: In this study, an active prospective investigation allowed LSO detection during the first 6 months after RIT.. This finding demonstrates the importance of making this association clear to patients and health professionals, with a view to early diagnosis, appropriate treatment and preventing LSO-related complications.  .

PMID: 27565021 [PubMed - as supplied by publisher]

from #ENT via xlomafota13 on Inoreader http://ift.tt/2bYtdXF
via IFTTT