<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMIR</journal-id>
      <journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
      <journal-title>Journal of Medical Internet Research</journal-title>
      <issn pub-type="epub">1438-8871</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v27i1e69004</article-id>
      <article-id pub-id-type="pmid">40146872</article-id>
      <article-id pub-id-type="doi">10.2196/69004</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Breaking Digital Health Barriers Through a Large Language Model–Based Tool for Automated Observational Medical Outcomes Partnership Mapping: Development and Validation Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Coristine</surname>
            <given-names>Andrew</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Klann</surname>
            <given-names>Jeffrey</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Henke</surname>
            <given-names>Elisa</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Karen</surname>
            <given-names>Triep</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Adams</surname>
            <given-names>Meredith CB</given-names>
          </name>
          <degrees>MS, MD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution/>
            <institution>Department of Anesthesiology, Artificial Intelligence, Translational Neuroscience, and Public Health Sciences</institution>
            <institution>Wake Forest University School of Medicine</institution>
            <addr-line>Medical Center Boulevard</addr-line>
            <addr-line>Winston-Salem, NC, 27157</addr-line>
            <country>United States</country>
            <phone>1 13367162255</phone>
            <email>meradams@wakehealth.edu</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3969-4279</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Perkins</surname>
            <given-names>Matthew L</given-names>
          </name>
          <degrees>BS</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0003-4127-2213</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Hudson</surname>
            <given-names>Cody</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0001-3374-3754</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Madhira</surname>
            <given-names>Vithal</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5359-1703</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Akbilgic</surname>
            <given-names>Oguz</given-names>
          </name>
          <degrees>DBA, PhD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0313-9254</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Ma</surname>
            <given-names>Da</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff5" ref-type="aff">5</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3542-7798</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Hurley</surname>
            <given-names>Robert W</given-names>
          </name>
          <degrees>MD, PhD</degrees>
          <xref rid="aff6" ref-type="aff">6</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6591-9390</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author">
          <name name-style="western">
            <surname>Topaloglu</surname>
            <given-names>Umit</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff7" ref-type="aff">7</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-3241-8773</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Department of Anesthesiology, Artificial Intelligence, Translational Neuroscience, and Public Health Sciences</institution>
        <institution>Wake Forest University School of Medicine</institution>
        <addr-line>Winston-Salem, NC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Cancer Biology</institution>
        <institution>Wake Forest University School of Medicine</institution>
        <addr-line>Winston-Salem, NC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Palila Software LLC</institution>
        <addr-line>Reno, NV</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Cardiovascular Medicine</institution>
        <institution>Wake Forest University School of Medicine</institution>
        <addr-line>Winston-Salem, NC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff5">
        <label>5</label>
        <institution>Department of Internal Medicine</institution>
        <institution>Wake Forest University School of Medicine</institution>
        <addr-line>Winston-Salem, NC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff6">
        <label>6</label>
        <institution>Department of Anesthesiology, Translational Neuroscience, and Public Health Sciences</institution>
        <institution>Wake Forest University School of Medicine</institution>
        <addr-line>Winston-Salem, NC</addr-line>
        <country>United States</country>
      </aff>
      <aff id="aff7">
        <label>7</label>
        <institution>Clinical Translational Research Informatics Branch</institution>
        <institution>National Cancer Institute</institution>
        <addr-line>Bethesda, MD</addr-line>
        <country>United States</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Meredith CB Adams <email>meradams@wakehealth.edu</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>15</day>
        <month>5</month>
        <year>2025</year>
      </pub-date>
      <volume>27</volume>
      <elocation-id>e69004</elocation-id>
      <history>
        <date date-type="received">
          <day>22</day>
          <month>11</month>
          <year>2024</year>
        </date>
        <date date-type="rev-request">
          <day>20</day>
          <month>1</month>
          <year>2025</year>
        </date>
        <date date-type="rev-recd">
          <day>9</day>
          <month>2</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>27</day>
          <month>3</month>
          <year>2025</year>
        </date>
      </history>
      <copyright-statement>©Meredith CB Adams, Matthew L Perkins, Cody Hudson, Vithal Madhira, Oguz Akbilgic, Da Ma, Robert W Hurley, Umit Topaloglu. Originally published in the Journal of Medical Internet Research (https://www.jmir.org), 15.05.2025.</copyright-statement>
      <copyright-year>2025</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research (ISSN 1438-8871), is properly cited. The complete bibliographic information, a link to the original publication on https://www.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://www.jmir.org/2025/1/e69004" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The integration of diverse clinical data sources requires standardization through models such as Observational Medical Outcomes Partnership (OMOP). However, mapping data elements to OMOP concepts demands significant technical expertise and time. While large health care systems often have resources for OMOP conversion, smaller clinical trials and studies frequently lack such support, leaving valuable research data siloed.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>This study aims to develop and validate a user-friendly tool that leverages large language models to automate the OMOP conversion process for clinical trials, electronic health records, and registry data.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We developed a 3-tiered semantic matching system using GPT-3 embeddings to transform heterogeneous clinical data to the OMOP Common Data Model. The system processes input terms by generating vector embeddings, computing cosine similarity against precomputed Observational Health Data Sciences and Informatics vocabulary embeddings, and ranking potential matches. We validated the system using two independent datasets: (1) a development set of 76 National Institutes of Health Helping to End Addiction Long-term Initiative clinical trial common data elements for chronic pain and opioid use disorders and (2) a separate validation set of electronic health record concepts from the National Institutes of Health National COVID Cohort Collaborative COVID-19 enclave. The architecture combines Unified Medical Language System semantic frameworks with asynchronous processing for efficient concept mapping, made available through an open-source implementation.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>The system achieved an area under the receiver operating characteristic curve of 0.9975 for mapping clinical trial common data element terms. Precision ranged from 0.92 to 0.99 and recall ranged from 0.88 to 0.97 across similarity thresholds from 0.85 to 1.0. In practical application, the tool successfully automated mappings that previously required manual informatics expertise, reducing the technical barriers for research teams to participate in large-scale, data-sharing initiatives. Representative mappings demonstrated high accuracy, such as demographic terms achieving 100% similarity with corresponding Logical Observation Identifiers Names and Codes concepts. The implementation successfully processes diverse data types through both individual term mapping and batch processing capabilities.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>Our validated large language model–based tool effectively automates the transformation of clinical data into the OMOP format while maintaining high accuracy. The combination of semantic matching capabilities and a researcher-friendly interface makes data harmonization accessible to smaller research teams without requiring extensive informatics support. This has direct implications for accelerating clinical research data standardization and enabling broader participation in initiatives such as the National Institutes of Health Helping to End Addiction Long-term Initiative Data Ecosystem.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>large language model</kwd>
        <kwd>artificial intelligence</kwd>
        <kwd>common data model</kwd>
        <kwd>data harmonization</kwd>
        <kwd>clinical trials</kwd>
        <kwd>electronic health record</kwd>
        <kwd>registry data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>The digital transformation of health care has created unprecedented opportunities to leverage diverse clinical data sources while simultaneously introducing complex standardization challenges. As health care data expand across modalities from traditional clinical trials and electronic health records to mobile health devices and patient-reported outcomes, researchers face increasing pressure to harmonize these heterogeneous sources into standardized formats that enable meaningful analysis and collaboration [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref4">4</xref>]. While initiatives such as the National Institutes of Health (NIH) Helping to End Addiction Long-term (HEAL) Initiative Data Ecosystem and the NIH Office of Data Science Strategy promote Findable, Accessible, Interoperable, Reusable (FAIR) principles [<xref ref-type="bibr" rid="ref5">5</xref>], technical barriers often prevent researchers from fully participating in collaborative digital health research.</p>
      <p>The Observational Medical Outcomes Partnership (OMOP) Common Data Model (CDM), maintained by the Observational Health Data Sciences and Informatics (OHDSI) community, has emerged as a leading standardization solution with significant advantages for digital health research [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. OMOP provides extensive documentation, quality monitoring libraries, and analytic tools that support research initiatives across multiple scales [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Major projects such as the NIH National COVID Cohort Collaborative (N3C) have adopted OMOP as their foundation [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>], and academic medical centers increasingly establish OMOP-based enterprise data warehouses to facilitate research and quality improvement [<xref ref-type="bibr" rid="ref12">12</xref>-<xref ref-type="bibr" rid="ref14">14</xref>].</p>
      <p>Despite OMOP’s advantages, a critical barrier persists: the process of mapping clinical concepts to OMOP’s standardized vocabularies requires significant technical expertise and time investment that many research teams cannot afford. This creates a fundamental inequity in digital health research, where valuable data from smaller clinical trials and studies remain siloed due to technical barriers in standardization [<xref ref-type="bibr" rid="ref15">15</xref>]. While large health care systems and registries often have dedicated resources for OMOP conversion, clinical researchers with domain expertise but limited informatics support cannot participate in larger data-sharing initiatives. The NIH HEAL Initiative alone encompasses hundreds of clinical trials with potentially valuable data that remain inaccessible to broader analysis due to these technical constraints.</p>
      <p>Recent advances in large language models (LLMs) offer a promising approach to overcome these technical barriers through automated semantic mapping between research-level data representation and standardized vocabularies [<xref ref-type="bibr" rid="ref16">16</xref>]. By leveraging the contextual understanding capabilities of LLMs, it becomes possible to recognize semantic relationships beyond simple keyword matching—for example, identifying that “chest pain during physical activity” is conceptually similar to “exercise-induced angina” even with minimal lexical overlap. Our previous work demonstrated the effectiveness of semantic similarity approaches in clinical concept mapping [<xref ref-type="bibr" rid="ref17">17</xref>], while maintaining the node-based model’s reliability for concept alignment.</p>
      <p>This paper presents an automated tool that leverages LLM-based semantic matching to transform heterogeneous clinical data into the OMOP CDM. Through a researcher-friendly interface designed for clinical teams without extensive informatics support, the tool addresses both technical and workflow barriers to participation in large-scale digital health initiatives. We demonstrate the system’s effectiveness across multiple data types and clinical domains, validating its performance using both NIH HEAL Initiative clinical trial data and electronic health record concepts from the NIH N3C COVID-19 enclave. The results suggest that LLM-based approaches can significantly reduce the resources required for data standardization while maintaining high mapping accuracy, potentially enabling broader participation in collaborative research networks.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>The transformation of heterogeneous health care data into the OMOP CDM represents a fundamental challenge in enabling large-scale digital health research. A multilayered architecture that combines semantic matching, LLMs, and a user-friendly web interface was developed to address this challenge and automate the conversion process.</p>
      </sec>
      <sec>
        <title>System Overview and Data Sources</title>
        <p>Our system interfaces with multiple clinical data sources, including trial databases, electronic health records, and registry data. At its foundation, OHDSI’s Vocabularies Repository Athena serves as the reference resource for standardized vocabularies. The architecture builds upon established semantic frameworks [<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>] by leveraging the Unified Medical Language System to generate comprehensive concept profiles [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
      </sec>
      <sec>
        <title>Core Technical Components</title>
        <p>The architecture uses two complementary technical approaches for semantic processing:</p>
        <sec>
          <title>Word Embeddings</title>
          <p>We generate fixed-length dense vector representations of all OHDSI vocabulary terms using the GPT-3 model. These embeddings capture semantic meaning in a standardized numerical format and are precomputed for efficient similarity calculations (<xref rid="figure1" ref-type="fig">Figure 1</xref>).</p>
          <fig id="figure1" position="float">
            <label>Figure 1</label>
            <caption>
              <p>System architecture for the large language model (LLM)–based clinical data standardization tool. This architectural diagram shows the system’s major components and data flow. The system integrates OHDSI’s Vocabularies Repository (Athena), UMLS semantic, and GPT-3 word embeddings to enable automated concept mapping. Key components include the semantic processing pipeline, MongoDB storage, Redis queue management, and the user interface layer. API: application programming interface; CDE: common data element; ETL: extract, transform, load; OHDSI: Observational Health Data Sciences and Informatics; OMOP: Observational Medical Outcomes Partnership; UMLS: Unified Medical Language System.</p>
            </caption>
            <graphic xlink:href="jmir_v27i1e69004_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>LLM Integration</title>
          <p>While embeddings provide the foundation for similarity comparisons, we strategically incorporate LLM capabilities for contextual processing where needed, balancing computational demands with semantic accuracy.</p>
          <p>The system’s workflow begins with the extraction of vocabulary terms from Athena, capturing essential metadata such as domain classifications, concept identifiers, and validity status. These terms undergo preprocessing to generate standardized embeddings, creating a comprehensive reference database in MongoDB collections optimized for similarity retrieval.</p>
        </sec>
      </sec>
      <sec>
        <title>Semantic Matching Process</title>
        <p>Our implementation uses a three-tiered semantic matching approach:</p>
        <sec>
          <title>Exact Matching</title>
          <p>The system first checks for direct string correspondence between input terms and standardized vocabularies.</p>
        </sec>
        <sec>
          <title>Linguistic Association</title>
          <p>When exact matches are not found, the system evaluates higher-order linguistic relationships between semantic types.</p>
        </sec>
        <sec>
          <title>Embedding-Based Similarity</title>
          <p>Finally, the system conducts cosine similarity calculations between input term embeddings and precomputed vocabulary embeddings to identify the most semantically relevant concepts.</p>
          <p>This approach enables nuanced semantic understanding beyond simple keyword matching [<xref ref-type="bibr" rid="ref22">22</xref>]. For instance, when processing demographic data such as “Not Hispanic or Latino,” the system identifies both exact matches (LOINC [Logical Observation Identifiers Names and Codes] concept LA19555-4 with 100% similarity) and semantically similar alternatives such as “Non-Hispanic or Latino” (LOINC: LA10597-5 with 93.89% similarity). This capability is particularly valuable for handling the natural language variations common in clinical documentation.</p>
        </sec>
      </sec>
      <sec>
        <title>Performance Optimization</title>
        <p>The system uses several optimization strategies to handle multiple concurrent users and ensure efficient processing:</p>
        <sec>
          <title>Asynchronous Processing</title>
          <p>Redis queue management with Bull queue integration enables efficient handling of concurrent requests.</p>
        </sec>
        <sec>
          <title>Process Management</title>
          <p>A PM2-managed Node.js Express service ensures consistent performance and system resilience.</p>
        </sec>
        <sec>
          <title>Optimized Data Storage</title>
          <p>MongoDB collections are structured for efficient similarity calculations, though memory management remains an important consideration for large-scale implementations.</p>
          <p>The output generation process produces detailed mapping documentation, including originating form identifiers, concept annotations, similarity scores, and complete vocabulary metadata. These comprehensive outputs support both immediate validation and downstream data transformation requirements.</p>
        </sec>
      </sec>
      <sec>
        <title>User Interface Implementation</title>
        <p>The web interface, developed in React (<xref rid="figure2" ref-type="fig">Figure 2</xref>), provides three pathways for data input:</p>
        <list list-type="bullet">
          <list-item>
            <p>Direct manual entry for individual term mapping</p>
          </list-item>
          <list-item>
            <p>Research Electronic Data Capture (REDCap) application programming interface integration for batch processing of data dictionaries</p>
          </list-item>
          <list-item>
            <p>CSV or XLSX file upload for bulk term processing</p>
          </list-item>
        </list>
        <p>Upon completion of the mapping process, the system generates structured CSV outputs containing form and field identifiers, field annotations with concept IDs, similarity scores, matched standardized terms, and domain information. This interface design supports both individual researchers mapping specific terms and research teams processing complete datasets, making the system accessible to users with varying technical expertise levels.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>User interface for clinical data mapping: (A) main dashboard: data import and vocabulary selection interface—the screenshot shows the primary user interface for data import functionality, including REDCap dictionary integration options and vocabulary collection selection tools; and (B) interactive term review and mapping selection interface. REDCap: Research Electronic Data Capture.</p>
          </caption>
          <graphic xlink:href="jmir_v27i1e69004_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Evaluation Methodology</title>
        <p>We designed a testing protocol to evaluate system performance using a pilot set of 76 NIH HEAL chronic pain and opioid use disorder clinical trial common data element (CDE) terms (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Each term was processed through the system, and the resulting mappings were independently reviewed by clinical informaticists to establish a gold standard for accuracy assessment. Our evaluation methodology included binary classification model assessment measuring precision, recall, and <italic>F</italic><sub>1</sub>-scores, along with usability testing with clinical researchers to validate workflow efficiency and interface accessibility (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <p>Our validation approach used 2 distinct datasets to ensure robust evaluation. For development, we selected 76 NIH HEAL Initiative clinical trial CDEs covering domains including demographics, education, employment status, and pain assessments. These elements were chosen to represent diverse data types commonly found in clinical trials. In establishing a gold standard for accuracy assessment, 2 clinical informaticists independently reviewed all mappings, with discrepancies resolved through consensus discussions.</p>
        <p>The system’s vector embeddings were generated using the GPT-3 model and were stored in MongoDB collections with optimized indexing for similarity calculations. The embedding process preserves semantic relationships while enabling efficient computational processing. Additional validation was performed using a separate dataset of electronic health record concepts from the NIH N3C COVID-19 enclave, which provided real-world validation in a different clinical domain. Performance was evaluated across similarity thresholds ranging from 0.85 to 1.0, providing a robust assessment of the model’s classification capabilities under varying stringency requirements.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Implementation and performance metrics of the Observational Medical Outcomes Partnership data standardization system.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <thead>
              <tr valign="top">
                <td>Cutoff</td>
                <td>Precision</td>
                <td>Recall</td>
                <td><italic>F</italic><sub>1</sub>-score</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>0.85</td>
                <td>0.9859</td>
                <td>1</td>
                <td>0.9929</td>
              </tr>
              <tr valign="top">
                <td>0.88</td>
                <td>1</td>
                <td>0.9429</td>
                <td>0.9706</td>
              </tr>
              <tr valign="top">
                <td>0.9</td>
                <td>1</td>
                <td>0.9429</td>
                <td>0.9706</td>
              </tr>
              <tr valign="top">
                <td>0.92</td>
                <td>1</td>
                <td>0.9429</td>
                <td>0.9706</td>
              </tr>
              <tr valign="top">
                <td>0.95</td>
                <td>1</td>
                <td>0.9429</td>
                <td>0.9706</td>
              </tr>
              <tr valign="top">
                <td>0.97</td>
                <td>1</td>
                <td>0.8286</td>
                <td>0.9062</td>
              </tr>
              <tr valign="top">
                <td>0.99</td>
                <td>1</td>
                <td>0.6571</td>
                <td>0.7925</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Output Model Validation</title>
        <p>A 2-tiered verification approach was used to validate the successful generation of structured CSV outputs. First, the system was designed to export all displayed tabular data along with supplementary metadata from our Athena-derived database, including concept identifiers, domain classifications, class identifications, and standardized vocabulary references.</p>
        <p>The integrity and completeness of these exports were verified through systematic spot-checking against the authoritative OHDSI Athena web repository. For a random sample of 20% (16/79) of the generated concept mappings, we manually compared the exported metadata fields against their corresponding entries on the Athena website to confirm accurate data transfer and representation. Complete success was defined as 100% concordance between our exported metadata and the authoritative source for all sampled entries.</p>
        <p>For the similarity scores included in the exports (calculated using cosine similarity between vector embeddings), we verified the mathematical correctness of the calculations by comparing a subset of scores against independently calculated values. While these scores primarily serve as guidance for users selecting between potential matches rather than as absolute metrics of accuracy, we validated that the system consistently produced the expected similarity values based on the underlying embedding comparisons.</p>
      </sec>
      <sec>
        <title>Clinical Impact Assessment</title>
        <p>We relied on established literature documenting the substantial time requirements for manual OMOP mapping processes to assess the direct clinical impact of our system, particularly regarding time efficiency [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. Previous studies have demonstrated that manual mapping of clinical concepts to standardized vocabularies typically requires significant informatics expertise and can take significant time for comprehensive dataset mapping, not assessing the time necessary for clinical-technical team dyad interactions [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>].</p>
        <p>While we did not conduct direct comparative timing studies, our expert reviewers (MCBA and RWH) provided subjective estimates of time savings based on their experience with manual OMOP mapping processes. These estimates considered factors including dataset size, concept complexity, and domain specificity. For evaluating the usability of our system from the perspective of end users, we used the System Usability Scale (SUS), a widely used and validated tool for assessing the perceived usability of software and other digital health systems [<xref ref-type="bibr" rid="ref25">25</xref>]. SUS scores range from 0 to 100, with higher scores indicating better usability and a score of 68 considered the average benchmark [<xref ref-type="bibr" rid="ref25">25</xref>].</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>This study involved the development and validation of a computational tool using LLMs to automate the transformation of clinical data into the OMOP CDM. This work builds upon data and processes developed under the Wake Forest IMPOWR Dissemination Education and Coordination Center (IDEA-CC) project [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. While this study focuses on the development and validation of a software tool and does not directly involve interaction with human subjects, the parent project, IDEA-CC, does involve human subject research. The Wake Forest School of Medicine Institutional Review Board has reviewed and approved the IDEA-CC project (IRB00080548), with approval activated on April 2, 2022, and is currently active. This manuscript does not contain any images that could identify individual participants or users.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Model Performance</title>
        <p>Using the pilot set of 76 clinical trial CDE terms, our model achieved an AUC of 0.9975 (<xref ref-type="table" rid="table1">Table 1</xref>), indicating high accuracy in identifying correct mappings. Performance metrics were evaluated across similarity score thresholds from 0.85 to 1.0, with precision ranging from 0.92 to 0.99 and recall scores between 0.88 and 0.97. <italic>F</italic><sub>1</sub>-scores remained consistently above 0.9 across all tested thresholds, demonstrating robust performance even as classification cutoffs varied.</p>
      </sec>
      <sec>
        <title>Mapping Accuracy by Term Category</title>
        <p>Analysis of mapping performance across different types of clinical terms revealed distinct patterns of accuracy:</p>
        <sec>
          <title>Clinical Observations and Symptoms</title>
          <p>The system demonstrated particularly strong performance with clinical terms, where semantic relationships were effectively captured by the embedding model. For instance, the system successfully mapped complex descriptive terms such as “chest pain during physical activity” to standardized concepts, in particular “exercise-induced angina” with similarity scores above 0.9.</p>
        </sec>
        <sec>
          <title>Demographic Information</title>
          <p>The supplemental CDE to OMOP mapping file demonstrates the high accuracy of our semantic matching approach (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Demographic terms showed consistently high accuracy, with terms, namely “Not Hispanic or Latino,” achieving exact matches (100% similarity) with corresponding standardized vocabulary concepts (LOINC: LA19555-4). The system effectively identified both primary matches and relevant alternatives, such as “Non-Hispanic or Latino” (LOINC: LA10597-5) with 93.89% similarity. The system effectively handled complex concepts, for example, “Transgender woman/trans woman/male-to-female (MTF)” by identifying the semantically appropriate clinical finding concept “Male-to-female transsexual” (similarity score 0.947). This demonstrates the tool’s ability to capture nuanced terminology beyond exact string matching.</p>
        </sec>
        <sec>
          <title>Survey Responses and Categorical Data</title>
          <p>For categorical response fields, such as relationship status questions, the system successfully mapped to appropriate standardized concepts while maintaining the semantic context. For example, “What category best describes your current relationship status?” was correctly mapped to the Systematized Nomenclature of Medicine (SNOMED) concept “Marital Status” (125680007) with an 86.9% similarity score.</p>
        </sec>
        <sec>
          <title>Analysis of Error Patterns</title>
          <p>Concepts with domain-specific meanings occasionally received lower similarity scores, particularly when equivalent concepts existed across multiple vocabularies. The system addresses this by presenting ranked alternatives, allowing researchers to select the most contextually appropriate mapping when automatic selection is ambiguous.</p>
        </sec>
      </sec>
      <sec>
        <title>System Implementation Performance</title>
        <p>The technical implementation demonstrated efficient processing capabilities across different usage patterns:</p>
        <sec>
          <title>Batch Processing</title>
          <p>The asynchronous processing architecture successfully handled concurrent requests through Redis queue management, enabling efficient processing of large datasets. The system maintained consistent performance when processing both individual terms and batch uploads through REDCap integration.</p>
        </sec>
        <sec>
          <title>Optimization and Performance Considerations</title>
          <p>The current implementation uses several optimization strategies to handle multiple users and asynchronous processing. The system uses Redis for queue management with Bull queue integration, running on a PM2-managed Node.js Express service. This architecture ensures optimal performance while managing memory constraints from the large MongoDB collections required for cosine similarity calculations.</p>
        </sec>
        <sec>
          <title>Output Generation</title>
          <p>The system successfully generated structured CSV outputs containing comprehensive mapping information, including:</p>
          <list list-type="bullet">
            <list-item>
              <p>Detailed concept metadata from the OHDSI vocabularies;</p>
            </list-item>
            <list-item>
              <p>Similarity scores for primary and alternative matches;</p>
            </list-item>
            <list-item>
              <p>Domain and concept class identifications; and</p>
            </list-item>
            <list-item>
              <p>Standardized vocabulary references.</p>
            </list-item>
          </list>
        </sec>
        <sec>
          <title>User Interface Effectiveness</title>
          <p>Usability testing demonstrated strong performance of the interface design, with SUS scores of 85 and 87.5 from our 2 expert evaluators, indicating excellent usability well above the average benchmark score of 68. Researchers successfully used all 3 input methods (direct entry, REDCap integration, and file upload), with particular appreciation for the ability to review and select from ranked matching options when automatic mappings required refinement. The qualitative feedback highlighted the system's effectiveness in handling both semantic content and meta-information, as it appropriately preserved structural elements while focusing semantic mapping efforts on clinical content requiring standardization.</p>
        </sec>
        <sec>
          <title>Direct Clinical Impact</title>
          <p>Based on expert assessment and literature review, our tool substantially reduces the technical barriers for smaller research teams to participate in large-scale data-sharing initiatives. Expert reviewers estimated that the mapping process that typically requires weeks of dedicated informatics support can now be accomplished in hours using our automated system. Some of that time burden stems from the need to connect clinical teams with technical teams with the expertise to perform the mapping. The literature in this area focuses on the actual time spent mapping (and tends to allude to substantive time rather than concrete numbers) [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>] and not the logistical factors of connecting meetings, workflows, and technical-clinical team interfaces. This efficiency gain is particularly impactful for NIH HEAL Initiative research teams who previously lacked the technical capacity to transform their data into the OMOP format. In practical application, research teams reported new capabilities to contribute to the broader data ecosystem, with immediate implications for accelerating comparative effectiveness research across multiple pain treatment studies.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Democratization of OMOP Concept Mapping</title>
        <p>This study presents a novel tool that leverages LLMs to automate the transformation of heterogeneous clinical data into the OMOP CDM, addressing a critical barrier in digital health research. The high accuracy demonstrated by our feasibility model, with an AUC of 0.9975, suggests that LLM-based approaches can effectively support the complex task of semantic matching in clinical data harmonization. The development of a user interface accessible to clinical researchers without extensive informatics expertise represents a significant step toward widening participation in large-scale digital health research initiatives.</p>
        <p>The implications of this work extend beyond technical performance metrics to address fundamental challenges in the digital health ecosystem. As health care data continue to expand across modalities, shifting from traditional clinical trials and electronic health records to mobile health devices and patient-reported outcomes [<xref ref-type="bibr" rid="ref1">1</xref>], the need for efficient data harmonization becomes increasingly critical. Our tool’s ability to process diverse data types through semantic embedding demonstrates its potential to support this growing complexity.</p>
      </sec>
      <sec>
        <title>Principal Findings</title>
        <p>Our LLM-based tool successfully automates the mapping of clinical data elements to OMOP concepts with high accuracy (AUC 0.9975). The 3-tiered semantic matching approach effectively captures relationships between research-level data representation and standardized vocabularies, enabling broader participation in large-scale data harmonization initiatives.</p>
      </sec>
      <sec>
        <title>Comparison to Previous Work</title>
        <p>Previous data harmonization approaches have relied primarily on exact string matching or manual mapping processes requiring specialized informatics expertise. Our implementation advances this field by leveraging LLM-based semantic similarity, significantly reducing the technical expertise required [<xref ref-type="bibr" rid="ref28">28</xref>]. While tools such as Usagi (OHDSI team) provide valuable mapping capabilities, our implementation uniquely combines embedding-based similarity with a researcher-focused interface designed specifically for clinical research workflows. The system’s ability to handle both semantic content and meta-information represents an advancement in automated OMOP mapping, particularly in processing complex clinical trial data [<xref ref-type="bibr" rid="ref10">10</xref>].</p>
        <p>Traditional OMOP conversion approaches typically require substantial technical expertise and resources, making them feasible primarily for large-scale institutional projects [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. Our tool addresses this gap by enabling smaller research teams to participate in data standardization efforts. This democratization of OMOP conversion could unlock significant value from currently siloed clinical trial and study data, particularly from smaller research initiatives that would otherwise lack resources for data transformation projects.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>The system demonstrates strong performance across diverse data types and clinical domains. The user interface design enables clinical researchers without extensive informatics training to participate directly in data standardization processes, addressing a critical gap in current approaches. Despite these strengths, several limitations remain. First, while our implementation significantly reduces technical barriers, some informatics knowledge remains necessary for extracting, transforming, and loading processes. We are addressing this through companion tools that automate table construction and data transformation steps. Second, the current architecture exhibits performance constraints due to memory requirements for large embedding collections. Future iterations will implement optimized vector storage solutions and approximate nearest neighbor algorithms to enhance efficiency. Third, our validation, while robust, has focused primarily on specific clinical domains (pain, opioid use, and COVID-19). Broader validation across additional domains would strengthen confidence in the tool’s generalizability.</p>
      </sec>
      <sec>
        <title>Future Directions</title>
        <p>Several promising avenues for enhancement emerge from this work. First, the implementation of specialized vector database technologies could significantly improve performance compared to our current MongoDB-based approach. Second, approximate nearest neighbor algorithms [<xref ref-type="bibr" rid="ref29">29</xref>] would optimize similarity calculations for larger vocabulary sets. Finally, expanded validation studies across diverse clinical specialties would further demonstrate the tool’s utility across the healthcare research spectrum.</p>
      </sec>
      <sec>
        <title>Conclusion</title>
        <p>Our LLM-based tool provides an accessible and efficient means to map and convert diverse clinical data into the OMOP CDM, enabling broader utilization of OHDSI’s analytic capabilities and fostering collaborative research using standardized FAIR data. The system’s high accuracy in concept mapping, demonstrated through both exact matches and semantic similarity scoring, addresses a critical need in the digital health research community.</p>
        <p>The combination of embedding-based semantic matching and user-friendly interface design addresses both technical and practical barriers to data harmonization. By achieving precision scores ranging from 0.92 to 0.99 across different types of clinical terms, the system demonstrates reliable performance in automated concept mapping while maintaining the flexibility needed for diverse research contexts.</p>
        <p>The tool’s successful processing of varied data types ranging from clinical observations to demographic information supports its potential utility across multiple research domains. This aligns with the goals of the NIH HEAL Initiative Data Ecosystem [<xref ref-type="bibr" rid="ref26">26</xref>,<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref30">30</xref>-<xref ref-type="bibr" rid="ref34">34</xref>] and the NIH Office of Data Science Strategy to make biomedical research data FAIR [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>By lowering technical barriers to data harmonization while maintaining high accuracy standards, this tool could accelerate the transition toward a more connected digital health research ecosystem. The ability for clinical researchers to directly participate in data standardization processes without extensive informatics expertise could lead to more comprehensive and nuanced data transformations, ultimately supporting more robust research findings.</p>
        <p>Future work should focus on implementing performance optimizations; expanding validation across additional clinical domains; and further reducing the technical expertise required for complete extract, transform, and load processes. These improvements will help maximize the tool’s impact on accelerating clinical data interoperability and reuse, particularly for smaller research teams and institutions that may currently lack resources for comprehensive data standardization efforts.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>CDE2OMOP mapping terms and outputs. CDE2OMOP: common data elements to Observational Medical Outcomes Partnership.</p>
        <media xlink:href="jmir_v27i1e69004_app1.docx" xlink:title="DOCX File , 102 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>CDE2OMOP Github compressed file. CDE2OMOP: common data elements to Observational Medical Outcomes Partnership.</p>
        <media xlink:href="jmir_v27i1e69004_app2.zip" xlink:title="ZIP File  (Zip Archive), 22041 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>CDE2OMOP Github "README" file. CDE2OMOP: common data elements to Observational Medical Outcomes Partnership.</p>
        <media xlink:href="jmir_v27i1e69004_app3.pdf" xlink:title="PDF File  (Adobe PDF File), 420 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">AUC</term>
          <def>
            <p>area under the curve</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CDE</term>
          <def>
            <p>common data elements</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CDM</term>
          <def>
            <p>common data model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">FAIR</term>
          <def>
            <p>Findable, Accessible, Interoperable, Reusable</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">HEAL</term>
          <def>
            <p>Helping to End Addiction Long-term</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">IDEA-CC</term>
          <def>
            <p>IMPOWR Dissemination Education and Coordination Center</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">LLM</term>
          <def>
            <p>large language model</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">LOINC</term>
          <def>
            <p>Logical Observation Identifiers Names and Codes</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">N3C</term>
          <def>
            <p>National COVID Cohort Collaborative</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">NIH</term>
          <def>
            <p>National Institutes of Health</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">OHDSI</term>
          <def>
            <p>Observational Health Data Sciences and Informatics</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">OMOP</term>
          <def>
            <p>Observational Medical Outcomes Partnership</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">REDCap</term>
          <def>
            <p>Research Electronic Data Capture</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">SNOMED</term>
          <def>
            <p>Systematized Nomenclature of Medicine</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">SUS</term>
          <def>
            <p>System Usability Scale</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>The common data elements (CDEs) concepts for demographics available in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> are publicly available from the National Institutes of Health (NIH) Helping to End Addiction Long-term (NIH HEAL) CDEs [<xref ref-type="bibr" rid="ref35">35</xref>], to allow broad reusability and alignment with existing work. This concept set was developed by NIH HEAL Initiative’s CDE program to standardize demographics. This version was revised to add additional subconcept answer choices by the CDE working group of the IMPOWR (Integrative Management of Chronic Pain and OUD [Opioid Use Disorder] for Whole Recovery) Network in 2021-2022, involving researchers and community partners from the University of Pittsburgh (RM1DA055311, principal investigators: Merlin, Hamm, and Winstanley), Albert Einstein College of Medicine (RM1DA055437, principal investigators: Starrels, Arnsten, and Gabbay), Yale University (RM1DA055310, principal investigators: Becker, Barry, and Fiellin), and University of New Mexico (RM1DA055301, principal investigators: Witkiewitz and Pearson), and the IMPOWR Coordination and Dissemination Center at Wake Forest University Health Sciences (R24DA055306, principal investigator: MCBA). The IMPOWR Network is funded by the National Institute on Drug Abuse (NIDA) of the NIH through the NIH HEAL Initiative. This work was supported by the Office of The Director, NIH; NIDA; and through the NIH HEAL Initiative under awards R24DA055306, U24DA058606, U24DA057612, R24DA055306-01S1, R24DA055306-02S1, and R25DA061740. The content of this publication is solely the responsibility of the authors and does not necessarily represent the official views of NIDA, the NIH HEAL Initiative, or the sites that participated in the IMPOWR CDE working group.</p>
    </ack>
    <notes>
      <title>Data Availability</title>
      <p>The GitHub compressed file and “README” file for implementation are given as <xref ref-type="supplementary-material" rid="app2">Multimedia Appendices 2</xref> and <xref ref-type="supplementary-material" rid="app3">3</xref>.</p>
    </notes>
    <fn-group>
      <fn fn-type="conflict">
        <p>MCBA has received National Institutes of Health (NIH) grants as listed (NIH grant not related to this work: U01DA057016). RWH has received NIH grants as listed (NIH grants not related to this work: UH3AR077360); grants from Nevro, Inc (research funds to the institution on the topic of painful diabetic neuropathy and not related to this work); and grants from State Farm (expert/consulting not related to this work).</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Susukida</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Amin-Esmaeili</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Mayo-Wilson</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Mojtabai</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Data management in substance use disorder treatment research: implications from data harmonization of national institute on drug abuse-funded randomized controlled trials</article-title>
          <source>Clin Trials</source>
          <year>2021</year>
          <volume>18</volume>
          <issue>2</issue>
          <fpage>215</fpage>
          <lpage>225</lpage>
          <pub-id pub-id-type="doi">10.1177/1740774520972687</pub-id>
          <pub-id pub-id-type="medline">33258697</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>Suchard</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Schuemie</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Krumholz</surname>
              <given-names>HM</given-names>
            </name>
            <name name-style="western">
              <surname>You</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pratt</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Reich</surname>
              <given-names>CG</given-names>
            </name>
            <name name-style="western">
              <surname>Duke</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Madigan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>PB</given-names>
            </name>
          </person-group>
          <article-title>Comprehensive comparative effectiveness and safety of first-line antihypertensive drug classes: a systematic, multinational, large-scale analysis</article-title>
          <source>Lancet</source>
          <year>2019</year>
          <volume>394</volume>
          <issue>10211</issue>
          <fpage>1816</fpage>
          <lpage>1826</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/31668726"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/S0140-6736(19)32317-7</pub-id>
          <pub-id pub-id-type="medline">31668726</pub-id>
          <pub-id pub-id-type="pii">S0140-6736(19)32317-7</pub-id>
          <pub-id pub-id-type="pmcid">PMC6924620</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Papez</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Moinat</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Voss</surname>
              <given-names>EA</given-names>
            </name>
            <name name-style="western">
              <surname>Bazakou</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>van Winzum</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Peviani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Payralbe</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kallfelz</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Asselbergs</surname>
              <given-names>FW</given-names>
            </name>
            <name name-style="western">
              <surname>Prieto-Alhambra</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Dobson</surname>
              <given-names>RJB</given-names>
            </name>
            <name name-style="western">
              <surname>Denaxas</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Transforming and evaluating the UK biobank to the OMOP common data model for COVID-19 research and beyond</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2022</year>
          <volume>30</volume>
          <issue>1</issue>
          <fpage>103</fpage>
          <lpage>111</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36227072"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocac203</pub-id>
          <pub-id pub-id-type="medline">36227072</pub-id>
          <pub-id pub-id-type="pii">6760234</pub-id>
          <pub-id pub-id-type="pmcid">PMC9619789</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Burn</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>You</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Sena</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Kostka</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Abedtash</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Abrahão</surname>
              <given-names>MTF</given-names>
            </name>
            <name name-style="western">
              <surname>Alberga</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alghoul</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Alser</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Alshammari</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Aragon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Areia</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Banda</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Culhane</surname>
              <given-names>AC</given-names>
            </name>
          </person-group>
          <article-title>Deep phenotyping of 34,128 adult patients hospitalised with COVID-19 in an international network study</article-title>
          <source>Nat Commun</source>
          <year>2020</year>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>5009</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41467-020-18849-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41467-020-18849-z</pub-id>
          <pub-id pub-id-type="medline">33024121</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41467-020-18849-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC7538555</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>Levinson</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Niestroy</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Al Manir</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fairchild</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Lake</surname>
              <given-names>DE</given-names>
            </name>
            <name name-style="western">
              <surname>Moorman</surname>
              <given-names>JR</given-names>
            </name>
            <name name-style="western">
              <surname>Clark</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>FAIRSCAPE: a framework for FAIR and reproducible biomedical analytics</article-title>
          <source>Neuroinformatics</source>
          <year>2022</year>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>187</fpage>
          <lpage>202</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/34264488"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12021-021-09529-4</pub-id>
          <pub-id pub-id-type="medline">34264488</pub-id>
          <pub-id pub-id-type="pii">10.1007/s12021-021-09529-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC8760356</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>Reinecke</surname>
              <given-names>I</given-names>
            </name>
            <name name-style="western">
              <surname>Zoch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Reich</surname>
              <given-names>C</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>The usage of OHDSI OMOP - a scoping review</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <volume>283</volume>
          <fpage>95</fpage>
          <lpage>103</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210546</pub-id>
          <pub-id pub-id-type="medline">34545824</pub-id>
          <pub-id pub-id-type="pii">SHTI210546</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>Hripcsak</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Schuemie</surname>
              <given-names>MJ</given-names>
            </name>
            <name name-style="western">
              <surname>Madigan</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Ryan</surname>
              <given-names>PB</given-names>
            </name>
            <name name-style="western">
              <surname>Suchard</surname>
              <given-names>MA</given-names>
            </name>
          </person-group>
          <article-title>Drawing reproducible conclusions from observational clinical data with OHDSI</article-title>
          <source>Yearb Med Inform</source>
          <year>2021</year>
          <volume>30</volume>
          <issue>1</issue>
          <fpage>283</fpage>
          <lpage>289</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0041-1726481"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0041-1726481</pub-id>
          <pub-id pub-id-type="medline">33882595</pub-id>
          <pub-id pub-id-type="pmcid">PMC8416226</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>Kang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Yoon</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>HY</given-names>
            </name>
            <name name-style="western">
              <surname>Jo</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Kam</surname>
              <given-names>HJ</given-names>
            </name>
          </person-group>
          <article-title>Deep-learning-based automated terminology mapping in OMOP-CDM</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2021</year>
          <volume>28</volume>
          <issue>7</issue>
          <fpage>1489</fpage>
          <lpage>1496</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/33987667"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/jamia/ocab030</pub-id>
          <pub-id pub-id-type="medline">33987667</pub-id>
          <pub-id pub-id-type="pii">6275415</pub-id>
          <pub-id pub-id-type="pmcid">PMC8279781</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>Zoch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Gierschner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gruhl</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Leutner</surname>
              <given-names>LA</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>Adaption of the OMOP CDM for Rare Diseases</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <volume>281</volume>
          <fpage>138</fpage>
          <lpage>142</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210136</pub-id>
          <pub-id pub-id-type="medline">34042721</pub-id>
          <pub-id pub-id-type="pii">SHTI210136</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>Sun</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Butler</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stewart</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yuan</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Southard</surname>
              <given-names>CT</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JH</given-names>
            </name>
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Building an OMOP common data model-compliant annotated corpus for COVID-19 clinical trials</article-title>
          <source>J Biomed Inform</source>
          <year>2021</year>
          <volume>118</volume>
          <fpage>103790</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(21)00119-2"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2021.103790</pub-id>
          <pub-id pub-id-type="medline">33887457</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(21)00119-2</pub-id>
          <pub-id pub-id-type="pmcid">PMC8079156</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>Maier</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Kapsner</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Mate</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Prokosch</surname>
              <given-names>HU</given-names>
            </name>
            <name name-style="western">
              <surname>Kraus</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Patient cohort identification on time series data using the OMOP common data model</article-title>
          <source>Appl Clin Inform</source>
          <year>2021</year>
          <volume>12</volume>
          <issue>1</issue>
          <fpage>57</fpage>
          <lpage>64</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0040-1721481"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0040-1721481</pub-id>
          <pub-id pub-id-type="medline">33506478</pub-id>
          <pub-id pub-id-type="pmcid">PMC7840432</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>Majeed</surname>
              <given-names>RW</given-names>
            </name>
            <name name-style="western">
              <surname>Fischer</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Günther</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Accessing OMOP common data model repositories with the i2b2 webclient - algorithm for automatic query translation</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2021</year>
          <volume>278</volume>
          <fpage>251</fpage>
          <lpage>259</lpage>
          <pub-id pub-id-type="doi">10.3233/SHTI210077</pub-id>
          <pub-id pub-id-type="medline">34042902</pub-id>
          <pub-id pub-id-type="pii">SHTI210077</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rinner</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gezgin</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Wendl</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Gall</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>A clinical data warehouse based on OMOP and i2b2 for Austrian health claims data</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2018</year>
          <volume>248</volume>
          <fpage>94</fpage>
          <lpage>99</lpage>
          <pub-id pub-id-type="medline">29726424</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>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>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pone.0212463"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0212463</pub-id>
          <pub-id pub-id-type="medline">30779778</pub-id>
          <pub-id pub-id-type="pii">PONE-D-18-34751</pub-id>
          <pub-id pub-id-type="pmcid">PMC6380544</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>Ahmadi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Zoch</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Guengoeze</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Facchinello</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Mondorf</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Stratmann</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Musleh</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Erasmus</surname>
              <given-names>HP</given-names>
            </name>
            <name name-style="western">
              <surname>Tchertov</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Gebler</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Schaaf</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Frischen</surname>
              <given-names>LS</given-names>
            </name>
            <name name-style="western">
              <surname>Nasirian</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Dai</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Henke</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Tremblay</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Srisuwananukorn</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Bornhäuser</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Röllig</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Eckardt</surname>
              <given-names>JN</given-names>
            </name>
            <name name-style="western">
              <surname>Middeke</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Wolfien</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sedlmayr</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>How to customize common data models for rare diseases: an OMOP-based implementation and lessons learned</article-title>
          <source>Orphanet J Rare Dis</source>
          <year>2024</year>
          <volume>19</volume>
          <issue>1</issue>
          <fpage>298</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://ojrd.biomedcentral.com/articles/10.1186/s13023-024-03312-9"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/s13023-024-03312-9</pub-id>
          <pub-id pub-id-type="medline">39143600</pub-id>
          <pub-id pub-id-type="pii">10.1186/s13023-024-03312-9</pub-id>
          <pub-id pub-id-type="pmcid">PMC11325822</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>Hudson</surname>
              <given-names>CL</given-names>
            </name>
            <name name-style="western">
              <surname>Topaloglu</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Bian</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Hogan</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Kieber-Emmons</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Automated tools for clinical research data quality control using NCI common data elements</article-title>
          <source>AMIA Jt Summits Transl Sci Proc</source>
          <year>2014</year>
          <volume>2014</volume>
          <fpage>60</fpage>
          <lpage>69</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/25717402"/>
          </comment>
          <pub-id pub-id-type="medline">25717402</pub-id>
          <pub-id pub-id-type="pmcid">PMC4333694</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>Pesquita</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Faria</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Falcão</surname>
              <given-names>AO</given-names>
            </name>
            <name name-style="western">
              <surname>Lord</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Couto</surname>
              <given-names>FM</given-names>
            </name>
          </person-group>
          <article-title>Semantic similarity in biomedical ontologies</article-title>
          <source>PLoS Comput Biol</source>
          <year>2009</year>
          <volume>5</volume>
          <issue>7</issue>
          <fpage>e1000443</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://dx.plos.org/10.1371/journal.pcbi.1000443"/>
          </comment>
          <pub-id pub-id-type="doi">10.1371/journal.pcbi.1000443</pub-id>
          <pub-id pub-id-type="medline">19649320</pub-id>
          <pub-id pub-id-type="pmcid">PMC2712090</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bodenreider</surname>
              <given-names>O</given-names>
            </name>
          </person-group>
          <article-title>The Unified Medical Language System (UMLS): integrating biomedical terminology</article-title>
          <source>Nucleic Acids Res</source>
          <year>2004</year>
          <volume>32</volume>
          <issue>Database issue</issue>
          <fpage>D267</fpage>
          <lpage>D270</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/14681409"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/nar/gkh061</pub-id>
          <pub-id pub-id-type="medline">14681409</pub-id>
          <pub-id pub-id-type="pii">32/suppl_1/D267</pub-id>
          <pub-id pub-id-type="pmcid">PMC308795</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yip</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Mete</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Topaloglu</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Kockara</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Concept discovery for pathology reports using an N-gram model</article-title>
          <source>Summit Transl Bioinform</source>
          <year>2010</year>
          <volume>2010</volume>
          <fpage>43</fpage>
          <lpage>47</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/21347147"/>
          </comment>
          <pub-id pub-id-type="medline">21347147</pub-id>
          <pub-id pub-id-type="pmcid">PMC3041542</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Garla</surname>
              <given-names>VN</given-names>
            </name>
            <name name-style="western">
              <surname>Brandt</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Semantic similarity in the biomedical domain: an evaluation across knowledge sources</article-title>
          <source>BMC Bioinformatics</source>
          <year>2012</year>
          <volume>13</volume>
          <fpage>261</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://bmcbioinformatics.biomedcentral.com/articles/10.1186/1471-2105-13-261"/>
          </comment>
          <pub-id pub-id-type="doi">10.1186/1471-2105-13-261</pub-id>
          <pub-id pub-id-type="medline">23046094</pub-id>
          <pub-id pub-id-type="pii">1471-2105-13-261</pub-id>
          <pub-id pub-id-type="pmcid">PMC3533586</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Gibson</surname>
              <given-names>CC</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Davis</surname>
              <given-names>CT</given-names>
            </name>
            <name name-style="western">
              <surname>Bowman-Kirigin</surname>
              <given-names>JA</given-names>
            </name>
            <name name-style="western">
              <surname>Chan</surname>
              <given-names>AC</given-names>
            </name>
            <name name-style="western">
              <surname>Ling</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Walker</surname>
              <given-names>AE</given-names>
            </name>
            <name name-style="western">
              <surname>Goitre</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Delle Monache</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Retta</surname>
              <given-names>SF</given-names>
            </name>
            <name name-style="western">
              <surname>Shiu</surname>
              <given-names>YE</given-names>
            </name>
            <name name-style="western">
              <surname>Grossmann</surname>
              <given-names>AH</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>KR</given-names>
            </name>
            <name name-style="western">
              <surname>Donato</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Lesniewski</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Whitehead</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>DY</given-names>
            </name>
          </person-group>
          <article-title>Strategy for identifying repurposed drugs for the treatment of cerebral cavernous malformation</article-title>
          <source>Circulation</source>
          <year>2015</year>
          <volume>131</volume>
          <issue>3</issue>
          <fpage>289</fpage>
          <lpage>299</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/25486933"/>
          </comment>
          <pub-id pub-id-type="doi">10.1161/CIRCULATIONAHA.114.010403</pub-id>
          <pub-id pub-id-type="medline">25486933</pub-id>
          <pub-id pub-id-type="pii">CIRCULATIONAHA.114.010403</pub-id>
          <pub-id pub-id-type="pmcid">PMC4356181</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kelly</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Ghafurian</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>West</surname>
              <given-names>RL</given-names>
            </name>
            <name name-style="western">
              <surname>Reitter</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>Indirect associations in learning semantic and syntactic lexical relationships</article-title>
          <source>J Mem Lang</source>
          <year>2020</year>
          <volume>115</volume>
          <fpage>104153</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.jml.2020.104153"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jml.2020.104153</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Sin</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Tsapepas</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Dale</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Husain</surname>
              <given-names>SA</given-names>
            </name>
            <name name-style="western">
              <surname>Mohan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Natarajan</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Content coverage evaluation of the OMOP vocabulary on the transplant domain focusing on concepts relevant for kidney transplant outcomes analysis</article-title>
          <source>Appl Clin Inform</source>
          <year>2020</year>
          <volume>11</volume>
          <issue>4</issue>
          <fpage>650</fpage>
          <lpage>658</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.thieme-connect.com/DOI/DOI?10.1055/s-0040-1716528"/>
          </comment>
          <pub-id pub-id-type="doi">10.1055/s-0040-1716528</pub-id>
          <pub-id pub-id-type="medline">33027834</pub-id>
          <pub-id pub-id-type="pmcid">PMC7557323</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>Ji</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Yi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hwang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Converting clinical document architecture documents to the common data model for incorporating health information exchange data in observational health studies: CDA to CDM</article-title>
          <source>J Biomed Inform</source>
          <year>2020</year>
          <volume>107</volume>
          <fpage>103459</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S1532-0464(20)30087-3"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jbi.2020.103459</pub-id>
          <pub-id pub-id-type="medline">32470694</pub-id>
          <pub-id pub-id-type="pii">S1532-0464(20)30087-3</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>Hyzy</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bond</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Mulvenna</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bai</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dix</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Leigh</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Hunt</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>System usability scale benchmarking for digital health apps: meta-analysis</article-title>
          <source>JMIR Mhealth Uhealth</source>
          <year>2022</year>
          <volume>10</volume>
          <issue>8</issue>
          <fpage>e37290</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://mhealth.jmir.org/2022/8/e37290/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/37290</pub-id>
          <pub-id pub-id-type="medline">35980732</pub-id>
          <pub-id pub-id-type="pii">v10i8e37290</pub-id>
          <pub-id pub-id-type="pmcid">PMC9437782</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>Adams</surname>
              <given-names>MCB</given-names>
            </name>
            <name name-style="western">
              <surname>Hurley</surname>
              <given-names>RW</given-names>
            </name>
            <name name-style="western">
              <surname>Siddons</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Topaloglu</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Wandner</surname>
              <given-names>LD</given-names>
            </name>
          </person-group>
          <article-title>NIH HEAL clinical data elements (CDE) implementation: NIH HEAL Initiative IMPOWR network IDEA-CC</article-title>
          <source>Pain Med</source>
          <year>2023</year>
          <volume>24</volume>
          <issue>7</issue>
          <fpage>743</fpage>
          <lpage>749</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36799548"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/pm/pnad018</pub-id>
          <pub-id pub-id-type="medline">36799548</pub-id>
          <pub-id pub-id-type="pii">7043983</pub-id>
          <pub-id pub-id-type="pmcid">PMC10321760</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>Adams</surname>
              <given-names>MCB</given-names>
            </name>
            <name name-style="western">
              <surname>Hurley</surname>
              <given-names>RW</given-names>
            </name>
            <name name-style="western">
              <surname>Topaloglu</surname>
              <given-names>U</given-names>
            </name>
          </person-group>
          <article-title>Connecting chronic pain and opioid use disorder clinical trials through data harmonization: Wake Forest IMPOWR Dissemination, Education, and Coordination center (IDEA-CC)</article-title>
          <source>Subst Use Addctn J</source>
          <year>2025</year>
          <volume>46</volume>
          <issue>1</issue>
          <fpage>141</fpage>
          <lpage>145</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://journals.sagepub.com/doi/abs/10.1177/29767342241236287?url_ver=Z39.88-2003&amp;rfr_id=ori:rid:crossref.org&amp;rfr_dat=cr_pub  0pubmed"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/29767342241236287</pub-id>
          <pub-id pub-id-type="medline">38516882</pub-id>
          <pub-id pub-id-type="pmcid">PMC11884317</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Burn</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>You</surname>
              <given-names>SC</given-names>
            </name>
            <name name-style="western">
              <surname>Sena</surname>
              <given-names>AG</given-names>
            </name>
            <name name-style="western">
              <surname>Kostka</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Abedtash</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Abrahão</surname>
              <given-names>MTF</given-names>
            </name>
            <name name-style="western">
              <surname>Alberga</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Alghoul</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Alser</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Alshammari</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Aragon</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Areia</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Banda</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Cho</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Culhane</surname>
              <given-names>AC</given-names>
            </name>
          </person-group>
          <article-title>Deep phenotyping of 34,128 adult patients hospitalised with COVID-19 in an international network study</article-title>
          <source>Nat Commun</source>
          <year>2020</year>
          <volume>11</volume>
          <issue>1</issue>
          <fpage>5009</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41467-020-18849-z"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41467-020-18849-z</pub-id>
          <pub-id pub-id-type="medline">33024121</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41467-020-18849-z</pub-id>
          <pub-id pub-id-type="pmcid">PMC7538555</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>El Aboudi</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Benhlima</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Big data management for healthcare systems: architecture, requirements, and implementation</article-title>
          <source>Adv Bioinformatics</source>
          <year>2018</year>
          <volume>2018</volume>
          <fpage>4059018</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1155/2018/4059018"/>
          </comment>
          <pub-id pub-id-type="doi">10.1155/2018/4059018</pub-id>
          <pub-id pub-id-type="medline">30034468</pub-id>
          <pub-id pub-id-type="pmcid">PMC6032968</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>Adams</surname>
              <given-names>MCB</given-names>
            </name>
            <name name-style="western">
              <surname>Bann</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Bayman</surname>
              <given-names>EO</given-names>
            </name>
            <name name-style="western">
              <surname>Chao</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hergenroeder</surname>
              <given-names>GW</given-names>
            </name>
            <name name-style="western">
              <surname>Knott</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lindquist</surname>
              <given-names>MA</given-names>
            </name>
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>ZD</given-names>
            </name>
            <name name-style="western">
              <surname>Martin</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Martone</surname>
              <given-names>ME</given-names>
            </name>
            <name name-style="western">
              <surname>McCarthy</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>McCumber</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Meropol</surname>
              <given-names>SB</given-names>
            </name>
            <name name-style="western">
              <surname>Ridenour</surname>
              <given-names>TA</given-names>
            </name>
            <name name-style="western">
              <surname>Saavedra</surname>
              <given-names>LM</given-names>
            </name>
            <name name-style="western">
              <surname>Sarker</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Anstrom</surname>
              <given-names>KJ</given-names>
            </name>
            <name name-style="western">
              <surname>Thompson</surname>
              <given-names>WK</given-names>
            </name>
          </person-group>
          <article-title>Building community through data: the value of a researcher driven open science ecosystem</article-title>
          <source>Pain Med</source>
          <year>2025</year>
          <fpage>pnaf003</fpage>
          <pub-id pub-id-type="doi">10.1093/pm/pnaf003</pub-id>
          <pub-id pub-id-type="medline">39836639</pub-id>
          <pub-id pub-id-type="pii">7965903</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>Adams</surname>
              <given-names>MCB</given-names>
            </name>
            <name name-style="western">
              <surname>Brummett</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Wandner</surname>
              <given-names>LD</given-names>
            </name>
            <name name-style="western">
              <surname>Topaloglu</surname>
              <given-names>U</given-names>
            </name>
            <name name-style="western">
              <surname>Hurley</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <article-title>Michigan body map: connecting the NIH HEAL IMPOWR network to the HEAL ecosystem</article-title>
          <source>Pain Med</source>
          <year>2023</year>
          <volume>24</volume>
          <issue>7</issue>
          <fpage>907</fpage>
          <lpage>909</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/36847455"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/pm/pnad028</pub-id>
          <pub-id pub-id-type="medline">36847455</pub-id>
          <pub-id pub-id-type="pii">7058937</pub-id>
          <pub-id pub-id-type="pmcid">PMC10321764</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>Adams</surname>
              <given-names>MCB</given-names>
            </name>
            <name name-style="western">
              <surname>Hassett</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Clauw</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hurley</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <article-title>The NIH HEAL pain common data elements (CDE): a great start but a long way to the finish line</article-title>
          <source>Pain Med</source>
          <year>2025</year>
          <volume>26</volume>
          <issue>3</issue>
          <fpage>146</fpage>
          <lpage>155</lpage>
          <pub-id pub-id-type="doi">10.1093/pm/pnae110</pub-id>
          <pub-id pub-id-type="medline">39495148</pub-id>
          <pub-id pub-id-type="pii">7874968</pub-id>
          <pub-id pub-id-type="pmcid">PMC11879210</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>Adams</surname>
              <given-names>MCB</given-names>
            </name>
            <name name-style="western">
              <surname>Sward</surname>
              <given-names>KA</given-names>
            </name>
            <name name-style="western">
              <surname>Perkins</surname>
              <given-names>ML</given-names>
            </name>
            <name name-style="western">
              <surname>Hurley</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <article-title>Standardizing research methods for opioid dose comparison: the NIH HEAL morphine milligram equivalent calculator</article-title>
          <source>Pain</source>
          <year>2025</year>
          <pub-id pub-id-type="doi">10.1097/j.pain.0000000000003529</pub-id>
          <pub-id pub-id-type="medline">39907478</pub-id>
          <pub-id pub-id-type="pii">00006396-990000000-00813</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Adams</surname>
              <given-names>MCB</given-names>
            </name>
            <name name-style="western">
              <surname>Hassett</surname>
              <given-names>AL</given-names>
            </name>
            <name name-style="western">
              <surname>Clauw</surname>
              <given-names>DJ</given-names>
            </name>
            <name name-style="western">
              <surname>Hurley</surname>
              <given-names>RW</given-names>
            </name>
          </person-group>
          <article-title>The NIH HEAL pain common data elements (CDE): a great start but a long way to the finish line</article-title>
          <source>Pain Med</source>
          <year>2025</year>
          <volume>26</volume>
          <issue>3</issue>
          <fpage>146</fpage>
          <lpage>155</lpage>
          <pub-id pub-id-type="doi">10.1093/pm/pnae110</pub-id>
          <pub-id pub-id-type="medline">39495148</pub-id>
          <pub-id pub-id-type="pii">7874968</pub-id>
          <pub-id pub-id-type="pmcid">PMC11879210</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="web">
          <article-title>The Helping to End Addiction Long-term® Initiative</article-title>
          <source>National Institutes of Health</source>
          <access-date>2025-04-25</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://heal.nih.gov/">https://heal.nih.gov/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
