Use of topical antibiotics with intravitreal injections: a controversy coming to an end

On 2 February 2018, Ophthalmologica published “2018 Update on Intravitreal Injections:

Euretina Expert Consensus Recommendations” (DOI: 10.1159/000486145) online, authored by Andrzej Grzybowski, Reinhard Told, Stefan Sacu, Francesco Bandello, Elad Moisseiev, Anat Loewenstein, and Ursula Schmidt-Erfurth on behalf of the Euretina Board.

The article was intended “to highlight important aspects of pre- and post-injection management by examining the recent literature for evidence-based suggestions providing a standardized and structured approach.”

On the long-debated issue of antibiotic prophylaxis, the authors concluded that, based on current evidence, “perioperative antibiotics cannot be considered the standard of care, as there is no evidence of prophylactic effects with regard to EO [endophthalmitis] when using perioperative antibiotics.”

In addition, large studies have reported a paradox effect, leading to increased rates of endophthalmitis due to repeated antibiotic exposure. Intravitreal injections are administered frequently and over the long term, and it should be kept in mind that “the widespread and frequent use of topical antibiotics promotes increasing resistance to antibiotic substances and growth of pan-drug-resistant bacteria,” the authors wrote.

Here are the opinions of experts from around the world on the topic.

Paolo Lanzetta, MD

Professor and Chair of the Department of Ophthalmology, University of Udine and Scientific Director of the European Institute of Ocular Microsurgery (IEMO), Udine, Italy

Jordi Monés, MD

Director of the Institut de la Màcula and Barcelona Macula Foundation, Barcelona, Spain

Frank Holz, MD

Professor and Chair of the Department of Ophthalmology, University of Bonn, Germany

Keith A. Warren, MD

Warren Retina Associates, Overland Park, Kansas, USA

Carl D. Regillo, MD, FACS

Director of the Retina Service, Wills Eye Hospital, Philadelphia, USA

There has been a strong trend away from the use of topical antibiotics with intravitreal injections. Only a very small minority still do it. We all used to do it, but it has fallen by the wayside for the most part and now it is pretty rare. Yes, nowadays to see the practice of using topical antibiotics after an intravitreal injection is very rare.

A lot of us used them at first, but as time went by studies seemed to indicate that it was not necessary. It didn’t really do anything above and beyond the standard Betadine prep.

Judy E. Kim, MD

Professor of Ophthalmology, Medical College of Wisconsin, Milwaukee, WI, USA

I have not used topical antibiotics for intravitreal injection for some years now. Topical antibiotics before or after the injections have not shown to be beneficial in most cases.  At Diabetic Retinopathy Clinical Research network (DRCR.net), we studied a large number of injections and were among the first to show that there was no benefit. There are also studies showing that repeated use of topical antibiotics can lead to growth of superbugs with drug resistance, which can actually be detrimental to the patients. In addition, use of antibiotics pose added cost and burden on the patients. Keeping the lashes away, not talking (or wearing a mask) during injections and the use of povidone iodine are some of the key steps in infection control related to intravitreal injections.

Pravin U. Dugel, MD

Retinal Consultants of Arizona, Phoenix, USA

We don’t use antibiotics we use Betadine. I use it in every patient that I inject. I don’t do an injection without Betadine preparation first. We don’t use antibiotics, but we always use Betadine.

Antibiotic prophylaxis is first of all very costly. Secondly, there are side effects in selecting out resistant organisms and there is very good evidence that with Betadine alone we do achieve a level of sterilization that is more than adequate.

I think the overwhelming majority of retina specialists in the US use Betadine alone.

J. Fernando Arevalo, MD, FACS

President of the Pan-American Association of Ophthalmology, Academia Ophthalmologica Internationalis Member (Chair: XXIX), Edmund F. and Virginia B. Ball Professor of Ophthalmology, Chairman, Department of Ophthalmology, Johns Hopkins Bayview Medical Center Retina Division, Wilmer Eye Institute, The Johns Hopkins University School of Medicine, Baltimore, Maryland, USA

