MétaCan
Menu
Back to cohort
Record W2596012313 · doi:10.2196/mhealth.7073

Content, Usability, and Utilization of Plain Language in Breast Cancer Mobile Phone Apps: A Systematic Analysis

2017· article· en· W2596012313 on OpenAlexvenueno aff
Tamar Ginossar, Sayyed Fawad Ali Shah, Andrew J. West, Joshua M. Bentley, Charlene Caburnay, Matthew W. Kreuter, Anita Y. Kinney

Bibliographic record

VenueJMIR mhealth and uhealth · 2017
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
FundersNational Institute of Diabetes and Digestive and Kidney DiseasesNational Cancer Institute
KeywordsUsabilityBreast cancerMobile phoneMedicineMammographyInternet privacyPhoneApp storeCancerWorld Wide WebComputer scienceInternal medicine

Abstract

fetched live from OpenAlex

BACKGROUND: Breast cancer is one of the leading contributors to preventable illness and death among women. Although mobile phone apps provide unprecedented opportunity to engage women along the cancer continuum, little is known about the availability, content, and usability of breast cancer mobile phone apps. OBJECTIVE: This study analyzed the content and adherence to literate design standards of all breast cancer-related apps available on the App Store and Google Play, as well as the relationship between their content, user ratings, and price. METHODS: Following identification and downloading of all available breast cancer mobile phone apps in October 2015, 101 apps were confirmed as focusing on breast cancer. Based on prior research, we adapted and applied a content analysis scheme that was specific to breast cancer apps, including their main purpose, relevance to the cancer care continuum, and adherence to usability standards outlined by the Institute of Medicine (IOM). RESULTS: The most common aim of apps was educational (73/101, 72.3%), followed by behavior change (24/101, 23.9%), fundraising (20/101, 19.8%), and advocacy (14/101, 13.9%). On the cancer continuum, primary prevention (strategies to prevent cancer cells from occurring) was mentioned in almost one-third of the apps (30/101, 29.7%). Less than half of the apps (46/101, 45.5%) presented information about mammography and/or breast clinical exam, and 53 apps (52.5%) discussed breast self-exam (which is no longer recommended). Symptoms of cancer prediagnosis, such as a lump, were discussed in almost half of the apps (48/101, 47.5%) and a similar number of apps included information about genetic risk for breast cancer (47/101, 46.5%). Information about breast cancer diagnosis was included in 42 apps (41.58%) and 43 (42.6%) apps discussed treatment options. Survivorship issues were addressed in 17 (16.8%) apps. Only one (1.0%) app discussed hospice. Adherence to usability recommendations was low. The median composite score was 3 (mean 2.60, SD 1.20) of the six recommended usability items. With eight plain language items, the median of the composite health literacy score was 5 (mean 5.06, SD 2.00). Most apps did not use easy-to-understand words (44/101, 43.6%) and few (24/101, 23.8%) defined key terms. CONCLUSIONS: Current breast cancer apps provide important information about breast cancer, but the most common topic covered is breast self-examination, a non-evidence-based screening strategy. Apps that focus on evidence-based strategies on the cancer continuum are needed, with a notable pressing need for apps that would address survivorship and end of life. Finally, developers of breast cancer apps should adhere to IOM standards to meet the needs of diverse populations and reduce current disparities.

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 distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.133
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0020.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

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.119
GPT teacher head0.489
Teacher spread0.370 · 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 teacher head, not a consensus.

Study designObservational
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

Citations57
Published2017
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealthSame topicMobile Health and mHealth ApplicationsFrench-language works237,207