Development of a web-based patient decision aid for initiating disease modifying anti-rheumatic drugs using user-centred design methods
Bibliographic record
Abstract
BACKGROUND: A main element of patient-centred care, Patient Decision Aids (PtDAs) facilitate shared decision-making (SDM). A recent update of the International Patient Decision Aids Standards (IPDAS) emphasised patient involvement during PtDA development, but omitted a methodology for doing so. This article reports on the value of user-centred design (UCD) methods for the development of a PtDA that aims to support inflammatory arthritis patients in their choice between disease modifying anti-rheumatic drugs (DMARDs). METHODS: The IPDAS development process model in combination with UCD methods were applied. The process was overseen by an eight-member multidisciplinary steering group. Patients and health professionals were iteratively consulted. Qualitative in-depth interviews combined with rapid prototyping were conducted with patients to assess their needs for specific functionality, content and design of the PtDA. Group meetings with health professionals were organized to assess patients' needs and to determine how the PtDA should be integrated into patient pathways. The current literature was reviewed to determine the clinical evidence to include in the PtDA. To evaluate usability among patients, they were observed using the PtDA while thinking aloud and then interviewed. RESULTS: The combination of patient interviews with rapid prototyping revealed that patients wanted to compare multiple DMARDs both for their clinical aspects and implications for daily life. Health professionals mainly wanted to refer patients to a reliable, easily adjustable source of information about DMARDs. A web-based PtDA was constructed consisting of four parts: 1) general information about SDM, inflammatory arthritis and DMARDs; 2) an application to compare particular DMARDs; 3) value clarification exercises; and 4) a printed summary of patients' notes, preferences, worries and questions that they could bring to discuss with their rheumatologist. CONCLUSIONS: The study demonstrated that UCD methods can be of great value for the development of PtDAs. The early, iterative involvement of patients and health professionals was helpful in developing a novel user-friendly PtDA that allowed patients to choose between DMARDs. The PtDA fits the values of all stakeholders and easily integrates with the patient pathway and daily workflow of health professionals. This collaborative designed PtDA may improve SDM and patient participation in arthritis care.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.018 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.004 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
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 teacher head, 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".