<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR AI</journal-id><journal-id journal-id-type="publisher-id">ai</journal-id><journal-id journal-id-type="index">41</journal-id><journal-title>JMIR AI</journal-title><abbrev-journal-title>JMIR AI</abbrev-journal-title><issn pub-type="epub">2817-1705</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">v5i1e93996</article-id><article-id pub-id-type="doi">10.2196/93996</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Large Language Model&#x2013;Assisted Semiautomated Data Harmonization Pipeline for the Multiple Chronic Disease Disparities Research Consortium: Framework Development and Comparative Validation Study</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Kim</surname><given-names>Hyelee</given-names></name><degrees>MD, MAS, MS, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Liang</surname><given-names>Shuang</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lanier</surname><given-names>Kathy</given-names></name><degrees>MPH</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Helman</surname><given-names>Sarit</given-names></name><degrees>MPH</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Cheng</surname><given-names>Nancy F</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Ameli</surname><given-names>Niloufar</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Davidson</surname><given-names>Jays&#x00F3;n</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff7">7</xref><xref ref-type="aff" rid="aff8">8</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Mehta</surname><given-names>Shivani</given-names></name><degrees>MPH, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Hswen</surname><given-names>Yulin</given-names></name><degrees>MPH, SD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff4">4</xref><xref ref-type="aff" rid="aff8">8</xref><xref ref-type="aff" rid="aff9">9</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Oldenburg</surname><given-names>Catherine E</given-names></name><degrees>MPH, SD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff10">10</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Rhoads</surname><given-names>Kim F</given-names></name><degrees>MD, MS, MPH</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref><xref ref-type="aff" rid="aff11">11</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Charlebois</surname><given-names>Edwin D</given-names></name><degrees>MPH, PhD</degrees><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Gansky</surname><given-names>Stuart A</given-names></name><degrees>MS, DrPH</degrees><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff6">6</xref><xref ref-type="aff" rid="aff8">8</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Brown III</surname><given-names>William</given-names></name><degrees>MA, DrPH, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="aff" rid="aff3">3</xref><xref ref-type="aff" rid="aff4">4</xref><xref ref-type="aff" rid="aff8">8</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Epidemiology and Biostatistics, University of California</institution><addr-line>550 16th St., Floor 2</addr-line><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff2"><institution>Division of Preventive Science, Department of Medicine, University of California</institution><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff3"><institution>Research Coordinating Center for Reducing Disparities in Multiple Chronic Diseases, University of California</institution><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff4"><institution>Computational Precision Health, University of California San Francisco and University of California Berkeley</institution><addr-line>Berkeley</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff5"><institution>Social and Behavioral Sciences Branch, Division of Intramural Research, Eunice Kennedy Shriver National Institute of Child Health and Human Development</institution><addr-line>BG 6710 Rockledge Dr Wing B</addr-line><addr-line>Bethesda</addr-line><addr-line>MD</addr-line><country>United States</country></aff><aff id="aff6"><institution>Division of Oral Epidemiology &#x0026; Dental Public Health, University of California</institution><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff7"><institution>Pharmaceutical Science and Pharmacogenomics program, University of California</institution><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff8"><institution>Bakar Computational Health Sciences Institute, University of California</institution><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff9"><institution>College of Computer Mathematical and Natural Science, Department of Epidemiology and Biostatistics, School of Public Health, The Artificial Intelligence Interdisciplinary Institute at Maryland (AIM), University System of Maryland</institution><addr-line>College Park</addr-line><addr-line>MD</addr-line><country>United States</country></aff><aff id="aff10"><institution>Francis I. Proctor Foundation, University of California</institution><addr-line>San Francisco</addr-line><addr-line>CA</addr-line><country>United States</country></aff><aff id="aff11"><institution>Massey Comprehensive Cancer Center, Virginia Commonwealth University</institution><addr-line>Richmond</addr-line><addr-line>VA</addr-line><country>United States</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Luo</surname><given-names>Gang</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Hynes</surname><given-names>Denise</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Ogundeko-Olugbami</surname><given-names>Oluwafunmilayo</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Hyelee Kim, MD, MAS, MS, PhD, Social and Behavioral Sciences Branch, Division of Intramural Research, Eunice Kennedy Shriver National Institute of Child Health and Human Development, BG 6710 Rockledge Dr Wing B, Bethesda, MD, 20817, United States, 1 301-555-6677; <email>char00@snu.ac.kr</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>22</day><month>10</month><year>2026</year></pub-date><volume>5</volume><elocation-id>e93996</elocation-id><history><date date-type="received"><day>09</day><month>03</month><year>2026</year></date><date date-type="rev-recd"><day>08</day><month>08</month><year>2026</year></date><date date-type="accepted"><day>31</day><month>08</month><year>2026</year></date></history><copyright-statement>&#x00A9; Hyelee Kim, Shuang Liang, Kathy Lanier, Sarit Helman, Nancy F Cheng, Niloufar Ameli, Jays&#x00F3;n Davidson, Shivani Mehta, Yulin Hswen, Catherine E Oldenburg, Kim F Rhoads, Edwin D Charlebois, Stuart A Gansky, William Brown III. Originally published in JMIR AI (<ext-link ext-link-type="uri" xlink:href="https://ai.jmir.org">https://ai.jmir.org</ext-link>), 22.10.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR AI, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://www.ai.jmir.org/">https://www.ai.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://ai.jmir.org/2026/1/e93996"/><abstract><sec><title>Background</title><p>The increasing availability of machine-readable research data has created a growing need for efficient large-scale data harmonization (DH). Although large language models (LLMs) show promise for reducing the time and labor required for DH, their effective integration into harmonization workflows remains an important methodological challenge.</p></sec><sec><title>Objective</title><p>This study aims to develop and evaluate a semiautomated, human-in-the-loop (HITL) LLM-assisted DH workflow as a proof of concept across 8 projects within a research consortium focused on disparities in multiple chronic conditions.</p></sec><sec sec-type="methods"><title>Methods</title><p>We developed an LLM-assisted DH workflow that combined preprocessing, semantic mapping, variable response mapping, synthetic data generation, data transformation, and iterative researcher review. Using Generative Pretrained Transformer (GPT-4o) hosted in a secure academic environment, project-specific survey items were mapped to 114 Consortium Common Data Element (CDE) semantic groups. Semantic mapping accuracy was evaluated based on the Consortium&#x2019;s consensus harmonization results. Complete and incomplete semantic mappings were distinguished according to construct overlap, and incomplete mappings requiring context-dependent human judgment were excluded for mapped item pairs and CDE semantic groups with and without HITL review.</p></sec><sec sec-type="results"><title>Results</title><p>Following preprocessing, 884 survey items were included in the DH workflow, of which 812 were mapped to a mean of 79 CDE semantic groups per project. Mean semantic mapping accuracy for item pairs was 95.9% (SD 5.7%) with HITL review and 86.7% (SD 8.6%) without HITL review. At the CDE semantic-group level, the corresponding accuracies were 98.9% (SD 1.7%) and 94.9% (SD 4.0%), respectively. Across projects, omission of valid semantic mappings occurred more frequently than incorrect semantic mappings, particularly for heterogeneous response structures and subjective constructs measured using different instruments. Pipeline components&#x2014;including concept-based preprocessing, iterative prompt refinement, and targeted HITL review&#x2014;improved mapping completeness and supported variable harmonization across heterogeneous datasets.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>This proof-of-concept study demonstrates that the effectiveness of LLM-assisted DH depends more on the design of a structured HITL workflow rather than on the LLM alone. Combining preprocessing, iterative verification, and targeted human oversight improved the efficiency and reliability of DH while preserving researcher judgment for complex mapping decisions.</p></sec></abstract><kwd-group><kwd>large language model</kwd><kwd>human-in-the-loop</kwd><kwd>semiautomation</kwd><kwd>data harmonization</kwd><kwd>common data element</kwd><kwd>social determinants of health</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><sec id="s1-1"><title>Background</title><p>Data harmonization (DH) enables the integration of individual-level data across studies, increasing statistical power to address complex biomedical and public health research questions [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. Unlike approaches like meta-analysis [<xref ref-type="bibr" rid="ref3">3</xref>] or federated learning [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>], which combine study-level results or trained models, DH directly integrates participant-level data for a wide range of research and clinical applications. Over the past 2 decades, numerous approaches have been developed to improve DH across research domains [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref10">10</xref>]. These include standardized information technology platforms and Common Data Models (CDMs), such as BioSHaRE (Biobank Standardization and Harmonization for Research Excellence in the European Union), the Observational Medical Outcomes Partnership (OMOP) CDM in the All of Us, and National Patient-Centered Clinical Research Network (PCORnet) by the Patient-Centered Outcomes Research Institute (PCORI) [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref16">16</xref>].</p><p>Despite these advances, semantic heterogeneity remains a major challenge because similar constructs are often collected using different question wording, response options, or levels of granularity [<xref ref-type="bibr" rid="ref9">9</xref>]. As a result, harmonization frequently requires subjective human judgment and may result in incomplete or inconsistent mappings. To improve data consistency and interoperability, standardized data content and formats should ideally be established before data collection [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. Reflecting this need, the National Institutes of Health (NIH) introduced the 2023 NIH Data Management and Sharing Policy, which recommends the use of common data elements (CDEs) to promote standardized, interoperable, and reusable data in NIH-funded research [<xref ref-type="bibr" rid="ref18">18</xref>].</p><p>The Multiple Chronic Disease Disparities Research (MCD-DR) Consortium (hereafter referred to as the Consortium), also known as the Health Excellence Action Network, is an initiative funded by the National Institute on Minority Health and Health Disparities (NIMHD) [<xref ref-type="bibr" rid="ref19">19</xref>]. Its mission is to prevent and manage multiple chronic conditions among populations disproportionately affected by health disparities [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. The Consortium comprises 11 regional research centers funded through P50 Specialized Center grants, community partners, and the University of California San Francisco (UCSF) Research Coordinating Center, funded through a U24 Resource-Related Project cooperative agreement. To support data integration across diverse studies, the Consortium developed a bidirectional DH framework that combines retrospective harmonization for projects initiated before Consortium CDEs were established with prospective harmonization for projects launched afterward [<xref ref-type="bibr" rid="ref19">19</xref>]. Unlike previous large research consortia, which have primarily relied on retrospective harmonization after project-specific data collection was completed [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref9">9</xref>], this framework enables harmonization throughout the lifecycle of an ongoing research consortium.</p><p>Successful implementation of the Consortium&#x2019;s bidirectional DH framework required sustained collaboration between the Research Coordinating Center and community research centers to build trust and support community-based participatory research and establish consensus on CDEs [<xref ref-type="bibr" rid="ref19">19</xref>]. To facilitate this process, the Research Coordinating Center established the CDE and DH Working Group (hereafter, the Working Group), which included investigators from the Research Coordinating Center and the P50 Centers. Through an iterative consensus process, the Working Group developed a recommended CDE set comprising 55 concepts (43 required and 12 high-value optional) across multiple domains of social determinants of health (also referred to as social drivers of health; SDOH) based on the NIMHD Research Framework [<xref ref-type="bibr" rid="ref22">22</xref>]. The SDOH domains encompassed demographics, neighborhood and physical environment, food insecurity, social and community context, education attainment, economic security, discrimination, disability, and health and clinical care [<xref ref-type="bibr" rid="ref23">23</xref>]. These were operationalized into 178 questionnaire items from the existing validated toolkits (eg, Phenotypes and eXposures [PhenX] Toolkit and Patient-Reported Outcomes Measurement Information System [PROMIS] Global Health, the Accountable Health Communities Health-Related Social Needs Screening Tool, and the All of Us Research Program SDOH Module) (Table S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Details of the CDE data dictionary are publicly available on the Consortium website<ext-link ext-link-type="uri" xlink:href="https://health-excellence-action.org/nih-cde">-</ext-link>. For prospective harmonization, participating projects were strongly encouraged to incorporate these CDEs into their project-specific data dictionaries to improve interoperability and facilitate data reuse.</p><p>Despite these efforts, DH remains labor-intensive and time-consuming because harmonizing semantically heterogeneous variables requires both domain expertise and iterative consensus building [<xref ref-type="bibr" rid="ref24">24</xref>]. The process also demands substantial coordination among researchers and community partners [<xref ref-type="bibr" rid="ref24">24</xref>]. Consequently, developing approaches that reduce the time and resource burden of manual CDE mapping while maintaining mapping accuracy and supporting the internal validity of harmonized data has become an important priority.</p></sec><sec id="s1-2"><title>Related Work</title><p>Information on SDOH is often embedded within unstructured sources, such as clinical notes or datasets collected for purposes other than SDOH research [<xref ref-type="bibr" rid="ref25">25</xref>]. Consequently, natural language processing (NLP) and large language models (LLMs) have demonstrated strong performance in extracting SDOH information from electronic health records (EHRs). For example, 1 study [<xref ref-type="bibr" rid="ref26">26</xref>] reported that LLMs captured 94% of SDOH information (eg, employment, housing, and social support), whereas the <italic>ICD-10</italic> (<italic>International Statistical Classification of Diseases, Tenth Revision</italic>) codes captured only 2% based on human annotation. These findings suggest that LLMs can effectively identify semantically related concepts despite heterogeneous data representations.</p><p>Building on these capabilities, researchers have explored NLP-based approaches to reduce the manual effort required for DH. Traditional NLP methods use rule-based techniques, such as exact and fuzzy matching, together with semantic text representations (ie, embeddings). For instance, Urbanowicz et al [<xref ref-type="bibr" rid="ref27">27</xref>] applied exact and fuzzy matching to harmonize 37,105 medical history records and 58,170 adverse event records from 21 randomized controlled trials of pulmonary arterial hypertension and chronic thromboembolic pulmonary hypertension. Automated exact matching replaced manual mapping for 74.9% of medical history records and 85.5% of adverse event records, substantially reducing manual annotation. Similarly, Blom et al [<xref ref-type="bibr" rid="ref28">28</xref>] used a skip-gram model pretrained on English-language Wikipedia to generate semantic embeddings from metadata, including item names, definitions, response options, to harmonize patient-reported outcome measures across datasets of patients with multimorbidity.</p><p>More recently, transformer-based models have been adopted for large-scale DH tasks [<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>]. For example, Zhou et al [<xref ref-type="bibr" rid="ref30">30</xref>] used BERT (Bidirectional Encoder Representations from Transformers) and a knowledge graph to harmonize cross-institutional EHRs by aligning heterogeneous coding systems across 2 health care institutions. Their approach achieved an area under the receiver operating characteristic curve (AUROC) of 0.92 for identifying similar entity pairs. Mapping performance varied by data type, with medication codes achieving 91.0%&#x2010;97.5% accuracy and laboratory codes achieving 59.1%&#x2010;75.8% accuracy.</p><p>Additionally, researchers have begun applying LLMs not only to information extraction but also broader DH tasks to improve scalability and efficiency [<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>]. For instance, Cho et al [<xref ref-type="bibr" rid="ref32">32</xref>] reported that a fine-tuned small language model (eg, Mistral 7B) outperformed larger LLMs in extracting cancer staging information. In another study, researchers at the National Institute on Aging also used Generative Pretrained Transformer (GPT-4) in the AI-assisted Data Inventory and Verification Environment for Research (DIVER) platform (Center for Alzheimer&#x2019;s and Related Dementias, NIH, and Data Tecnica LLC) to develop CDEs from multiple sources, including existing studies, ontologies, and medical coding systems [<xref ref-type="bibr" rid="ref33">33</xref>]. The researchers used LLMs to generate CDEs from 31 datasets and reported that 94% of the generated metadata fields required no revision.</p><p>In a preliminary study [<xref ref-type="bibr" rid="ref35">35</xref>], we compared the 2 LLM-based pipelines for semantic mapping of data dictionaries from 5 Consortium projects: 1) the zero-shot OpenAI GPT-4-turbo model accessed through an API, and 2) the chat-based version of the same model. The chat interface supports interactive natural-language communication, whereas the API enables fully automated workflows through programming languages, such as Python (Python Software Foundation) or R (R Foundation for Statistical Computing). For identifying the best-matched CDE items for 1305 project questionnaire items, the chat-based approach required approximately 5 days, whereas the fully automated API pipeline completed the task in just 1 day (excluding time required to learn the LLM and develop the Python scripts). The API-based approach achieved a mean semantic mapping accuracy of 80.3% (SD 10.0%) at an additional API cost of US $87 for LLM, while the free chat-based version achieved a slightly higher mean accuracy of 86.6% (SD 13.0%). Performance varied according to the characteristics of each project&#x2019;s data dictionary, suggesting that no single LLM workflow was optimal for all harmonization tasks. Furthermore, the large volume of metadata made it difficult to identify LLM-generated omissions during downstream harmonization. These findings suggested that a semiautomated, human-in-the-loop (HITL) workflow could better balance efficiency, accuracy, and completeness than either approach alone.</p></sec><sec id="s1-3"><title>Study Objectives</title><p>During implementation of the Consortium&#x2019;s bidirectional DH framework, advances in LLMs presented an opportunity to reduce the labor-intensive process of mapping heterogeneous study variables to Consortium CDEs (<xref ref-type="table" rid="table1">Table 1</xref>). Rather than evaluating the LLM in isolation, this proof-of-concept study evaluated the feasibility of integrating LLMs into a structured HITL DH workflow that combines preprocessing, semantic mapping, variable response mapping, and iterative researcher review. Specifically, we examined whether LLM-assisted harmonization could improve the efficiency and scalability of semantic mapping while maintaining expert oversight and mapping accuracy.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Lists and examples of heterogeneities in data dictionaries.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Questionnaire example A</td><td align="left" valign="bottom">Questionnaire example B</td></tr></thead><tbody><tr><td align="left" valign="bottom" colspan="2">List 1. Question for the responder or the family, including the responder (response for families and responder could be different)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>In the last 12 months, did you or other adults in your household ever cut the size of your meals or skip meals because there wasn&#x2019;t enough money for food?</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>In the last 12 months, did you ever cut the size of your meals or skip meals because there wasn&#x2019;t enough money for food?</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 2. Differences in branching logic (changes in meaning by changing the denominator of the variable)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>How often did this happen - almost every month, some months but not every month, or in only 1 or 2 months?</p></list-item><list-item><p>A question was asked in the condition:[12_mos_change_diet] =&#x201C;1&#x201D;</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The same food insecurity question was asked in these conditions: [12_mos_food_money_freq]=&#x201C;1&#x201D; or [12_mos_food_money_freq]=&#x201C;2&#x201D;or [12_mos_afford_balanced_meals]=&#x201C;1&#x201D; or [12_mos_afford_balanced_meals]=&#x201C;2&#x201D; or [12_mos_change_diet]=&#x201C;1&#x201D;</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 3. Differences in response options (we need household size up until 20 to identify the federal poverty levels)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>Household size: 1, 2, 3, 4, 5, 6 or more</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Household size: response options up until 20</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 4. Differences in response options and duration asked in the question (we need to make a consensus if we are going to harmonize these variables and how to map them)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>Over the past 7 days, how often did you engage in moderate sport and recreational activities such as doubles tennis, ballroom dancing, hunting, ice skating, golf without a cart, softball or other similar activities?</p></list-item></list><list list-type="bullet"><list-item><p>0: Never</p></list-item><list-item><p>1: Seldom (1&#x2010;2 days)</p></list-item><list-item><p>2: Sometimes (3&#x2010;4 days)</p></list-item><list-item><p>3: Often (5&#x2010;7 days)</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>In the last 30 days, other than the activities you did for work, on average, how many days per week did you engage in moderate exercise (like walking fast, running, jogging, dancing, swimming, biking, or other similar activities)?</p></list-item></list><list list-type="bullet"><list-item><p>0, 0</p></list-item><list-item><p>1, 1</p></list-item><list-item><p>2, 2</p></list-item><list-item><p>3, 3</p></list-item><list-item><p>4, 4</p></list-item><list-item><p>5, 5</p></list-item><list-item><p>6, 6</p></list-item><list-item><p>7, 7</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 5. Asking in a single question or multiple questions (If there are projects that used a combined questionnaire, we cannot harmonize the questions separately)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>Has lack of transportation kept you from medical appointments or from getting medications?</p></list-item><list-item><p>Has lack of transportation kept you from doing things needed for daily living?</p></list-item><list-item><p>Has lack of transportation been a problem for you?</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>In the past 12 months, has lack of reliable transportation kept you from medical appointments, meetings, work or from getting things needed for daily living?</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 6. Asking about depression using different questionnaires (first question asks about anxiety or depression, whereas the second question asks symptoms of depression)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>Anxiety or depression</p></list-item></list><list list-type="bullet"><list-item><p>I am not anxious or depressed</p></list-item><list-item><p>I am slightly anxious or depressed</p></list-item><list-item><p>I am moderately anxious or depressed</p></list-item><list-item><p>I am severely anxious or depressed</p></list-item><list-item><p>I am extremely anxious or depressed</p></list-item><list-item><p>&#x2212;99, skip</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Over the past 2 weeks, how often have you been bothered by any of the following? Feeling down, depressed, or hopeless?</p></list-item></list><list list-type="bullet"><list-item><p>Not at all</p></list-item><list-item><p>Several Days</p></list-item><list-item><p>More than half the days</p></list-item><list-item><p>Nearly every day</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 7. Asking about stress using different questionnaires (we need to decide whether and how to map these questions)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>Questions from the PSS<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></p></list-item></list><list list-type="bullet"><list-item><p>In the last month, how often have you felt that you were unable to control the important things in your life?</p></list-item><list-item><p>In the last month, how often have you felt confident about your ability to handle your personal problems?</p></list-item><list-item><p>In the last month, how often have you felt that things were going your way?</p></list-item><list-item><p>In the last month, how often have you felt difficulties were piling up so high that you could not overcome them?</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Question from the Accountable Health Communities Health-Related Social Needs Screening Tool</p></list-item><list-item><p>Stress means a situation in which a person feels tense, restless, nervous, or anxious, or is unable to sleep at night because his or her mind is troubled all the time. Do you feel this kind of stress these days?</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 8. Differences in response option values (response mapping needs additional attention to avoid incorrect value mappings)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>Birth state</p></list-item></list><list list-type="bullet"><list-item><p>1, Alabama</p></list-item><list-item><p>2, Alaska</p></list-item><list-item><p>3, Arizona</p></list-item><list-item><p>4, Arkansas</p></list-item><list-item><p>5, California</p></list-item><list-item><p>6, Colorado</p></list-item><list-item><p>7, Connecticut</p></list-item><list-item><p>8, Delaware</p></list-item><list-item><p>9, District of Columbia</p></list-item><list-item><p>10, Florida</p></list-item><list-item><p><bold>:</bold></p></list-item></list><list list-type="bullet"><list-item><p>50, Wisconsin</p></list-item><list-item><p>51, Wyoming</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Birth state</p></list-item></list><list list-type="bullet"><list-item><p>1, Alabama</p></list-item><list-item><p>2, Alaska</p></list-item><list-item><p>3, Arizona</p></list-item><list-item><p>4, Arkansas</p></list-item><list-item><p>5, California</p></list-item><list-item><p>6, Colorado</p></list-item><list-item><p>7, Connecticut</p></list-item><list-item><p>8, Delaware</p></list-item><list-item><p>9, Florida</p></list-item><list-item><p><bold>:</bold></p></list-item><list-item><p>49, Wisconsin</p></list-item><list-item><p>50, Wyoming</p></list-item><list-item><p>51, Washington, D.C.</p></list-item></list></td></tr><tr><td align="left" valign="top" colspan="2">List 9. Differences in question structures (one of the examples that may be missed by human researcher)</td></tr><tr><td align="left" valign="top"><list list-type="bullet"><list-item><p>Does it limit your activities? (Rheumatoid arthritis, 1: Yes, 0: No)</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Do you have chronic muscular or joint issues that cause pain and physical limitation?</p></list-item></list><list list-type="bullet"><list-item><p>1, Yes</p></list-item><list-item><p>0, No</p></list-item><list-item><p>2, Don&#x2019;t know/ Unsure</p></list-item></list><list list-type="bullet"><list-item><p>If yes, what is causing the pain? (Mark all that apply)</p></list-item></list><list list-type="bullet"><list-item><p>Lupus (systemic lupus erythematosus)</p></list-item><list-item><p>Polymyalgia rheumatica</p></list-item><list-item><p>Osteoarthritis</p></list-item><list-item><p>Rheumatoid Arthritis</p></list-item><list-item><p>Other, specify: {muscular_issue_oth}</p></list-item><list-item><p>Don&#x2019;t know/ Unsure</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>PSS: Perceived Stress Scale.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Data: Consortium CDE and Project Dictionaries</title><p>The Consortium CDE dictionary contains 178 items, of which 154 were eligible for mapping. The eligible CDE items consisted exclusively of survey questionnaire items and did not include vital signs, laboratory results, or biospecimen data. Twenty-four items, such as record identifiers and questionnaire instructions, were excluded.</p><p>To facilitate semantic mapping, the study authors (HK and SAG) manually grouped the 154 eligible CDE items into 114 discrete CDE semantic groups according to their broader CDE concepts. These semantic groups were developed specifically for this study to provide an appropriate level of granularity for evaluating semantic mapping accuracy and were not part of the Consortium&#x2019;s original CDE harmonization process. The resulting semantic groups comprised 99 required groups and 15 high-value-optional groups and served as the reference standard for evaluating LLM semantic mapping performance (Table S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Although the Consortium Working Group developed a standardized CDE dictionary, the number and types of CDE semantic groups represented in each project varied depending on investigator decisions and the timing of project initiation (ie, before or after finalization of the Consortium CDE dictionary).</p><p>Among the 41 Consortium projects eligible for CDE mapping (42 projects at the time of writing [July 2026]), we selected 8 studies, each representing a different regional research center (P50), for this proof-of-concept evaluation [<xref ref-type="bibr" rid="ref19">19</xref>]. The characteristics of the included studies are summarized in Table S2 in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. Because 7 of the 8 participating projects were initiated before the Consortium CDE dictionary was finalized, most projects had already developed study-specific data dictionaries. Consequently, substantial variation in questionnaire content and metadata existed across projects, necessitating semantic DH.</p></sec><sec id="s2-2"><title>LLM-Assisted DH Pipeline With HITL</title><p>The DH pipeline consisted of 4 major steps [<xref ref-type="bibr" rid="ref1">1</xref>] semantic mapping [<xref ref-type="bibr" rid="ref2">2</xref>], variable response mapping [<xref ref-type="bibr" rid="ref3">3</xref>], applying the mapping to synthetic project data, and [<xref ref-type="bibr" rid="ref4">4</xref>] pooling mapped variables and restructuring existing CDEs (<xref ref-type="fig" rid="figure1">Figure 1</xref>). Semantic mapping identified project-specific questionnaire items representing the same or compatible constructs as Consortium CDEs. Variable response mapping determined how project-specific response categories should be transformed to align with standardized CDE response formats. The pooling and restructuring step ensured that harmonized variables comprehensively captured each CDE while preserving compatibility with heterogeneous project data structures.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Flowchart of LLM-assisted CDE harmonization workflow. Python was used for preprocessing data dictionaries, including NLP tasks and interactions with the OpenAI API, whereas R was used for data wrangling and transforming synthetic project data into the Consortium CDE formats. CDE: common data element; HITL: human-in-the-loop; LLM: large language model; NIL: natural language processing.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="ai_v5i1e93996_fig01.png"/></fig><p>We implemented a semiautomated, HITL workflow that was adapted to characteristics of each project&#x2019;s data dictionary, including its size, structure, similarity to the Consortium CDE dictionary, and results from previous steps. Rather than applying a fully automated workflow across all projects, we iteratively refined the pipeline, prompts, and programming code to improve mapping accuracy and minimize errors. The chat-based LLM interface was used to prototype prompts, simulate outputs, and assist with code development for the API-based workflow. Researcher oversight was incorporated throughout the pipeline by embedding verification steps into prompts (eg, instructing the LLM to report the number of processed items to detect potential omissions).</p><p>In the pipeline we used the OpenAI GPT-4o model through the UCSF Versa platform (University of California) [<xref ref-type="bibr" rid="ref36">36</xref>], a secure Microsoft Azure AI environment that supports the Health Insurance Portability and Accountability Act (HIPAA)-compliant processing of sensitive research data (<xref ref-type="bibr" rid="ref37">37</xref><ext-link ext-link-type="uri" xlink:href="https://www.zotero.org/google-docs/?bUU2NY">)</ext-link>. Although no personally identifiable information was included in this study, project data dictionaries were harmonized within the secure Versa environment because they were not publicly available. In addition, interactions conducted through the UCSF Versa platform were not retained by the hosted models, thereby protecting data security and privacy. To support reproducibility and collaboration, the API-based workflow was implemented in Jupyter Notebook (version 7.2.2; Project Jupyter) [<xref ref-type="bibr" rid="ref38">38</xref>], which provides an interactive computational environment for Python and R. Python (version 3.9.21) was used for preprocessing data dictionaries, including NLP tasks and interactions with the OpenAI API, whereas R (version 4.4.2) was used for data wrangling (eg, using the <italic>dplyr</italic> package) and transforming synthetic project data into the Consortium CDE formats [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. This combined workflow leveraged the complementary strengths of both programming languages.</p></sec><sec id="s2-3"><title>Data Preprocessing</title><p>Preprocessing procedures were adapted to the size and structure of each project&#x2019;s data dictionary. For dictionaries containing more than 800 questionnaire items, researchers first performed a broad manual screening to identify relevant sections. Metadata from the projects&#x2019; data dictionaries&#x2014;including variable names, section headers, question content, response options, and associated branching logic&#x2014;were programmatically extracted from the CSV-formatted data dictionaries using Python. Based on findings from our preliminary study [<xref ref-type="bibr" rid="ref35">35</xref>], the extracted metadata were divided into concept-based, manageable chunks before semantic mapping to accommodate the token size limitations of LLMs. For example, because comorbidity items represented the largest CDE concept (42 of 154 CDE items), the LLM first identified comorbidity-related items (<xref ref-type="other" rid="box1">Textbox 1</xref>). Additional chunks were created for demographic variables (eg, race, ethnicity, sex, and age) and the remaining questionnaire items.</p><boxed-text id="box1"><title> Table of example prompts used in the pipeline.</title><p><bold>Task</bold></p><p>You are a clinical informaticist who will conduct semantic mapping of 2 datasets.</p><p>Identifying comorbidity items in the data dictionary</p><p>Below is a data dictionary.</p><p>Provide a list_A of comma-separated, quoted &#x2018;variable_name&#x2019; for comorbidities, treatment, and functional limitations, including total numbers.</p><p>Provide a list_B of comma-separated, quoted &#x2018;variable_name&#x2019;,&#x2018;variable_name,&#x2019; which are not for comorbidities, treatment, and functional limitations, including total numbers.</p><p>Provide a list_C which is not included in list_A or list_B.</p><p>List A: &#x2019;scq_covid19&#x2019;,&#x2018;scq_covid19,&#x2019;&#x2019;scq_heart'&#x2019;</p><p><bold>Explanation</bold></p><list list-type="bullet"><list-item><p>Although this prompt was aimed to identify item lists for comorbidities and the related questions (treatment and functional limitations), we want to see the rest of the items to see if there were any omitted items in the list A</p></list-item><list-item><p>Additionally, we wanted only variable names included in the list. Therefore, we provided the example list to the model</p></list-item><list-item><p>To prevent unexpected omissions, we requested to provide the numbers in each list</p></list-item></list><p><bold>Task</bold></p><p>Identifying the variable response mapping</p><p>'df_vt'&#x2019; is the data dictionary for matched variables from CDE and project.</p><p>Included information: variable name, section header, question content, response, branching logic</p><p>'project_b'&#x2019; is a project data (includes missing observation). We have a csv file of project_b. No need to include code to generate '&#x2019;project_b'&#x2019;</p><p>Provide an R code to transform a project variable presented in former columns to the CDE variable presented in latter columns in the same row. Name it '&#x2019;transformed_data'&#x2019;</p><p>The beginning of R code includes copying &#x2018;project_b&#x2019; data frame as '&#x2019;transformed_data'&#x2019;</p><p><bold>Explanation</bold></p><list list-type="bullet"><list-item><p>We informed which information each data dictionary contains.</p></list-item><list-item><p>We clarified that we do not need coding for generating synthetic data to prevent unnecessary token usage.</p></list-item><list-item><p>We provided information about the position of CDE and project presented in a same row</p></list-item><list-item><p>To maintain consistency in coding, we instructed to start from copying the project data.</p></list-item></list></boxed-text><p>During the previous study, we observed that instructional text was occasionally mapped to questionnaire items because of semantic similarity. For example, instructions preceding family income questions were incorrectly mapped to the family income question CDE. To address this issue, we restructured the metadata by incorporating relevant instructions into the corresponding section headers rather than treating them as separate items, enabling the LLM to better capture the relationships between instructions and questionnaire items. The semantic harmonization analysis was limited to English-language questionnaire content. When project data dictionaries contained bilingual (English and Spanish) questionnaire items, only the English text was included in the LLM input to reduce token length and improve processing efficiency. The token size for CDE dictionary was divided into 3 chunks: comorbidities (2.4 thousand tokens), demographics (3.7 thousand tokens), and all remaining items (10.9 thousand tokens), resulting in a total of 17.0 thousand tokens.</p></sec><sec id="s2-4"><title>Semantic Mapping Using LLMs</title><p>For semantic mapping, metadata from both the Consortium CDE dictionary and each project data dictionary, including variable names, section headers, questionnaire items, response options, and branching logic, were provided to the LLM as structured prompt input organized into concept-based chunks (eg, comorbidities, demographics, and remaining questionnaire items) (<xref ref-type="fig" rid="figure1">Figure 1</xref>). The LLM was then prompted to identify semantically corresponding questionnaire items and generate mapping clusters between the project and Consortium CDE dictionaries.</p><p>Several strategies were additionally incorporated to improve mapping performance. Prompts required the LLMs to explicitly report unmapped items to minimize omissions, and additional instructions clarified item ordering and formatting to reduce ambiguity. Following each mapping task, researchers reviewed the LLM-generated clusters, corrected mapping errors if necessary, and approved the results before proceeding to variable response mapping. Mapped items were organized according to CDE item numbers, whereas unmapped project items were flagged for further review to determine whether additional harmonization was possible. This process was repeated for every chunk across all 8 projects.</p><p>For evaluation, semantic mapping results were classified as either complete or incomplete according to the degree of conceptual overlap between project items and the corresponding CDEs (ie, complete vs partial construct overlap).</p></sec><sec id="s2-5"><title>Variable Response Mapping, Data Transformation, and Harmonized Variable Restructuring</title><p>Semantic mapping results were stored in 2 complementary formats: [<xref ref-type="bibr" rid="ref1">1</xref>] CDE semantic group-specific files (one file for each of the 114 semantic groups), and [<xref ref-type="bibr" rid="ref2">2</xref>] project-specific mapping files (one file per project). Project-specific mapping files were initially used to transform project variables into the corresponding Consortium CDE formats. However, differences in response categories across projects often required additional harmonization. For example, the Consortium CDE for educational attainment included more detailed response categories than those collected in some individual projects. To establish consistent harmonization rules, project variables belonging to the same CDE semantic group were consolidated across projects and reviewed collectively. The LLM then analyzed the grouped variables, identified similarities and differences in response structures, and suggested candidate harmonization strategies while highlighting discrepancies among projects (<xref ref-type="other" rid="box2">Textbox 2</xref>).</p><boxed-text id="box2"><title> Example of items related to a discrete Common Data Element (CDE) construct collected across the studies and large language model (LLM)&#x2019;s analysis for data harmonization (DH).</title><p>Prompt</p><p>'df'&#x2019; is the data dictionary for matched variables from CDE and projects.</p><p>Included information: variable name, section header, question content, response, branching logic</p><p>Based on the information, could you suggest how to harmonize the presented variables? Develop a new CDE item that can harmonize them.</p><p>If you find any problems from harmonizing them, describe what they are.</p><p>Response</p><p>To harmonize the presented variables from different projects, we need to create a comprehensive set of questions and responses that can incorporate the different aspects covered by these datasets. We can start by assessing the commonalities and differences in the datasets and then suggest a unified approach.</p><p>### Commonalities:</p><list list-type="order"><list-item><p>**Domain**: Most datasets consider trouble paying for basic needs such as housing, heat and electricity, medical needs, transportation, childcare, and debts.</p></list-item><list-item><p>**Response Options**: The response options are fairly consistent across datasets, usually including "Yes",&#x201C;Yes,&#x201D; "No",&#x201C;No,&#x201D; and a "&#x201C;Prefer not to answer"&#x201D; option.</p></list-item><list-item><p>**Time Frame**: Most instruments refer to the past three months.</p></list-item></list><p>(omitted)</p><p>### Problems and Considerations:</p><list list-type="order"><list-item><p>**Response Recoding**: The harmonized dataset will need to reconcile differences in response coding to ensure consistency, eg, standardizing "Prefer not to answer" to -88.</p></list-item><list-item><p>**Data Loss or Detail Reduction**: There is a risk of losing specific nuances provided by more detailed response options or specialized questions in the original datasets.</p></list-item><list-item><p>**Aggregation of "&#x201C;Other"&#x201D; Responses**: The utility of an "&#x201C;Other"&#x201D; category depends on the detail provided by respondents. Therefore, aggregation and harmonization may lead to merged data that lacks clarity.</p></list-item><list-item><p>**Compatibility with Existing Systems**: Harmonizing may require changes in how data systems currently store and process responses, potentially requiring reevaluation of data models.</p></list-item></list><p>Establishing this new harmonized CDE item will create a more comprehensive yet standardized approach, allowing for consistent cross-dataset analysis while minimizing information loss.</p></boxed-text><p>For variable response mapping, we used the <italic>rpy2</italic> package within the IPython kernel to enable seamless integration of Python and R in a single Jupyter Notebook environment. Synthetic project data (10 observations per project) were generated by the LLM from each project&#x2019;s data dictionary to simulate the variable transformation procedure without actual project data. Using the semantic mapping results, the LLM generated code to transform project-specific variables into standardized Consortium CDE formats. To improve coding accuracy, transformations were generated and validated iteratively in small batches of 5&#x2010;10 variables. When errors were identified, prompts and generated code were refined before the transformation was repeated. For complex mappings involving one-to-many or many-to-many relationships (eg, a single diabetes variable containing both diagnosis and treatment information), all relevant variables were presented simultaneously to enable LLM to generate appropriate transformation rules.</p><p>Variable response mapping results were classified as either complete or incomplete. Incomplete mappings represented situations in which multiple harmonization strategies were reasonable because of differences in variable structure or response categories across studies (eg, mapping multiple-choice and single-choice race variables). These mappings were excluded from automated variable transformation in this proof-of-concept study. Throughout the pipeline, prompts and input data were iteratively refined to improve transformation accuracy. Overall, the pipeline was designed to support iterative collaboration between researchers and the LLM rather than fully automate the DH.</p></sec><sec id="s2-6"><title>Evaluation of LLM Performance</title><p>Because incomplete semantic mappings required context-dependent human judgment, they were excluded from accuracy evaluation. Such mappings often involve multiple reasonable harmonization strategies depending on the intended research question, such as harmonizing variables with different categorizations (eg, race, insurance, or comorbidities) or determining whether conceptually related but nonidentical questionnaire items should be combined. Including incomplete mappings would therefore make the evaluation dependent on subjective scoring decisions rather than objective semantic agreement. Accordingly, incomplete mappings were excluded from both the numerator and denominator when calculating semantic mapping accuracy.</p><p>To evaluate the contribution of human oversight, mapping accuracy was compared before and after researcher review (ie, with HITL correction). Semantic mapping accuracy was evaluated at 2 levels. First, accuracy was calculated for individual semantically mapped item pairs as the percentage of correctly mapped project-CDE pairs among all complete semantic mappings. Because a single project item could correspond to multiple CDE items (or vice versa), the total number of mapped pairs varied across projects depending on the final harmonization decisions.</p><disp-formula id="E1"> <label>(1)</label><mml:math id="eqn1"><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd/><mml:mtd><mml:mtext>Accuracy of semantically mapped item pairs</mml:mtext></mml:mtd></mml:mtr><mml:mtr><mml:mtd/><mml:mtd><mml:mi/><mml:mo>=</mml:mo><mml:mfrac><mml:mtext>The number of correctly mapped pairs</mml:mtext><mml:mtext>Total number of complete semantic mappings</mml:mtext></mml:mfrac><mml:mo>&#x00D7;</mml:mo><mml:mn>100</mml:mn></mml:mtd></mml:mtr></mml:mtable></mml:mstyle></mml:mrow></mml:mstyle></mml:math></disp-formula><p>Second, accuracy was evaluated at the CDE semantic-group level to account for differences in the importance and granularity of individual questionnaire items. Semantic-group accuracy was defined as the percentage of correctly mapped CDE semantic groups among all complete semantic groups represented in a project&#x2019;s data dictionary (maximum of 114 groups). A semantic group was considered correctly mapped when the project&#x2019;s key concepts were accurately aligned with the corresponding Consortium CDE semantic group. The 2 metrics provide complementary evaluations: item-level accuracy reflects the correctness of individual semantic mappings, whereas semantic-group accuracy assesses whether the intended CDE constructs were successfully identified.</p><disp-formula id="E2"> <label>(2)</label><mml:math id="eqn2"><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mrow><mml:mstyle displaystyle="true" scriptlevel="0"><mml:mtable columnalign="right left right left right left right left right left right left" rowspacing="3pt" columnspacing="0em 2em 0em 2em 0em 2em 0em 2em 0em 2em 0em" displaystyle="true"><mml:mtr><mml:mtd/><mml:mtd><mml:mtext>Accuracy of CDE semantic group</mml:mtext></mml:mtd></mml:mtr><mml:mtr><mml:mtd/><mml:mtd><mml:mi/><mml:mo>=</mml:mo><mml:mfrac><mml:mtext>The number of correctly mapped CDE groups</mml:mtext><mml:mtext>Total number of complete CDE group mappings</mml:mtext></mml:mfrac><mml:mo>&#x00D7;</mml:mo><mml:mn>100</mml:mn></mml:mtd></mml:mtr></mml:mtable></mml:mstyle></mml:mrow></mml:mstyle></mml:math></disp-formula><p>The reference standard for evaluating mapping accuracy was the final semantic mapping established through the Consortium&#x2019;s DH process. Because harmonization began at different times across projects, the initial mapping approach varied. One project initially used an NLP-based fuzzy matching approach, whereas another project completed semantic and variable mapping independently and shared the results with the Research Coordinating Center. Regardless of the initial approach, all projects subsequently followed the same consensus workflow. First, the initial semantic mappings generated by the LLM (GPT-4-turbo in the UCSF Versa platform) were reviewed by the individual project team to identify inaccuracies and provide domain-specific feedback. Second, the Research Coordinating Center integrated project feedback and reached internal consensus. Finally, mappings that remained controversial after this review were discussed during the Consortium&#x2019;s monthly Working Group meetings. The resulting consensus mappings served as the reference standard for evaluating LLM performance. We also recorded the total API cost and processing time required to complete the harmonization workflow across all eight projects. Although prompt length was reduced when necessary (eg, by excluding duplicate Spanish-language questionnaire text) to remain within the LLM context window, token usage itself was not evaluated as a study outcome.</p></sec><sec id="s2-7"><title>Ethical Considerations</title><p>No personally identifiable information, or participant interactions were included in this study. Project metadata (ie, data dictionaries) were analyzed within the secure UCSF Versa environment because these materials were not publicly available. Access was restricted to authorized UCSF researchers. The UCSF Institutional Review Board determined that this study was exempt from review (protocol #21&#x2010;35033).</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Overall DH Performance</title><p>Across all 8 projects, the workflow successfully integrated LLM-assisted semantic mapping, variable response mapping, and iterative researcher review. Following preprocessing, 884 questionnaire items from the 8 project data dictionaries were included in the DH pipeline. Of these, 812 items (812/884, 91.9% of eligible questionnaire items and 812/903, 90.0% of all data dictionary items) were semantically mapped to a mean of 79 CDE semantic groups per project, including incomplete semantic mappings (Table S3 <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). The number of projects represented within each CDE semantic group varied across the Consortium. <xref ref-type="fig" rid="figure2">Figure 2</xref> summarizes the distribution of topic entities across projects.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Chord diagram of topic entities included in the projects the chord diagram illustrates the relationships between the 8 consortium projects and the 15 topic entities represented in their data dictionaries. Each ribbon indicates that a project includes data related to the corresponding topic entity. For example, project 1 includes 4 topic entities: cardiovascular disease, hypertension, children, and community health workers. Likewise, the cardiovascular disease topic is represented in 5 projects (projects 1, 4, 5, 6, and 8). The diagram provides an overview of the distribution of research topics across projects and highlights similarities and differences in their thematic focus.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="ai_v5i1e93996_fig02.png"/></fig><p>After excluding incomplete semantic mappings (Table S4 in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>), the mean accuracy of semantically mapped item pairs was 95.9% (SD 5.7%) with HITL review and 86.7% (SD 8.6%) without HITL review. At the CDE semantic-group level, the corresponding mean accuracies were 98.9% (SD 1.7%) and 94.9% (SD 4.0%), respectively (<xref ref-type="table" rid="table2">Table 2</xref>). The complete LLM-assisted DH workflow across all 8 projects processed approximately 2.4 million tokens and incurred a total API cost of US $11.44. The LLM also generated recommendations for harmonizing variables with heterogeneous response structures across projects, providing guidance for variable response mapping and data transformation (Table S5 in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>).</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Accuracy of semantically mapped item pairs with and without HITL<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup> according to projects<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup>.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Number of eligible items</td><td align="left" valign="bottom">Project</td><td align="left" valign="bottom">Mapped item pairs<break/>(% of incomplete mappings)<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup></td><td align="left" valign="bottom">Item pair accuracy (%)<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup></td><td align="left" valign="bottom">Semantic group accuracy (%)<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup></td><td align="left" valign="bottom">Mapped item pairs (% of incomplete mappings)<sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup></td><td align="left" valign="bottom">Item pair accuracy (%)<sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup></td><td align="left" valign="bottom">Semantic group accuracy (%)<sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup></td><td align="left" valign="bottom">Total number of mapped semantic groups</td></tr></thead><tbody><tr><td align="left" valign="top">1</td><td align="left" valign="top">127</td><td align="left" valign="top">125 (0)</td><td align="left" valign="top">96.1</td><td align="left" valign="top">96.4</td><td align="left" valign="top">124 (0)</td><td align="left" valign="top">100.0</td><td align="left" valign="top">100.0</td><td align="left" valign="top">84</td></tr><tr><td align="left" valign="top">2</td><td align="left" valign="top">118</td><td align="left" valign="top">94 (13.8)</td><td align="left" valign="top">84.4</td><td align="left" valign="top">93.8</td><td align="left" valign="top">97 (14.4)</td><td align="left" valign="top">85.6</td><td align="left" valign="top">95.5</td><td align="left" valign="top">75</td></tr><tr><td align="left" valign="top">3</td><td align="left" valign="top">79</td><td align="left" valign="top">50 (12.0)</td><td align="left" valign="top">69.8</td><td align="left" valign="top">86.0</td><td align="left" valign="top">70 (11.4)</td><td align="left" valign="top">100.0</td><td align="left" valign="top">100.0</td><td align="left" valign="top">52</td></tr><tr><td align="left" valign="top">4</td><td align="left" valign="top">131</td><td align="left" valign="top">123 (4.9)</td><td align="left" valign="top">97.4</td><td align="left" valign="top">96.7</td><td align="left" valign="top">117 (2.6)</td><td align="left" valign="top">100.0</td><td align="left" valign="top">100.0</td><td align="left" valign="top">91</td></tr><tr><td align="left" valign="top">5</td><td align="left" valign="top">126</td><td align="left" valign="top">123 (0)</td><td align="left" valign="top">82.9</td><td align="left" valign="top">97.8</td><td align="left" valign="top">123 (0)</td><td align="left" valign="top">100.0</td><td align="left" valign="top">100.0</td><td align="left" valign="top">90</td></tr><tr><td align="left" valign="top">6</td><td align="left" valign="top">71</td><td align="left" valign="top">50 (8.0)</td><td align="left" valign="top">86.3</td><td align="left" valign="top">97.4</td><td align="left" valign="top">60 (16.7)</td><td align="left" valign="top">94.3</td><td align="left" valign="top">97.6</td><td align="left" valign="top">45</td></tr><tr><td align="left" valign="top">7</td><td align="left" valign="top">129</td><td align="left" valign="top">122 (0)</td><td align="left" valign="top">89.1</td><td align="left" valign="top">98.0</td><td align="left" valign="top">122 (0)</td><td align="left" valign="top">89.1</td><td align="left" valign="top">98.0</td><td align="left" valign="top">101</td></tr><tr><td align="left" valign="top">8</td><td align="left" valign="top">122</td><td align="left" valign="top">102 (1.0)</td><td align="left" valign="top">87.3</td><td align="left" valign="top">93.0</td><td align="left" valign="top">112 (4.5)</td><td align="left" valign="top">98.2</td><td align="left" valign="top">100.0</td><td align="left" valign="top">86</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>HITL: human-in-the-loop.</p></fn><fn id="table2fn2"><p><sup>b</sup>Accuracy was calculated after excluding incomplete semantic mappings. The Consortium common data element (CDE) dictionary contains 154 questionnaire items eligible for semantic mapping, grouped into 114 discrete common data element (CDE) semantic groups (99 required and 15 high-value-optional). Because projects initiated before the development of the Consortium common data element (CDE) dictionary could not modify their existing data dictionaries (ie, retrospective harmonization), the number of common data element (CDE) semantic groups represented varied across projects. Therefore, differences in the total number of mapped semantic groups shown in the final column are expected.</p></fn><fn id="table2fn3"><p><sup>c</sup>Without HITL.</p></fn><fn id="table2fn4"><p><sup>d</sup>With HITL.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2"><title>Project-Specific Mapping Characteristics</title><p>Although semantic mapping performance varied across projects because of differences in data dictionary content and structure, several consistent patterns emerged. <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> represents the DH results across eight projects according to semantic CDE groups. Across all 8 projects, omission of valid semantic mapping was a more frequent source of error than incorrect semantic mappings. Omission errors occurred primarily when variables required one-to-many or many-to-many mappings or when conceptually similar constructs were measured using different questionnaires. These findings highlight the importance of researcher review during semantic mapping, particularly for heterogeneous response structures and subjective constructs.</p><sec id="s3-2-1"><title>Project 1</title><p>Project 1 primarily consisted of questionnaire items corresponding to the required Consortium CDEs. Minor differences included additional response options (eg, Middle Eastern and North African [MENA] race) and social needs questions introduced after the project was initiated. With HITL review, all 124 eligible items were correctly mapped to 84 CDE semantic groups without omissions. Without HITL, omission of 2 standard response-option items (ie, &#x2212;77 for &#x201C;Don&#x2019;t know&#x201D;, and &#x2212;88 for &#x201C;Prefer not to answer&#x201D;) and incorrect mapping of COVID-19 comorbidity questions (ie, past vs current) reduced semantic group accuracy from 100% to 96.4%.</p></sec><sec id="s3-2-2"><title>Projects 2 and 6</title><p>These projects contained substantial structural differences from the Consortium CDEs, including variations in insurance, race, household income, and comorbidity questions. Consequently, one-to-many, and many-to-many mappings were common, and frequently required researcher judgment. Although overall semantic group accuracy remained relatively high, incomplete mappings were common because multiple harmonization strategies were possible. For example, the Consortium CDE included items on heart disease diagnosis and its treatment, which asked about the current diagnosis and treatment of heart diseases. In contrast, the corresponding Project 2 questions asked about the current and past diagnosis of heart attack and the current and past treatment for heart failure (heart attacks and heart failure are related but not the same). Similarly, questions about kidney disease and lung disease did not explicitly ask about treatment or functional limitations from diseases like Consortium CDEs but included treatment in the disease item description that indirectly suggested functional limitations, such as hemodialysis, peritoneal dialysis, and kidney transplantation. Variable response mapping also required additional review when response categories differed between the project and CDE formats. As presented in Table S3 in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>, the semantically mapped race items were classified as incomplete mappings due to differences in question logic, demonstrating difficulties in harmonizing race obtained from different question structures.</p></sec><sec id="s3-2-3"><title>Projects 3, 6, and 8</title><p>Subjective constructs measured using different validated instruments, including depression, stress, and loneliness, were particularly challenging for fully automated mapping. The LLM often omitted these items when the questionnaire wording differed from the Consortium CDEs (ie, depression measured with Patient Health Questionnaire vs PSS), even when the underlying constructs were conceptually related. In these cases, HITL review successfully identified additional candidate mappings but researcher judgment remained necessary because complete harmonization depended on study-specific analytic objectives.</p></sec><sec id="s3-2-4"><title>Projects 4, 5, and 7</title><p>These projects largely consisted of questionnaire items corresponding to the Consortium CDEs and achieved semantic group accuracies of 98%&#x2010;100%. Nevertheless, subtle differences in branching logic, response options, and question structure still required manual review. Examples include multiple-choice versus single-choice insurance questions, household income collected using federal poverty level threshold categories rather than income ranges, and repeated one-to-many mappings for social needs questions.</p></sec></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>This proof-of-concept study demonstrates that successful LLM-assisted DH depends on the design of the overall workflow rather than on the LLM alone. Applied to 8 Consortium projects, the pipeline successfully integrated LLMs into semantic mapping, variable response mapping, and data transformation while preserving researcher oversight throughout the harmonization process. The relatively high mapping accuracy observed in this study was facilitated, in part, by the Consortium&#x2019;s bidirectional harmonization framework, in which the Consortium CDEs were developed through an iterative consensus process involving community research centers, the Research Coordinating Center, and other stakeholders.</p></sec><sec id="s4-2"><title>Value of HITL</title><p>Although semantic mapping accuracy was high both with and without HITL review, researcher involvement consistently reduced omission errors and incorrect mappings while producing more consistent performance across projects. Notably, omission of valid semantic mappings occurred more frequently than incorrect semantic mappings. These omissions were most common when variables required one-to-many or many-to-many mappings or when conceptually similar constructs were measured using different questionnaires. Subjective constructs, including depression, stress, and loneliness, were particularly challenging because different validated instruments measured similar concepts using different wording and response structures. These findings suggest that human review should be prioritized for variables with heterogeneous response formats and subjective constructs rather than uniformly applied across all semantic mappings. The need for HITL is likely to decrease as participating studies adopt standardized CDEs prospectively after the Consortium CDE&#x2019;s launch, although researcher oversight will probably remain necessary for heterogeneous response structures and subjective constructs.</p></sec><sec id="s4-3"><title>Pipeline Design Matters</title><p>Our findings demonstrate that successful LLM-assisted harmonization depends not only on model capability but also on thoughtful pipeline design. Providing clear and specific instructions to the LLM reduced errors during both semantic and variable response mapping. Dividing large data dictionaries into concept-based chunks, providing complete metadata (including section headers and branching logic), and incorporating explicit verification steps into prompts all improved mapping accuracy and reduced omissions. Similarly, restructuring metadata during preprocessing enabled the LLM to better distinguish questionnaire instructions from survey items, highlighting the importance of data preparation in addition to prompt engineering.</p></sec><sec id="s4-4"><title>Human Factors Matter</title><p>Our experience also showed that successful workflow design must account for human cognitive workload in addition to LLM performance. Although we initially explored a fully automated workflow, an iterative HITL review approach proved more practical. Fully automated approaches generated comprehensive outputs but also increased computational cost, development time, and the cognitive burden associated with reviewing lengthy LLM responses. As the output volume increased, researchers were more likely to overlook omitted or incorrect mappings despite repeated review. This observation is consistent with previous studies suggesting that overreliance on AI-generated recommendations can adversely affect human decision making when AI outputs contain systematic errors [<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Consequently, dividing harmonization into smaller, verifiable steps was more effective than attempting end-to-end automation. In our experience, rather than replacing human expertise, LLMs were more effective when supporting researchers in a structured, iterative workflow. This human-centered approach is also consistent with the Belmont Principles of beneficence, respect for persons, and justice, that emphasize responsible use of AI in research [<xref ref-type="bibr" rid="ref43">43</xref>,<xref ref-type="bibr" rid="ref44">44</xref>].</p></sec><sec id="s4-5"><title>Implications for Future Research Consortia</title><p>Our findings also have implications for the design of future multicenter research consortia. Establishing data governance policies, standardized CDEs, and harmonization expectations at study initiation can substantially reduce semantic heterogeneity and facilitate downstream DH [<xref ref-type="bibr" rid="ref19">19</xref>]. However, prospective standardization alone is unlikely to eliminate the need for HITL review. Study-specific adaptations, evolving research objectives, and differences in questionnaire implementation can introduce semantic ambiguity that requires domain expertise to resolve. In our experience, conceptually complex variables, response value mappings, and context-dependent questionnaire items were more likely to benefit from expert review. Rather than replacing human expertise, LLMs may be most effective as decision-support tools that accelerate harmonization while allowing investigators to focus on the relatively small number of challenging mappings requiring expert consensus.</p></sec><sec id="s4-6"><title>Limitations</title><p>This proof-of-concept study has several limitations. First, the workflow simplified several aspects of real-world DH. For example, missing data mechanisms and differences arising from branching logic or unavailable response categories were simplified for this evaluation. Second, although this AI-implemented pipeline reduced the manual effort required for semantic mapping and variable transformation, actual consortium-wide harmonization also involves substantial time for data sharing, updating data dictionaries, communication among investigators, and consensus building, which were not fully represented in this study [<xref ref-type="bibr" rid="ref9">9</xref>].</p><p>Third, this study included 8 projects selected as a proof of concept, whereas the Consortium ultimately comprises 41 projects. As the number and diversity of participating projects increase, semantic heterogeneity and harmonization complexity are also expected to increase. Although prospective data governance and standardized CDEs can facilitate harmonization, the high mapping accuracy observed in this study should not be generalized to larger or more heterogeneous harmonization efforts without careful consideration.</p><p>Finally, this study did not evaluate the environmental impact or long-term sustainability of LLM-assisted harmonization. Further research should examine how to balance the efficiency gains proved by LLMs with their computational costs and broader sustainability implications [<xref ref-type="bibr" rid="ref45">45</xref>-<xref ref-type="bibr" rid="ref47">47</xref>].</p></sec><sec id="s4-7"><title>Conclusion</title><p>This proof-of-concept study demonstrates that an LLM-assisted, HITL DH workflow can improve the efficiency of harmonizing heterogeneous research data while maintaining high semantic mapping accuracy. Rather than replacing researcher expertise, LLMs were most effective when integrated into a structured workflow that combined semantic mapping, variable response mapping, iterative verification, and human oversight.</p><p>These findings provide practical guidance for researchers seeking to incorporate LLMs into DH workflows, particularly when harmonizing questionnaire-based data and SDOH CDEs. Our results also highlight that careful preprocessing, prompt design, and targeted human review are essential for handling heterogeneous response structures and subjective constructs measured using different instruments.</p><p>Future research should evaluate the scalability of this approach in larger and more heterogeneous research consortia, refine harmonization strategies for complex variable structures, and develop transparent, reproducible workflows for LLM-assisted DH. Such efforts will help maximize the value of harmonized research data for secondary analyses while supporting the responsible, and human-centered use of AI in biomedical research.</p></sec></sec></body><back><ack><p>We gratefully acknowledge the participants, families, and researchers of the Multiple Chronic Disease Disparities Research Consortium for their contributions to this work. We also thank the University of California San Francisco (UCSF) AI Tiger Team, UCSF Academic Research Services, UCSF Research Information Technology, and the UCSF Chancellor&#x2019;s Task Force for Generative AI for their software development, analytical and technical support related to the use of UCSF Versa. During the preparation of this work, the author used (Generative Pretrained Transformer) GPT-4o and GPT&#x2011;5.3 in order to check grammar and improve readability. After using this tool or service, the authors reviewed and edited the content as needed and took full responsibility for the content of the published article.</p></ack><notes><sec><title>Funding</title><p>Research reported in this publication was supported by the National Institute on Minority Health and Health Disparities of the National Institutes of Health (NIH) under Award Numbers U24MD017250 and U24MD017250-S1. WB III has been supported by NIH/National Institute on Drug Abuse (NIDA) K01DA055081 and an institutional NIH T32MD015070 at the University of California, San Francisco. HK's contribution to this work is funded in part by the Intramural Research Program of the <italic>Eunice Kennedy Shriver</italic> National Institute of Child Health and Human Development, National Institutes of Health, through an Intramural Research Training Award. HK's contribution is considered a Work of the United States Government. The findings and conclusions presented in this paper are those of the NIH author and do not necessarily reflect the views of the NIH or the U.S. Department of Health and Human Services.</p></sec><sec><title>Data Availability</title><p>The Consortium Common Data Element (CDE) dictionary is publicly available on the Multiple Chronic Disease Disparities Research website [<xref ref-type="bibr" rid="ref48">48</xref>].</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: SL, JD, SM, YH, CEO, SAG, WB III</p><p>Data curation: SL, KL, SH, NFC, NA</p><p>Formal analysis: HK, WB III</p><p>Funding acquisition: KR, EDC, SAG</p><p>Investigation: HK, SL</p><p>Methodology: HK</p><p>Project administration: KL</p><p>Resources: SH, NA</p><p>Supervision: SAG, WB III</p><p>Validation: NFC, JD, SM, YH, CEO.</p><p>Visualization: HK.</p><p>Software: SL, NA.</p><p>Writing &#x2013; original draft: HK, WB III.</p><p>Writing &#x2013; review &#x0026; editing: HK, SL, KL, SH, NFC, NA, JD, SM, YH, CEO, KR, EDC, SAG.</p></fn><fn fn-type="conflict"><p>SM is an employee of Abbott Diabetes Care. The remaining authors declare that they have no known competing financial interests or personal relationships that could have appeared to influence the work reported in this paper.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AUROC</term><def><p>area under the receiver operating characteristic curve</p></def></def-item><def-item><term id="abb2">BERT</term><def><p>Bidirectional Encoder Representations from Transformers</p></def></def-item><def-item><term id="abb3">BioSHaRE</term><def><p>Biobank Standardization and Harmonization for Research Excellence in the European Union</p></def></def-item><def-item><term id="abb4">CDE</term><def><p>Common Data Element</p></def></def-item><def-item><term id="abb5">CDM</term><def><p>Common Data Model</p></def></def-item><def-item><term id="abb6">DH</term><def><p> data harmonization</p></def></def-item><def-item><term id="abb7">DIVER</term><def><p>Data Inventory and Verification Environment for Research</p></def></def-item><def-item><term id="abb8">EHR</term><def><p>electronic health record</p></def></def-item><def-item><term id="abb9">GPT</term><def><p>Generative Pretrained Transformer</p></def></def-item><def-item><term id="abb10">HIPAA</term><def><p>Health Insurance Portability and Accountability Act</p></def></def-item><def-item><term id="abb11">HITL</term><def><p>human-in-the-loop</p></def></def-item><def-item><term id="abb12"><italic>ICD-10</italic></term><def><p><italic>International Statistical Classification of Diseases, Tenth Revision</italic></p></def></def-item><def-item><term id="abb13">LLM</term><def><p>large language model</p></def></def-item><def-item><term id="abb14">MCD-DR</term><def><p>Multiple Chronic Disease Disparities Research</p></def></def-item><def-item><term id="abb15">MENA</term><def><p>Middle Eastern and North African</p></def></def-item><def-item><term id="abb16">NIH</term><def><p>National Institutes of Health</p></def></def-item><def-item><term id="abb17">NIHMD</term><def><p>National Institute on Minority Health and Health Disparities</p></def></def-item><def-item><term id="abb18">NLP</term><def><p>natural language processing</p></def></def-item><def-item><term id="abb19">OMOP</term><def><p>Observational Medical Outcomes Partnership</p></def></def-item><def-item><term id="abb20">PCORI</term><def><p>Patient-Centered Outcomes Research Institute</p></def></def-item><def-item><term id="abb21">PCORnet</term><def><p>National Patient-Centered Clinical Research Network</p></def></def-item><def-item><term id="abb22">PhenX</term><def><p>Phenotypes and eXposures</p></def></def-item><def-item><term id="abb23">PROMIS</term><def><p>Patient-Reported Outcomes Measurement Information System</p></def></def-item><def-item><term id="abb24">UCSF</term><def><p>University of California San Francisco</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Adhikari</surname><given-names>K</given-names> </name><name name-style="western"><surname>Patten</surname><given-names>SB</given-names> </name><name name-style="western"><surname>Patel</surname><given-names>AB</given-names> </name><etal/></person-group><article-title>Data harmonization and data pooling from cohort studies: a practical approach for data management</article-title><source>Int J Popul Data Sci</source><year>2021</year><volume>6</volume><issue>1</issue><fpage>1680</fpage><pub-id pub-id-type="doi">10.23889/ijpds.v6i1.1680</pub-id><pub-id pub-id-type="medline">34888420</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>Pan</surname><given-names>K</given-names> </name><name name-style="western"><surname>Bazzano</surname><given-names>LA</given-names> </name><name name-style="western"><surname>Betha</surname><given-names>K</given-names> </name><etal/></person-group><article-title>Large-scale data harmonization across prospective studies</article-title><source>Am J Epidemiol</source><year>2023</year><month>11</month><day>10</day><volume>192</volume><issue>12</issue><fpage>2033</fpage><lpage>2049</lpage><pub-id pub-id-type="doi">10.1093/aje/kwad153</pub-id><pub-id pub-id-type="medline">37403415</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Deeks</surname><given-names>JJ</given-names> </name><name name-style="western"><surname>Higgins</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Altman</surname><given-names>DG</given-names> </name><name name-style="western"><surname>McKenzie</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Veroniki</surname><given-names>AA</given-names> </name></person-group><article-title>Chapter 10: analysing data and undertaking meta-analyses</article-title><source>Cochrane Handbook for Systematic Reviews of Interventions</source><year>2024</year><access-date>2026-09-23</access-date><publisher-name>Version 6.5. Cochrane</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.cochrane.org/authors/handbooks-and-manuals/handbook/current/chapter-10">https://www.cochrane.org/authors/handbooks-and-manuals/handbook/current/chapter-10</ext-link></comment></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>Wen</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Lan</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Cui</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Cai</surname><given-names>J</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>W</given-names> </name></person-group><article-title>A survey on federated learning: challenges and applications</article-title><source>Int J Mach Learn Cybern</source><year>2023</year><volume>14</volume><issue>2</issue><fpage>513</fpage><lpage>535</lpage><pub-id pub-id-type="doi">10.1007/s13042-022-01647-y</pub-id><pub-id pub-id-type="medline">36407495</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>Karargyris</surname><given-names>A</given-names> </name><name name-style="western"><surname>Umeton</surname><given-names>R</given-names> </name><name name-style="western"><surname>Sheller</surname><given-names>MJ</given-names> </name><etal/></person-group><article-title>Federated benchmarking of medical artificial intelligence with MedPerf</article-title><source>Nat Mach Intell</source><year>2023</year><month>07</month><volume>5</volume><issue>7</issue><fpage>799</fpage><lpage>810</lpage><pub-id pub-id-type="doi">10.1038/s42256-023-00652-2</pub-id><pub-id pub-id-type="medline">38706981</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>Hao</surname><given-names>X</given-names> </name><name name-style="western"><surname>Li</surname><given-names>X</given-names> </name><name name-style="western"><surname>Zhang</surname><given-names>GQ</given-names> </name><etal/></person-group><article-title>An ontology-based approach for harmonization and cross-cohort query of Alzheimer&#x2019;s disease data resources</article-title><source>BMC Med Inform Decis Mak</source><year>2023</year><month>08</month><day>4</day><volume>23</volume><issue>Suppl 1</issue><fpage>151</fpage><pub-id pub-id-type="doi">10.1186/s12911-023-02250-z</pub-id><pub-id pub-id-type="medline">37542312</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>Doiron</surname><given-names>D</given-names> </name><name name-style="western"><surname>Marcon</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Fortier</surname><given-names>I</given-names> </name><name name-style="western"><surname>Burton</surname><given-names>P</given-names> </name><name name-style="western"><surname>Ferretti</surname><given-names>V</given-names> </name></person-group><article-title>Software application profile: opal and mica: open-source software solutions for epidemiological data management, harmonization and dissemination</article-title><source>Int J Epidemiol</source><year>2017</year><month>10</month><day>1</day><volume>46</volume><issue>5</issue><fpage>1372</fpage><lpage>1378</lpage><pub-id pub-id-type="doi">10.1093/ije/dyx180</pub-id><pub-id pub-id-type="medline">29025122</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>Kalter</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sweegers</surname><given-names>MG</given-names> </name><name name-style="western"><surname>Verdonck-de Leeuw</surname><given-names>IM</given-names> </name><name name-style="western"><surname>Brug</surname><given-names>J</given-names> </name><name name-style="western"><surname>Buffart</surname><given-names>LM</given-names> </name></person-group><article-title>Development and use of a flexible data harmonization platform to facilitate the harmonization of individual patient data for meta-analyses</article-title><source>BMC Res Notes</source><year>2019</year><month>03</month><day>22</day><volume>12</volume><issue>1</issue><fpage>164</fpage><pub-id pub-id-type="doi">10.1186/s13104-019-4210-7</pub-id><pub-id pub-id-type="medline">30902064</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>Fortier</surname><given-names>I</given-names> </name><name name-style="western"><surname>Doiron</surname><given-names>D</given-names> </name><name name-style="western"><surname>Little</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Is rigorous retrospective harmonization possible? Application of the DataSHaPER approach across 53 large studies</article-title><source>Int J Epidemiol</source><year>2011</year><month>10</month><volume>40</volume><issue>5</issue><fpage>1314</fpage><lpage>1328</lpage><pub-id pub-id-type="doi">10.1093/ije/dyr106</pub-id><pub-id pub-id-type="medline">21804097</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>Mallya</surname><given-names>P</given-names> </name><name name-style="western"><surname>Stevens</surname><given-names>LM</given-names> </name><name name-style="western"><surname>Zhao</surname><given-names>J</given-names> </name><etal/></person-group><article-title>Facilitating harmonization of variables in Framingham, MESA, ARIC, and REGARDS studies through a metadata repository</article-title><source>Circ Cardiovasc Qual Outcomes</source><year>2023</year><month>11</month><volume>16</volume><issue>11</issue><fpage>e009938</fpage><pub-id pub-id-type="doi">10.1161/CIRCOUTCOMES.123.009938</pub-id><pub-id pub-id-type="medline">37850400</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>Winters</surname><given-names>K</given-names> </name><name name-style="western"><surname>Netscher</surname><given-names>S</given-names> </name><name name-style="western"><surname>Rosenbloom</surname><given-names>JL</given-names> </name></person-group><article-title>Proposed standards for variable harmonization documentation and referencing: a case study using QuickCharmStats 1.1</article-title><source>PLoS ONE</source><year>2016</year><volume>11</volume><issue>2</issue><fpage>e0147795</fpage><pub-id pub-id-type="doi">10.1371/journal.pone.0147795</pub-id><pub-id pub-id-type="medline">26859494</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>Doiron</surname><given-names>D</given-names> </name><name name-style="western"><surname>Burton</surname><given-names>P</given-names> </name><name name-style="western"><surname>Marcon</surname><given-names>Y</given-names> </name><etal/></person-group><article-title>Data harmonization and federated analysis of population-based studies: the BioSHaRE project</article-title><source>Emerg Themes Epidemiol</source><year>2013</year><month>11</month><day>21</day><volume>10</volume><issue>1</issue><fpage>12</fpage><lpage>12</lpage><pub-id pub-id-type="doi">10.1186/1742-7622-10-12</pub-id><pub-id pub-id-type="medline">24257327</pub-id></nlm-citation></ref><ref id="ref13"><label>13</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Sim</surname><given-names>I</given-names> </name></person-group><article-title>Vivli clinical research data sharing: share. discover. innovate</article-title><source>Vivli Center for Global Clinical Research Data</source><year>2020</year><month>02</month><day>11</day><access-date>2026-09-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://vivli.org/wp-content/uploads/2020/02/Sim-VIVLI_NIH-Repository-meeting_FINAL.pdf">https://vivli.org/wp-content/uploads/2020/02/Sim-VIVLI_NIH-Repository-meeting_FINAL.pdf</ext-link></comment></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>Yu</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Zong</surname><given-names>N</given-names> </name><name name-style="western"><surname>Wen</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Developing an ETL tool for converting the PCORnet CDM into the OMOP CDM to facilitate the COVID-19 data integration</article-title><source>J Biomed Inform</source><year>2022</year><month>03</month><volume>127</volume><fpage>104002</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2022.104002</pub-id><pub-id pub-id-type="medline">35077901</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>Klann</surname><given-names>JG</given-names> </name><name name-style="western"><surname>Joss</surname><given-names>MAH</given-names> </name><name name-style="western"><surname>Embree</surname><given-names>K</given-names> </name><name name-style="western"><surname>Murphy</surname><given-names>SN</given-names> </name></person-group><article-title>Data model harmonization for the All Of Us research program: transforming i2b2 data into the OMOP common data model</article-title><source>PLoS ONE</source><year>2019</year><volume>14</volume><issue>2</issue><fpage>e0212463</fpage><pub-id pub-id-type="doi">10.1371/journal.pone.0212463</pub-id><pub-id pub-id-type="medline">30779778</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>Hallinan</surname><given-names>CM</given-names> </name><name name-style="western"><surname>Ward</surname><given-names>R</given-names> </name><name name-style="western"><surname>Hart</surname><given-names>GK</given-names> </name><etal/></person-group><article-title>Seamless EMR data access: integrated governance, digital health and the OMOP-CDM</article-title><source>BMJ Health Care Inform</source><year>2024</year><month>02</month><day>21</day><volume>31</volume><issue>1</issue><fpage>e100953</fpage><pub-id pub-id-type="doi">10.1136/bmjhci-2023-100953</pub-id><pub-id pub-id-type="medline">38387992</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>Henke</surname><given-names>E</given-names> </name><name name-style="western"><surname>Zoch</surname><given-names>M</given-names> </name><name name-style="western"><surname>Peng</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Reinecke</surname><given-names>I</given-names> </name><name name-style="western"><surname>Sedlmayr</surname><given-names>M</given-names> </name><name name-style="western"><surname>Bathelt</surname><given-names>F</given-names> </name></person-group><article-title>Conceptual design of a generic data harmonization process for OMOP common data model</article-title><source>BMC Med Inform Decis Mak</source><year>2024</year><month>02</month><day>26</day><volume>24</volume><issue>1</issue><fpage>58</fpage><pub-id pub-id-type="doi">10.1186/s12911-024-02458-7</pub-id><pub-id pub-id-type="medline">38408983</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="web"><article-title>2023 NIH data management and sharing policy</article-title><source>NIH Office of Intramural Research</source><year>2023</year><access-date>2024-12-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://oir.nih.gov/sourcebook/intramural-program-oversight/intramural-data-sharing/2023-nih-data-management-sharing-policy">https://oir.nih.gov/sourcebook/intramural-program-oversight/intramural-data-sharing/2023-nih-data-management-sharing-policy</ext-link></comment></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>Kim</surname><given-names>H</given-names> </name><name name-style="western"><surname>Liang</surname><given-names>S</given-names> </name><name name-style="western"><surname>Lanier</surname><given-names>K</given-names> </name><etal/></person-group><article-title>Bidirectional data harmonization across the multiple chronic disease disparities research consortium: a pipeline description of opportunities and challenges</article-title><source>J Biomed Inform</source><year>2026</year><month>05</month><volume>177</volume><fpage>105004</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2026.105004</pub-id><pub-id pub-id-type="medline">41771392</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="report"><article-title>Consolidated appropriations act</article-title><year>2021</year><month>03</month><access-date>2026-09-23</access-date><publisher-name>U.S. Government Publishing Office</publisher-name><fpage>133</fpage><comment><ext-link ext-link-type="uri" xlink:href="https://www.govinfo.gov/content/pkg/CPRT-117HPRT43749/html/CPRT-117HPRT43749.htm">https://www.govinfo.gov/content/pkg/CPRT-117HPRT43749/html/CPRT-117HPRT43749.htm</ext-link></comment></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><article-title>NIMHD provides over $200 million in funding for research in chronic disease prevention and treatment</article-title><source>National Institute on Minority Health and Health Disparities</source><year>2021</year><month>10</month><day>14</day><access-date>2024-12-10</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nimhd.nih.gov/news-events/news-releases/2021/pr-2021-10-14-nimhd-funds-chronic-disease-disparities-research.html">https://www.nimhd.nih.gov/news-events/news-releases/2021/pr-2021-10-14-nimhd-funds-chronic-disease-disparities-research.html</ext-link></comment></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>Alvidrez</surname><given-names>J</given-names> </name><name name-style="western"><surname>Castille</surname><given-names>D</given-names> </name><name name-style="western"><surname>Laude-Sharp</surname><given-names>M</given-names> </name><name name-style="western"><surname>Rosario</surname><given-names>A</given-names> </name><name name-style="western"><surname>Tabor</surname><given-names>D</given-names> </name></person-group><article-title>The National Institute on Minority Health and Health Disparities research framework</article-title><source>Am J Public Health</source><year>2019</year><month>01</month><volume>109</volume><issue>S1</issue><fpage>S16</fpage><lpage>S20</lpage><pub-id pub-id-type="doi">10.2105/AJPH.2018.304883</pub-id><pub-id pub-id-type="medline">30699025</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Gansky</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Cheng</surname><given-names>AC</given-names> </name><name name-style="western"><surname>Mendhe</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Common data element (CDE) success from community-engagement not mandates: if you build it [data warehouse], will they [participants] come?</article-title><year>2025</year><month>07</month><volume>115</volume><publisher-name>Am J Public Health</publisher-name><fpage>S110</fpage><lpage>S115</lpage><pub-id pub-id-type="doi">10.2105/AJPH.2025.308114</pub-id><pub-id pub-id-type="medline">40561407</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>Rolland</surname><given-names>B</given-names> </name><name name-style="western"><surname>Reid</surname><given-names>S</given-names> </name><name name-style="western"><surname>Stelling</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Toward rigorous data harmonization in cancer epidemiology research: one approach</article-title><source>Am J Epidemiol</source><year>2015</year><month>12</month><day>15</day><volume>182</volume><issue>12</issue><fpage>1033</fpage><lpage>1038</lpage><pub-id pub-id-type="doi">10.1093/aje/kwv133</pub-id><pub-id pub-id-type="medline">26589709</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>Glenn</surname><given-names>J</given-names> </name><name name-style="western"><surname>Kleinhenz</surname><given-names>G</given-names> </name><name name-style="western"><surname>Smith</surname><given-names>JMS</given-names> </name><etal/></person-group><article-title>Do healthcare providers consider the social determinants of health? Results from a nationwide cross-sectional study in the United States</article-title><source>BMC Health Serv Res</source><year>2024</year><month>03</month><day>4</day><volume>24</volume><issue>1</issue><fpage>271</fpage><pub-id pub-id-type="doi">10.1186/s12913-024-10656-2</pub-id><pub-id pub-id-type="medline">38438936</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>Guevara</surname><given-names>M</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>S</given-names> </name><name name-style="western"><surname>Thomas</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Large language models to identify social determinants of health in electronic health records</article-title><source>NPJ Digit Med</source><year>2024</year><month>01</month><day>11</day><volume>7</volume><issue>1</issue><fpage>6</fpage><pub-id pub-id-type="doi">10.1038/s41746-023-00970-0</pub-id><pub-id pub-id-type="medline">38200151</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>Urbanowicz</surname><given-names>RJ</given-names> </name><name name-style="western"><surname>Holmes</surname><given-names>JH</given-names> </name><name name-style="western"><surname>Appleby</surname><given-names>D</given-names> </name><etal/></person-group><article-title>A semi-automated term harmonization pipeline applied to pulmonary arterial hypertension clinical trials</article-title><source>Methods Inf Med</source><year>2022</year><month>05</month><volume>61</volume><issue>1-02</issue><fpage>3</fpage><lpage>10</lpage><pub-id pub-id-type="doi">10.1055/s-0041-1739361</pub-id><pub-id pub-id-type="medline">34820791</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Blom</surname><given-names>MC</given-names> </name><name name-style="western"><surname>Khalid</surname><given-names>M</given-names> </name><name name-style="western"><surname>Van-Lettow</surname><given-names>B</given-names> </name><name name-style="western"><surname>Hutink</surname><given-names>H</given-names> </name><name name-style="western"><surname>Larsson</surname><given-names>S</given-names> </name><name name-style="western"><surname>Huff</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Harmonization of the ICHOM quality measures to enable health outcomes measurement in multimorbid patients</article-title><source>Front Digit Health</source><year>2020</year><month>12</month><day>15</day><access-date>2026-09-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.frontiersin.org/journals/digital-health/articles/10.3389/fdgth.2020.606246">https://www.frontiersin.org/journals/digital-health/articles/10.3389/fdgth.2020.606246</ext-link></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>Mitchell</surname><given-names>JR</given-names> </name><name name-style="western"><surname>Szepietowski</surname><given-names>P</given-names> </name><name name-style="western"><surname>Howard</surname><given-names>R</given-names> </name><etal/></person-group><article-title>A question-and-answer system to extract data from free-text oncological pathology reports (CancerBERT Network): development study</article-title><source>J Med Internet Res</source><year>2022</year><month>03</month><day>23</day><volume>24</volume><issue>3</issue><fpage>e27210</fpage><pub-id pub-id-type="doi">10.2196/27210</pub-id><pub-id pub-id-type="medline">35319481</pub-id></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Zhou</surname><given-names>D</given-names> </name><name name-style="western"><surname>Gan</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Shi</surname><given-names>X</given-names> </name><etal/></person-group><article-title>Multiview incomplete knowledge graph integration with application to cross-institutional EHR data harmonization</article-title><source>J Biomed Inform</source><year>2022</year><month>09</month><volume>133</volume><fpage>104147</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2022.104147</pub-id><pub-id pub-id-type="medline">35872266</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mallya</surname><given-names>P</given-names> </name><name name-style="western"><surname>Henao</surname><given-names>R</given-names> </name><name name-style="western"><surname>Hong</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Automated data harmonization in clinical research: natural language processing approach</article-title><source>JMIR Form Res</source><year>2025</year><month>08</month><day>27</day><volume>9</volume><fpage>e75608</fpage><pub-id pub-id-type="doi">10.2196/75608</pub-id><pub-id pub-id-type="medline">40874791</pub-id></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Cho</surname><given-names>H</given-names> </name><name name-style="western"><surname>Yoo</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>B</given-names> </name><etal/></person-group><article-title>Extracting lung cancer staging descriptors from pathology reports: a generative language model approach</article-title><source>J Biomed Inform</source><year>2024</year><month>09</month><volume>157</volume><fpage>104720</fpage><pub-id pub-id-type="doi">10.1016/j.jbi.2024.104720</pub-id><pub-id pub-id-type="medline">39233209</pub-id></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Long</surname><given-names>RA</given-names> </name><name name-style="western"><surname>Ballard</surname><given-names>S</given-names> </name><name name-style="western"><surname>Shah</surname><given-names>S</given-names> </name><etal/></person-group><article-title>A new AI assisted approach aligns data standards and accelerates interoperability in biomedical research</article-title><source>NPJ Digit Med</source><year>2026</year><month>06</month><day>12</day><pub-id pub-id-type="doi">10.1038/s41746-026-02795-z</pub-id><pub-id pub-id-type="medline">42286188</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Talby</surname><given-names>D</given-names> </name></person-group><article-title>Automated harmonization of multimodal clinical data into OMOP using generative &#x0026; agentic AI</article-title><source>AMIA</source><year>2025</year><access-date>2026-09-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://amia.org/education-events/education-catalog/automated-harmonization-multimodal-clinical-data-omop-using">https://amia.org/education-events/education-catalog/automated-harmonization-multimodal-clinical-data-omop-using</ext-link></comment></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Kim</surname><given-names>H</given-names> </name><name name-style="western"><surname>Liang</surname><given-names>S</given-names> </name><name name-style="western"><surname>Lanier</surname><given-names>K</given-names> </name><name name-style="western"><surname>Helman</surname><given-names>S</given-names> </name><name name-style="western"><surname>Gansky</surname><given-names>S</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>W</given-names> </name></person-group><article-title>Comparison and cost strategies using AI chat vs API to map cdes across studies of chronic diseases and disparities in the health equity action network (HEAN) research consortium</article-title><access-date>2026-10-04</access-date><conf-name>AMIA 2024 Annual Symposium</conf-name><conf-date>Nov 11, 2024</conf-date><comment><ext-link ext-link-type="uri" xlink:href="https://amia.secure-platform.com/symposium/solicitations/102001/sessiongallery/schedule/items/94174">https://amia.secure-platform.com/symposium/solicitations/102001/sessiongallery/schedule/items/94174</ext-link></comment></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="web"><article-title>Foundry models sold by Azure in Azure Government</article-title><source>Microsoft Ignite</source><year>2025</year><access-date>2026-09-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://learn.microsoft.com/en-us/azure/ai-foundry/openai/azure-government">https://learn.microsoft.com/en-us/azure/ai-foundry/openai/azure-government</ext-link></comment></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="report"><person-group person-group-type="author"><collab>Developed by University California, San Francisco</collab></person-group><article-title>UCSF versa</article-title><year>2025</year><access-date>2026-10-04</access-date><publisher-name>Hosted on Microsoft Azure OpenAI</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://ai.ucsf.edu/platforms-tools-and-resources/ucsf-versa">https://ai.ucsf.edu/platforms-tools-and-resources/ucsf-versa</ext-link></comment></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Granger</surname><given-names>BE</given-names> </name><name name-style="western"><surname>Perez</surname><given-names>F</given-names> </name></person-group><article-title>Jupyter: thinking and storytelling with code and data</article-title><source>Comput Sci Eng</source><year>2021</year><month>01</month><volume>23</volume><issue>2</issue><fpage>7</fpage><lpage>14</lpage><pub-id pub-id-type="doi">10.1109/MCSE.2021.3059263</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="web"><article-title>The R project for statistical computing</article-title><source>The R Foundation</source><year>2024</year><access-date>2026-09-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.R-project.org/">https://www.R-project.org/</ext-link></comment></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Van Rossum</surname><given-names>G</given-names> </name><name name-style="western"><surname>Drake</surname><given-names>FL</given-names> </name></person-group><source>Python 3 Reference Manual</source><year>2009</year><access-date>2026-09-23</access-date><publisher-name>CreateSpace</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://dl.acm.org/doi/book/10.5555/1593511">https://dl.acm.org/doi/book/10.5555/1593511</ext-link></comment></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Jabbour</surname><given-names>S</given-names> </name><name name-style="western"><surname>Fouhey</surname><given-names>D</given-names> </name><name name-style="western"><surname>Shepard</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Measuring the impact of AI in the diagnosis of hospitalized patients: a randomized clinical vignette survey study</article-title><source>JAMA</source><year>2023</year><month>12</month><day>19</day><volume>330</volume><issue>23</issue><fpage>2275</fpage><lpage>2284</lpage><pub-id pub-id-type="doi">10.1001/jama.2023.22295</pub-id><pub-id pub-id-type="medline">38112814</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Kolstad</surname><given-names>J</given-names> </name></person-group><article-title>Cognitive capacity, fatigue and decision making: evidence from the practice of medicine</article-title><year>2024</year><access-date>2026-10-04</access-date><publisher-name>Harris School of Public Policy, The University of Chicago</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://harris.uchicago.edu/sites/default/files/inline-files/Kolstad%20PPE%20seminar%20abstract%204-23-24.pdf">https://harris.uchicago.edu/sites/default/files/inline-files/Kolstad%20PPE%20seminar%20abstract%204-23-24.pdf</ext-link></comment></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sim</surname><given-names>I</given-names> </name><name name-style="western"><surname>Cassel</surname><given-names>C</given-names> </name></person-group><article-title>The ethics of relational AI - expanding and implementing the Belmont principles</article-title><source>N Engl J Med</source><year>2024</year><month>07</month><day>18</day><volume>391</volume><issue>3</issue><fpage>193</fpage><lpage>196</lpage><pub-id pub-id-type="doi">10.1056/NEJMp2314771</pub-id><pub-id pub-id-type="medline">39007542</pub-id></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Adler-Milstein</surname><given-names>J</given-names> </name><name name-style="western"><surname>Redelmeier</surname><given-names>DA</given-names> </name><name name-style="western"><surname>Wachter</surname><given-names>RM</given-names> </name></person-group><article-title>The limits of clinician vigilance as an AI safety bulwark</article-title><source>JAMA</source><year>2024</year><month>04</month><day>9</day><volume>331</volume><issue>14</issue><fpage>1173</fpage><lpage>1174</lpage><pub-id pub-id-type="doi">10.1001/jama.2024.3620</pub-id><pub-id pub-id-type="medline">38483397</pub-id></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Xiao</surname><given-names>T</given-names> </name><name name-style="western"><surname>Nerini</surname><given-names>FF</given-names> </name><name name-style="western"><surname>Matthews</surname><given-names>HD</given-names> </name><name name-style="western"><surname>Tavoni</surname><given-names>M</given-names> </name><name name-style="western"><surname>You</surname><given-names>F</given-names> </name></person-group><article-title>Environmental impact and net-zero pathways for sustainable artificial intelligence servers in the USA</article-title><source>Nat Sustain</source><year>2025</year><month>11</month><day>10</day><volume>8</volume><issue>12</issue><fpage>1541</fpage><lpage>1553</lpage><pub-id pub-id-type="doi">10.1038/s41893-025-01681-y</pub-id></nlm-citation></ref><ref id="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Coulson</surname><given-names>A</given-names> </name></person-group><article-title>The environmental impact of AI in the lab: a double-edged sword?</article-title><source>BioTechniques</source><year>2024</year><volume>76</volume><issue>8</issue><fpage>353</fpage><lpage>356</lpage><pub-id pub-id-type="doi">10.1080/07366205.2024.2376459</pub-id><pub-id pub-id-type="medline">39082228</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Chen</surname><given-names>YH</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>E</given-names> </name><name name-style="western"><surname>Tan</surname><given-names>J</given-names> </name><name name-style="western"><surname>Thompson</surname><given-names>H</given-names> </name><name name-style="western"><surname>Deardorff</surname><given-names>A</given-names> </name></person-group><article-title>AI in your toolkit: critical approaches to using AI in your work</article-title><source>UCSF Library</source><year>2025</year><month>11</month><day>13</day><access-date>2026-09-23</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://courses.ucsf.edu/course/view.php?id=12582">https://courses.ucsf.edu/course/view.php?id=12582</ext-link></comment></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="web"><article-title>Tackling health inequity</article-title><source>Health Excellence Action Network</source><access-date>2026-10-14</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://health-excellence-action.org/">https://health-excellence-action.org/</ext-link></comment></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>CDE concepts, question items, and semantic groups</p><media xlink:href="ai_v5i1e93996_app1.docx" xlink:title="DOCX File, 1695 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Details of the included studies</p><media xlink:href="ai_v5i1e93996_app2.docx" xlink:title="DOCX File, 1684 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Mapping Results of the Required CDE Semantic Groups</p><media xlink:href="ai_v5i1e93996_app3.docx" xlink:title="DOCX File, 69 KB"/></supplementary-material><supplementary-material id="app4"><label>Multimedia Appendix 4</label><p>Analysis for the incomplete mapping items.</p><media xlink:href="ai_v5i1e93996_app4.docx" xlink:title="DOCX File, 3327 KB"/></supplementary-material><supplementary-material id="app5"><label>Multimedia Appendix 5</label><p>Example R code LLM generated for variable mapping.</p><media xlink:href="ai_v5i1e93996_app5.docx" xlink:title="DOCX File, 3326 KB"/></supplementary-material></app-group></back></article>