Clinicians’ Perceptions of an Artificial Intelligence–Based Blood Utilization Calculator: Qualitative Exploratory Study
Bibliographic record
Abstract
BACKGROUND: According to the US Food and Drug Administration Center for Biologics Evaluation and Research, health care systems have been experiencing blood transfusion overuse. To minimize the overuse of blood product transfusions, a proprietary artificial intelligence (AI)-based blood utilization calculator (BUC) was developed and integrated into a US hospital's electronic health record. Despite the promising performance of the BUC, this technology remains underused in the clinical setting. OBJECTIVE: This study aims to explore how clinicians perceived this AI-based decision support system and, consequently, understand the factors hindering BUC use. METHODS: We interviewed 10 clinicians (BUC users) until the data saturation point was reached. The interviews were conducted over a web-based platform and were recorded. The audiovisual recordings were then anonymously transcribed verbatim. We used an inductive-deductive thematic analysis to analyze the transcripts, which involved applying predetermined themes to the data (deductive) and consecutively identifying new themes as they emerged in the data (inductive). RESULTS: We identified the following two themes: (1) workload and usability and (2) clinical decision-making. Clinicians acknowledged the ease of use and usefulness of the BUC for the general inpatient population. The clinicians also found the BUC to be useful in making decisions related to blood transfusion. However, some clinicians found the technology to be confusing due to inconsistent automation across different blood work processes. CONCLUSIONS: This study highlights that analytical efficacy alone does not ensure technology use or acceptance. The overall system's design, user perception, and users' knowledge of the technology are equally important and necessary (limitations, functionality, purpose, and scope). Therefore, the effective integration of AI-based decision support systems, such as the BUC, mandates multidisciplinary engagement, ensuring the adequate initial and recurrent training of AI users while maintaining high analytical efficacy and validity. As a final takeaway, the design of AI systems that are made to perform specific tasks must be self-explanatory, so that the users can easily understand how and when to use the technology. Using any technology on a population for whom it was not initially designed will hinder user perception and the technology's use.
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.023 | 0.050 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.007 | 0.008 |
| Scholarly communication | 0.005 | 0.005 |
| Open science | 0.002 | 0.004 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 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 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".