The evolving role of patient preference studies in health-care decision-making, from clinical drug development to clinical care management
Bibliographic record
Abstract
Introduction: There is a growing trend of using patient preference studies to help incorporate the patient perspective into clinical drug development, care management, and health-care decision-making. Collecting and interpreting patient preference data is integral to multi-stakeholder engagement, patient-centric drug development, and clinical care management. Operationally, challenges exist in understanding ‘when’ and ‘how’ to embark on patient preference studies. This review will provide a brief overview of stated-preference methods, discuss applications throughout the clinical drug development and care management, and highlight how preference studies serve as a powerful tool for quantifying patient experiences for better outcomes.Areas covered: We present case studies to complement the different applications of stated-preference methods in clinical drug development and care management. We discuss the applications of preference data to help inform evidence-based patient advocacy, clinical development strategy, operational feasibility, regulator benefit-risk assessments, health technology assessments, and clinical decision-making.Expert commentary: Patient preference studies can serve as a powerful tool to engage patients and their communities as well as quantify the patient voice across different stages of clinical drug development and care management to support patient-centric health-care decision-making. It is expected that the application of these strategies will quickly advance in the coming years.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.154 | 0.257 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.005 | 0.003 |
| Bibliometrics | 0.005 | 0.010 |
| Science and technology studies | 0.001 | 0.007 |
| Scholarly communication | 0.008 | 0.010 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.005 | 0.008 |
| Insufficient payload (model declined to judge) | 0.008 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".