Several studies have shown by now that in thousands of injections, the incidence of endophthalmitis without the use of antibiotics before or after injections is very low. In addition, the studies suggest that the use of prophylactic antibiotics may increase resistance and, in fact, increase the incidence of endophthalmitis. The reported endophthalmitis rates after IVT injection range from 0.020% to 0.085% (very low but they are zero as would be desirable). The two key issues involved in the prevention of endophthalmitis are pre-IVT injection disinfection using povidone-iodine (PVI) and the use of topical antibiotics as prophylaxis. Recent data suggest that there is inadequate evidence to support the routine use of prophylactic pre-, peri-, or postinjection antibiotics to reduce the risk of endophthalmitis. Pre-IVT injection disinfection using povidone-iodine (PVI) remains the gold standard. [Information cited comes from the following studies: Acute endophthalmitis after intravitreal injection and preventive effect of preoperative topical antibiotics.Park Y et al. J Ocul Pharmacol Ther. (2013). Prophylactic antibiotic use after intravitreal injection: effect on endophthalmitis rate.Bhatt SS et al. Retina. (2011). Intravitreal Injection–Technique and Safety.Lai TY et al. Asia Pac J Ophthalmol (Phila). (2015)]

Dhivya Ashok Kumar, MD

Dr. Agarwal’s Eye Hospital, Chennai, India

We do not combine intravitreal antibiotics for routine intravitreal injections like anti-VEGF or triamcinolone. However, we keep the patient on topical antibiotics, preferably fourth generation flouroquinolones, namely moxifloxacin qid after intravitreal injections, for 1 week. We take enough sterile precautions during intravitreal injections to prevent the transfer of microbes by treating periocular infections before taking the patient for injection. Pre-injection Betadine cleaning of the conjunctival sac and periocular tissue is mandatory in all our cases. All intravitreal injections are performed in a sterile operating room set up. Proper scrubbing, sterile precautions during injections, and regular checking of drug vial status reduce the risk of infection. Prophylactic antibiotics orally are also given for 5 days following intravitreal injections. Immediate instillation of topical antibiotics by the end of the intravitreal procedure and good postoperative follow-up is required. Many of our eye care centers in this part of the country follow the same protocol. Intravitreal antibiotics are given only in cases with endophthalmitis or suspected endophthalmitis.

Sundaram Natarajan, MD

Professor and Chairman, Aditya Jyot Eye Hospital, Mumbai, India

In India, many of us use antibiotic drops, the day before and in the three days post-injection. On the day of the injection, we use povidone iodine, and we perform the injection in the operating room.

The Vitreo-Retina Society of India still recommends this practice. We have discussed changes in many of the current practices, but there has been no discussion yet on the use of antibiotics. Personally, I think that we should align with other countries and release recommendations that povidone iodine alone is sufficient to prevent infection.

We have had clusters of endophthalmitis with Avastin, likely due to contamination during preparation of the drug, but with the other drugs, Lucentis and Eylea, endophthalmitis is extremely rare.

Tien Y. Wong, MD, PhD

Professor and Chairman, Department of Ophthalmology, National University of Singapore, Singapore

There is clearly no evidence in the literature and the guidelines on injections do not support routine use of topical antibiotics. I perform intravitreal injections in a clean room in the office setting. Clean with iodine, drape and speculum. No antibiotics are used. We are now progressing to nurse-led injection clinics for simple cases.

Anat Loewenstein, MD, MHA

Professor of Ophthalmology and Deputy Dean, Medical School, Sackler Faculty of Medicine, Tel Aviv University, and Chairman of the Department of Ophthalmology, Tel Aviv Sourasky Medical Center (TASMC, Tel Aviv, Israel )

I do not prescribe topical antibiotics prior to the administration of intravitreal injections. There have been no prospective studies demonstrating that pre-injection antibiotics reduce the risk of endophthalmitis. Moreover, the repetitive nature of intraocular injection of anti-VEGF agents, and thus repeated use of topical antibiotics, dramatically increases the potential for colonization of the ocular surface with resistant bacteria. Also, the use of antibiotics prior to intravitreal injection increases cost and patient inconvenience, particularly when patients are managed in an [as-needed] PRN manner.

