<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v14i1e96129</article-id>
      <article-id pub-id-type="pmid">42398927</article-id>
      <article-id pub-id-type="doi">10.2196/96129</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Multimodule Human–Artificial Intelligence Collaboration Pipeline for Large Language Model–Assisted Thematic Analysis Across Digital Health Interview Studies: Comparative Evaluation Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Coristine</surname>
            <given-names>Andrew</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Chen</surname>
            <given-names>Mei</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes" equal-contrib="yes">
          <name name-style="western">
            <surname>Bai</surname>
            <given-names>Yunbing</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Arizona Center for Telemedicine and Digital Health</institution>
            <institution>College of Medicine</institution>
            <institution>University of Arizona</institution>
            <addr-line>1501 N Campbell Ave AHSL 1156</addr-line>
            <addr-line>Tucson, AZ, 85724-5105</addr-line>
            <country>United States</country>
            <phone>1 5206263944</phone>
            <email>yunbing@arizona.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0005-4910-4497</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Finkelstein</surname>
            <given-names>Joseph</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8084-7441</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Arizona Center for Telemedicine and Digital Health</institution>
        <institution>College of Medicine</institution>
        <institution>University of Arizona</institution>
        <addr-line>Tucson, AZ</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Yunbing Bai <email>yunbing@arizona.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>3</day>
        <month>7</month>
        <year>2026</year>
      </pub-date>
      <volume>14</volume>
      <elocation-id>e96129</elocation-id>
      <history>
        <date date-type="received">
          <day>25</day>
          <month>3</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>23</day>
          <month>4</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>8</day>
          <month>6</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>9</day>
          <month>6</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Yunbing Bai, Joseph Finkelstein. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 03.07.2026.</copyright-statement>
      <copyright-year>2026</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2026/1/e96129" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Qualitative thematic analysis is widely used in health research to examine patient experiences and inform the refinement of digital health interventions, but it is time- and labor-intensive. Large language models (LLMs) may help accelerate this process, yet their performance may depend not only on the model itself but also on how the analytic workflow is structured. Current evidence remains limited on how different LLMs perform across multistage thematic analysis workflows and across multiple health-related qualitative datasets.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aimed to evaluate a modular human–artificial intelligence (AI) collaboration pipeline for LLM-assisted thematic analysis and compare how model choice and workflow strategy influence alignment between AI-generated and human-generated themes across 3 qualitative health studies.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The framework was applied to analyze deidentified semistructured interview transcripts from 3 completed qualitative health studies involving patients with interstitial lung disease, postural orthostatic tachycardia syndrome, and chronic obstructive pulmonary disease. Three LLMs were compared: Gemini (Gemini 3 Pro), ChatGPT (GPT-5.2-thinking), and Opus (version 4.6). The workflow separated analysis into code extraction, code combination, and theme generation, and 5 strategies were tested. AI-generated themes were embedded using sentence-t5-xxl and compared with human-generated themes using cosine similarity after alignment with Hungarian and Greedy matching. Runtime and output-format consistency were also examined.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Output volume differed substantially by model. Gemini generated the fewest codes and themes, while ChatGPT showed a similar but higher output ceiling. Opus produced the largest and most variable codebooks and theme sets. Across the 3 studies, Opus showed the strongest and most consistent alignment with human-generated themes, with the best cosine similarity scores observed in postural orthostatic tachycardia syndrome–direct coding (mean 0.893, SD 0.041), chronic obstructive pulmonary disease–direct grouping (mean 0.891, SD 0.027), and interstitial lung disease–L3 (mean 0.889, SD 0.032). ChatGPT was competitive in selected settings, whereas Gemini generally produced slightly lower similarity scores but had the shortest runtime. ChatGPT and Opus also showed better formatting consistency and workflow usability than Gemini.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>A modular human-AI pipeline can support thematic analysis across multiple digital health interview studies, but performance depends strongly on both model choice and workflow design. Opus produced the most consistently human-aligned themes, while Gemini and ChatGPT showed different trade-offs in speed, fidelity, and usability. These findings support the use of LLMs as structured, human-supervised analytic assistants rather than replacements for qualitative researchers.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>large language model</kwd>
        <kwd>LLM</kwd>
        <kwd>generative AI</kwd>
        <kwd>thematic analysis</kwd>
        <kwd>qualitative study</kwd>
        <kwd>human-AI collaboration</kwd>
        <kwd>health informatics</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Qualitative methods are widely used in health research to examine patient experiences, identify barriers and facilitators to care, and guide the refinement of clinical and digital health interventions. Among these methods, thematic analysis is especially useful because it provides a flexible yet systematic approach for identifying, organizing, and interpreting patterns of meaning across textual data. Thematic analysis involves systematically identifying patterns in qualitative data through iterative coding and abstraction. For example, in a patient interview, a participant might state, “I get short of breath when walking even short distances, and it makes me anxious to leave the house.” A researcher may assign codes such as activity limitation<italic>,</italic> dyspnea<italic>,</italic> and anxiety for symptoms. Across multiple interviews, similar codes are grouped and refined into broader themes, such as the impact of symptoms on daily functioning or emotional responses to chronic illness. This process is inherently interpretive and requires balancing detail preservation with conceptual abstraction, making it both time-intensive and dependent on analyst judgment.</p>
      <p>Foundational and health-oriented methodological literature emphasizes that rigorous thematic analysis depends on transparency, traceability, and a clear fit between analytic procedures and research aims [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. In multidisciplinary health research teams, structured approaches such as the framework method can further improve consistency and auditability when working with large collections of interview transcripts. At the same time, qualitative analysis remains labor-intensive, requiring repeated transcript review, iterative code development, comparison across cases, and abstraction from codes to higher-level themes. These demands can make rigorous analysis difficult to scale, particularly in digital health research, where interview-based usability and implementation studies often need timely feedback to support intervention refinement. Prior studies of home telemanagement and rehabilitation technologies have further shown that understanding patient experiences, usability concerns, and practical barriers to participation is important for designing patient-centered systems for home use [<xref ref-type="bibr" rid="ref4">4</xref>-<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      <p>The use of artificial intelligence (AI) to support qualitative data analysis is not entirely new, but the recent emergence of large language models (LLMs) has substantially renewed interest in this area. Recent overviews show that AI-supported qualitative analysis has been applied across inductive and deductive coding, thematic analysis, discourse analysis, and analysis of large text corpora, suggesting that the current LLM wave should be understood as an acceleration of a longer methodological trajectory rather than an entirely new phenomenon [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. What has changed is accessibility: contemporary LLMs can produce fluent codes, summaries, and theme descriptions directly from natural language prompts, making them attractive to researchers. However, this accessibility also raises the risk of superficial or poorly governed use if methodological safeguards are not clearly specified.</p>
      <p>Recent literature on LLM-assisted qualitative analysis presents a mixed picture of promise and caution. Recent empirical and methodological studies have examined LLMs for qualitative coding, content analysis, grounded theory, thematic analysis, and thematic summarization in health and social science research [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref26">26</xref>]. These studies suggest that LLMs can support coding, theme generation, and synthesis, particularly when prompts are structured, and outputs are reviewed by human researchers [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. For example, recent work has compared GPT-4 with human researchers in qualitative health care data analysis, evaluated LLMs for thematic summarization in qualitative health research, and tested ChatGPT-based protocols for thematic analysis and grounded theory [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. At the same time, these studies consistently emphasize the need for human oversight, transparent prompts, validation procedures, and caution when interpreting AI-generated themes [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. Taken together, the literature suggests that LLMs can contribute meaningfully to qualitative workflows, but their usefulness depends heavily on the dataset, task, model, prompt design, and workflow structure.</p>
      <p>At the same time, more recent studies also highlight important limitations that are directly relevant to thematic analysis. Sakaguchi and colleagues [<xref ref-type="bibr" rid="ref18">18</xref>] found that ChatGPT with GPT-4 achieved high agreement with human researchers for more descriptive themes in Japanese interview data, but its performance dropped markedly for themes requiring deeper cultural and emotional interpretation, with some agreement rates around 30%. Wen and colleagues [<xref ref-type="bibr" rid="ref19">19</xref>] similarly showed that model choice matters: in a real-world charity-sector case study, GPT-4o achieved substantial agreement with human coders in multilabel categorization, whereas GPT-4o-mini showed only moderate agreement and greater instability across runs. These findings reinforce concerns that LLM outputs may be more reliable for surface-level pattern detection than for context-dependent interpretation, especially when cultural nuance, ambiguity, or subtle experiential distinctions are important. More critical methodological discussions have therefore argued that generative AI in qualitative data analysis introduces epistemic risks and should be treated as an assistive, human-supervised analytic tool rather than an autonomous interpreter [<xref ref-type="bibr" rid="ref20">20</xref>].</p>
      <p>Despite this growing literature, several gaps remain. First, many studies evaluate a single model, a single dataset, or a single prompting approach, which makes it difficult to separate model-specific behavior from workflow-specific effects. Second, much of the literature focuses on direct or near end-to-end prompting, with less attention to how multistage workflows may preserve or distort traceability as data move from transcripts to codes and from codes to themes. Third, evaluation practices remain heterogeneous: some studies emphasize feasibility, efficiency, or human comparison, whereas others compare thematic overlap or semantic similarity [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. Few studies directly compare alternative workflow structures across multiple qualitative health datasets under standardized conditions. These gaps are especially important in health-related qualitative research, where less frequent but clinically meaningful concerns may be lost if models overcompress the data or privilege more common patterns [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref25">25</xref>].</p>
      <p>Building on this literature, this study evaluates a modular human-AI collaboration framework for thematic analysis across 3 completed qualitative health studies involving patients with interstitial lung disease (ILD), postural orthostatic tachycardia syndrome (POTS), and chronic obstructive pulmonary disease (COPD) [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. The framework decomposes thematic analysis into 3 discrete subtasks—code extraction, code combination, and theme generation—each conducted in independent LLM sessions to reduce context overload and improve traceability [<xref ref-type="bibr" rid="ref30">30</xref>]. Using this framework, we compare 3 widely used LLM platforms (ChatGPT, Opus, and Gemini) and 5 workflow strategies, including both hierarchical and direct approaches to code consolidation and theme development [<xref ref-type="bibr" rid="ref31">31</xref>-<xref ref-type="bibr" rid="ref33">33</xref>]. AI-generated themes are then benchmarked against human-generated themes from the original studies using embedding-based semantic similarity and systematic alignment. By doing so, this study aims to clarify how model choice and workflow structure influence thematic fidelity, how iterative consolidation affects information retention, and what practical trade-offs emerge when implementing LLM-supported qualitative analysis in digital health research.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Model Selection</title>
        <p>In this study, we selected 3 models from 3 widely used LLM platforms for evaluation and comparison. Specifically, we evaluated ChatGPT with GPT-5.2-thinking (with extended thinking; OpenAI), Opus (version 4.6; Anthropic), and Gemini (Gemini 3 Pro; Google) [<xref ref-type="bibr" rid="ref31">31</xref>-<xref ref-type="bibr" rid="ref33">33</xref>]. During the study window, extended thinking modes were available for ChatGPT and Opus but not for Gemini; therefore, each platform was evaluated using the relevant configuration available through its consumer-facing web interface at the time of analysis.</p>
        <p>We intentionally used the consumer-facing web interfaces rather than the corresponding application programming interfaces (APIs), and each model-workflow condition was executed once using a standardized prompt and independent conversation, because the goal of this study was to evaluate a practical, researcher-facing workflow under conditions that resemble how many qualitative researchers currently interact with these tools in applied settings, rather than to benchmark API-level performance under fully programmatic control. This choice also allowed direct assessment of operational factors relevant to multistep qualitative analysis, including conversation organization, output exportability, and adherence to structured prompts within the native user interfaces.</p>
        <p>All data collection and model interactions were conducted within a fixed study window from February 10, 2026, to March 30, 2026, to provide a temporal anchor for the model versions available at the time of evaluation. To reduce variability related to prior interaction history, all analyses were performed using newly registered accounts with paid personal subscriptions (ChatGPT Plus, Claude Pro, and Gemini Pro). Where available, settings that allow models to reference prior conversations were disabled (eg, “Reference chat history” in ChatGPT). Each analytical subtask was performed in a new, independent conversation so that no model could rely on prior session memory. The same standardized prompts, workflow logic, and transcript inputs were applied across all 3 platforms.</p>
      </sec>
      <sec>
        <title>Human-AI Collaboration Framework</title>
        <p>To conduct thematic analysis, we applied a human-AI collaboration framework developed in our prior study [<xref ref-type="bibr" rid="ref30">30</xref>]. In this framework, the overall analytical workflow is decomposed into a series of discrete, model-specific subtasks, each executed by a specialized LLM module. Each subtask is performed within an independent LLM conversation, and modules do not share memory or contextual knowledge across sessions. This modular architecture reduces per-module complexity, mitigates data loss caused by context-window limitations, lowers computational overhead, and improves the consistency and quality of the generated outputs. The framework consists of 3 specialized modules: a code extraction module, a code combination module, and a theme generation module. <xref rid="figure1" ref-type="fig">Figure 1</xref> shows the prompts for the 3 modules.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Verbatim standardized prompts used for the 3 modules in the modular human–artificial intelligence collaboration pipeline for large language model–assisted thematic analysis. This figure reproduces the exact prompt wording used across all analyses for the code extraction module, code combination module, and theme generation module. The prompts were applied consistently across ChatGPT (GPT-5.2-thinking), Opus (version 4.6), and Gemini (Gemini 3 Pro). The code extraction prompt instructs the model to identify transcript-level qualitative codes, assign concise titles, generate approximately 80-word descriptions, and cite question number–based supporting evidence. The code combination prompt instructs the model to merge semantically overlapping codes while preserving traceability to source code identifiers and standardized formatting. The theme generation prompt instructs the model to group codes into nonoverlapping, human-style qualitative themes with explicit rules for naming, definition structure, coverage, and source attribution.</p>
          </caption>
          <graphic xlink:href="medinform_v14i1e96129_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>The code extraction module is responsible for identifying all relevant qualitative codes from an input transcript. A standardized prompt is provided alongside the transcript, instructing the model to identify as many relevant codes as possible, assign each code a concise name limited to 10 words, and produce an approximately 80-word description for each code. The prompt also requires the model to cite the corresponding interview question number as supporting evidence, use clear and concrete language, avoid clichés or vague generalizations, and generate outputs in a predefined standardized format.</p>
        <p>The code combination module consolidates overlapping or redundant codes in order to produce a more coherent and streamlined codebook. Using another standardized prompt, the model is instructed to group codes with substantially similar titles and descriptions and generate a new name and definition for each merged group. For codes without close counterparts, the original title and description are retained. To ensure traceability throughout the analysis process, the module records the original code number or numbers associated with each merged group, and the final results are produced in the same prescribed output format.</p>
        <p>The theme generation module derives higher-level themes from the consolidated codebook. Its prompt directs the model to cluster codes and their descriptions into themes that reflect conventions commonly used in human-authored qualitative research. Detailed guidelines regarding length constraints, thematic structure, and stylistic requirements are embedded in the prompt to guide the generation process. Each code must be assigned to exactly 1 theme, ensuring complete coverage of the dataset without overlapping. The final output consists of a comprehensive list of themes, with each theme accompanied by a title, a descriptive summary, and the original code numbers associated with the codes it subsumes.</p>
      </sec>
      <sec>
        <title>Strategies for Using the Framework</title>
        <p><xref rid="figure2" ref-type="fig">Figure 2</xref> illustrates the workflow of the human-AI collaboration framework. The input for our framework would be a set of transcripts of interviews. Each transcript was uploaded as a .txt file into a new LLM conversation together with the standardized prompt for the code extraction module. Initiating a separate conversation for each transcript ensured that the interview context was preserved while respecting token-length constraints, maintained uniform analytical conditions, and prevented contamination from prior interactions.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Overview of the multistage human–artificial intelligence collaboration pipeline and the 5 workflow strategies evaluated for large language model–assisted thematic analysis across different digital health qualitative interview studies. The framework was applied to deidentified semistructured interview transcripts, all drawn from previously completed telerehabilitation-related studies. The pipeline decomposes thematic analysis into 3 sequential large language model–assisted subtasks performed in independent conversations: code extraction, code combination, and theme generation. In the hierarchical workflows, transcripts are first analyzed individually to produce an L1 codebook, followed by iterative consolidation into an L2 and L3 codebook before theme generation. In the direct workflows, either all transcripts are analyzed together once to produce a DC codebook or the L1-codebook is submitted directly for 1-step consolidation to produce a DG codebook. Each resulting codebook (L1, L2, L3, DC, and DG) is then independently submitted to the theme generation module to produce a corresponding theme set. DC: direct coding; DG: direct grouping; L1: layer 1; L2: layer 2; L3: layer 3.</p>
          </caption>
          <graphic xlink:href="medinform_v14i1e96129_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>After code extraction, one researcher (YB) collected the model-generated codes in text files. To reduce manual effort and the risk of identifier transcription errors, a short Python script (Python Software Foundation) was used solely to assign unique identifiers to the collected codes and generate 2 structured text files: a layer 1 (L1) codebook containing the code number, name, and definition for each code, and a quote-trace file containing the code number, code name, and corresponding interview question numbers. This deterministic organizational step did not modify code content, conduct qualitative analysis, or involve programmatic interaction with the LLM platforms, and it could be performed manually if needed.</p>
        <p>To reduce redundancy, the code combination module was applied. The L1 codebook was divided into 4 subcodebooks to control the input length for each LLM conversation; each subcodebook contained the codes and descriptions derived from 4 to 5 transcripts. This partition was selected as a practical heuristic to balance input-length constraints and codebook diversity. Specifically, grouping 4-5 transcripts ensured that each subcodebook remained within a manageable size for the consumer-facing web interfaces used in this study, while still preserving sufficient variation in codes to support meaningful consolidation at the L2 stage. This approach allowed iterative merging without exceeding response length limits or overly compressing heterogeneous concepts in a single step.</p>
        <p>These 4 subcodebooks were submitted independently to new LLM conversations together with the standardized code combination module prompt. The resulting outputs were then collected and processed to form the layer 2 (L2) codebook. To further consolidate overlapping codes, the L2 codebook was submitted again to the code combination module, producing the layer 3 (L3) codebook. Throughout this iterative consolidation process, parent-layer code numbers were preserved to maintain traceability between newly generated codes and their original source quotes.</p>
        <p>In addition to this hierarchical workflow, we evaluated 2 straightforward strategies that did not impose input length controls. In the first approach, all transcripts were merged into a single txt file and submitted directly to the code extraction module, producing a direct coding (DC) codebook. In the second approach, the L1 codebook was submitted directly to the code combination module without dividing it into subcodebooks, producing a direct grouping (DG) codebook. Finally, all 5 resulting codebooks—L1, L2, L3, DG, and DC—were independently submitted to the theme generation module in separate LLM conversations using the same standardized prompt. The themes generated were then used for subsequent evaluation and comparison across the different analytical strategies.</p>
      </sec>
      <sec>
        <title>Semistructured Qualitative Interviews</title>
        <p>The semistructured qualitative interviews were collected as part of 3 usability studies using a mixed methods design [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>]. The studies aimed at assessing usability, attitudes, and acceptance of home-based telerehabilitation systems in patients with 1 of 3 conditions: COPD, POTS, or related dysautonomia, and ILD. All study participants were aged 18 years or older. They also needed the ability to complete study procedures, including usability testing and a semistructured interview. Individuals were excluded if they had medical conditions that could increase risk during the exercise‑related usability evaluation, including unstable angina, uncontrolled hypertension, a recent myocardial infarction, pacemaker use, painful or unstable bony metastases, recent skeletal fractures, or any other condition that, in the clinical or research team’s judgment, would make participation unsafe. Enrolled participants attended a single, 1‑hour, in‑person visit. After providing informed consent, research staff demonstrated the telerehabilitation system and supervised a practice session and then administered a sociodemographic questionnaire. Usability testing comprised 3 standardized tasks completed independently: logging into the system, completing a survey, and reviewing and performing an exercise routine. Analyses were stratified by the underlying medical conditions.</p>
        <p>After usability testing, participants took part in a semistructured interview with open‑ended questions to explore their perceptions of the system and its potential for home‑based symptom management. Interviews were transcribed verbatim and deidentified. The qualitative interview data were analyzed using thematic analysis following Braun and Clarke’s [<xref ref-type="bibr" rid="ref1">1</xref>] 6-phase process to organize, identify, and interpret key patterns and themes. The qualitative analysis team comprised a qualitative researcher (Aileen Gabriel) and a clinician-scientist (JF). The disagreements were resolved by a clinical informatician familiar with qualitative analysis. The iterative analysis continued until all codes were finalized and disagreements were reconciled. The research team repeatedly reviewed transcripts to immerse themselves in the data; initial codes were generated inductively through open coding, iteratively refined, and grouped into broader categories to capture patterns across participants. These categories were then synthesized into themes representing key aspects of participant experiences [<xref ref-type="bibr" rid="ref27">27</xref>-<xref ref-type="bibr" rid="ref29">29</xref>].</p>
      </sec>
      <sec>
        <title>Evaluation</title>
        <p>For evaluation, we used the original deidentified interview transcripts and the final human-generated thematic analysis results from the 3 source studies. The ILD dataset included 17 transcripts, for which the human analysis generated 169 codes and 7 themes. The POTS dataset included 15 transcripts, for which the human analysis generated 178 codes and 10 themes. The COPD dataset included 16 transcripts, for which the human analysis generated 261 codes and 6 themes. The original transcripts were submitted as input to the LLM-assisted workflow, and the corresponding human-generated themes served as the reference standard for evaluating framework-derived themes.</p>
        <p>All interview transcripts used in this study were deidentified and were not publicly available, published, or released before the present analysis. Therefore, direct exposure of the evaluated models to the source transcripts through publicly accessible training data is unlikely. The code extraction module prompt also included a study background field that was populated separately for each disease cohort. The exact verbatim text used for the ILD, POTS, and COPD datasets is provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p>
        <p>To quantitatively assess the similarity between human-generated themes and those produced by the LLM, we used the sentence-transformer model sentence-t5-xxl, which has demonstrated strong performance on sentence similarity tasks, to embed the theme texts into a 768-dimensional dense vector space [<xref ref-type="bibr" rid="ref34">34</xref>]. Because this model has a bounded maximum input length, we verified that all theme texts were below this limit; therefore, no truncation was applied during embedding. The resulting vectors were normalized to remove length bias and ensure that comparisons reflected semantic similarity rather than differences in text magnitude. Cosine similarity was then calculated for each pair of human and LLM theme vectors. Cosine similarity scores range from −1 to +1 and indicate the degree to which 2 texts describe conceptually similar content, with higher values representing greater semantic similarity. In addition, to verify traceability fidelity, we developed a Python script to validate whether each propagated parent-layer code identifier referenced an existing valid code in the immediately preceding codebook layer. The number of themes identified by humans and by the LLM often differed. To compare unequal theme sets while preserving both alignment quality and complete theme coverage, we used a 2-stage matching procedure combining the Hungarian algorithm and a Greedy nearest-neighbor assignment [<xref ref-type="bibr" rid="ref35">35</xref>,<xref ref-type="bibr" rid="ref36">36</xref>]. <xref rid="figure3" ref-type="fig">Figure 3</xref> illustrates this alignment process.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Themes alignment procedure is used to compare artificial intelligence (AI)–generated themes with human-generated reference themes across different qualitative health interview studies. This schematic illustrates the 2-step matching approach used after generating themes. First, theme descriptions from the human analysis and from each AI-generated output were embedded into 768-dimensional vector spaces using sentence-t5-xxl, and pairwise cosine similarity was calculated. Because the number of themes differed between the human and AI outputs across models and workflow strategies, the Hungarian algorithm was first applied to create a globally optimal one-to-one alignment between the smaller theme set and a subset of the larger theme set. Any remaining unmatched themes in the larger set were then assigned using a Greedy algorithm to the most similar theme in the smaller set. This combined procedure ensured that all themes were matched while maximizing overall semantic similarity.</p>
          </caption>
          <graphic xlink:href="medinform_v14i1e96129_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p>First, the Hungarian algorithm was applied to the cosine similarity matrix to identify the globally optimal one-to-one alignment between the smaller theme set and an equally sized subset of the larger theme set, thereby establishing the primary bidirectional correspondences. Using the Hungarian algorithm alone would have excluded the remaining unmatched themes in the larger set from evaluation, which could bias the final similarity upward by omitting surplus themes with lower semantic similarity. Therefore, any remaining unmatched themes in the larger set were subsequently assigned to their most semantically similar theme in the smaller set using a Greedy nearest-neighbor procedure, ensuring that all themes contributed to the evaluation rather than discarding surplus themes. A Greedy-only strategy was not used because it does not enforce a globally optimal one-to-one primary alignment, and some themes in the opposite set may remain without any primary correspondence.</p>
        <p>When multiple themes from the larger set mapped to the same theme in the smaller set, the cosine similarity values for those mappings were averaged rather than retaining only the single highest-scoring match. As a result, generating additional themes did not inherently improve the final score; extra weakly aligned themes could reduce the aggregate similarity. Basic statistical measures (average, standard deviation, maximum, median, and minimum) were then calculated for the resulting cosine similarity scores.</p>
        <p>Processing time was measured manually using a digital clock or stopwatch. Timing began when the prompt and input file were submitted through the web interface and ended when the model completed its full response. Therefore, the recorded time represents end-user wall-clock processing time, including web interface latency, model response generation, and streaming time, rather than isolated model inference time. For theme generation tasks, processing time was measured 3 times, once for each study dataset. For L1 code extraction, 5 transcripts were randomly selected from the 48 available transcripts, and the corresponding extraction tasks were timed for each model. For the other tasks, processing time was measured across 5 randomly selected observations. Reported values are presented as mean (SD) in seconds.</p>
        <p>We also conducted a brief descriptive assessment of output format consistency and workflow management. Format deviations were defined as responses that did not follow the prompt-specified structure and required manual correction before downstream processing, such as missing required fields, inconsistent numbering, omitted source or parent-code identifiers, or unrequested formatting changes. One researcher (YB) reviewed the generated outputs and recorded distinct format patterns. Workflow management was assessed descriptively based on whether the web interface supported project-level organization, easy tracking of multiple conversations, and convenient copying or exporting of outputs. Interrater agreement was not assessed because this was a practical workflow observation rather than a formal usability evaluation.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study did not involve human participants or the collection of identifiable private information. No patient identifiers were accessed, recorded, or analyzed, and no attempt was made to reidentify individuals. In accordance with JMIR guidelines, this research does not meet the definition of human subjects research and was therefore exempt from institutional review board review and informed consent requirements. The study was conducted in compliance with applicable ethical standards for research using deidentified secondary data. The qualitative interview protocol was approved by the institutional review board of the University of Utah (protocol IRB_00168937).</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>For the AI-generated codes and themes, output volume varied substantially by strategy and model (<xref ref-type="table" rid="table1">Table 1</xref>). Gemini produced the fewest codes, with outputs remaining at approximately 10 codes per conversation, including definitions and traceability information, regardless of whether the task involved code extraction or code combination. ChatGPT showed a similar but higher capped pattern, producing approximately 25 codes per conversation across most tasks, except during the L2-to-L3 code combination step. In contrast, Opus did not exhibit a fixed-count pattern: extracted codes ranged from 15 to 60, and combined codes ranged from 43 to 153. These differences in code volume also shaped theme generation. Gemini produced fewer inputs for theme development and generated only 3-5 themes in several DC and DG settings, whereas Opus produced the largest codebooks and generally yielded the greatest number of themes. Python-based validation identified no invalid or hallucinated propagated code identifiers; all parent-layer code references were valid across models and consolidation stages.</p>
      <table-wrap position="float" id="table1">
        <label>Table 1</label>
        <caption>
          <p>Counts of artificial intelligence–generated codes and themes across 3 large language models, 5 workflow strategies, and 3 digital health qualitative interview datasets<sup>a</sup>.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="80"/>
          <col width="110"/>
          <col width="110"/>
          <col width="80"/>
          <col width="110"/>
          <col width="110"/>
          <col width="80"/>
          <col width="0"/>
          <col width="100"/>
          <col width="110"/>
          <col width="80"/>
          <thead>
            <tr valign="bottom">
              <td colspan="2">Category</td>
              <td colspan="3">ILD<sup>b</sup></td>
              <td colspan="4">POTS<sup>c</sup></td>
              <td colspan="3">COPD<sup>d</sup></td>
            </tr>
            <tr valign="top">
              <td colspan="2">
                <break/>
              </td>
              <td>Gemini</td>
              <td>ChatGPT</td>
              <td>Opus</td>
              <td>Gemini</td>
              <td>ChatGPT</td>
              <td>Opus</td>
              <td colspan="2">Gemini</td>
              <td>ChatGPT</td>
              <td>Opus</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="12">
                <bold>AI<sup>e</sup>-generated codes, n</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>L1<sup>f</sup></td>
              <td>185</td>
              <td>314</td>
              <td>395</td>
              <td>155</td>
              <td>303</td>
              <td>341</td>
              <td colspan="2">159</td>
              <td>295</td>
              <td>357</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>L2<sup>g</sup></td>
              <td>43</td>
              <td>114</td>
              <td>208</td>
              <td>46</td>
              <td>118</td>
              <td>167</td>
              <td colspan="2">58</td>
              <td>128</td>
              <td>201</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>L3<sup>h</sup></td>
              <td>15</td>
              <td>64</td>
              <td>129</td>
              <td>13</td>
              <td>52</td>
              <td>85</td>
              <td colspan="2">13</td>
              <td>78</td>
              <td>114</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>DC<sup>i</sup></td>
              <td>10</td>
              <td>24</td>
              <td>60</td>
              <td>12</td>
              <td>22</td>
              <td>47</td>
              <td colspan="2">10</td>
              <td>22</td>
              <td>53</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>DG<sup>j</sup></td>
              <td>10</td>
              <td>28</td>
              <td>153</td>
              <td>13</td>
              <td>25</td>
              <td>91</td>
              <td colspan="2">29</td>
              <td>50</td>
              <td>107</td>
            </tr>
            <tr valign="top">
              <td colspan="12">
                <bold>AI-generated themes, n</bold>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>L1</td>
              <td>11</td>
              <td>12</td>
              <td>23</td>
              <td>6</td>
              <td>12</td>
              <td>21</td>
              <td colspan="2">8</td>
              <td>15</td>
              <td>21</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>L2</td>
              <td>7</td>
              <td>9</td>
              <td>27</td>
              <td>8</td>
              <td>10</td>
              <td>24</td>
              <td colspan="2">8</td>
              <td>12</td>
              <td>20</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>L3</td>
              <td>6</td>
              <td>17</td>
              <td>15</td>
              <td>4</td>
              <td>10</td>
              <td>16</td>
              <td colspan="2">5</td>
              <td>13</td>
              <td>13</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>DC</td>
              <td>3</td>
              <td>7</td>
              <td>12</td>
              <td>3</td>
              <td>8</td>
              <td>13</td>
              <td colspan="2">4</td>
              <td>9</td>
              <td>11</td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td>DG</td>
              <td>4</td>
              <td>9</td>
              <td>17</td>
              <td>4</td>
              <td>7</td>
              <td>17</td>
              <td colspan="2">5</td>
              <td>14</td>
              <td>13</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table1fn1">
            <p><sup>a</sup>This table presents the numbers of codes and final themes generated by Gemini, ChatGPT, and Opus when the modular human–artificial intelligence thematic analysis pipeline was applied to deidentified semistructured interview transcripts from patients with interstitial lung disease (n=17), postural orthostatic tachycardia syndrome or related dysautonomia (n=15), and chronic obstructive pulmonary disease (n=16). Results are shown for 5 workflow strategies: L1, in which themes were generated from transcript-level extracted codes; L2 and L3, in which themes were generated after successive code combination stages; direct coding, in which combined transcripts were submitted directly for code extraction; and direct grouping, in which the L1 codebook was submitted directly for code consolidation before theme generation.</p>
          </fn>
          <fn id="table1fn2">
            <p><sup>b</sup>ILD: interstitial lung disease.</p>
          </fn>
          <fn id="table1fn3">
            <p><sup>c</sup>POTS: postural orthostatic tachycardia syndrome.</p>
          </fn>
          <fn id="table1fn4">
            <p><sup>d</sup>COPD: chronic obstructive pulmonary disease.</p>
          </fn>
          <fn id="table1fn5">
            <p><sup>e</sup>AI: artificial intelligence.</p>
          </fn>
          <fn id="table1fn6">
            <p><sup>f</sup>L1: layer 1.</p>
          </fn>
          <fn id="table1fn7">
            <p><sup>g</sup>L2: layer 2.</p>
          </fn>
          <fn id="table1fn8">
            <p><sup>h</sup>L3: layer 3.</p>
          </fn>
          <fn id="table1fn9">
            <p><sup>i</sup>DC: direct coding.</p>
          </fn>
          <fn id="table1fn10">
            <p><sup>j</sup>DG: direct grouping.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p>To examine whether these differences reflected broader output length behavior, we analyzed input and output word counts at each stage (<xref ref-type="table" rid="table2">Table 2</xref>). Input transcript lengths were comparable across models, but output lengths differed substantially. Gemini and ChatGPT produced relatively stable output lengths across tasks, with limited variation despite large differences in input size. This pattern suggests an effective output ceiling, where response length did not scale proportionally with input length. By contrast, Opus showed a more input-responsive pattern, with output length increasing in high-input settings such as DC and large codebook consolidation. This word count pattern supports the code and theme count findings, suggesting that Gemini and ChatGPT generated relatively bounded outputs, whereas Opus produced more variable and input-dependent results.</p>
      <p>Input and output length also influenced the runtime. <xref ref-type="table" rid="table3">Table 3</xref> summarizes end-user wall-clock processing time across models and workflow tasks. Gemini generally had the shortest processing time across most stages, while Opus required the longest time in code combination and theme generation tasks. The longer processing times for Opus are consistent with its larger and more variable outputs, which increased both response generation time and the amount of text carried into later workflow stages. Because processing time was measured through consumer-facing web interfaces, these values should be interpreted as practical workflow benchmarks rather than hardware-controlled inference-speed measurements.</p>
      <table-wrap position="float" id="table2">
        <label>Table 2</label>
        <caption>
          <p>Input and output word counts across models and workflow stages in the modular human–artificial intelligence thematic analysis pipeline<sup>a</sup>.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="180"/>
          <col width="100"/>
          <col width="20"/>
          <col width="100"/>
          <col width="20"/>
          <col width="100"/>
          <col width="20"/>
          <col width="100"/>
          <col width="20"/>
          <col width="100"/>
          <col width="20"/>
          <col width="100"/>
          <col width="20"/>
          <col width="100"/>
          <thead>
            <tr valign="top">
              <td>Task</td>
              <td colspan="4">Gemini word counts, n</td>
              <td colspan="4">ChatGPT word counts, n</td>
              <td colspan="4">Opus word counts, n</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>
                <break/>
              </td>
              <td colspan="2">Input</td>
              <td colspan="2">Output</td>
              <td colspan="2">Input</td>
              <td colspan="2">Output</td>
              <td colspan="2">Input</td>
              <td colspan="2">Output</td>
              <td>
                <break/>
              </td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>L1<sup>b</sup> code extraction (n=48 transcripts)</td>
              <td colspan="2">1023 (277)</td>
              <td colspan="2">1174 (281)</td>
              <td colspan="2">1023 (277)</td>
              <td colspan="2">1946 (428)</td>
              <td colspan="2">1023 (277)</td>
              <td colspan="2">2128 (401)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>DC<sup>c</sup> code extraction (n=3 datasets)</td>
              <td colspan="2">16,860 (1560)</td>
              <td colspan="2">1749 (232)</td>
              <td colspan="2">16,860 (1560)</td>
              <td colspan="2">2949 (154)</td>
              <td colspan="2">16,860 (1560)</td>
              <td colspan="2">8890 (391)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>L1-L2<sup>d</sup> code combination (n=12 subcodebooks)</td>
              <td colspan="2">3119 (551)</td>
              <td colspan="2">1015 (157)</td>
              <td colspan="2">6180 (792)</td>
              <td colspan="2">2754 (731)</td>
              <td colspan="2">6302 (982)</td>
              <td colspan="2">3914 (793)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>L2-L3<sup>e</sup> code combination (n=3 datasets)</td>
              <td colspan="2">3579 (345)</td>
              <td colspan="2">1164 (94)</td>
              <td colspan="2">10,310 (599)</td>
              <td colspan="2">5783 (797)</td>
              <td colspan="2">14,735 (1600)</td>
              <td colspan="2">8999 (1036)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>L1-DG<sup>f</sup> code combination (n=3 datasets)</td>
              <td colspan="2">12,474 (1257)</td>
              <td colspan="2">1605 (457)</td>
              <td colspan="2">24,720 (842)</td>
              <td colspan="2">2876 (492)</td>
              <td colspan="2">25,210 (2482)</td>
              <td colspan="2">8502 (1711)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>L1 theme generation (n=3 datasets)</td>
              <td colspan="2">12,474 (1257)</td>
              <td colspan="2">1210 (258)</td>
              <td colspan="2">24,720 (842)</td>
              <td colspan="2">1800 (70)</td>
              <td colspan="2">25,210 (2482)</td>
              <td colspan="2">3118 (150)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>L2 theme generation (n=3 datasets)</td>
              <td colspan="2">3579 (345)</td>
              <td colspan="2">870 (113)</td>
              <td colspan="2">10,310 (599)</td>
              <td colspan="2">1617 (442)</td>
              <td colspan="2">14,735 (1600)</td>
              <td colspan="2">3063 (319)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>L3 theme generation (n=3 datasets)</td>
              <td colspan="2">1053 (101)</td>
              <td colspan="2">463 (81)</td>
              <td colspan="2">5479 (771)</td>
              <td colspan="2">1680 (148)</td>
              <td colspan="2">8506 (982)</td>
              <td colspan="2">1839 (192)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>DC theme generation (n=3 datasets)</td>
              <td colspan="2">807 (176)</td>
              <td colspan="2">376 (25)</td>
              <td colspan="2">1855 (87)</td>
              <td colspan="2">828 (26)</td>
              <td colspan="2">3747 (478)</td>
              <td colspan="2">1437 (77)</td>
              <td>
                <break/>
              </td>
            </tr>
            <tr valign="top">
              <td>DG theme generation (n=3 datasets)</td>
              <td>3</td>
              <td colspan="2">1214 (500)</td>
              <td colspan="2">478 (21)</td>
              <td colspan="2">2404 (492)</td>
              <td colspan="2">958 (205)</td>
              <td colspan="2">7607 (1603)</td>
              <td colspan="2">2271 (167)</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table2fn1">
            <p><sup>a</sup>Values represent mean (SD) word counts for inputs and generated outputs at each stage for Gemini, ChatGPT, and Opus (Claude), applied to 3 qualitative health interview datasets (ILD, POTS, and COPD). Tasks include L1 code extraction, DC, hierarchical code combination (L1→L2, L2→L3), DG, and theme generation across codebook levels. Input lengths reflect submitted transcripts or codebooks, and outputs include generated codes, definitions, and traceability information. Gemini and ChatGPT showed relatively stable output lengths across tasks, whereas Opus exhibited more input-responsive output scaling.</p>
          </fn>
          <fn id="table2fn2">
            <p><sup>b</sup>L1: layer 1.</p>
          </fn>
          <fn id="table2fn3">
            <p><sup>c</sup>DC: direct coding.</p>
          </fn>
          <fn id="table2fn4">
            <p><sup>d</sup>L2: layer 2.</p>
          </fn>
          <fn id="table2fn5">
            <p><sup>e</sup>L3: layer 3.</p>
          </fn>
          <fn id="table2fn6">
            <p><sup>f</sup>DG: direct grouping.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <table-wrap position="float" id="table3">
        <label>Table 3</label>
        <caption>
          <p>Processing time across models and workflow tasks in the modular human–artificial intelligence thematic analysis pipeline<sup>a</sup>.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="360"/>
          <col width="220"/>
          <col width="220"/>
          <col width="200"/>
          <thead>
            <tr valign="top">
              <td>Task</td>
              <td>Gemini (seconds), mean (SD)</td>
              <td>ChatGPT (seconds), mean (SD)</td>
              <td>Opus (seconds), mean (SD)</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td>Extract codes from 1 transcript (L1<sup>b</sup> extraction)</td>
              <td>72 (6)</td>
              <td>123 (16)</td>
              <td>81 (9)</td>
            </tr>
            <tr valign="top">
              <td>Combine codes from L1 codes in 4 transcripts (L1-L2<sup>c</sup> combination)</td>
              <td>91 (8)</td>
              <td>185 (21)</td>
              <td>273 (28)</td>
            </tr>
            <tr valign="top">
              <td>Combine codes from L2 codes (L2-L3<sup>d</sup> combination)</td>
              <td>133 (11)</td>
              <td>196 (19)</td>
              <td>663 (56)</td>
            </tr>
            <tr valign="top">
              <td>L1 theme generation</td>
              <td>145 (13)</td>
              <td>168 (16)</td>
              <td>488 (42)</td>
            </tr>
            <tr valign="top">
              <td>L2 theme generation</td>
              <td>65 (5)</td>
              <td>127 (17)</td>
              <td>402 (36)</td>
            </tr>
            <tr valign="top">
              <td>L3 theme generation</td>
              <td>40 (4)</td>
              <td>62 (5)</td>
              <td>268 (25)</td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table3fn1">
            <p><sup>a</sup>Processing time was measured manually using a digital clock or stopwatch from prompt submission through the web interface to completion of the full model response. Theme generation tasks were measured 3 times, once for each study dataset, whereas all other tasks were measured across 5 observations. These values reflect end-user wall-clock time under consumer-facing web interface conditions and therefore include interface latency, response generation, and streaming time rather than isolated model inference time.</p>
          </fn>
          <fn id="table3fn2">
            <p><sup>b</sup>L1: layer 1.</p>
          </fn>
          <fn id="table3fn3">
            <p><sup>c</sup>L2: layer 2.</p>
          </fn>
          <fn id="table3fn4">
            <p><sup>d</sup>L3: layer 3.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <p><xref ref-type="table" rid="table4">Table 4</xref> shows the cosine similarity between human-generated themes and AI-generated themes under different settings, and <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> visualizes the distribution of similarity scores. Because this study was designed as a descriptive workflow evaluation, the cosine similarity results are reported as descriptive summaries rather than inferential statistical comparisons. Across the 3 studies, Opus showed the strongest and most consistent alignment with human-generated themes, achieving the highest average cosine similarity in nearly all settings. Its scores were generally clustered around 0.88-0.89, with the best performance observed in POTS-DC (mean 0.893, SD 0.041), COPD-DG (mean 0.891, SD 0.027), and ILD-L3 (mean 0.889, SD 0.032). In comparison, ChatGPT showed competitive performance in some settings, particularly ILD-L1 (mean 0.870, SD 0.027), POTS-L2 (mean 0.881, SD 0.052), and COPD-DC (mean 0.872, SD 0.040), but its results were more variable across workflows. Gemini generally produced slightly lower similarity scores than the other 2 models, although it remained competitive in several direct-coding settings, such as ILD-DC (mean 0.866, SD 0.024) and COPD-DC (mean 0.865, SD 0.036). Word count of human-generated and AI-generated themes across models and workflow strategies was similar and lower than the limitation of the embedding models. Values are reported as mean word count with range and number of themes in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p>
      <p>Across workflow strategies, no single strategy was universally best for all models, but some patterns were evident. For Opus, L3, DC, and DG consistently yielded the highest similarities, suggesting that either deeper hierarchical consolidation or DC strategies helped produce themes closer to human reference. For ChatGPT, performance was relatively stronger in L1 and L2, indicating that it may perform better with moderate structure rather than extensive consolidation. Gemini showed comparatively stable but less optimal performance, with its best results often appearing in DC or L1 settings. Overall, these findings suggest that model choice had a greater effect on theme similarity than workflow strategy, and that Opus combined with L3, DC, or DG produced the most human-aligned thematic outputs.</p>
      <p>To help interpret the cosine similarity scores, <xref ref-type="boxed-text" rid="box1">Textbox 1</xref> provides a representative example from the POTS dataset. The human-generated theme “biofeedback and self-monitoring” was closely matched with AI-generated themes from all 3 models, with cosine similarity scores of 0.89 for Gemini, 0.94 for ChatGPT, and 0.96 for Opus. These matched themes shared the central concept of using real-time physiological feedback, especially heart rate and oxygen saturation monitoring, to support safe exercise and symptom management. For comparison, the textbox also includes AI-generated themes that were mapped to different human themes in the full alignment but had lower cosine similarity scores when compared with “biofeedback and self-monitoring”. These examples show how scores decreased when the AI-generated theme focused on adjacent but less directly related concepts, such as home-based rehabilitation logistics, onboarding, device accessibility, or equipment constraints.</p>
      <table-wrap position="float" id="table4">
        <label>Table 4</label>
        <caption>
          <p>Mean cosine similarity between human-generated themes and artificial intelligence–generated themes across 3 qualitative health interview studies, 5 workflow strategies, and 3 large language models<sup>a</sup>.</p>
        </caption>
        <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
          <col width="30"/>
          <col width="170"/>
          <col width="0"/>
          <col width="200"/>
          <col width="0"/>
          <col width="200"/>
          <col width="0"/>
          <col width="300"/>
          <thead>
            <tr valign="top">
              <td colspan="3">Study and themes</td>
              <td colspan="2">Gemini, mean (SD)</td>
              <td colspan="2">ChatGPT, mean (SD)</td>
              <td>Opus, mean (SD)</td>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td colspan="8">ILD<sup>b</sup></td>
            </tr>
            <tr valign="top">
              <td rowspan="5">
                <break/>
              </td>
              <td>L1<sup>c</sup></td>
              <td colspan="2">0.840 (0.024)</td>
              <td colspan="2">0.870 (0.027)</td>
              <td colspan="2">0.884 (0.029)</td>
            </tr>
            <tr valign="top">
              <td>L2<sup>d</sup></td>
              <td colspan="2">0.843 (0.027)</td>
              <td colspan="2">0.869 (0.032)</td>
              <td colspan="2">0.868 (0.034)</td>
            </tr>
            <tr valign="top">
              <td>L3<sup>e</sup></td>
              <td colspan="2">0.841 (0.035)</td>
              <td colspan="2">0.844 (0.042)</td>
              <td colspan="2">0.889 (0.032)<sup>f</sup></td>
            </tr>
            <tr valign="top">
              <td>DC<sup>g</sup></td>
              <td colspan="2">0.866 (0.024)</td>
              <td colspan="2">0.851 (0.038)</td>
              <td colspan="2">0.882 (0.019)</td>
            </tr>
            <tr valign="top">
              <td>DG<sup>h</sup></td>
              <td colspan="2">0.848 (0.031)</td>
              <td colspan="2">0.865 (0.041)</td>
              <td colspan="2">0.882 (0.021)</td>
            </tr>
            <tr valign="top">
              <td colspan="8">POTS<sup>i</sup></td>
            </tr>
            <tr valign="top">
              <td rowspan="5">
                <break/>
              </td>
              <td>L1</td>
              <td colspan="2">0.874 (0.046)</td>
              <td colspan="2">0.874 (0.038)</td>
              <td colspan="2">0.887 (0.039)</td>
            </tr>
            <tr valign="top">
              <td>L2</td>
              <td colspan="2">0.856 (0.054)</td>
              <td colspan="2">0.881 (0.052)</td>
              <td colspan="2">0.888 (0.027)</td>
            </tr>
            <tr valign="top">
              <td>L3</td>
              <td colspan="2">0.841 (0.021)</td>
              <td colspan="2">0.852 (0.050)</td>
              <td colspan="2">0.888 (0.035)</td>
            </tr>
            <tr valign="top">
              <td>DC</td>
              <td colspan="2">0.859 (0.022)</td>
              <td colspan="2">0.872 (0.045)</td>
              <td colspan="2">0.893 (0.041)<sup>f</sup></td>
            </tr>
            <tr valign="top">
              <td>DG</td>
              <td colspan="2">0.859 (0.025)</td>
              <td colspan="2">0.866 (0.026)</td>
              <td colspan="2">0.882 (0.035)</td>
            </tr>
            <tr valign="top">
              <td colspan="8">COPD<sup>j</sup></td>
            </tr>
            <tr valign="top">
              <td rowspan="5">
                <break/>
              </td>
              <td>L1</td>
              <td colspan="2">0.861 (0.039)</td>
              <td colspan="2">0.861 (0.041)</td>
              <td colspan="2">0.879 (0.041)</td>
            </tr>
            <tr valign="top">
              <td>L2</td>
              <td colspan="2">0.861 (0.030)</td>
              <td colspan="2">0.852 (0.045)</td>
              <td colspan="2">0.884 (0.028)</td>
            </tr>
            <tr valign="top">
              <td>L3</td>
              <td colspan="2">0.859 (0.042)</td>
              <td colspan="2">0.869 (0.038)</td>
              <td colspan="2">0.890 (0.031)</td>
            </tr>
            <tr valign="top">
              <td>DC</td>
              <td colspan="2">0.865 (0.036)</td>
              <td colspan="2">0.872 (0.040)</td>
              <td colspan="2">0.888 (0.028)</td>
            </tr>
            <tr valign="top">
              <td>DG</td>
              <td colspan="2">0.863 (0.037)</td>
              <td colspan="2">0.844 (0.038)</td>
              <td colspan="2">0.891 (0.027)<sup>f</sup></td>
            </tr>
          </tbody>
        </table>
        <table-wrap-foot>
          <fn id="table4fn1">
            <p><sup>a</sup>This table summarizes semantic alignment between the original human-generated themes and artificial intelligence (AI)–generated themes produced by Gemini, ChatGPT, and Opus when the modular human-AI collaboration pipeline was applied to deidentified interview transcripts from 3 previously completed studies: ILD (17 patients evaluated during a 1-hour in-person feasibility session of a home-based telerehabilitation system, followed by semistructured interviews), POTS (15 patients with dysautonomia or POTS evaluated during a 1-hour in-person telerehabilitation usability session, followed by semistructured interviews), and COPD (16 patients interviewed remotely after completing a 12-month home-based pulmonary telerehabilitation program). Results are shown for 5 workflow strategies: L1, L2, L3, DC, and DG. Theme descriptions were embedded using sentence-t5-xxl, aligned using a combined Hungarian and Greedy matching procedure, and compared using cosine similarity. Higher values indicate greater semantic agreement between AI-generated and human-generated themes.</p>
          </fn>
          <fn id="table4fn2">
            <p><sup>b</sup>ILD: interstitial lung disease.</p>
          </fn>
          <fn id="table4fn3">
            <p><sup>c</sup>L1: layer 1.</p>
          </fn>
          <fn id="table4fn4">
            <p><sup>d</sup>L2: layer 2.</p>
          </fn>
          <fn id="table4fn5">
            <p><sup>e</sup>L3: layer 3.</p>
          </fn>
          <fn id="table4fn6">
            <p><sup>f</sup>Highest values for each study.</p>
          </fn>
          <fn id="table4fn7">
            <p><sup>g</sup>DC: direct coding.</p>
          </fn>
          <fn id="table4fn8">
            <p><sup>h</sup>DG: direct grouping.</p>
          </fn>
          <fn id="table4fn9">
            <p><sup>i</sup>POTS: postural orthostatic tachycardia syndrome.</p>
          </fn>
          <fn id="table4fn10">
            <p><sup>j</sup>COPD: chronic obstructive pulmonary disease.</p>
          </fn>
        </table-wrap-foot>
      </table-wrap>
      <boxed-text id="box1" position="float">
        <title>A representative example illustrates how cosine similarity scores (CSSs) vary with thematic overlap between human-generated and AI-generated themes. This textbox presents 1 human-generated reference theme from the postural orthostatic tachycardia syndrome telerehabilitation dataset, “biofeedback and self-monitoring”, alongside artificial intelligence (AI)–generated themes from Gemini, ChatGPT, and Opus. The first row shows that the AI-generated theme matched to this human theme during the alignment procedure and its CSS. The second row shows an AI-generated theme from each model that was mapped to a different human theme in the full alignment, but was compared with “biofeedback and self-monitoring” to illustrate how similarity scores decrease when thematic overlap is partial or adjacent rather than direct. This example provides an interpretive anchor for understanding the cosine similarity range reported in the quantitative results.</title>
        <p>
          <bold>Human theme</bold>
        </p>
        <list list-type="bullet">
          <list-item>
            <p>“Biofeedback and self-monitoring”: Real-time biofeedback, particularly heart rate and oxygen saturation monitoring, was viewed as essential for exercising safely with postural orthostatic tachycardia syndrome (POTS) symptoms. Participants reported that these features provided reassurance, guided exercise intensity, and helped prevent overexertion, enabling them to exercise independently with confidence. Visual displays, including engaging elements such as the racecar avatar, were appreciated for making monitoring intuitive and motivating. Tracking progress over time further reinforced adherence and a sense of accomplishment. Suggestions for improvement included making data more visible, adding instructional cues, expanding monitoring to blood pressure or symptom logging, and offering alerts to emergency contacts.</p>
          </list-item>
        </list>
        <p>
          <bold>Primary matched artificial intelligence–generated themes for this human theme</bold>
        </p>
        <list list-type="bullet">
          <list-item>
            <p>Gemini (CSS 0.89): Using Biofeedback and Structure for Safety and Symptom Management: Participants identified real-time physiological biofeedback, particularly heart rate monitoring, as a critical safety tool that transformed abstract sensations into actionable data for self-regulation. The structured nature of the program provided a verified medical framework that alleviated anxiety about overexertion, allowing users to move from avoidance behaviors to active management with confidence. Ultimately, users viewed this combination of biofeedback and guided pacing as a vital strategy for preventing “boom and bust” cycles and managing long-term stamina within the constraints of their condition.</p>
          </list-item>
          <list-item>
            <p>ChatGPT (CSS 0.94): Biofeedback-led pacing and safeguards address fear of flares: Participants described real-time vitals feedback (especially heart rate and oxygen) as central for pacing and safety during POTS-appropriate exercise. Participants reported using biofeedback to adjust intensity moment-to-moment and to decide when to slow down or stop, and some wanted additional vitals (eg, blood pressure) integrated to match their personal thresholds. Participants also wanted vitals displayed more prominently so that they can check quickly during exertion without competing visual elements. Participants linked these features to concerns about overexertion, symptom worsening, and the need for safeguards that respect “bad day” limitations and flexible intensity.</p>
          </list-item>
          <list-item>
            <p>Opus (CSS 0.96): Real-Time Physiological Monitoring for Safe Exercise Management: Participants with POTS identified continuous heart rate and oxygen saturation monitoring as medically essential for exercising safely, given the unpredictable cardiovascular responses characteristic of the condition. Real-time biofeedback allowed users to adjust exertion levels and avoid symptom flares from overexertion. Specific design feedback included repositioning the vital signs display for better visibility during active pedaling. Participants also requested the addition of blood pressure monitoring to provide a more complete physiological picture for both self-management and provider review.</p>
          </list-item>
        </list>
        <p>
          <bold>Comparison with artificial intelligence–generated themes mapped to another human theme</bold>
        </p>
        <list list-type="bullet">
          <list-item>
            <p>Gemini (CSS 0.80): Motivation, Accountability, and Logistical Factors in Home-Based Rehabilitation: Participants emphasized that the home-based model eliminated draining commutes, thereby conserving energy for exercise and democratizing access to care for those with mobility limitations. Engagement was further driven by gamified elements that provided mental distraction from physical exertion, as well as the professional accountability of knowing that a health care provider was monitoring their progress remotely. However, while the convenience was a primary driver for adherence, some participants noted that practical constraints, such as the need for dedicated physical space and equipment setup, presented logistical barriers in smaller living environments.</p>
          </list-item>
          <list-item>
            <p>ChatGPT (CSS 0.75): Guided Onboarding and Practice Builds Independent System Use: Participants reported that an initial walk-through or practice session was needed to learn how to use the system correctly, even when the interface later felt intuitive. Participants described onboarding as helping them understand where to click, how to start sessions, and how to set up the tablet and connected peripherals. Participants also suggested that future users with less technology experience may need additional support such as tutorial videos or remote guidance to replicate setup and use at home.</p>
          </list-item>
          <list-item>
            <p>Opus (CSS 0.77): Device Accessibility, Equipment Constraints, and Adoption Barriers: Participants identified practical barriers that could limit system adoption across diverse users and living situations. Requests for smartphone and tablet compatibility reflected the preference for accessing the system on primary daily devices rather than a dedicated computer. Physical space requirements for the recumbent pedal device and associated equipment were seen as potentially prohibitive for those in small living spaces. Cost concerns were raised as a hypothetical barrier given existing medical expenses, and participants noted that individuals with limited technology experience—particularly older adults—would require enhanced onboarding and tutorial support.</p>
          </list-item>
        </list>
      </boxed-text>
      <p>Across the full pipeline, ChatGPT and Opus also demonstrated stronger usability and task management support. Both platforms provided project-level conversation grouping, which facilitated tracking and managing the multiple conversations required by the pipeline. Gemini lacked an equivalent project management function; although this did not create a major limitation in our experimental setup (which used a new account with a single project), it may become more consequential in larger or longer-term studies.</p>
      <p>Finally, with explicit output format requirements in the prompts, ChatGPT and Opus followed the requested format reliably and could export outputs as .txt files without additional prompting or tuning. Gemini was less consistent in adhering to the specified format: across 48 code extraction conversations, it produced 12 distinct formats; across 15 code combination conversations, it produced 5 formats; and across 15 theme generation conversations, it produced 8 formats. This variability increased downstream preprocessing effort relative to the other 2 models.</p>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings</title>
        <p>This study evaluated a modular human–AI collaboration pipeline for LLM-assisted thematic analysis across 3 qualitative digital health interview datasets and 5 workflow strategies. Overall, the findings show that both model choice and workflow structure shaped thematic outputs, but model choice appeared to have a stronger influence on alignment with human-generated themes. Across ILD, POTS, and COPD, Opus produced the most consistently human-aligned themes, while ChatGPT performed competitively in selected settings, and Gemini showed more constrained but relatively stable performance. These findings suggest that LLM-assisted thematic analysis should not be treated as a single generic capability; rather, performance depends on how a model interacts with specific workflow designs for extraction, consolidation, and theme generation.</p>
        <p>A key finding is that Gemini and ChatGPT exhibited constrained output behavior under the evaluated conditions. Both models produced relatively fixed numbers of codes across tasks (approximately 10 for Gemini and approximately 25 for ChatGPT), even when input size and task complexity varied. In qualitative analysis, this matters because thematic fidelity depends on adequately capturing the diversity of participant experiences. When outputs are effectively bounded, there is a risk of undercoding distinct ideas and underrepresenting less frequent but potentially important perspectives. This risk is particularly important in health-related interviews, where less frequent concerns may still be clinically meaningful [<xref ref-type="bibr" rid="ref18">18</xref>-<xref ref-type="bibr" rid="ref20">20</xref>].</p>
        <p>The word count analysis provides additional evidence supporting this pattern. Despite substantial variation in input length across workflow stages, Gemini and ChatGPT produced outputs with relatively stable lengths, suggesting the presence of an effective output ceiling under the evaluated conditions. In contrast, Opus exhibited more input-responsive behavior, with output length increasing in higher-input settings such as DC and large codebook consolidation. This difference in output length responsiveness is consistent with the observed variation in code and theme counts across models.</p>
        <p>At the same time, the findings show that workflow structure can partly compensate for model-specific limitations. For Opus, the hierarchical strategies performed especially well, with L3 producing the highest or near-highest similarity in 2 of the 3 studies, and strong performance was also observed in DC and DG settings. This pattern suggests that Opus was able to absorb longer inputs and iterative consolidation without substantial thematic drift. In practical terms, this is encouraging for larger qualitative projects: a staged workflow that first extracts detailed codes and then merges them iteratively may reduce redundancy while still preserving conceptual distinctions. The strong performance of DC and DG for Opus also indicates that the model can tolerate broader inputs, giving researchers flexibility to choose between hierarchical and direct strategies depending on dataset size, desired granularity, and time constraints.</p>
        <p>For ChatGPT, a different pattern emerged. Its performance was relatively stronger in L1 and L2, with less consistent results after deeper consolidation. This suggests that ChatGPT may benefit from moderately structured intermediate representations but lose details when codes are repeatedly merged. One interpretation is that each consolidation step reduces input richness, and because ChatGPT also showed capped output behavior, repeated merging may amplify information loss. In this sense, ChatGPT appears well suited to workflows that preserve more of the original code diversity rather than heavily compressing it. For small- to medium-sized datasets, this may make L1 or L2 especially useful, whereas for larger datasets requiring multiple rounds of consolidation, the trade-off between manageability and thematic detail may become more pronounced.</p>
        <p>Gemini showed the lowest overall similarity scores in most settings, but its results were not uniformly weak. In several direct-coding settings, it remained competitive, and its performance was relatively stable across studies. However, Gemini’s strong tendency to generate approximately the same number of codes regardless of input size suggests limited responsiveness to transcript complexity. This likely constrained downstream theme generation by reducing the range of available concepts before theming even began. From a practical perspective, Gemini may still be useful when the analytic goal is rapid, high-level summarization rather than detailed qualitative interpretation. Its short outputs and fast runtimes make it efficient, but that efficiency appears to come at the cost of granularity and formatting consistency.</p>
        <p>The runtime findings reinforce this interpretation of model behavior. Across the pipeline, processing time was driven less by the nominal task type than by cumulative input and output length. Opus had the longest runtimes because it also generated the most extensive output, which then increased the size of the next-stage inputs. Gemini was consistently the fastest, reflecting its shorter and more compressed responses. This highlights an important trade-off in applied LLM-assisted qualitative research: the most detailed outputs may better preserve thematic nuance, but they also require more time and create heavier downstream processing burdens. Therefore, researchers need to balance fidelity, scalability, and efficiency when selecting a platform and workflow.</p>
        <p>Another practical contribution of this study is that it evaluates not only thematic similarity but also the operational usability of the platforms for multistep qualitative work. ChatGPT and Opus more reliably followed the required output structure and supported easier management of multiple conversations through project-level organization. Gemini was less consistent in output format, which increased preprocessing effort. These differences may seem secondary to thematic quality, but they matter in real-world research settings. A workflow that requires dozens of extractions, combinations, and theme generation sessions depends on consistent formatting and manageable conversation organization. Thus, platform usability should be considered alongside analytic performance when choosing tools for LLM-assisted qualitative analysis.</p>
      </sec>
      <sec>
        <title>Comparison With Prior Work</title>
        <p>Compared with prior literature, this study contributes a more explicitly workflow-centered evaluation. Recent studies have shown that LLMs can support qualitative coding, content analysis, grounded theory, and thematic summarization, including comparisons between AI-generated and human-generated qualitative analyses [<xref ref-type="bibr" rid="ref13">13</xref>-<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref23">23</xref>-<xref ref-type="bibr" rid="ref25">25</xref>]. However, many prior studies rely on single-prompt, single-model, or near end-to-end approaches. These approaches can be efficient, but they make it harder to identify where information loss occurs and often provide less traceability across analytic stages. By contrast, our pipeline separates code extraction, code consolidation, and theme generation into independent, standardized steps. This structure makes the analytic process more auditable and allows direct comparison of hierarchical versus direct strategies, aligning with recent recommendations that LLM-supported qualitative analysis should emphasize transparency, reproducibility, validation, and human oversight [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref22">22</xref>,<xref ref-type="bibr" rid="ref24">24</xref>-<xref ref-type="bibr" rid="ref26">26</xref>].</p>
        <p>This study also adds a reproducible quantitative evaluation layer by comparing AI-generated themes with human-generated themes through embedding-based semantic similarity and systematic alignment. Although semantic similarity cannot fully capture qualitative rigor, it provides a useful comparative signal across models, workflows, and datasets [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref20">20</xref>]. In this study, the use of 3 separate health interview datasets strengthens confidence that the observed patterns are not tied to a single sample alone. Across ILD, POTS, and COPD, Opus remained consistently strong, while the relative strengths and weaknesses of ChatGPT and Gemini followed broadly similar patterns. This cross-study consistency suggests that workflow-model interactions may be a meaningful area for future methodological research in LLM-assisted qualitative analysis.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>Several limitations should be noted. First, all analyses were conducted through consumer-facing web interfaces rather than APIs. Although we used newly registered paid accounts, disabled memory settings where available, and restricted data collection to a fixed study window, web-based platforms may still be affected by unannounced model updates, interface-level output constraints, and uncontrolled generation settings. In addition, the available configurations differed across platforms: ChatGPT and Opus were evaluated with extended thinking modes, whereas Gemini did not offer a comparable extended thinking option during the study window and was evaluated in its available standard configuration. Accordingly, Gemini’s shorter outputs and generally lower similarity scores may reflect differences in the available model-interface configuration, in addition to differences in model behavior.</p>
        <p>Second, the study used standardized prompts and a modular workflow, which improved consistency across models but may not reflect performance under alternative prompt designs or less structured qualitative analysis workflows. In addition, each model-workflow condition was executed once to mirror practical researcher-facing use, so within-model stochastic variation was not quantified.</p>
        <p>Third, the evaluation relied on embedding-based cosine similarity and a 2-stage Hungarian plus Greedy alignment procedure. This approach allowed all themes to be included in the comparison, but it is not equivalent to a formal precision-recall framework and does not fully capture qualitative rigor, interpretive depth, or potential overgeneration effects.</p>
        <p>Fourth, this study was descriptive rather than confirmatory. Formal inferential testing was not conducted because theme pair similarity scores were generated through an alignment procedure, were not fully independent, and came from only 3 datasets with 1 run per model-workflow condition. Therefore, differences across models and strategies should be interpreted as descriptive patterns rather than statistically confirmed effects.</p>
        <p>Although all LLM interactions were performed through consumer-facing web interfaces, to reduce manual labor and the risk of human error, this implementation used a simple Python-assisted identifier assignment step to organize intermediate outputs, which requires intermediate programmatic data-processing skills.</p>
        <p>Finally, the study evaluated only 3 LLMs and included a descriptive assessment of output format consistency and workflow management conducted by one researcher (YB). Future work should include additional proprietary and open-source models, repeated runs, independent workflow assessments, and prespecified statistical analyses across larger and more diverse qualitative datasets.</p>
      </sec>
      <sec>
        <title>Future Directions</title>
        <p>Future work should validate this framework across larger and more diverse qualitative datasets, disease areas, and methodological traditions. Additional studies should include a broader range of proprietary and open-source LLMs, repeated runs for each model-workflow condition, and API-based implementations with controlled decoding parameters to better assess reproducibility and run-to-run variability. Evaluation should also extend beyond embedding-based semantic similarity by incorporating expert ratings of theme quality, code-level validation linking excerpts to assigned codes, human-human comparison baselines, and measures of thematic coverage, missed concepts, and overgeneration. Future research could further examine how prompt design, transcript partitioning strategies, and human intervention at different stages influence analytic fidelity. These efforts would help clarify which combinations of model choice, workflow design, and human oversight are most appropriate for different qualitative research goals.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>This study shows that a modular human-AI pipeline can support thematic analysis across multiple digital health interview studies, but its effectiveness depends strongly on both model choice and workflow design. Opus achieved the most consistent alignment with human-generated themes, while ChatGPT and Gemini showed distinct trade-offs in thematic fidelity, runtime, and usability. These results suggest that LLMs can serve as valuable assistants in qualitative research when embedded within structured, transparent, and human-supervised workflows. Rather than replacing qualitative researchers, LLMs may be most useful as configurable analytic partners whose strengths and limitations must be carefully matched to the goals and scale of the study.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Exact verbatim study background text inserted into the code extraction module prompt for each qualitative interview dataset. The table reports the full study-specific background text used to replace the “[100 words of study background]” placeholder in the standardized code extraction module prompt before transcript-level analysis. Separate text was used for the 3 previously completed telerehabilitation-related qualitative studies involving patients with interstitial lung disease, postural orthostatic tachycardia syndrome, and chronic obstructive pulmonary disease.</p>
        <media xlink:href="medinform_v14i1e96129_app1.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Distribution of cosine similarity scores between human-generated themes and artificial intelligence (AI)–generated themes across 3 large language models, 5 workflow strategies, and 3 digital health qualitative interview studies. This figure visualizes the distribution of semantic similarity scores obtained after aligning AI-generated themes to the human-generated reference themes from 3 previously completed thematic analyses involving patients with interstitial lung disease (n=17), postural orthostatic tachycardia syndrome (n=15), and chronic obstructive pulmonary disease (n=16). For each model (Gemini 3 Pro, GPT-5.2-thinking, and Opus 4.6) and each workflow strategy (layer 1 [L1], layer 2 [L2], layer 3 [L3], direct coding [DC], and direct grouping [DG]), theme descriptions were embedded using sentence-t5-xxl and compared using cosine similarity after Hungarian plus Greedy matching. Higher scores indicate closer semantic alignment between the AI-derived themes and the original human thematic analysis. Across the 3 studies, Opus 4.6 generally showed the highest and most consistent similarity distributions.</p>
        <media xlink:href="medinform_v14i1e96129_app2.docx" xlink:title="DOCX File , 699 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Word count distribution of human-generated and artificial intelligence (AI)–generated theme summaries across models and workflow strategies. Values are reported as mean word count with range (minimum–maximum) and number of themes (n). Human-generated themes (n=23) were derived from 3 qualitative health interview studies (interstitial lung disease, postural orthostatic tachycardia syndrome, and chronic obstructive pulmonary disease). AI-generated themes were produced by Gemini 3 Pro, ChatGPT with GPT-5.2-thinking, and Opus 4.6 across the 3 studies using 5 workflow strategies: layer 1 (L1), layer 2 (L2), layer 3 (L3), direct coding (DC), and direct grouping (DG).</p>
        <media xlink:href="medinform_v14i1e96129_app3.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AI</term>
          <def>
            <p>artificial intelligence</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">API</term>
          <def>
            <p>application programming interface</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">COPD</term>
          <def>
            <p>chronic obstructive pulmonary disease</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">DC</term>
          <def>
            <p>direct coding</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">DG</term>
          <def>
            <p>direct grouping</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">ILD</term>
          <def>
            <p>interstitial lung disease</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">L1</term>
          <def>
            <p>layer 1</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">L2</term>
          <def>
            <p>layer 2</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">L3</term>
          <def>
            <p>layer 3</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">LLM</term>
          <def>
            <p>large language model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">POTS</term>
          <def>
            <p>postural orthostatic tachycardia syndrome</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The authors used the generative artificial intelligence tool ChatGPT by OpenAI, Claude by Anthropic, and Gemini by Google to perform the thematic analysis in this study. ChatGPT (OpenAI) was additionally used for language editing during manuscript preparation. We appreciate Aileen Gabriel’s input on qualitative analysis methods.</p>
    </ack>
    <notes>
      <sec>
        <title>Funding</title>
        <p>The project was in part funded by the National Institutes of Health (grant R33HL143317).</p>
      </sec>
      <sec>
        <title>Data Availability</title>
        <p>The data in our study are available from the corresponding author on reasonable request. The code can be accessed at the Arizona Telemedicine Program [<xref ref-type="bibr" rid="ref37">37</xref>].</p>
      </sec>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>Conceptualization: JF (lead), YB (equal)</p>
        <p>Data curation: YB (lead), JF (equal)</p>
        <p>Formal analysis: YB</p>
        <p>Funding acquisition: JF</p>
        <p>Investigation: YB</p>
        <p>Methodology: YB</p>
        <p>Resources: JF</p>
        <p>Software: YB</p>
        <p>Supervision: JF</p>
        <p>Validation: YB (lead), JF (equal)</p>
        <p>Visualization: YB</p>
        <p>Writing—original draft: YB</p>
        <p>Writing—review and editing: YB (lead), JF (equal)</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Braun</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Clarke</surname>
              <given-names>V</given-names>
            </name>
          </person-group>
          <article-title>Using thematic analysis in psychology</article-title>
          <source>Qual Res Psychol</source>
          <year>2006</year>
          <volume>3</volume>
          <issue>2</issue>
          <fpage>77</fpage>
          <lpage>101</lpage>
          <pub-id pub-id-type="doi">10.1191/1478088706qp063oa</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kiger</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>Varpio</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Thematic analysis of qualitative data: AMEE Guide No. 131</article-title>
          <source>Med Teach</source>
          <year>2020</year>
          <volume>42</volume>
          <issue>8</issue>
          <fpage>846</fpage>
          <lpage>854</lpage>
          <pub-id pub-id-type="doi">10.1080/0142159x.2020.1755030</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>Gale</surname>
              <given-names>NK</given-names>
            </name>
            <name name-style="western">
              <surname>Heath</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Cameron</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Rashid</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Redwood</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Using the framework method for the analysis of qualitative data in multi-disciplinary health research</article-title>
          <source>BMC Med Res Methodol</source>
          <year>2013</year>
          <volume>13</volume>
          <fpage>117</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcmedresmethodol.biomedcentral.com/articles/10.1186/1471-2288-13-117"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1471-2288-13-117</pub-id>
          <pub-id pub-id-type="medline">24047204</pub-id>
          <pub-id pub-id-type="pii">1471-2288-13-117</pub-id>
          <pub-id pub-id-type="pmcid">PMC3848812</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>Smiley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Home automated telemanagement system for individualized exercise programs: design and usability evaluation</article-title>
          <source>JMIR Biomed Eng</source>
          <year>2024</year>
          <volume>9</volume>
          <fpage>e65734</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://biomedeng.jmir.org/2024//e65734/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/65734</pub-id>
          <pub-id pub-id-type="medline">39658220</pub-id>
          <pub-id pub-id-type="pii">v9i1e65734</pub-id>
          <pub-id pub-id-type="pmcid">PMC11724215</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>Cross</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Challenges in the design of a home telemanagement trial for patients with ulcerative colitis</article-title>
          <source>Clin Trials</source>
          <year>2009</year>
          <volume>6</volume>
          <issue>6</issue>
          <fpage>649</fpage>
          <lpage>657</lpage>
          <pub-id pub-id-type="doi">10.1177/1740774509346978</pub-id>
          <pub-id pub-id-type="medline">19822631</pub-id>
          <pub-id pub-id-type="pii">1740774509346978</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>Gabriel</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Assessing the barriers and facilitators to pulmonary rehabilitation referrals using the Consolidated Framework for Implementation Research (CFIR)</article-title>
          <source>AMIA Jt Summits Transl Sci Proc</source>
          <year>2024</year>
          <volume>2024</volume>
          <fpage>172</fpage>
          <lpage>181</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38827066"/>
          </comment>
          <pub-id pub-id-type="medline">38827066</pub-id>
          <pub-id pub-id-type="pii">2269</pub-id>
          <pub-id pub-id-type="pmcid">PMC11141829</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>Castro</surname>
              <given-names>HK</given-names>
            </name>
            <name name-style="western">
              <surname>Cross</surname>
              <given-names>RK</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Using a home automated telemanagement (HAT) system: experiences and perceptions of patients with inflammatory bowel disease</article-title>
          <source>AMIA Annu Symp Proc</source>
          <year>2006</year>
          <volume>2006</volume>
          <fpage>872</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/17238492"/>
          </comment>
          <pub-id pub-id-type="medline">17238492</pub-id>
          <pub-id pub-id-type="pii">85855</pub-id>
          <pub-id pub-id-type="pmcid">PMC1839272</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>Cook</surname>
              <given-names>DA</given-names>
            </name>
            <name name-style="western">
              <surname>Ginsburg</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sawatsky</surname>
              <given-names>AP</given-names>
            </name>
            <name name-style="western">
              <surname>Kuper</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>D’Angelo</surname>
              <given-names>JD</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence to support qualitative data analysis: promises, approaches, pitfalls</article-title>
          <source>Acad Med</source>
          <year>2025</year>
          <volume>100</volume>
          <issue>10</issue>
          <fpage>1134</fpage>
          <lpage>1149</lpage>
          <pub-id pub-id-type="doi">10.1097/acm.0000000000006134</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>Hitch</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Artificial intelligence augmented qualitative analysis: the way of the future?</article-title>
          <source>Qual Health Res</source>
          <year>2024</year>
          <volume>34</volume>
          <issue>7</issue>
          <fpage>595</fpage>
          <lpage>606</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/10.1177/10497323231217392?url_ver=Z39.88-2003&#38;rfr_id=ori:rid:crossref.org&#38;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/10497323231217392</pub-id>
          <pub-id pub-id-type="medline">38064244</pub-id>
          <pub-id pub-id-type="pmcid">PMC11103925</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>Lee</surname>
              <given-names>VV</given-names>
            </name>
            <name name-style="western">
              <surname>van der Lubbe</surname>
              <given-names>SCC</given-names>
            </name>
            <name name-style="western">
              <surname>Goh</surname>
              <given-names>LH</given-names>
            </name>
            <name name-style="western">
              <surname>Valderas</surname>
              <given-names>JM</given-names>
            </name>
          </person-group>
          <article-title>Harnessing ChatGPT for thematic analysis: are we ready?</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <volume>26</volume>
          <fpage>e54974</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e54974/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/54974</pub-id>
          <pub-id pub-id-type="medline">38819896</pub-id>
          <pub-id pub-id-type="pii">v26i1e54974</pub-id>
          <pub-id pub-id-type="pmcid">PMC11179012</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>Nguyen-Trung</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT in thematic analysis: Can AI become a research assistant in qualitative research?</article-title>
          <source>Qual Quant</source>
          <year>2025</year>
          <volume>59</volume>
          <issue>6</issue>
          <fpage>4945</fpage>
          <lpage>4978</lpage>
          <pub-id pub-id-type="doi">10.1007/s11135-025-02165-z</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>Goyanes</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Lopezosa</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Jordá</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <article-title>Thematic analysis of interview data with ChatGPT: designing and testing a reliable research protocol for qualitative research</article-title>
          <source>Qual Quant</source>
          <year>2025</year>
          <volume>59</volume>
          <issue>6</issue>
          <fpage>5491</fpage>
          <lpage>5510</lpage>
          <pub-id pub-id-type="doi">10.1007/s11135-025-02199-3</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>Jeong</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Smith</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gallo</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Knowlton</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Shieh</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Leveraging ChatGPT for thematic analysis of medical best practice advisory data</article-title>
          <source>JAMIA Open</source>
          <year>2025</year>
          <volume>8</volume>
          <issue>5</issue>
          <fpage>ooaf126</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/jamiaopen/article-lookup/doi10.1093/jamiaopen/ooaf126"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamiaopen/ooaf126</pub-id>
          <pub-id pub-id-type="medline">41487277</pub-id>
          <pub-id pub-id-type="pii">ooaf126</pub-id>
          <pub-id pub-id-type="pmcid">PMC12757007</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>Bijker</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Merkouris</surname>
              <given-names>SS</given-names>
            </name>
            <name name-style="western">
              <surname>Dowling</surname>
              <given-names>NA</given-names>
            </name>
            <name name-style="western">
              <surname>Rodda</surname>
              <given-names>SN</given-names>
            </name>
          </person-group>
          <article-title>ChatGPT for automated qualitative research: content analysis</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <volume>26</volume>
          <fpage>e59050</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e59050/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/59050</pub-id>
          <pub-id pub-id-type="medline">39052327</pub-id>
          <pub-id pub-id-type="pii">v26i1e59050</pub-id>
          <pub-id pub-id-type="pmcid">PMC11310599</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>Prescott</surname>
              <given-names>MR</given-names>
            </name>
            <name name-style="western">
              <surname>Yeager</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Ham</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Rivera Saldana</surname>
              <given-names>CD</given-names>
            </name>
            <name name-style="western">
              <surname>Serrano</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Narez</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Paltin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Delgado</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Moore</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Montoya</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Comparing the efficacy and efficiency of human and generative AI: qualitative thematic analyses</article-title>
          <source>JMIR AI</source>
          <year>2024</year>
          <volume>3</volume>
          <fpage>e54482</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ai.jmir.org/2024//e54482/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/54482</pub-id>
          <pub-id pub-id-type="medline">39094113</pub-id>
          <pub-id pub-id-type="pii">v3i1e54482</pub-id>
          <pub-id pub-id-type="pmcid">PMC11329846</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>Deiner</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Honcharov</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Mackey</surname>
              <given-names>TK</given-names>
            </name>
            <name name-style="western">
              <surname>Porco</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Sarkar</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Large language models can enable inductive thematic analysis of a social media corpus in a single prompt: human validation study</article-title>
          <source>JMIR Infodemiology</source>
          <year>2024</year>
          <volume>4</volume>
          <fpage>e59641</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://infodemiology.jmir.org/2024//e59641/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/59641</pub-id>
          <pub-id pub-id-type="medline">39207842</pub-id>
          <pub-id pub-id-type="pii">v4i1e59641</pub-id>
          <pub-id pub-id-type="pmcid">PMC11393503</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>Castellanos</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Gomes</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Vander Meer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Castillo</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Large language models for thematic summarization in qualitative health care research: comparative analysis of model and human performance</article-title>
          <source>JMIR AI</source>
          <year>2025</year>
          <volume>4</volume>
          <fpage>e64447</fpage>
          <lpage>e64447</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ai.jmir.org/2025//e64447/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/64447</pub-id>
          <pub-id pub-id-type="medline">40611510</pub-id>
          <pub-id pub-id-type="pii">v4i1e64447</pub-id>
          <pub-id pub-id-type="pmcid">PMC12231516</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>Sakaguchi</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Sakama</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Watari</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Evaluating ChatGPT in qualitative thematic analysis with human researchers in the japanese clinical context and its cultural interpretation challenges: comparative qualitative study</article-title>
          <source>J Med Internet Res</source>
          <year>2025</year>
          <volume>27</volume>
          <fpage>e71521</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2025//e71521/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/71521</pub-id>
          <pub-id pub-id-type="medline">40273439</pub-id>
          <pub-id pub-id-type="pii">v27i1e71521</pub-id>
          <pub-id pub-id-type="pmcid">PMC12062757</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wen</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Clough</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Paton</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Middleton</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Leveraging large language models for thematic analysis: a case study in the charity sector</article-title>
          <source>AI Soc</source>
          <year>2025</year>
          <volume>41</volume>
          <issue>1</issue>
          <fpage>731</fpage>
          <lpage>748</lpage>
          <pub-id pub-id-type="doi">10.1007/s00146-025-02487-4</pub-id>
        </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>Nguyen</surname>
              <given-names>DC</given-names>
            </name>
            <name name-style="western">
              <surname>Welch</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Generative artificial intelligence in qualitative data analysis: analyzing—or just chatting?</article-title>
          <source>Organ Res Methods</source>
          <year>2025</year>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>3</fpage>
          <lpage>39</lpage>
          <pub-id pub-id-type="doi">10.1177/10944281251377154</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>De Paoli</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Performing an inductive thematic analysis of semi-structured interviews with a large language model: an exploration and provocation on the limits of the approach</article-title>
          <source>Soc Sci Comput Rev</source>
          <year>2023</year>
          <fpage>997</fpage>
          <lpage>1019</lpage>
          <pub-id pub-id-type="doi">10.1177/08944393231220483</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>Jalali</surname>
              <given-names>MS</given-names>
            </name>
            <name name-style="western">
              <surname>Akhavan</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Integrating AI language models in qualitative research: replicating interview data analysis with ChatGPT</article-title>
          <source>Syst Dyn Rev</source>
          <year>2024</year>
          <volume>40</volume>
          <issue>3</issue>
          <fpage>e1772</fpage>
          <pub-id pub-id-type="doi">10.1002/sdr.1772</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>Li</surname>
              <given-names>KD</given-names>
            </name>
            <name name-style="western">
              <surname>McAndrew</surname>
              <given-names>TC</given-names>
            </name>
            <name name-style="western">
              <surname>Hui</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Appa</surname>
              <given-names>AA</given-names>
            </name>
            <name name-style="western">
              <surname>Reddy</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Santucci</surname>
              <given-names>RA</given-names>
            </name>
          </person-group>
          <article-title>Comparing GPT-4 and human researchers in health care data analysis: qualitative description study</article-title>
          <source>J Med Internet Res</source>
          <year>2024</year>
          <volume>26</volume>
          <fpage>e56500</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2024//e56500/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/56500</pub-id>
          <pub-id pub-id-type="medline">39167785</pub-id>
          <pub-id pub-id-type="pii">v26i1e56500</pub-id>
          <pub-id pub-id-type="pmcid">PMC11375389</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>Yue</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Lv</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Hao</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cui</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <article-title>A practical guide and assessment on using ChatGPT to conduct grounded theory: tutorial</article-title>
          <source>J Med Internet Res</source>
          <year>2025</year>
          <volume>27</volume>
          <fpage>e70122</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2025//e70122/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/70122</pub-id>
          <pub-id pub-id-type="medline">40367510</pub-id>
          <pub-id pub-id-type="pii">v27i1e70122</pub-id>
          <pub-id pub-id-type="pmcid">PMC12120365</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>Hill</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Dahil</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Simpson</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Hardisty</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Keast</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Pinn</surname>
              <given-names>CK</given-names>
            </name>
            <name name-style="western">
              <surname>Dambha-Miller</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>Large language models for thematic analysis in healthcare research: a blinded mixed-methods comparison with human analysts</article-title>
          <source>PLOS Digit Health</source>
          <year>2026</year>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e0001189</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pdig.0001189"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pdig.0001189</pub-id>
          <pub-id pub-id-type="medline">41931471</pub-id>
          <pub-id pub-id-type="pii">PDIG-D-25-01248</pub-id>
          <pub-id pub-id-type="pmcid">PMC13048440</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Perkins</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Roe</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The use of generative AI in qualitative analysis: inductive thematic analysis with ChatGPT</article-title>
          <source>J Appl Learn Teach</source>
          <year>2024</year>
          <volume>7</volume>
          <issue>1</issue>
          <fpage>390</fpage>
          <lpage>395</lpage>
          <pub-id pub-id-type="doi">10.37074/jalt.2024.7.1.22</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gabriel</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Tsai</surname>
              <given-names>TY</given-names>
            </name>
            <name name-style="western">
              <surname>Reategui-Rivera</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Smiley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Waddoups</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Scholand</surname>
              <given-names>MB</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Feasibility of telerehabilitation for the treatment of interstitial lung disease</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2025</year>
          <volume>327</volume>
          <fpage>1170</fpage>
          <lpage>1174</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI250574</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gabriel</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Smiley</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Rocco</surname>
              <given-names>PGL</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cortez</surname>
              <given-names>MM</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Perspective of patients with dysautonomia on home-based telerehabilitation</article-title>
          <source>2026 IEEE World AI IoT Congress (AIIoT)</source>
          <year>2026</year>
          <conf-name>2026 IEEE World AI IoT Congress (AIIoT)</conf-name>
          <conf-date>June 11, 2026</conf-date>
          <conf-loc>Seattle, WA</conf-loc>
          <fpage>744</fpage>
          <lpage>749</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.researchgate.net/publication/407503681_Perspective_of_Patients_with_Dysautonomia_on_Home-Based_Telerehabilitation"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gabriel</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Parvanova</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Tsai</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Assessing patient perspectives on pulmonary telerehabilitation using thematic analysis of semi-structured qualitative interviews</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2024</year>
          <volume>310</volume>
          <fpage>1434</fpage>
          <lpage>1435</lpage>
          <pub-id pub-id-type="doi">10.3233/shti231231</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bai</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gabriel</surname>
              <given-names>AS</given-names>
            </name>
            <name name-style="western">
              <surname>Finkelstein</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Human-AI collaboration pipeline for thematic analysis: example of VR-supported pulmonary rehabilitation</article-title>
          <year>2025</year>
          <conf-name>IEEE 16th Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON)</conf-name>
          <conf-date>June 11, 2026</conf-date>
          <conf-loc>Berkeley, CA, USA</conf-loc>
          <fpage>71</fpage>
          <lpage>78</lpage>
          <pub-id pub-id-type="doi">10.1109/iemcon67450.2025.11381093</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="web">
          <article-title>Introducing GPT-5.2</article-title>
          <source>OpenAI</source>
          <year>2025</year>
          <access-date>2026-06-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://openai.com/index/introducing-gpt-5-2/">https://openai.com/index/introducing-gpt-5-2/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="web">
          <article-title>Introducing Claude Opus 4.6</article-title>
          <source>Anthropic</source>
          <year>2026</year>
          <access-date>2026-06-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.anthropic.com/news/claude-opus-4-6">https://www.anthropic.com/news/claude-opus-4-6</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="web">
          <article-title>Gemini 3 Pro</article-title>
          <source>Google DeepMind</source>
          <year>2025</year>
          <access-date>2026-06-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://deepmind.google/models/gemini/pro/?utm_source=chatgpt.com">https://deepmind.google/models/gemini/pro/?utm_source=chatgpt.com</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ni</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hernandez</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Constant</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Ma</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hall</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Cer</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Sentence-T5: scalable sentence encoders from pre-trained text-to-text models</article-title>
          <source>Findings of the Association for Computational Linguistics: ACL 2022</source>
          <year>2022</year>
          <publisher-loc>Dublin, Ireland</publisher-loc>
          <publisher-name>Association for Computational Linguistics</publisher-name>
          <fpage>1864</fpage>
          <lpage>1874</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kuhn</surname>
              <given-names>HW</given-names>
            </name>
          </person-group>
          <article-title>The Hungarian method for the assignment problem</article-title>
          <source>Nav Res Logist Q</source>
          <year>1955</year>
          <volume>2</volume>
          <issue>1-2</issue>
          <fpage>83</fpage>
          <lpage>97</lpage>
          <pub-id pub-id-type="doi">10.1002/nav.3800020109</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Drake</surname>
              <given-names>Doratha E</given-names>
            </name>
            <name name-style="western">
              <surname>Hougardy</surname>
              <given-names>Stefan</given-names>
            </name>
          </person-group>
          <article-title>A simple approximation algorithm for the weighted matching problem</article-title>
          <source>Information Processing Letters</source>
          <year>2003</year>
          <month>2</month>
          <day>28</day>
          <volume>85</volume>
          <issue>4</issue>
          <fpage>211</fpage>
          <lpage>213</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/abs/pii/S0020019002003939"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0020-0190(02)00393-9</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref37">
        <label>37</label>
        <nlm-citation citation-type="web">
          <article-title>Resources</article-title>
          <source>Arizona Telemedicine Program</source>
          <access-date>2026-06-29</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://telemedicine.arizona.edu/resources">https://telemedicine.arizona.edu/resources</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
