Open Access

Pembrolizumab in endometrial cancer: Where we stand now (Review)

  • Authors:
    • Aikaterini Aravantinou‑Fatorou
    • Angeliki Andrikopoulou
    • Michael Liontos
    • Oraianthi Fiste
    • Vasiliki E. Georgakopoulou
    • Meletios-Athanasios Dimopoulos
    • Maria Gavriatopoulou
    • Flora Zagouri
  • View Affiliations

  • Published online on: October 8, 2021
  • Article Number: 821
  • Copyright: © Aravantinou‑Fatorou et al. This is an open access article distributed under the terms of Creative Commons Attribution License.

Metrics: Total Views: 0 (Spandidos Publications: | PMC Statistics: )
Total PDF Downloads: 0 (Spandidos Publications: | PMC Statistics: )


Recently, immunotherapy has shown promising results in solid tumors. To the best of our knowledge, this is the first systematic review of published literature synthesizing all the available data and evaluating both the efficacy and safety of pembrolizumab in endometrial cancer. The present study was performed in accordance with the PRISMA guidelines. Eligible articles were identified by searching the MEDLINE and databases, using a predefined combination of the terms ‘endometrial cancer’ and ‘pembrolizumab’. Overall, nine articles incorporating data from 712 patients were eligible. Pembrolizumab was demonstrated to be an effective and safe therapeutic option for the management of advanced/metastatic endometrial cancer. Results of ongoing trials evaluating either pembrolizumab alone or in combination with other antineoplastic regimens are expected to confirm its efficacy in this setting of patients. Pembrolizumab appears to be both durable and robust in endometrial cancer. However, there is an emerging need for novel predictive biomarkers to guide clinical practice.
Something has gone wrong

HTTP Error 400

Well this is embarrassing. Something has gone wrong. Hopefully it is a transient error that will go away if you retry.

If the problem persists if you email our System Administrators letting them know what you were doing and telling them it was because:

Exception evaluating SpringEL expression: "dispArt?.images" (template: "article" - line 384, col 9)

and then they can get to work fixing it