MétaCan
Menu
Retour à la cohorte
Enregistrement W4379537147 · doi:10.1177/11769351231178587

Development of an eHealth Tool for Capturing and Analyzing the Immune-related Adverse Events (irAEs) in Cancer Treatment

2023· article· en· W4379537147 sur OpenAlex

Pourquoi ce travail est dans la base

Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.

affAu moins un auteur déclare une institution canadienne dans l'instantané OpenAlex épinglé.

Notice bibliographique

RevueCancer Informatics · 2023
Typearticle
Langueen
DomaineMedicine
ThématiqueCancer survivorship and care
Établissements canadiensPrincess Margaret Cancer CentreToronto Metropolitan UniversityUniversity of WaterlooUniversity of TorontoYork University
Organismes subventionnairesnon disponible
Mots-clésOperationalizationeHealthComputer scienceMedicineAndroid (operating system)Agile software developmentHealth careSoftware engineering

Résumé

récupéré en direct d'OpenAlex

Introduction: Immunotherapy has revolutionized the treatment of many different types of cancer, but it is associated with a myriad of immune-related adverse events (irAEs). Patient-reported outcome (PRO) measures have been identified as valuable tools for continuously collecting patient-centered data and are frequently used in oncology trials. However, few studies still research an ePRO follow-up approach on patients treated with Immunotherapy, potentially reflecting a lack of support services for this population. Methods: The team co-developed a digital platform (V-Care) using ePROs to create a new follow-up pathway for cancer patients receiving immunotherapy. To operationalize the first 3 phases of the CeHRes roadmap, we employed multiple methods that were integrated throughout the development process, rather than being performed in a linear fashion. The teams employed an agile approach in a dynamic and iterative manner, engaging key stakeholders throughout the process. Results: The development of the application was categorized into 2 phases: "user interface" (UI) and "user experience" (UX) designs. In the first phase, the pages of the application were segmented into general categories, and feedback from all stakeholders was received and used to modify the application. In phase 2, mock-up pages were developed and sent to the Figma website. Moreover, the Android Package Kit (APK) of the application was installed and tested multiple times on a mobile phone to proactively detect and fix any errors. After resolving some technical issues and adjusting errors on the Android version to improve the user experience, the iOS version of the application was developed. Discussion: By incorporating the latest technological developments, V-Care has enabled cancer patients to have access to more comprehensive and personalized care, allowing them to better manage their condition and be better informed about their health decisions. These advances have also enabled healthcare professionals to be better equipped with the knowledge and tools to provide more effective and efficient care. In addition, the advances in V-Care technology have allowed patients to connect with their healthcare providers more easily, providing a platform to facilitate communication and collaboration. Although usability testing is necessary to evaluate the efficacy and user experience of the app, it can be a significant investment of time and resources. Conclusion: The V-Care platform can be used to investigate the reported symptoms experienced by cancer patients receiving Immune checkpoint inhibitors (ICIs) and to compare them with the results from clinical trials. Furthermore, the project will utilize ePRO tools to collect symptoms from patients and provide insight into whether the reported symptoms are linked to the treatment. Clinical Relevance: V-Care provides a secure, easy-to-use interface for patient-clinician communication and data exchange. Its clinical system stores and manages patient data in a secure environment, while its clinical decision support system helps clinicians make decisions that are more informed, efficient, and cost-effective. This system has the potential to improve patient safety and quality of care, while also helping to reduce healthcare costs.

Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.

Prédiction distillée sur la base complète

Imitation des enseignants

Ni prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.

score de la tête « metaresearch » (Codex)0,000
score de la tête « metaresearch » (Gemma)0,000
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesaucune
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Observationnel · Signal consensuel: aucune
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,644
Score d'incertitude au seuil0,364

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0000,000
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0000,000
Bibliométrie0,0000,000
Études des sciences et des technologies0,0000,000
Communication savante0,0000,000
Science ouverte0,0000,000
Intégrité de la recherche0,0000,000
Charge utile insuffisante (le modèle a refusé de juger)0,0000,000

Scores machine (provisoires)

Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.

Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.

Tête enseignante Opus0,038
Tête enseignante GPT0,334
Écart entre enseignants0,296 · la distance entre les deux têtes enseignantes sur ce seul travail
Statut de validationscore_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle