Abstract
OBJECTIVES: Aspergillus coinfection in coronavirus disease 2019 patients has rarely been described but may be occurring among coronavirus disease 2019 patients admitted to ICUs. Previous reports of viral coinfections with Aspergillus, including influenza-associated pulmonary aspergillosis, suggest that coronavirus disease 2019-associated aspergillosis is plausible. This report aims to summarize what is known about coronavirus disease 2019 complicated by Aspergillus, introduces coronavirus disease 2019-associated pulmonary aspergillosis as a possible clinical entity, and describes reasons clinical suspicion of Aspergillus is warranted in the critical care setting. DATA SOURCES: We summarize the available evidence suggesting the existence of Aspergillus coinfection among severe coronavirus disease 2019 patients. This includes published coronavirus disease 2019 patient case series, a case description, and a review of potential biologic mechanisms. STUDY SELECTION: Reports of coronavirus disease 2019 patient attributes were selected if they included clinical, microbiologic, or radiologic signs of invasive fungal infection. DATA EXTRACTION: Data included in summary tables were identified through a literature search for coronavirus disease 2019-associated pulmonary aspergillosis. DATA SYNTHESIS: We present descriptive data extracted from coronavirus disease 2019-associated pulmonary aspergillosis case series current at the time of article submission. DISCUSSION: Pulmonary aspergillosis is known to occur among influenza patients requiring intensive care and is associated with increased mortality. If Aspergillus coinfections are occurring among coronavirus disease 2019 patients, early clinical suspicion and testing are needed to understand the epidemiology of these infections and prevent associated mortality. As the coronavirus disease 2019 pandemic unfolds, reports on the existence of this coinfection are needed, and opportunities to contribute cases of Aspergillus coinfection among coronavirus disease 2019 patients to an ongoing registry are described.