Invasive Pulmonary Adenocarcinoma with Lepidic Growth Pattern in a Pregnant Patient

Among the differential diagnoses that should be considered in acute respiratory failure (ARF) are infectious processes, autoimmune diseases, interstitial pulmonary fibrosis, and pulmonary neoplasia. Timely diagnosis of lung neoplasia is complicated in the early stages. An opportune diagnosis, as well as the specific treatment, decrease mortality. ARF occurs 1 in 500 pregnancies and is most common during the postpartum period. Among the specific etiologies that cause ARF during pregnancy that must be considered are: (1) preeclampsia; (2) embolism of amniotic fluid; (3) peripartum cardiomyopathy; and (4) trophoblastic embolism. The case of a 36-year-old patient with a 33-week pregnancy and ARF is presented. The patient presented dyspnea while exerting moderate effort that progressed to orthopnea and type 1 respiratory insufficiency. Imaging studies showed bilateral alveolar infiltrates and predominantly right areas of consolidation. Blood cultures, a galactomannan assay and IgG antibodies against mycoplasma pneumoniae, were reported as negative. Autoimmune etiology was ruled out through an immunoassay. A percutaneous pulmonary biopsy was performed and an invasive pulmonary adenocarcinoma with lepidic growth pattern (i.e. lepidic pulmonary adenocarcinoma, LPA) result was reported. This etiology is rare and very difficult to recognize in acute respiratory failure cases. After infectious, autoimmune and interstitial lung fibrosis have been excluded the clinician must suspect of lung cancer in a patient with acute respiratory failure and chest imaging compatible with the presence of ground-glass nodular opacities, a solitary nodule or mass with bronchogram, and lung consolidation. In the presence of acute respiratory failure, the suspicion of pulmonary neoplasia in an adult of reproductive age must be timely. Failure to recognize this etiology can lead to fatal results.

Abstract licence: CC BY-NC

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.