<?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">v14i1e96548</article-id><article-id pub-id-type="doi">10.2196/96548</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Real-World Applicability of Multiple International Terminology Systems in Oncology: Mapping Study of Clinical Terms for Cancer Diagnosis and Treatment</article-title></title-group><contrib-group><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Jang</surname><given-names>Boyun</given-names></name><degrees>MPH</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author" equal-contrib="yes"><name name-style="western"><surname>Park</surname><given-names>Eunhye</given-names></name><degrees>MPH</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff2">2</xref><xref ref-type="fn" rid="equal-contrib1">*</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Lee</surname><given-names>Sangwon</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Ju</surname><given-names>Eunbi</given-names></name><degrees>BS</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>Jang</surname><given-names>Yewon</given-names></name><degrees>BS</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>Kwak</surname><given-names>In Hae</given-names></name><degrees>BS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Choi</surname><given-names>Kui Son</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kong</surname><given-names>Hyun-Joo</given-names></name><degrees>MS</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Cha</surname><given-names>Hyo Soung</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Kim</surname><given-names>Hyun-Jin</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Chae</surname><given-names>Heejung</given-names></name><degrees>MD, PhD</degrees><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="aff" rid="aff4">4</xref></contrib></contrib-group><aff id="aff1"><institution>Cancer Data Center, National Cancer Control Institute, National Cancer Center</institution><addr-line>Goyang</addr-line><country>South Korea</country></aff><aff id="aff2"><institution>Department of Medical Information Management, National Cancer Center</institution><addr-line>Goyang</addr-line><country>South Korea</country></aff><aff id="aff3"><institution>Department of Public Health and Artificial Intelligence, Graduate School of Cancer Science and Policy, National Cancer Center</institution><addr-line>Goyang</addr-line><country>South Korea</country></aff><aff id="aff4"><institution>Department of Internal Medicine, Seoul National University Bundang Hospital</institution><addr-line>82 Gumi-ro 173beon-gil</addr-line><addr-line>Seongnam</addr-line><country>South Korea</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name></contrib><contrib contrib-type="editor"><name name-style="western"><surname>Steenstra</surname><given-names>Ivan</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Satravada</surname><given-names>Baby</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Triep</surname><given-names>Karen</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Werle</surname><given-names>Silke D</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Heejung Chae, MD, PhD, Department of Internal Medicine, Seoul National University Bundang Hospital, 82 Gumi-ro 173beon-gil, Seongnam, 13620, South Korea, +82-31-787-7863; <email>hchae21@gmail.com</email></corresp><fn fn-type="equal" id="equal-contrib1"><label>*</label><p>these authors contributed equally</p></fn><fn fn-type="other" id="pa1"><label>&#x2021;</label><p>Department of Internal Medicine, Seoul National University Bundang Hospital, 82 Gumi-ro 173 beon-gil, Bundang, Seongnam, Republic of Korea</p></fn></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>27</day><month>10</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e96548</elocation-id><history><date date-type="received"><day>02</day><month>04</month><year>2026</year></date><date date-type="rev-recd"><day>15</day><month>09</month><year>2026</year></date><date date-type="accepted"><day>16</day><month>09</month><year>2026</year></date></history><copyright-statement>&#x00A9; Boyun Jang, Eunhye Park, Sangwon Lee, Eunbi Ju, Yewon Jang, In Hae Kwak, Kui Son Choi, Hyun-Joo Kong, Hyo Soung Cha, Hyun-Jin Kim, Heejung Chae. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 27.10.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR 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/e96548"/><abstract><sec><title>Background</title><p>With the rapid expansion of health care data, multiple international standardized terminology systems have been developed and refined to ensure semantic interoperability, which is a crucial factor in facilitating collaborative use.</p></sec><sec><title>Objective</title><p>This study aimed to evaluate the real-world use and applicability of standardized terminology systems by mapping clinical terms from routine cancer care and to propose guidelines that optimize mapping.</p></sec><sec sec-type="methods"><title>Methods</title><p>Clinical terms generated during cancer care at the National Cancer Center Korea were extracted and mapped to multiple target terminology systems: the Korean Standard Classification of Diseases; <italic>International Classification of Diseases, 9th Revision, Clinical Modification</italic>; Logical Observation Identifiers Names and Codes; RxNorm; Anatomical Therapeutic Chemical classification; and Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT). A multidisciplinary working group of health care information managers, data experts, and oncologists verified the mapping outcomes, calculated the cross-verification discordance rate, and compared the coverage across systems.</p></sec><sec sec-type="results"><title>Results</title><p>A total of 3472 source terms were identified across 7 domains: chief complaint, diagnosis, laboratory test, imaging test, surgery/procedure, medication, and radiation therapy. With postcoordination and predefined mapping guidelines, SNOMED CT achieved high overall mapping rates (98.3%&#x2010;100%) across domains. Applying postcoordination as needed substantially improved exact semantic match rates, which exceeded 90% in most domains. However, more than 40% of source terms were broadly mapped in the imaging test and radiation therapy domains because procedural details such as imaging technique and radiation field configuration could not be represented in SNOMED CT. The cross-verification discordance rate between mappers, defined as the proportion of source terms with disagreement, remained low (0.3%&#x2010;1.3%). RxNorm and Logical Observation Identifiers Names and Codes showed complementary strengths within their specialized domains, adding detail or specificity where SNOMED CT was less complete.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>Standardized terminology systems are feasible and effective in encoding clinical terms for cancer care. SNOMED CT was the most comprehensive, and predefined mapping guidelines provide a structured framework for mapping and consensus resolution. Domain-specific systems should be used alongside SNOMED CT, and all systems should be updated regularly to reflect evolving clinical practice.</p></sec></abstract><kwd-group><kwd>clinical terms</kwd><kwd>health care terminology</kwd><kwd>mapping</kwd><kwd>oncology</kwd><kwd>Systematized Nomenclature of Medicine Clinical Terms</kwd><kwd>SNOMED CT</kwd><kwd>terminology standard</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>With advances in IT and precision medicine, health care data volumes have expanded exponentially [<xref ref-type="bibr" rid="ref1">1</xref>]. The growth of multicenter research and federated analyses has increased the complexity of data exchange. Unlike other big data, health care data originates from diverse sources, many of which are unstructured, creating interoperability challenges when integrating real-world data for clinical research [<xref ref-type="bibr" rid="ref2">2</xref>]. Effective exchange requires 4 levels of interoperability: foundational, structural, semantic, and organizational. Semantic interoperability, enabling different systems to interpret information with the same meaning, is critical for complex, large-scale health care data [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>].</p><p>Standardized terminology systems that define and organize medical terms have been developed to achieve semantic interoperability. In the 1940s, the World Health Organization (WHO) introduced the <italic>International Classification of Diseases</italic> (<italic>ICD</italic>) for morbidity and mortality statistics, the current version of which is the <italic>ICD-11</italic>. With advances in oncology, more specialized systems have been established, such as the <italic>International Classification of Diseases for Oncology</italic> (<italic>ICD-O</italic>), which codes neoplasms by tumor site (topography) and histology (morphology) [<xref ref-type="bibr" rid="ref5">5</xref>]. Additional domain-specific systems include the <italic>ICD-10</italic>-Procedure Coding System (<italic>ICD-10</italic>-PCS) for surgical procedures and treatments, Logical Observation Identifiers Names and Codes (LOINC) for laboratory tests, and RxNorm for medications [<xref ref-type="bibr" rid="ref6">6</xref>-<xref ref-type="bibr" rid="ref8">8</xref>]. Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT), originating from the College of American Pathologists&#x2019; Systematized Nomenclature of Pathology and later merged with the United Kingdom&#x2019;s Read Codes, is the most widely adopted standardized medical terminology system [<xref ref-type="bibr" rid="ref9">9</xref>].</p><p>Despite substantial progress in terminology development, gaps remain in real-world clinical application. High-quality research requires minimizing information loss during terminology mapping. However, the application of multiple standardized terminology systems to original real-world clinical terms containing detailed, unaltered information has not been widely examined, and potential intermapper discrepancies have not been fully evaluated. Moreover, few studies have addressed the unique complexities of patients with cancer, who undergo more diverse and intricate diagnostic and treatment processes than general patients. In this study, a multidisciplinary team mapped clinical terms from routine cancer care to multiple standardized terminology systems to assess their applicability, identify challenges, and propose guidelines for optimizing real-world clinical terminology mapping.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Working Group</title><p>The Cancer Data Center of the National Cancer Center Korea (NCCK), South Korea&#x2019;s National Cancer Data Center, establishes the data infrastructure and utilization environment required to promote nationwide cancer data research. As part of these efforts, a clinical term-to-standard terminology mapping project was initiated. A multidisciplinary working group of 3 data experts, 7 health information managers, and 2 clinical oncologists was convened. Data experts, who are responsible for building and maintaining the National Cancer Data Center research database and NCCK Clinical Research Data Warehouse (CRDW), conducted source term extraction, integration of the mapping outputs into the database, and quality control to ensure data integrity and operational suitability for standardization and reuse. Five health information managers, with expertise in electronic medical record (EMR) data management, multicenter data standardization, and standard terminology mapping, served as primary mappers. Two senior health information managers (the Chief of Medical Information Management Team and the Terminology Governance Lead of the EMR Steering Committee) supervised the overall mapping process and performed final review and approval of all mapping outputs. The 2 dedicated clinical oncologists, 1 medical oncologist and 1 cancer surgeon, contributed domain expertise in cancer care to review whether the clinical meaning of the source terms was preserved during mapping. When specialized clinical interpretation was required, additional consultation was obtained from relevant physicians within the institution. The working group held regular monthly meetings and biweekly written discussions for project design, progress review, mapping issue discussion, and consensus resolution (<xref ref-type="fig" rid="figure1">Figure 1</xref>).</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Structure of the multidisciplinary working group and workflow of the standard terminology mapping process. The National Cancer Center Korea established a multidisciplinary working group comprising data experts, certified health information managers, and clinical oncologists, with domain-specific physicians consulted as needed. Each step of the mapping process was carried out by the designated members of the working group, as indicated. EMR: electronic medical record.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e96548_fig01.png"/></fig></sec><sec id="s2-2"><title>Study Population and Source Terms</title><p>Candidate source terms were identified from clinical data in the CRDW, which collects comprehensive information from the EMR system and houses deidentified data for research. Patients diagnosed with one of 6 primary cancers (stomach, breast, liver, colorectal, pancreatic, or lung) at the NCCK between 2010 and 2023 were included. Inclusion was based on <italic>ICD</italic>-O-3 codes: C16 (stomach), C50 (breast), C18/C19/C20 (colorectal), C22 (liver), C25 (pancreas), and C33/C34 (lung). Patients with intrahepatic bile duct cancer (C22.1) and islet cell tumors of the pancreas (C25.4) were excluded. Clinical data were extracted and classified into 7 domains: chief complaint, diagnosis, laboratory test, imaging test, surgery/procedure, medication, and radiation therapy. The source terms underwent minimal refinement to preserve their original clinical meaning: correction of typographical errors and spacing, expansion of abbreviations, removal of duplicates, and splitting of multivalued terms. Electronic data interchange (EDI) reimbursement codes for Korean National Health Insurance (NHI) claims and their effective dates were extracted from the CRDW for reference during mapping.</p></sec><sec id="s2-3"><title>Mapping</title><p>Each source term was mapped to relevant standardized terminology systems according to its clinical domain. Domain-specific mappings included the Korean Standard Classification of Diseases (KCD), LOINC, <italic>International Classification of Diseases, 9th Revision, Clinical Modification</italic> (<italic>ICD-9-CM</italic>) Volume 3, RxNorm, and the Anatomical Therapeutic Chemical (ATC); all terms, regardless of domain, were mapped to SNOMED CT (<xref ref-type="fig" rid="figure2">Figure 2</xref>). Although newer procedure classifications such as <italic>ICD-10</italic>-PCS have been developed, <italic>ICD-9-CM</italic> Volume 3 has been used by many countries and remains in use across several Asian countries because of its established role within national coding infrastructures and the operational complexity of migration [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref14">14</xref>]. In South Korea, <italic>ICD-9-CM</italic> continues to serve as the procedure classification reference for national health statistics, and clinical terms are generated and managed on this basis [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Therefore, <italic>ICD-9-CM</italic> Volume 3 was selected for the surgery/procedure domain to reflect the source data context.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Mapping of clinical source terms to domain-specific standard terminology systems. Clinical terms were extracted from the clinical research data warehouse (CRDW), which contains deidentified data sourced from the hospital&#x2019;s electronic medical records (EMR) system. Source terms from 7 clinical domains&#x2014;chief complaint, diagnosis, laboratory test, imaging test, surgery/procedure, medication, and radiation therapy&#x2014;were mapped to appropriate standardized terminology systems. ATC: Anatomical Therapeutic Chemical; <italic>ICD-9-CM</italic>: <italic>International Classification of Diseases, 9th Revision, Clinical Modification</italic>; KCD: Korean Standard Classification of Diseases; LOINC: Logical Observation Identifiers Names and Codes; RxNorm: normalized naming system for generic and branded drugs.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e96548_fig02.png"/></fig><p>All mappings followed the commonly recognized rules for each terminology system. For SNOMED CT, mappings adhered to the SNOMED CT Editorial Guide, compositional grammar, and concept model principles [<xref ref-type="bibr" rid="ref17">17</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. For postcoordination, focus concepts, attributes, and attribute values were selected in accordance with the permitted attributes and value ranges defined in the Machine Readable Concept Model (MRCM) [<xref ref-type="bibr" rid="ref19">19</xref>]. The working group established and shared predefined guidelines with all mappers to specify mapping priorities and ensure consistency when multiple MRCM-compliant mapping options were available within the SNOMED CT framework. SNOMED CT mapping was categorized as &#x201C;exact&#x201D; when the target concept matched the source term in meaning, &#x201C;broad&#x201D; when the target concept was broader than the source, &#x201C;narrow&#x201D; when the target concept was narrower than the source, and &#x201C;not-mapped&#x201D; when no suitable target existed. Given the potential loss of semantic specificity and reduced fidelity to the original clinical meaning, narrow mappings were not counted as successful mappings, and grouped with &#x201C;not-mapped&#x201D; category as &#x201C;narrow/not-mapped&#x201D; in the final mapping performance analysis. Information that the SNOMED CT Editorial Guide identifies as outside the scope of the SNOMED CT International Edition&#x2014;such as brand names in the medicinal product [<xref ref-type="bibr" rid="ref20">20</xref>] and administrative or reimbursement-related procedure descriptions, including procedure counts or procedure order [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref22">22</xref>]&#x2014;was not classified as a broad mapping when absent from the target concept. In contrast, the clinical meaning of the source term itself was considered essential to the mapping and had to be represented in the target concept for the mapping to be classified as exact.</p><p>Following initial mapping by 5 mappers each assigned to a designated subset of source terms, 2 peer mappers cross-reviewed each other&#x2019;s mapping results and recorded agreement or disagreement. Any disagreement was escalated to the multidisciplinary working group for consensus resolution. Clinical oncologists verified that the clinical meaning of each source term was accurately preserved, while data experts and supervising health information managers assessed whether the mapping was operationally appropriate and not overly specific in a way that would compromise standardization and reuse. Final decisions were made by prioritizing (1) accurate preservation of the original clinical meaning and (2) consistent application of predefined mapping principles. Cross-verification results were summarized using the cross-verification discordance rate, defined as the proportion of source terms for which disagreement was identified during cross-verification.</p></sec><sec id="s2-4"><title>Ethical Considerations</title><p>This study analyzed a terminology dataset of clinical source terms extracted from the institutional deidentified data warehouse and their mapping results, rather than individual-level clinical records. The unit of analysis was the terminology concept rather than the individual patient, and the analytic dataset contained no identifiable personal information or patient-level linkage. Accordingly, this study was granted exemption by the Institutional Review Board of NCCK (No. 2026&#x2010;0204), with a waiver of informed consent. The study was conducted in accordance with the principles of the Declaration of Helsinki.</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Identification of Source Terms</title><p>Among the 468,193 patients registered in the CRDW by 2023, 66,380 who were diagnosed with primary stomach, breast, liver, colorectal, pancreatic, or lung cancer between 2010 and 2023 were included. Following extraction, source terms underwent a refinement process, including typographical correction, expansion of abbreviations, duplicate removal, and splitting of multivalued terms (Supplementary Material S1 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). No semantic modification or simplification was allowed. A total of 3472 clinical terms were finalized as source terms (Supplementary Material S2 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). For the chief complaint domain, the 200 most frequent terms were extracted to prioritize the terms most relevant to routine clinical use. For the medication domain, information on drugs related to cancer prevention and treatment was extracted. All available clinical terms were extracted for the remaining domains.</p></sec><sec id="s3-2"><title>Predefined Mapping Guidelines</title><p>While all mappings followed the official guidance of each terminology system, the working group established predefined guidelines incorporating oncology-specific considerations to better preserve the original clinical context of source terms and improve consistency across mappers when multiple clinically plausible and terminology-compliant mapping options were available. The predefined guidelines were as follows.</p><p>To map chief complaint and diagnosis terms to KCD, if the source term is semantically identical to a subterm of the KCD target term, it should be mapped to that subterm; otherwise, it should be mapped to the main term, which is the primary identifier for the KCD code. In the surgery/procedure domain, if a single-source term contains multiple surgeries or procedures, each surgery or procedure should be mapped individually. The Korean Standard Terminology of Medicine can be used as a supplementary reference for mapping to the <italic>ICD-9-CM</italic> [<xref ref-type="bibr" rid="ref23">23</xref>]. Although the EDI codes for NHI claims may be considered when available, priority should be given to the meaning of the source term from the CRDW.</p><p>For SNOMED CT, each source term should typically be mapped to the relevant hierarchy; however, if a chief complaint indicates the purpose of admission (eg, &#x201C;for endoscopic variceal ligation&#x201D;), it should be mapped to the procedure hierarchy. In the medication domain, information outside the scope of SNOMED CT, such as brand name or clinical indication (eg, transcatheter arterial chemoembolization), should be excluded. When the focus concept lacks dose form or strength information, postcoordination should be used. In the radiation therapy domain, if the meaning of a source term is ambiguous, it should be clarified by referencing the EDI codes for NHI claims before mapping. Narrow mappings that might distort the original meaning of the source term should be avoided, and exact mappings should be prioritized over broad mappings. When multiple postcoordinated representations are possible within SNOMED CT Editorial Guide and MRCM-defined attribute constraints, focus concepts, attributes, and attribute values should be selected according to the priority rules summarized in <xref ref-type="table" rid="table1">Table 1</xref>.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) postcoordination priorities by clinical domains.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain and focus concept</td><td align="left" valign="bottom">Attribute-value<break/>(semantic tag)</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Chief complaint</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Symptom</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select the focus concept corresponding to the main symptom</td><td align="left" valign="top">Postcoordinate &#x201C;Site (body structure),&#x201D; if applicable</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Reason for admission</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select &#x201C;304566005 |Admission for treatment (procedure)|&#x201D; as the focus concept</td><td align="left" valign="top">Apply postcoordination in the following priority order:<break/>&#x2460; Treatment name (procedure, regimen/therapy)<break/>&#x2461; Causative procedure (procedure)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select &#x201C;76464004 |Hospital admission, for observation (procedure)|&#x201D; as the focus concept</td><td align="left" valign="top">Postcoordinate &#x201C;Test name (procedure),&#x201D; if applicable</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Complications</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select the focus concept corresponding to the main symptom</td><td align="left" valign="top">Postcoordinate &#x201C;Causative procedure or surgery (procedure),&#x201D; if applicable</td></tr><tr><td align="left" valign="top" colspan="2">Diagnosis</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select the focus concept that best captures the following information, in priority order:<break/>&#x2460; Behavior + morphology + site<break/>&#x2461; Morphology + site<break/>&#x2462; Behavior + site<break/>&#x2463; Behavior + morphology<break/>&#x2464; Morphology<break/>&#x2465; Behavior</td><td align="left" valign="top">Postcoordinate additional information not captured by the focus concept in the following priority order:<break/>&#x2460; Detailed site or laterality (body structure)<break/>&#x2461; Detailed morphology (morphologic abnormality)<break/>&#x2462; Other information (disorder, observable entity, qualifier value, procedure)</td></tr><tr><td align="left" valign="top" colspan="2">Laboratory test</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select the focus concept that best captures the following information, in priority order:<break/>&#x2460; Test name + sample type<break/>&#x2461; Test name</td><td align="left" valign="top">Postcoordinate additional information not captured by the focus concept in the following priority order:<break/>&#x2460; Test substance (substance, cell)<break/>&#x2461; (Detailed) sample type (specimen)<break/>&#x2462; Test method (procedure)<break/>&#x2463; Quantitative/qualitative (qualifier value)<break/>&#x2464; Other information (qualifier value, physical object, person)</td></tr><tr><td align="left" valign="top" colspan="2">Imaging test</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>In-house imaging study</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select the focus concept that best captures the following information, in priority order:<break/>&#x2460; Modality + site + position<break/>&#x2461; Modality + site + injected agents<break/>&#x2462; Modality + site<break/>&#x2463; Modality + injected agents<break/>&#x2464; Modality</td><td align="left" valign="top">Postcoordinate additional information not captured by the focus concept in the following priority order:<break/>&#x2460; (Detailed) site or laterality (body structure)<break/>&#x2461; Injected agents (substance, procedure)<break/>&#x2462; Test method (procedure)<break/>&#x2463; Purpose of test (procedure)<break/>&#x2464; Using device (physical object, physical force)<break/>&#x2465; Other information (disorder, finding, qualifier value, physical force, person)</td></tr><tr><td align="left" valign="top" colspan="2"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Review of outside imaging</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select &#x201C;28191001 |Consultation and report by radiologist (procedure)|&#x201D; as the focus concept</td><td align="left" valign="top">Apply postcoordination in the following priority order:<break/>&#x2460; Modality + site + injected agents (procedure)<break/>&#x2461; Modality + site (procedure)<break/>&#x2462; (Detailed) site (body structure)</td></tr><tr><td align="left" valign="top" colspan="2">Surgery/procedure</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>No additional priority rules</td><td align="left" valign="top">No additional priority rules</td></tr><tr><td align="left" valign="top" colspan="2">Medication</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>Select the focus concept that best captures the following information, in priority order:<break/>&#x2460; Ingredient + dose form + strength<break/>&#x2461; Ingredient + dose form</td><td align="left" valign="top">Postcoordinate additional information not captured by the focus concept in the following priority order:<break/>&#x2460; Detailed dose form (dose form)<break/>&#x2461; Detailed dose form unit (unit of presentation)<break/>&#x2462; Numerator value (qualifier value)<break/>&#x2463; Numerator unit (qualifier value)<break/>&#x2464; Denominator value (qualifier value)<break/>&#x2465; Denominator unit (qualifier value)</td></tr><tr><td align="left" valign="top" colspan="2">Radiation therapy</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>No additional priority rules needed</td><td align="left" valign="top">No additional priority rules needed</td></tr></tbody></table></table-wrap><p>All mappings followed the SNOMED CT Editorial Guide and MRCM. The priorities listed below were applied additionally, only when multiple valid mapping options existed within these rules.</p><p>SNOMED CT concepts are displayed in the format &#x201C;concept identifier |term|.&#x201D; The numeric identifier represents the SNOMED CT concept ID, and the term enclosed by vertical bars (&#x201C;| |&#x201D;) is the human-readable SNOMED CT term [<xref ref-type="bibr" rid="ref18">18</xref>]. Numbered items (&#x2460;, &#x2461;, &#x2462;, etc) indicate the priority order used in this study for selecting focus concepts or postcoordination attributes when a source term contained multiple mappable elements.</p></sec><sec id="s3-3"><title>Mapping Results</title><p><xref ref-type="table" rid="table2">Table 2</xref> provides examples of how source terms were mapped to the corresponding target terminology systems in each clinical domain and how the SNOMED CT postcoordination priorities described in <xref ref-type="table" rid="table1">Table 1</xref> were applied. Supplementary Material S3 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> provides further details on the selection of SNOMED CT postcoordination attributes. For instance, in the case of &#x201C;Carcinosarcoma, connective and soft tissue, unspecified&#x201D; in the diagnosis domain, no single target term representing both &#x201C;&#x2460; behavior + morphology + site&#x201D; and &#x201C;&#x2461; morphology + site&#x201D; could be identified. Therefore, the focus concepts &#x201C;448274000 |Malignant neoplasm of connective tissue (disorder)|&#x201D; and &#x201C;269469005 |Malignant neoplasm of soft tissue (disorder)|&#x201D; were used to capture the &#x201C;&#x2462; behavior (malignant) and the sites (connective and soft tissue)&#x201D; in a 1:N relationship. The remaining information, morphology, was captured using a postcoordinated expression: &#x201C;116676008 |Associated morphology(attribute)| = 63264007 |Carcinosarcoma(morphologic abnormality)|.&#x201D; In the laboratory test domain, following the priority order of &#x201C;&#x2460; Test name + sample type,&#x201D; no single concept capturing both elements was available for &#x201C;Anti-HCV, immunoassay.&#x201D; The second priority, test name, was mapped to the focus concept &#x201C;64411004 | Hepatitis C antibody measurement (procedure)|.&#x201D; The remaining details were represented through postcoordination by specifying the &#x201C;&#x2461; (Detailed) sample type (specimen),&#x201D; and &#x201C;&#x2462; Test method (procedure)&#x201D; as follows: &#x201C;116686009 |Has specimen(attribute)| = 119364003 |Serum specimen (specimen)|&#x201D; and &#x201C;370129005 |Measurement method (attribute)| = 104417008 |Immunoassay, qualitative, multiple step method (procedure)|,&#x201D; respectively.</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Examples of mappings for each domain.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain: clinical source terms</td><td align="left" valign="bottom">Target</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="2">Chief complaint: Back pain</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>KCD<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup></td><td align="left" valign="top">M54.99 |Dorsalgia, unspecified, site unspecified|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<sup><xref ref-type="table-fn" rid="table2fn2">b</xref></sup><break/>(1:1 Exact)</td><td align="left" valign="top">161891005 |Backache (finding)|</td></tr><tr><td align="left" valign="top" colspan="2">Diagnosis: carcinosarcoma, connective and soft tissue, unspecified</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>KCD<sup><xref ref-type="table-fn" rid="table2fn3">c</xref></sup></td><td align="left" valign="top">C49.9 |Malignant neoplasm of connective and soft tissue, unspecified|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:N Exact)</td><td align="left" valign="top">&#x2460; 448274000 |Malignant neoplasm of connective tissue (disorder)| : { 116676008 |Associated morphology (attribute)| = 63264007 |Carcinosarcoma (morphologic abnormality)| } &#x2461; 269469005 |Malignant neoplasm of soft tissue (disorder)| : { 116676008 |Associated morphology (attribute)| = 63264007 |Carcinosarcoma (morphologic abnormality)| }</td></tr><tr><td align="left" valign="top" colspan="2">Laboratory test: Anti-HCV<sup><xref ref-type="table-fn" rid="table2fn4">d</xref></sup> (test name: hepatitis test and serology; sample name: serum; test unit: X) (EDI<sup><xref ref-type="table-fn" rid="table2fn5">e</xref></sup>: precision immunoassay-hepatitis C antibody)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>LOINC<sup><xref ref-type="table-fn" rid="table2fn6">f</xref></sup></td><td align="left" valign="top">13955&#x2010;0 |Hepatitis C virus Ab [Presence] in Serum or Plasma by Immunoassay|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top">64411004 |Hepatitis C antibody measurement (procedure)| : { 116686009 |Has specimen (attribute)| = 119364003 |Serum specimen (specimen)|, 370129005 |Measurement method (attribute)| = 104417008 |Immunoassay, qualitative, multiple step method (procedure)| }</td></tr><tr><td align="left" valign="top" colspan="2">Imaging test: CT<sup><xref ref-type="table-fn" rid="table2fn7">g</xref></sup> dynamic liver (contrast)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top">438591004 |Computed tomography triple phase of liver (procedure)|</td></tr><tr><td align="left" valign="top" colspan="2">Surgery/ procedure: Laparoscopic pelvic lymphadenectomy</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>ICD-9</italic>-<italic>CM</italic><sup><xref ref-type="table-fn" rid="table2fn8">h</xref></sup></td><td align="left" valign="top">40.3 | Regional lymph node excision|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top">14059008 |Pelvic lymphadenectomy (procedure)| : { 424226004 |Using device (attribute)| = 86174004 |Laparoscope, device (physical object)| }</td></tr><tr><td align="left" valign="top" colspan="2">Medication: Adriamycin RDF<sup><xref ref-type="table-fn" rid="table2fn9">i</xref></sup> 10 mg (doxorubicin)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>RxNorm</td><td align="left" valign="top">1790097 |5 ML doxorubicin hydrochloride 2 mg/mL Injection|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>ATC<sup><xref ref-type="table-fn" rid="table2fn10">j</xref></sup></td><td align="left" valign="top">L01DB01 |Doxorubicin|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top">1209144002 |Product containing precisely doxorubicin hydrochloride 2 mg/mL conventional release solution for infusion and/or injection|</td></tr><tr><td align="left" valign="top" colspan="2">Radiation therapy: Intensity modulated radiation therapy [per session] (EDI: IMRT-VMAT)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top">1156530009 |Volumetric modulated arc therapy (procedure)|</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>KCD: Korean Standard Classification of Diseases.</p></fn><fn id="table2fn2"><p><sup>b</sup>SNOMED CT: Systematized Nomenclature of Medicine Clinical Terms. </p></fn><fn id="table2fn3"><p><sup>c</sup>KCD: Korean Standard Classification of Diseases.</p></fn><fn id="table2fn4"><p><sup>d</sup>Hepatitis C virus.</p></fn><fn id="table2fn5"><p><sup>e</sup>EDI: EDI codes for NHI claims.</p></fn><fn id="table2fn6"><p><sup>f</sup>LOINC: Logical Observation Identifiers Names and Codes.</p></fn><fn id="table2fn7"><p><sup>g</sup>CT: computed tomography.</p></fn><fn id="table2fn8"><p><sup>h</sup><italic>ICD-9-CM</italic>: <italic>International Classification of Diseases, 9th Revision, Clinical Modification</italic>.</p></fn><fn id="table2fn9"><p><sup>i</sup>RDF: ready to dilute formulation.</p></fn><fn id="table2fn10"><p><sup>j</sup>ATC: Anatomical Therapeutic Chemical.</p></fn></table-wrap-foot></table-wrap><p>After mapping all the source terms, we examined how each term was represented across multiple target terminology systems to identify system-specific characteristics (<xref ref-type="table" rid="table3">Table 3</xref>). In the chief complaint and diagnosis domains, KCD could not fully represent certain terms, such as purposes of admission (eg, &#x201C;for transplantation work-up&#x201D;) or morphological detail in &#x201C;adenocarcinoma of sigmoid colon,&#x201D; whereas SNOMED CT captured these terms via postcoordination. In the surgery/procedure domain, behavioral characteristics (eg, malignancy) could not be included in <italic>ICD-9-CM</italic> procedure codes, whereas SNOMED CT allowed behavior to be represented as attributes in addition to the procedure focus. In the laboratory test domain, LOINC supports the specification of the unit of measure (eg, mg/dL for phosphate) through recommended units, whereas SNOMED CT lacks this level of unit specificity. Conversely, LOINC could not capture additional contextual information, such as &#x201C;(em)&#x201D; denoting an emergency procedure, whereas SNOMED CT could via postcoordination. In the medication domain, RxNorm generally represented detailed medication information most completely; for example, it captured ingredient, dose form, strength, and brand name for &#x201C;Avastin 400 mg injection (bevacizumab).&#x201D; In contrast, SNOMED CT represented ingredient, dose form, and strength but typically did not include brand name and often expressed strength per unit (eg, 25 mg per 1 mL) rather than total dose. The ATC classification included only ingredient-level information. Although RxNorm was usually the most complete, exceptions existed; for example, for &#x201C;Mitomycin-C Kyowa,&#x201D; SNOMED CT provided more complete information than RxNorm.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Comparison of mapping results according to the target terminology system.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain: clinical source terms</td><td align="left" valign="bottom" colspan="2">Target</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="3">Chief complaint: For transplantation work-up</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>KCD<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup></td><td align="left" valign="top" colspan="2">Z04.8 |Examination and observation for other specified reasons|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup><break/>(1:1 Exact)</td><td align="left" valign="top" colspan="2">76464004 |Hospital admission, for observation<break/>(procedure)| : { 363702006 |Has focus (attribute)| = 1303222006 | Pretransplant evaluation of recipient (procedure)| }</td></tr><tr><td align="left" valign="top" colspan="3">Diagnosis: Adenocarcinoma of sigmoid colon</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>KCD<sup><xref ref-type="table-fn" rid="table3fn3">c</xref></sup></td><td align="left" valign="top" colspan="2">C18.7 |Malignant neoplasm of sigmoid colon|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top" colspan="2">301756000 |Adenocarcinoma of sigmoid colon (disorder)|</td></tr><tr><td align="left" valign="top" colspan="3">Laboratory test: Phosphorus (em)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>LOINC<sup><xref ref-type="table-fn" rid="table3fn4">d</xref></sup></td><td align="left" valign="top" colspan="2">2777&#x2010;1 |Phosphate [Mass/volume] in Serum or Plasma|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top" colspan="2">8364005 |Phosphorus measurement (procedure)| : { 116686009 |Has specimen (attribute)| = 119364003 |Serum specimen (specimen)|, 260870009 |Priority (attribute)| = 25876001 |Emergency (qualifier value)| }</td></tr><tr><td align="left" valign="top" colspan="3">Surgery/ procedure: Excision of retroperitoneal tumor (malignant)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><italic>ICD-9-CM</italic><sup><xref ref-type="table-fn" rid="table3fn5">e</xref></sup></td><td align="left" valign="top" colspan="2">54.4 |Excision or destruction of peritoneal tissue|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content><break/>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top" colspan="2">8951004 |Excision of lesion of retroperitoneum<break/>(procedure)| : { 363700003 |Direct morphology (attribute)| = 1240414004 |Malignant neoplasm (morphologic abnormality)| }</td></tr><tr><td align="left" valign="top" colspan="3">Medication:<break/>Avastin 400 mg inj<break/>(bevacizumab)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>RxNorm</td><td align="left" valign="top" colspan="2">1657074 |16 ML bevacizumab 25 MG/ML Injection [Avastin]|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>ATC<sup><xref ref-type="table-fn" rid="table3fn6">f</xref></sup></td><td align="left" valign="top" colspan="2">L01FG01 |Bevacizumab|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top" colspan="2">781788003 |Product containing precisely bevacizumab 25 milligram/1 milliliter conventional release solution for injection (clinical drug)|</td></tr><tr><td align="left" valign="top" colspan="3">Medication:<break/>Mitomycin-c kyowa<break/>10 mg inj (mitomycin)</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>RxNorm</td><td align="left" valign="top" colspan="2">1165372 |Mitomycin Injectable Product|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>ATC</td><td align="left" valign="top" colspan="2">L01DC03 |Mitomycin|</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>SNOMED CT<break/>(1:1 Exact)</td><td align="left" valign="top" colspan="2">326815001 |Product containing precisely mitomycin 10 milligram/1 vial powder for conventional release solution for injection (clinical drug)|</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>KCD: Korean Standard Classification of Diseases.</p></fn><fn id="table3fn2"><p><sup>b</sup>SNOMED CT: Systematized Nomenclature of Medicine Clinical Terms.</p></fn><fn id="table3fn3"><p><sup>c</sup>KCD: Korean Standard Classification of Diseases.</p></fn><fn id="table3fn4"><p><sup>d</sup>LOINC: Logical Observation Identifiers Names and Codes.</p></fn><fn id="table3fn5"><p><sup>e</sup><italic>ICD-9-CM</italic>: <italic>International Classification of Diseases, 9th Revision, Clinical Modification</italic>.</p></fn><fn id="table3fn6"><p><sup>f</sup>ATC: Anatomical Therapeutic Chemical.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s3-4"><title>Cross-Verification and Consensus Resolution</title><p>The initial mapping performed by the assigned mapper was additionally reviewed by 2 peer mappers, who recorded their agreement or disagreement with each mapping result. A mapping was considered discordant if either reviewer disagreed with the initial mapping result, and such cases were referred to the multidisciplinary working group for consensus resolution. There were no major discrepancies in the chief complaint, imaging test, or medication domains; the remaining domains showed cross-verification discordance rates of 0.3% to 1.3%. In the diagnosis domain, the cross-verification discordance rate was 0.3%, primarily involving source terms containing more than 1 anatomical site. This was resolved by adding a rule specifying that if multiple sites in a source term belong to the same parent concept, the term should be mapped to that parent concept rather than mapped 1:N to each child concept. For example, &#x201C;Neoplasm of uncertain or unknown behavior of liver, gallbladder, and bile ducts&#x201D; should be mapped to &#x201C;liver and/or biliary passages,&#x201D; not separately to &#x201C;liver,&#x201D; &#x201C;gallbladder,&#x201D; and &#x201C;bile duct.&#x201D; The surgery/procedure domain showed a 1.0% cross-verification discordance rate, largely from inconsistent handling of parenthetical details; this was addressed by mapping to target terms that incorporate the parenthetical meaning whenever possible (eg, retaining &#x201C;malignant&#x201D; in targets for &#x201C;excision of retroperitoneal tumor (malignant)&#x201D;). A 1.3% cross-verification discordance rate in the radiation therapy domain was mostly attributable to limited familiarity with the SNOMED CT relationship groups. Even when the meaning of a source term is not entirely reflected in the fully specified name of a focus concept, relationship group attributes may convey the necessary details, negating additional postcoordination. For example, &#x201C;external irradiation&#x2013;high energy radiotherapy&#x201D; should map to the SNOMED CT concept &#x201C;high energy beam therapy,&#x201D; which includes a device attribute in its relationship group that represents external beam delivery, eliminating the need to encode &#x201C;external irradiation&#x201D; and &#x201C;high energy.&#x201D; Through this process of cross-verification and consensus discussion within the multidisciplinary working group, final mappings were confirmed; as examples, the mapping results for the 20% most frequent terms per each clinical domain are provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p></sec><sec id="s3-5"><title>Mapping Rates by Standardized Terminology System</title><p>Overall mapping rates were high across most domain-system pairs, with the chief complaint domain showing the lowest rates at 97.7% for KCD and 98.3% for SNOMED CT (Supplementary Material S5 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). The narrow/not-mapped terms in the chief complaint domain were primarily attributable to ambiguity or insufficient specificity in the source terms, such as &#x201C;oozing,&#x201D; &#x201C;prolapse,&#x201D; &#x201C;malfunction,&#x201D; and &#x201C;for admission,&#x201D; for which a semantically appropriate SNOMED CT target could not be reliably selected. In the diagnosis domain, KCD achieved a 100% mapping rate, whereas SNOMED CT achieved 99.9% because a small number of source terms that could only be narrowly mapped (eg, malignant neoplasm of overlapping lesion of other and ill-defined sites) were treated as narrow/not mapped. Outside these two domains, all source terms were successfully mapped to SNOMED CT. In the medication domain, 1.2% of the terms were not mapped to RxNorm owing to the absence of codes for drugs approved only in specific countries (eg, TS-1). All source terms were successfully mapped to other systems (LOINC, <italic>ICD-9-CM</italic> Volume 3, and ATC) within their respective domains.</p><p>The detailed SNOMED CT mapping results are presented in <xref ref-type="table" rid="table4">Table 4</xref>. Among the exact mappings, precoordination predominated in chief complaint (64.7%), diagnosis (79.1%), imaging test (58.9%), surgery/procedure (63.1%), medication (90.1%), and radiation therapy (70.7%), whereas postcoordination was more frequent in laboratory tests (80.2%). In laboratory tests, postcoordination captures additional information such as quantitative/qualitative details and test methods beyond the focus concept. Broad mappings occurred most frequently in the imaging test (43.3%) and radiation therapy domains (40.7%). In the imaging test domain, broad mappings arose mainly because information on view and projection (eg, pelvic inlet and outlet), patient position (eg, decubitus, supine, and erect), and other acquisition techniques (eg, 3D reconstruction and low-dose protocols) could not be represented in the target concepts. In the radiation therapy domain, source terms in the treatment prescription subdomain showed a high broad mapping rate (61.3%), while source terms in the treatment site subdomain achieved a 100% exact mapping rate. Specifically, most broad mappings resulted from incomplete representation of the number of ports (eg, 3 ports) and field arrangement (eg, parallel-opposed 2 fields), whereas information on the preparation processes (eg, simulation and treatment planning), modalities (eg, tomotherapy), and radiation types (eg, proton therapy) was precisely represented in the target concepts.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) mapping results<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup>.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Mapping type<sup><xref ref-type="table-fn" rid="table4fn2">b</xref></sup></td><td align="left" valign="bottom">Chief complaint (%)</td><td align="left" valign="bottom">Diagnosis<break/>(%)</td><td align="left" valign="bottom">Laboratory test (%)</td><td align="left" valign="bottom">Imaging test (%)</td><td align="left" valign="bottom">Surgery/procedure (%)</td><td align="left" valign="bottom">Medication<break/>(%)</td><td align="left" valign="bottom">Radiation therapy (%)<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup></td></tr></thead><tbody><tr><td align="left" valign="top">Exact</td><td align="left" valign="top">97.1</td><td align="left" valign="top">97.8</td><td align="left" valign="top">98.3</td><td align="left" valign="top">56.7</td><td align="left" valign="top">89.3</td><td align="left" valign="top">100</td><td align="left" valign="top">59.3</td></tr><tr><td align="left" valign="top">PRE</td><td align="left" valign="top">64.7</td><td align="left" valign="top">79.1</td><td align="left" valign="top">19.8</td><td align="left" valign="top">58.9</td><td align="left" valign="top">63.1</td><td align="left" valign="top">90.1</td><td align="left" valign="top">70.7</td></tr><tr><td align="left" valign="top">POST</td><td align="left" valign="top">34.1</td><td align="left" valign="top">20.2</td><td align="left" valign="top">75.9</td><td align="left" valign="top">39.7</td><td align="left" valign="top">30.6</td><td align="left" valign="top">9.9</td><td align="left" valign="top">29.3</td></tr><tr><td align="left" valign="top">PRE + POST</td><td align="left" valign="top">1.2</td><td align="left" valign="top">0.7</td><td align="left" valign="top">4.3</td><td align="left" valign="top">1.4</td><td align="left" valign="top">6.2</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td></tr><tr><td align="left" valign="top">Broad<sup><xref ref-type="table-fn" rid="table4fn4">d</xref></sup></td><td align="left" valign="top">1.2</td><td align="left" valign="top">2.2</td><td align="left" valign="top">1.7</td><td align="left" valign="top">43.3</td><td align="left" valign="top">10.7</td><td align="left" valign="top">0.0</td><td align="left" valign="top">40.7</td></tr><tr><td align="left" valign="top">PRE</td><td align="left" valign="top">0.0</td><td align="left" valign="top">91.2</td><td align="left" valign="top">0.0</td><td align="left" valign="top">89.6</td><td align="left" valign="top">63.8</td><td align="left" valign="top">0.0</td><td align="left" valign="top">83.8</td></tr><tr><td align="left" valign="top">POST</td><td align="left" valign="top">100</td><td align="left" valign="top">8.8</td><td align="left" valign="top">100</td><td align="left" valign="top">10.4</td><td align="left" valign="top">30.4</td><td align="left" valign="top">0.0</td><td align="left" valign="top">16.2</td></tr><tr><td align="left" valign="top">PRE + POST</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td><td align="left" valign="top">5.8</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td></tr><tr><td align="left" valign="top">Narrow/not-mapped<sup><xref ref-type="table-fn" rid="table4fn5">e</xref></sup></td><td align="left" valign="top">1.7</td><td align="left" valign="top">0.1</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td><td align="left" valign="top">0.0</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>PRE, precoordinated concept (when an existing SNOMED CT concept fully represented the source term); POST, postcoordinated expression (when a single pre-coordinated concept did not fully capture clinically meaningful details).</p></fn><fn id="table4fn2"><p><sup>b</sup>Absence of information outside the scope of the SNOMED CT International Edition (eg, brand names, reimbursement-related information) was not classified as a broad mapping.</p></fn><fn id="table4fn3"><p><sup>c</sup>By subdomain, mapping results were as follows: Treatment prescription, Exact 38.7% (PRE 32.6%, POST 67.4%), Broad 61.3% (PRE 83.8%, POST 16.2%), and Narrow/not-mapped 0.0%; Treatment site, Exact 100% (PRE 100%, POST 0.0%), Broad 0.0%, and Narrow/not-mapped 0.0%.</p></fn><fn id="table4fn4"><p><sup>d</sup>Examples of broad mapping for each clinical domain are provided in Supplementary Material S6 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p></fn><fn id="table4fn5"><p><sup>e</sup>All narrow/not-mapped cases with detailed rationale are summarized in Supplementary Material S7 in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. These cases were attributable to ambiguity or insufficient specificity of the source terms, which prevented reliable selection of a semantically appropriate SNOMED CT target, rather than to the absence of relevant concepts in SNOMED CT.</p></fn></table-wrap-foot></table-wrap></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><p>We mapped 3472 clinical source terms from real-world records of patients with 6 cancers to multiple standardized terminology systems. Several studies have mapped clinical terms to standardized systems; however, few have documented detailed, real-world mapping experiences. For example, a South Korean study introduced a 9-step process to map local EMR terms to SNOMED CT [<xref ref-type="bibr" rid="ref4">4</xref>], and a Hungarian group mapped 4661 national procedural codes from 2 university hospitals to SNOMED CT [<xref ref-type="bibr" rid="ref24">24</xref>]. Although these studies covered a wide range of clinical terms and offered valuable insights, they limited their source terms to specific domains (eg, procedures), restricted their targets to SNOMED CT, and reported ~60% exact mapping rates because postcoordination was not used. In contrast, we focused on patients with cancer, whose care is particularly complex, to better understand the standardization of clinical terms in oncology, where multicenter research demand is high. We included terms across the continuum of cancer care and mapped them not only to SNOMED CT but also to other standardized systems, depending on the clinical domain. We also conducted exhaustive cross-verification for all mappings, whereas previous studies omitted or only partially applied cross-verification.</p><p>In our study, SNOMED CT achieved high overall mapping rates, ranging from 98.3% to 100% across all domains, confirming its broad applicability as one of the most comprehensive standardized terminology systems. Applying postcoordination as needed substantially improved exact semantic match rates, which exceeded 90% in most domains. Prior studies have noted lower exact mapping rates in certain domains [<xref ref-type="bibr" rid="ref25">25</xref>-<xref ref-type="bibr" rid="ref28">28</xref>]. For instance, Sung [<xref ref-type="bibr" rid="ref25">25</xref>] et al reported that only 1574/4,111 (38.2%) EDI codes for NHI claims mapped in the laboratory test domain, and Kang et al [<xref ref-type="bibr" rid="ref28">28</xref>] found a 398/2500 (31.9%) match for therapeutic/surgical procedures; Jung [<xref ref-type="bibr" rid="ref27">27</xref>] et al showed 11,453/22,610 (50.6%) for medications. However, these rates reflect a reliance on precoordinated concepts. After applying postcoordination, Sung et al [<xref ref-type="bibr" rid="ref25">25</xref>] and Kang et al [<xref ref-type="bibr" rid="ref28">28</xref>] improved to 90.4% and 63.6%, respectively. Similarly, our precoordinated match in laboratory tests was 19.8%, rising to 98.3% with postcoordination. SNOMED CT postcoordination also captured details not represented by LOINC attributes, underscoring its role in fully representing the original clinical data and enabling precise use across domains [<xref ref-type="bibr" rid="ref29">29</xref>,<xref ref-type="bibr" rid="ref30">30</xref>].</p><p>However, even when postcoordination was used, exact semantic match rates remained relatively low in the imaging test and radiation therapy domains, with broad mappings accounting for more than 40% of source terms in each domain. In the imaging test domain, imaging adjustments related to view or projection, patient position, and technique were not permitted in postcoordination, although such information was considered clinically important for the correct acquisition and interpretation of images [<xref ref-type="bibr" rid="ref31">31</xref>]. Similarly, in the radiation therapy domain, the number of ports and field arrangement could not be represented in SNOMED CT International Edition, despite their relevance to treatment configuration and dosimetric evaluation. Although these limitations reflect the scope and modeling principle of the SNOMED CT International Edition, which does not include certain protocol- or configuration-level details to maintain standardized representation of clinical procedures, our findings suggest that this approach may reduce the semantic fidelity of complex imaging and radiation therapy data that are crucial to cancer care and research. To improve semantic representation, frequently used details could be represented through SNOMED CT national extensions and organized through implementation-specific reference sets. In addition, acquisition parameters and radiation therapy protocol details could be captured using complementary domain-specific terminologies and standards such as Radiology Lexicon and Digital Imaging and Communications in Medicine, including its radiotherapy extension (Digital Imaging and Communications in Medicine &#x2013; Radiation Therapy) [<xref ref-type="bibr" rid="ref32">32</xref>-<xref ref-type="bibr" rid="ref34">34</xref>]. Such a combined approach may help preserve detailed procedural information and improve semantic interoperability in real-world oncology data.</p><p>Despite the breadth of SNOMED CT, the complementary use of domain-specific systems is necessary to capture the full characteristics of source terms. For example, although SNOMED CT aligns with the Identification of Medicinal Products, an international standard for dose forms and clinically appropriate strengths, it has limitations with respect to brand names, packaging, and country-specific details (eg, drug codes and reimbursement/insurance status) [<xref ref-type="bibr" rid="ref35">35</xref>-<xref ref-type="bibr" rid="ref37">37</xref>]. In contrast, RxNorm represents drug information in greater detail, including multi-ingredient combinations, brand names, exact strengths, and national drug codes. In our study, with precoordination alone, coverage for ingredients, dose form, and strength was same for SNOMED CT (90.1%) and RxNorm (90.1%), but RxNorm more precisely represented the dosage by explicitly encoding the total dose. Although postcoordination can improve SNOMED CT coverage, encoding dosage through postcoordination increases structural complexity, which is a practical limitation. Such country-specific details can also be addressed through a national extension of SNOMED CT, which allows member countries to add concepts and reference sets to meet national requirements while retaining interoperability with the international core [<xref ref-type="bibr" rid="ref38">38</xref>]. In the United Kingdom, for example, the NHS dictionary of medicines and devices, implemented as the SNOMED CT UK Drug Extension, represents brand names, packaging, and reimbursement-related information using SNOMED CT-compatible identifiers [<xref ref-type="bibr" rid="ref39">39</xref>]. As South Korea joined SNOMED International in 2020 and is currently developing a national extension, such administrative or policy-related details could also be represented in addition to internationally standardized clinical concepts.</p><p>For laboratory tests, LOINC provides a more specialized representation than SNOMED CT via its six-axis model, namely component, property, time, system, scale, and method [<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]. In our study, precoordinated SNOMED CT concepts alone accounted for only 19.8% of exact SNOMED CT mappings in the laboratory test domain, whereas the remaining 80.2% of exact mappings required postcoordination. Although SNOMED CT postcoordination enabled high mapping rates and captured additional contexts not represented by LOINC (eg, urgent testing status), this limited precoordinated coverage explains the widespread adoption of LOINC-based coding system for laboratory test data in many institutions. These findings support the complementary use of domain-specific terminology systems alongside SNOMED CT. Beyond using these systems in parallel, the recently released LOINC Ontology, a LOINC and SNOMED CT interoperability solution jointly developed by Regenstrief Institute and SNOMED International, may offer a more integrated approach [<xref ref-type="bibr" rid="ref42">42</xref>,<xref ref-type="bibr" rid="ref43">43</xref>]. By representing LOINC content within a SNOMED CT concept model, it is expected to enhance LOINC&#x2019;s computability and improve interoperability between LOINC-coded laboratory observations and broader SNOMED CT-based clinical concepts. Such integrated approaches, rather than the independent use of separate domain-specific terminology systems, may further enhance the semantic interoperability and reusability of real-world clinical data.</p><p>To broaden the adoption of SNOMED CT, whose strengths are detailed semantics and wide applicability, the complexity of postcoordination must be addressed [<xref ref-type="bibr" rid="ref44">44</xref>]. Postcoordination was necessary for 9.9% to 80.2% of the exact mappings in our study. However, SNOMED CT&#x2019;s flexibility, supporting various precoordinated and postcoordinated expressions, can yield inconsistent code usage across mappers, challenging standardization, because multiple concepts with similar meanings may exist and several valid combinations of focus concepts, attributes, and attribute values may exist [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref45">45</xref>]. In this study, the use of predefined mapping priorities in addition to SNOMED CT Editorial Guide and MRCM supported high consistency in postcoordination decisions (cross-verification discordance rate, 0.3%&#x2010;1.3%). To maintain consistency without sacrificing the flexibility of SNOMED CT, it is necessary to incorporate structured mapper training in both clinical domain knowledge and terminology systems, predefined priority rules on selecting focus concepts and attributes, standardized postcoordination templates or reusable expression libraries for recurrent source-term patterns, and cross-verification with regular consensus review. In addition, SNOMED CT content should be periodically updated through the review of frequently used postcoordinated expressions in routine clinical practice, which may be considered as candidates for precoordinated concepts or national extensions.</p><p>This study has the limitation in that mappings were developed at a single institution without multicenter validation. Because standard terminology mapping can be influenced by institution-specific workflows, local code management practices, and information system environments, whether the present results can be applied identically to other institutions remains uncertain. Nevertheless, interinstitutional heterogeneity in South Korea might be relatively less pronounced than in health care systems with more fragmented insurance and coding structures. South Korea operates a single-payer NHI system, and medical services are documented and managed using national-level classification systems. In addition, recent government-led initiatives have continued to promote the standardization of health data across institutions, through the establishment of multicenter common clinical data infrastructures (eg, the Data-Driven Hospital Project and the Korea-Clinical Data Utilization Network for Research Excellence), as well as national standards for health data elements terminology (eg, the Korea Core Data for Interoperability) [<xref ref-type="bibr" rid="ref46">46</xref>,<xref ref-type="bibr" rid="ref47">47</xref>]. Accordingly, source terms linked to nationally standardized coding systems, such as KCD, LOINC, and EDI claims codes for NHI, are less likely to show large interinstitutional variation and may therefore be more consistently applicable across other institutions. In contrast, locally maintained terms, such as institution-specific names for procedures, surgeries, laboratory tests, and imaging studies, or free-text entries in chief complaints, may yield different mapping results across institutions. Further multicenter validation should focus on these locally maintained terms to determine whether our mapping results remain reproducible across institutions and to identify which source-term categories require local adaptation before broader implementation.</p><p>Another limitation concerns the choice of procedure classification system. <italic>ICD-9-CM</italic> Volume 3 was selected for the surgery/procedure domain, considering the Korean clinical coding context in which <italic>ICD-9-CM</italic>&#x2013;based procedure classification continues to serve as a reference classification for national health statistics [<xref ref-type="bibr" rid="ref15">15</xref>]. However, this may limit the international applicability of the mapped data. Procedure and intervention classification remains highly heterogeneous across countries. Although the WHO introduced International Classification of Procedures in Medicine in 1978, it was not subsequently maintained, and many countries developed their own procedure classification systems with different structures and purposes, limiting international comparability of intervention data [<xref ref-type="bibr" rid="ref48">48</xref>-<xref ref-type="bibr" rid="ref50">50</xref>]. In response to the need for more harmonized frameworks, the WHO has developed the International Classification of Health Interventions to provide a common structure to which codes in national classifications can be mapped for compiling international data [<xref ref-type="bibr" rid="ref51">51</xref>]. Further studies will be needed to extend the mapping of local clinical terms beyond <italic>ICD-9-CM</italic> toward emerging global standards, thereby enhancing the international interoperability of real-world clinical data.</p><p>To the best of our knowledge, this is the first large-scale investigation to compare the strengths and limitations of multiple standardized terminology systems by mapping real-world clinical terms across a full continuum of cancer care. Our study demonstrates the feasibility of applying standardized terminology systems to real-world oncology terms. SNOMED CT is the most comprehensive and universally applicable system, whereas domain-specific systems play essential roles in capturing more specialized aspects of clinical data. Clear mapping priorities in addition to the official guidance for each terminology system, together with cross-verification and consensus review, provided a practical framework for resolving mapping disagreement while maintaining flexibility. Regular updates of standardized terminology systems to accommodate newly emerging clinical terms, together with ongoing mapper education, are important to maintain mapping consistency. Future work may enhance the interoperability of real-world cancer data and contribute to the standardization of research data for the development of clinical decision support systems, health care information exchange, and multicenter research facilitation.</p></sec></body><back><ack><p>Generative AI, OpenAI ChatGPT, was used for language refinement and editing of text originally drafted by the authors. It was not used to analyze data, interpret results, generate figures, or collect references. The authors reviewed and revised all AI-assisted suggestions and take full responsibility for the final manuscript.</p></ack><notes><sec><title>Funding</title><p>This work was supported by the National Cancer Center Korea [2310850&#x2010;3]. The funding source had no role in the study design, data collection, data analysis, interpretation of results, manuscript preparation, or the decision to submit the manuscript for publication.</p></sec><sec><title>Data Availability</title><p>The dataset used in this research contains original clinical information extracted from an electronic medical record system and, therefore, cannot be made publicly available. Deidentified data may be shared by the corresponding author upon reasonable request for academic research purposes.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: KSC, SL, HSC</p><p>Data curation: SL, EJ, YJ, IHK</p><p>Investigation: BJ, EP, SL, EJ, YJ</p><p>Resources: KSC, HJ Kong, HSC, HJ Kim</p><p>Writing &#x2013; original draft: BJ, EP, SL, EJ, YJ</p><p>Writing &#x2013; review &#x0026; editing: HC</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">ATC</term><def><p>Anatomical Therapeutic Chemical</p></def></def-item><def-item><term id="abb2">CRDW</term><def><p>Clinical Research Data Warehouse</p></def></def-item><def-item><term id="abb3">EDI</term><def><p>electronic data interchange</p></def></def-item><def-item><term id="abb4">EMR</term><def><p>electronic medical record</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"><italic>ICD-10-PCS</italic></term><def><p><italic>International Classification of Diseases, 10th Revision, Procedure Coding System</italic></p></def></def-item><def-item><term id="abb7"><italic>ICD-9-CM</italic></term><def><p><italic>International Classification of Diseases, 9th Revision, Clinical Modification</italic></p></def></def-item><def-item><term id="abb8"><italic>ICD-O</italic></term><def><p><italic>International Classification of Diseases for Oncology</italic></p></def></def-item><def-item><term id="abb9">KCD</term><def><p>Korean Standard Classification of Diseases</p></def></def-item><def-item><term id="abb10">LOINC</term><def><p>Logical Observation Identifiers Names and Codes</p></def></def-item><def-item><term id="abb11">MRCM</term><def><p>Machine Readable Concept Model</p></def></def-item><def-item><term id="abb12">NCCK</term><def><p>National Cancer Center Korea</p></def></def-item><def-item><term id="abb13">NHI</term><def><p>National Health Insurance</p></def></def-item><def-item><term id="abb14">SNOMED CT</term><def><p>Systematized Nomenclature of Medicine Clinical Terms</p></def></def-item><def-item><term id="abb15">WHO</term><def><p>World Health Organization</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Matengo</surname><given-names>W</given-names> </name><name name-style="western"><surname>Otsieno</surname><given-names>E</given-names> </name><name name-style="western"><surname>Wanjiru</surname><given-names>K</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Chaari</surname><given-names>L</given-names> </name></person-group><article-title>Big data analytics in healthcare</article-title><source>Digital Health in Focus of Predictive, Preventive and Personalised Medicine</source><year>2020</year><publisher-name>Springer</publisher-name><fpage>129</fpage><lpage>138</lpage><pub-id pub-id-type="doi">10.1007/978-3-030-49815-3_15</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>Amar</surname><given-names>F</given-names> </name><name name-style="western"><surname>April</surname><given-names>A</given-names> </name><name name-style="western"><surname>Abran</surname><given-names>A</given-names> </name></person-group><article-title>Electronic health record and semantic issues using Fast Healthcare Interoperability Resources: systematic mapping review</article-title><source>J Med Internet Res</source><year>2024</year><month>01</month><day>30</day><volume>26</volume><fpage>e45209</fpage><pub-id pub-id-type="doi">10.2196/45209</pub-id><pub-id pub-id-type="medline">38289660</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="web"><source>Healthcare Information and Management Systems Society (HIMSS)</source><year>2020</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://legacy.himss.org/resources/interoperability-healthcare">https://legacy.himss.org/resources/interoperability-healthcare</ext-link></comment></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Sung</surname><given-names>S</given-names> </name><name name-style="western"><surname>Park</surname><given-names>HA</given-names> </name><name name-style="western"><surname>Jung</surname><given-names>H</given-names> </name><name name-style="western"><surname>Kang</surname><given-names>H</given-names> </name></person-group><article-title>A SNOMED CT mapping guideline for the local terms used to document clinical findings and procedures in electronic medical records in South Korea: methodological study</article-title><source>JMIR Med Inform</source><year>2023</year><month>04</month><day>18</day><volume>11</volume><fpage>e46127</fpage><pub-id pub-id-type="doi">10.2196/46127</pub-id><pub-id pub-id-type="medline">37071456</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="book"><person-group person-group-type="editor"><name name-style="western"><surname>Fritz</surname><given-names>AG</given-names> </name></person-group><source>International Classification of Diseases for Oncology: ICD-O</source><year>2000</year><edition>3</edition><publisher-name>World Health Organization</publisher-name><pub-id pub-id-type="other">978-92-4-154534-1</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>Averill</surname><given-names>RF</given-names> </name><name name-style="western"><surname>Mullin</surname><given-names>RL</given-names> </name><name name-style="western"><surname>Steinbeck</surname><given-names>BA</given-names> </name><name name-style="western"><surname>Goldfield</surname><given-names>NI</given-names> </name><name name-style="western"><surname>Grant</surname><given-names>TM</given-names> </name></person-group><article-title>Development of the ICD-10 procedure coding system (ICD-10-PCS)</article-title><source>Top Health Inf Manage</source><year>2001</year><month>02</month><volume>21</volume><issue>3</issue><fpage>54</fpage><lpage>88</lpage><pub-id pub-id-type="medline">11234732</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>McDonald</surname><given-names>CJ</given-names> </name><name name-style="western"><surname>Huff</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Suico</surname><given-names>JG</given-names> </name><etal/></person-group><article-title>LOINC, a universal standard for identifying laboratory observations: a 5-year update</article-title><source>Clin Chem</source><year>2003</year><month>04</month><volume>49</volume><issue>4</issue><fpage>624</fpage><lpage>633</lpage><pub-id pub-id-type="doi">10.1373/49.4.624</pub-id><pub-id pub-id-type="medline">12651816</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>Nelson</surname><given-names>SJ</given-names> </name><name name-style="western"><surname>Zeng</surname><given-names>K</given-names> </name><name name-style="western"><surname>Kilbourne</surname><given-names>J</given-names> </name><name name-style="western"><surname>Powell</surname><given-names>T</given-names> </name><name name-style="western"><surname>Moore</surname><given-names>R</given-names> </name></person-group><article-title>Normalized names for clinical drugs: RxNorm at 6 years</article-title><source>J Am Med Inform Assoc</source><year>2011</year><volume>18</volume><issue>4</issue><fpage>441</fpage><lpage>448</lpage><pub-id pub-id-type="doi">10.1136/amiajnl-2011-000116</pub-id><pub-id pub-id-type="medline">21515544</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>Stearns</surname><given-names>MQ</given-names> </name><name name-style="western"><surname>Price</surname><given-names>C</given-names> </name><name name-style="western"><surname>Spackman</surname><given-names>KA</given-names> </name><name name-style="western"><surname>Wang</surname><given-names>AY</given-names> </name></person-group><article-title>SNOMED clinical terms: overview of the development process and project status</article-title><source>Proc AMIA Symp</source><year>2001</year><fpage>662</fpage><lpage>666</lpage><pub-id pub-id-type="medline">11825268</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>Zafirah</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Nur</surname><given-names>AM</given-names> </name><name name-style="western"><surname>Puteh</surname><given-names>SEW</given-names> </name><name name-style="western"><surname>Aljunid</surname><given-names>SM</given-names> </name></person-group><article-title>Potential loss of revenue due to errors in clinical coding during the implementation of the Malaysia diagnosis related group (MY-DRG<sup>&#x00AE;</sup>) Casemix system in a teaching hospital in Malaysia</article-title><source>BMC Health Serv Res</source><year>2018</year><month>01</month><day>25</day><volume>18</volume><issue>1</issue><fpage>38</fpage><pub-id pub-id-type="doi">10.1186/s12913-018-2843-1</pub-id><pub-id pub-id-type="medline">29370785</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>Opitasari</surname><given-names>C</given-names> </name><name name-style="western"><surname>Nurwahyuni</surname><given-names>A</given-names> </name></person-group><article-title>The completeness and accuracy of clinical coding for diagnosis and medical procedure on the INA-CBGs claim amounts at a hospital in South Jakarta</article-title><source>Health Sci J Indones</source><year>2018</year><month>10</month><day>19</day><volume>9</volume><issue>1</issue><fpage>14</fpage><lpage>18</lpage><pub-id pub-id-type="doi">10.22435/hsji.v9i1.464</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>Chan</surname><given-names>KKP</given-names> </name><name name-style="western"><surname>Ng</surname><given-names>TCC</given-names> </name><name name-style="western"><surname>Sze</surname><given-names>CY</given-names> </name><etal/></person-group><article-title>Validation of diagnosis codes for pleural diseases and procedure codes for relevant respiratory procedures in a healthcare database in Hong Kong: a single tertiary centre study</article-title><source>Hong Kong Med J</source><year>2026</year><month>02</month><volume>32</volume><issue>1</issue><fpage>13</fpage><lpage>22</lpage><pub-id pub-id-type="doi">10.12809/hkmj2412275</pub-id><pub-id pub-id-type="medline">41612789</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>Yu</surname><given-names>L</given-names> </name><name name-style="western"><surname>Lang</surname><given-names>J</given-names> </name></person-group><article-title>Diagnosis-related Groups (DRG) pricing and payment policy in China: where are we?</article-title><source>Hepatobiliary Surg Nutr</source><year>2020</year><month>12</month><volume>9</volume><issue>6</issue><fpage>771</fpage><lpage>773</lpage><pub-id pub-id-type="doi">10.21037/hbsn-2020-8</pub-id><pub-id pub-id-type="medline">33299831</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>Giordani</surname><given-names>B</given-names> </name><name name-style="western"><surname>Burgio</surname><given-names>A</given-names> </name><name name-style="western"><surname>Grippo</surname><given-names>F</given-names> </name><name name-style="western"><surname>Barone</surname><given-names>A</given-names> </name><name name-style="western"><surname>Eugeni</surname><given-names>E</given-names> </name><name name-style="western"><surname>Baglio</surname><given-names>G</given-names> </name></person-group><article-title>The use of ICD-9-CM coding to identify COVID-19 diagnoses and determine risk factors for 30-day death rate in hospitalized patients in Italy: retrospective study</article-title><source>JMIR Public Health Surveill</source><year>2024</year><month>02</month><day>23</day><volume>10</volume><fpage>e44062</fpage><pub-id pub-id-type="doi">10.2196/44062</pub-id><pub-id pub-id-type="medline">38393763</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="report"><person-group person-group-type="author"><collab>Korean Health Information Management Association</collab></person-group><article-title>Study on development of Korean classification of health interventions, year 7 [Report in Korean]</article-title><year>2023</year><access-date>2026-08-02</access-date><publisher-name>Statistics Korea</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://mlib1.kostat.go.kr/search/detail/CATSUZ000000099128?location=A0000001">https://mlib1.kostat.go.kr/search/detail/CATSUZ000000099128?location=A0000001</ext-link></comment></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>Lee</surname><given-names>YK</given-names> </name><name name-style="western"><surname>Hong</surname><given-names>SO</given-names> </name><name name-style="western"><surname>Park</surname><given-names>SJ</given-names> </name><etal/></person-group><article-title>Data resource profile: the Korea National Hospital Discharge In-depth Injury Survey</article-title><source>Epidemiol Health</source><year>2021</year><volume>43</volume><fpage>e2021052</fpage><pub-id pub-id-type="doi">10.4178/epih.e2021052</pub-id><pub-id pub-id-type="medline">34412448</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="web"><article-title>SNOMED CT editorial guide</article-title><source>SNOMED International</source><year>2025</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide">https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide</ext-link></comment></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="web"><article-title>Compositional grammar specification</article-title><source>SNOMED International</source><year>2025</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-specifications/snomed-ct-compositional-grammar-specification">https://docs.snomed.org/snomed-ct-specifications/snomed-ct-compositional-grammar-specification</ext-link></comment></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="web"><article-title>SNOMED CT Machine Readable Concept Model</article-title><source>SNOMED International</source><year>2026</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-specifications/snomed-ct-machine-readable-concept-model">https://docs.snomed.org/snomed-ct-specifications/snomed-ct-machine-readable-concept-model</ext-link></comment></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="web"><article-title>Medicinal product</article-title><source>SNOMED International</source><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/medicinal-product">https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/pharmaceutical-and-biologic-product/medicinal-product</ext-link></comment></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><article-title>Out of scope</article-title><source>SNOMED International</source><year>2025</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/snomed-ct-introduction/out-of-scope">https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/snomed-ct-introduction/out-of-scope</ext-link></comment></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="web"><article-title>Procedure modeling</article-title><source>SNOMED International</source><year>2026</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/procedure/index-2">https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/procedure/index-2</ext-link></comment></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="report"><article-title>Korean Standard Terminology of Medicine (KOSTOM), version 7</article-title><access-date>2026-10-12</access-date><publisher-name>Ministry of Health and Welfare, Republic of Korea</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.hins.or.kr">https://www.hins.or.kr</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>M&#x00E9;sz&#x00E1;ros</surname><given-names>&#x00C1;</given-names> </name><name name-style="western"><surname>Kov&#x00E1;cs</surname><given-names>S</given-names> </name><name name-style="western"><surname>H&#x00E9;ja</surname><given-names>T</given-names> </name><name name-style="western"><surname>Bagyura</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Zempl&#x00E9;nyi</surname><given-names>A</given-names> </name></person-group><article-title>Mapping Hungarian procedure codes to SNOMED CT</article-title><source>BMC Med Res Methodol</source><year>2023</year><month>10</month><day>18</day><volume>23</volume><issue>1</issue><fpage>240</fpage><pub-id pub-id-type="doi">10.1186/s12874-023-02036-x</pub-id><pub-id pub-id-type="medline">37853326</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>Sung</surname><given-names>S</given-names> </name><name name-style="western"><surname>Park</surname><given-names>HA</given-names> </name><name name-style="western"><surname>Park</surname><given-names>SK</given-names> </name><name name-style="western"><surname>Jung</surname><given-names>H</given-names> </name><name name-style="western"><surname>Kang</surname><given-names>H</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>MS</given-names> </name></person-group><article-title>Mapping Korean National Health Insurance claim codes for laboratory test to SNOMED CT</article-title><source>Stud Health Technol Inform</source><year>2023</year><month>05</month><day>18</day><volume>302</volume><fpage>78</fpage><lpage>82</lpage><pub-id pub-id-type="doi">10.3233/SHTI230068</pub-id><pub-id pub-id-type="medline">37203613</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>Hwang</surname><given-names>EJ</given-names> </name><name name-style="western"><surname>Park</surname><given-names>HA</given-names> </name><name name-style="western"><surname>Sohn</surname><given-names>SK</given-names> </name><etal/></person-group><article-title>Mapping Korean EDI medical procedure code to SNOMED CT</article-title><source>Stud Health Technol Inform</source><year>2019</year><month>08</month><day>21</day><volume>264</volume><fpage>178</fpage><lpage>182</lpage><pub-id pub-id-type="doi">10.3233/SHTI190207</pub-id><pub-id pub-id-type="medline">31437909</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>Jung</surname><given-names>H</given-names> </name><name name-style="western"><surname>Park</surname><given-names>HA</given-names> </name><name name-style="western"><surname>Kang</surname><given-names>H</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>M</given-names> </name><name name-style="western"><surname>Sung</surname><given-names>S</given-names> </name><name name-style="western"><surname>Park</surname><given-names>S</given-names> </name></person-group><article-title>Mapping Korean National Health Insurance pharmaceutical claim codes to SNOMED CT</article-title><source>Stud Health Technol Inform</source><year>2022</year><month>05</month><day>25</day><volume>294</volume><fpage>297</fpage><lpage>301</lpage><pub-id pub-id-type="doi">10.3233/SHTI220462</pub-id><pub-id pub-id-type="medline">35612080</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>Kang</surname><given-names>H</given-names> </name><name name-style="western"><surname>Park</surname><given-names>HA</given-names> </name></person-group><article-title>Mapping Korean National Health Insurance reimbursement claim codes for therapeutic and surgical procedures to SNOMED-CT to facilitate data reuse</article-title><source>Stud Health Technol Inform</source><year>2022</year><month>06</month><day>6</day><volume>290</volume><fpage>101</fpage><lpage>105</lpage><pub-id pub-id-type="doi">10.3233/SHTI220040</pub-id><pub-id pub-id-type="medline">35672979</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>Richesson</surname><given-names>RL</given-names> </name><name name-style="western"><surname>Andrews</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Krischer</surname><given-names>JP</given-names> </name></person-group><article-title>Use of SNOMED CT to represent clinical research data: a semantic characterization of data items on case report forms in vasculitis research</article-title><source>J Am Med Inform Assoc</source><year>2006</year><volume>13</volume><issue>5</issue><fpage>536</fpage><lpage>546</lpage><pub-id pub-id-type="doi">10.1197/jamia.M2093</pub-id><pub-id pub-id-type="medline">16799121</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>Campbell</surname><given-names>JR</given-names> </name><name name-style="western"><surname>Xu</surname><given-names>J</given-names> </name><name name-style="western"><surname>Fung</surname><given-names>KW</given-names> </name></person-group><article-title>Can SNOMED CT fulfill the vision of a compositional terminology? Analyzing the use case for problem list</article-title><source>AMIA Annu Symp Proc</source><year>2011</year><volume>2011</volume><fpage>181</fpage><lpage>188</lpage><pub-id pub-id-type="medline">22195069</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="web"><article-title>Imaging adjustments for view, projection, or technique</article-title><source>SNOMED International</source><year>2025</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/procedure/index-1/index/imaging-adjustments-for-view-projection-or-technique">https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/procedure/index-1/index/imaging-adjustments-for-view-projection-or-technique</ext-link></comment></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>Marquis</surname><given-names>M</given-names> </name><name name-style="western"><surname>Bossenko</surname><given-names>I</given-names> </name><name name-style="western"><surname>Ross</surname><given-names>P</given-names> </name></person-group><article-title>RadLex and SNOMED CT integration: a pilot study for standardising radiology classification</article-title><source>Insights Imaging</source><year>2025</year><month>03</month><day>13</day><volume>16</volume><issue>1</issue><fpage>58</fpage><pub-id pub-id-type="doi">10.1186/s13244-025-01935-5</pub-id><pub-id pub-id-type="medline">40080225</pub-id></nlm-citation></ref><ref id="ref33"><label>33</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kahn</surname><given-names>CE</given-names> </name><name name-style="western"><surname>Langlotz</surname><given-names>CP</given-names> </name><name name-style="western"><surname>Channin</surname><given-names>DS</given-names> </name><name name-style="western"><surname>Rubin</surname><given-names>DL</given-names> </name></person-group><article-title>Informatics in radiology: an information model of the DICOM standard</article-title><source>Radiographics</source><year>2011</year><volume>31</volume><issue>1</issue><fpage>295</fpage><lpage>304</lpage><pub-id pub-id-type="doi">10.1148/rg.311105085</pub-id><pub-id pub-id-type="medline">20980665</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Law</surname><given-names>MYY</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>B</given-names> </name></person-group><article-title>Informatics in radiology: DICOM-RT and its utilization in radiation therapy</article-title><source>Radiographics</source><year>2009</year><volume>29</volume><issue>3</issue><fpage>655</fpage><lpage>667</lpage><pub-id pub-id-type="doi">10.1148/rg.293075172</pub-id><pub-id pub-id-type="medline">19270073</pub-id></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bodenreider</surname><given-names>O</given-names> </name><name name-style="western"><surname>Cornet</surname><given-names>R</given-names> </name><name name-style="western"><surname>Vreeman</surname><given-names>DJ</given-names> </name></person-group><article-title>Recent developments in clinical terminologies&#x2014;SNOMED CT, LOINC, and RxNorm</article-title><source>Yearb Med Inform</source><year>2018</year><month>08</month><volume>27</volume><issue>1</issue><fpage>129</fpage><lpage>139</lpage><pub-id pub-id-type="doi">10.1055/s-0038-1667077</pub-id><pub-id pub-id-type="medline">30157516</pub-id></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bodenreider</surname><given-names>O</given-names> </name><name name-style="western"><surname>James</surname><given-names>J</given-names> </name></person-group><article-title>The new SNOMED CT International Medicinal Product model</article-title><source>CEUR Workshop Proc</source><year>2018</year><month>12</month><volume>2285</volume><fpage>36</fpage><pub-id pub-id-type="medline">36277122</pub-id></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Noel Nikiema</surname><given-names>J</given-names> </name><name name-style="western"><surname>Bodenreider</surname><given-names>O</given-names> </name></person-group><article-title>Comparing the representation of medicinal products in RxNorm and SNOMED CT&#x2014;consequences on interoperability</article-title><source>CEUR Workshop Proc</source><year>2019</year><month>08</month><volume>2931</volume><fpage>F1</fpage><lpage>F6</lpage><pub-id pub-id-type="medline">36276234</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="web"><article-title>Extension and customization</article-title><source>SNOMED International</source><year>2025</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-starter-guide/10-extension-and-customization">https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-starter-guide/10-extension-and-customization</ext-link></comment></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="web"><article-title>Dictionary of medicines and devices (dm+d)</article-title><source>NHS England Digital</source><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://digital.nhs.uk/services/terminology-and-classifications/dm-d">https://digital.nhs.uk/services/terminology-and-classifications/dm-d</ext-link></comment></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="web"><article-title>LOINC users&#x2019; guide</article-title><source>LOINC</source><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://loinc.org/kb/users-guide">https://loinc.org/kb/users-guide</ext-link></comment></nlm-citation></ref><ref id="ref41"><label>41</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bodenreider</surname><given-names>O</given-names> </name></person-group><article-title>Issues in mapping LOINC laboratory tests to SNOMED CT</article-title><source>AMIA Annu Symp Proc</source><year>2008</year><month>11</month><day>6</day><fpage>51</fpage><lpage>55</lpage><pub-id pub-id-type="medline">18999311</pub-id></nlm-citation></ref><ref id="ref42"><label>42</label><nlm-citation citation-type="web"><article-title>Implementation guide for the LOINC ontology</article-title><source>SNOMED International</source><year>2026</year><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/implementation-guides/loinc-implementation-guide">https://docs.snomed.org/implementation-guides/loinc-implementation-guide</ext-link></comment></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="web"><source>Regenstrief Institute &#x0026; SNOMED International</source><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://loincsnomed.org/">https://loincsnomed.org/</ext-link></comment></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Benson</surname><given-names>T</given-names> </name></person-group><source>Principles of Health Interoperability HL7 and SNOMED</source><year>2012</year><edition>2</edition><publisher-name>Springer</publisher-name><pub-id pub-id-type="other">9781447128007</pub-id></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>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="ref46"><label>46</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>S</given-names> </name><name name-style="western"><surname>Choi</surname><given-names>YH</given-names> </name><name name-style="western"><surname>Kim</surname><given-names>HM</given-names> </name><etal/></person-group><article-title>The Cancer Clinical Library Database (CCLD) from the Korea-Clinical Data Utilization Network for Research Excellence (K-CURE) project</article-title><source>Cancer Res Treat</source><year>2025</year><month>01</month><volume>57</volume><issue>1</issue><fpage>19</fpage><lpage>27</lpage><pub-id pub-id-type="doi">10.4143/crt.2024.218</pub-id><pub-id pub-id-type="medline">39010797</pub-id></nlm-citation></ref><ref id="ref47"><label>47</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Kwon</surname><given-names>A</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>HY</given-names> </name><name name-style="western"><surname>Shin</surname><given-names>SY</given-names> </name><etal/></person-group><article-title>Current health data standardization project and future directions to ensure interoperability in Korea</article-title><source>Healthc Inform Res</source><year>2024</year><month>04</month><volume>30</volume><issue>2</issue><fpage>93</fpage><lpage>102</lpage><pub-id pub-id-type="doi">10.4258/hir.2024.30.2.93</pub-id><pub-id pub-id-type="medline">38755100</pub-id></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="book"><source>International Classification of Procedures in Medicine</source><year>1978</year><publisher-name>World Health Organization</publisher-name><pub-id pub-id-type="other">9789241541244</pub-id></nlm-citation></ref><ref id="ref49"><label>49</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Paviot</surname><given-names>BT</given-names> </name><name name-style="western"><surname>Madden</surname><given-names>R</given-names> </name><name name-style="western"><surname>Moskal</surname><given-names>L</given-names> </name><etal/></person-group><article-title>Development of a new international classification of health interventions based on an ontology framework</article-title><source>Stud Health Technol Inform</source><year>2011</year><volume>169</volume><fpage>749</fpage><lpage>753</lpage><pub-id pub-id-type="medline">21893847</pub-id></nlm-citation></ref><ref id="ref50"><label>50</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Mellinghoff</surname><given-names>SC</given-names> </name><name name-style="western"><surname>Bruns</surname><given-names>C</given-names> </name><name name-style="western"><surname>Al-Monajjed</surname><given-names>R</given-names> </name><etal/></person-group><article-title>Harmonized procedure coding system for surgical procedures and analysis of surgical site infections (SSI) of five European countries</article-title><source>BMC Med Res Methodol</source><year>2022</year><month>08</month><day>12</day><volume>22</volume><issue>1</issue><fpage>225</fpage><pub-id pub-id-type="doi">10.1186/s12874-022-01702-w</pub-id><pub-id pub-id-type="medline">35962320</pub-id></nlm-citation></ref><ref id="ref51"><label>51</label><nlm-citation citation-type="web"><article-title>WHO-FIC maintenance platform</article-title><source>International Classification of Health Interventions (ICHI)</source><access-date>2026-08-02</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://icd.who.int/dev11/l-ichi/en">https://icd.who.int/dev11/l-ichi/en</ext-link></comment></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Supplementary Material S1. Examples of source term refinement prior to mapping Supplementary Material S2. Number of source terms for mapping by clinical domain and cancer type Supplementary Material S3. Examples illustrating the Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT) postcoordination process Supplementary Material S4. Representative mapping results for the most frequent 20% of clinical terms in each domain to standard terminologies Supplementary Material S5. Mapping rates of source terms to each standard terminology system by clinical domain Supplement Material S6. Representative examples of broad mapping in SNOMED CT for each clinical domain Supplementary Material S7. Complete list of not-mapped cases in SNOMED CT mapping and their rationale.</p><media xlink:href="medinform_v14i1e96548_app1.docx" xlink:title="DOCX File, 442 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Representative mapping results for the most frequent 20% of clinical terms.</p><media xlink:href="medinform_v14i1e96548_app2.xlsx" xlink:title="XLSX File, 146 KB"/></supplementary-material></app-group></back></article>