We still give one drop of antibiotic at the end of the procedure, as this is the common practice in my country. Nevertheless, it should be noted that topical antibiotic use at the time of the injection procedure offers no additional benefit over topical broad-spectrum microbicides and antiseptic administration.

Topical antibiotic use after the injection procedure also offers no reduction of endophthalmitis risk. In fact, topical antibiotics have poor penetration into the eye due to various physiological barriers, so they do not reach therapeutic levels in the vitreous.

Antibiotic resistance is a serious concern. In multiple large case series comparing intravitreal injection with or without the use of antibiotics, there is a numerical trend in most cases toward increased rates of endophthalmitis when antibiotics are used.

logo IVEG
Privacy Overview

Owner and Data Controller

Stichting Intravitreal Expert Group
Westerstraat 10
3016DH, Rotterdam
Netherlands

Owner contact email: info@intravitrealexperts.com

Types of Data collected

Among the types of Personal Data that this Application collects, by itself or through third parties, there are: Cookies; Usage Data; first name; last name; email address.

Complete details on each type of Personal Data collected are provided in the dedicated sections of this privacy policy or by specific explanation texts displayed prior to the Data collection.
Personal Data may be freely provided by the User, or, in case of Usage Data, collected automatically when using this Application.
Unless specified otherwise, all Data requested by this Application is mandatory and failure to provide this Data may make it impossible for this Application to provide its services. In cases where this Application specifically states that some Data is not mandatory, Users are free not to communicate this Data without consequences to the availability or the functioning of the Service.
Users who are uncertain about which Personal Data is mandatory are welcome to contact the Owner.
Any use of Cookies – or of other tracking tools – by this Application or by the owners of third-party services used by this Application serves the purpose of providing the Service required by the User, in addition to any other purposes described in the present document and in the Cookie Policy, if available.

Users are responsible for any third-party Personal Data obtained, published or shared through this Application and confirm that they have the third party’s consent to provide the Data to the Owner.

Mode and place of processing the Data

Methods of processing

The Owner takes appropriate security measures to prevent unauthorized access, disclosure, modification, or unauthorized destruction of the Data.
The Data processing is carried out using computers and/or IT enabled tools, following organizational procedures and modes strictly related to the purposes indicated. In addition to the Owner, in some cases, the Data may be accessible to certain types of persons in charge, involved with the operation of this Application (administration, sales, marketing, legal, system administration) or external parties (such as third-party technical service providers, mail carriers, hosting providers, IT companies, communications agencies) appointed, if necessary, as Data Processors by the Owner. The updated list of these parties may be requested from the Owner at any time.

Legal basis of processing

The Owner may process Personal Data relating to Users if one of the following applies:

  • Users have given their consent for one or more specific purposes. Note: Under some legislations the Owner may be allowed to process Personal Data until the User objects to such processing (“opt-out”), without having to rely on consent or any other of the following legal bases. This, however, does not apply, whenever the processing of Personal Data is subject to European data protection law;
  • provision of Data is necessary for the performance of an agreement with the User and/or for any pre-contractual obligations thereof;
  • processing is necessary for compliance with a legal obligation to which the Owner is subject;
  • processing is related to a task that is carried out in the public interest or in the exercise of official authority vested in the Owner;
  • processing is necessary for the purposes of the legitimate interests pursued by the Owner or by a third party.

In any case, the Owner will gladly help to clarify the specific legal basis that applies to the processing, and in particular whether the provision of Personal Data is a statutory or contractual requirement, or a requirement necessary to enter into a contract.

Place

The Data is processed at the Owner’s operating offices and in any other places where the parties involved in the processing are located.

Depending on the User’s location, data transfers may involve transferring the User’s Data to a country other than their own. To find out more about the place of processing of such transferred Data, Users can check the section containing details about the processing of Personal Data.

Users are also entitled to learn about the legal basis of Data transfers to a country outside the European Union or to any international organization governed by public international law or set up by two or more countries, such as the UN, and about the security measures taken by the Owner to safeguard their Data.

