<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id><journal-id journal-id-type="publisher-id">medinform</journal-id><journal-id journal-id-type="index">7</journal-id><journal-title>JMIR Medical Informatics</journal-title><abbrev-journal-title>JMIR Med Inform</abbrev-journal-title><issn pub-type="epub">2291-9694</issn><publisher><publisher-name>JMIR Publications</publisher-name><publisher-loc>Toronto, Canada</publisher-loc></publisher></journal-meta><article-meta><article-id pub-id-type="publisher-id">v14i1e80039</article-id><article-id pub-id-type="doi">10.2196/80039</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Developing a Thai User Interface Terminology for Systematized Nomenclature of Medicine Clinical Terms Implementation in Primary Care: Cross-Sectional Content Coverage Analysis</article-title></title-group><contrib-group><contrib contrib-type="author"><name name-style="western"><surname>Tangchitnob</surname><given-names>Nat</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Ponthongmak</surname><given-names>Wanchana</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kijsanayotin</surname><given-names>Boonchai</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Pattanaprateep</surname><given-names>Oraluck</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Phusanti</surname><given-names>Sithakom</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Atiksawedparit</surname><given-names>Pongsakorn</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Suwanthaweemeesuk</surname><given-names>Kamonporn</given-names></name><degrees>MSc, MD</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Siangfu</surname><given-names>Jirayus</given-names></name><degrees>MD</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>McKay</surname><given-names>Gareth J</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Attia</surname><given-names>John</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Thakkinstian</surname><given-names>Ammarin</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib></contrib-group><aff id="aff1"><institution>Department of Clinical Epidemiology and Biostatistics, Faculty of Medicine, Ramathibodi Hospital, Mahidol University</institution><addr-line>Rama 6 Road, Ratchathewi</addr-line><addr-line>Bangkok</addr-line><country>Thailand</country></aff><aff id="aff2"><institution>Thai Health Information Standards Development Center, Health Systems Research Institute, Ministry of Public Health</institution><addr-line>Bangkok</addr-line><country>Thailand</country></aff><aff id="aff3"><institution>Chakri Naruebodindra Medical Institute, Faculty of Medicine Ramathibodi Hospital, Mahidol University</institution><addr-line>Bangkok</addr-line><country>Thailand</country></aff><aff id="aff4"><institution>Chulabhorn Hospital, Chulabhorn Royal Academy</institution><addr-line>Bangkok</addr-line><country>Thailand</country></aff><aff id="aff5"><institution>Centre for Public Health, Queen's University Belfast</institution><addr-line>Belfast</addr-line><country>United Kingdom</country></aff><aff id="aff6"><institution>Centre for Clinical Epidemiology and Biostatistics, School of Medicine and Public Health, University of Newcastle Australia</institution><addr-line>Newcastle</addr-line><country>Australia</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Kanter</surname><given-names>Andrew S</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Ohlsen</surname><given-names>Tessa</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Wanchana Ponthongmak, PhD, Department of Clinical Epidemiology and Biostatistics, Faculty of Medicine, Ramathibodi Hospital, Mahidol University, Rama 6 Road, Ratchathewi, Bangkok, 10400, Thailand, 0833744997; <email>wanchana.pon@mahidol.ac.th</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>9</day><month>3</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e80039</elocation-id><history><date date-type="received"><day>03</day><month>07</month><year>2025</year></date><date date-type="accepted"><day>08</day><month>01</month><year>2026</year></date></history><copyright-statement>&#x00A9; Nat Tangchitnob, Wanchana Ponthongmak, Boonchai Kijsanayotin, Oraluck Pattanaprateep, Sithakom Phusanti, Pongsakorn Atiksawedparit, Kamonporn Suwanthaweemeesuk, Jirayus Siangfu, Gareth J McKay, John Attia, Ammarin Thakkinstian. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 9.3.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org/">https://medinform.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://medinform.jmir.org/2026/1/e80039"/><abstract><sec><title>Background</title><p>Primary care in Thailand often uses mixed Thai-English free-text documentation for diagnoses and clinical problems, limiting standardization, interoperability, and secondary data use. Clinical terminologies like Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT), a comprehensive reference terminology, can bridge this gap through the use of structured clinical data. Developing and mapping a local user interface terminology (UIT) is one of the key strategies for implementing SNOMED CT in real-world clinical settings.</p></sec><sec><title>Objective</title><p>This study aimed to develop a Thai UIT derived from frequently used terms in real-world primary care practice, map these terms to SNOMED CT concepts, and evaluate the extent of concept coverage.</p></sec><sec sec-type="methods"><title>Methods</title><p>Frequently used clinical terms were extracted from outpatient medical records from the family, emergency, and internal medicine departments using a customized tokenization method, N-gram analysis, and expert review. This process yielded 2054 Thai-specific terms. All terms were normalized and mapped to SNOMED CT through manual expert-driven and semiautomated tools. Unmapped terms were subsequently analyzed to identify mapping barriers and solutions.</p></sec><sec sec-type="results"><title>Results</title><p>Of the 2054 Thai-specific terms, 2012 were successfully mapped to 2041 (97.98%) SNOMED CT concepts, including 1781 (85.50%) fully, 123 (5.90%) broader, 56 (2.69%) narrower, 81 (3.89%) inexact mappings, and 42 (2.02%) remained unmapped. Most mappings were one-to-one (1984), with 28 terms mapped to multiple concepts (57), covering 1486 unique SNOMED CT concepts. The remaining 42 unmapped terms were mostly due to culturally specific expressions or concepts not yet represented in SNOMED CT. These were categorized for potential postcoordination, exclusion, or national extension development.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>This study demonstrates the feasibility of developing a Thai UIT mapped to SNOMED CT and describes mapping challenges. The resulting UIT enhances semantic clarity in clinical documentation and supports better interoperability, clinical decision-making, and health data analytics within Thailand&#x2019;s health care system.</p></sec></abstract><kwd-group><kwd>standards and interoperability</kwd><kwd>Systematized Nomenclature of Medicine Clinical Terms</kwd><kwd>SNOMED CT</kwd><kwd>eHealth infrastructure</kwd><kwd>clinical terminology</kwd><kwd>natural language processing</kwd><kwd>concept coverage</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Health care provision is a knowledge-intensive industry, but the quality and accessibility of health care data often fail to adequately meet these needs [<xref ref-type="bibr" rid="ref1">1</xref>]. This is partly due to the data collection process, which commonly takes place in a fast-paced, high-pressure point-of-care environment [<xref ref-type="bibr" rid="ref2">2</xref>], leading to the generation of data sufficient to meet the immediate clinical tasks but often lacking the completeness, standardization, and structure necessary for secondary use, for example, research, that drives health care improvement [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. This limitation may compromise patient safety, care quality, and the ability to generate actionable insights [<xref ref-type="bibr" rid="ref2">2</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. To harness the full potential of health care data, it is essential to prioritize structured data collection that supports timely and effective use across the health care ecosystem [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. Standardized clinical terminology, structured representations of clinical concepts understandable to both humans and computer systems, is an essential technology improvement required for developing reusable data that enables interoperable health care delivery [<xref ref-type="bibr" rid="ref6">6</xref>].</p><p>Because clinical terminology must be comprehensive and support multilingual use, the Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) has been widely adopted internationally as a reference terminology standard that is indispensable for standardized information exchange across clinical care and research settings [<xref ref-type="bibr" rid="ref7">7</xref>]. SNOMED CT adopts a concept-oriented structure; each unique clinical idea is represented by a concept identified by a language-independent, machine-readable unique identifier.</p><p>SNOMED CT consists of 3 core components, including concepts, descriptions, and relationships. Concepts represent the underlying clinical meaning; descriptions provide human-readable terms in multiple languages; and relationships define how concepts are linked within the ontology. A single concept can have multiple descriptions, enabling flexible, precise, and multilingual representation of clinical ideas. Relationships form a poly-hierarchical graph structure to express, distinguish, and connect each clinical concept, maximizing practicality while minimizing ambiguity [<xref ref-type="bibr" rid="ref8">8</xref>]. For example, the concept &#x201C;Nodule of lung (disorder)&#x201D; can be described by multiple terms across languages (eg, English, French, and Swedish), and its meaning is defined through relationships as the child of both &#x201C;Lesion of lung (disorder)&#x201D; and &#x201C;Lung mass (finding),&#x201D; the associated morphology &#x201C;Nodule (morphologic abnormality),&#x201D; and the finding site &#x201C;Lung structure (body structure).&#x201D; This structure enables consistent clinical data representation and supports semantic interoperability. Successfully implementing SNOMED CT not only improves data quality and standardization of clinical data but also enhances the quality of health care through more efficient data use for both clinical and research applications [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. While SNOMED CT offers a robust, language-independent conceptual framework, it does not automatically capture the variability of clinical expressions used in routine practice, particularly in multilingual or mixed-language documentation environments.</p><p>User interface terminology (UIT) refers to the set of terms clinicians use during routine clinical documentation. It consists of user-friendly and context-specific expressions that reflect the natural phrasing and cognitive patterns of clinical practice [<xref ref-type="bibr" rid="ref11">11</xref>]. UITs are typically designed to be used by a defined user group and certain settings, prioritizing efficiency and usability [<xref ref-type="bibr" rid="ref12">12</xref>]. Within the Open Medical Record System (OpenMRS; OpenMRS Inc) ecosystem, many implementations rely on Columbia International eHealth Laboratory (CIEL), an openly maintained UIT that serves as a common starting point for clinical data capture in OpenMRS deployments [<xref ref-type="bibr" rid="ref13">13</xref>]. CIEL supports user-friendly clinical data capture while providing mappings to international reference terminologies (including SNOMED CT) [<xref ref-type="bibr" rid="ref14">14</xref>], enabling the harmonization of locally meaningful data for use with global standards, facilitating secondary data use, interoperability, and research usability [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. Combining the advantages of both terminologies leverages their complementary strengths, enhancing communication accuracy, data quality, and adoption among clinicians, while providing semantic precision, computability, and cross-system interoperability [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Together, they facilitate the standardization of a clinical narrative into more structured data [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>].</p><p>Despite its advantages, implementing SNOMED CT presents challenges, particularly in non&#x2013;English-speaking contexts [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. Studies investigating the performance of SNOMED CT in multilingual contexts report 2 important indicators. Concept coverage refers to the proportion of source clinical ideas that can be represented by a concept, while term coverage refers to the proportion of source terms included in the SNOMED CT description, reflecting comprehensiveness of concept and the usability of descriptions, respectively [<xref ref-type="bibr" rid="ref18">18</xref>]. For example, European-based studies demonstrate varying degrees of success in translation and implementation efforts. A fully translated Swedish version of SNOMED CT achieved good concept coverage (87%) but lower term coverage (47%), reflecting limited alignment with real-world clinical language [<xref ref-type="bibr" rid="ref19">19</xref>]. In contrast, a German UIT without the use of SNOMED CT reached comparable term coverage (46%) despite the lack of codes in some key semantic areas, such as procedures, devices, or genes [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. These findings suggest that constructing or adopting language-specific UITs, linked to SNOMED CT&#x2019;s richer semantics and logical structure, is urgently needed and more effective than simply relying on direct translation [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p><p>Thailand became a member of SNOMED International in 2022, signaling a national commitment to adopt SNOMED CT as the reference terminology for addressing the country&#x2019;s interoperability and health care data quality challenges [<xref ref-type="bibr" rid="ref20">20</xref>]. Since joining, SNOMED CT codes have been incorporated into the national reporting and reimbursement datasets for diagnostic data. In clinical practice, a few health care institutes have begun integrating SNOMED CT&#x2019;s abundant descriptions into their diagnosis entry systems. This approach complements the previous process, in which physicians manually selected <italic>International Classification of Diseases (ICD)</italic> codes. However, the potential benefits of adopting SNOMED CT (eg, improved data granularity, semantic interoperability, and enhanced secondary data use) have yet to be fully realized across the country [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>]. A prior study in Thailand attempted to auto-map Thai discharge summary terms to <italic>ICD</italic> codes through SNOMED CT descriptions but excluded all non-English characters, limiting its ability to interpret locally used abbreviations and mixed-language expressions common in Thai clinical documentation [<xref ref-type="bibr" rid="ref21">21</xref>].</p><p>This study was conducted with the following 3 main objectives. First, to develop a Thai-language UIT derived from real-world clinical practice. Using a dynamic corpus of clinical texts, we apply a term collection methodology that integrates clinical expertise with natural language processing (NLP) techniques. The resulting UIT is expected to facilitate and support standardized data entry, enhance data quality, and improve user acceptance of SNOMED CT within Thailand&#x2019;s health care system.</p><p>Second, to evaluate the content coverage of SNOMED CT, defined as the proportion of clinical ideas in the Thai context that can be represented through international reference terminology.</p><p>Third, to perform mapping analysis of partially mapped and unmapped terms in order to identify potential areas where SNOMED CT or the Thai national extension may need further refinement to better represent Thai health care data.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Data Source</title><p>Data used for the development of the UIT were retrospectively retrieved from the chief complaint and present illness sections of electronic medical records (EMRs) at Chakri Naruebodindra Medical Institute, Ramathibodi Hospital, Mahidol University, covering the period from January 2019 to April 2023. Data were obtained from outpatient clinics in the family medicine (FM) and emergency departments, representing primary care settings. To enhance lexical diversity and coverage, additional data were obtained from the high-volume internal medicine (IM) department. Records lacking both the chief complaint and present illness sections were excluded from the study.</p></sec><sec id="s2-2"><title>UIT</title><p>In this study, UIT was defined as a set of clinically relevant terms used by clinicians to express their clinical ideas within the EMRs. These terms can be presented in either the semistructured or unstructured free-text entries. To qualify as UIT, the terms must contain adequate meaning, clarity, and clinical specificity to support accurate documentation and enable secondary uses, as assessed by medical doctors (eg, &#x201C;&#x0E40;&#x0E08;&#x0E47;&#x0E1A;&#x0E2B;&#x0E19;&#x0E49;&#x0E32;&#x0E2D;&#x0E01;&#x201D; [chest pain], &#x201C;&#x0E2D;&#x0E32;&#x0E40;&#x0E08;&#x0E35;&#x0E22;&#x0E19;&#x0E40;&#x0E1B;&#x0E47;&#x0E19;&#x0E40;&#x0E25;&#x0E37;&#x0E2D;&#x0E14;&#x201D; [vomiting blood], &#x201C;&#x0E42;&#x0E23;&#x0E04;&#x0E2B;&#x0E31;&#x0E27;&#x0E43;&#x0E08;&#x0E02;&#x0E32;&#x0E14;&#x0E40;&#x0E25;&#x0E37;&#x0E2D;&#x0E14;&#x201D; [ischemic heart disease]), whereas terms that were vague or noninformative (eg, &#x201C;1 &#x0E40;&#x0E14;&#x0E37;&#x0E2D;&#x0E19; pta&#x201D; [1 month prior to admission] or &#x201C;without evidence of&#x201D;) were not considered UIT.</p><p>The content of the UIT was harvested from the free-text documents produced during actual patient encounters. Clinician-entered free-text data (chief complaint and present illness) from the EMRs were preprocessed and transformed into clinical terms using NLP techniques, including cleaning, tokenization using our customized method, and N-gram generation. Term frequencies were then calculated, and terms meeting predefined threshold criteria were included in the UIT. The overall process is illustrated as follows (see <xref ref-type="fig" rid="figure1">Figure 1</xref>):</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Summary overview of the mapping process. Collecting data from all sources (left upper box). Turning free text to N-gram using a customized dictionary from 5 sources (middle upper box). Interface terms selected by term frequency and experts (right upper box). Indexing the interface terms (pink). Mapping to the semantically equivalent SNOMED CT concept (blue). OA: osteoarthritis; SNOMED CT: Systematized Nomenclature of Medicine Clinical Terms.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e80039_fig01.png"/></fig></sec><sec id="s2-3"><title>Text Preprocessing and Tokenization</title><p>Free-text data were preprocessed using the Python library for Thai NLP (ie, PyThaiNLP version 4.0.2) [<xref ref-type="bibr" rid="ref22">22</xref>], which normalized texts by applying case normalization, correcting misplaced Thai tone marks and vowels, removing punctuation, and eliminating duplicate entries (eg, repeated sentences from prior visits). This process removed approximately 11.4% of the total characters, improving data consistency and validity. The code used for implementing text preprocessing and tokenization is provided in the GitHub repository [<xref ref-type="bibr" rid="ref23">23</xref>].</p><p>Because Thai is a continuous-script language, which has no word and sentence boundaries (eg, &#x201C;&#x0E42;&#x0E23;&#x0E04;&#x0E2B;&#x0E31;&#x0E27;&#x0E43;&#x0E08;&#x0E02;&#x0E32;&#x0E14;&#x0E40;&#x0E25;&#x0E37;&#x0E2D;&#x0E14;&#x201D; [ischemic heart disease] consists of 4 lexical units: &#x201C;&#x0E42;&#x0E23;&#x0E04;&#x201D;(disease), &#x201C;&#x0E2B;&#x0E31;&#x0E27;&#x0E43;&#x0E08;&#x201D;(heart), &#x201C;&#x0E02;&#x0E32;&#x0E14;&#x201D;(deficiency), &#x201C;&#x0E40;&#x0E25;&#x0E37;&#x0E2D;&#x0E14;&#x201D;(blood)), standard Thai tokenizers trained on general Thai corpora perform poorly, particularly for medical text [<xref ref-type="bibr" rid="ref24">24</xref>]. We therefore used a customized maximum matching algorithm, a greedy approach that segments text by repeatedly choosing the longest possible valid term from a dictionary that matches the current position. The dictionary was expanded to include medical jargon, drug names, and local abbreviations to optimize tokenization accuracy for clinical narratives.</p><p>Formally, given an input string <inline-formula><mml:math id="ieqn1"><mml:mi>S</mml:mi></mml:math></inline-formula> and a dictionary <inline-formula><mml:math id="ieqn2"><mml:mi>D</mml:mi></mml:math></inline-formula>, at each position <inline-formula><mml:math id="ieqn3"><mml:mi>j</mml:mi></mml:math></inline-formula>, the algorithm identifies all candidate substrings of <inline-formula><mml:math id="ieqn4"><mml:mi>S</mml:mi></mml:math></inline-formula> beginning at <inline-formula><mml:math id="ieqn5"><mml:mi>j</mml:mi></mml:math></inline-formula> that appear in <inline-formula><mml:math id="ieqn6"><mml:mi>D</mml:mi></mml:math></inline-formula>, and selects the candidate with the maximum length. This substring is then appended to the output sequence of tokens, and the process continues from the next unmatched character until the entire string is segmented.</p><p>This left-to-right longest-match strategy enables more accurate tokenization of Thai medical terms.</p><p>The custom dictionary <inline-formula><mml:math id="ieqn7"><mml:mi>D</mml:mi></mml:math></inline-formula> integrated five sources (<xref ref-type="fig" rid="figure1">Figure 1</xref>) (1) English WordNet; (2) Thai WordNet; (3) SNOMED CT descriptions (providing English clinical terms and medical jargon); (4) Thai medicine terminology (the national medicine database contains drug ingredients, generic names, trade names, and herbal medicine); and (5) a manually curated abbreviation dictionary (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>), comprising abbreviations with &#x2265;2 capital letters occurring &#x003E;100 times in the dataset. These abbreviations were reviewed by physicians, validated using 5 random samples of medical records, and mapped to SNOMED CT. This custom dictionary was also used to spell-check before tokenization, ensuring that incorrect or nonstandard spellings were corrected before segmentation (<xref ref-type="fig" rid="figure1">Figure 1</xref>).</p><p>The N-grams of length 1&#x2010;5, representing continuous sequences of N tokens (or grams), were generated to identify meaningful patterns and construct candidate terms or phrases.</p><p>For example, words contained unigram to 5-grams were: &#x201C;&#x0E44;&#x0E02;&#x0E49;&#x201D; (fever) for unigram, &#x201C;&#x0E1B;&#x0E27;&#x0E14; &#x0E17;&#x0E49;&#x0E2D;&#x0E07;&#x201D; (abdominal pain) for bigram, &#x201C;&#x0E41;&#x0E1C;&#x0E25; &#x0E43;&#x0E19; &#x0E1B;&#x0E32;&#x0E01;&#x201D; (oral cavity wound) for trigram, &#x201C;&#x0E02;&#x0E32; &#x0E2A;&#x0E2D;&#x0E07; &#x0E02;&#x0E49;&#x0E32;&#x0E07; &#x0E1A;&#x0E27;&#x0E21;&#x201D; (both legs are swelled) for 4-gram, and &#x201C;&#x0E40;&#x0E25;&#x0E37;&#x0E2D;&#x0E14; &#x0E2D;&#x0E2D;&#x0E01; &#x0E1C;&#x0E34;&#x0E14;&#x0E1B;&#x0E01;&#x0E15;&#x0E34; &#x0E17;&#x0E32;&#x0E07; &#x0E0A;&#x0E48;&#x0E2D;&#x0E07;&#x0E04;&#x0E25;&#x0E2D;&#x0E14;&#x201D; (abnormal bleeding from vagina) for 5-gram. Syntactically irrelevant N-grams (ie, those containing &#x003E;50% stop words, punctuation, or numbers; or terms beginning or ending with stop words or prepositions) were excluded. The remaining N-grams were ranked by frequency and carefully reviewed by experienced clinicians. Clinically relevant terms were defined as those that conveyed sufficient meaning for documenting patient conditions.</p><p>In the first round, medical doctors reviewed intervals of ranked lists (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>), marked the terms that are clinically meaningful and appropriate for representing as structured data, and selected the terms by applying the following inclusion criteria: (1) frequency rank within the top 70th percentile or (2) absolute frequency &#x2265;300 occurrences, thresholds that reflected diminishing returns in identifying clinically relevant terms (<xref ref-type="fig" rid="figure2">Figure 2</xref>). After the second round, 2054 terms were selected from the pool of 10,260 candidate terms for inclusion in the interface terminology, representing commonly used clinical expressions across EMRs.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Numbers of included clinical terms per interval of rank-frequency categorized by the N of N-gram. Blue vertical lines indicate the cut point where term frequency was 300. Red vertical lines indicate the cut point where the percentile of rank-frequency reaches 70.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e80039_fig02.png"/></fig></sec><sec id="s2-4"><title>Mapping to SNOMED CT</title><p>Each UIT term was mapped to a semantically equivalent SNOMED CT concept using Snap2SNOMED, an open-source, publicly available mapping tool developed and maintained by SNOMED International. The tool provides key functionalities, including a built-in SNOMED CT browser, versioning, and automated lexical mapping (applicable to English-language terms only). Because automated mapping requires English input, 946 Thai terms were translated into English using Google Translate (Google LLC), and these translated terms were used as source terms for mapping. The automated mapping results were manually reviewed and validated by 2 clinical domain experts (NT and JS). To ensure semantic equivalency to the original Thai terms, 5 clinical usage contexts were supplied to the mappers for each term, selected at random from different patients. Manual mappings were guided by semantic equivalence criteria recommended in the Snap2SNOMED User Guide, prioritizing alignment for meaning, clinical intent, and hierarchical appropriateness. Disagreements between mappers were resolved through iterative discussion and consensus-based remapping.</p><p>Mapping results were classified into three categories, as illustrated in <xref ref-type="fig" rid="figure1">Figure 1</xref>: (1) fully mapped: SNOMED CT concepts that fully captured the semantics of the source term (eg, &#x201C;valvular heart disease&#x201D; mapped to &#x201C;Heart valve disorder [disorder]&#x201D;); (2) partially mapped: SNOMED CT concepts that were close but not fully semantically equivalent to the source term (eg, &#x201C;home SBP&#x201D; mapped to the narrower concept &#x201C;Average home systolic blood pressure [observable entity]&#x201D;); and (3) unmapped: source terms that lacked sufficient representation in existing SNOMED CT concepts.</p><p>A single source term could be potentially mapped to multiple SNOMED CT concepts (referred to as one-to-many mapping), resulting in more mapping pairs than source terms. This arose from one of two scenarios (1) homonyms, terms carried multiple distinct meanings, each represented by different SNOMED CT concepts following guidelines from SNOMED CT managing conventions and (2) ambiguous terms explicitly excluded from SNOMED CT due to insufficient contextual specificity (eg, &#x201C;fundus&#x201D; referring to either a hollow organ apex or the eye&#x2019;s interior surface). These ambiguous terms were conservatively classified as unmapped to preserve terminological clarity and precision.</p><p>Partially mapped pairs were further classified into broader, narrower, and inexact relationships to quantify mapping quality. The broader referred to the SNOMED CT concept, which encompasses the meaning of the source term. Narrower referred to when the SNOMED CT concept represented only part of the source term&#x2019;s meaning. In cases where semantic equivalence required postcoordination with multiple SNOMED CT concepts, we selected a single precoordinated concept in the same hierarchy as the narrower one. For example, &#x201C;nodule at right upper lung&#x201D; was mapped to the broader concept <italic>&#x201C;</italic>Nodule of lung (disorder)<italic>&#x201D;</italic> rather than combining a finding with &#x201C;Upper lobe of right lung (body structure).&#x201D; Inexact referred to mappings where the best available SNOMED CT concept differed in lexical and semantic characteristics but provided a clinically relevant approximation. For example, &#x201C;over-the-counter drug use&#x201D; was inexactly mapped to &#x201C;Patient on self-medication (finding).&#x201D;</p></sec><sec id="s2-5"><title>Mapping Analysis</title><p>Terms unable to be mapped by mappers were discussed and categorized into either partially mapped or unmapped terms, including ambiguous terms and terms for which no semantic equivalency was found in SNOMED CT. For the terms that can be represented using postcoordination of 2 or more concepts from the same hierarchy, for example, &#x201C;&#x0E40;&#x0E2B;&#x0E07;&#x0E37;&#x0E48;&#x0E2D;&#x0E41;&#x0E15;&#x0E01;&#x0E43;&#x0E08;&#x0E2A;&#x0E31;&#x0E48;&#x0E19;&#x201D; (sweating and palpitation), we decided to categorize them as unmapped terms for further analysis. Partially mapped and unmapped terms were analyzed to assess their potential for practical implementation within our research team. Specifically, the analysis examined whether these terms could be adequately represented through SNOMED CT postcoordination or should be proposed for inclusion in an updated national edition of SNOMED CT. This evaluation helped identify specific content areas where concept expansion would better align the terminology with local clinical practice and ensure comprehensive coverage in the national edition.</p></sec><sec id="s2-6"><title>Ethical Considerations</title><p>The study protocol was reviewed and approved by the Ramathibodi Human Research Ethics Committee (Approval number COA.MURA2023/469). The informed consent was waived due to the retrospective nature of the dataset and minimal risk to participants. All personally identifiable information (eg, names, surnames, dates of birth, addresses, hospital numbers, and visit dates) was removed from the dataset prior to analysis to ensure privacy and confidentiality.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Dataset Characteristics</title><p>A total of 1,88,468 documents were initially retrieved from the EMRs during the study period. After excluding records with missing data, 1,83,557 documents from 53,142 patients were included in the analysis to develop the interface terminology. Characteristics of the 53,142 patients are described in <xref ref-type="table" rid="table1">Table 1</xref>. IM patients were the oldest (mean 59.3, SD 16.9), followed by FM (mean 54.4, SD 15.2), and emergency department (mean 43.4, SD 28.0). The percentage of males was highest in emergency (44.3%), followed by IM (39.7%) and FM (36.94%).</p><p>At the document level, the IM department contributed the largest volume (1,18,382/1,83,557, 64.5%), followed by the emergency (34,829/1,83,557, 19.0%) and FM departments (30,346/1,83,557, 16.5%). The median number of documents per patient (IQR) was 2 (1-5) for IM, 1 (1-2) for emergency, and 1 (1-3) for FM (<xref ref-type="table" rid="table1">Table 1</xref>).</p><p>Text-level analysis of 1,83,557 documents yielded 14,946,559 total words. IM contributed the majority (10,471,768/14,946,559, 70.1%), followed by emergency (2,750,896/14,946,559, 18.4%) and FM (1,723,895/14,946,559, 11.5%). Median (IQR) words per document were 107 (62-175) for IM, 74 (44-125) for ER, and 60 (38-99) for FM. Thai words were varied by department. Emergency department documents had the highest proportion of Thai words (1,752,756/2,750,896, 63.7%), followed by FM (1,016,914/1,723,895, 59.0%), while IM contained the lowest proportion (4,154,255/10,471,768, 39.7%).</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Characteristics of data from the 3 outpatient departments.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristics</td><td align="left" valign="bottom">FM<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td><td align="left" valign="bottom">ER<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup></td><td align="left" valign="bottom">IM<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup></td><td align="left" valign="bottom">Total</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="5">Patient-level</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Number of patients (n)</td><td align="left" valign="top">12,128</td><td align="left" valign="top">22,878</td><td align="left" valign="top">29,985</td><td align="left" valign="top">53,142</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Age (years), mean (SD)</td><td align="left" valign="top">54.37 (15.21)</td><td align="left" valign="top">43.42 (27.97)</td><td align="left" valign="top">59.31 (16.91)</td><td align="left" valign="top">53.98 (15.42)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Male (sex), n (%)</td><td align="left" valign="top">4480 (36.94)</td><td align="left" valign="top">10,137 (44.31)</td><td align="left" valign="top">11,892 (39.66)</td><td align="left" valign="top">21,821 (41.06)</td></tr><tr><td align="left" valign="top" colspan="5">Document level</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Number of documents (n)</td><td align="left" valign="top">30,346</td><td align="left" valign="top">34,829</td><td align="left" valign="top">1,18,382</td><td align="left" valign="top">1,83,557</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Documents per patient, median (IQR)</td><td align="left" valign="top">1 (1-3)</td><td align="left" valign="top">1 (1-2)</td><td align="left" valign="top">2 (1-5)</td><td align="left" valign="top">2 (1-4)</td></tr><tr><td align="left" valign="top" colspan="5">Text-level</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unique words (n)</td><td align="left" valign="top">20,070</td><td align="left" valign="top">25,055</td><td align="left" valign="top">33,286</td><td align="left" valign="top">41,755</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Unique Thai words, n (%)</td><td align="left" valign="top">10,475 (52.19)</td><td align="left" valign="top">12,647 (50.78)</td><td align="left" valign="top">15,216 (45.71)</td><td align="left" valign="top">20,407 (48.87)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Total words (n)</td><td align="left" valign="top">1,723,895</td><td align="left" valign="top">2,750,896</td><td align="left" valign="top">10,471,768</td><td align="left" valign="top">14,946,559</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Total Thai words, n (%)</td><td align="left" valign="top">1,016,914 (58.99)</td><td align="left" valign="top">1,752,756 (63.72)</td><td align="left" valign="top">4,154,255 (39.67)</td><td align="left" valign="top">6,923,925 (46.32)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Word per document, median (IQR)</td><td align="left" valign="top">60 (38&#x2010;99)</td><td align="left" valign="top">74 (44&#x2010;125)</td><td align="left" valign="top">107 (62&#x2010;175)</td><td align="left" valign="top">81 (43&#x2010;141)</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>FM: family medicine.</p></fn><fn id="table1fn2"><p><sup>b</sup>ER: emergency room.</p></fn><fn id="table1fn3"><p><sup>c</sup>IM: internal medicine.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-2"><title>Coverage</title><p>A total of 2054 frequently used clinical source terms met the inclusion criteria and were integrated into the interface terminology. Of these, 2012 terms were successfully mapped to 2041 SNOMED CT concepts. Most terms were mapped one-to-one (1984 terms), while 28 terms were mapped to 57 multiconcepts through one-to-many mappings, yielding a total of 2083 entries while covering 1486 unique SNOMED CT codes. The final mappings are provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>. Mapping characteristics are as follows:</p><list list-type="bullet"><list-item><p>Language: English (1140 out of 2083 terms [54.73%]) and Thai (943 out of 2083 terms [45.27%]).</p></list-item><list-item><p>N-gram: unigrams (1098 terms), bigrams (741 terms), trigrams (189 terms), 4-grams (45 terms), and 5-grams (10 terms).</p></list-item><list-item><p>Equivalency: 1781 (85.50%) fully mapped terms, 123 (5.90%) mapped to broader concepts, 56 (2.69%) mapped to narrower concepts, and 81 (3.89%) inexactly mapped terms (<xref ref-type="table" rid="table2">Table 2</xref>). The remaining 42 terms (2.02%) could not be mapped due to culturally specific expressions or clinical concepts not yet represented in any SNOMED CT concept.</p></list-item><list-item><p>Overall, the concept coverage was 85.50%. Combining fully and partially mapped terms yielded an overall concept coverage of 97.98%.</p></list-item></list><p>Term coverage is defined as the percentage of local clinical terms that can be accurately mapped to an existing SNOMED CT description. Among 1140 English terms, 656 terms (31.49%) had direct lexical matches with English SNOMED CT descriptions, including simple variations of writing, for example, &#x201C;wound dressing&#x201D; versus &#x201C;Dressing wound.&#x201D; The remaining 484 English terms (23.24%) did not have an exact lexical match and were still mappable through contextual interpretation, such as local abbreviations (eg, &#x201C;f/u&#x201D; <italic>&#x2192;</italic> &#x201C;Follow-up visit [procedure]&#x201D;), or variation in writing style (eg, &#x201C;contact tb&#x201D; &#x2192; &#x201C;Exposure to tuberculosis [situation]&#x201D;). As expected, no Thai terms were considered direct lexical matches because SNOMED CT descriptions are not yet translated into Thai.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Concept coverage of Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) for Thai interface terminology.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Concept equivalency</td><td align="left" valign="bottom">English</td><td align="left" valign="bottom">Thai</td><td align="left" valign="bottom">Total</td></tr></thead><tbody><tr><td align="left" valign="top">Fully mapped, n (%)</td><td align="left" valign="top">973 (46.71)</td><td align="left" valign="top">808 (38.79)</td><td align="left" valign="top">1781 (85.50)</td></tr><tr><td align="left" valign="top">Partially mapped, n (%)</td><td align="left" valign="top">140 (6.72)</td><td align="left" valign="top">120 (5.75)</td><td align="left" valign="top">260 (14.48)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Broader</td><td align="left" valign="top">65 (3.12)</td><td align="left" valign="top">58 (2.78)</td><td align="left" valign="top">123 (5.90)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Narrower</td><td align="left" valign="top">38 (1.82)</td><td align="left" valign="top">18(0.86)</td><td align="left" valign="top">56 (2.69)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Inexact</td><td align="left" valign="top">37 (1.78)</td><td align="left" valign="top">44 (2.11)</td><td align="left" valign="top">81 (3.89)</td></tr><tr><td align="left" valign="top">Unmapped, n (%)</td><td align="left" valign="top">27 (1.30)</td><td align="left" valign="top">15 (0.72)</td><td align="left" valign="top">42 (2.02)</td></tr><tr><td align="left" valign="top">Total, n (%)</td><td align="left" valign="top">1140 (54.73)</td><td align="left" valign="top">943 (45.27)</td><td align="left" valign="top">2083 (100)</td></tr></tbody></table></table-wrap></sec><sec id="s3-3"><title>Mapping Analysis</title><p>Mapping analysis of the 260 partially mapped terms revealed linguistic and semantic challenges. All 123 broader (5.90%) and 56 narrower (2.69%) pairs comprised of concepts differed in granularity, where terms belonged to the same semantic domain, but they were at different levels of clinical detail or abstraction. On the other hand, inexact terms arose when clinical intention aligned, but lexical or cultural expression differed. For example, &#x201C;&#x0E19;&#x0E2D;&#x0E19;&#x0E2B;&#x0E19;&#x0E38;&#x0E19;&#x0E2B;&#x0E21;&#x0E2D;&#x0E19;&#x201D; (sleep with multiple pillows) was used to indicate the situation when a patient cannot sleep lying down due to shortness of breath; it was inexactly mapped to <italic>&#x201C;</italic>Orthopnea (finding)&#x201D; and &#x201C;&#x0E17;&#x0E32;&#x0E19;&#x0E22;&#x0E32;&#x0E2A;&#x0E21;&#x0E48;&#x0E33;&#x0E40;&#x0E2A;&#x0E21;&#x0E2D; (taking medicine regularly)&#x201D; and its variations were the patient-reported concept &#x201C;Drug compliance good (finding).&#x201D;</p><p>We also observed that culture and linguistic characteristics contributed to mismatches. Some Thai expressions convey complex clinical scenarios through idiomatic phrasing, complicating alignment with SNOMED CT. For example, &#x201C;over-the-counter drug use&#x201D; in the Thai context often implies access to medications that would require prescriptions in many other countries. After deliberation in our team, although this was mapped to &#x201C;Patient on self-medication (finding),&#x201D; this concept does not fully capture its implications within Thailand&#x2019;s health care system.</p><p>Forty-two unmapped terms (2.02%) were further categorized into 3 categories based on their characteristics (see <xref ref-type="table" rid="table3">Table 3</xref>).</p><p>Ambiguous terms (23/42, 54.76%) violated SNOMED CT naming conventions and required additional contexts for appropriate representation (eg, &#x201C;lobe,&#x201D; &#x201C;node,&#x201D; and &#x201C;septum&#x201D;).</p><p>Multiple clinical concepts (10/42, 23.81%) represented multiple distinct findings or events (eg, &#x201C;s1 s2&#x201D; [heart sounds], &#x201C;&#x0E40;&#x0E2B;&#x0E07;&#x0E37;&#x0E48;&#x0E2D;&#x0E41;&#x0E15;&#x0E01;&#x0E43;&#x0E08;&#x0E2A;&#x0E31;&#x0E48;&#x0E19;&#x201D; [sweating and palpitation], &#x201C;&#x0E25;&#x0E49;&#x0E21;&#x0E28;&#x0E35;&#x0E23;&#x0E29;&#x0E30;&#x0E01;&#x0E23;&#x0E30;&#x0E41;&#x0E17;&#x0E01;&#x201D; [fall and head collision]). Many terms reflect Thai-specific linguistic constructions and could potentially be addressed through postcoordination.</p><p>Clinically meaningful terms without SNOMED CT equivalents (9/42, 21.43%). Some terms were (locally) nationally specific (eg, &#x201C;&#x0E2B;&#x0E27;&#x0E34;&#x0E27;&#x201D; [fear of heights or a feeling of butterflies in the stomach]) while others were universally applicable but absent from SNOMED CT (eg, &#x201C;&#x0E22;&#x0E32;&#x0E25;&#x0E14;&#x0E44;&#x0E02;&#x0E49;&#x201D; [antipyretic medicine] and &#x201C;DOI&#x201D; [date of infection]). The terms were exhaustively searched using both lexical and graph properties of SNOMED CT through the use of SNOMED CT Expression Constraint Language.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Categories for unmapped concepts.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Characteristics</td><td align="left" valign="bottom">Ambiguous terms</td><td align="left" valign="bottom">Multiconcept terms</td><td align="left" valign="bottom">No concept terms</td></tr></thead><tbody><tr><td align="left" valign="top">Value, n (%)</td><td align="left" valign="top">23 (54.76)</td><td align="left" valign="top">10 (23.81)</td><td align="left" valign="top">9 (21.43)</td></tr><tr><td align="left" valign="top">Further intervention</td><td align="left" valign="top">Exclusion from terminology or addition of contextual information</td><td align="left" valign="top">Postcoordination or separation to multiple distinct concepts</td><td align="left" valign="top">Creation of new concept</td></tr><tr><td align="left" valign="top">Examples</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Lobe</p></list-item><list-item><p>Node</p></list-item><list-item><p>Septum</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>S1S2 (Heart sounds)</p></list-item><list-item><p>&#x0E40;&#x0E2B;&#x0E07;&#x0E37;&#x0E48;&#x0E2D;&#x0E41;&#x0E15;&#x0E01;&#x0E43;&#x0E08;&#x0E2A;&#x0E31;&#x0E48;&#x0E19; (sweating and palpitation)</p></list-item><list-item><p>&#x0E25;&#x0E49;&#x0E21;&#x0E28;&#x0E35;&#x0E23;&#x0E29;&#x0E30;&#x0E01;&#x0E23;&#x0E30;&#x0E41;&#x0E17;&#x0E01; (fall and head collision)</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>DOI (Date of Infection)</p></list-item><list-item><p>&#x0E22;&#x0E32;&#x0E25;&#x0E14;&#x0E44;&#x0E02;&#x0E49; (Antipyretic medicine)</p></list-item><list-item><p>&#x0E2B;&#x0E27;&#x0E34;&#x0E27; (fear of heights or a feeling of butterflies in the stomach)</p></list-item></list></td></tr></tbody></table></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>This study developed a multilingual UIT derived from real-world clinical documents across the FM, emergency, and IM departments and evaluated its alignment with SNOMED CT. The resulting UIT reflects a nearly balanced linguistic composition (54.49% English terms and 45.51% Thai terms). Consistent with the bilingual nature of Thai medical records. SNOMED CT demonstrated strong concept coverage with 85.50% full and 97.98% full plus partial coverage, confirming its suitability as a reference terminology even in the setting where nearly half of the source terms are non-English. However, term coverage remained modest (31.49%) because SNOMED CT descriptions have not yet been translated into Thai, making exact lexical matches possible only for English-language terms.</p><p>The source data also showed different patterns in clinical documentation practices. For instance, IM generated the highest volume of text but had the lowest proportion of Thai words, consistent with its more technical and specialty-oriented clinical activities. In contrast, emergency and FM documents contained more Thai narrative language, which may reflect more direct patient-provider interaction, brief encounters, and patient-reported symptoms. These differences emphasize the need for UITs that can accommodate both biomedical language and colloquial Thai expressions.</p><p>We also found that only a small proportion of terms remained unmapped (2.02%), underscoring that the majority of local expressions can be integrated into SNOMED CT without major structural changes. These relatively small, unmapped concepts may help identify where efforts should be strategically concentrated at the national level. Moreover, the moderate-term coverage (31.49%), driven entirely by English lexical matches, reinforces the need for localized terminology tools and translation strategies if Thailand aims to scale SNOMED CT adoption nationwide.</p></sec><sec id="s4-2"><title>Comparison With Previous Work</title><p>Despite differences in term extraction methods, particularly our focus on commonly used clinical terms and the use of a more recent SNOMED CT release, our findings generally align with previous evaluations of SNOMED CT concept coverage. Prior studies have reported a strong preference for high coverage in the English-language international edition (86% fully mapped and 92% partially mapped) and similar strong performance in the fully translated Swedish edition when applied to Swedish clinical datasets (87% fully mapped and 92% partially mapped) [<xref ref-type="bibr" rid="ref19">19</xref>]. In comparison, our findings showed 85.50% full and 97.98% full plus partial coverage, demonstrating that SNOMED CT remains robust even in bilingual and partially non-English documentation environments.</p><p>Comparable evidence has also been observed in low- and middle-income country settings. For example, an evaluation from Argentina reported 83% coverage based on user feedback during real-world implementation [<xref ref-type="bibr" rid="ref12">12</xref>]. Other specific domains targeting nationwide data collection and surveillance objectives have very high coverage, 99% precoordinated and 100% postcoordinated concept coverage for AIDS-defining illnesses in Kenya [<xref ref-type="bibr" rid="ref25">25</xref>], and high correspondence for tuberculosis-related terminology, although the latter did not include a formal concept coverage analysis [<xref ref-type="bibr" rid="ref14">14</xref>].</p><p>In Thailand, a prior study mapped Thai discharge summary notes to SNOMED CT but removed non-English content and did not report concept coverage [<xref ref-type="bibr" rid="ref21">21</xref>]. Our study extends this work by incorporating both English and Thai clinical terms from 3 departments, performing concept coverage, term coverage, and mapping analysis, and examining implications for national UIT development. This provides a more comprehensive and representative assessment of SNOMED CT&#x2019;s applicability for Thai primary care and hospital settings.</p><p>Partially mapped terms frequently reflect homonyms (eg, &#x201C;&#x0E21;&#x0E27;&#x0E19;&#x201D; meaning both abdominal colic and a cigarette unit), mismatches in granularity (eg, &#x201C;hypoglycemic symptom&#x201D; mapped to hypoglycemia [disorder]), or culturally shaped usage patterns. These challenges are consistent with those reported in other multilingual SNOMED CT mapping studies [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref26">26</xref>]. In the Thai language, many biomedical concepts and terms are not readily expressed in Thai. Unlike languages that share linguistic roots (eg, English, French, and Swedish), Thai lacks direct lexical equivalents for some medical terms, creating communication barriers between clinicians, patients, and even health care providers. To ensure mutual understanding, clinicians need to phrase simple questions that patients can comprehend, allowing information to be collected accurately. For example, &#x201C;compliance&#x201D; is simply conveyed as &#x201C;taking medicine regularly&#x201D; or &#x201C;never miss a dose,&#x201D; which is reflected in how these terms appeared in the EMRs. This observation has also been reported in other languages, not from the same roots as the English language [<xref ref-type="bibr" rid="ref27">27</xref>].</p><p>Term coverage in our dataset was modest (31.49%), driven entirely by English lexical matches. The observed term coverage is comparable with countries whose SNOMED CT editions are only partially translated, for example, Dutch (35%) and French (39%) [<xref ref-type="bibr" rid="ref19">19</xref>]. A considerable proportion of our Thai clinical terms were synonymous with globally common English medical jargon, reflecting Thailand&#x2019;s long-standing integration of English terminology in medical education and clinical communication. As shown in <xref ref-type="table" rid="table1">Table 1</xref>, Thai language use was more prevalent in primary care departments (FM and emergency), while IM documents contained more specialized English terminology, consistent with previous reports [<xref ref-type="bibr" rid="ref28">28</xref>].</p></sec><sec id="s4-3"><title>Challenges in Expressing Clinical Concepts in the Thai Context</title><p>Our mapping analysis of partially mapped terms highlighted several challenges in representing Thai clinical concepts within SNOMED CT. Many partially mapped terms require determining whether they should (1) be represented through postcoordination with existing SNOMED CT concepts (thereby supporting international interoperability) or (2) be introduced as new concepts in the Thai national extension to preserve locally specific meaning.</p><p>Postcoordination can be beneficial for international interoperability but may lose nuanced local semantics. Conversely, creating new concepts preserves the locally used expression but introduces a long-term maintenance burden and requires clear criteria for inclusion. No standardized national guidelines currently exist; decisions must consider clinical relevance, documentation frequency, clinical importance, and anticipated use cases within Thailand&#x2019;s EMR ecosystem. A representative example from our study is &#x201C;over-the-counter drug use,&#x201D; which frequently appeared in our dataset and reflects a long-standing public health challenge in unsupervised medication access in Thailand [<xref ref-type="bibr" rid="ref29">29</xref>], which contributes to national issues such as antimicrobial resistance and drug misuse [<xref ref-type="bibr" rid="ref30">30</xref>]. While &#x201C;Patient on self-medication (finding)&#x201D; is the most relevant concept in SNOMED CT, it does not fully represent Thailand&#x2019;s regulatory distinctions and safety concerns. If more granular differentiation is required in Thailand for surveillance or policy purposes, a new child concept under <italic>&#x201C;</italic>Patient on self-medication (finding)<italic>&#x201D;</italic> may be warranted.</p><p>The analysis of unmapped terms also highlighted the role of language-specific and culturally specific expressions that are not directly translatable into English (see <xref ref-type="table" rid="table3">Table 3</xref>). In our data, 20.93% of unmapped terms reflected culturally unique, ambiguous, or context-dependent meanings. These findings suggested three key strategies for terminology management and strengthening (1) exclude ambiguous terms or add contextual information to the context-dependent terms. For example, the Thai term &#x201C;&#x0E2B;&#x0E27;&#x0E34;&#x0E27;&#x201D; has multiple meanings (fear of heights or a feeling of butterflies in the stomach). Instead of mapping it directly, adding the more specific term &#x201C;&#x0E43;&#x0E08;&#x0E2B;&#x0E27;&#x0E34;&#x0E27;&#x201D; (giddiness in the heart) mapped to &#x201C;Palpitations (finding)&#x201D; can ensure clarity and avoid misclassification. (2) Use postcoordination for multiconcept or idiomatic expressions. This pattern was also found in the English context, for example, the concept &#x201C;Nausea and vomiting (finding),&#x201D; which exists as a precoordinated concept within the international edition of SNOMED CT. However, since separated distinct concepts are presented, we suggest mapping to separate entities to preserve legacy information and also interoperability with the international context. (3) Recommend new concepts for national extension or international inclusion for globally relevant but unsupported terms. This should be done with a well-established concept with clear practical implications. One example we found was a local abbreviation, &#x201C;DOI (Date of Infection),&#x201D; which we believe has seen an increase in occurrences during the pandemic, particularly in cases where infectious history has been thoroughly collected. Additionally, some of these represent global clinically relevant concepts insufficiently addressed by SNOMED CT, indicating areas for future expansion [<xref ref-type="bibr" rid="ref7">7</xref>].</p><p>Overall, these challenges highlight the need for national governance structures, clearly defined criteria for new concept creation, and a systematic strategy for translation and localization to ensure accurate, consistent, and interoperable representation of Thai clinical terminology. Regional guidance from the Asia eHealth Information Network (AeHIN) similarly emphasizes that successful and sustainable interoperability depends not only on the technical standards but also on governance, architecture, workforce capacity, and institutional processes [<xref ref-type="bibr" rid="ref31">31</xref>]. Centralized governance through a national health data dictionary and terminology services, as described in many interoperability architectures, like Open Health Information Exchange (OpenHIE; Linux Foundation Public Health), can standardize terminological assets and reduce fragmentation across implementation sites [<xref ref-type="bibr" rid="ref32">32</xref>]. Such services can support the controlled use of postcoordination and governed concept creation and enable local expressiveness while preserving semantic consistency and international interoperability. Importantly, these functions are best managed at the terminology service level rather than within individual EMR implementations, thereby reducing duplication and implementation burden. In addition, mappings between shared UITs and reference terminologies or classification systems (eg, the <italic>ICD</italic> family) should be centrally maintained, versioned, and routinely updated. For example, the OpenMRS ecosystem also adopts the similar implementation pattern, where many deployments rely on the CIEL interface terminology, centrally managed and distributed via Open Concept Lab, supporting reuse and reducing divergence across implementations [<xref ref-type="bibr" rid="ref13">13</xref>].</p></sec><sec id="s4-4"><title>Strengths and Limitations</title><p>To our knowledge, this is the first study in Thailand&#x2014;and among the few resource-limited countries&#x2014;to develop a UIT and evaluate both concept- and term-level coverage of SNOMED CT in a real-world clinical setting. A key strength of this study lies in its data source, free-text entries from actual clinical encounters, which ensures that the extracted terms are grounded in real-world usage. Moreover, the terminology development process integrated clinical expertise with NLP techniques in a resource-limited setting, offering valuable insights for similar environments. The final UIT is composed of the commonly used clinical term. Although it is small in numbers, we believe this terminology to be generally applicable for use within Thailand. Although SNOMED CT concept coverage has been examined in a few resource-limited country settings, evidence remains scarce. This study extends the discussion to Southeast Asia by evaluating Thai-language primary care data, constructing a UIT mapped to SNOMED CT, and reporting concept coverage.</p><p>Several limitations should be acknowledged. First, source data were collected from a single hospital, which may limit the generalizability of the developed UIT. Consequently, the developed UIT may not fully capture the diversity of expression terms used across Thailand&#x2019;s broader health care system, particularly in regions where distinct dialects or documentation styles prevail. Nevertheless, this study achieved its goal of constructing a realistic UIT to inform national implementation strategies and evaluate the feasibility of adopting SNOMED CT as a national standard. As new clinical terms and concepts emerge, the UTI can be continuously expanded through routine monitoring, domain-expert review, and integration of automated extraction tools to ensure incremental improvement over time. Second, although the mapping and term extraction processes were performed by clinically trained physicians, the subjective nature of manual mapping introduces the potential for interpretation bias or human error. An interannotator agreement score was not assessed due to constraints in available personnel and resources; consequently, only one mapper and one reviewer contributed to the final mapping. Third, the coverage results may be overestimated compared to those reported in previous studies because our term list was developed from commonly used clinical expressions and mapped to a more recent SNOMED CT release. At the same time, the mapping tool Snap2SNOMED does not support postcoordination at the time of this writing, which may lead to a potential underestimation of full SNOMED CT content coverage. However, since postcoordination has not been generally performed in previous studies, the results remain broadly comparable with existing evidence [<xref ref-type="bibr" rid="ref19">19</xref>].</p></sec><sec id="s4-5"><title>Recommendation for Future Research</title><p>Future research should expand the evaluation of concept and term coverage across hospitals of varying sizes and settings, including northern, northeastern, and southern regions of Thailand, where specific dialects may influence clinical documentation practices. Extending these methods beyond a single institution will help determine the generalizability of the UIT and support efforts toward national standardization.</p><p>Automated methods should also be explored. Advanced NLP techniques and large language models may substantially improve the efficiency and accuracy of term extraction, disambiguation, and SNOMED CT mapping, particularly as our team is already beginning to implement these tools in parallel methodological work. Additional studies should examine how postcoordination can be operationalized in real-world EMRs, with the goal of identifying best practices that maintain semantic precision without burdening clinicians during documentation.</p><p>Finally, future research should include more diverse document types (eg, operative notes, procedure reports, and specialty consults) and a broader population. Doing such improves characterization of locally used clinical concepts, strengthens coverage estimates, and supports the development of a more comprehensive national UIT that accurately reflects the linguistic and clinical diversity of Thailand&#x2019;s health care system.</p></sec><sec id="s4-6"><title>Conclusions</title><p>In conclusion, SNOMED CT represents most common clinical concepts but lacks sufficient local language coverage. With the interpretation of local clinical terms, a Thai UIT mapped to SNOMED CT can serve as a comprehensive standard for clinical documentation. This hybrid approach can enhance data quality, promote interoperability, and facilitate better use of health care data, contributing to improved patient care and creating opportunities for international collaboration.</p></sec></sec></body><back><ack><p>This manuscript is a part of the thesis of Nat Tangchitnob, MD, within the international Ph.D. program in Data Science for Healthcare and Clinical Informatics, conducted at the Department of Clinical Epidemiology and Biostatistics, Faculty of Medicine, Ramathibodi Hospital, Mahidol University, Bangkok, Thailand.</p></ack><notes><sec><title>Funding</title><p>The authors received no specific funding for this work.</p></sec><sec><title>Data Availability</title><p>All terminology data generated or analyzed during this study are included in this published article and its supplementary information files. The developed codes for this study are available at GitHub [<xref ref-type="bibr" rid="ref23">23</xref>].</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: NT, WP, BK, OP, AT</p><p>Data curation: SP, PA, KS</p><p>Formal analysis: NT, WP, OP, AT</p><p>Funding acquisition: OP, AT</p><p>Investigation: NT, JS</p><p>Methodology: NT, WP, BK, GJM, JA, AT</p><p>Project administration: WP, OP</p><p>Resources: OP</p><p>Software: NT, WP</p><p>Supervision: WP, BK, OP, AT</p><p>Validation: WP, BK, AT</p><p>Visualization: NT</p><p>Writing &#x2013; original draft: NT, WP, OP, JS</p><p>Writing &#x2013; review &#x0026; editing: NT, BK, SP, PA, KS, GJM, JA, AT</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AeHIN</term><def><p>Asia eHealth Information Network</p></def></def-item><def-item><term id="abb2">CIEL</term><def><p>Columbia International eHealth Laboratory</p></def></def-item><def-item><term id="abb3">EMR</term><def><p>electronic medical record</p></def></def-item><def-item><term id="abb4">FM</term><def><p>family medicine</p></def></def-item><def-item><term id="abb5"><italic>ICD</italic></term><def><p><italic>International Classification of Diseases</italic></p></def></def-item><def-item><term id="abb6">IM</term><def><p>internal medicine</p></def></def-item><def-item><term id="abb7">NLP</term><def><p>natural language processing</p></def></def-item><def-item><term id="abb8">OpenHIE</term><def><p>Open Health Information Exchange</p></def></def-item><def-item><term id="abb9">OpenMRS</term><def><p>Open Medical Record System</p></def></def-item><def-item><term id="abb10">SNOMED CT</term><def><p>Systematized Nomenclature of Medicine Clinical Terms</p></def></def-item><def-item><term id="abb11">UIT</term><def><p>user interface terminology</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lewis</surname><given-names>AE</given-names> </name><name name-style="western"><surname>Weiskopf</surname><given-names>N</given-names> </name><name name-style="western"><surname>Abrams</surname><given-names>ZB</given-names> </name><etal/></person-group><article-title>Electronic health record data quality assessment and tools: a systematic review</article-title><source>J Am Med Inform Assoc</source><year>2023</year><month>09</month><day>25</day><volume>30</volume><issue>10</issue><fpage>1730</fpage><lpage>1740</lpage><pub-id pub-id-type="doi">10.1093/jamia/ocad120</pub-id><pub-id pub-id-type="medline">37390812</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>Linder</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Schnipper</surname><given-names>JL</given-names> </name><name name-style="western"><surname>Middleton</surname><given-names>B</given-names> </name></person-group><article-title>Method of electronic health record documentation and quality of primary care</article-title><source>J Am Med Inform Assoc</source><year>2012</year><volume>19</volume><issue>6</issue><fpage>1019</fpage><lpage>1024</lpage><pub-id pub-id-type="doi">10.1136/amiajnl-2011-000788</pub-id><pub-id pub-id-type="medline">22610494</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>Liu</surname><given-names>F</given-names> </name><name name-style="western"><surname>Panagiotakos</surname><given-names>D</given-names> </name></person-group><article-title>Real-world data: a brief review of the methods, applications, challenges and opportunities</article-title><source>BMC Med Res Methodol</source><year>2022</year><month>11</month><day>5</day><volume>22</volume><issue>1</issue><fpage>287</fpage><pub-id pub-id-type="doi">10.1186/s12874-022-01768-6</pub-id><pub-id pub-id-type="medline">36335315</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>Botsis</surname><given-names>T</given-names> </name><name name-style="western"><surname>Hartvigsen</surname><given-names>G</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>F</given-names> </name><name name-style="western"><surname>Weng</surname><given-names>C</given-names> </name></person-group><article-title>Secondary use of EHR: data quality issues and informatics opportunities</article-title><source>Summit Transl Bioinform</source><year>2010</year><month>03</month><day>1</day><volume>2010</volume><issue>1-5</issue><fpage>1</fpage><lpage>5</lpage><pub-id pub-id-type="medline">21347133</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>Bowman</surname><given-names>S</given-names> </name></person-group><article-title>Impact of electronic health record systems on information integrity: quality and safety implications</article-title><source>Perspect Health Inf Manag</source><year>2013</year><volume>10</volume><issue>Fall</issue><fpage>1c</fpage><pub-id pub-id-type="medline">24159271</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>Cimino</surname><given-names>JJ</given-names> </name></person-group><article-title>Desiderata for controlled medical vocabularies in the twenty-first century</article-title><source>Methods Inf Med</source><year>1998</year><month>11</month><volume>37</volume><issue>4-5</issue><fpage>394</fpage><lpage>403</lpage><pub-id pub-id-type="doi">10.1055/s-0038-1634558</pub-id><pub-id pub-id-type="medline">9865037</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>Millar</surname><given-names>J</given-names> </name></person-group><article-title>The need for a global language - SNOMED CT introduction</article-title><source>Stud Health Technol Inform</source><year>2016</year><volume>225</volume><issue>683-5</issue><fpage>683</fpage><lpage>685</lpage><pub-id pub-id-type="doi">10.3233/978-1-61499-658-3-683</pub-id><pub-id pub-id-type="medline">27332304</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>Rector</surname><given-names>A</given-names> </name><name name-style="western"><surname>Schulz</surname><given-names>S</given-names> </name><name name-style="western"><surname>Rodrigues</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Chute</surname><given-names>CG</given-names> </name><name name-style="western"><surname>Solbrig</surname><given-names>H</given-names> </name></person-group><article-title>On beyond Gruber: &#x201C;Ontologies&#x201D; in today&#x2019;s biomedical information systems and the limits of OWL</article-title><source>J Biomed Inform</source><year>2019</year><volume>100S</volume><fpage>100002</fpage><pub-id pub-id-type="doi">10.1016/j.yjbinx.2019.100002</pub-id><pub-id pub-id-type="medline">34384571</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>Thiel</surname><given-names>R</given-names> </name><name name-style="western"><surname>Birov</surname><given-names>S</given-names> </name><name name-style="western"><surname>Piesche</surname><given-names>K</given-names> </name><etal/></person-group><article-title>The costs and benefits of SNOMED CT implementation: an economic assessment model</article-title><source>Stud Health Technol Inform</source><year>2016</year><volume>228</volume><issue>441-5</issue><fpage>441</fpage><lpage>445</lpage><pub-id pub-id-type="doi">10.3233/978-1-61499-678-1-441</pub-id><pub-id pub-id-type="medline">27577421</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>Vuokko</surname><given-names>R</given-names> </name><name name-style="western"><surname>Vakkuri</surname><given-names>A</given-names> </name><name name-style="western"><surname>Palojoki</surname><given-names>S</given-names> </name></person-group><article-title>Systematized Nomenclature of Medicine-Clinical Terminology (SNOMED CT) clinical use cases in the context of electronic health record systems: systematic literature review</article-title><source>JMIR Med Inform</source><year>2023</year><month>02</month><day>6</day><volume>11</volume><fpage>e43750</fpage><pub-id pub-id-type="doi">10.2196/43750</pub-id><pub-id pub-id-type="medline">36745498</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>Rosenbloom</surname><given-names>ST</given-names> </name><name name-style="western"><surname>Miller</surname><given-names>RA</given-names> </name><name name-style="western"><surname>Johnson</surname><given-names>KB</given-names> </name><name name-style="western"><surname>Elkin</surname><given-names>PL</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>SH</given-names> </name></person-group><article-title>Interface terminologies: facilitating direct entry of clinical data into electronic health record systems</article-title><source>J Am Med Inform Assoc</source><year>2006</year><volume>13</volume><issue>3</issue><fpage>277</fpage><lpage>288</lpage><pub-id pub-id-type="doi">10.1197/jamia.M1957</pub-id><pub-id pub-id-type="medline">16501181</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>Osornio</surname><given-names>AL</given-names> </name><name name-style="western"><surname>Luna</surname><given-names>D</given-names> </name><name name-style="western"><surname>Gambarte</surname><given-names>ML</given-names> </name><name name-style="western"><surname>Gomez</surname><given-names>A</given-names> </name><name name-style="western"><surname>Reynoso</surname><given-names>G</given-names> </name><name name-style="western"><surname>de Quir&#x00F3;s</surname><given-names>FGB</given-names> </name></person-group><article-title>Creation of a local interface terminology to SNOMED CT</article-title><source>Stud Health Technol Inform</source><year>2007</year><volume>129</volume><issue>Pt 1</issue><fpage>765</fpage><lpage>769</lpage><pub-id pub-id-type="medline">17911820</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>Kanter</surname><given-names>AS</given-names> </name><name name-style="western"><surname>Borland</surname><given-names>R</given-names> </name><name name-style="western"><surname>Barasa</surname><given-names>M</given-names> </name><etal/></person-group><article-title>The importance of using open source technologies and common standards for interoperability within eHealth: perspectives from the millennium villages project</article-title><source>Adv Health Care Manag</source><year>2012</year><volume>12</volume><issue>189-204</issue><fpage>189</fpage><lpage>204</lpage><pub-id pub-id-type="doi">10.1108/s1474-8231(2012)0000012013</pub-id><pub-id pub-id-type="medline">22894051</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>Halland</surname><given-names>K</given-names> </name><name name-style="western"><surname>Britz</surname><given-names>K</given-names> </name><name name-style="western"><surname>Gerber</surname><given-names>A</given-names> </name></person-group><article-title>Investigations into the use of Snomed CT to enhance an OpenMRS health information system</article-title><source>SACJ</source><year>2011</year><volume>47</volume><issue>1</issue><fpage>33</fpage><lpage>45</lpage><pub-id pub-id-type="doi">10.18489/sacj.v47i0.14</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>Schulz</surname><given-names>S</given-names> </name><name name-style="western"><surname>Rodrigues</surname><given-names>JM</given-names> </name><name name-style="western"><surname>Rector</surname><given-names>A</given-names> </name><name name-style="western"><surname>Chute</surname><given-names>CG</given-names> </name></person-group><article-title>Interface terminologies, reference terminologies and aggregation terminologies: a strategy for better integration</article-title><source>Stud Health Technol Inform</source><year>2017</year><volume>245</volume><issue>940-4</issue><fpage>940</fpage><lpage>944</lpage><pub-id pub-id-type="doi">10.3233/978-1-61499-830-3-940</pub-id><pub-id pub-id-type="medline">29295238</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>Hashemian Nik</surname><given-names>D</given-names> </name><name name-style="western"><surname>Kas&#x00E1;&#x010D;</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Goda</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Semlitsch</surname><given-names>A</given-names> </name><name name-style="western"><surname>Schulz</surname><given-names>S</given-names> </name></person-group><article-title>Building an experimental German user interface terminology linked to SNOMED CT</article-title><source>Stud Health Technol Inform</source><year>2019</year><month>08</month><day>21</day><volume>264</volume><issue>153-7</issue><fpage>153</fpage><lpage>157</lpage><pub-id pub-id-type="doi">10.3233/SHTI190202</pub-id><pub-id pub-id-type="medline">31437904</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>Park</surname><given-names>HA</given-names> </name><name name-style="western"><surname>Yu</surname><given-names>SJ</given-names> </name><name name-style="western"><surname>Jung</surname><given-names>H</given-names> </name></person-group><article-title>Strategies for adopting and implementing SNOMED CT in Korea</article-title><source>Healthc Inform Res</source><year>2021</year><month>01</month><volume>27</volume><issue>1</issue><fpage>3</fpage><lpage>10</lpage><pub-id pub-id-type="doi">10.4258/hir.2021.27.1.3</pub-id><pub-id pub-id-type="medline">33611871</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>Rosenbloom</surname><given-names>ST</given-names> </name><name name-style="western"><surname>Miller</surname><given-names>RA</given-names> </name><name name-style="western"><surname>Johnson</surname><given-names>KB</given-names> </name><name name-style="western"><surname>Elkin</surname><given-names>PL</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>SH</given-names> </name></person-group><article-title>A model for evaluating interface terminologies</article-title><source>J Am Med Inform Assoc</source><year>2008</year><volume>15</volume><issue>1</issue><fpage>65</fpage><lpage>76</lpage><pub-id pub-id-type="doi">10.1197/jamia.M2506</pub-id><pub-id pub-id-type="medline">17947616</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>Mi&#x00F1;arro-Gim&#x00E9;nez</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Cornet</surname><given-names>R</given-names> </name><name name-style="western"><surname>Jaulent</surname><given-names>MC</given-names> </name><etal/></person-group><article-title>Quantitative analysis of manual annotation of clinical text samples</article-title><source>Int J Med Inform</source><year>2019</year><month>03</month><volume>123</volume><issue>37-48</issue><fpage>37</fpage><lpage>48</lpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2018.12.011</pub-id><pub-id pub-id-type="medline">30654902</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="web"><article-title>Thailand</article-title><source>SNOMED International</source><year>2025</year><month>10</month><day>22</day><access-date>2026-02-27</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.snomed.org/members/thailand">https://www.snomed.org/members/thailand</ext-link></comment></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>Isaradech</surname><given-names>N</given-names> </name><name name-style="western"><surname>Khumrin</surname><given-names>P</given-names> </name></person-group><article-title>Auto-mapping clinical documents to ICD-10 using SNOMED-CT</article-title><source>AMIA Jt Summits Transl Sci Proc</source><year>2021</year><volume>2021</volume><fpage>296</fpage><lpage>304</lpage><pub-id pub-id-type="medline">34457144</pub-id></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Phatthiyaphaibun</surname><given-names>W</given-names> </name><name name-style="western"><surname>Chaovavanich</surname><given-names>K</given-names> </name><name name-style="western"><surname>Polpanumas</surname><given-names>C</given-names> </name><etal/></person-group><article-title>PyThaiNLP: thai natural language processing in python</article-title><access-date>2026-02-05</access-date><conf-name>Proceedings of the 3rd Workshop for Natural Language Processing Open Source Software (NLP-OSS 2023)</conf-name><conf-date>Jul 13, 2023</conf-date><comment><ext-link ext-link-type="uri" xlink:href="https://aclanthology.org/2023.nlposs-1">https://aclanthology.org/2023.nlposs-1</ext-link></comment><pub-id pub-id-type="doi">10.18653/v1/2023.nlposs-1.4</pub-id></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="web"><article-title>Chirurgo/terminology2snomed [internet]</article-title><source>GitHub</source><access-date>2026-02-05</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://github.com/Chirurgo/terminology2snomed">https://github.com/Chirurgo/terminology2snomed</ext-link></comment></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>Damrongkamoltip</surname><given-names>K</given-names> </name><name name-style="western"><surname>Ruenlek</surname><given-names>K</given-names> </name><name name-style="western"><surname>Limprasert</surname><given-names>W</given-names> </name><name name-style="western"><surname>Boonkwan</surname><given-names>P</given-names> </name></person-group><article-title>Comparing a Thai words segmentation methods in the LST20 dataset</article-title><source>J Comput Creat Technol</source><year>2024</year><volume>2</volume><issue>2</issue><fpage>61</fpage><lpage>70</lpage><pub-id pub-id-type="doi">10.14456/jcct.2024.7</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>Oluoch</surname><given-names>T</given-names> </name><name name-style="western"><surname>de Keizer</surname><given-names>N</given-names> </name><name name-style="western"><surname>Langat</surname><given-names>P</given-names> </name><etal/></person-group><article-title>A structured approach to recording AIDS-defining illnesses in Kenya: a SNOMED CT based solution</article-title><source>J Biomed Inform</source><year>2015</year><month>08</month><volume>56</volume><issue>387-94</issue><fpage>387</fpage><lpage>394</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2015.07.009</pub-id><pub-id pub-id-type="medline">26184057</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>Mi&#x00F1;arro-Gim&#x00E9;nez</surname><given-names>JA</given-names> </name><name name-style="western"><surname>Mart&#x00ED;nez-Costa</surname><given-names>C</given-names> </name><name name-style="western"><surname>Karlsson</surname><given-names>D</given-names> </name><name name-style="western"><surname>Schulz</surname><given-names>S</given-names> </name><name name-style="western"><surname>G&#x00F8;eg</surname><given-names>KR</given-names> </name></person-group><article-title>Qualitative analysis of manual annotations of clinical text with SNOMED CT</article-title><source>PLoS ONE</source><year>2018</year><volume>13</volume><issue>12</issue><fpage>e0209547</fpage><pub-id pub-id-type="doi">10.1371/journal.pone.0209547</pub-id><pub-id pub-id-type="medline">30589855</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>Perez-de-Vi&#x00F1;aspre</surname><given-names>O</given-names> </name><name name-style="western"><surname>Oronoz</surname><given-names>M</given-names> </name></person-group><article-title>SNOMED CT in a language isolate: an algorithm for a semiautomatic translation</article-title><source>BMC Med Inform Decis Mak</source><year>2015</year><volume>15 Suppl 2</volume><issue>Suppl 2</issue><fpage>S5</fpage><pub-id pub-id-type="doi">10.1186/1472-6947-15-S2-S5</pub-id><pub-id pub-id-type="medline">26100112</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>Yusuff</surname><given-names>KB</given-names> </name><name name-style="western"><surname>Tayo</surname><given-names>F</given-names> </name></person-group><article-title>Does a physician&#x2019;s specialty influence the recording of medication history in patients&#x2019; case notes?</article-title><source>Br J Clin Pharmacol</source><year>2008</year><month>08</month><volume>66</volume><issue>2</issue><fpage>308</fpage><lpage>312</lpage><pub-id pub-id-type="doi">10.1111/j.1365-2125.2008.03202.x</pub-id><pub-id pub-id-type="medline">18537964</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>Cooper</surname><given-names>RJ</given-names> </name></person-group><article-title>Over-the-counter medicine abuse - a review of the literature</article-title><source>J Subst Use</source><year>2013</year><month>04</month><volume>18</volume><issue>2</issue><fpage>82</fpage><lpage>107</lpage><pub-id pub-id-type="doi">10.3109/14659891.2011.615002</pub-id><pub-id pub-id-type="medline">23525509</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>Chautrakarn</surname><given-names>S</given-names> </name><name name-style="western"><surname>Khumros</surname><given-names>W</given-names> </name><name name-style="western"><surname>Phutrakool</surname><given-names>P</given-names> </name></person-group><article-title>Self-medication with over-the-counter medicines among the working age population in metropolitan areas of Thailand</article-title><source>Front Pharmacol</source><year>2021</year><volume>12</volume><issue>726643</issue><fpage>726643</fpage><pub-id pub-id-type="doi">10.3389/fphar.2021.726643</pub-id><pub-id pub-id-type="medline">34456738</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Marcelo</surname><given-names>AB</given-names> </name><name name-style="western"><surname>Pascual</surname><given-names>KC</given-names> </name><name name-style="western"><surname>Udayasankaran</surname><given-names>JG</given-names> </name><name name-style="western"><surname>Allaudin</surname><given-names>FS</given-names> </name><name name-style="western"><surname>Kijsanayotin</surname><given-names>B</given-names> </name></person-group><article-title>A framework for regional health information systems interoperability: the asia ehealth information network (AeHIN) experience</article-title><source>Roadmap to Successful Digital Health Ecosystems</source><year>2022</year><publisher-name>Elsevier</publisher-name><fpage>399</fpage><lpage>414</lpage><pub-id pub-id-type="doi">10.1016/B978-0-12-823413-6.00005-7</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>Mamuye</surname><given-names>AL</given-names> </name><name name-style="western"><surname>Yilma</surname><given-names>TM</given-names> </name><name name-style="western"><surname>Abdulwahab</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Health information exchange policy and standards for digital health systems in africa: a systematic review</article-title><source>PLOS Digit Health</source><year>2022</year><month>10</month><volume>1</volume><issue>10</issue><fpage>e0000118</fpage><pub-id pub-id-type="doi">10.1371/journal.pdig.0000118</pub-id><pub-id pub-id-type="medline">36812615</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Top 10 frequency of the most common abbreviations and First-round results of interface term selection.</p><media xlink:href="medinform_v14i1e80039_app1.docx" xlink:title="DOCX File, 26 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Interface Terminology mapped to SNOMED CT (Systematized Nomenclature of Medicine Clinical Terms).</p><media xlink:href="medinform_v14i1e80039_app2.xlsx" xlink:title="XLSX File, 234 KB"/></supplementary-material></app-group></back></article>