<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id><journal-id journal-id-type="publisher-id">medinform</journal-id><journal-id journal-id-type="index">7</journal-id><journal-title>JMIR Medical Informatics</journal-title><abbrev-journal-title>JMIR Med Inform</abbrev-journal-title><issn pub-type="epub">2291-9694</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v14i1e99472</article-id><article-id pub-id-type="doi">10.2196/99472</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Expert Perspectives on Transparency and Trust in AI-Based Clinical Decision Support Systems for Chest X-Ray Diagnosis: Qualitative Study</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Sriviboon</surname><given-names>Yada</given-names></name><degrees>MEng</degrees><xref ref-type="aff" rid="aff1"/></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Jiamsanguanwong</surname><given-names>Arisara</given-names></name><degrees>DEng</degrees><xref ref-type="aff" rid="aff1"/></contrib></contrib-group><aff id="aff1"><institution>Department of Industrial Engineering, Center of Excellence for Human-Robot Collaboration and Systems Integration, Faculty of Engineering, Chulalongkorn University</institution><addr-line>254 Phayathai Rd, Pathumwan</addr-line><addr-line>Bangkok</addr-line><country>Thailand</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Kalckreuth</surname><given-names>Niklas von</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Kim</surname><given-names>Su-Hwan</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Kanno</surname><given-names>Taro</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Authayarat</surname><given-names>Waratta</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Arisara Jiamsanguanwong, DEng, Department of Industrial Engineering, Center of Excellence for Human-Robot Collaboration and Systems Integration, Faculty of Engineering, Chulalongkorn University, 254 Phayathai Rd, Pathumwan, Bangkok, 10330, Thailand, +66 2218 6829; <email>arisara.j@chula.ac.th</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>5</day><month>11</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e99472</elocation-id><history><date date-type="received"><day>25</day><month>04</month><year>2026</year></date><date date-type="rev-recd"><day>15</day><month>09</month><year>2026</year></date><date date-type="accepted"><day>08</day><month>10</month><year>2026</year></date></history><copyright-statement>&#x00A9; Yada Sriviboon, Arisara Jiamsanguanwong. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 5.11.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/">https://medinform.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://medinform.jmir.org/2026/1/e99472"/><abstract><sec><title>Background</title><p>The integration of AI-based Clinical Decision Support Systems (AI-CDSS) into clinical practice has expanded rapidly, particularly in medical imaging. Beyond algorithmic performance, growing evidence suggests that clinicians&#x2019; engagement with AI-CDSS is shaped by how transparently systems communicate their outputs, and how trust is formed through human-AI interaction. However, a limited understanding of how these concepts are perceived by end users and developers continues to hinder real-world implementation.</p></sec><sec><title>Objective</title><p>This study aims to explore expert perspectives on transparency and trust in AI-CDSS for chest X-ray diagnosis, with a focus on the two-dimensional lens: user interface and users&#x2019; mental models.</p></sec><sec sec-type="methods"><title>Methods</title><p>A qualitative study was conducted using semistructured interviews with a total of 21 experts, including 11 radiologists and 10 AI experts experienced in AI-CDSS. Data were analyzed thematically to explore factors perceived to influence transparent communication and trust.</p></sec><sec sec-type="results"><title>Results</title><p>Three themes emerged: (1) perspective of transparency and trust, (2) user interface, and (3) users&#x2019; mental models. Findings reveal that trust is a dynamic calibration process developed through repeated use, feedback loops, and alignment with clinicians&#x2019; mental models, rather than algorithmic accuracy alone. Significant discrepancies were identified between how developers design system transparency and how clinicians interpret AI outputs.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>This study demonstrates that transparency and trust are achieved through interpretable outputs, clear communication of system limitations, and alignment with clinical workflows. Designing trustworthy AI-CDSS requires integrating transparent interface design with consideration of users&#x2019; knowledge, experience, and attitudes to support effective human-AI interaction.</p></sec></abstract><kwd-group><kwd>transparency</kwd><kwd>trust</kwd><kwd>user interface</kwd><kwd>user&#x2019;s mental model</kwd><kwd>AI-CDSS</kwd><kwd>AI-based Clinical Decision Support Systems</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>AI-based Clinical Decision Support Systems (AI-CDSS) represent an advanced evolution of conventional decision support technologies, leveraging AI techniques to augment clinical decision-making processes. By using sophisticated algorithms such as machine learning and deep learning, AI-CDSS are capable of interpreting and analyzing large volumes of complex medical data, including radiological images, laboratory results, and electronic health records [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. Rather than replacing medical professionals, these systems are designed to support the diagnostic process, assisting medical professionals in generating hypotheses, identifying patterns, and reducing the likelihood of diagnostic errors, thereby enhancing both the quality and efficiency of health care delivery [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>].</p><p>Despite these technological advances, the successful integration of AI-CDSS into clinical practice depends not only on algorithmic performance but also on how effectively these systems communicate their outputs to medical professionals and support informed human-AI collaboration [<xref ref-type="bibr" rid="ref5">5</xref>]. AI characteristics, such as lack of transparency, self-learning, and autonomous characteristics, bring uncertainty and pose significant challenges to establishing trust in the implementation of AI [<xref ref-type="bibr" rid="ref6">6</xref>]. Transparency refers to the disclosure of relevant information about a system&#x2019;s decision-making processes, procedures, performance, and functioning [<xref ref-type="bibr" rid="ref7">7</xref>]. In this study, transparent communication denotes the system-user communication aspect of transparency, specifically making information about AI-CDSS understandable to clinicians so they can evaluate its outputs. Explainability concerns explanations that clarify a model&#x2019;s internal functioning, whereas interpretability concerns the extent to which a model is understandable to a human [<xref ref-type="bibr" rid="ref8">8</xref>]. A perceived lack of transparency in system design and operation has been shown to undermine users&#x2019; trust in digital interfaces and decision-support processes [<xref ref-type="bibr" rid="ref9">9</xref>]. In the context of AI-CDSS, trust refers to the attitude that the system will help clinicians achieve their goals under conditions of uncertainty and vulnerability [<xref ref-type="bibr" rid="ref10">10</xref>]. Trust in a specific technology can further be understood through users&#x2019; beliefs about its functionality, helpfulness, and reliability [<xref ref-type="bibr" rid="ref11">11</xref>]. Trustworthiness refers to the properties of an AI system that justify placing trust in it [<xref ref-type="bibr" rid="ref12">12</xref>]. Trust is distinct from reliance, which refers to the behavioral use of automation; trust guides, but does not fully determine, reliance [<xref ref-type="bibr" rid="ref13">13</xref>]. In this study, trust calibration is used to describe whether clinicians&#x2019; trust is appropriately aligned with the system&#x2019;s reliability [<xref ref-type="bibr" rid="ref10">10</xref>].</p><p>When transparency is insufficient, medical professionals may struggle to understand how and on what basis AI systems generate recommendations, limiting their ability to evaluate, justify, or appropriately rely on AI outputs [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. As a result, when users are unable to discern the rationale behind AI recommendations, concerns about the system&#x2019;s effectiveness and the potential for patient harm are heightened among medical professionals [<xref ref-type="bibr" rid="ref16">16</xref>]. In contrast, transparent AI systems can support informed clinical judgment by enabling users to critically assess AI recommendations while retaining professional autonomy in decision-making [<xref ref-type="bibr" rid="ref17">17</xref>]. Nevertheless, adoption remains limited; recent reports indicate that 64% of medical professionals in the United States have not adopted AI technologies, with concerns about the credibility of AI-generated information cited as a primary barrier [<xref ref-type="bibr" rid="ref18">18</xref>].</p><p>To examine transparent communication in context, this study adopts a conceptual lens grounded in human-computer interaction (HCI) and human factors, drawing on the concepts of the Gulf of Execution and Gulf of Evaluation [<xref ref-type="bibr" rid="ref19">19</xref>] and Carroll and Olson's discussion of mental models in HCI [<xref ref-type="bibr" rid="ref20">20</xref>]. These frameworks inform a two-dimensional perspective on human-AI interaction: the technology dimension, concerning how information is conveyed through the user interface, and the human dimension, focused on users&#x2019; mental models, which are an individual&#x2019;s knowledge and understanding that form the basis for constructing reasonable actions and explanations about why certain actions are appropriate and predictive reasoning regarding both familiar and novel situations [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>].</p><p>Understanding transparency in AI-CDSS requires insights from both system developers and clinical end users [<xref ref-type="bibr" rid="ref23">23</xref>]. They may differ in their goals and interpretations of explainable AI, highlighting the value of considering both perspectives [<xref ref-type="bibr" rid="ref24">24</xref>]. AI experts play a critical role in determining how systems are developed and which features and explanations are implemented and presented through the user interface. In contrast, medical professionals, as end users, must interpret AI outputs through their mental models and integrate them into clinical reasoning. Discrepancies between how transparency is designed and how it is perceived can lead to misalignment in human-AI interaction, resulting in inappropriate reliance on AI recommendations. Therefore, incorporating perspectives from both AI experts and medical professionals is essential for understanding how user interface design and user mental models may support transparency and trust in real-world clinical decision-making contexts.</p><p>Accordingly, this study aims to explore expert perspectives on transparency and trust in AI-CDSS for chest X-ray diagnosis through a qualitative, semistructured interview approach. This study addresses the following research questions (RQs):</p><list list-type="bullet"><list-item><p>RQ1: How do medical professionals and AI experts perceive transparency and trust in AI-CDSS?</p></list-item><list-item><p>RQ2: What user interface-related information and design elements are perceived by medical professionals and AI experts as important for supporting transparent communication and/or trust in AI-CDSS?</p></list-item><list-item><p>RQ3: What aspects of users&#x2019; mental models are perceived by medical professionals and AI experts as important for supporting transparent communication and/or trust in AI-CDSS?</p></list-item></list><p>This study contributes to the literature on human-AI interaction in AI-CDSS in 2 key ways. First, it provides qualitative insights into what transparency and trust in AI-CDSS are perceived to mean from the perspectives of both AI experts and medical professionals, grounded in the context of chest X-ray diagnosis. Second, it elucidates what user interface design considerations and users&#x2019; mental models are perceived to support transparent communication and trust in AI-CDSS, providing qualitative insights to guide future design of AI-CDSS in real-world clinical settings.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Interview Design</title><p>This study used a qualitative research design using semistructured, one-to-one expert interviews to explore perceptions of transparency and trust in AI-CDSS for chest X-ray diagnosis. The interview approach was designed to elicit in-depth insights into user interface design considerations and users&#x2019; mental models perceived to support transparent communication and trust in AI-CDSS. One-to-one interviews were selected to encourage open discussion, enabling participants to articulate their perspectives based on professional experience.</p><p>All participants were asked to reflect on AI-CDSS for chest X-ray interpretation. No common scenario, AI-CDSS interface screenshot, or example AI output was presented; radiologists reflected on systems they had used, whereas AI experts referred to systems they had developed or worked with. The systems discussed were designed to detect or localize suspected abnormalities to assist clinicians in interpreting chest radiographs. Interview questions addressed user interface elements, including heatmaps, confidence information, and feedback mechanisms that allow users to report errors. The interview questions were developed from the research questions and a review of relevant literature on transparency, trust, user interface design, and users&#x2019; mental models in human-AI interaction. The guides began with questions about radiologists&#x2019; experience with AI-CDSS or AI experts&#x2019; goals in developing such systems, followed by questions on transparency and trust, user interface design, and users&#x2019; mental models. Questions were tailored to each group&#x2019;s role: radiologists were asked about clinical use and interpretation, whereas AI experts were asked about development and design considerations. Open-ended questions invited explanations and additional suggestions beyond the specified topics. To ensure clarity, relevance, and content validity, the interview guide was reviewed by domain experts using the Index of Item-Objective Congruence (IOC). Following revision, all interview questions received an IOC score of 1.00. Before data collection, the guide was reviewed by a health care innovation expert and a physician who served as the head of a radiology center. However, it was not formally pilot tested or cognitively pretested with representatives of the target groups. The interview guide was not modified after data collection began. Interviews were conducted in Thai to facilitate the accurate expression of participants&#x2019; perspectives. The validated interview questions are provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p></sec><sec id="s2-2"><title>Expert Selection</title><p>Purposive sampling was used to recruit experts whose professional backgrounds aligned with the objectives of the study. Potential participants were identified based on their professional roles and experience in either the development or clinical use of AI-CDSS for chest X-ray diagnosis. Eligible experts were invited to participate via direct contact (eg, email or professional networks), and participation was entirely voluntary.</p><p>Two groups of experts were included to capture complementary perspectives: (1) Medical professionals specializing in radiology for at least 5 years, with at least 3 years of experience using AI-CDSS for chest X-ray in clinical diagnostic practice. (2) AI experts with a minimum of 5 years of experience in developing AI technologies for medical imaging. The selection criteria for experts in this study were established based on the minimum threshold of 5 years of professional experience in their respective fields. This duration ensures that participants have surpassed the initial skill acquisition stages and possess the necessary practical wisdom to provide insightful perspectives [<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. For medical professionals, a minimum of 3 years of experience using AI-CDSS for chest X-ray was required, as the widespread adoption of AI-CDSS in clinical practice in Thailand has occurred only in recent years, beginning around 2021. The sample size for the qualitative interviews was guided by recommendations in qualitative research, suggesting that between 5 and 30 participants are generally sufficient for in-depth interviews, depending on the complexity of the research questions. Recruitment continued until theoretical saturation was achieved, that is, when additional interviews no longer yielded new insights relevant to the RQs [<xref ref-type="bibr" rid="ref27">27</xref>].</p></sec><sec id="s2-3"><title>Procedure</title><p>Qualitative data were collected through online interviews conducted via Microsoft Teams. Before the interviews, participants received an informed consent form detailing the study objectives, procedures, and ethical considerations, followed by a briefing using Thai-language slides covering the study objectives, interview structure, key concepts, and participants&#x2019; rights. Participants then completed a brief questionnaire collecting demographic and professional background information before their interviews began. The briefing slides and their English translation are provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. Separate, but conceptually aligned interview guides were used for AI experts and radiologists. Interviews typically lasted 20&#x2010;30 minutes. All interviews were audio-recorded with participants&#x2019; informed consent and transcribed verbatim for subsequent analysis.</p></sec><sec id="s2-4"><title>Data Analysis</title><p>Interview transcripts were analyzed using thematic analysis following the six-phase approach proposed by Braun and Clarke [<xref ref-type="bibr" rid="ref28">28</xref>]. This method was selected for its suitability in identifying patterned meanings across expert accounts while remaining grounded in participants&#x2019; perspectives and the study&#x2019;s RQs. Analysis began with familiarization through repeated reading of transcripts to gain an overall understanding of participants&#x2019; views. Initial codes were then generated inductively, focusing on statements related to transparency and trust, user interface, and users&#x2019; mental models in AI-CDSS use. Coding was conducted across both expert groups (radiologists and AI experts) to identify shared and differing perspectives. Next, codes were examined and grouped into potential themes by identifying conceptual relationships and recurring patterns across participants. These candidate themes were iteratively reviewed and refined to ensure internal coherence and clear distinction between themes. Finally, themes were reported with illustrative quotations to preserve participants&#x2019; voices and to demonstrate analytic grounding in the data. The quotations selected for reporting were translated from Thai into English by the principal investigator. The English translations were subsequently checked against the original Thai quotations in collaboration with coresearcher (AJ) to ensure accuracy and preserve the intended meaning.</p></sec><sec id="s2-5"><title>Ethical Considerations</title><p>The study was approved by the Research Ethics Review Committee for Research Involving Human Research Participants, Group I, Chulalongkorn University, Thailand (Certificate of Approval number 079/69). The protocol adhered to the Belmont Report (1979), Declaration of Helsinki (2013), Council for International Organizations of Medical Sciences (2016), Standards of Research Ethics Committee (2017), and National Policy for Human Research (2015).</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Overview</title><p>A total of 21 experts participated in the study, including 11 radiologists and 10 AI experts. Among the radiologists, 10 of 11 (91%) participants were female, and 1 of 11 (9%) participants was male. In terms of workplace, 7 of 11 (64%) participants worked in private hospitals, and 4 of 11 (36%) participants worked in public hospitals. Participants had substantial clinical experience, ranging from 5 to 33 years, with a mean of 16.0 (SD 8.94) years of clinical practice in radiology. All radiologists had direct experience using AI-CDSS for chest X-ray diagnosis, with a mean AI-CDSS usage experience of 4 (SD 0) years. On average, participants interpreted approximately 30.9 (SD 8.31) chest X-ray cases per day, reflecting routine engagement with high-volume diagnostic tasks. Among the AI experts, 3 of 10 (30%) participants were female, and 7 of 10 (70%) participants were male, with professional roles spanning professor, associate professor, assistant professor, lecturer, researcher, and chief technology officer (CTO). In terms of affiliation, 8 of 10 (80%) participants were affiliated with public universities, 1 of 10 (10%) participants was affiliated with a private university, and 1 of 10 (10%) participants was affiliated with an AI-based medical imaging company. The AI experts had a mean of 9.4 (SD 3.5) years of experience in AI and medical imaging&#x2013;related research or development, ensuring in-depth familiarity with model development, explainability techniques, and user interface design for chest X-ray applications. Participant characteristics for radiologists are presented in <xref ref-type="table" rid="table1">Table 1</xref>, and for AI experts in <xref ref-type="table" rid="table2">Table 2</xref>.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Characteristics of radiologist participants (n=11).</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">ID</td><td align="left" valign="bottom">Gender</td><td align="left" valign="bottom">Years in radiology</td><td align="left" valign="bottom">AI-CDSS<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup> experience (years)</td><td align="left" valign="bottom">Hospital type</td><td align="left" valign="bottom">Frequency of AI-CDSS use</td></tr></thead><tbody><tr><td align="left" valign="top">R1</td><td align="left" valign="top">Female</td><td align="left" valign="top">24</td><td align="left" valign="top">4</td><td align="left" valign="top">Private</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R2</td><td align="left" valign="top">Female</td><td align="left" valign="top">33</td><td align="left" valign="top">4</td><td align="left" valign="top">Private</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R3</td><td align="left" valign="top">Female</td><td align="left" valign="top">18</td><td align="left" valign="top">4</td><td align="left" valign="top">Private</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R4</td><td align="left" valign="top">Female</td><td align="left" valign="top">28</td><td align="left" valign="top">4</td><td align="left" valign="top">Private</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R5</td><td align="left" valign="top">Female</td><td align="left" valign="top">14</td><td align="left" valign="top">4</td><td align="left" valign="top">Private</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R6</td><td align="left" valign="top">Female</td><td align="left" valign="top">14</td><td align="left" valign="top">4</td><td align="left" valign="top">Private</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R7</td><td align="left" valign="top">Female</td><td align="left" valign="top">12</td><td align="left" valign="top">4</td><td align="left" valign="top">Public</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R8</td><td align="left" valign="top">Female</td><td align="left" valign="top">7</td><td align="left" valign="top">4</td><td align="left" valign="top">Public</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R9</td><td align="left" valign="top">Female</td><td align="left" valign="top">8</td><td align="left" valign="top">4</td><td align="left" valign="top">Private</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R10</td><td align="left" valign="top">Male</td><td align="left" valign="top">5</td><td align="left" valign="top">4</td><td align="left" valign="top">Public</td><td align="left" valign="top">Daily</td></tr><tr><td align="left" valign="top">R11</td><td align="left" valign="top">Female</td><td align="left" valign="top">13</td><td align="left" valign="top">4</td><td align="left" valign="top">Public</td><td align="left" valign="top">Daily</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>AI-CDSS: AI&#x2013;based Clinical Decision Support Systems. </p></fn></table-wrap-foot></table-wrap><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Characteristics of AI expert participants (n=10).</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">ID</td><td align="left" valign="bottom">Gender</td><td align="left" valign="bottom">Years in AI (medical imaging)</td><td align="left" valign="bottom">Highest degree</td><td align="left" valign="bottom">Affiliation type</td><td align="left" valign="bottom">Role/position</td></tr></thead><tbody><tr><td align="left" valign="top">A1</td><td align="left" valign="top">Female</td><td align="left" valign="top">10</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Associate professor</td></tr><tr><td align="left" valign="top">A2</td><td align="left" valign="top">Male</td><td align="left" valign="top">6</td><td align="left" valign="top">MD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Associate professor</td></tr><tr><td align="left" valign="top">A3</td><td align="left" valign="top">Female</td><td align="left" valign="top">8</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Lecturer</td></tr><tr><td align="left" valign="top">A4</td><td align="left" valign="top">Female</td><td align="left" valign="top">8</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Assistant professor</td></tr><tr><td align="left" valign="top">A5</td><td align="left" valign="top">Male</td><td align="left" valign="top">14</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Associate professor</td></tr><tr><td align="left" valign="top">A6</td><td align="left" valign="top">Male</td><td align="left" valign="top">9</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Assistant professor</td></tr><tr><td align="left" valign="top">A7</td><td align="left" valign="top">Male</td><td align="left" valign="top">15</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Private university</td><td align="left" valign="top">Professor</td></tr><tr><td align="left" valign="top">A8</td><td align="left" valign="top">Male</td><td align="left" valign="top">13</td><td align="left" valign="top">PhD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Associate professor</td></tr><tr><td align="left" valign="top">A9</td><td align="left" valign="top">Male</td><td align="left" valign="top">6</td><td align="left" valign="top">MD</td><td align="left" valign="top">AI-based medical imaging company</td><td align="left" valign="top">CTO<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup></td></tr><tr><td align="left" valign="top">A10</td><td align="left" valign="top">Male</td><td align="left" valign="top">5</td><td align="left" valign="top">MD</td><td align="left" valign="top">Public university</td><td align="left" valign="top">Researcher</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>CTO: chief technology officer.</p></fn></table-wrap-foot></table-wrap><p>The results use a participant coding scheme to attribute quotes and insights while preserving confidentiality. Each participant is identified using a shorthand code (X, Y, and Z), where X denotes the participant&#x2019;s role (Radiologist [R] or AI expert [A]), Y indicates gender (Male [M] or Female [F]), and Z represents years of professional experience in radiology or AI development in health care. A total of 266 attributed quotations were identified across the interview dataset. <xref ref-type="table" rid="table3">Table 3</xref> presents their distribution across the 3 themes and associated subthemes, together with sample quotations. The first theme, Perspective of transparency and trust, describes participants&#x2019; perspectives on transparency and trust when interacting with the AI-CDSS. The second theme, User Interface, highlights how specific user interface design elements facilitate clear communication and foster trust in the AI&#x2019;s recommendations. The third theme, Users&#x2019; Mental Models, illustrates how participants&#x2019; experience, attitude, and knowledge about AI shape their interpretation of the AI&#x2019;s outputs and their trust in the system. <xref ref-type="fig" rid="figure1">Figure 1</xref> presents an overview of the 3 themes, their associated subthemes, and the key findings within each subtheme.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Distribution of attributed quotations across the themes and subthemes, with sample quotes.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Themes and subthemes, n (%)<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="left" valign="bottom">Sample quotes</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Perspective of<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup> transparency and trust</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Transparency that clinicians need (n=24, 9%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;Radiologists don&#x2019;t expect to understand the whole model, but they need to know why it flags something.&#x201D; (A8, M, 13)</p></list-item><list-item><p>&#x201C;Heatmap shows what the AI is looking at.&#x201D; (A7, M, 15)</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Perceived role of AI (n=29, 10.9%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;AI is like a friend double-checking for me.&#x201D; (R3, F, 18)</p></list-item><list-item><p>&#x201C;If it flags something I didn&#x2019;t see, I&#x2019;ll recheck that spot.&#x201D; (R7, F, 12)</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Trust calibration (n=19,7.1%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;I trust it more when it shows confidence levels.&#x201D; (R5, F, 14)</p></list-item><list-item><p>&#x201C;We know which findings it&#x2019;s good or weak at.&#x201D; (R1, F, 24)</p></list-item><list-item><p>&#x201C;Users need to know what AI can and can&#x2019;t do.&#x201D;(A5, M, 14)</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">User interface<sup><xref ref-type="table-fn" rid="table3fn3">c</xref></sup></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>What information should be presented (n=42,15.8%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;Heatmap and confidence levels are most useful.&#x201D; (R9, F, 8)</p></list-item><list-item><p>&#x201C;If AI can&#x2019;t give context,. it may mislead on TB.&#x201D; (R8, F, 7)</p></list-item><list-item><p>&#x201C;Radiologists wanted AI to prioritize urgent abnormalities for quicker clinical action.&#x201D; (R5, F, 14)</p></list-item><list-item><p>&#x201C;Developers should provide details about the training data. what diseases it learned from.&#x201D; (A2, M, 6)</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>How should information be presented (n=27, 10.2%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;I prefer information shown as images rather than text. Numbers are okay, but not too much.&#x201D; (A1, F, 10)</p></list-item><list-item><p>&#x201C;Don&#x2019;t clutter the screen with too much info.&#x201D; (R6, F, 14)</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Feedback loop (n=14, 5.3%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;Feedback is a must; otherwise, errors persist.&#x201D; (A8, M, 13)</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">Users&#x2019; mental models<sup><xref ref-type="table-fn" rid="table3fn4">d</xref></sup></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Knowledge (n=54, 20.3%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;You don&#x2019;t need to understand deep algorithms, just where the answers come from.&#x201D; (R1, F, 24)</p></list-item><list-item><p>&#x201C;We need enough knowledge to use the system and interpret the results.&#x201D; (A5, M, 14)</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Experience (n=24, 9.0%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;We&#x2019;ve learned what it often gets wrong and check those again.&#x201D; (R9, F, 8)</p></list-item><list-item><p>&#x201C;Clinical experience and years in practice matter. For example, newly graduated doctors are more likely to trust the AI outputs without question.&#x201D; (R4, F, 28)</p></list-item><list-item><p>&#x201C;If doctors are involved from the start, they understand the AI better.&#x201D; (A2, M, 6)</p></list-item></list></td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Attitude (n=33, 12.4%)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>&#x201C;Younger doctors are more likely to use and trust the system because they grew up with technology.&#x201D; (R9, F, 8)</p></list-item><list-item><p>&#x201C;Doctors must be open to using it or they&#x2019;ll fall behind.&#x201D; (R10, M, 5)</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>n represents attributed quotations and % represents % of total quotations.</p></fn><fn id="table3fn2"><p><sup>b</sup>Theme total, n (%): 72 (27.1).</p></fn><fn id="table3fn3"><p><sup>c</sup>Theme total, n (%): 83 (31.2).</p></fn><fn id="table3fn4"><p><sup>d</sup>Theme total, n (%): 111 (41.7).</p></fn></table-wrap-foot></table-wrap><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>An overview of the 3 themes, their associated subthemes, and the key findings within each subtheme.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e99472_fig01.png"/></fig></sec><sec id="s3-2"><title>Theme 1: Perspective of Transparency and Trust</title><sec id="s3-2-1"><title>Overview</title><p>The perspective of transparency and trust in AI-CDSS was structured into 3 interrelated subthemes: Transparency That Clinicians Need, Perceived Role of AI, and Trust Calibration. These subthemes reflect how both radiologists and AI developers conceptualized the meaning and importance of transparency, the functional role of AI in clinical practice, and the dynamic process of trust formation.</p></sec><sec id="s3-2-2"><title>Transparency That Clinicians Need</title><p>Radiologists and AI experts converged on the view that transparency in AI-CDSS refers not to full algorithmic interpretability, but to the system&#x2019;s ability to communicate its reasoning and limitations in a manner that radiologists can meaningfully engage with. This form of functional transparency was widely seen as foundational to trust. One AI expert distinguished model transparency, concerning access to the system&#x2019;s internal logic, from information transparency, concerning the understandable communication of its outputs.</p><p>Participants from both groups emphasized that without visual or numerical explanations, such as heatmaps or confidence levels, AI-CDSS systems risk becoming &#x201C;black boxes&#x201D; and alienating their users. Participants described these explanations as helping clinicians understand:</p><disp-quote><p>What the AI is looking at when generating findings.</p><attrib>A7, M, 15 years of experience</attrib></disp-quote><p>Highlighted regions, confidence scores, and system rationales were viewed as interpretable cues that enable clinicians to scrutinize and contextualize AI outputs. As one AI expert remarked:</p><disp-quote><p>Radiologists don&#x2019;t expect to understand the whole model, but they need to know why it flags something; that&#x2019;s what explanation means to them.</p><attrib>A8, M, 13 years of experience</attrib></disp-quote><p>Turning to trust, both groups emphasized that it must be developed over time through consistent performance and transparent communication. While transparency facilitated trust formation, accuracy was seen as its core foundation:</p><disp-quote><p>Trust [in the AI] depends on its accuracy. If I know it&#x2019;s very accurate on a particular finding, I tend to trust it.</p><attrib>R1, F, 24 years of experience</attrib></disp-quote><p>Explanations aligned with clinical reasoning were also perceived to enhance the system&#x2019;s trustworthiness:</p><disp-quote><p>Providing an explanation makes it look more trustworthy and might make me trust it more.</p><attrib>R5, F, 14 years of experience</attrib></disp-quote></sec><sec id="s3-2-3"><title>Perceived Role of AI</title><p>Participants from both groups described AI-CDSS as a supportive tool that complements but does not replace clinical judgment. Rather than perceiving the system as authoritative, radiologists framed it as a &#x201C;second opinion&#x201D; or &#x201C;additional view&#x201D; that helps validate or challenge their initial impression. As one participant remarked, using the system was &#x201C;like playing a spot-the-difference game&#x201D; (R3, F, 18) where AI cues helped direct attention to potential oversights.</p><p>Several radiologists described a consistent 4-step process: (1) reviewing the original radiograph, (2) forming a preliminary diagnosis, (3) consulting the AI&#x2019;s output, and (4) revisiting the film to compare areas of agreement or discrepancy. Agreement reinforced their initial interpretation, whereas unexpected findings prompted further examination rather than automatic acceptance or dismissal. Radiologists described the AI-CDSS as a useful double-check mechanism to either confirm their own assessments or draw attention to possible oversights:</p><disp-quote><p>AI is like another friend helping me diagnose. If it flags the same area which I&#x2019;m concerned about, then we&#x2019;re done. If it flags something different, I&#x2019;ll investigate that spot further.</p><attrib>R3, F, 18 years of experience</attrib></disp-quote></sec><sec id="s3-2-4"><title>Trust Calibration</title><p>Several AI experts emphasized that system design alone cannot ensure appropriate trust. Rather, users&#x2019; mental models, their understanding of what the AI can and cannot do, play a critical role:</p><disp-quote><p>Achieving the right level of trust comes down to communication and AI literacy&#x2026; The system alone can&#x2019;t fix it; we need to talk to users about what the AI can and cannot do.</p><attrib>A6, M, 9 years of experience</attrib></disp-quote><p>Importantly, trust was not viewed as binary. Instead, experts described a need for trust calibration, where overtrust may lead to uncritical acceptance, and undertrust may result in dismissal of potentially helpful insights. Most participants believed undertrust to be more prevalent in practice:</p><disp-quote><p>Physicians are quite cautious, so under-trust happens more than over-trust in practice.</p><attrib>A5, M, 14 years of experience</attrib></disp-quote></sec></sec><sec id="s3-3"><title>Theme 2: User Interface</title><sec id="s3-3-1"><title>Overview</title><p>Participants&#x2019; perspectives on user interface design were organized around 3 interrelated subthemes: what information the system should present to users, how that information should be presented, and the feedback loop. Across these subthemes, both radiologists and AI experts emphasized the importance of clarity, intuitiveness, and alignment with clinical workflows, although their priorities differed according to their professional roles.</p></sec><sec id="s3-3-2"><title>What Information Should Be Presented</title><p>Participants in both groups identified specific types of information that they considered important for an AI-CDSS to present to support transparency. For radiologists, the most essential features were the visual heatmap, highlighting areas of suspected abnormality, and the confidence level associated with each finding. One radiologist explained:</p><disp-quote><p>The heatmap shows where AI is suspicious, how much it&#x2019;s suspicious in each spot, which helps boost my confidence, because I can see what it saw.</p><attrib>R10, M, 5 years of experience</attrib></disp-quote><p>Radiologists described heatmaps as helping them localize and evaluate AI-identified findings, whereas confidence information indicated the strength of each prediction. Although both were considered foundational, radiologists varied in the importance they assigned to each element. For instance:</p><disp-quote><p>I&#x2019;m mainly interested in the heatmap; the confidence level is only a little.</p><attrib>R11, F, 13 years of experience</attrib></disp-quote><p>Some radiologists also requested richer textual or visual explanations that communicated not only where an abnormality was detected but also why the AI produced its conclusion.</p><disp-quote><p>I&#x2019;d trust it more if it could explain how it got to its answer. That would make a real difference.</p><attrib>R6, F, 14 years of experience</attrib></disp-quote><p>Suggestions included distinguishing between types of detected lesions (eg, calcified nodule vs soft-tissue mass) and providing context-sensitive reasoning. Particularly for findings that typically require patient history, like tuberculosis, radiologists cautioned that AI predictions without context could lead to overdiagnosis or false reassurance:</p><disp-quote><p>If the AI can&#x2019;t account for clinical context, it might label something as TB and be misleading, which many of us find inaccurate.</p><attrib>R8, F, 7 years of experience</attrib></disp-quote><p>One participant recommended that such ambiguous outputs be either suppressed or clearly flagged as uncertain to prevent misinterpretation. Conversely, urgent and actionable abnormalities, such as pneumothorax, could be prioritized to support timely clinical action. Radiologists wanted information on how confidence scores were calculated, alongside broader performance measures such as sensitivity, specificity, and known limitations. As one noted:</p><disp-quote><p>Approximately how accurate is this model, and how much can I trust it? I want to know the range of what it&#x2019;s good and not good at.</p><attrib>R5, F, 14 years of experience</attrib></disp-quote><p>AI experts echoed many of these needs but proposed additional forms of information. In addition to heatmaps and scores, they suggested providing textual explanations that resemble mini radiology reports, generated via explainable or generative AI. For instance:</p><disp-quote><p>The AI sees a diffuse haziness in the right lung, suggestive of pneumonia, because the opacity has XXX characteristics.</p><attrib>A3, F, 8 years of experience</attrib></disp-quote><p>They emphasized the importance of model-centric transparency, such as detailing training data characteristics, model provenance, and blind spots. AI experts believed such background would help users understand why the AI behaves the way it does:</p><disp-quote><p>Developers should provide details about the training data, what diseases it learned from, and how balanced it was.</p><attrib>A2, M, 6 years of experience</attrib></disp-quote><p>Another area of emphasis was flagging uncertainty. AI experts suggested interface features for indicating low-confidence predictions (eg, color-coded warnings or disclaimers), allowing users to calibrate their trust accordingly. Conversely, high-confidence findings could be visually marked to reassure users:</p><disp-quote><p>If a prediction is borderline, the system should say so clearly. We don&#x2019;t want users to over-trust it by default.</p><attrib>A4, F, 8 years of experience</attrib></disp-quote><p>Overall, both groups regarded heatmaps and confidence levels as foundational to transparency, although radiologists emphasized actionable information, prioritization of urgent findings, and avoidance of misleading content, whereas AI developers emphasized broader system transparency, explanation depth, and interface adaptability.</p></sec><sec id="s3-3-3"><title>How Should Information Be Presented</title><p>Participants from both groups emphasized that AI outputs should be clinically usable: easy to perceive, quick to interpret, and aligned with real diagnostic workflows, while avoiding interface burden or cognitive overload. Radiologists particularly preferred control over when AI outputs became visible. Many wanted AI outputs to function as a secondary layer rather than being imposed upfront, allowing clinicians first to form an independent impression and then consult AI for confirmation or discrepancy-checking. This was reflected in requests for toggle-based interactions, where heatmaps can be switched on and off over the original image:</p><disp-quote><p>The heatmap could be shown by clicking once to overlay it on the original, like turning it on and off; however, it depends on the hospital settings.</p><attrib>R1, F, 24 years of experience</attrib></disp-quote><p>Radiologists also emphasized that AI-marked images should maintain visual comparability with standard reads:</p><disp-quote><p>The AI image should be the same size as the original film so doctors can clearly see the point the AI is indicating.</p><attrib>R1, F, 24 years of experience</attrib></disp-quote><p>Participants from both groups also emphasized managing information density and screen clutter, which they associated with cognitive load and decision time. Radiologists cautioned against overcrowded interfaces:</p><disp-quote><p>Be careful not to have too much information until the screen becomes messy.</p><attrib>R6, F, 14 years of experience</attrib></disp-quote><p>Radiologists also regarded excessive textual information as problematic and expressed irritation when interfaces fragmented attention unnecessarily, such as separating outputs into multiple views for minor findings:</p><disp-quote><p>If it splits out heatmaps for every finding, especially for tiny things, it becomes annoying.&#x201D;</p><attrib>R7, F, 12 years of experience</attrib></disp-quote><p>Another recurring concern involved clear visual mapping between highlighted regions and diagnostic meaning, particularly when multiple findings are present. Radiologists requested that heatmaps explicitly indicate which abnormality each region corresponds to:</p><disp-quote><p>I want the heatmap to clearly indicate which lesion it belongs to. If it&#x2019;s combined into one image, it should identify the location.</p><attrib>R10, M, 5 years of experience</attrib></disp-quote><p>From the AI experts&#x2019; perspective, these concerns aligned with a preference for visual rather than text-heavy presentation:</p><disp-quote><p>I prefer information shown as images rather than text. Numbers are okay, but not too much.</p><attrib>A1, F, 10 years of experience</attrib></disp-quote><p>AI experts additionally emphasized that presentation requirements are task-dependent, cautioning against one-size-fits-all visualization strategies:</p><disp-quote><p>How to show the heatmap depends more on the task. For COVID, we look at the overall lung pattern, not a single point, but for some diseases, you need segmentation or boundary boxes.</p><attrib>A6, M, 9 years of experience</attrib></disp-quote><p>They also stressed the importance of involving clinicians early in interface design to avoid cumulative microburdens:</p><disp-quote><p>Doctors should be involved from the beginning. Even one extra click is not okay if they do the task 100 times, that&#x2019;s 100 extra clicks.</p><attrib>A5, M, 14 years of experience</attrib></disp-quote><p>Relatedly, experts highlighted that interface familiarity and prioritization matter:</p><disp-quote><p>Design should ask doctors as the main users about what they want to see first, second, third. Even the old interface style matters because it links to user experience.</p><attrib>A6, M, 9 years of experience</attrib></disp-quote><p>Several AI experts described desirable enhancements in interaction and fidelity, while still adhering to a minimalist philosophy. For example, interactive image manipulation was suggested:</p><disp-quote><p>Ideally, the image should be interactive, and the user can rotate it and view it from different angles.</p><attrib>A1, F, 10 years of experience</attrib></disp-quote><p>Others emphasized that AI displays should not disrupt ongoing clinical work:</p><disp-quote><p>If original and AI images can be placed side by side or switched between modes easily, the key is that it must not interfere with the physician&#x2019;s workflow.</p><attrib>A8, M, 13 years of experience</attrib></disp-quote><p>Some experts advocated structuring heatmaps per abnormality to preserve interpretability. At the same time, restraint remained a shared design value:</p><disp-quote><p>Less is more. Don&#x2019;t make it complicated, provide enough information for decision-making.</p><attrib>A9, M, 6 years of experience</attrib></disp-quote><p>Overall, radiologists emphasized workflow protection and low-clutter clarity, whereas AI experts emphasized task-dependent visualization, clinician co-design, and interaction design that minimizes cumulative burden. Both groups emphasized presenting sufficient information for clinical decision-making without disrupting workflow.</p></sec><sec id="s3-3-4"><title>Feedback Loop</title><p>Participants also described transparency as an interactive process that should enable users to respond to AI outputs, identify errors, and contribute feedback for system improvement. Both radiologists and AI experts emphasized that feedback loops are essential for sustaining trust, calibrating reliance, and improving real-world performance. Radiologists consistently framed feedback as a &#x201C;must-have&#x201D; feature rather than an optional add-on, particularly because clinicians are the first to notice recurring errors or shifts in system behavior.</p><p>Radiologists emphasized the need for direct, integrated feedback mechanisms that would allow them to mark AI outputs as correct or incorrect, identify error locations, and optionally add brief comments. These features were considered especially important for recurrent false positives, such as nipple shadows, electrocardiogram (ECG) leads, or bone artifacts, which clinicians can easily recognize but which repeatedly undermine confidence when misclassified:</p><disp-quote><p>If the AI keeps misreading the same obvious things, it feels unreliable. Being able to flag those mistakes would really help.</p><attrib>R3, F, 18 years of experience</attrib></disp-quote><p>Participants emphasized that feedback should be simple, efficient, and integrated into the reading workflow, as indirect reporting may delay system improvement and reduce clinicians&#x2019; sense of agency.</p><p>AI experts further stressed that the depth and quality of feedback matter. Superficial signals alone (eg, binary correct/incorrect) were considered insufficient, whereas expert-level feedback, such as identifying error types, anatomical regions, or contextual causes, was seen as substantially more valuable for refining model behavior:</p><disp-quote><p>Feedback from experienced doctors is especially valuable because they can comment at a deeper level, not just right or wrong.</p><attrib>A1, F, 10 years of experience</attrib></disp-quote><p>Both groups cautioned that feedback mechanisms must be carefully designed so as not to burden clinicians or disrupt clinical workflows. AI experts emphasized that even small increases in interaction cost could quickly become unacceptable in high-volume practice:</p><disp-quote><p>We want feedback from clinicians every time they use the system, but it has to be effortless. The interaction must be simple, intuitive, and require as little movement and clicking as possible; otherwise, it won&#x2019;t be used in real practice.</p><p>[A5, M, 14 years of experience]</p></disp-quote><p>Overall, both groups regarded feedback as an interactive component of transparency but differed in emphasis. Radiologists emphasized its role in reporting recurring errors and maintaining an active role in AI use, whereas AI experts highlighted the importance of obtaining clinically meaningful feedback through low-burden mechanisms.</p></sec></sec><sec id="s3-4"><title>Theme 3: Users&#x2019; Mental Models</title><sec id="s3-4-1"><title>Overview</title><p>Participants&#x2019; accounts indicated that transparent communication in AI-CDSS is also influenced by users&#x2019; mental models of the system. In this study, this theme comprises the following subthemes: knowledge, experience, and attitudes. Within this theme, radiologists described the knowledge, experience, and attitudes shaping their interaction with AI-CDSS, whereas AI experts provided development-oriented observations about how these user characteristics may affect system interpretation and use.</p></sec><sec id="s3-4-2"><title>Knowledge</title><p>User knowledge emerged as a foundational factor for transparent and appropriate interaction with AI-CDSS. Participants from both groups framed the knowledge required for AI-CDSS use not as deep technical expertise in algorithms, but as a conceptual understanding of how the system generates output, what it is trained to detect, and where its limitations lie. Radiologists emphasized that effective AI use presupposes sufficient domain knowledge. AI-CDSS was repeatedly described as an assistive tool that relies on the clinician&#x2019;s ability to judge plausibility, recognize artifacts, and identify common pitfalls:</p><disp-quote><p>You don&#x2019;t need to understand deep algorithms, just where the answers come from. If doctors know that, they won&#x2019;t question every AI output unnecessarily.</p><attrib>R1, F, 24 years of experience</attrib></disp-quote><disp-quote><p>Doctors must know enough to check whether the AI is right or wrong. When it flags something, I try to understand why it appears.</p><attrib>R5, F, 14 years of experience</attrib></disp-quote><p>Radiologists described their clinical knowledge as helping them recognize likely false positives arising from normal anatomy or artifacts, such as calcifications, vessels, or external devices:</p><disp-quote><p>Because we&#x2019;ve been trained, we can already guess where false positives are likely to occur.</p><attrib>R10, M, 5 years of experience</attrib></disp-quote><p>Beyond clinical expertise, participants highlighted the importance of understanding the AI system itself, particularly its scope, training focus, and performance variability across findings. Radiologists did not expect to understand model internals but wanted clarity on what the system was trained to detect, where it performed reliably, and where errors were likely:</p><disp-quote><p>If you know the sensitivity and specificity, you can decide how much to trust it in different situations.</p><attrib>R9, F, 8 years of experience</attrib></disp-quote><p>Participants associated such knowledge with decisions about when to rely on or further verify AI outputs:</p><disp-quote><p>Knowing the strengths and limitations helps doctors plan their work, where to double-check more and where they can rely on it.&#x201D;</p><attrib>A2, M, 6 years of experience</attrib></disp-quote><p>Participants also stressed the need to correctly interpret system outputs, particularly confidence scores and visual explanations. AI experts cautioned against misinterpreting these parameters:</p><disp-quote><p>Doctors need to understand what confidence percentage really means. A confidence score doesn&#x2019;t guarantee the heatmap location is correct.</p><attrib>A10, M, 5 years of experience</attrib></disp-quote><p>Training was considered necessary, with both groups recommending structured training covering system use, interpretation, and limitations:</p><disp-quote><p>Every time new software is installed, there must be training, both an overview and how to use it in practice.</p><attrib>A5, M, 14 years of experience</attrib></disp-quote><p>AI experts emphasized that explaining validation logic, data characteristics, and experimental design without excessive technical detail helps users form realistic expectations:</p><disp-quote><p>We don&#x2019;t explain deep techniques, but we explain how the experiments were designed and how the model was validated.</p><attrib>A2, M, 6 years of experience</attrib></disp-quote><p>Participants further noted that clinicians involved early in system development naturally developed stronger users&#x2019; mental models of the AI, while other users required clear manuals explaining displayed metrics and high-risk findings:</p><disp-quote><p>If doctors weren&#x2019;t involved in development, they need a user manual explaining what each value means and which findings require caution.</p><attrib>A4, F, 8 years of experience</attrib></disp-quote><p>Overall, participants regarded clinical and system-specific knowledge as a basis for trust calibration. Training, expectation-setting, and clear documentation were considered necessary to help clinicians interpret AI outputs appropriately and understand the system&#x2019;s scope and limitations.</p></sec><sec id="s3-4-3"><title>Experience</title><p>Clinical experience and hands-on exposure to AI-CDSS shaped how radiologists incorporated AI outputs into their reading practice. Participants from both groups described a gradient in use patterns: less-experienced readers tended to rely on AI more readily, whereas highly experienced radiologists perceived fewer incremental benefits and primarily used AI for confirmation rather than guidance.</p><p>Experience with the AI tool itself was described as cumulative. With continued use, radiologists learned the system&#x2019;s typical error patterns and adjusted their verification strategies, accordingly, scrutinizing findings known to be error-prone while moving more efficiently through scenarios where the AI performed reliably:</p><disp-quote><p>As we use it more, we learn where it often gets things wrong; those areas or findings we recheck more carefully, and we may look for additional details.&#x201D;</p><attrib>R8, F, 7 years of experience</attrib></disp-quote><p>Radiologists described developing practical routines for when to consult AI and how much weight to assign to its outputs. Readiness to adopt AI was reported across experience levels, although reliance patterns differed. Many radiologists indicated that repeated exposure to real cases helped them calibrate their expectations and integrate AI into routine workflows:</p><disp-quote><p>If you keep using it, you learn and adapt with the AI; over time, you become more accepting and can balance how you use it.</p><attrib>R6, F, 14 years of experience</attrib></disp-quote><p>AI experts also noted that radiologists&#x2019; routine engagement with digital tools could facilitate AI integration:</p><disp-quote><p>Radiologists are already used to using new tools, so adoption is generally easier compared with some other fields.</p><attrib>A2, M, 6 years of experience</attrib></disp-quote><p>Overall, clinical and system-specific experience shaped when, how, and to what extent radiologists relied on AI-CDSS in diagnostic decision-making.</p></sec><sec id="s3-4-4"><title>Attitudes</title><p>Participants from both groups described attitudes toward AI-CDSS as ranging from active resistance to pragmatic acceptance. Across interviews, attitudes were shaped by (1) beliefs about human-AI capability, (2) willingness to engage with new technology, and (3) perceived consequences of agreeing with or challenging AI outputs:</p><disp-quote><p>Some clinicians hold an ego mindset that AI can never be better than them, so they avoid using it or ignore the AI&#x2019;s outputs.</p><attrib>R1, F, 24 years of experience</attrib></disp-quote><p>Another radiologist noted:</p><disp-quote><p>My own confidence in reading films affects how much I trust and believe in the AI.</p><attrib>R11, F, 13 years of experience</attrib></disp-quote><p>Radiologists regarded openness as important for adoption and for learning how to work with the system over time. They described this openness as an adaptive stance involving acceptance of AI as part of current practice rather than treating it as optional:</p><disp-quote><p>You must be open to using it; if you resist, you&#x2019;ll fall behind. We need to move with it and use it to stay ahead.</p><attrib>R10, M, 5 years of experience</attrib></disp-quote><p>At the same time, AI experts also noted attitudinal extremes in trust calibration. Some clinicians were described as trusting immediately, while others continued to distrust it:</p><disp-quote><p>If they trust, they trust completely; if they distrust, they distrust completely.&#x201D;</p><attrib>A9, M, 6 years of experience</attrib></disp-quote><p>Several radiologists also noted that different responses to AI could arise for nontechnical reasons such as reluctance to contradict the system, while others were perceived as seeing little need for AI because of strong confidence in their own judgment:</p><disp-quote><p>Some doctors believe in AI because they&#x2019;re afraid to argue with it if AI says it&#x2019;s right, they accept it even when it&#x2019;s wrong. But doctors who strongly trust themselves, especially seniors, may see no need for it.</p><attrib>R6, F, 14 years of experience</attrib></disp-quote><p>AI experts emphasized that negative attitudes were often driven less by the idea of AI itself than by perceived burden or workflow disruption; clinicians were reported to reject systems that add steps or friction, regardless of model performance:</p><disp-quote><p>Most of the time, it&#x2019;s not over-trust people don&#x2019;t accept it because they see it as a burden and extra steps. If it adds steps, doctors won&#x2019;t use it.</p><attrib>A8, M, 13 years of experience</attrib></disp-quote><p>Overall, attitudes toward AI-CDSS varied from openness to resistance and influenced how clinicians engaged with, interpreted, and acted on AI outputs.</p></sec></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Transparency for Trust Calibration</title><p>Across the themes, our findings suggest that in AI-CDSS for chest X-ray, transparency is interpreted functionally, not as full access to model internals, but as the system&#x2019;s ability to communicate why it flagged a finding, how certain it is, and where it is likely to fail in a way clinicians can meaningfully use. Its contribution to trust therefore depends not only on the information presented through the interface but also on clinicians&#x2019; knowledge, experience, and attitudes when evaluating that information. This interpretation is consistent with a recent systematic review that identified system transparency, interpretability, clinical reliability, and alignment with clinical judgment as factors shaping health care professionals&#x2019; trust in AI-CDSS [<xref ref-type="bibr" rid="ref29">29</xref>]. In this context, when outputs are delivered as unexplained &#x201C;answers,&#x201D; users are pushed into accept/reject behavior without defensible justification, which can erode confidence over time and inhibit sustained adoption [<xref ref-type="bibr" rid="ref30">30</xref>]. Our findings extend prior work by showing that trust develops dynamically through repeated comparisons between AI outputs and clinicians&#x2019; own interpretations, rather than from accuracy or transparency alone. In chest X-ray reading, radiologists described forming an independent judgment, consulting AI as a second opinion, and revisiting discordant findings, illustrating how transparency is integrated into clinical reasoning.</p><p>A key implication is that transparency should be designed to support trust calibration, not to maximize trust. In safety-critical domains, both extremes are harmful: undertrust produces disuse of potentially valuable support, while overtrust increases susceptibility to automation bias and uncritical acceptance. Recent commentary in clinical AI highlights automation bias as a realistic risk when users defer to AI recommendations despite uncertainty or imperfect reliability, especially under time pressure [<xref ref-type="bibr" rid="ref31">31</xref>].</p><p>Accordingly, transparency mechanisms should be explicitly &#x201C;calibration-facing&#x201D;: they should (1) communicate uncertainty, (2) disclose known limitations and boundary conditions, and (3) provide performance expectations that are understandable and clinically relevant. These cues should support clinicians&#x2019; judgments about when to rely on, verify, or override AI outputs, rather than serve merely as signals of credibility. To address undertrust specifically, clear information about performance in relevant clinical tasks, together with training using representative cases, may help clinicians calibrate their trust to the system&#x2019;s demonstrated reliability and recognize situations in which AI is likely to provide valuable support. When an AI output conflicts with an initial interpretation, the user interface could provide a neutral prompt to reexamine the relevant region rather than a persuasive recommendation. This approach may discourage premature rejection without encouraging automatic acceptance. Clinician-facing transparency may also have implications for patient communication. Understanding the basis and limitations of AI outputs may help clinicians explain how AI contributed to a diagnosis and discuss uncertainty during shared decision-making. Such communication may influence patient trust and acceptance of AI-supported diagnoses, although these patient-facing implications were not examined in this study.</p></sec><sec id="s4-2"><title>Aligning Transparency With Clinical Decision-Making</title><p>Supporting trust calibration requires more than making system information available: clinicians must be able to interpret and use it within their workflow. Considered together, the user interface and users&#x2019; mental model findings suggest that transparency depends on aligning what the system communicates with users&#x2019; understanding and clinical tasks. A review of AI in radiology similarly emphasizes that integration success depends not only on performance but also on workflow fit and adoption factors; the &#x201C;right&#x201D; information must arrive in a form that clinicians will actually use at scale [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. The radiology user interface literature has reported mixed findings regarding preferred interfaces: some users favor detailed displays combining heatmaps, text, and confidence information, whereas others prefer simple and uncomplicated designs [<xref ref-type="bibr" rid="ref34">34</xref>]. The current study helps explain this apparent inconsistency. Participants did not necessarily prefer either more or less information in absolute terms; rather, they wanted information to be task-dependent, clinically relevant, and accessible without creating screen clutter or disrupting independent image interpretation. Within these shared requirements, radiologists emphasized actionable, context-sensitive cues, whereas AI experts additionally emphasized system-level information about training data, provenance, and limitations. These competing requirements may be partly reconciled through progressive disclosure, whereby essential information is presented initially, and further details are made available on demand [<xref ref-type="bibr" rid="ref33">33</xref>,<xref ref-type="bibr" rid="ref35">35</xref>]. In practice, localized findings and concise confidence or uncertainty information could appear on the primary display, while technical details about training data, validation, performance, and limitations could be accessed through secondary views. For critical abnormalities such as pneumothorax, the suspected finding, location, urgency, and uncertainty should be immediately visible to support timely verification and prioritization, whereas routine screening may benefit from a concise initial display with additional information available on demand to minimize workflow burden. Moreover, UI design requires more than simply displaying additional information; it must ensure that users can correctly interpret what each element represents. For example, in usability testing of a chest X-ray AI tool, radiologists were uncertain about how to interpret confidence values and requested guidance on which confidence levels should be considered clinically meaningful [<xref ref-type="bibr" rid="ref36">36</xref>]. Additionally, AI assistance increased total reporting time by 14 (33%) seconds, although this difference did not reach statistical significance, with the additional decision-making time largely attributed to reviewing heatmaps [<xref ref-type="bibr" rid="ref36">36</xref>]. These findings highlight a potential trade-off: additional explanations may support interpretability but can also increase cognitive and workflow demands without necessarily improving diagnostic performance. User interface elements should therefore be evaluated according to whether their benefits for understanding and clinical decision-making justify the additional time required. Beyond these usability considerations, the explanation and uncertainty methods themselves have important technical limitations. Current visual explanation methods, including saliency- and attribution-based heatmaps, may produce plausible-looking outputs without reliably explaining the basis or correctness of an individual prediction [<xref ref-type="bibr" rid="ref37">37</xref>]. In evaluations using chest radiographs, saliency-map methods have also demonstrated limitations in localization utility, sensitivity to model randomization, repeatability, and reproducibility [<xref ref-type="bibr" rid="ref38">38</xref>]. Similarly, predictive uncertainty estimates may become less reliable when deployment data differ from the training distribution [<xref ref-type="bibr" rid="ref39">39</xref>]. Heatmaps and uncertainty estimates should therefore be presented as decision-support cues rather than definitive evidence of diagnostic correctness, together with clear information about their intended meaning, validation, and limitations.</p><p>Additionally, the user interface should include guardrails that reduce automation bias. Visual cues can improve efficiency, but they can also become persuasive anchors if not paired with uncertainty and boundary messaging. The automation-bias literature in clinical decision support underscores that systems should avoid presenting outputs in ways that encourage default deference; instead, they should support deliberate verification, especially for borderline or high-impact decisions [<xref ref-type="bibr" rid="ref31">31</xref>]. Consistent with this concern, our findings suggest communicating uncertainty and limitations and presenting the original radiograph before introducing the AI output. For borderline outputs, additional guardrails could include explicit labels such as &#x201C;uncertain&#x201D; or &#x201C;verification required,&#x201D; avoidance of definitive recommendations, and concise prompts for independent verification. Under time pressure, such guardrails should be visually salient and limited to ambiguous or clinically consequential findings to facilitate verification without producing excessive alerts or workflow burden.</p><p>Finally, feedback extends this relationship beyond the interpretation of individual outputs by connecting clinicians&#x2019; recognition of errors with opportunities for system improvement. The findings suggest that allowing users to flag errors may also support agency and continued critical engagement with AI. This aligns with implementation recommendations that emphasize feedback loops as part of integrating AI into real-world clinical workflows, rather than treating deployment as a one-time event [<xref ref-type="bibr" rid="ref32">32</xref>]. However, the presence of a feedback function alone is insufficient; it must be intuitive and integrated into the existing workflow while minimizing cognitive and interaction burden. Our findings revealed different priorities: radiologists emphasized immediate, workflow-integrated feedback, whereas AI experts valued detailed input but cautioned against workflow disruption. These priorities could be reconciled by embedding one-click confirmation or rejection directly into the image-reading interface while making error localization and brief comments optional. This approach would enable rapid routine feedback and more detailed input when needed without requiring a separate reporting process.</p></sec><sec id="s4-3"><title>Users&#x2019; Mental Models and the Interpretation of Transparency</title><p>The relationship between interface design and trust calibration depends partly on users&#x2019; mental models. This research suggests that the same transparency feature may be interpreted differently depending on clinicians&#x2019; knowledge, experience, and attitudes. This helps explain why &#x201C;more explanation&#x201D; is not automatically better: transparency is only effective when users can correctly interpret it and integrate it into clinical reasoning.</p><p>Previous evidence regarding the need for user training has been mixed. A recent scoping review reported that one included study characterized a chest X-ray AI system as easy to understand without requiring specialized training, although the evaluation used no formal scoring system and reported only limited qualitative findings [<xref ref-type="bibr" rid="ref34">34</xref>]. By contrast, usability testing of another chest X-ray AI tool found that radiologists were uncertain about how to interpret confidence values and considered some form of training necessary before deployment [<xref ref-type="bibr" rid="ref36">36</xref>]. More broadly, a systematic review identified training and familiarity as factors shaping trust and noted that opaque AI outputs may cause confusion and, in some cases, contribute to overreliance, particularly among less experienced clinicians [<xref ref-type="bibr" rid="ref29">29</xref>]. Based on our findings, the 2 groups emphasized complementary pathways for developing users&#x2019; mental models. AI experts focused on structured information about system scope, validation, performance, and limitations, whereas radiologists described refining their understanding through repeated use and recognition of recurring errors. Together, these findings suggest that initial conceptual training should be complemented by continued learning through clinical use. This interpretation is consistent with previous work emphasizing that explainability and trust depend on users understanding the system&#x2019;s intended purpose, outputs, and limitations [<xref ref-type="bibr" rid="ref40">40</xref>]. Therefore, training is not &#x201C;extras&#x201D;; it is part of the transparency system. Well-designed training strengthens mental models so that clinicians use transparency cues for calibration (verify/override appropriately) rather than as reassurance signals that accelerate overreliance.</p><p>Attitudes, in particular, may shape the relationship between transparency and trust. Previous research has similarly recognized attitudes, perceptions, and positive expectations as factors shaping health care professionals&#x2019; trust in AI-CDSS [<xref ref-type="bibr" rid="ref29">29</xref>]. Our findings add further context by suggesting that openness or resistance shapes whether transparency cues are attended to, dismissed, or treated as confirmation. This suggests a design requirement for plural-user transparency: systems should simultaneously (1) provide enough credibility and evidence to engage skeptics and (2) provide enough uncertainty and boundary messaging to constrain enthusiastic users from overtrust.</p></sec><sec id="s4-4"><title>Design Implications for Transparent and Trustworthy AI-CDSS</title><p>To synthesize these findings and highlight their practical implications, <xref ref-type="table" rid="table4">Table 4</xref> summarizes key design considerations for transparent and trustworthy AI-CDSS derived from expert perspectives and provides illustrative clinical scenarios showing how these considerations could be applied in practice. <xref ref-type="fig" rid="figure2">Figure 2</xref> presents a conceptual user interface mockup illustrating one possible implementation of the findings from Theme 2, while <xref ref-type="table" rid="table5">Table 5</xref> presents a proposed training curriculum based on the interview findings.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Design implications for transparent and trustworthy AI-CDSS<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup>.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Theme and key insight from expert perspectives</td><td align="left" valign="bottom">Design implication for AI-CDSS</td><td align="left" valign="bottom">Illustrative clinical scenario</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="3">Theme 1: transparency and trust</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Clinicians tend to distrust &#x201C;black box&#x201D; systems even when performance is high.</td><td align="left" valign="top">User interface should prioritize functional transparency that supports clinical reasoning, rather than full algorithmic interpretability.</td><td align="left" valign="top">A suspected abnormality is presented with its location, confidence level, and a brief rationale.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Trust is shaped by understanding AI reasoning and limitations, not accuracy alone.</td><td align="left" valign="top">AI-CDSS should explicitly communicate uncertainty, confidence levels, and limitations rather than presenting binary or opaque outputs.</td><td align="left" valign="top">A low-confidence finding is accompanied by a verification cue and relevant model limitations.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Appropriate trust lies between overtrust and undertrust.</td><td align="left" valign="top">AI-CDSS should be designed to support trust calibration, not to maximize trust.</td><td align="left" valign="top">The clinician reviews the original radiograph before revealing the AI findings for comparison.</td></tr><tr><td align="left" valign="top" colspan="3">Theme 2: user interface</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Visual explanations (eg, heatmaps) can support interpretation but may induce automation bias.</td><td align="left" valign="top">Visual cues should be accompanied by uncertainty indicators (eg, confidence scores, caution flags) to prevent over-reliance</td><td align="left" valign="top">Each heatmap is accompanied by a finding-specific confidence score and an uncertainty cue.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Excessive information increases cognitive load and disrupts workflow.</td><td align="left" valign="top">User interface should follow a minimalist, workflow-aligned design that presents only clinically relevant information</td><td align="left" valign="top">Selecting a finding automatically displays its relevant information in a structured panel.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Misalignment with clinical workflow reduces acceptance regardless of model quality.</td><td align="left" valign="top">AI-CDSS should be seamlessly integrated into existing radiology workflows without adding unnecessary steps</td><td align="left" valign="top">AI findings are accessed within the existing image-review workflow without opening a separate application.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Expert feedback is valuable for model refinement.</td><td align="left" valign="top">AI-CDSS should enable experienced clinicians to provide feedback without increasing their workload.</td><td align="left" valign="top">Clinicians provide feedback by selecting &#x201C;Agree,&#x201D; &#x201C;Uncertain,&#x201D; or &#x201C;Disagree,&#x201D; with an optional comment.</td></tr><tr><td align="left" valign="top" colspan="3">Theme 3: users&#x2019; mental model</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Users require a conceptual, not technical, understanding of AI.</td><td align="left" valign="top">AI-CDSS should provide onboarding and contextual explanations about the model, training data, and performance boundaries</td><td align="left" valign="top">Brief onboarding explains the AI-CDSS&#x2019;s intended use, outputs, training data, and limitations.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Misinterpretation of confidence scores or explanations can lead to misuse.</td><td align="left" valign="top">Explanatory elements should be designed to align with clinicians&#x2019; existing diagnostic reasoning practices</td><td align="left" valign="top">Confidence is described as a model estimate rather than diagnostic certainty.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Trust becomes calibrated through repeated real-case use.</td><td align="left" valign="top">AI-CDSS should support gradual learning and adaptation rather than enforcing rigid reliance</td><td align="left" valign="top">Repeated use helps clinicians recognize the AI-CDSS&#x2019;s strengths and limitations across cases.</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Attitudes toward AI range from resistance to over-deference.</td><td align="left" valign="top">System communication and framing should consistently position AI as a supportive tool rather than a replacement for clinical judgment</td><td align="left" valign="top">AI outputs are presented for clinician review, with the final decision remaining with the clinician.</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>AI-CDSS: AI&#x2013;based Clinical Decision Support System.</p></fn></table-wrap-foot></table-wrap><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Conceptual user interface mockup for transparent communication in a chest X-ray AI-CDSS. CC: Clinical context; CDSS: Clinical decision support system; CXR: chest X-ray; TX: Treatment; UD: Underlying disease.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e99472_fig02.png"/></fig><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Proposed training modules for supporting the users&#x2019; mental models of AI-CDSS.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Module</td><td align="left" valign="bottom">Training content</td></tr></thead><tbody><tr><td align="left" valign="top">Introduction to AI and AI-CDSS<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup></td><td align="left" valign="top">Conceptual overview of how AI-CDSS generates outputs and its intended purpose and scope</td></tr><tr><td align="left" valign="top">System capabilities, limitations, and trust calibration</td><td align="left" valign="top">Target findings, areas of reliable and unreliable performance, common false-positive patterns, sensitivity and specificity, limitations, and the risks of undertrust and overtrust</td></tr><tr><td align="left" valign="top">Training data and model validation</td><td align="left" valign="top">Conceptual explanation of training data characteristics, training focus, experimental design, and model validation without unnecessary technical detail</td></tr><tr><td align="left" valign="top">Interpretation and practical use of AI outputs</td><td align="left" valign="top">Meaning and appropriate use of AI findings, confidence and uncertainty information, heatmaps, displayed performance metrics, findings requiring caution, and situations in which users should rely on or further verify AI outputs</td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>AI-CDSS: AI-based Clinical Decision Support Systems. </p></fn></table-wrap-foot></table-wrap></sec><sec id="s4-5"><title>Limitation and Future Work</title><p>First, this study focused on chest X-ray diagnosis; therefore, transparency and trust requirements may differ across other diagnostic contexts with varying information needs, risk levels, or interpretive workflows. Second, this study was conducted primarily in Thailand; thus, participants&#x2019; perspectives may reflect local disease patterns, including those associated with tropical settings, as well as clinical workflows, resource availability, and experience with AI-CDSS. Although context-specific preferences may not be directly transferable to all health care systems, the broader principles of understandable AI communication, uncertainty disclosure, workflow-aligned design, and support for users&#x2019; mental models may have wider relevance. Multicountry studies across diverse clinical and health care contexts are needed to assess the international applicability of these findings. Third, the purposive sample of experienced radiologists and AI experts may not capture the perspectives of novice users or clinicians without prior AI-CDSS experience. Participants&#x2019; existing experience with AI-CDSS may also have been associated with greater technology affinity, potentially underrepresenting barriers faced by less willing adopters. Fourth, the interview guide underwent researcher review, expert review, and assessment using the IOC; however, it was not formally pilot tested or cognitively pretested with representatives of the target groups. Consequently, potential differences in how participants interpreted the questions may not have been identified before data collection. Fifth, interviews shared a chest X-ray AI-CDSS context; however, the absence of a standardized scenario or visual stimulus may have led participants to refer to systems with different functionalities and user interfaces, potentially affecting their mental representations and the comparability of some responses. Future studies could use a shared prototype or standardized scenarios to provide a more consistent basis for eliciting perspectives. Finally, interviews were conducted in Thai, and quotations were reported in English. The Thai and English versions were checked against each other in collaboration with another researcher (AJW) to preserve meaning. Nevertheless, some linguistic nuances and culturally specific meanings may not have been fully conveyed in translation. Future research could adopt a mixed methods design by developing a survey instrument based on the themes identified in this study. Administering the instrument to a larger and more diverse sample of radiologists and AI experts could complement the qualitative findings, quantify the distribution of the identified attitudes and perspectives, and examine their associations with professional role, clinical experience, and prior experience with AI-CDSS.</p></sec><sec id="s4-6"><title>Conclusions</title><p>This qualitative study demonstrates that trust in AI-CDSS is fundamentally shaped by transparency as experienced through human-AI interaction, rather than by algorithmic accuracy alone. Radiologists and AI developers converged on the view that transparent communication through interpretable explanations, visible uncertainty, and clearly defined system boundaries enables clinicians to integrate AI outputs into clinical reasoning while retaining professional autonomy. Our findings further show that trust is dynamic and calibrated, developing through repeated use, feedback, and alignment between system behavior and clinicians&#x2019; mental models. Importantly, transparency must be enacted not only through interface design, but also through consideration of users&#x2019; experience, knowledge, and attitudes toward AI. Together, these results underscore that designing trustworthy AI-CDSS requires a human-centered approach, in which transparency supports appropriate reliance rather than blind acceptance or rejection. By aligning technical design with clinical workflows and users&#x2019; mental models, AI-CDSS can function as a reliable collaborative partner in real-world diagnostic practice.</p></sec></sec></body><back><notes><sec><title>Generative AI Use</title><p>During the preparation of this work, the authors used GPT-5.6 Sol (OpenAI) to assist with proofreading, language editing, and the revision of selected manuscript passages to improve clarity and readability. All AI-assisted content was reviewed and edited by the authors, who take full responsibility for the final content of the manuscript.</p></sec><sec><title>Funding</title><p>This project is supported by 111<sup>th</sup> Anniversary Engineering Research Catalyst Fund Towards U Top 100, Faculty of Engineering, Chulalongkorn University.</p></sec><sec><title>Data Availability</title><p>The full interview transcripts are not available for sharing due to confidentiality restrictions imposed by the Institutional Review Board.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: YS, AJ</p><p>Investigation: YS, AJ</p><p>Methodology: YS, AJ</p><p>Supervision: AJ</p><p>Writing &#x2013; original draft: YS</p><p>Writing &#x2013; review &#x0026; editing: AJ</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AI-CDSS</term><def><p>AI-based Clinical Decision Support Systems</p></def></def-item><def-item><term id="abb2">CTO</term><def><p>chief technology officer</p></def></def-item><def-item><term id="abb3">ECG</term><def><p>electrocardiogram</p></def></def-item><def-item><term id="abb4">HCI</term><def><p>human-computer interaction</p></def></def-item><def-item><term id="abb5">IOC</term><def><p>Index of Item-Objective Congruence</p></def></def-item><def-item><term id="abb6">RQ</term><def><p>research question</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yamashita</surname><given-names>R</given-names> </name><name name-style="western"><surname>Long</surname><given-names>J</given-names> </name><name name-style="western"><surname>Longacre</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Deep learning model for the prediction of microsatellite instability in colorectal cancer: a diagnostic study</article-title><source>Lancet Oncol</source><year>2021</year><month>01</month><volume>22</volume><issue>1</issue><fpage>132</fpage><lpage>141</lpage><pub-id pub-id-type="doi">10.1016/S1470-2045(20)30535-0</pub-id><pub-id pub-id-type="medline">33387492</pub-id></nlm-citation></ref><ref id="ref2"><label>2</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kim</surname><given-names>RY</given-names> </name><name name-style="western"><surname>Oke</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Pickup</surname><given-names>LC</given-names> </name><etal/></person-group><article-title>Artificial intelligence tool for assessment of indeterminate pulmonary nodules detected with CT</article-title><source>Radiology</source><year>2022</year><month>09</month><volume>304</volume><issue>3</issue><fpage>683</fpage><lpage>691</lpage><pub-id pub-id-type="doi">10.1148/radiol.212182</pub-id><pub-id pub-id-type="medline">35608444</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>He</surname><given-names>J</given-names> </name><name name-style="western"><surname>Baxter</surname><given-names>SL</given-names> </name><name name-style="western"><surname>Xu</surname><given-names>J</given-names> </name><name name-style="western"><surname>Xu</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zhou</surname><given-names>X</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>K</given-names> </name></person-group><article-title>The practical implementation of artificial intelligence technologies in medicine</article-title><source>Nat Med</source><year>2019</year><month>01</month><volume>25</volume><issue>1</issue><fpage>30</fpage><lpage>36</lpage><pub-id pub-id-type="doi">10.1038/s41591-018-0307-0</pub-id><pub-id pub-id-type="medline">30617336</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Topol</surname><given-names>EJ</given-names> </name></person-group><article-title>High-performance medicine: the convergence of human and artificial intelligence</article-title><source>Nat Med</source><year>2019</year><month>01</month><volume>25</volume><issue>1</issue><fpage>44</fpage><lpage>56</lpage><pub-id pub-id-type="doi">10.1038/s41591-018-0300-7</pub-id><pub-id pub-id-type="medline">30617339</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="confproc"><article-title>Rethinking human-AI collaboration in complex medical decision making: a case study in sepsis diagnosis</article-title><conf-name>Proceedings of the 2024 CHI Conference on Human Factors in Computing Systems</conf-name><conf-date>Apr 11-16, 2024</conf-date><pub-id pub-id-type="doi">10.1145/3613904.3642343</pub-id></nlm-citation></ref><ref id="ref6"><label>6</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Steerling</surname><given-names>E</given-names> </name><name name-style="western"><surname>Siira</surname><given-names>E</given-names> </name><name name-style="western"><surname>Nilsen</surname><given-names>P</given-names> </name><name name-style="western"><surname>Svedberg</surname><given-names>P</given-names> </name><name name-style="western"><surname>Nygren</surname><given-names>J</given-names> </name></person-group><article-title>Implementing AI in healthcare-the relevance of trust: a scoping review</article-title><source>Front Health Serv</source><year>2023</year><volume>3</volume><fpage>1211150</fpage><pub-id pub-id-type="doi">10.3389/frhs.2023.1211150</pub-id><pub-id pub-id-type="medline">37693234</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Curtin</surname><given-names>D</given-names> </name><name name-style="western"><surname>Meijer</surname><given-names>AJ</given-names> </name></person-group><article-title>Does transparency strengthen legitimacy?</article-title><source>IP</source><year>2006</year><volume>11</volume><issue>2</issue><fpage>109</fpage><lpage>122</lpage><pub-id pub-id-type="doi">10.3233/IP-2006-0091</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Barredo Arrieta</surname><given-names>A</given-names> </name><name name-style="western"><surname>D&#x00ED;az-Rodr&#x00ED;guez</surname><given-names>N</given-names> </name><name name-style="western"><surname>Del Ser</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Explainable artificial intelligence (XAI): concepts, taxonomies, opportunities and challenges toward responsible AI</article-title><source>Information Fusion</source><year>2020</year><month>06</month><volume>58</volume><fpage>82</fpage><lpage>115</lpage><pub-id pub-id-type="doi">10.1016/j.inffus.2019.12.012</pub-id></nlm-citation></ref><ref id="ref9"><label>9</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Gulati</surname><given-names>S</given-names> </name><name name-style="western"><surname>McDonagh</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sousa</surname><given-names>S</given-names> </name><name name-style="western"><surname>Lamas</surname><given-names>D</given-names> </name></person-group><article-title>Trust models and theories in human&#x2013;computer interaction: a systematic literature review</article-title><source>Computers in Human Behavior Reports</source><year>2024</year><month>12</month><volume>16</volume><fpage>100495</fpage><pub-id pub-id-type="doi">10.1016/j.chbr.2024.100495</pub-id></nlm-citation></ref><ref id="ref10"><label>10</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hoff</surname><given-names>KA</given-names> </name><name name-style="western"><surname>Bashir</surname><given-names>M</given-names> </name></person-group><article-title>Trust in automation: integrating empirical evidence on factors that influence trust</article-title><source>Hum Factors</source><year>2015</year><month>05</month><volume>57</volume><issue>3</issue><fpage>407</fpage><lpage>434</lpage><pub-id pub-id-type="doi">10.1177/0018720814547570</pub-id><pub-id pub-id-type="medline">25875432</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mcknight</surname><given-names>DH</given-names> </name><name name-style="western"><surname>Carter</surname><given-names>M</given-names> </name><name name-style="western"><surname>Thatcher</surname><given-names>JB</given-names> </name><name name-style="western"><surname>Clay</surname><given-names>PF</given-names> </name></person-group><article-title>Trust in a specific technology: an investigation of its components and measures</article-title><source>ACM Trans Manage Inf Syst</source><year>2011</year><volume>2</volume><issue>2</issue><fpage>1</fpage><lpage>25</lpage><pub-id pub-id-type="doi">10.1145/1985347.1985353</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Toreini</surname><given-names>E</given-names> </name><name name-style="western"><surname>Aitken</surname><given-names>M</given-names> </name><name name-style="western"><surname>Coopamootoo</surname><given-names>K</given-names> </name><name name-style="western"><surname>Elliott</surname><given-names>K</given-names> </name><name name-style="western"><surname>Zelaya</surname><given-names>CG</given-names> </name></person-group><article-title>The relationship between trust in AI and trustworthy machine learning technologies</article-title><conf-name>FAT* &#x2019;20: Proceedings of the 2020 Conference on Fairness, Accountability, and Transparency</conf-name><conf-date>Jan 27-30, 2020</conf-date><conf-loc>Barcelona, Spain</conf-loc><fpage>272</fpage><lpage>283</lpage><pub-id pub-id-type="doi">10.1145/3351095.3372834</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>JD</given-names> </name><name name-style="western"><surname>See</surname><given-names>KA</given-names> </name></person-group><article-title>Trust in automation: designing for appropriate reliance</article-title><source>Hum Factors</source><year>2004</year><volume>46</volume><issue>1</issue><fpage>50</fpage><lpage>80</lpage><pub-id pub-id-type="doi">10.1518/hfes.46.1.50_30392</pub-id><pub-id pub-id-type="medline">15151155</pub-id></nlm-citation></ref><ref id="ref14"><label>14</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Minh</surname><given-names>D</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>HX</given-names> </name><name name-style="western"><surname>Li</surname><given-names>YF</given-names> </name><name name-style="western"><surname>Nguyen</surname><given-names>TN</given-names> </name></person-group><article-title>Explainable artificial intelligence: a comprehensive review</article-title><source>Artif Intell Rev</source><year>2022</year><month>06</month><volume>55</volume><issue>5</issue><fpage>3503</fpage><lpage>3568</lpage><pub-id pub-id-type="doi">10.1007/s10462-021-10088-y</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kaplan</surname><given-names>S</given-names> </name><name name-style="western"><surname>Uusitalo</surname><given-names>H</given-names> </name><name name-style="western"><surname>Lensu</surname><given-names>L</given-names> </name></person-group><article-title>A unified and practical user-centric framework for explainable artificial intelligence</article-title><source>Knowl Based Syst</source><year>2024</year><month>01</month><volume>283</volume><fpage>111107</fpage><pub-id pub-id-type="doi">10.1016/j.knosys.2023.111107</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Shamszare</surname><given-names>H</given-names> </name><name name-style="western"><surname>Choudhury</surname><given-names>A</given-names> </name></person-group><article-title>Clinicians&#x2019; perceptions of artificial intelligence: focus on workload, risk, trust, clinical decision making, and clinical integration</article-title><source>Health Care (Don Mills)</source><year>2023</year><volume>11</volume><issue>16</issue><fpage>2308</fpage><pub-id pub-id-type="doi">10.3390/healthcare11162308</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tucci</surname><given-names>V</given-names> </name><name name-style="western"><surname>Saary</surname><given-names>J</given-names> </name><name name-style="western"><surname>Doyle</surname><given-names>TE</given-names> </name></person-group><article-title>Factors influencing trust in medical artificial intelligence for healthcare professionals: a narrative review</article-title><source>J Med Artif Intell</source><year>2021</year><volume>5</volume><fpage>4</fpage><lpage>4</lpage><pub-id pub-id-type="doi">10.21037/jmai-21-25</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Stevens</surname><given-names>AF</given-names> </name><name name-style="western"><surname>Stetson</surname><given-names>P</given-names> </name></person-group><article-title>Theory of trust and acceptance of artificial intelligence technology (TrAAIT): an instrument to assess clinician trust and acceptance of artificial intelligence</article-title><source>J Biomed Inform</source><year>2023</year><month>12</month><volume>148</volume><fpage>104550</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2023.104550</pub-id><pub-id pub-id-type="medline">37981107</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Norman</surname><given-names>D</given-names> </name></person-group><article-title>Cognitive engineering</article-title><source>User Centered System Design: New Perspectives on Human-Computer Interaction</source><year>1986</year><publisher-name>Lawrence Erlbaum Associates</publisher-name><fpage>31</fpage><lpage>61</lpage><pub-id pub-id-type="doi">10.1201/9780367807320-3</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Carroll</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Olson</surname><given-names>JR</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Helander</surname><given-names>M</given-names> </name></person-group><article-title>Mental models in human-computer interaction</article-title><source>Handbook of Human-Computer Interaction</source><year>1988</year><publisher-name>North-Holland</publisher-name><fpage>45</fpage><lpage>65</lpage><pub-id pub-id-type="doi">10.1016/B978-0-444-70536-5.50007-5</pub-id></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tenhundfeld</surname><given-names>NL</given-names> </name><name name-style="western"><surname>Barr</surname><given-names>HM</given-names> </name><name name-style="western"><surname>O&#x2019;Hear</surname><given-names>EH</given-names> </name><name name-style="western"><surname>Weger</surname><given-names>K</given-names> </name></person-group><article-title>Is my Siri the same as your Siri? An exploration of users&#x2019; mental model of virtual personal assistants, implications for trust</article-title><source>IEEE Trans Human-Mach Syst</source><year>2022</year><volume>52</volume><issue>3</issue><fpage>512</fpage><lpage>521</lpage><pub-id pub-id-type="doi">10.1109/THMS.2021.3107493</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Gentner</surname><given-names>D</given-names> </name></person-group><article-title>Mental models, psychology of</article-title><source>International Encyclopedia of the Social and Behavioral Sciences</source><year>2001</year><publisher-name>Elsevier Science</publisher-name><pub-id pub-id-type="doi">10.1016/B0-08-043076-7/01487-X</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Yang</surname><given-names>Q</given-names> </name><name name-style="western"><surname>Steinfeld</surname><given-names>A</given-names> </name><name name-style="western"><surname>Ros&#x00E9;</surname><given-names>C</given-names> </name><name name-style="western"><surname>Zimmerman</surname><given-names>J</given-names> </name></person-group><article-title>Re-examining whether, why, and how human-AI interaction is uniquely difficult to design</article-title><conf-name>CHI &#x2019;20: Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems</conf-name><conf-date>Apr 25-30, 2020</conf-date><conf-loc>Honolulu, HI, USA</conf-loc><fpage>1</fpage><lpage>13</lpage><pub-id pub-id-type="doi">10.1145/3313831.3376301</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bienefeld</surname><given-names>N</given-names> </name><name name-style="western"><surname>Boss</surname><given-names>JM</given-names> </name><name name-style="western"><surname>L&#x00FC;thy</surname><given-names>R</given-names> </name><etal/></person-group><article-title>Solving the explainable AI conundrum by bridging clinicians&#x2019; needs and developers&#x2019; goals</article-title><source>NPJ Digit Med</source><year>2023</year><month>05</month><day>22</day><volume>6</volume><issue>1</issue><fpage>94</fpage><pub-id pub-id-type="doi">10.1038/s41746-023-00837-4</pub-id><pub-id pub-id-type="medline">37217779</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hoffman</surname><given-names>RR</given-names> </name></person-group><article-title>The problem of extracting the knowledge of experts from the perspective of experimental psychology</article-title><source>AI Mag</source><year>1987</year><volume>8</volume><issue>2</issue><fpage>53</fpage><lpage>67</lpage><pub-id pub-id-type="doi">10.1609/aimag.v8i2.583</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hallowell</surname><given-names>MR</given-names> </name><name name-style="western"><surname>Gambatese</surname><given-names>JA</given-names> </name></person-group><article-title>Qualitative research: application of the Delphi method to CEM research</article-title><source>J Constr Eng Manage</source><year>2010</year><month>01</month><volume>136</volume><issue>1</issue><fpage>99</fpage><lpage>107</lpage><pub-id pub-id-type="doi">10.1061/(ASCE)CO.1943-7862.0000137</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Tenny</surname><given-names>S</given-names> </name><name name-style="western"><surname>Brannan</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Brannan</surname><given-names>GD</given-names> </name></person-group><source>Qualitative Study</source><year>2022</year><access-date>2026-11-02</access-date><publisher-name>StatPearls Publishing</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.ncbi.nlm.nih.gov/books/NBK470395/">https://www.ncbi.nlm.nih.gov/books/NBK470395/</ext-link></comment><pub-id pub-id-type="medline">29262162</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Braun</surname><given-names>V</given-names> </name><name name-style="western"><surname>Clarke</surname><given-names>V</given-names> </name></person-group><article-title>Using thematic analysis in psychology</article-title><source>Qual Res Psychol</source><year>2006</year><month>01</month><volume>3</volume><issue>2</issue><fpage>77</fpage><lpage>101</lpage><pub-id pub-id-type="doi">10.1191/1478088706qp063oa</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Tun</surname><given-names>HM</given-names> </name><name name-style="western"><surname>Rahman</surname><given-names>HA</given-names> </name><name name-style="western"><surname>Naing</surname><given-names>L</given-names> </name><name name-style="western"><surname>Malik</surname><given-names>OA</given-names> </name></person-group><article-title>Trust in artificial intelligence-based clinical decision support systems among health care workers: systematic review</article-title><source>J Med Internet Res</source><year>2025</year><month>07</month><day>29</day><volume>27</volume><fpage>e69678</fpage><pub-id pub-id-type="doi">10.2196/69678</pub-id><pub-id pub-id-type="medline">40772775</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Chapiro</surname><given-names>J</given-names> </name></person-group><article-title>Explainable AI for prostate MRI: don&#x2019;t trust, verify</article-title><source>Radiology</source><year>2023</year><month>05</month><volume>307</volume><issue>4</issue><fpage>e230574</fpage><pub-id pub-id-type="doi">10.1148/radiol.230574</pub-id><pub-id pub-id-type="medline">37039689</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Khera</surname><given-names>R</given-names> </name><name name-style="western"><surname>Simon</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Ross</surname><given-names>JS</given-names> </name></person-group><article-title>Automation bias and assistive AI: risk of harm from AI-driven clinical decision support</article-title><source>JAMA</source><year>2023</year><month>12</month><day>19</day><volume>330</volume><issue>23</issue><fpage>2255</fpage><lpage>2257</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.22557</pub-id><pub-id pub-id-type="medline">38112824</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Najjar</surname><given-names>R</given-names> </name></person-group><article-title>Redefining radiology: a review of artificial intelligence integration in medical imaging</article-title><source>Diagnostics (Basel)</source><year>2023</year><month>08</month><day>25</day><volume>13</volume><issue>17</issue><fpage>2760</fpage><pub-id pub-id-type="doi">10.3390/diagnostics13172760</pub-id><pub-id pub-id-type="medline">37685300</pub-id></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Patel</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Baxter</surname><given-names>W</given-names> </name><name name-style="western"><surname>Porat</surname><given-names>T</given-names> </name></person-group><article-title>Toward guidelines for designing holistic integrated information visualizations for time-critical contexts: systematic review</article-title><source>J Med Internet Res</source><year>2024</year><month>11</month><day>20</day><volume>26</volume><fpage>e58088</fpage><pub-id pub-id-type="doi">10.2196/58088</pub-id><pub-id pub-id-type="medline">39566050</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Gill</surname><given-names>A</given-names> </name><name name-style="western"><surname>Rainey</surname><given-names>C</given-names> </name><name name-style="western"><surname>McLaughlin</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Artificial intelligence user interface preferences in radiology: a scoping review</article-title><source>J Med Imaging Radiat Sci</source><year>2025</year><month>05</month><volume>56</volume><issue>3</issue><fpage>101866</fpage><pub-id pub-id-type="doi">10.1016/j.jmir.2025.101866</pub-id><pub-id pub-id-type="medline">40020339</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Muralidhar</surname><given-names>D</given-names> </name><name name-style="western"><surname>Belloum</surname><given-names>R</given-names> </name><name name-style="western"><surname>Ashok</surname><given-names>A</given-names> </name></person-group><article-title>Operationalizing selective transparency using progressive disclosure in artificial intelligence clinical diagnosis systems</article-title><source>Int J Hum Comput Stud</source><year>2025</year><month>10</month><volume>204</volume><issue>C</issue><fpage>103591</fpage><pub-id pub-id-type="doi">10.1016/j.ijhcs.2025.103591</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lam Shin Cheung</surname><given-names>J</given-names> </name><name name-style="western"><surname>Ali</surname><given-names>A</given-names> </name><name name-style="western"><surname>Abdalla</surname><given-names>M</given-names> </name><name name-style="western"><surname>Fine</surname><given-names>B</given-names> </name></person-group><article-title>U"AI" testing: user interface and usability testing of a chest X-ray AI tool in a simulated real-world workflow</article-title><source>Can Assoc Radiol J</source><year>2023</year><month>05</month><volume>74</volume><issue>2</issue><fpage>314</fpage><lpage>325</lpage><pub-id pub-id-type="doi">10.1177/08465371221131200</pub-id><pub-id pub-id-type="medline">36189838</pub-id></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ghassemi</surname><given-names>M</given-names> </name><name name-style="western"><surname>Oakden-Rayner</surname><given-names>L</given-names> </name><name name-style="western"><surname>Beam</surname><given-names>AL</given-names> </name></person-group><article-title>The false hope of current approaches to explainable artificial intelligence in health care</article-title><source>Lancet Digit Health</source><year>2021</year><month>11</month><volume>3</volume><issue>11</issue><fpage>e745</fpage><lpage>e750</lpage><pub-id pub-id-type="doi">10.1016/S2589-7500(21)00208-9</pub-id><pub-id pub-id-type="medline">34711379</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Arun</surname><given-names>N</given-names> </name><name name-style="western"><surname>Gaw</surname><given-names>N</given-names> </name><name name-style="western"><surname>Singh</surname><given-names>P</given-names> </name><etal/></person-group><article-title>Assessing the trustworthiness of saliency maps for localizing abnormalities in medical imaging</article-title><source>Radiol Artif Intell</source><year>2021</year><month>11</month><volume>3</volume><issue>6</issue><fpage>e200267</fpage><pub-id pub-id-type="doi">10.1148/ryai.2021200267</pub-id><pub-id pub-id-type="medline">34870212</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="other"><person-group person-group-type="author"><name name-style="western"><surname>Ovadia</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Fertig</surname><given-names>E</given-names> </name><name name-style="western"><surname>Ren</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Can you trust your model&#x2019;s uncertainty? Evaluating predictive uncertainty under dataset shift</article-title><source>arXiv</source><comment>Preprint posted online on  Jun 6, 2019</comment><pub-id pub-id-type="doi">10.48550/arXiv.1906.02530</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Rezaeian</surname><given-names>O</given-names> </name><name name-style="western"><surname>Asan</surname><given-names>O</given-names> </name><name name-style="western"><surname>Bayrak</surname><given-names>AE</given-names> </name></person-group><article-title>The impact of AI explanations on clinicians&#x2019; trust and diagnostic accuracy in breast cancer</article-title><source>Appl Ergon</source><year>2025</year><month>11</month><volume>129</volume><fpage>104577</fpage><pub-id pub-id-type="doi">10.1016/j.apergo.2025.104577</pub-id><pub-id pub-id-type="medline">40577970</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Interview questions.</p><media xlink:href="medinform_v14i1e99472_app1.pdf" xlink:title="PDF File, 84 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Interview guide.</p><media xlink:href="medinform_v14i1e99472_app2.pdf" xlink:title="PDF File, 532 KB"/></supplementary-material></app-group></back></article>