MétaCan
Menu
← Back to cohort
Record W4408283562 · doi:10.2196/57474

Preferences and Willingness to Pay for Health App Assessments Among Health Care Stakeholders: Discrete Choice Experiment

2025· article· en· W4408283562 on OpenAlexvenueno aff
Anna-Lena Frey, Simon Leigh, Carla Toro, Carme Pratdepàdua Bufill, Charles McCay, Tatjana Prenđa Trupec, Giuseppe D’Avenio, Menno Kok, Antanas Montvila, Philipp Goedecker, Petra Hoogendoorn

Bibliographic record

VenueJMIR mhealth and uhealth · 2025
Typearticle
Languageen
FieldHealth Professions
TopicMobile Health and mHealth Applications
Canadian institutionsnot available
Fundersnot available
KeywordsPreprintWillingness to payHealth caremHealthPsychologyMarketingBusinessInternet privacyComputer scienceEconomicsWorld Wide Web

Abstract

fetched live from OpenAlex

BACKGROUND: The adoption of high-quality health apps has been slow, despite the myriad benefits associated with their use. This is partly due to concerns regarding the effectiveness, safety, and data privacy of such apps. Quality assessments with robust and transparent criteria can address these concerns and, thereby, encourage the use of high-quality apps. However, a major challenge for such assessments is reaching a scale at which a substantial proportion of the more than 350,000 available health apps can be evaluated. OBJECTIVE: To support the scaling of health app quality assessments, this study aimed to examine the preferences and willingness to pay for assessments with different value propositions among potential customers. METHODS: We conducted 2 discrete choice experiments: one with 41 health app developers and another with 46 health system representatives (from health care institutions, authorities, and insurers) from across Europe. Mixed logit models were applied to examine the impact of assessment attributes on participants' choices as well as to calculate marginal willingness to pay and predicted assessment uptake. RESULTS: Among health app developers, the attributes with the largest impact on assessment choices were the associated clinical care uptake (integration into clinical guidelines and reimbursement or procurement) and cost (purchase price). Increased willingness to use assessed apps and app store integration of assessment results had a moderate impact on choices, while required developer time investment and time until assessment results become available made the smallest contribution. Among health system representatives, increased willingness of clinicians and patients to use evaluated apps had the greatest impact on assessment choices, followed by cost. Time until assessment result availability and the percentage of peers recommending the assessment made a moderate contribution, while reassessment frequency had the smallest impact on choices. On average, health app developers were willing to pay an additional €9020 (95% CI €4968-€13,072) if an assessment facilitates guideline integration and procurement or reimbursement (at the time of data collection, €1=US $1.11), while health system representatives were, on average, willing to pay €7037 (95% CI €4267-€9806) more if an assessment results in a large, rather than a small, increase in willingness to use the evaluated app. The predicted uptake of assessments that offer the preferred values for all attributes was 88.6% among app developers and 91.1% among health system representatives. CONCLUSIONS: These findings indicate that, to maximize uptake and willingness to pay among health app developers, it is advisable for assessments to facilitate or enable clinical guideline integration and reimbursement or procurement for high-scoring apps. Assessment scaling thus requires close collaboration with health authorities, health care institutions, and insurers. Furthermore, if health system organizations are targeted as customers, it is essential to provide evidence for the assessment's impact on patients' and clinicians' willingness to use health apps.

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.018
metaresearch head score (Gemma)0.031
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.018
Threshold uncertainty score0.095

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0180.031
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0000.000
Science and technology studies0.0010.002
Scholarly communication0.0030.002
Open science0.0010.002
Research integrity0.0040.004
Insufficient payload (model declined to judge)0.0110.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.173
GPT teacher head0.537
Teacher spread0.364 · 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 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

Citations0
Published2025
Admission routes1
Has abstractyes

Explore more

Same venueJMIR mhealth and uhealth→Same topicMobile Health and mHealth Applications→French-language works237,207→