EUVIMEDEUVIMED entdecken
FallberichtOpen Access · CC BY 4.0

Case Series: Can Daily Patient‐Reported Outcome Measures Be Implemented for Cancer‐Related Fatigue?

Alexander Tilg iD, Andreas Meryk iD, Johannes G Weiss, Roman Crazzolara iD

Cancer Reports · 2026-06 · 9 (6)

DOI: 10.1002/cnr2.70616 ↗

Kurz gefasst

Fallbericht in der Zeitschrift Cancer Reports, online erschienen am 23.06.2026. Verfasst von Alexander Tilg und 3 weiteren Autor:innen. Beteiligte Einrichtung: Medical University of Innsbruck, Innsbruck, Austria. Hauptthemen laut MEDLINE: Fatigue, Patient Reported Outcome Measures, Precursor Cell Lymphoblastic Leukemia-Lymphoma, Precursor B-Cell Lymphoblastic Leukemia-Lymphoma. Die Arbeit nennt 21 Literaturangaben. Der Volltext ist frei zugänglich (Open Access, CC BY 4.0). Gefördert von: Kinderkrebshilfe Tirol und Vorarlberg, Kinderhilfe Südtirol-Regenbogen.

AbstractSchlagwörterBibliografische AngabenZitierenVerwandte Studien

Abstract (Originalsprache)

Background

Cancer‐related fatigue (CrF), a prevalent and debilitating symptom among cancer patients, remains underrecognized and unstandardized in routine oncology care. To address this, we introduced a new digital tool for daily CrF measurement and integration in routine cancer treatment. Case This case series investigates the use of the ePROtect app for daily CrF assessment in two pediatric acute lymphoblastic leukemia (ALL) patients. Data were collected up to 2 weeks after the end of intensive therapy (before the start of maintenance) and analyzed using two questions informed by the National Comprehensive Cancer Network (NCCN), each offering five possible responses and categorizing fatigue into different subclasses. This analysis compares two 3‐year‐old girls with pre‐B ALL, one with standard risk (SR) and favorable genetics, the other one with poor therapy response and stratified to high risk (HR) treatment. The SR patient responded well to treatment, experiencing severe CrF on only 6% of the treatment days. In contrast, the HR patient required intensified treatment with multiple re‐induction phases, resulting in more frequent hospitalizations and severe CrF on 19.4% of the treatment days. CrF assessments were conducted daily for both patients, achieving 98.6% and 69.5% completion rates throughout intensive therapy, for the SR and HR patient, respectively.

Conclusion

This case series illustrates the feasibility and potential suitability of our tool using PROMs for CrF assessment. Furthermore, it highlights the correlation between treatment intensity, complications, and CrF levels, underlying the importance of systematically measuring fatigue in cancer patients. Such measurement may inform future efforts to develop and refine individualized supportive care strategies.

Schlagwörter

MeSH-Schlagwörter (MEDLINE)

FatiguePatient Reported Outcome MeasuresPrecursor Cell Lymphoblastic Leukemia-LymphomaPrecursor B-Cell Lymphoblastic Leukemia-LymphomaHumansFemaleChild, PreschoolAntineoplastic Combined Chemotherapy Protocols

Stichwörter der Autor:innen

cancer‐related fatiguechildrendaily PROMleukemia

Autor:innen und Institutionen

  • Medical University of Innsbruck, Innsbruck, Austria.

ORCID-Profile: Alexander Tilg, Andreas Meryk, Roman Crazzolara

Förderung

  • Kinderkrebshilfe Tirol und Vorarlberg
  • Kinderhilfe Südtirol-Regenbogen

Zitieren

APA

Tilg, A., Meryk, A., Weiss, J. G., & Crazzolara, R. (2026). Case Series: Can Daily Patient‐Reported Outcome Measures Be Implemented for Cancer‐Related Fatigue?. Cancer Reports, 9(6). https://doi.org/10.1002/cnr2.70616

Vancouver

Tilg A, Meryk A, Weiss JG, Crazzolara R. Case Series: Can Daily Patient‐Reported Outcome Measures Be Implemented for Cancer‐Related Fatigue?. Cancer Reports. 2026;9(6). doi:10.1002/cnr2.70616

BibTeX
@article{Tilg2026,
  author = {Tilg, Alexander and Meryk, Andreas and Weiss, Johannes G and Crazzolara, Roman},
  title = {Case Series: Can Daily Patient‐Reported Outcome Measures Be Implemented for Cancer‐Related Fatigue?},
  journal = {Cancer Reports},
  year = {2026},
  volume = {9},
  number = {6},
  doi = {10.1002/cnr2.70616}
}
Kostenlos starten →