<?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="letter"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Form Res</journal-id><journal-id journal-id-type="publisher-id">formative</journal-id><journal-id journal-id-type="index">27</journal-id><journal-title>JMIR Formative Research</journal-title><abbrev-journal-title>JMIR Form Res</abbrev-journal-title><issn pub-type="epub">2561-326X</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">v9i1e74038</article-id><article-id pub-id-type="doi">10.2196/74038</article-id><article-categories><subj-group subj-group-type="heading"><subject>Research Letter</subject></subj-group></article-categories><title-group><article-title>Use First, Trust Later? Exploring How Health Care Providers View the Gaps Between AI&#x2019;s Regulation and Its Implementation</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Raz</surname><given-names>Aviad</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Inbar</surname><given-names>Yael</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Paz</surname><given-names>Ziv</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Hofman</surname><given-names>Barkan</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Itzhakov</surname><given-names>Zalman</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Weinstein</surname><given-names>Orly</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Sociology and Anthropology, Ben-Gurion University of the Negev</institution><addr-line>Be'er-Sheva</addr-line><addr-line>Be'er-Sheva</addr-line><country>Israel</country></aff><aff id="aff2"><institution>Technology Management and Information Systems, Tel Aviv University</institution><addr-line>Tel-Aviv</addr-line><country>Israel</country></aff><aff id="aff3"><institution>Clalit Health Services</institution><addr-line>Tel-Aviv</addr-line><country>Israel</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Mavragani</surname><given-names>Amaryllis</given-names></name></contrib><contrib contrib-type="editor"><name name-style="western"><surname>Sarvestan</surname><given-names>Javad</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Adekola</surname><given-names>Adeleke</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Onah</surname><given-names>Chibuzo</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Wagle</surname><given-names>Sridevi</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Aviad Raz, PhD, Department of Sociology and Anthropology, Ben-Gurion University of the Negev, Be'er-Sheva, Be'er-Sheva, 8496500, Israel, 972 86472058; <email>aviadraz@bgu.ac.il</email></corresp></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>10</day><month>11</month><year>2025</year></pub-date><volume>9</volume><elocation-id>e74038</elocation-id><history><date date-type="received"><day>16</day><month>03</month><year>2025</year></date><date date-type="rev-recd"><day>23</day><month>09</month><year>2025</year></date><date date-type="accepted"><day>24</day><month>09</month><year>2025</year></date></history><copyright-statement>&#x00A9; Aviad Raz, Yael Inbar, Ziv Paz, Barkan Hofman, Zalman Itzhakov, Orly Weinstein. Originally published in JMIR Formative Research (<ext-link ext-link-type="uri" xlink:href="https://formative.jmir.org">https://formative.jmir.org</ext-link>), 10.11.2025. </copyright-statement><copyright-year>2025</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 Formative Research, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://formative.jmir.org">https://formative.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://formative.jmir.org/2025/1/e74038"/><abstract><p>The regulatory focus on premarket approval, overlooking and limiting the life cycle, real-world adaptiveness potential of artificial intelligence in health care, requires ongoing oversight and quality assurance by health care providers&#x2013;cum-deployers, especially during early adoption.</p></abstract><kwd-group><kwd>artificial intelligence</kwd><kwd>regulation</kwd><kwd>implementation</kwd><kwd>health care management</kwd><kwd>radiology</kwd><kwd>content analysis</kwd><kwd>qualitative</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>This study explores how the specific nature of regulating health care artificial intelligence (AI) influences managing its deployment. Food and Drug Administration and European Commission regulations focus on premarket approval yet fail to address monitoring of AI postmarketing [<xref ref-type="bibr" rid="ref1">1</xref>]. Better regulations for &#x201C;adaptive&#x201D; AI systems are needed. These are considered with precaution as &#x201C;high-risk&#x201D; and prohibited from fully autonomous diagnosis. As AI models are exposed to new data in clinical settings, their performance may degrade or alter over time, necessitating ongoing oversight [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref3">3</xref>]. This often means that health care providers must step into the regulatory ambiguity zone to develop local protocols for quality assurance during early adoption phases.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Overview</title><p>In-depth semistructured interviews (30&#x2010;80 min) were conducted with 65 (29 females, 36 males) managers and physicians (mainly radiologists) from 4 different Israeli hospitals. Participants, identified by hospital management, were voluntarily included as deployers of AI for medical imaging analysis. Using a grounded theory approach [<xref ref-type="bibr" rid="ref4">4</xref>], preliminary codes were identified based on the literature review, with additional themes identified through interview analysis. The research team did the coding in parallel to ensure interrater reliability and to discuss further emerging codes. Data analysis was completed upon agreement that thematic saturation was reached.</p></sec><sec id="s2-2"><title>Ethical Considerations</title><p>This research was approved by Clalit Health Services Ethical Review Board (number 0001&#x2010;22-CNT-C). Participants signed an informed consent form; all details were anonymized to maintain privacy and confidentiality; no compensation was provided to participants.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Overview</title><p>Many of our respondents criticized the absence of clear regulations for AI implementation, seen as challenging and at times confusing, yet also enabling experimentation.</p></sec><sec id="s3-2"><title>The Precautionary Nature of AI Regulation in Health Care and Its Postdeployment Implications</title><p>Current premarket approval processes require AI-based medical devices to stop their retraining postdeployment. This reflects precautionary regulation regarding health care AI. Our respondents expressed worries about having to become the &#x201C;AI&#x2019;s QA [quality assurance] testers&#x201D;: &#x201C;I cannot always rely on the AI in trauma cases where the injection is not good enough and it does not detect heart failure...At nights I filter the hemorrhages alerts because it is over-sensitive...I wish I could teach it, talk to it, like a real team member&#x201D; (N8).</p><p>AI systems were considered &#x201C;overalerting,&#x201D; and managers instructed physicians to customize the alert threshold according to their needs: &#x201C;We got used to all sorts of false alerts. So, we rely more on our experience and knowledge, and we combine that with the system&#x201D; (M6). Managers and local &#x201C;champions&#x201D; (&#x201C;superuser&#x201D; radiologists) had to become AI supervisors: &#x201D;I make everyone here provide feedback regarding the AI system&#x201D; (M5). Playing an active role in shaping the use of AI systems was nevertheless seen positively: &#x201C;We feel like we are part of the development team. It feels good. It makes me even more engaged&#x201D; (R1).</p></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><p>Our main study findings show how regulating health care AI influences managing its deployment by highlighting the need for customization of the AI tools that require experimentation. Strategies included vendor-appointed &#x201C;champions&#x201D; and on-site feedback loops [<xref ref-type="bibr" rid="ref5">5</xref>]. Nevertheless, such customization requires further monitoring of bias metrics in model outputs and selective use by physicians.</p><p>There are some limitations to consider. Findings were drawn from interviews with radiologists, considered early adaptors of technologies, whose experiences may vary from that of other health providers. Although the study captures early adoption phases, future research should explore how this might shape long-term AI integration. In conclusion, the broader implications are that to become a sustainable approach in medical AI implementation, the &#x201C;use first, trust later&#x201D; mindset cannot be left unmonitored. Regulation should address adaptive AI and consider how transparency (rather than explainability) of the initial and postdeployment training, as well as bias monitoring, can enable oversight. Additionally, hospital administrators should work with AI developers to monitor biases in customization [<xref ref-type="bibr" rid="ref6">6</xref>], as well as manage effective teaming routines with AI.</p></sec></body><back><ack><p>The authors acknowledge support from the Israel Science Foundation grant number 1325/23. We are grateful to all our team members at the AI in Healthcare Organizations Lab [<xref ref-type="bibr" rid="ref7">7</xref>] and to the interviewees who participated in the study.</p></ack><notes><sec><title>Data Availability</title><p>Anonymized transcripts are available from the corresponding author.</p></sec></notes><fn-group><fn fn-type="con"><p>AR: conceptualization, writing, formal analysis. YI: writing, formal analysis. ZP: review &#x0026; editing, funding acquisition. BH: investigation, formal analysis, review &#x0026; editing. ZI and OW: project administration.</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</term><def><p>artificial intelligence</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>Agarwal</surname><given-names>R</given-names> </name><name name-style="western"><surname>Dugas</surname><given-names>M</given-names> </name><name name-style="western"><surname>Gao</surname><given-names>G (Gordon</given-names> </name></person-group><article-title>Augmenting physicians with artificial intelligence to transform healthcare: Challenges and opportunities</article-title><source>Economics Manag Strategy</source><year>2024</year><month>03</month><volume>33</volume><issue>2</issue><fpage>360</fpage><lpage>374</lpage><pub-id pub-id-type="doi">10.1111/jems.12555</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>Yu</surname><given-names>KH</given-names> </name><name name-style="western"><surname>Beam</surname><given-names>AL</given-names> </name><name name-style="western"><surname>Kohane</surname><given-names>IS</given-names> </name></person-group><article-title>Artificial intelligence in healthcare</article-title><source>Nat Med</source><year>2021</year><volume>27</volume><issue>1</issue><fpage>9</fpage><lpage>20</lpage></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>Lee</surname><given-names>P</given-names> </name><name name-style="western"><surname>Kummerfeld</surname><given-names>E</given-names> </name><name name-style="western"><surname>Yu</surname><given-names>KH</given-names> </name></person-group><article-title>Regulatory oversight of artificial intelligence and machine learning in healthcare</article-title><source>J Healthc Inform Res</source><year>2020</year><volume>4</volume><issue>1</issue><fpage>32</fpage><lpage>54</lpage></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>Gioia</surname><given-names>DA</given-names> </name><name name-style="western"><surname>Corley</surname><given-names>KG</given-names> </name><name name-style="western"><surname>Hamilton</surname><given-names>AL</given-names> </name></person-group><article-title>Seeking Qualitative Rigor in Inductive Research</article-title><source>Organ Res Methods</source><year>2013</year><month>01</month><volume>16</volume><issue>1</issue><fpage>15</fpage><lpage>31</lpage><pub-id pub-id-type="doi">10.1177/1094428112452151</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Faulconbridge</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sarwar</surname><given-names>A</given-names> </name><name name-style="western"><surname>Spring</surname><given-names>M</given-names> </name></person-group><article-title>How Professionals Adapt to Artificial Intelligence: The Role of Intertwined Boundary Work</article-title><source>J Management Studies</source><year>2025</year><month>07</month><volume>62</volume><issue>5</issue><fpage>1991</fpage><lpage>2024</lpage><pub-id pub-id-type="doi">10.1111/joms.12936</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>Cross</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Choma</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Onofrey</surname><given-names>JA</given-names> </name></person-group><article-title>Bias in medical AI</article-title><source>PLOS Digit Health</source><year>2024</year><month>07</month><volume>3</volume><issue>11</issue><fpage>e0000651</fpage><pub-id pub-id-type="doi">10.1371/journal.pdig.0000651</pub-id></nlm-citation></ref><ref id="ref7"><label>7</label><nlm-citation citation-type="web"><article-title>AI in Healthcare Organizations Lab</article-title><access-date>2025-11-03</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://aihealthcarelab.com/">https://aihealthcarelab.com/</ext-link></comment></nlm-citation></ref></ref-list></back></article>