MétaCan
Menu
Back to cohort
Record W4410769867 · doi:10.2196/69756

Clinician Needs and Requirements for a Decision Aid Navigator: Qualitative Study

2025· article· en· W4410769867 on OpenAlexvenueno aff
Brad Morse, Carrie Reale, An Nguyen, Erin Latella, Hannah Bauguess, Shilo Anders, Pamela Roberts, Spencer L. SooHoo, Robert El‐Kareh, Andrey Soares, Lisa M. Schilling

Bibliographic record

VenueJMIR Human Factors · 2025
Typearticle
Languageen
FieldHealth Professions
TopicPatient-Provider Communication in Healthcare
Canadian institutionsnot available
FundersAgency for Healthcare Research and Quality
KeywordsPreprintEngineeringPsychologyComputer scienceWorld Wide Web

Abstract

fetched live from OpenAlex

Background: Decision aids (DAs) are important tools that support shared decision-making (SDM) between clinicians and patients, enabling patients to be more informed and engaged in decisions regarding their care. The use of DAs can increase patient knowledge, reduce decisional regret, and engage the clinician and patient in meaningful dialog. Despite proven effectiveness in enhancing patient-centered care, a gap remains in clinician use of DAs. Known clinician barriers to using DAs include (1) time constraints, (2) concerns about the match between patient need and available DAs, (3) forcing users to leave the electronic health record (EHR) to access DAs, and (4) the burden of manually entering data into the DA. Objective: This qualitative study identified the needs and requirements of clinicians to inform the design of a clinician-facing, EHR-integrated, Substitutable Medical Applications, Reusable Technologies (SMART; SMART Health IT) on Fast Healthcare Interoperability Resources (FHIR) (HL7) app, the Decision Aid Navigator (DEAN; University of Colorado Anschutz Medical Campus). The Navigator identifies and surfaces DAs that are relevant to a patient's health care conditions (eg, atrial fibrillation), current care (eg, not on anticoagulation), and demographics (eg, check the youngest age for the stroke prevention), and facilitates documentation of SDM discussions and decisions. Methods: We conducted 13 semistructured interviews with clinicians who were recruited from 4 academic medical centers. Interviews included a demonstration of an initial, mid-fidelity, DEAN app prototype that was designed to address DA use and barriers described in the literature. The interviews focused on clinician context and use of the prototype, affordances and barriers to using the system, and clinician needs and requirements of the system. We used qualitative content analysis to code and reduce the data, using a consensus-making approach, and identify emerging themes. Results: We identified 3 overarching themes: (1) streamlined functionality may simplify workflow and decrease the burden of DA use and SDM; (2) clinicians need appropriate competencies to effectively use the Navigator and relevant DAs; and (3) trust that the Navigator suggests prevetted DAs. Unanimously, clinicians shared that the DEAN Navigator should be integrated into the EHR. To accomplish this clear priority, clinicians stated that they needed the requisite competencies to successfully use the tool within their workflow and build trust with the tool itself. Conclusions: Better tools to support and harness the benefits of SDM are needed. Overcoming the barriers of using DAs is paramount. Tools designed and developed to support DA use must be integrated into the EHR efficiently to create an opportunity for uptake of the technology by busy clinicians. If tools like DEAN can streamline the cumbersome process of documenting the use of DAs, more clinicians may potentially use DAs with their patients, given the right context and appropriate DA.

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

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0380.068
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.002
Science and technology studies0.0100.008
Scholarly communication0.0050.006
Open science0.0030.006
Research integrity0.0030.004
Insufficient payload (model declined to judge)0.0030.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.428
GPT teacher head0.608
Teacher spread0.181 · 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 designQualitative
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

Citations1
Published2025
Admission routes1
Has abstractyes

Explore more

Same venueJMIR Human FactorsSame topicPatient-Provider Communication in HealthcareFrench-language works237,207