Extra-ocular movement restriction and diplopia following orbital fracture repair

Publication date: Available online 25 August 2017
Source:American Journal of Otolaryngology
Author(s): H.A. Shah, Taha Shipchandler, Dominic Vernon, Maraya Baumanis, David Chan, William R. Nunery, Hui Bae Harold Lee
PurposeTo report a series of patients with extra-ocular movement restriction and diplopia after orbital fracture repair, and determine the effect of timing of repair and the type of implant used.MethodsA chart review was conducted identifying all patients >18years of age at our institution between June 2005 and June 2008 who underwent orbital fracture repair, and presented with clinically significant diplopia and extra-ocular movement restriction persisting longer than one month after repair. Data collected included timing of repair, implant used within the orbit, and need for revision.ResultsTen patients were identified with a mean time to primary orbital fracture repair at 9days (range 1–48). Seven patients underwent revision of their orbital fracture repair with removal of the previously placed implant and replacement with non-porous 0.4mm Supramid Foil, whereas one patient underwent lateral and inferior rectus recessions without revision of primary fracture repair. Titanium mesh was the intra-orbital implant found in all patients requiring revision of orbital fracture repair. All revisions resulted in resolution of clinically significant diplopia.ConclusionsClinically significant diplopia and extra-ocular movement restriction is not an uncommon complication after orbital fracture repair. In our series, there was a strong association between these complications and the use of porous titanium mesh implants. Revision of fractures significantly improved diplopia in all but one patient. This suggests that meticulous fracture repair and the use of non-porous implants primarily or secondarily may preclude the need for strabismus surgery after orbital trauma.



from ! ORL Sfakianakis via paythelady.61 on Inoreader http://ift.tt/2wHiy0S
via IFTTT