MétaCan
Menu
← Back to cohort
Record W4415666166 · doi:10.2196/65504

Obtaining Patient-Reported Outcome Data via a Home Patient Monitoring App: Development, Implementation, and Validation of Novel Interface Terminology

2025· article· en· W4415666166 on OpenAlexvenueno aff
Lucia Sacchi, Giordano Lanzola, Silvana Quaglini, Nicole Veggiotti, Silvia Panzarasa, Valentina Tibollo, Matteo Terzaghi, Itske Fraterman, Savannah Glaser, Manuel Ottaviano, Vadzim Khadakou, Vitali Hisko, Mor Peleg, Sofie Wilgenhof, Henk Mallo, Alexandra Kogan, David Glasspool, Stephanie Medlock, Laura Del Campo, Matteo Gabetta, Mimma Rizzo, Laura D. Locati, Paola Gabanelli, Sara Demurtas, Andrea Premoli, Szymon Wilk

Bibliographic record

VenueJMIR mhealth and uhealth · 2025
Typearticle
Languageen
FieldHealth Professions
TopicElectronic Health Records Systems
Canadian institutionsnot available
FundersHorizon 2020 Framework Programme
KeywordsTerminologyExploitInterface (matter)Clinical decision support systemDecision support systemUsabilityRemote patient monitoringOutcome (game theory)

Abstract

fetched live from OpenAlex

BACKGROUND: Adverse events (AEs) related to cancer treatment represent a valuable source of information that can be used to adjust therapy for individual patients. The NIH developed the Common Terminology Criteria for Adverse Events (CTCAE), a comprehensive standardized terminology for healthcare providers to consistently report AEs during patient visits. mHealth technologies, in principle, also allow AEs to be self-reported by patients in-between visits; however, the terminology poses challenges for them, both in selecting the correct symptom to report and in rating its severity. NIH developed the Patient-Reported Outcomes (PRO)-CTACE as the patient-oriented companion of the CTCAE. However, it shows some weaknesses in completeness and precision when used for continuous home patient monitoring and for decision support. OBJECTIVE: The aim of this work is to propose a new terminology for reporting AEs, which is easy for patients to use while also being clinically meaningful for healthcare providers, and easily exploitable by decision support systems. Moreover, we aim to demonstrate its implementation and validation within the CAPABLE EU project. METHODS: The development of the new terminology starts from the CTCAE, which includes a comprehensive list of signs and symptoms along with guidance for accurately grading their severity. Through a multi-step, participatory approach involving both patients and healthcare providers, we reduced and adapted the AE list for patient-oriented applications. During the CAPABLE project, the proposed terminology was integrated in a mobile app and evaluated within a clinical pilot study involving 86 patients who were monitored through the app for at least 6 months, and a control cohort of 133 patients monitored using standard care practices. RESULTS: The final terminology includes 124 AEs, 49 expressed as "present/absent", and 77 associated with four description levels. A mapping between the description levels and the original CTCAE grades enables running the decision support system embedded in the CAPABLE app. The pilot study demonstrated that the majority of the patients used the symptoms reporting functionality, sharing also 24 unique AEs that are not present in the PRO-CTCAE. Symptoms reported using the proposed terminology allowed the enactment of the clinical practice guidelines included in the CAPABLE decision support tool, triggering 11 distinct recommendations. CONCLUSIONS: The results obtained from the clinical study support our claim regarding the need for a novel terminology for the self-reporting of AEs, characterized by ease of use, completeness, and clinical meaningfulness. Finally, by mapping our terminology to the CTCAE, we demonstrated that it is possible to exploit self-reported data to trigger decision support rules consistent with clinical practice guidelines.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.014
metaresearch head score (Gemma)0.042
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.014
Threshold uncertainty score0.075

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0140.042
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.000
Science and technology studies0.0000.001
Scholarly communication0.0020.002
Open science0.0020.002
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0020.001

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.221
GPT teacher head0.527
Teacher spread0.305 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2025
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealth→Same topicElectronic Health Records Systems→French-language works237,207→