If any such transfer takes place, Users can find out more by checking the relevant sections of this document or inquire with the Owner using the information provided in the contact section.

Retention time

Personal Data shall be processed and stored for as long as required by the purpose they have been collected for.

Therefore:

  • Personal Data collected for purposes related to the performance of a contract between the Owner and the User shall be retained until such contract has been fully performed.
  • Personal Data collected for the purposes of the Owner’s legitimate interests shall be retained as long as needed to fulfill such purposes. Users may find specific information regarding the legitimate interests pursued by the Owner within the relevant sections of this document or by contacting the Owner.

The Owner may be allowed to retain Personal Data for a longer period whenever the User has given consent to such processing, as long as such consent is not withdrawn. Furthermore, the Owner may be obliged to retain Personal Data for a longer period whenever required to do so for the performance of a legal obligation or upon order of an authority.

Once the retention period expires, Personal Data shall be deleted. Therefore, the right to access, the right to erasure, the right to rectification and the right to data portability cannot be enforced after expiration of the retention period.

The purposes of processing

The Data concerning the User is collected to allow the Owner to provide its Services, as well as for the following purposes: Analytics, Contacting the User and Displaying content from external platforms.

Users can find further detailed information about such purposes of processing and about the specific Personal Data used for each purpose in the respective sections of this document.

Analytics

The services contained in this section enable the Owner to monitor and analyze web traffic and can be used to keep track of User behavior.

Google Analytics (Google Ireland Limited)

Google Analytics is a web analysis service provided by Google Ireland Limited (“Google”). Google utilizes the Data collected to track and examine the use of this Application, to prepare reports on its activities and share them with other Google services.
Google may use the Data collected to contextualize and personalize the ads of its own advertising network.

Personal Data collected: Cookies; Usage Data.

Place of processing: Ireland – Privacy Policy – Opt Out. Privacy Shield participant.

Contacting the user

Contact form (this Application)

By filling in the contact form with their Data, the User authorizes this Application to use these details to reply to requests for information, quotes or any other kind of request as indicated by the form’s header.

Personal Data collected: email address; first name; last name.

Mailing list or newsletter (this Application)

By registering on the mailing list or for the newsletter, the User’s email address will be added to the contact list of those who may receive email messages containing information of commercial or promotional nature concerning this Application. Your email address might also be added to this list as a result of signing up to this Application or after making a purchase.

Personal Data collected: email address.

Displaying content from external platforms

This type of service allows you to view content hosted on external platforms directly from the pages of this Application and interact with them.
This type of service might still collect web traffic data for the pages where the service is installed, even when Users do not use it.

YouTube video widget (Google Ireland Limited)

YouTube is a video content visualization service provided by Google Ireland Limited that allows this Application to incorporate content of this kind on its pages.

Personal Data collected: Cookies; Usage Data.

Place of processing: Ireland – Privacy Policy. Privacy Shield participant.

The rights of Users

Users may exercise certain rights regarding their Data processed by the Owner.

In particular, Users have the right to do the following:

  • Withdraw their consent at any time. Users have the right to withdraw consent where they have previously given their consent to the processing of their Personal Data.
  • Object to processing of their Data. Users have the right to object to the processing of their Data if the processing is carried out on a legal basis other than consent. Further details are provided in the dedicated section below.
  • Access their Data. Users have the right to learn if Data is being processed by the Owner, obtain disclosure regarding certain aspects of the processing and obtain a copy of the Data undergoing processing.
  • Verify and seek rectification. Users have the right to verify the accuracy of their Data and ask for it to be updated or corrected.
  • Restrict the processing of their Data. Users have the right, under certain circumstances, to restrict the processing of their Data. In this case, the Owner will not process their Data for any purpose other than storing it.
  • Have their Personal Data deleted or otherwise removed. Users have the right, under certain circumstances, to obtain the erasure of their Data from the Owner.
  • Receive their Data and have it transferred to another controller. Users have the right to receive their Data in a structured, commonly used and machine readable format and, if technically feasible, to have it transmitted to another controller without any hindrance. This provision is applicable provided that the Data is processed by automated means and that the processing is based on the User’s consent, on a contract which the User is part of or on pre-contractual obligations thereof.
  • Lodge a complaint. Users have the right to bring a claim before their competent data protection authority.

