<?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">J Med Internet Res</journal-id><journal-id journal-id-type="publisher-id">jmir</journal-id><journal-id journal-id-type="index">1</journal-id><journal-title>Journal of Medical Internet Research</journal-title><abbrev-journal-title>J Med Internet Res</abbrev-journal-title><issn pub-type="epub">1438-8871</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">v27i1e76941</article-id><article-id pub-id-type="doi">10.2196/76941</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Physician Use of Large Language Models: A Quantitative Study Based on Large-Scale Query-Level Data</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes" equal-contrib="yes"><name name-style="western"><surname>Qiu</surname><given-names>Lin</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Tang</surname><given-names>Chuang</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Bi</surname><given-names>Xuan</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Burtch</surname><given-names>Gordon</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff4">4</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Chen</surname><given-names>Yanmin</given-names></name><degrees>MM</degrees><xref ref-type="aff" rid="aff5">5</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Zhang</surname><given-names>Heping</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff6">6</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Information Systems and Management Engineering, Southern University of Science and Technology</institution><addr-line>CoE North 907, 1088 Xueyuan Ave</addr-line><addr-line>Shenzhen</addr-line><country>China</country></aff><aff id="aff2"><institution>Peking University HSBC Business School</institution><addr-line>Shenzhen</addr-line><country>China</country></aff><aff id="aff3"><institution>Department of Information and Decision Sciences, Carlson School of Management, University of Minnesota</institution><addr-line>Minnesota</addr-line><addr-line>MN</addr-line><country>United States</country></aff><aff id="aff4"><institution>Department of Information Systems, Questrom School of Business, Boston University</institution><addr-line>Boston</addr-line><addr-line>MA</addr-line><country>United States</country></aff><aff id="aff5"><institution>Shenzhen Maternity and Child Healthcare Hospital, Southern Medical University</institution><addr-line>Shenzhen</addr-line><country>China</country></aff><aff id="aff6"><institution>Department of Biostatistics, Yale University School of Public Health</institution><addr-line>New Haven</addr-line><addr-line>CT</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Coristine</surname><given-names>Andrew</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Wang</surname><given-names>Le</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Kim</surname><given-names>Seung Hyun</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Zhou</surname><given-names>Ya</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Lin</surname><given-names>Yan</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Lin Qiu, PhD, Department of Information Systems and Management Engineering, Southern University of Science and Technology, CoE North 907, 1088 Xueyuan Ave, Shenzhen, 518055, China, 86 0755 88012425; <email>qiul@sustech.edu.cn</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>these authors contributed equally</p></fn></author-notes><pub-date pub-type="collection"><year>2025</year></pub-date><pub-date pub-type="epub"><day>25</day><month>8</month><year>2025</year></pub-date><volume>27</volume><elocation-id>e76941</elocation-id><history><date date-type="received"><day>06</day><month>05</month><year>2025</year></date><date date-type="rev-recd"><day>12</day><month>07</month><year>2025</year></date><date date-type="accepted"><day>14</day><month>07</month><year>2025</year></date></history><copyright-statement>&#x00A9; Lin Qiu, Chuang Tang, Xuan Bi, Gordon Burtch, Yanmin Chen, Heping Zhang. Originally published in the Journal of Medical Internet Research (<ext-link ext-link-type="uri" xlink:href="https://www.jmir.org">https://www.jmir.org</ext-link>), 25.8.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 the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.jmir.org/">https://www.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://www.jmir.org/2025/1/e76941"/><abstract><sec><title>Background</title><p>Generative artificial intelligence (GenAI) has rapidly emerged as a promising tool in health care. Despite its growing adoption, how physicians make use of it in medical practice has not been qualitatively studied. Existing literature has largely focused on theoretical applications or experimental validations, with limited insight into real-world physician engagement with GenAI technologies.</p></sec><sec><title>Objective</title><p>The aim of this study was to leverage a fine-grained dataset at the query level to quantitatively examine how physicians incorporate GenAI into their clinical and research workflows. The primary objective was to analyze usage patterns over time and across physician demographics. A secondary goal was to assess potential risks to patient privacy arising from physicians&#x2019; interactions with GenAI platforms.</p></sec><sec sec-type="methods"><title>Methods</title><p>This study collected 106,942 query-and-answer pairs by 989 physicians between August 29, 2023, and April 16, 2024. We performed topic classification to identify the most prevalent use cases, examining how these use cases evolved over time and across demographics. We also developed sensitivity classifiers to detect personally identifiable information in physicians&#x2019; queries to explore the potential privacy breach risks around physicians&#x2019; use of GenAI.</p></sec><sec sec-type="results"><title>Results</title><p>Approximately 40% (396/989) of the enrolled physicians were female, 45.9% (454/989) were younger than 25 years, and 54.1% (535/989) were between 25 and 56 years of age. The majority of them worked in clinical departments (680/989, 68.8%) or medical technology departments (127/989, 12.8%). Our classification-based quantitative analyses suggest the following. First, physicians use GenAI predominantly for medical research (64,379/106,942, 60.2%) rather than clinical practice (13,100/106,942, 12.25%). Second, physicians focus more on health care&#x2013;related questions (rising from 64,165/106,942, 60% to 83,415/106,942, 78%) within the first 15% (16,041/106,942) of their query sequence. Third, the use of GenAI differed across physician demographics and features. Specifically, female physicians asked a larger proportion of clinical questions (female: 0.154 vs male: 0.108; <italic>P</italic>&#x003C;.001) and administration questions (female: 0.027 vs male: 0.018; <italic>P</italic>&#x003C;.001) than male physicians; younger physicians posed more clinical questions (age &#x2264;25: 0.146 vs age &#x2208; (25, 40]: 0.115 vs age &#x003E;40: 0.103; <italic>P</italic>&#x003C;.001) but fewer research questions (age &#x2264;25: 0.580 vs age &#x2208; (25, 40]: 0.607 vs age &#x003E;40: 0.664; <italic>P</italic>&#x003C;.001) than senior physicians; and physicians accessing GenAI via computers asked more research questions (computer: 0.637 vs mobile: 0.296; <italic>P&#x003C;.</italic>001), whereas physicians using mobile devices asked more clinical questions (computer: 0.107 vs mobile: 0.264; <italic>P</italic>&#x003C;.001). Fourth, only 2.68% (2866/106,942) of physician queries contained sensitive information, the majority of which were primarily derived from writing and editing.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Physicians are actively integrating GenAI into their professional routines, primarily leveraging it for research but also increasingly for clinical support. Usage patterns vary significantly across demographic lines, including gender, age, and device preference. Despite the presence of sensitive information in some queries, the risk of privacy breaches appears to be low.</p></sec></abstract><kwd-group><kwd>generative AI</kwd><kwd>large language models</kwd><kwd>health care</kwd><kwd>generative AI usage</kwd><kwd>privacy</kwd><kwd>artificial intelligence</kwd><kwd>generative artificial intelligence</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Since its launch in late 2022, ChatGPT has been at the forefront of the burgeoning field of generative artificial intelligence (GenAI), sparking immense enthusiasm yet significant concerns within academic and professional communities [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref4">4</xref>].</p><p>GenAI models offer significant potential for innovation in the health care domain [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. They have the potential to streamline time-consuming administrative tasks [<xref ref-type="bibr" rid="ref12">12</xref>], support informed medical decisions through precise and personalized treatment recommendations [<xref ref-type="bibr" rid="ref6">6</xref>], serve as an interactive encyclopedia for medical education [<xref ref-type="bibr" rid="ref7">7</xref>], and drive medical research forward more generally [<xref ref-type="bibr" rid="ref7">7</xref>]. However, the realization of these benefits depends on various factors. To provide value in clinical decision support, these technologies must first be integrated into existing technological systems [<xref ref-type="bibr" rid="ref7">7</xref>] and their implementation must be coupled with significant modifications to medical workflows and processes [<xref ref-type="bibr" rid="ref12">12</xref>]. Unfortunately, comprehensively implementing these technologies within the health care sector is made difficult because GenAI technologies present unique challenges [<xref ref-type="bibr" rid="ref12">12</xref>]. The most notable risks that have been raised to date include data privacy concerns [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>] (eg, noncompliance with the Health Insurance Portability and Accountability Act [<xref ref-type="bibr" rid="ref15">15</xref>]), the concern that clinicians may enter patients&#x2019; protected health care information within queries, and &#x201C;hallucination,&#x201D; whereby LLMs could potentially mislead physicians [<xref ref-type="bibr" rid="ref6">6</xref>].</p><p>As GenAI increasingly penetrates health care practice, it is essential to understand how physicians are adopting and using these technologies. Existing research on this topic generally falls into 3 main streams. The first stream is studying GenAI models for medical applications, as exemplified by various MedGPTs [<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. Although these studies demonstrate potential use cases for GenAI, they are typically conducted in experimental settings [<xref ref-type="bibr" rid="ref16">16</xref>-<xref ref-type="bibr" rid="ref19">19</xref>]. How physicians engage with these technologies in real-world settings remains poorly understood. The second stream involves small-scale qualitative research, such as interviews or surveys with limited participant pools [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. Although valuable for exploratory insights, these studies offer limited generalizability due to their constrained sample sizes. The third stream consists of review papers that synthesize existing AI-related research to infer potential uses of GenAI in health care [<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. However, these reviews often lack detailed, practice-level insights into how GenAI is being integrated into clinical or research workflows. To date, few studies have quantitatively examined how physicians actually use GenAI in routine clinical or research practice.</p><p>Moreover, while many studies have highlighted the potential advantages of GenAI in health care [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref9">9</xref>], few address the challenges associated with its use. At this early stage of GenAI adoption, it remains unclear whether digital divides exist across different demographic groups. Digitally disadvantaged users may be less likely to adopt advanced GenAI tools, thereby hindering the widespread integration of these models. Additionally, given that GenAI systems are not yet formally regulated or integrated into mainstream electronic health record systems, privacy risks have not been systematically assessed.</p><p>Given the foregoing situation, this paper explored large-scale query-level data to quantitatively explore the use of GenAI by physicians in practice. Specifically, we sought to answer questions including the following: What types of topics do physicians inquire about? How do these topics evolve with increased engagement and vary across physician demographics? How frequently do the queries contain sensitive information?</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design</title><p>This study used a classification-based quantitative descriptive design, which is well-suited for examining use patterns and uncovering empirical insights into the use of GenAI [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. We applied separate classification models to identify query topics and detect sensitive information&#x2014;approaches that have demonstrated strong performance in processing large-scale textual data [<xref ref-type="bibr" rid="ref26">26</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. By categorizing the topics of physician queries, we were able to trace usage trends over time and across demographic groups. In parallel, our sensitivity analysis allowed us to evaluate potential privacy risks associated with physicians&#x2019; interactions with GenAI platforms.</p></sec><sec id="s2-2"><title>Setting, Participants, and Sampling</title><p>Our query-and-answer data were collected from a company in Xiamen, China, which hosts a website that allowed physicians to access popular GenAI (eg, ChatGPT-4 and ChatGPT-3.5 from OpenAI) via these models&#x2019; application programming interfaces. This company invited physician participants from Dingxiangyuan, a leading medical community in China. As one of the largest web-based platforms for doctors, researchers, and health care professionals in the country, Dingxiangyuan provides a valuable resource for accessing a broad pool of physician users.</p><p>As most of these users were from China, they had limited access to cutting-edge GenAI models via non&#x2013;application programming interface channels during our study period. The data collected are believed to reflect the majority of participating physicians&#x2019; use of GenAI during the observation period. Users&#x2019; demographic information, including age, gender, department, and device type, was also collected from this company.</p></sec><sec id="s2-3"><title>Data Collection</title><p>This study collected 106,942 query-and-answer pairs by 989 physicians between August 29, 2023, and April 16, 2024, to examine how the use of GenAI evolved over time and across demographics. Approximately 40% (n=396) of the enrolled physicians were female, 45.9% (n=454) were younger than 25 years, and 54.1% (n=535) were between 25 and 56 years. The majority worked in clinical departments (n=680, 68.8%) or medical technology departments (n=127, 12.8%).</p></sec><sec id="s2-4"><title>Data Analysis</title><p>We conducted two sets of text analyses. First, we classified the queries to identify the search topics from physician users. We integrated a GPT-4&#x2013;based classifier with a rule-based method to perform this classification (for method details, see the Topic Classification section of <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). These classified topics allowed us to determine the topics of physicians&#x2019; prevalent use cases and to examine if these use cases significantly varied with physicians&#x2019; engagement and their demographics.</p><p>Second, we performed an additional text-mining analysis to detect potentially sensitive information existing in the queries. We created a detector that incorporates regular expressions, Microsoft&#x2019;s Presidio [<xref ref-type="bibr" rid="ref29">29</xref>], and ChatGPT-based detection to thoroughly search for personally identifiable information (for method details, see the Sensitivity Detection section of <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). By analyzing the detected sensitive information, we categorized and quantified the types and frequency of sensitive data present in physicians&#x2019; queries. This allowed us to assess the risks of privacy breaches and identify specific instances where breaches may occur.</p></sec><sec id="s2-5"><title>Ethical Considerations</title><p>We obtained permission from the Xiamen Moniu Investment Company to use their dataset for our secondary data analysis. At the time of data collection, the company obtained informed consent from all participants, and all records were subsequently anonymized to safeguard privacy and confidentiality. Participants received complimentary access to the GenAI tool as compensation.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Query Topics</title><p>To understand physicians&#x2019; objectives when they engage with GenAI models, we conducted text mining on a broad sample of input queries. <xref ref-type="table" rid="table1">Table 1</xref> summarizes 15 topics extracted from user queries. They are divided into 4 broad groups in both health care&#x2013;related and non&#x2013;health care settings. As depicted, physicians used the GenAI tool not only for health care&#x2013;related tasks, including clinical practice, medical research, and administrative work, but also for tasks unrelated to health care. The distribution across all 15 topic categories is also detailed in <xref ref-type="table" rid="table1">Table 1</xref>. In health care&#x2013;related queries, a significant proportion of the 106,942 physician queries were related to medical research, such as writing and editing (n=24,688, 23.09%), translation (n=19,835, 18.55%), and data analysis and software use (n=17,412, 16.28%). This implies that physicians primarily use GenAI models for research in health care&#x2013;related settings. Compared with conventional medical research tools like Google Scholar or PubMed, which serve primarily as search engines and databases for retrieving content, GenAI tools actively generate new text and help synthesize information across sources. Notably, physicians are not just consuming information. They are interactively collaborating with GenAI tools to think through research problems in real time (eg, following the chain of thought in solving data analysis problems). All of these advanced capabilities of GenAI are attracting users&#x2019; attention.</p><p>Further, our findings revealed a seeming reluctance among physicians to engage in queries related to clinical practice. Examples of queries and answers for clinical practice and medical research are presented in <xref ref-type="other" rid="box1">Textbox 1</xref>. These examples demonstrate that GenAI can provide reasonable answers to both types of questions. However, physicians searched for clinical practice significantly less frequently than they searched for medical research. Physicians sought information about basic medical science and clinical medicine at rates of 6.80% and 3.66%, respectively. Searches for medication information and surgical techniques were markedly lower, at just 0.94% and 0.85%, respectively. There are several potential underlying reasons for this hesitancy. First, physicians are cautious about sharing patient information on the third-party GenAI platform, even anonymously. Without sufficient patient information, queries related to clinical practice become significantly less effective. Second, the conversational nature of GenAI models requires substantial effort to sequentially input a complete patient health profile [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. This is time-consuming and deters the integration of clinical practice with GenAI models. Third, the current capabilities of GenAI are limited in integrating complex medical information, often resulting in clinical ineffectiveness, particularly when multiple conditions must be considered [<xref ref-type="bibr" rid="ref32">32</xref>].</p><p>In queries unrelated to health care, the majority tended to be informal. The largest proportion of these queries pertained to writing and editing tasks (12.86%), including the preparation of documents for non&#x2013;health care purposes. An additional share of queries involved informal interactions (8.76%), such as searching for recipes, composing poetry, and writing greetings.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Distribution of 15 topic categories from queries (N=106,942).</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Topic category</td><td align="left" valign="bottom">Values, n (%)</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Health care&#x2013;related</td></tr><tr><td align="left" valign="top">&#x2003;Writing and editing</td><td align="left" valign="top">24,688 (23.09)</td></tr><tr><td align="left" valign="top">&#x2003;Translation</td><td align="left" valign="top">19,835 (18.55)</td></tr><tr><td align="left" valign="top">&#x2003;Data analysis and software use</td><td align="left" valign="top">17,412 (16.28)</td></tr><tr><td align="left" valign="top">&#x2003;Medical experimental design</td><td align="left" valign="top">2439 (2.28)</td></tr><tr><td align="left" valign="top">&#x2003;Basic medical science</td><td align="left" valign="top">7267 (6.80)</td></tr><tr><td align="left" valign="top">&#x2003;Clinical medicine</td><td align="left" valign="top">3910 (3.66)</td></tr><tr><td align="left" valign="top">&#x2003;Medication information</td><td align="left" valign="top">1007 (0.94)</td></tr><tr><td align="left" valign="top">&#x2003;Surgical techniques</td><td align="left" valign="top">904 (0.85)</td></tr><tr><td align="left" valign="top">&#x2003;Public education</td><td align="left" valign="top">1222 (1.14)</td></tr><tr><td align="left" valign="top">&#x2003;Hospital governance</td><td align="left" valign="top">971 (0.91)</td></tr><tr><td align="left" valign="top" colspan="2">Not related to health care</td></tr><tr><td align="left" valign="top">&#x2003;Writing and editing</td><td align="left" valign="top">13,753 (12.86)</td></tr><tr><td align="left" valign="top">&#x2003;Other</td><td align="left" valign="top">9366 (8.76)</td></tr><tr><td align="left" valign="top">&#x2003;Data analysis and software use</td><td align="left" valign="top">3013 (2.82)</td></tr><tr><td align="left" valign="top">&#x2003;Relationships</td><td align="left" valign="top">897 (0.84)</td></tr><tr><td align="left" valign="top">&#x2003;Entertainment</td><td align="left" valign="top">258 (0.24)</td></tr></tbody></table></table-wrap><boxed-text id="box1"><title> Examples of topic categories.</title><p><bold>Writing and editing</bold></p><p>Q. How to Determine a PhD Research Topic in Gynecologic Oncology?</p><p>A. Determining a PhD research topic is a process that requires careful consideration and thorough investigation. If you are interested in pursuing doctoral research in the field of gynecologic oncology, the following steps and suggestions may be helpful:</p><p>Understand the Field: Begin by extensively reading scientific literature related to gynecologic oncology. Familiarize yourself with current research developments, key issues, and unresolved scientific challenges. This will help you build a strong foundational understanding and stay informed about the latest trends in the field.</p><p>Find a Supervisor: Look for a mentor with expertise and experience in gynecologic oncology. A qualified advisor can help you choose a suitable research direction and provide professional guidance and support throughout your study.</p><p>Identify a Research Question: Based on your interests and the current state of the field, define a specific research question or hypothesis. Your research topic should be academically significant and practically valuable&#x2014;aiming to fill existing knowledge gaps or address real-world problems.</p><p>Design a Research Plan: Develop a detailed research plan based on your research question. This plan should include the research methodology, experimental design, data collection strategies, and analysis methods.</p><p>Set Research Objectives and Expected Outcomes: Clearly define your research objectives and establish reasonable expectations for results. This helps maintain focus during your study and provides criteria for evaluating the success of your research.</p><p>Submit a Topic Proposal: Once you have finalized your research direction and discussed it with your supervisor, you will need to submit a formal research proposal according to your university or research institution's requirements.</p><p>Please note that the above steps are for reference only. The process of defining a PhD topic may vary by institution. It is best to have detailed discussions with your supervisor or relevant academic advisors to receive tailored guidance.</p><p><bold>Translation</bold></p><p>Q. Please translate: &#x201D;&#x672C;&#x7814;&#x7A76;&#x65E8;&#x5728;&#x6BD4;&#x8F83;&#x6297;&#x83CC;&#x5149;&#x52A8;&#x529B;&#x7597;&#x6CD5;&#x548C;&#x6B21;&#x6C2F;&#x9178;&#x94A0;&#x51B2;&#x6D17;&#xFF08;&#x6839;&#x7BA1;&#x51B2;&#x6D17;&#x7684;&#x91D1;&#x6807;&#x51C6;&#xFF09;&#x5728;&#x6297;&#x7CAA;&#x80A0;&#x7403;&#x83CC;&#x611F;&#x67D3;&#x7684;&#x6CBB;&#x7597;&#x6548;&#x679C;&#x201D;</p><p>A. &#x201C;The aim of this study was to compare the effectiveness of antimicrobial photodynamic therapy and sodium hypochlorite irrigation (the gold standard for root canal irrigation) in the treatment of Enterococcus faecalis infection.&#x201D;</p><p><bold>Data analysis and software use</bold></p><p>Q. In Mendelian randomization data analysis, if the odds ratio (OR) and p-value are known, how can the beta coefficient and standard error (SE) be calculated?</p><p>A. In Mendelian randomization data analysis, the odds ratio (OR) is a measure used to quantify the difference in rates between two groups. The p-value is a statistical indicator used to assess whether this difference is significant. If the OR and p-value are known, you can calculate the beta coefficient and standard error (SE) using the following formulas:</p><p>1. First, compute the natural logarithm of the OR: ln(OR) = ln(OR value)</p><p>2. Then calculate the beta value: beta = ln(OR) / 1.96</p><p>3. Calculate the standard error (SE): SE = 1 / (1.96 &#x00D7; &#x221A;(sample size of case group / sample size of control group))</p><p>Notes:</p><p>1. 1.96 is a constant used for computing a 95% confidence interval.</p><p>2. The case group refers to the treatment or intervention group, while the control group refers to the comparison or untreated group.</p><p>3. Sample size refers to the number of observations in each group.</p><p>Using these formulas, you can derive the beta and SE from the OR and p-value. These values are essential for further statistical inference and analysis.</p><p>Let me know if you'd like a numerical example or code to calculate these!</p><p><bold>Medical experimental design</bold></p><p>A. What Are the Current Mainstream Steps in a GST Pull-Down Assay?</p><p>Q. GST pull-down is a commonly used technique to study protein-protein interactions. The basic procedure includes the following steps:</p><p>Cloning and Expression of GST Fusion Protein:</p><p>The coding sequence of the target protein is fused with the GST (Glutathione S-Transferase) gene. This fusion gene is then cloned into an appropriate host organism (such as E. coli) for expression of the GST-tagged protein.</p><p>Purification of GST Fusion Protein:</p><p>The expressed GST fusion protein is purified using affinity chromatography. Glutathione agarose or magnetic beads are typically used because GST has a strong affinity for glutathione, allowing it to bind to the beads during purification.</p><p>Preparation of Cell Lysate:</p><p>The cells that may contain proteins interacting with the GST fusion protein are lysed using appropriate methods (e.g., mechanical disruption, sonication) to release intracellular proteins.</p><p>Affinity Precipitation (Pull-Down):</p><p>The cell lysate is incubated with the GST fusion protein immobilized on glutathione beads. This allows potential interacting partner proteins to bind to the GST-tagged protein.</p><p>Washing and Elution:</p><p>Multiple wash steps are performed to remove non-specific binders. Then, proteins specifically bound to the GST fusion protein are eluted by increasing the glutathione concentration.</p><p>Analysis:</p><p>The eluted proteins are analyzed by SDS-PAGE, followed by silver staining or Western blotting to identify which proteins interact with the GST fusion protein.</p><p>These are the standard steps in a GST pull-down assay. Specific protocols may vary depending on the nature of the proteins and experimental conditions. It is essential to maintain rigor and reproducibility in the experimental design to ensure the accuracy and reliability of the results.</p><p><bold>Basic medical science</bold></p><p>Q. What is relationship between iron metabolism and ferroptosis</p><p>A. There is a close relationship between iron metabolism and ferroptosis. Iron is an essential element for sustaining life and participates in many biological processes, including oxygen transport, DNA synthesis, and energy metabolism. However, when there is an excess of iron in the body or iron metabolism becomes dysregulated, it can lead to the production of large amounts of reactive oxygen species (ROS). This induces oxidative stress, damaging cell membranes, proteins, lipids, and DNA, ultimately resulting in cell death&#x2014;a process known as ferroptosis.</p><p>Ferroptosis is a newly identified form of programmed cell death, distinct from apoptosis, necrosis, and autophagy. During ferroptosis, excess iron catalyzes the Fenton reaction, producing hydroxyl radicals&#x2014;highly reactive free radicals that cause oxidative damage to proteins, lipids, and DNA, leading to cell injury and death.</p><p>Currently, ferroptosis is a major focus in tumor biology and neurodegenerative disease research. Many types of cancer cells and cells affected by neurodegenerative diseases show a high dependency on iron. Understanding and regulating the process of ferroptosis could provide new therapeutic strategies for treating these diseases.</p><p><bold>Clinical medicine</bold></p><p>Q. Differential diagnosis between sirenomelia and incomplete caudal regression</p><p>A. Sirenomelia (also known as Mermaid Syndrome) is a rare congenital developmental disorder characterized by the fusion of the lower limbs, giving the appearance of a mermaid&#x2019;s tail. In contrast, incomplete caudal regression refers to the underdevelopment or malformation of the caudal (tail) region, which may manifest as missing or abnormal tail structures.</p><p>Although sirenomelia and incomplete caudal regression share certain similarities, they are distinct conditions. Sirenomelia primarily involves fusion of the lower limbs, while incomplete caudal regression is centered around abnormalities in the development of the tail region.</p><p>In sirenomelia, additional malformations often accompany limb fusion, including abnormalities of the urogenital system and spinal column. In contrast, incomplete caudal regression typically involves developmental defects limited to the tail region and may not be associated with other organ anomalies.</p><p>Therefore, in clinical practice, these two conditions can be differentiated and diagnosed based on the specific features of the lower limbs and caudal region.</p><p><bold>Medication information</bold></p><p>Q. Can pregnant women take Azithromycin tablets?</p><p>A. The use of azithromycin during pregnancy should be approached with caution. Although some studies suggest that azithromycin is relatively safe for use during pregnancy, there may still be potential risks, especially when used in early pregnancy, as it could slightly increase the risk of certain birth defects.</p><p>Therefore, if you are pregnant and need to take azithromycin, it is essential to do so under a doctor's guidance. Your physician will evaluate the risks and benefits based on your specific condition and stage of pregnancy.</p><p>In general, the use of any medication during pregnancy&#x2014;including antibiotics&#x2014;should be under medical supervision. Self-medicating or purchasing drugs without a prescription is not recommended.</p><p><bold>Surgical techniques</bold></p><p>Q. Can an Attending Physician Perform a Level-III Surgery?</p><p>A. Generally speaking, attending physicians typically do not perform level-III surgeries independently, as such procedures are relatively complex and high-risk. These surgeries usually require the guidance of more senior doctors or collaboration with other specialists.</p><p>However, the ability to perform surgeries and the classification of surgical levels may vary depending on the hospital's requirements, the physician&#x2019;s professional experience, and their training background. Some attending physicians may possess advanced skills in specific fields or procedures and may therefore be authorized to perform certain level-III surgeries. This would require their qualifications and experience to be formally recognized and supported by the healthcare institution and relevant professional bodies.</p><p>The most accurate and specific information should come from the medical institution in question or the physician&#x2019;s official credentials. If you have questions about whether a specific procedure can be performed by an attending physician, it is advisable to consult the hospital&#x2019;s surgical department or the physician directly.</p></boxed-text></sec><sec id="s3-2"><title>Usage Pattern</title><p>Our study also examined how physicians use GenAI models. For precision, we focused specifically on the 4 broad groups outlined in <xref ref-type="table" rid="table1">Table 1</xref>.</p><p>First, we analyzed the temporal dynamics of health care&#x2013;related (including medical research, clinical practice, and administration groups) versus non&#x2013;health care topics in user queries, as illustrated in <xref ref-type="fig" rid="figure1">Figure 1</xref>. The x-axis represents the percentile of physicians&#x2019; queries in sequential order. A higher x-axis value indicates a later query, while a lower value indicates an earlier one. The y-axis represents the proportion of queries related to either the health care or non&#x2013;health care topic. This plot demonstrates an increase of around 20% in the proportion of health care&#x2013;related queries and a corresponding decrease of around 20% in non&#x2013;health care queries within approximately the first 15% of the query sequence, suggesting that engagement with the platform influences the predominance of health care queries. After this &#x201C;warm-up&#x201D; period, topic proportions stabilize, indicating a plateau in shifts as user engagement continues. This suggests that physicians start with casual, nonprofessional questions but shift to more serious ones over time, reflecting growing engagement and trust. These trends are also statistically verified through piecewise regression (see the Model Specification section of <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Dynamics of queries. The x-axis represents the percentile of a physician&#x2019;s queries in sequential order. The y-axis represents the proportion of queries related to either the health care or non&#x2013;health care topic. The black dashed line indicates a point (approximately the 15th percentile) starting from which the proportion of health care&#x2013;related queries became relatively high and consistent.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="jmir_v27i1e76941_fig01.png"/></fig><p>Second, we examined the heterogeneity in usage patterns across user demographics. <xref ref-type="table" rid="table2">Table 2</xref> displays the group means across different dimensions. First, we observed that the usage patterns among physicians varied by gender. Compared with male physicians, female physicians asked a larger proportion of clinical questions (female: 0.154 vs male: 0.108; <italic>P</italic>&#x003C;.001) and administration questions (female: 0.027 vs male: 0.018; <italic>P</italic>&#x003C;.001). Second, age and experience also affected usage. Younger physicians, early in their careers, tended to pose more clinical-related questions (age &#x2264;25: 0.146 vs age &#x2208; (25,40]: 0.115 vs age &#x003E;40: 0.103; <italic>P</italic>&#x003C;.001) compared to their senior counterparts, who were more inclined to inquire about research-related topics (age &#x2264;25: 0.580 vs age &#x2208; (25,40]: 0.607 vs age &#x003E;40: 0.664; <italic>P</italic>&#x003C;.001). This suggests that, unlike younger physicians, experienced physicians seemingly rely more on their own expertise in clinical settings but seek external input more frequently when engaging in research activities. Third, usage patterns varied based on the device used. Physicians accessing the platforms via computers asked more research-oriented questions (computer: 0.637 vs mobile: 0.296; <italic>P</italic>&#x003C;.001), whereas those using mobile devices primarily inquired about clinical (computer: 0.107 vs mobile: 0.264; <italic>P</italic>&#x003C;.001) and non&#x2013;health care (computer: 0.238 vs mobile: 0.393; <italic>P</italic>&#x003C;.001) topics. This discrepancy indicates that clinical and casual queries often arise spontaneously and are more likely to be addressed on-the-go, while research activities are typically conducted in a more serious manner, for example, via using desktops. Fourth, the department (ie, specialty) of physicians mattered. Among all departments, staff from the clinical department asked the most research questions (clinical department: 0.634 vs medical technology department: 0.540 vs other department: 0.418; <italic>P</italic>&#x003C;.001) and those from the medical technology department asked the most clinical questions (clinical department: 0.133 vs medical technology department: 0.141 vs other department: 0.078; <italic>P</italic>&#x003C;.001). We further used regression analyses to examine the heterogeneity in usage patterns across user demographics. The results are shown in <xref ref-type="table" rid="table3">Table 3</xref>. We found that the heterogeneity in usage patterns remained consistent even after controlling for other demographic factors.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Average proportions of queries across 4 topic groups.<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup></p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">Clinical</td><td align="left" valign="bottom">Research</td><td align="left" valign="bottom">Administration</td><td align="left" valign="bottom">Non&#x2013;health care</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="5">Gender</td></tr><tr><td align="left" valign="top">&#x2003;Female</td><td align="left" valign="top">0.154</td><td align="left" valign="top">0.588</td><td align="left" valign="top">0.027</td><td align="left" valign="top">0.232</td></tr><tr><td align="left" valign="top">&#x2003;Male</td><td align="left" valign="top">0.108</td><td align="left" valign="top">0.609</td><td align="left" valign="top">0.018</td><td align="left" valign="top">0.265</td></tr><tr><td align="left" valign="top">&#x2003;<italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Age (years)</td></tr><tr><td align="left" valign="top">&#x2003;&#x2264;25</td><td align="left" valign="top">0.146</td><td align="left" valign="top">0.58</td><td align="left" valign="top">0.02</td><td align="left" valign="top">0.254</td></tr><tr><td align="left" valign="top">&#x2003;(25,40]</td><td align="left" valign="top">0.115</td><td align="left" valign="top">0.607</td><td align="left" valign="top">0.02</td><td align="left" valign="top">0.258</td></tr><tr><td align="left" valign="top">&#x2003;&#x003E;40</td><td align="left" valign="top">0.103</td><td align="left" valign="top">0.664</td><td align="left" valign="top">0.024</td><td align="left" valign="top">0.208</td></tr><tr><td align="left" valign="top">&#x2003;<italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Device type</td></tr><tr><td align="left" valign="top">&#x2003;Computer</td><td align="left" valign="top">0.107</td><td align="left" valign="top">0.637</td><td align="left" valign="top">0.018</td><td align="left" valign="top">0.238</td></tr><tr><td align="left" valign="top">&#x2003;Mobile</td><td align="left" valign="top">0.264</td><td align="left" valign="top">0.296</td><td align="left" valign="top">0.043</td><td align="left" valign="top">0.393</td></tr><tr><td align="left" valign="top">&#x2003;<italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Department</td></tr><tr><td align="left" valign="top">&#x2003;Clinical</td><td align="left" valign="top">0.133</td><td align="left" valign="top">0.634</td><td align="left" valign="top">0.022</td><td align="left" valign="top">0.211</td></tr><tr><td align="left" valign="top">&#x2003;Medical tech</td><td align="left" valign="top">0.141</td><td align="left" valign="top">0.54</td><td align="left" valign="top">0.027</td><td align="left" valign="top">0.293</td></tr><tr><td align="left" valign="top">&#x2003;Others</td><td align="left" valign="top">0.078</td><td align="left" valign="top">0.418</td><td align="left" valign="top">0.014</td><td align="left" valign="top">0.49</td></tr><tr><td align="left" valign="top">&#x2003;<italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>We evaluated the average proportions of queries across the 4 topic groups: clinical practice, medical research, administration, and non&#x2013;health care. Group means across gender, age, device type, and department (ie, physician specialty) were considered. Systematic differences in patterns of use across physician demographics and device types were observed.</p></fn></table-wrap-foot></table-wrap><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Regression results of query types on users&#x2019; demographic information.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">(1) Clinical</td><td align="left" valign="bottom">(2) Research</td><td align="left" valign="bottom">(3) Administration</td><td align="left" valign="bottom">(4) Non&#x2013;health care</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="5">Male</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coefficient</td><td align="left" valign="top">&#x2212;0.039</td><td align="left" valign="top">&#x2212;0.009</td><td align="left" valign="top">&#x2212;0.007</td><td align="left" valign="top">0.055</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">.006</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Age</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x2003;Coefficient</named-content></td><td align="left" valign="top">0.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">0.000</td><td align="left" valign="top">&#x2212;0.001</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">.001</td><td align="left" valign="top">.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Department: clinical</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x2003;Coefficient</named-content></td><td align="left" valign="top">0.051</td><td align="left" valign="top">0.226</td><td align="left" valign="top">0.008</td><td align="left" valign="top">&#x2212;0.285</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Department: medical tech</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x2003;Coefficient</named-content></td><td align="left" valign="top">0.057</td><td align="left" valign="top">0.132</td><td align="left" valign="top">0.012</td><td align="left" valign="top">&#x2212;0.201</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Mobile</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x2003;Coefficient</named-content></td><td align="left" valign="top">0.157</td><td align="left" valign="top">&#x2212;0.333</td><td align="left" valign="top">0.024</td><td align="left" valign="top">0.153</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="5">Constant</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coefficient</td><td align="left" valign="top">0.084</td><td align="left" valign="top">0.442</td><td align="left" valign="top">0.009</td><td align="left" valign="top">0.465</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top">Observations</td><td align="left" valign="top">97,644</td><td align="left" valign="top">97,644</td><td align="left" valign="top">97,644</td><td align="left" valign="top">97,644</td></tr><tr><td align="left" valign="top"><italic>R</italic><sup>2</sup></td><td align="left" valign="top">0.031</td><td align="left" valign="top">0.073</td><td align="left" valign="top">0.005</td><td align="left" valign="top">0.071</td></tr></tbody></table></table-wrap></sec><sec id="s3-3"><title>Data Privacy</title><p>We examined potential privacy issues arising from the use of GenAI models by physicians. As GenAI models typically work as third-party entities, they often caution users against inputting sensitive information into the system. However, a thorough analysis is essential to determine the extent to which physicians adhere to these guidelines and prevent inadvertent input of sensitive data.</p><p>According to the Health Insurance Portability and Accountability Act Privacy Rule, there are 18 types of identifiers that may contain sensitive or personally identifiable information [<xref ref-type="bibr" rid="ref15">15</xref>]. As users were from China and had limited access to cutting-edge GenAI (<xref ref-type="table" rid="table4">Table 4</xref>), 15 types of identifiers were detected in our data.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Percentage of Health Insurance Portability and Accountability Act identifiers in physician queries.<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">Identifier</td><td align="left" valign="bottom">Values, n (%)</td></tr></thead><tbody><tr><td align="left" valign="top">Human name</td><td align="left" valign="top">958 (0.9)</td></tr><tr><td align="left" valign="top">Location</td><td align="left" valign="top">574 (0.5)</td></tr><tr><td align="left" valign="top">Account name</td><td align="left" valign="top">460 (0.4)</td></tr><tr><td align="left" valign="top">Age</td><td align="left" valign="top">284 (0.3)</td></tr><tr><td align="left" valign="top">Date</td><td align="left" valign="top">231 (0.2)</td></tr><tr><td align="left" valign="top">URL</td><td align="left" valign="top">132 (0.1)</td></tr><tr><td align="left" valign="top">Email address</td><td align="left" valign="top">60 (0.1)</td></tr><tr><td align="left" valign="top">Zip code</td><td align="left" valign="top">59 (0.1)</td></tr><tr><td align="left" valign="top">IP address</td><td align="left" valign="top">39 (0)</td></tr><tr><td align="left" valign="top">Phone number</td><td align="left" valign="top">27 (0)</td></tr><tr><td align="left" valign="top">Body information</td><td align="left" valign="top">21 (0)</td></tr><tr><td align="left" valign="top">Medical number</td><td align="left" valign="top">13 (0)</td></tr><tr><td align="left" valign="top">Vehicle number</td><td align="left" valign="top">1 (0)</td></tr><tr><td align="left" valign="top">Credit card</td><td align="left" valign="top">1 (0)</td></tr><tr><td align="left" valign="top">Fax number</td><td align="left" valign="top">1 (0)</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>Fifteen of 18 Health Insurance Portability and Accountability Act identifiers were detected in physician queries. The names of the 15 identifiers are provided. The count and percentage of queries that contained each identifier were recorded. Percentage = count/total number of queries &#x00D7; 100%.</p></fn></table-wrap-foot></table-wrap><p>We observed that users disclosed sensitive information on the GenAI platform extremely rarely. Among those rare instances, the most commonly disclosed sensitive information included human names, locations, and usernames, followed by ages, dates, and URLs. We further investigated the distribution of all types of identifiers across the 15 topic categories defined in <xref ref-type="table" rid="table1">Table 1</xref>. The majority of sensitive information was primarily derived from writing and editing. For instance, 576 of 958 instances of sensitive information on human names were linked to writing and editing, while 302 of 574 location-related sensitive information instances were connected to writing and editing. This suggests that users are less mindful of sensitive information when writing or editing documents. Moreover, sensitive information related to account names (435/460) and URLs (83/132) mainly arose from data analysis and software usage. This indicates a tendency for physicians to disclose sensitive information when copying directories or web sources.</p><p>To investigate how the privacy risk varied by user group, we regressed the indicator of whether to disclose sensitive information in the query on users&#x2019; demographic information. The results are shown in <xref ref-type="table" rid="table5">Table 5</xref>. In the first column, we used the ordinary least squares estimator, and in the second column, we used the logit estimator. Their results were consistent. We found that male physicians, compared with female physicians, were more likely to disclose sensitive information. Physicians from the medical technology department faced higher privacy risks than those from the clinical department and other departments. If physicians used the mobile version of the model, their likelihood of posting sensitive information was higher.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Regression results of privacy disclosure on users&#x2019; demographic information.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom"/><td align="left" valign="bottom">(1) Ordinary least squares</td><td align="left" valign="bottom">(2) Logit</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="3">Male</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x2003;Coefficient</named-content></td><td align="left" valign="top">0.007</td><td align="left" valign="top">0.372</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="3">Age</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coefficient</td><td align="left" valign="top">&#x2212;0.000</td><td align="left" valign="top">&#x2212;0.003</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">.01</td><td align="left" valign="top">.11</td></tr><tr><td align="left" valign="top" colspan="3">Department: clinical</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coefficient</td><td align="left" valign="top">0.004</td><td align="left" valign="top">0.257</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="3">Department: medical tech</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coefficient</td><td align="left" valign="top">0.007</td><td align="left" valign="top">0.362</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top" colspan="3">Mobile</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coefficient</td><td align="left" valign="top">0.002</td><td align="left" valign="top">0.129</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">.01</td><td align="left" valign="top">.08</td></tr><tr><td align="left" valign="top" colspan="3">Constant</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Coefficient</td><td align="left" valign="top">0.012</td><td align="left" valign="top">&#x2212;4.370</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>P</italic> value</td><td align="left" valign="top">&#x003C;.001</td><td align="left" valign="top">&#x003C;.001</td></tr><tr><td align="left" valign="top">Observations</td><td align="left" valign="top">97,644</td><td align="left" valign="top">97,644</td></tr><tr><td align="left" valign="top"><italic>R</italic><sup>2</sup></td><td align="left" valign="top">0.001</td><td align="left" valign="top">&#x2014;<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup></td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>Not applicable.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>This paper leverages a comprehensive query-and-answer dataset to understand how physicians use the current third-party GenAI models. Our findings offer key insights into GenAI model usage and potential in health care. We identify that, when used by physicians, GenAI models are predominantly used for medical research tasks rather than direct clinical applications. This trend highlights a gap between the potential and actual uses of GenAI models in health care, particularly in clinical practice. Health institutions can begin by promoting GenAI use in research applications, such as documentation, literature review, or patient education. These uses can build trust among physicians and demonstrate early value. Once this foundation is in place, institutions should introduce formal validation frameworks, standardized performance benchmarks, and clinical guidelines to assess GenAI for higher-stakes, decision-critical use.</p><p>Another observation is the gradual increase in physicians&#x2019; reliance on GenAI, starting with informal or personal queries and then evolving to more professional queries. This progression indicates a growing trust and familiarity with the technology. Accordingly, with time and improved integration, GenAI models could become a more requisite tool in health care.</p><p>Further, the varied usage patterns based on demographic factors also reveal how different groups within the medical community are adapting to GenAI. These differences not only point to the existence of digital divides but also offer valuable insights into how user needs and behaviors vary by gender, age, device type, and departmental affiliation. First, we showed that female physicians ask a larger proportion of clinical questions and administration questions than male physicians. This suggests that female physicians are more likely to see GenAI as a practical assistant for managing clinical decision-making and routine administrative tasks. Second, we found that younger physicians depend on GenAI in clinical settings more than senior physicians do. Practically, younger physicians&#x2019; greater focus on clinical use may reflect higher openness to technology or a need for support with real-time decision-making, while senior physicians&#x2019; stronger interest in research may point to their roles in academic medicine. Third, our results showed that physicians using GenAI on computers tend to ask more research-related questions, while those using mobile devices focus more on clinical inquiries. Such device-based variation highlights the importance of context-aware interface design&#x2014;mobile platforms may benefit from more streamlined, clinically oriented features. Last, we found that staff from clinical departments ask the most research questions, and those from medical technology departments ask the most clinical questions. This indicates that GenAI may be serving as a bridge between technical roles and clinical relevance, helping nonphysician staff understand how their work impacts patient care.</p><p>This study also quantifies privacy risks associated with GenAI, an area that has garnered increasing attention. Our findings indicate that while concerns about data privacy are acknowledged, the actual likelihood of sensitive information disclosure is relatively low. Importantly, we identify specific use scenarios&#x2014;such as drafting or editing documents&#x2014;where the risk of inadvertent disclosure is higher. These insights underscore the need for clear guidelines and safeguards to ensure responsible use of GenAI in medical contexts. Institutions should address this by establishing clear usage policies, input restrictions, and built-in safety mechanisms. For instance, institutions can enable input filters or redaction suggestions that flag or block sensitive content in real time, particularly for drafting or editing documents.</p><p>In sum, this real-world behavioral dataset offers a foundation for evidence-based governance of GenAI in health care. Regulatory agencies and professional bodies can use these insights to craft balanced guidelines that support innovation while safeguarding patient data and care quality.</p></sec><sec id="s4-2"><title>Limitations</title><p>Although the results of this study are promising, there are a number of limitations that should be considered. First, the majority of participating physicians were based in China, which may limit the generalizability of the results to other health care systems. The health care infrastructure, digital health policies, and physician workflows in China differ significantly from those in other countries such as the United States or those in Europe. For example, in China, a notable proportion of GenAI use cases involves language translation&#x2014;an application that may be less prevalent among physicians in English-speaking countries such as the United States. However, it is also important to highlight that many aspects of physician workflows are shared globally. Regardless of location, physicians commonly engage in both clinical decision-making and medical research, suggesting that core use cases for GenAI&#x2014;such as writing and editing, basic medical science, and clinical medicine&#x2014;are likely to be relevant across health care systems. Second, while this study uses a large-scale quantitative dataset, it does not incorporate qualitative data such as in-depth interviews or open-ended survey responses. Future studies could benefit from integrating qualitative methods to gain richer insights into physicians&#x2019; motivations, concerns, and contextual factors shaping GenAI usage. This mixed methods approach could also help explore nuances in trust-building and perceived risks that are difficult to capture through quantitative analysis alone. Last, the data used in this study were observational and derived from real-world usage logs, which means we cannot fully account for physicians&#x2019; intentions or the broader clinical context in which queries were made. This could limit the interpretability of some behavioral patterns.</p></sec><sec id="s4-3"><title>Conclusions</title><p>This study reveals that physicians primarily use GenAI for research rather than clinical tasks, with usage patterns evolving alongside growing trust. Demographic differences shape adoption, and privacy risks remain low but nonnegligible. These findings provide insights into developing safe, effective integration of GenAI into health care practice.</p></sec></sec></body><back><ack><p>Funding for LQ was provided by the Bureau of Education of Shenzhen Municipality (Y01976108). Funding for CT was provided by the National Natural Science Foundation of China (72302008) and Guangdong Basic and Applied Basic Research Foundation (2023A1515010823). No artificial intelligence&#x2013;generated text was used in this manuscript.</p></ack><notes><sec><title>Data Availability</title><p>The data analyzed in this study are available from the corresponding author upon reasonable request. All sensitive information has been redacted.</p></sec></notes><fn-group><fn fn-type="con"><p>LQ, CT, XB, GB, HZ, and YC designed the study, wrote the original draft of the manuscript, and reviewed and edited the manuscript; LQ and YC administered the project; LQ and CT preprocessed, verified, and analyzed the data. All authors had final responsibility for the decision to submit for publication.</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">GenAI</term><def><p>generative artificial intelligence</p></def></def-item><def-item><term id="abb2">LLM</term><def><p>large language model</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>Bohacek</surname><given-names>M</given-names> </name><name name-style="western"><surname>Farid</surname><given-names>H</given-names> </name></person-group><article-title>The making of an AI news anchor-and its implications</article-title><source>Proc Natl Acad Sci U S A</source><year>2024</year><month>01</month><day>2</day><volume>121</volume><issue>1</issue><fpage>e2315678121</fpage><pub-id pub-id-type="doi">10.1073/pnas.2315678121</pub-id><pub-id pub-id-type="medline">38150500</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>Mitchell</surname><given-names>M</given-names> </name></person-group><article-title>Debates on the nature of artificial general intelligence</article-title><source>Science</source><year>2024</year><month>03</month><day>22</day><volume>383</volume><issue>6689</issue><fpage>eado7069</fpage><pub-id pub-id-type="doi">10.1126/science.ado7069</pub-id><pub-id pub-id-type="medline">38513022</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>Zhou</surname><given-names>E</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>D</given-names> </name></person-group><article-title>Generative artificial intelligence, human creativity, and art</article-title><source>PNAS Nexus</source><year>2024</year><month>03</month><volume>3</volume><issue>3</issue><fpage>pgae052</fpage><pub-id pub-id-type="doi">10.1093/pnasnexus/pgae052</pub-id><pub-id pub-id-type="medline">38444602</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>Cardamone</surname><given-names>NC</given-names> </name><name name-style="western"><surname>Olfson</surname><given-names>M</given-names> </name><name name-style="western"><surname>Schmutte</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Classifying unstructured text in electronic health records for mental health prediction models: large language model evaluation study</article-title><source>JMIR Med Inform</source><year>2025</year><month>01</month><day>21</day><volume>13</volume><issue>1</issue><fpage>e65454</fpage><pub-id pub-id-type="doi">10.2196/65454</pub-id><pub-id pub-id-type="medline">39864953</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>Anderer</surname><given-names>S</given-names> </name><name name-style="western"><surname>Hswen</surname><given-names>Y</given-names> </name></person-group><article-title>Will generative AI tools improve sccess to reliable health information?</article-title><source>JAMA</source><year>2024</year><month>04</month><day>23</day><volume>331</volume><issue>16</issue><fpage>1347</fpage><lpage>1349</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.23003</pub-id><pub-id pub-id-type="medline">38578617</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>Duffourc</surname><given-names>M</given-names> </name><name name-style="western"><surname>Gerke</surname><given-names>S</given-names> </name></person-group><article-title>Generative AI in health care and liability risks for physicians and safety concerns for patients</article-title><source>JAMA</source><year>2023</year><month>07</month><day>25</day><volume>330</volume><issue>4</issue><fpage>313</fpage><lpage>314</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.9630</pub-id><pub-id pub-id-type="medline">37410497</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>Haupt</surname><given-names>CE</given-names> </name><name name-style="western"><surname>Marks</surname><given-names>M</given-names> </name></person-group><article-title>AI-generated medical advice-GPT and beyond</article-title><source>JAMA</source><year>2023</year><month>04</month><day>25</day><volume>329</volume><issue>16</issue><fpage>1349</fpage><lpage>1350</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.5321</pub-id><pub-id pub-id-type="medline">36972070</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>Kulkarni</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Singh</surname><given-names>H</given-names> </name></person-group><article-title>Artificial intelligence in clinical diagnosis: opportunities, challenges, and hype</article-title><source>JAMA</source><year>2023</year><month>07</month><day>25</day><volume>330</volume><issue>4</issue><fpage>317</fpage><lpage>318</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.11440</pub-id><pub-id pub-id-type="medline">37410477</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>Sandmann</surname><given-names>S</given-names> </name><name name-style="western"><surname>Riepenhausen</surname><given-names>S</given-names> </name><name name-style="western"><surname>Plagwitz</surname><given-names>L</given-names> </name><name name-style="western"><surname>Varghese</surname><given-names>J</given-names> </name></person-group><article-title>Systematic analysis of ChatGPT, Google search and Llama 2 for clinical decision support tasks</article-title><source>Nat Commun</source><year>2024</year><month>03</month><day>6</day><volume>15</volume><issue>1</issue><fpage>2050</fpage><pub-id pub-id-type="doi">10.1038/s41467-024-46411-8</pub-id><pub-id pub-id-type="medline">38448475</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>Strachan</surname><given-names>JWA</given-names> </name><name name-style="western"><surname>Albergo</surname><given-names>D</given-names> </name><name name-style="western"><surname>Borghini</surname><given-names>G</given-names> </name><etal/></person-group><article-title>Testing theory of mind in large language models and humans</article-title><source>Nat Hum Behav</source><year>2024</year><month>07</month><volume>8</volume><issue>7</issue><fpage>1285</fpage><lpage>1295</lpage><pub-id pub-id-type="doi">10.1038/s41562-024-01882-z</pub-id><pub-id pub-id-type="medline">38769463</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>Thirunavukarasu</surname><given-names>AJ</given-names> </name><name name-style="western"><surname>Ting</surname><given-names>DSJ</given-names> </name><name name-style="western"><surname>Elangovan</surname><given-names>K</given-names> </name><name name-style="western"><surname>Gutierrez</surname><given-names>L</given-names> </name><name name-style="western"><surname>Tan</surname><given-names>TF</given-names> </name><name name-style="western"><surname>Ting</surname><given-names>DSW</given-names> </name></person-group><article-title>Large language models in medicine</article-title><source>Nat Med</source><year>2023</year><month>08</month><volume>29</volume><issue>8</issue><fpage>1930</fpage><lpage>1940</lpage><pub-id pub-id-type="doi">10.1038/s41591-023-02448-8</pub-id><pub-id pub-id-type="medline">37460753</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Wachter</surname><given-names>RM</given-names> </name><name name-style="western"><surname>Brynjolfsson</surname><given-names>E</given-names> </name></person-group><article-title>Will generative artificial intelligence deliver on its promise in health care?</article-title><source>JAMA</source><year>2024</year><month>01</month><day>2</day><volume>331</volume><issue>1</issue><fpage>65</fpage><lpage>69</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.25054</pub-id><pub-id pub-id-type="medline">38032660</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>Howell</surname><given-names>MD</given-names> </name><name name-style="western"><surname>Corrado</surname><given-names>GS</given-names> </name><name name-style="western"><surname>DeSalvo</surname><given-names>KB</given-names> </name></person-group><article-title>Three epochs of artificial intelligence in health care</article-title><source>JAMA</source><year>2024</year><month>01</month><day>16</day><volume>331</volume><issue>3</issue><fpage>242</fpage><lpage>244</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.25057</pub-id><pub-id pub-id-type="medline">38227029</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>Minssen</surname><given-names>T</given-names> </name><name name-style="western"><surname>Vayena</surname><given-names>E</given-names> </name><name name-style="western"><surname>Cohen</surname><given-names>IG</given-names> </name></person-group><article-title>The challenges for regulating medical use of ChatGPT and other large language models</article-title><source>JAMA</source><year>2023</year><month>07</month><day>25</day><volume>330</volume><issue>4</issue><fpage>315</fpage><lpage>316</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.9651</pub-id><pub-id pub-id-type="medline">37410482</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>Nosowsky</surname><given-names>R</given-names> </name><name name-style="western"><surname>Giordano</surname><given-names>TJ</given-names> </name></person-group><article-title>The Health Insurance Portability and Accountability Act of 1996 (HIPAA) privacy rule: implications for clinical research</article-title><source>Annu Rev Med</source><year>2006</year><volume>57</volume><issue>1</issue><fpage>575</fpage><lpage>590</lpage><pub-id pub-id-type="doi">10.1146/annurev.med.57.121304.131257</pub-id><pub-id pub-id-type="medline">16409167</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>Chen</surname><given-names>X</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>L</given-names> </name><name name-style="western"><surname>You</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Evaluating and enhancing large language models&#x2019; performance in domain-specific medicine: development and usability study with DocOA</article-title><source>J Med Internet Res</source><year>2024</year><month>07</month><day>22</day><volume>26</volume><fpage>e58158</fpage><pub-id pub-id-type="doi">10.2196/58158</pub-id><pub-id pub-id-type="medline">38833165</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>Tian</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Gan</surname><given-names>R</given-names> </name><name name-style="western"><surname>Song</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>Y</given-names> </name></person-group><article-title>ChiMed-GPT: a Chinese medical large language model with full training regime and better alignment to human preferences</article-title><source>Proc Annu Meet Assoc Comput Linguist</source><year>2024</year><fpage>7156</fpage><lpage>7173</lpage><pub-id pub-id-type="doi">10.18653/v1/2024.acl-long.386</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>Hou</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Patel</surname><given-names>J</given-names> </name><name name-style="western"><surname>Dai</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Benchmarking of large language models for the Dental Admission Test</article-title><source>Health Data Sci</source><year>2025</year><volume>5</volume><fpage>0250</fpage><pub-id pub-id-type="doi">10.34133/hds.0250</pub-id><pub-id pub-id-type="medline">40170799</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Moor</surname><given-names>MD</given-names> </name></person-group><source>MedGPT</source><year>2024</year><access-date>2025-08-12</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://chat.openai.com/g/g-jxm5ljJmo-medgpt">https://chat.openai.com/g/g-jxm5ljJmo-medgpt</ext-link></comment></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Su</surname><given-names>JJ</given-names> </name><name name-style="western"><surname>Chan</surname><given-names>MHS</given-names> </name><name name-style="western"><surname>Ghisi</surname><given-names>G de M</given-names> </name><etal/></person-group><article-title>Real-world mobile health implementation and patient safety: multicenter qualitative study</article-title><source>J Med Internet Res</source><year>2025</year><month>04</month><day>29</day><volume>27</volume><fpage>e71086</fpage><pub-id pub-id-type="doi">10.2196/71086</pub-id><pub-id pub-id-type="medline">40299494</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>Yun</surname><given-names>HS</given-names> </name><name name-style="western"><surname>Bickmore</surname><given-names>T</given-names> </name></person-group><article-title>Online health information-seeking in the era of large language models: cross-sectional web-based survey study</article-title><source>J Med Internet Res</source><year>2025</year><month>03</month><day>31</day><volume>27</volume><fpage>e68560</fpage><pub-id pub-id-type="doi">10.2196/68560</pub-id><pub-id pub-id-type="medline">40163112</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Yim</surname><given-names>D</given-names> </name><name name-style="western"><surname>Khuntia</surname><given-names>J</given-names> </name><name name-style="western"><surname>Parameswaran</surname><given-names>V</given-names> </name><name name-style="western"><surname>Meyers</surname><given-names>A</given-names> </name></person-group><article-title>Preliminary evidence of the use of generative AI in health care clinical services: systematic narrative review</article-title><source>JMIR Med Inform</source><year>2024</year><month>03</month><day>20</day><volume>12</volume><fpage>e52073</fpage><pub-id pub-id-type="doi">10.2196/52073</pub-id><pub-id pub-id-type="medline">38506918</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Morjaria</surname><given-names>L</given-names> </name><name name-style="western"><surname>Gandhi</surname><given-names>B</given-names> </name><name name-style="western"><surname>Haider</surname><given-names>N</given-names> </name><name name-style="western"><surname>Mellon</surname><given-names>M</given-names> </name><name name-style="western"><surname>Sibbald</surname><given-names>M</given-names> </name></person-group><article-title>Applications of generative artificial intelligence in electronic medical records: a scoping review</article-title><source>Information</source><year>2025</year><volume>16</volume><issue>4</issue><fpage>284</fpage><pub-id pub-id-type="doi">10.3390/info16040284</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>Yazdanian</surname><given-names>A</given-names> </name><name name-style="western"><surname>Mehdizadeh</surname><given-names>H</given-names> </name><name name-style="western"><surname>Balaghafari</surname><given-names>A</given-names> </name><name name-style="western"><surname>Kahouei</surname><given-names>M</given-names> </name><name name-style="western"><surname>Masoudinezhad</surname><given-names>M</given-names> </name></person-group><article-title>Mobile-based self-management application requirements for patients with gastric cancer: quantitative descriptive study of specialist and patient perspectives</article-title><source>JMIR Cancer</source><year>2022</year><month>04</month><day>27</day><volume>8</volume><issue>2</issue><fpage>e36788</fpage><pub-id pub-id-type="doi">10.2196/36788</pub-id><pub-id pub-id-type="medline">35475920</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>Lanssens</surname><given-names>D</given-names> </name><name name-style="western"><surname>Vandenberk</surname><given-names>T</given-names> </name><name name-style="western"><surname>Storms</surname><given-names>V</given-names> </name><etal/></person-group><article-title>Changes in intrapersonal factors of participants in the pregnancy remote monitoring study who are at risk for pregnancy-induced hypertension: descriptive quantitative study</article-title><source>J Med Internet Res</source><year>2023</year><month>09</month><day>6</day><volume>25</volume><fpage>e42686</fpage><pub-id pub-id-type="doi">10.2196/42686</pub-id><pub-id pub-id-type="medline">37672324</pub-id></nlm-citation></ref><ref id="ref26"><label>26</label><nlm-citation citation-type="other"><person-group person-group-type="author"><name name-style="western"><surname>Allahyari</surname><given-names>M</given-names> </name><name name-style="western"><surname>Pouriyeh</surname><given-names>S</given-names> </name><name name-style="western"><surname>Assefi</surname><given-names>M</given-names> </name><name name-style="western"><surname>Safaei</surname><given-names>S</given-names> </name></person-group><article-title>A brief survey of text mining: classification, clustering and extraction techniques</article-title><source>arXiv</source><comment>Preprint posted online on  Jul 10, 2017</comment><pub-id pub-id-type="doi">10.48550/arXiv.1707.02919</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="book"><person-group person-group-type="editor"><name name-style="western"><surname>Srivastava</surname><given-names>AN</given-names> </name><name name-style="western"><surname>Sahami</surname><given-names>M</given-names> </name></person-group><source>Text Mining: Classification, Clustering, and Applications</source><year>2009</year><publisher-name>CRC Press</publisher-name><pub-id pub-id-type="doi">10.1201/9781420059458</pub-id><pub-id pub-id-type="other">9780429191985</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>Hendrickx</surname><given-names>I</given-names> </name><name name-style="western"><surname>Voets</surname><given-names>T</given-names> </name><name name-style="western"><surname>van Dyk</surname><given-names>P</given-names> </name><name name-style="western"><surname>Kool</surname><given-names>RB</given-names> </name></person-group><article-title>Using text mining techniques to identify health care providers with patient safety problems: exploratory study</article-title><source>J Med Internet Res</source><year>2021</year><month>07</month><day>27</day><volume>23</volume><issue>7</issue><fpage>e19064</fpage><pub-id pub-id-type="doi">10.2196/19064</pub-id><pub-id pub-id-type="medline">34313604</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="web"><article-title>Presidio: data protection and de-identification SDK</article-title><source>Microsoft Presidio</source><access-date>2025-08-12</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://microsoft.github.io/presidio/">https://microsoft.github.io/presidio/</ext-link></comment></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>Chen</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Esmaeilzadeh</surname><given-names>P</given-names> </name></person-group><article-title>Generative AI in medical practice: in-depth exploration of privacy and security challenges</article-title><source>J Med Internet Res</source><year>2024</year><month>03</month><day>8</day><volume>26</volume><fpage>e53008</fpage><pub-id pub-id-type="doi">10.2196/53008</pub-id><pub-id pub-id-type="medline">38457208</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>Nakikj</surname><given-names>D</given-names> </name><name name-style="western"><surname>Kreda</surname><given-names>D</given-names> </name><name name-style="western"><surname>Luthria</surname><given-names>K</given-names> </name><name name-style="western"><surname>Gehlenborg</surname><given-names>N</given-names> </name></person-group><article-title>Patient-generated collections for organizing electronic health record data to elevate personal meaning, improve actionability, and support patient-health care provider communication: think-aloud evaluation study</article-title><source>JMIR Hum Factors</source><year>2025</year><month>02</month><day>3</day><volume>12</volume><issue>1</issue><fpage>e50331</fpage><pub-id pub-id-type="doi">10.2196/50331</pub-id><pub-id pub-id-type="medline">39899851</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="other"><person-group person-group-type="author"><name name-style="western"><surname>Ozdemir</surname><given-names>DY</given-names> </name><name name-style="western"><surname>Ayvaci</surname><given-names>M</given-names> </name><name name-style="western"><surname>Zentner</surname><given-names>A</given-names> </name></person-group><article-title>What people think of machines as doctors: unveiling the value of gen-AI for e-Health</article-title><source>SSRN</source><year>2024</year><month>03</month><day>21</day><pub-id pub-id-type="doi">10.2139/ssrn.4765222</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Supplemental materials for model specification, topic classification, and sensitivity detection.</p><media xlink:href="jmir_v27i1e76941_app1.docx" xlink:title="DOCX File, 1163 KB"/></supplementary-material></app-group></back></article>