Details about the right to object to processing

Where Personal Data is processed for a public interest, in the exercise of an official authority vested in the Owner or for the purposes of the legitimate interests pursued by the Owner, Users may object to such processing by providing a ground related to their particular situation to justify the objection.

Users must know that, however, should their Personal Data be processed for direct marketing purposes, they can object to that processing at any time without providing any justification. To learn, whether the Owner is processing Personal Data for direct marketing purposes, Users may refer to the relevant sections of this document.

How to exercise these rights

Any requests to exercise User rights can be directed to the Owner through the contact details provided in this document. These requests can be exercised free of charge and will be addressed by the Owner as early as possible and always within one month.

Additional information about Data collection and processing

Legal action

The User’s Personal Data may be used for legal purposes by the Owner in Court or in the stages leading to possible legal action arising from improper use of this Application or the related Services.
The User declares to be aware that the Owner may be required to reveal personal data upon request of public authorities.

Additional information about User’s Personal Data

In addition to the information contained in this privacy policy, this Application may provide the User with additional and contextual information concerning particular Services or the collection and processing of Personal Data upon request.

System logs and maintenance

For operation and maintenance purposes, this Application and any third-party services may collect files that record interaction with this Application (System logs) use other Personal Data (such as the IP Address) for this purpose.

Information not contained in this policy

More details concerning the collection or processing of Personal Data may be requested from the Owner at any time. Please see the contact information at the beginning of this document.

How “Do Not Track” requests are handled

This Application does not support “Do Not Track” requests.
To determine whether any of the third-party services it uses honor the “Do Not Track” requests, please read their privacy policies.

Changes to this privacy policy

The Owner reserves the right to make changes to this privacy policy at any time by giving notice to its Users on this page and possibly within this Application and/or – as far as technically and legally feasible – sending a notice to Users via any contact information available to the Owner. It is strongly recommended to check this page often, referring to the date of the last modification listed at the bottom.

Should the changes affect processing activities performed on the basis of the User’s consent, the Owner shall collect new consent from the User, where required.

Definitions and legal references

Personal Data (or Data)

Any information that directly, indirectly, or in connection with other information — including a personal identification number — allows for the identification or identifiability of a natural person.

Usage Data

Information collected automatically through this Application (or third-party services employed in this Application), which can include: the IP addresses or domain names of the computers utilized by the Users who use this Application, the URI addresses (Uniform Resource Identifier), the time of the request, the method utilized to submit the request to the server, the size of the file received in response, the numerical code indicating the status of the server’s answer (successful outcome, error, etc.), the country of origin, the features of the browser and the operating system utilized by the User, the various time details per visit (e.g., the time spent on each page within the Application) and the details about the path followed within the Application with special reference to the sequence of pages visited, and other parameters about the device operating system and/or the User’s IT environment.

User

The individual using this Application who, unless otherwise specified, coincides with the Data Subject.

Data Subject

The natural person to whom the Personal Data refers.

Data Processor (or Data Supervisor)

The natural or legal person, public authority, agency or other body which processes Personal Data on behalf of the Controller, as described in this privacy policy.

Data Controller (or Owner)

The natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of Personal Data, including the security measures concerning the operation and use of this Application. The Data Controller, unless otherwise specified, is the Owner of this Application.

This Application

The means by which the Personal Data of the User is collected and processed.

Service

The service provided by this Application as described in the relative terms (if available) and on this site/application.

European Union (or EU)

Unless otherwise specified, all references made within this document to the European Union include all current member states to the European Union and the European Economic Area.

Cookies

Small sets of data stored in the User’s device.


Legal information

This privacy statement has been prepared based on provisions of multiple legislations, including Art. 13/14 of Regulation (EU) 2016/679 (General Data Protection Regulation).

This privacy policy relates solely to this Application, if not stated otherwise within this document.