<?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">v14i1e103470</article-id><article-id pub-id-type="doi">10.2196/103470</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Assessing the Terminological Representation of Context Factors in Clinical Decision-Making Using SNOMED CT: Exploratory Analysis Study</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Schuler</surname><given-names>Katharina</given-names></name><degrees>MSc</degrees><xref ref-type="aff" rid="aff1"/></contrib><contrib contrib-type="author"><name name-style="western"><surname>Sedlmayr</surname><given-names>Martin</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1"/></contrib><contrib contrib-type="author"><name name-style="western"><surname>Henke</surname><given-names>Elisa</given-names></name><degrees>PhD</degrees><xref ref-type="aff" rid="aff1"/></contrib></contrib-group><aff id="aff1"><institution>Institute for Medical Informatics and Biometry, Faculty of Medicine and University Hospital Carl Gustav Carus, Technische Universit&#x00E4;t Dresden</institution><addr-line>Fetscherstra&#x00DF;e 74</addr-line><addr-line>Dresden</addr-line><addr-line>Saxony</addr-line><country>Germany</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Benis</surname><given-names>Arriel</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Cerovecki</surname><given-names>Ivan</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Park</surname><given-names>Kuenyoul</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Tsai</surname><given-names>Meng-Hsun</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Katharina Schuler, MSc, Institute for Medical Informatics and Biometry, Faculty of Medicine and University Hospital Carl Gustav Carus, Technische Universit&#x00E4;t Dresden, Fetscherstra&#x00DF;e 74, Dresden, Saxony, 01307, Germany; <email>Katharina.schuler1@tu-dresden.de</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>19</day><month>11</month><year>2026</year></pub-date><volume>14</volume><elocation-id>e103470</elocation-id><history><date date-type="received"><day>04</day><month>06</month><year>2026</year></date><date date-type="rev-recd"><day>02</day><month>09</month><year>2026</year></date><date date-type="accepted"><day>23</day><month>09</month><year>2026</year></date></history><copyright-statement>&#x00A9; Katharina Schuler, Martin Sedlmayr, Elisa Henke. Originally published in JMIR Medical Informatics (<ext-link ext-link-type="uri" xlink:href="https://medinform.jmir.org">https://medinform.jmir.org</ext-link>), 19.11.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/e103470"/><abstract><sec><title>Background</title><p>Clinical decision-making is inherently shaped by contextual factors that extend beyond guideline-based knowledge and objective clinical parameters. Although clinical decision support systems (CDSSs) aim to improve decision quality and safety, many existing systems insufficiently account for such contextual influences, limiting their effectiveness and acceptance. A prerequisite for a context-sensitive CDSS is the systematic and standardized representation of context factors. However, the extent to which existing clinical terminologies are capable of representing these factors remains unclear.</p></sec><sec><title>Objective</title><p>This study investigates the terminological representability of empirically identified context factors that influence clinical decision-making using SNOMED CT (Systematized Nomenclature of Medicine&#x2014;Clinical Terms) as the semantic interoperability standard.</p></sec><sec sec-type="methods"><title>Methods</title><p>The analysis builds on a previously established set of context concepts identified through a scoping review of empirical literature and organized within a hierarchical conceptual structure. An exploratory manual semantic mapping of these context concepts to SNOMED CT was conducted. Mapping quality was assessed using standardized equivalence classifications (equal, equivalent, wider, narrower, inexact, and unmatched). An independent expert review and consensus process ensured harmonized mapping results. Context concepts not represented in SNOMED CT were also examined using alternative vocabularies via the OHDSI (Observational Health Data Sciences and Informatics) Athena platform.</p></sec><sec sec-type="results"><title>Results</title><p>In total, 189 context concepts were analyzed. Of these, 81.5% (n=154) could be mapped to existing SNOMED CT concepts. Semantic correspondence varied across the analyzed context concepts: 36% (n=68) were classified as equal, 21.2% (n=40) as equivalent, 8.5% (n=16) as wider, 13.8% (n=26) as narrower, and 2.1% (n=4) as inexact. The remaining 18.5% (n=35) were classified as unmatched, indicating that no suitable SNOMED CT correspondence was identified. Patient-related context concepts demonstrated the highest coverage (70/75, 93.3%), whereas institution-related concepts showed substantially lower coverage (7/14, 50%). Mapped concepts were distributed across 11 SNOMED CT domains, most frequently observable entity and qualifier value. Entity-specific analyses revealed differences in both terminological coverage and equivalence status. A majority of nonrepresented concepts were identified in alternative vocabularies, primarily MeSH (23/35, 65.7%) and LOINC (Logical Observation Identifiers Names and Codes; 10/35, 28.6%), albeit often with inexact or partial correspondence.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>The findings indicate that a substantial proportion of empirically identified context factors influencing clinical decision-making can be terminologically represented in SNOMED CT, although relevant gaps persist, particularly for organizational and social context factors. These results highlight both the potential and the limitations of existing clinical terminologies for supporting context-sensitive CDSSs and provide a foundation for future work on semantic standardization, ontology development, and the integration of standardized contextual information into CDSSs.</p></sec></abstract><kwd-group><kwd>clinical decision-making</kwd><kwd>clinical decision support systems</kwd><kwd>Systematized Nomenclature of Medicine&#x2014;Clinical Terms</kwd><kwd>SNOMED CT</kwd><kwd>semantic interoperability</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Physician decision-making constitutes a central element of medical practice, in which scientific evidence, clinical experience, and situational responsibility converge. The quality of these decisions substantially influences the effectiveness, safety, and patient-centeredness of health care delivery [<xref ref-type="bibr" rid="ref1">1</xref>]. Clinical decision-making processes are characterized by a dynamic and iterative workflow in which information is continuously gathered, interpreted, and evaluated in light of situational constraints to derive diagnostic or therapeutic actions [<xref ref-type="bibr" rid="ref2">2</xref>]. In real-world settings, clinical decisions are rarely made under idealized, strictly evidence-based conditions; instead, they are strongly shaped by contextual circumstances. A growing body of empirical research demonstrates that medical decisions are not solely based on objectively measurable clinical parameters but are substantially influenced by contextual factors, including physician experience [<xref ref-type="bibr" rid="ref3">3</xref>], institutional conditions [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>], team interactions [<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref7">7</xref>], and individual patient preferences [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref9">9</xref>]. Accordingly, context factors extend beyond patient characteristics and disease management to include influences related to the treating physician, the professional and organizational environment, and the patient&#x2019;s family [<xref ref-type="bibr" rid="ref10">10</xref>]. Evidence further indicates that such contextual influences can lead to variation in diagnostic or therapeutic decisions even among patients with comparable clinical presentations [<xref ref-type="bibr" rid="ref11">11</xref>]. Clinical decision-making, therefore, extends beyond the mere application of guideline-based knowledge and represents a situational negotiation between medical expertise and the specific conditions of care delivery.</p><p>With the increasing digitalization of health care, the question of how contextual complexity can be represented within data-driven decision-making processes has gained growing relevance. Clinical decision support systems (CDSSs) are widely regarded as a key technology for making clinical decisions safer, more efficient, and more evidence-based [<xref ref-type="bibr" rid="ref12">12</xref>,<xref ref-type="bibr" rid="ref13">13</xref>]. CDSSs integrate patient-specific data, clinical knowledge, and decision rules to generate recommendations for diagnosis, therapy, or monitoring [<xref ref-type="bibr" rid="ref13">13</xref>].</p><p>However, the potential of these systems can only be realized if they adequately account for the situational conditions under which clinical decisions are made [<xref ref-type="bibr" rid="ref13">13</xref>]. In practice, many CDSSs insufficiently incorporate such contextual factors, resulting in inappropriate or redundant alerts and contributing to phenomena such as alert fatigue and declining system acceptance [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. The lack of context sensitivity therefore represents a central limitation of existing systems, affecting not only technical performance but also usability, user acceptance, and successful clinical integration [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. A context-sensitive CDSS is therefore essential and implies the system&#x2019;s ability to deliberately capture and process context factors as the situational conditions of a decision-making scenario in order to provide recommendations that are relevant to both the user and the clinical task [<xref ref-type="bibr" rid="ref17">17</xref>]. To enable such a context-sensitive design of a CDSS, context factors must be systematically identified, formally structured, and made machine-interpretable. In clinical practice, however, contextual information is often incomplete, heterogeneous, or only available in unstructured formats, which substantially limits its reuse within a CDSS [<xref ref-type="bibr" rid="ref18">18</xref>]. Moreover, there is still a lack of standardized representations of contextual information, further impeding the exchange of context-related data across different systems and settings [<xref ref-type="bibr" rid="ref19">19</xref>].</p><p>Embedding human contextual decision logic into a CDSS therefore requires a structured and standardized representation of relevant context factors. Although many technological approaches aim to improve clinical decision-making primarily through data-driven model optimization, the present work places the human dimension of clinical decision-making at the center of analysis. Accordingly, the focus is not on technical system development but on examining the extent to which existing clinical terminologies are capable of representing the contextual influences that shape real-world decision processes.</p><p>Various medical terminologies and classification systems exist to support the standardized representation of clinical information, each with different design purposes and levels of semantic expressiveness. LOINC (Logical Observation Identifiers Names and Codes) primarily focuses on the standardization of laboratory observations and measurements, with contextualization largely limited to attributes such as timing or specimen type [<xref ref-type="bibr" rid="ref20">20</xref>]. The International Classification of Diseases (ICD), while extended in ICD-11 (Revision 11) to increase expressiveness [<xref ref-type="bibr" rid="ref21">21</xref>], remains mainly oriented toward disease classification and coding for statistical and billing purposes. In contrast, SNOMED CT (Systematized Nomenclature of Medicine&#x2014;Clinical Terms) is designed as a comprehensive clinical reference terminology with a formal ontological structure and extensive support for semantic relationships. It provides specific mechanisms for representing contextual information, such as the &#x201C;situation with explicit context&#x201D; hierarchy and postcoordination, enabling flexible modeling of clinical statements [<xref ref-type="bibr" rid="ref22">22</xref>]. Given these characteristics, SNOMED CT was selected as the reference terminology for the present study to assess the terminological representability of context factors in clinical decision-making.</p><p>The objective of this study is to systematically assess the terminological coverage and semantic representability of these context factors within SNOMED CT and to identify areas in which conceptual gaps persist.</p><p>Based on this objective, this study addresses the following research questions:</p><list list-type="simple"><list-item><p>Research question 1: To what extent can empirically identified context factors influencing clinical decision-making be semantically represented by existing concepts in SNOMED CT?</p></list-item><list-item><p>Research question 2: What differences can be observed in the terminological coverage of context factors within SNOMED CT?</p></list-item></list><p>Existing terminology mapping studies have predominantly focused on aligning structured clinical data elements or domain-specific concepts with SNOMED CT. However, clinical decision-making is not solely determined by such structured data but is substantially shaped by contextual factors that are often implicit, heterogeneous, and not formally represented. To date, the terminological representability of these empirically grounded context factors has not been systematically investigated. By mapping a comprehensive, literature-derived set of context factors influencing clinical decision-making to SNOMED CT, this study introduces a novel, human-centered perspective on terminology evaluation. It thereby bridges a critical gap between the situational logic of clinical decision-making and its formal representation in interoperable knowledge systems. The results are intended to provide a foundation for the future development of semantically consistent, context-sensitive CDSSs and to contribute to the standardization and interoperability of context-related information in clinical decision support.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Study Design</title><p>The methodological workflow of the study is illustrated in <xref ref-type="fig" rid="figure1">Figure 1</xref>. The analysis builds on a data foundation developed in previous work, in which context factors of clinical decision-making were systematically identified through a scoping review and subsequently organized within a hierarchical conceptual structure [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. Building on this conceptual framework, the present study applies an exploratory semantic mapping approach to systematically assess the terminological coverage and semantic representability of these context factors within SNOMED CT.</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Overview of the methodological approach. Gray elements indicate preceding work, whereas blue elements represent the methods applied in this study. SNOMED CT: Systematized Nomenclature of Medicine&#x2014;Clinical Terms.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e103470_fig01.png"/></fig></sec><sec id="s2-2"><title>Data Foundation</title><p>The present study builds on a previously established set of evidence-based context factors relevant to clinical decision-making. These factors were identified through a scoping review of the empirical literature and subsequently organized within a structured conceptual framework, as reported in earlier publications [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref23">23</xref>]. The review focused on empirical studies addressing physician decision-making and applied a systematic search across multiple bibliographic databases (eg, PubMed, Web of Science, and Scopus). To support synthesis and consolidation, the identified context factors were iteratively structured and categorized based on the contextual model of Zimmermann et al [<xref ref-type="bibr" rid="ref24">24</xref>] using a multistage expert-based card sorting approach [<xref ref-type="bibr" rid="ref25">25</xref>].</p><p>This process aimed to establish a coherent and clinically meaningful conceptual structure while preserving the semantic richness of the identified factors. The outcome of this process was a hierarchical representation of context factors, referred to in this study as context concepts. This conceptualized dataset serves as the methodological foundation for the semantic mapping of context factors to SNOMED CT conducted in the present work.</p></sec><sec id="s2-3"><title>Mapping to SNOMED CT</title><sec id="s2-3-1"><title>Overview of the Mapping Process</title><p>The defined context concepts constitute the data basis for the terminological mapping conducted in this study. The objective of this step is to systematically examine the extent to which these context concepts can be semantically represented within an established clinical reference terminology. This analysis directly addresses the first research question by quantifying the degree of terminological coverage and identifying areas of limited or missing representation.</p><p>SNOMED CT was selected for the mapping process because it represents the most comprehensive and internationally established clinical reference terminology currently available. The mapping was conducted as an exploratory manual process with independent review by 2 reviewers, both researchers with expertise in medical informatics. The procedure comprised 4 steps adapted from the mapping approach described by Ehrsam et al [<xref ref-type="bibr" rid="ref26">26</xref>]: (1) structuring of the data foundation, (2) exploratory mapping, (3) assessment of semantic coverage, and (4) validation of the results. Each step is described in detail in the following sections and was designed to progressively refine the semantic analysis while maintaining transparency and reproducibility.</p></sec><sec id="s2-3-2"><title>Step 1: Structuring</title><p>First, the previously identified context concepts were systematically prepared in a structured Microsoft Excel spreadsheet [<xref ref-type="bibr" rid="ref27">27</xref>]. A hierarchical overview was created to represent all context factors within the overall conceptual framework according to their entity-specific assignments. The data were then organized into separate worksheets, with each hierarchical level (entity, category, and subcategory) represented on its own sheet. This structuring step was intended to support consistent semantic interpretation across hierarchy levels and to reduce the risk of context loss during the mapping process. Subsequently, the spreadsheet was extended in accordance with the SSSOM (Simple Standard for Sharing Ontology Mappings) guidelines [<xref ref-type="bibr" rid="ref28">28</xref>] by adding structured metadata fields, including concept ID, domain, reviewer ID, date, and equivalence status. The inclusion of these metadata elements enabled systematic and transparent documentation and later analysis of mapping decisions. A detailed description of the corresponding metadata elements is provided in <xref ref-type="table" rid="table1">Table 1</xref>.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Metadata extracted during the mapping process.</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Metadata</td><td align="left" valign="bottom">Description</td></tr></thead><tbody><tr><td align="left" valign="top">Context concept</td><td align="left" valign="top">Source context concept to be mapped</td></tr><tr><td align="left" valign="top">SNOMED CT<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup> concept</td><td align="left" valign="top">Target concept identified in SNOMED CT</td></tr><tr><td align="left" valign="top">Concept ID</td><td align="left" valign="top">Unique ID associated with the SNOMED CT concept</td></tr><tr><td align="left" valign="top">Domain</td><td align="left" valign="top">Semantic domain of the SNOMED CT concept</td></tr><tr><td align="left" valign="top">Reviewer ID</td><td align="left" valign="top">Identifier of the reviewer who performed the mapping</td></tr><tr><td align="left" valign="top">Date</td><td align="left" valign="top">Date on which the mapping was conducted</td></tr><tr><td align="left" valign="top">Equivalence status</td><td align="left" valign="top">Degree of semantic correspondence between context concept and SNOMED CT concept</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>SNOMED CT: Systematized Nomenclature of Medicine&#x2014;Clinical Terms.</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-3-3"><title>Step 2: Exploratory Mapping Using SNOMED CT</title><p>In the second step, an exploratory semantic search of the SNOMED CT hierarchy was conducted to align the context factors with existing SNOMED CT concepts. Each term was manually queried using the SNOMED CT Browser [<xref ref-type="bibr" rid="ref29">29</xref>]. The mapping was based on the SNOMED CT UK Edition (release v20250409), which includes the full content of the International Edition as well as UK-specific extensions. The use of the UK Edition ensured comprehensive coverage while allowing access to additional context-relevant concepts not available in the International Edition alone. Each category was assessed individually by systematically exploring parent and child concepts within the SNOMED CT hierarchy. This hierarchical exploration was used to evaluate both direct matches and semantically related concepts within the broader ontological context. A context concept was classified as &#x201C;mapped&#x201D; if at least one of the 4 predefined criteria in <xref ref-type="table" rid="table2">Table 2</xref> was met. Where more than one potentially relevant concept was identified, the concept with the highest semantic correspondence was selected. If none of these criteria was met, no valid correspondence was assumed, and the context concept was classified as &#x201C;not mapped&#x201D; (not representable in SNOMED CT).</p><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Mapping decision criteria.</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Criterion</td><td align="left" valign="bottom">Definition</td></tr></thead><tbody><tr><td align="left" valign="top">Lexical correspondence</td><td align="left" valign="top">A SNOMED CT<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup> concept carried a designation identical to that of the context concept.</td></tr><tr><td align="left" valign="top">Synonym correspondence</td><td align="left" valign="top">The context concept matched a synonym or alternative designation formally recorded for a SNOMED CT concept.</td></tr><tr><td align="left" valign="top">Conceptual correspondence</td><td align="left" valign="top">The designations differed lexically, but a SNOMED CT concept was judged to denote the same underlying concept.</td></tr><tr><td align="left" valign="top">Hierarchical correspondence</td><td align="left" valign="top">No lexical, synonymous, or conceptual correspondence existed, but a superordinate or subordinate SNOMED CT concept preserved the essential meaning of the context concept.</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>SNOMED CT: Systematized Nomenclature of Medicine&#x2014;Clinical Terms.</p></fn></table-wrap-foot></table-wrap><p>As the SNOMED CT Browser [<xref ref-type="bibr" rid="ref29">29</xref>] returns active concepts by default, the mapping was based on active concepts, and inactive (retired) concepts were not considered. Postcoordination was deliberately not applied, as the aim of this study was to identify potential terminological gaps rather than to bridge them by combining multiple SNOMED CT concepts. All identified concepts were recorded in a Microsoft Excel [<xref ref-type="bibr" rid="ref27">27</xref>] mapping table along with their concept ID, domain, and subtype. Context categories for which no correspondence was found were classified as not representable in SNOMED CT. To visualize the mapping results, Sankey diagrams were created using SankeyMATIC [<xref ref-type="bibr" rid="ref30">30</xref>].</p></sec><sec id="s2-3-4"><title>Step 3: Assessment of Semantic Coverage</title><p>For all mapped categories, an equivalence status was subsequently assigned to characterize the degree of semantic correspondence between the original category (source concept) and the assigned SNOMED CT concept (target concept). This step served as the primary analytical mechanism for evaluating semantic coverage and mapping quality beyond binary match/nonmatch decisions. Classification was performed in accordance with the definitions implemented in Usagi (version 1.4+) [<xref ref-type="bibr" rid="ref31">31</xref>], which are based on Health Level Seven International (HL7) specifications for conceptual equivalence [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>]. The semantic correspondence between source and target concepts was classified using 6 predefined equivalence levels, namely, equal, equivalent, wider, narrower, inexact, and unmatched, with their formal definitions provided in <xref ref-type="table" rid="table3">Table 3</xref>. Among these levels, equal, equivalent, wider, narrower, and inexact differentiate the degree of semantic correspondence between an identified source and target pair, whereas unmatched denotes the absence of a suitable target concept.</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Equivalence definition<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup>.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Equivalence level</td><td align="left" valign="bottom">Definition</td></tr></thead><tbody><tr><td align="left" valign="top">Equal</td><td align="left" valign="top">The concepts are exactly the same (ie, intensionally identical).</td></tr><tr><td align="left" valign="top">Equivalent</td><td align="left" valign="top">The concepts mean the same thing (ie, extensionally identical).</td></tr><tr><td align="left" valign="top">Wider</td><td align="left" valign="top">The target contains more information than the source.</td></tr><tr><td align="left" valign="top">Narrower</td><td align="left" valign="top">The target contains less information than the source.</td></tr><tr><td align="left" valign="top">Inexact</td><td align="left" valign="top">The target overlaps with the source, but both source and target cover additional meaning.</td></tr><tr><td align="left" valign="top">Unmatched</td><td align="left" valign="top">There is no match for this concept in the target code system.</td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>The equivalence definitions were adapted from Usagi (version 1.4+) [<xref ref-type="bibr" rid="ref31">31</xref>].</p></fn></table-wrap-foot></table-wrap></sec><sec id="s2-3-5"><title>Step 4: Validation of the Mapping</title><p>To ensure quality and validate the mapping results, an independent expert review was conducted. For validation, a second reviewer with demonstrated expertise in semantic interoperability and extensive experience in terminological mapping independently performed a separate mapping of all categories and assessed the corresponding equivalence levels. The results of both reviewers were systematically compared to verify consistency in concept assignment and equivalence classification. Initial interreviewer agreement was quantified descriptively as the proportion of context concepts for which both reviewers independently made the same decision, calculated separately for concept assignment and for equivalence-level classification. Any discrepancies were addressed through a structured consensus process. A discrepancy was defined as any case in which the 2 reviewers assigned a different SNOMED CT concept or a different equivalence level to the same context concept. All discrepant cases were reviewed jointly by both reviewers in a consensus meeting, in which the reviewers revisited the source concept, the candidate SNOMED CT concepts, the mapping decision criteria (<xref ref-type="table" rid="table2">Table 2</xref>), and the equivalence definitions (<xref ref-type="table" rid="table3">Table 3</xref>), before agreeing on a final concept assignment and equivalence classification. All discrepancies were resolved through discussion, and no third-party arbitration was required. The combination of independent dual mapping, standardized equivalence criteria, and structured consensus discussion strengthened the robustness and reproducibility of the results.</p></sec><sec id="s2-3-6"><title>Management of Concepts Not Represented in SNOMED CT</title><p>For context categories for which no suitable concept could be identified in SNOMED CT, an additional search was conducted using Athena [<xref ref-type="bibr" rid="ref34">34</xref>]. Athena [<xref ref-type="bibr" rid="ref34">34</xref>] is a searchable vocabulary platform provided by Observational Health Data Sciences and Informatics (OHDSI) that enables cross-vocabulary concept identification across multiple standardized terminologies (eg, MeSH, LOINC, and Nebraska Lexicon). This supplementary step was included to assess whether nonrepresentability was specific to SNOMED CT or reflected a broader lack of terminological coverage. Each term was manually entered into the Athena [<xref ref-type="bibr" rid="ref34">34</xref>] search interface and screened for potentially corresponding concepts. Identified candidate concepts were then documented in accordance with the SSSOM guidelines [<xref ref-type="bibr" rid="ref28">28</xref>], as previously described in Step 2, and assessed using the same predefined equivalence levels (<xref ref-type="table" rid="table3">Table 3</xref>) applied to the SNOMED CT mappings to reflect the degree of semantic correspondence.</p></sec></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Dataset Description and Structuring</title><p>The data basis for the terminological mapping consisted of the structured context concepts derived from the preceding work. These concepts were organized within a 3-level hierarchical structure in Microsoft Excel [<xref ref-type="bibr" rid="ref27">27</xref>]. The first level consisted of the entity level, encompassing 6 overarching context concepts: patient, physician, institution, patient&#x2019;s family, peers, and disease treatment. Each entity represents a distinct context concept at the highest level of the hierarchy. At the second hierarchical level, a total of 101 categories were assigned across the entities, while the third level comprised 82 subcategories. For example, the patient entity represents a context concept at the first hierarchical level, demographic characteristics constitute a category at the second level, and gender represents a corresponding subcategory at the third level. Similarly, within the physician entity, personal state constitutes a category at the second hierarchical level, with workload represented as a corresponding subcategory at the third level. To illustrate the thematic scope of the analyzed dataset and to support the interpretation of the subsequent entity-specific mapping results, <xref ref-type="table" rid="table4">Table 4</xref> provides representative context concepts for each of the 6 entities, together with the number of concepts analyzed per entity.</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Representative context concepts per entity (illustrative excerpt)<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">Entity (N=189)</td><td align="left" valign="bottom">Representative context concepts (with subcategories)</td></tr></thead><tbody><tr><td align="left" valign="top">Patient (n=75)</td><td align="left" valign="top">Demographics (eg, age, gender, ethnicity, socioeconomic status, and insurance), health status (eg, disease condition, comorbidities, and quality of life), wants and needs (eg, preferences and expectations), history (eg, medical history and social history), behavior (eg, compliance)</td></tr><tr><td align="left" valign="top">Physician (n=55)</td><td align="left" valign="top">Demographics (eg, age, education), work-related (eg, position and profession), personal states (eg, workload, stress, and sleepiness), emotions and feelings (eg, trust and confidence), perception (eg, perceived risks and benefits), decision-making (biases)</td></tr><tr><td align="left" valign="top">Patient&#x2019;s family (n=18)</td><td align="left" valign="top">Demographics, abilities, knowledge, emotions and feelings, attitude, behavior (family support), decision-making, time constraints, and parental absence</td></tr><tr><td align="left" valign="top">Institution (n=14)</td><td align="left" valign="top">Hospital factors (hospital structure, clinical load, resources, legal, and finance), culture, guidelines, scope of practice, management, and geographics</td></tr><tr><td align="left" valign="top">Peers (n=16)</td><td align="left" valign="top">Opinion, perception, experience, involvement, team structure, interaction (communication), decision-making, and behavior (support)</td></tr><tr><td align="left" valign="top">Disease treatment (n=11)</td><td align="left" valign="top">Severity, complexity, course, evidence, treatment options, treatment costs, treatment time, and history</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>The entity column corresponds to level 1 (overarching context concepts). In the right-hand column, the unenclosed terms denote level 2 categories, while the terms in parentheses denote the associated level 3 subcategories, shown where available.</p></fn></table-wrap-foot></table-wrap><p>Due to the relational structure of the context model, some context concepts (eg, demographics) may be associated with multiple entities and appear at different hierarchical and relational levels. A detailed overview of the complete hierarchical structure is provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p></sec><sec id="s3-2"><title>Results of Steps 2 to 4: Mapping, Coverage, and Validation</title><p>The described hierarchical organization of context concepts served as the empirical basis for the subsequent semantic mapping to SNOMED CT. Overall, 189 context concepts across all 3 hierarchical levels were included in the analysis.</p><p>First, the results of the 2 reviewers prior to consensus were analyzed. This analysis showed an agreement on concept assignment of 68.8% (130/189); for these concepts, the assigned equivalence level agreed in 89.2% (116/130) of cases. All remaining discrepancies were subsequently resolved through the consensus process. The mapping results reported below refer to the consolidated mapping for all 189 context concepts examined. Of these, 154 (81.5%) concepts were successfully mapped to an existing SNOMED CT concept, whereas 35 (18.5%) concepts could not be assigned a suitable terminological correspondence. A complete list of all mapped context concepts, including assigned SNOMED CT identifiers, domains, and equivalence classifications, is provided in <xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>.</p><p>For each context concept, semantic correspondence with the assigned SNOMED CT concept was evaluated using predefined equivalence levels. Of all 189 analyzed context concepts, 36% (n=68) were classified as equal; for example, &#x201C;abilities&#x201D; was classified as equal to &#x201C;14671000000105 | Abilities,&#x201D; and 21.2% (n=40) as equivalent, as in the case of &#x201C;comorbidities&#x201D; assigned to &#x201C;398192003 | Co-morbid conditions.&#x201D; Furthermore, 8.5% (n=16) were classified as wider, exemplified by &#x201C;social history&#x201D; and &#x201C;160476009 | Social / personal history observable,&#x201D; 13.8% (n=26) as narrower, as in &#x201C;performance status&#x201D; and &#x201C;278844005 | General clinical state,&#x201D; and 2.1% (n=4) as inexact, exemplified by &#x201C;interests&#x201D; and &#x201C;225469004 | Interested.&#x201D; The remaining 18.5% (n=35) of context concepts were classified as unmatched, indicating the absence of a suitable SNOMED CT concept.</p><p>Mapped context concepts were assigned to 11 distinct SNOMED CT domains. <xref ref-type="table" rid="table5">Table 5</xref> summarizes the domain distribution of the mapped 189 context concepts. The largest proportion was assigned to the domain observable entity (n=62, 32.8%), followed by qualifier value (n=30, 15.9%) and clinical finding (n=19, 10%). Additional domains represented at lower frequencies included procedure, situation with explicit context, social context, environment or geographical location, person, physical object, record artifact, and event. Context concepts without a suitable SNOMED CT correspondence were categorized as not applicable.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Distribution of all analyzed context concepts (N=189) across SNOMED CT<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup> domains, including definitions, absolute values (n), and relative (%) frequencies<sup><xref ref-type="table-fn" rid="table5fn2">b</xref></sup>.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Domain</td><td align="left" valign="bottom">Definition of domain according to SNOMED CT model [<xref ref-type="bibr" rid="ref35">35</xref>]</td><td align="left" valign="bottom">Value, n (%)</td></tr></thead><tbody><tr><td align="left" valign="top">Observable entity</td><td align="left" valign="top">Questions or assessments which can produce an answer or result</td><td align="left" valign="top">62 (32.80)</td></tr><tr><td align="left" valign="top">Not applicable</td><td align="left" valign="top">Context concepts for which no suitable SNOMED CT mapping could be identified</td><td align="left" valign="top">35 (18.52)</td></tr><tr><td align="left" valign="top">Qualifier value</td><td align="left" valign="top">Values for some SNOMED CT attributes, where those values are not subtypes of other top-level concepts</td><td align="left" valign="top">30 (15.87)</td></tr><tr><td align="left" valign="top">Clinical finding</td><td align="left" valign="top">Result of a clinical observation, assessment, or judgment and includes normal and abnormal clinical states</td><td align="left" valign="top">19 (10.05)</td></tr><tr><td align="left" valign="top">Social context</td><td align="left" valign="top">Social conditions and circumstances significant to health care</td><td align="left" valign="top">17 (8.99)</td></tr><tr><td align="left" valign="top">Situation with explicit context</td><td align="left" valign="top">Concepts in which the clinical context is specified as part of the definition of the concept itself</td><td align="left" valign="top">7 (3.70)</td></tr><tr><td align="left" valign="top">Record artifact</td><td align="left" valign="top">Content created for the purpose of providing other people with information about record events or states of affairs</td><td align="left" valign="top">6 (3.17)</td></tr><tr><td align="left" valign="top">Environment</td><td align="left" valign="top">Types of environments as well as named locations such as countries, states, regions, or other geographic areas</td><td align="left" valign="top">5 (2.65)</td></tr><tr><td align="left" valign="top">SNOMED CT model component</td><td align="left" valign="top">Technical metadata supporting the SNOMED CT release</td><td align="left" valign="top">5 (2.65)</td></tr><tr><td align="left" valign="top">Physical object</td><td align="left" valign="top">Natural or human-made physical objects</td><td align="left" valign="top">1 (0.53)</td></tr><tr><td align="left" valign="top">Procedure</td><td align="left" valign="top">Activities performed in the provision of health care</td><td align="left" valign="top">1 (0.53)</td></tr><tr><td align="left" valign="top">Special concept</td><td align="left" valign="top">Concepts outside the formal description logic of the concept model of the terminology, but which may be useful for specific use cases</td><td align="left" valign="top">1 (0.53)</td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>SNOMED CT: Systematized Nomenclature of Medicine&#x2014;Clinical Terms.</p></fn><fn id="table5fn2"><p><sup>b</sup>Context concepts without a suitable SNOMED CT correspondence are reported as not applicable. Relative frequencies are based on all analyzed context concepts (N=189).</p></fn></table-wrap-foot></table-wrap><p>To address the second research question (&#x201C;What differences can be observed in the terminological coverage of context factors within SNOMED CT?&#x201D;), the context concepts were further analyzed. To assess whether terminological coverage varied with conceptual granularity, mapping outcomes were first analyzed, stratified by hierarchical level. Mapping rates were largely comparable across the 3 levels: at the entity level, 83.3% (5/6) of concepts were successfully mapped to SNOMED CT, compared to 80.2% (81/101) at the category level and 82.9% (68/82) at the subcategory level. A more differentiated picture emerged when mapping outcomes were stratified by the 6 entities of the context framework (patient, physician, institution, patient&#x2019;s family, peers, and disease treatment). This entity-based analysis revealed marked differences in terminological coverage. Although patient-related context concepts (n=75) were largely mappable to SNOMED CT (n=70, 93.3%), only 50% (n=7) of institution-related context concepts (n=14) were successfully mapped. The relative distribution of mapped and unmapped concepts across entities is shown in <xref ref-type="fig" rid="figure2">Figure 2</xref>.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>Proportion of mapped and not mapped context concepts per entity, based on whether a suitable Systematized Nomenclature of Medicine&#x2014;Clinical Terms (SNOMED CT) concept could be identified.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e103470_fig02.png"/></fig><p>An entity-specific analysis of equivalence status demonstrated differences in mapping quality across the 6 entities (<xref ref-type="fig" rid="figure3">Figure 3</xref>). Here, the equivalence levels equal, equivalent, wider, narrower, and inexact jointly represent the semantic mapping quality of the mapped concepts, whereas the unmatched equivalence status corresponds to unmapped context concepts. The results indicate that the entities&#x2014;patient, patient&#x2019;s family, and disease treatment&#x2014;showed the highest proportions of equal and equivalent classifications. Mappings associated with the physician entity were distributed more across multiple equivalence categories. The institution and peers entities exhibited the highest proportions of unmatched context concepts. Across all entities, the inexact equivalence status occurred least frequently, while wider and narrower classifications were observed in nearly all entities with varying frequencies.</p><fig position="float" id="figure3"><label>Figure 3.</label><caption><p>Proportion of context concepts per entity according to their semantic mapping quality, differentiated by equivalence level.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e103470_fig03.png"/></fig><p>Subsequently, a domain-specific analysis stratified by entity was performed to examine the allocation of mapped context concepts to SNOMED CT domains. <xref ref-type="fig" rid="figure4">Figure 4</xref> illustrates the distribution of entity-specific context concepts across SNOMED CT domains, with unmapped concepts displayed separately.</p><fig position="float" id="figure4"><label>Figure 4.</label><caption><p>Distribution of context concepts by entity and corresponding Systematized Nomenclature of Medicine&#x2014;Clinical Terms (SNOMED CT) domain.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="medinform_v14i1e103470_fig04.png"/></fig><p>Among mapped patient-related context concepts, 45.7% (32/70) were assigned to the observable entity domain. A similar pattern was observed for mapped physician-related context concepts, with 44.2% (19/43) assigned to the same domain. For context concepts related to the patient&#x2019;s family, 46.7% (7/15) were assigned to the observable entity domain. Peer-related mapped context concepts were likewise most frequently assigned to this domain (4/10, 40%). In contrast, institution-related mapped context concepts were most frequently assigned to the qualifier value domain (3/7, 42.9%). The same domain predominated among mapped disease treatment&#x2013;related context concepts, accounting for 33.3% (3/9) of assignments.</p></sec><sec id="s3-3"><title>Concepts Not Represented in SNOMED CT</title><p>In a final analysis step, 35 context concepts not represented in SNOMED CT were cross-referenced with alternative vocabularies using the Athena [<xref ref-type="bibr" rid="ref34">34</xref>] search function. Among these, 65.7% (n=23) were mapped to MeSH concepts, while an additional 28.6% (n=10) were mapped to LOINC concepts. Single context concepts were mapped to the Nebraska Lexicon (n=1) and the UK Biobank (n=1), respectively. Most of these alternative mappings were assigned an equivalence status of inexact (n=12, 34.3%), followed by equivalent (26%, n=9), narrower (14%, n=5), equal (14%, n=5), and wider (11%, n=4). A detailed overview of these results is provided in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>.</p></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Discussion of Results</title><p>The aim of this study was to examine the extent to which empirically identified context factors that influence clinical decision-making can be semantically represented in SNOMED CT. Based on a previously established set of evidence-based context concepts, the present analysis assessed their terminological coverage and semantic correspondence within SNOMED CT using an exploratory manual mapping approach.</p><sec id="s4-1-1"><title>Principal Findings</title><p>The findings of the present analysis show that a large proportion of the identified context concepts (81%) could be terminologically represented in SNOMED CT. However, this coverage rate does not fully reflect the degree of semantic correspondence between the context concepts and their assigned SNOMED CT concepts. While equal and equivalent classifications indicate close semantic correspondence, wider, narrower, and inexact classifications indicate that the source and target concepts differ in scope or meaning. The overall mapping rate should therefore be interpreted as an indicator of terminological coverage rather than evidence of uniform semantic correspondence. This generally supports the suitability of SNOMED CT as a reference terminology for representing context-related factors in clinical decision-making. At the same time, mappings with partial semantic correspondence may require further refinement or additional modeling before they can be operationalized in a specific implementation context. This consideration is particularly relevant for institution-related, peer-related, and social context factors, for which partial semantic correspondence may be insufficient to support reliable system-level decision support. Furthermore, a relevant proportion of concepts (19%) could not be adequately represented in SNOMED CT, indicating the presence of persisting terminological gaps. The findings therefore suggest that evidence-based context factors of clinical decision processes are, in principle, amenable to formal modeling, but are not yet fully covered by SNOMED CT. Incomplete mapping rates have also been reported in other studies using comparable manual terminology-mapping approaches [<xref ref-type="bibr" rid="ref36">36</xref>-<xref ref-type="bibr" rid="ref38">38</xref>]. For example, Thandi et al [<xref ref-type="bibr" rid="ref38">38</xref>] reported an unmatched rate of 11% in a manual mapping of eCGA (electronic Comprehensive Geriatric Assessment) elements to SNOMED CT, while Tavakoli et al [<xref ref-type="bibr" rid="ref37">37</xref>] reported a coverage of 82% for ophthalmological infection and trauma concepts. The findings of the present study therefore fall within a range comparable to those reported in published mapping studies and further underline that even in established clinical domains, complete terminological representation in SNOMED CT cannot be assumed.</p></sec><sec id="s4-1-2"><title>Entity-Specific Differences in Terminological Coverage</title><p>With regard to the entity-specific analysis, the results revealed marked differences in representability across context concepts related to the 6 investigated entities: patient, physician, patient&#x2019;s family, institution, peers, and disease treatment. Since mapping outcomes were largely consistent across the 3 hierarchical levels (entities, categories, and subcategories), these differences can be attributed to characteristics of the entities themselves rather than to the conceptual granularity of the underlying concepts, supporting the interpretation of entity-specific terminological coverage as a substantive finding. In particular, coverage was highest for patient-related context concepts (mapping rate: 93%) and disease treatment&#x2013;related context concepts (mapping rate: 82%), whereas the coverage of institution-related context concepts was substantially lower (50%). These findings underscore the clinical and patient-centered orientation of SNOMED CT and are consistent with its primary practical use as a standard for electronic health records (EHRs), where data are collected primarily to support patient care [<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]. Consistent with the overall representability of patient-centered context concepts, their semantic fit to SNOMED CT concepts was also comparatively strong, with 40% classified as equal and 29% as equivalent, whereas institution-related concepts showed substantially lower semantic alignment (29% equal and 9% equivalent). Taken together, the findings regarding the semantic fit between evidence-based context factors derived from the literature and SNOMED CT concepts further highlight the strong suitability of SNOMED CT for representing clinical, patient-centered information. By contrast, physician-related context information and information concerning the patient&#x2019;s family showed a more heterogeneous distribution across equivalence levels, suggesting that physician states, working conditions, and family-related influences are not yet adequately captured in SNOMED CT. In addition, the high proportion of unmatched assignments among intention-related and peer-related context factors points to a systematic weakness in the representation of organizational and social contexts. This again reflects the strong focus of SNOMED CT as a standard for clinical information systems such as EHRs and its ability to effectively represent the types of data that are routinely captured in such systems [<xref ref-type="bibr" rid="ref41">41</xref>], where information is documented primarily for patient care purposes [<xref ref-type="bibr" rid="ref40">40</xref>]. However, contextual factors that shape clinical decision-making are often not documented in EHRs or other health information systems, meaning that the clinical reality of medical decision-making is not fully represented in current digital infrastructures [<xref ref-type="bibr" rid="ref42">42</xref>-<xref ref-type="bibr" rid="ref44">44</xref>]</p></sec><sec id="s4-1-3"><title>Domain-Specific Patterns Across Entities</title><p>With regard to the domains of the identified SNOMED CT concepts, a clear predominance of the observable entity domain was found for context information related to the patient, physician, patient&#x2019;s family, and peers. This pattern suggests that, within SNOMED CT, context is frequently represented as an observable characteristic or state. In contrast, institution-related and disease treatment&#x2013;related concepts were most often assigned to the qualifier value domain, indicating that these context-related information elements are primarily modeled as modifying attributes rather than as independent clinical concepts [<xref ref-type="bibr" rid="ref45">45</xref>]. By comparison, only a small proportion of concepts fell within the situation with explicit context domain, suggesting that the potential of this subhierarchy for representing contextual information has not yet been fully realized. However, this heterogeneity in concept representation should not be interpreted solely as a limitation of the terminology itself. Rather, it reflects the more fundamental challenge of defining and formally representing context as a multidimensional, dynamic, and situation-dependent construct [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref46">46</xref>]. At the same time, a more consistent domain assignment of context-related concepts within SNOMED CT could improve the conceptual clarity, structural coherence, and retrievability of contextual information within the terminology [<xref ref-type="bibr" rid="ref47">47</xref>].</p></sec><sec id="s4-1-4"><title>Interpretation of Nonmappable Context Concepts</title><p>Concepts that could not be represented in SNOMED CT were identified in other vocabularies, most notably MeSH (23/35, 65.7%) and, to a lesser extent, LOINC (10/35, 28.6%). This finding indicates that context-related information is, in principle, terminologically representable, but remains fragmented across multiple vocabularies. The high proportion of MeSH concepts suggests that a substantial share of the identified context factors is located primarily at a conceptual or knowledge-based level, which can plausibly be explained by the underlying data source, as the mapped context factors were extracted from the scientific literature. Whereas MeSH is designed to structure and index biomedical literature [<xref ref-type="bibr" rid="ref48">48</xref>], SNOMED CT is intended for the formal representation of clinical information in care settings [<xref ref-type="bibr" rid="ref49">49</xref>]. The distribution of context-related concepts across multiple vocabularies should therefore be understood as a reflection of this functional specialization. At the same time, however, it results in a fragmentation of relevant information that complicates consistent semantic integration and thus constitutes a major challenge for both interoperability [<xref ref-type="bibr" rid="ref37">37</xref>] and effective data management [<xref ref-type="bibr" rid="ref41">41</xref>]. Accordingly, the identification of a candidate correspondence in MeSH, LOINC, or another vocabulary should be interpreted as evidence of conceptual availability rather than direct operational readiness. Depending on the intended use case, further semantic modeling, terminology binding, and specification of the relevant data elements may be required before such concepts can be incorporated into EHR-based CDSSs.</p></sec></sec><sec id="s4-2"><title>Implications</title><p>Overall, these findings highlight both the limitations of existing terminologies and the need for more formal representations of contextual information in clinical decision support. In particular, context factors beyond traditional clinical parameters require explicit modeling to address persistent limitations of CDSSs, including the insufficient consideration of clinical workflows and organizational contexts [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref50">50</xref>]. Previous studies have shown that the standardized capture of contextual information remains limited [<xref ref-type="bibr" rid="ref51">51</xref>,<xref ref-type="bibr" rid="ref52">52</xref>], partly because such information often remains implicit, is not formally documented [<xref ref-type="bibr" rid="ref53">53</xref>,<xref ref-type="bibr" rid="ref54">54</xref>], or is recorded in free-text fields that hinder automated processing [<xref ref-type="bibr" rid="ref55">55</xref>]. The results of this study suggest that a substantial subset of these context factors can be represented using existing terminological structures and may provide a basis for their integration into CDSS logic. For example, contextual information such as physician workload, institutional resources, or patient-related social factors could be used to modulate system behavior, for instance, by adapting alert frequency, prioritizing recommendations, or tailoring decision support to specific situational conditions. To illustrate this more concretely, consider a medication-safety alert triggered by a potentially nephrotoxic drug combination in a patient with declining renal function. Drawing on the local formulary, the system could recommend a renally safer alternative that is actually stocked at the institution rather than one it does not carry. Drawing on the on-site availability of services, it could adapt the suggested follow-up, proposing therapeutic drug monitoring or a nephrology consultation where these are available, or prompting timely referral where they are not. Physician workload, in turn, derived from routinely available signals such as the active patient census, could be used to adapt alert frequency by deferring low-severity advisories during high-workload periods, while high-priority safety alerts remain unaffected. For a CDSS to make meaningful use of contextual information, these data must therefore be captured in a standardized and interoperable way. In this regard, the integration of terminologies into EHRs appears promising [<xref ref-type="bibr" rid="ref52">52</xref>], but this requires extending existing terminologies to incorporate contextual dimensions [<xref ref-type="bibr" rid="ref56">56</xref>]. The present findings provide an empirically grounded basis for such extensions and for the development of formal context ontologies and semantically coherent, context-sensitive information models. More broadly, they contribute to ongoing efforts to formally represent clinical decision logic for use in digital support systems.</p></sec><sec id="s4-3"><title>Limitations</title><p>Several limitations should be considered when interpreting these findings. The analysis was restricted to SNOMED CT and therefore does not allow conclusions about the representability of the identified context concepts in other terminologies. In addition, the mapped concepts were derived from literature-based context factors rather than real-world clinical data and may therefore not fully reflect the breadth of contextual information used in routine care. Although measures such as dual-independent mapping and consensus procedures were applied, some degree of subjectivity in the mapping process cannot be completely excluded. The practical applicability of the mapped concepts in operational CDSSs or interoperable health information systems was not evaluated, meaning that the results inform terminological representability rather than clinical utility or implementation performance. This study should therefore be understood as an exploratory mapping rather than an implementation proposal. Finally, the findings depend on the specific SNOMED CT edition and release used, and reported coverage rates may differ in jurisdictions without comparable national extensions. Despite expert review, some degree of subjectivity in the manual mapping process remains unavoidable.</p></sec><sec id="s4-4"><title>Future Research Directions</title><p>Future research should build on these results by moving from terminological representability toward implementation-oriented modeling of contextual information. This includes the development of formal context ontologies, context-sensitive information models, and strategies for the structured capture of contextual factors in clinical systems. In this context, future studies should assess whether concepts with partial or no correspondence can be more precisely represented through SNOMED CT postcoordination or require new concept authoring. In addition, further studies are needed to investigate which contextual factors are actually documented or can feasibly be captured in routine care, and how such information can be linked to decision support logic in a clinically meaningful way. It will also be important to examine how contextual concepts are represented across different SNOMED CT editions and how they can be consistently integrated across terminologies, ontologies, and information models in order to support semantic interoperability beyond isolated concept mapping. Finally, evaluation studies in real-world settings are required to determine whether improved formalization of contextual information can contribute to more relevant, acceptable, and practice-oriented CDSSs.</p></sec><sec id="s4-5"><title>Conclusions</title><p>This study shows that a substantial proportion of empirically identified context factors influencing clinical decision-making can be linked to existing concepts in SNOMED CT. At the same time, the observed gaps in coverage, particularly for organizational and social context factors, indicate that current terminological structures do not yet fully reflect the contextual complexity of clinical decision-making. The findings therefore support the view that SNOMED CT can provide an important terminological basis for formalizing contextual information, while also highlighting the need for complementary work on semantic modeling, terminology development, and implementation-oriented context representation. Advancing these areas will be important for enabling more context-sensitive and semantically robust digital decision support.</p></sec></sec></body><back><notes><sec><title>Funding</title><p>The research work was carried out as part of the junior research group "CDS2USE&#x2014;Prospective user-centered design of clinical decision support systems in the context of personalized medicine," funded by the Federal Ministry of Research, Technology and Space (BMFTR, grant 01ZZ2002).</p></sec><sec><title>Data Availability</title><p>The authors declare that the data supporting the findings of this review are available within the paper.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: KS</p><p>Data curation: KS</p><p>Formal analysis: KS</p><p>Funding acquisition: MS</p><p>Investigation: KS, EH</p><p>Methodology: KS, EH</p><p>Resources: KS</p><p>Supervision: MS</p><p>Validation: KS</p><p>Visualization: KS</p><p>Writing &#x2013; original draft: KS</p><p>Writing &#x2013; review &#x0026; editing: EH, MS</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">CDSS</term><def><p>clinical decision support system</p></def></def-item><def-item><term id="abb2">EHR</term><def><p>electronic health record</p></def></def-item><def-item><term id="abb3">HL7</term><def><p>Health Level Seven International</p></def></def-item><def-item><term id="abb4">ICD</term><def><p>International Classification of Diseases</p></def></def-item><def-item><term id="abb5">LOINC</term><def><p>Logical Observation Identifiers Names and Codes</p></def></def-item><def-item><term id="abb6">OHDSI</term><def><p>Observational Health Data Sciences and Informatics</p></def></def-item><def-item><term id="abb7">SNOMED CT</term><def><p>Systematized Nomenclature of Medicine&#x2014;Clinical Terms</p></def></def-item><def-item><term id="abb8">SSSOM</term><def><p>Simple Standard for Sharing Ontology Mappings</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Croskerry</surname><given-names>P</given-names> </name><name name-style="western"><surname>Campbell</surname><given-names>SG</given-names> </name><name name-style="western"><surname>Petrie</surname><given-names>DA</given-names> </name></person-group><article-title>The challenge of cognitive science for medical diagnosis</article-title><source>Cogn Res Princ Implic</source><year>2023</year><month>02</month><day>9</day><volume>8</volume><issue>1</issue><fpage>13</fpage><pub-id pub-id-type="doi">10.1186/s41235-022-00460-z</pub-id><pub-id pub-id-type="medline">36759370</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>Tiffen</surname><given-names>J</given-names> </name><name name-style="western"><surname>Corbridge</surname><given-names>SJ</given-names> </name><name name-style="western"><surname>Slimmer</surname><given-names>L</given-names> </name></person-group><article-title>Enhancing clinical decision making: development of a contiguous definition and conceptual framework</article-title><source>J Prof Nurs</source><year>2014</year><volume>30</volume><issue>5</issue><fpage>399</fpage><lpage>405</lpage><pub-id pub-id-type="doi">10.1016/j.profnurs.2014.01.006</pub-id><pub-id pub-id-type="medline">25223288</pub-id></nlm-citation></ref><ref id="ref3"><label>3</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>McCarthy</surname><given-names>MC</given-names> </name><name name-style="western"><surname>De Abreu Lourenco</surname><given-names>R</given-names> </name><name name-style="western"><surname>McMillan</surname><given-names>LJ</given-names> </name><name name-style="western"><surname>Meshcheriakova</surname><given-names>E</given-names> </name><name name-style="western"><surname>Cao</surname><given-names>A</given-names> </name><name name-style="western"><surname>Gillam</surname><given-names>L</given-names> </name></person-group><article-title>Finding out what matters in decision-making related to genomics and personalized medicine in pediatric oncology: developing attributes to include in a discrete choice experiment</article-title><source>Patient</source><year>2020</year><month>06</month><volume>13</volume><issue>3</issue><fpage>347</fpage><lpage>361</lpage><pub-id pub-id-type="doi">10.1007/s40271-020-00411-0</pub-id><pub-id pub-id-type="medline">32037479</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hajjaj</surname><given-names>FM</given-names> </name><name name-style="western"><surname>Salek</surname><given-names>MS</given-names> </name><name name-style="western"><surname>Basra</surname><given-names>MKA</given-names> </name><name name-style="western"><surname>Finlay</surname><given-names>AY</given-names> </name></person-group><article-title>Nonclinical influences, beyond diagnosis and severity, on clinical decision making in dermatology: understanding the gap between guidelines and practice</article-title><source>Br J Dermatol</source><year>2010</year><month>10</month><volume>163</volume><issue>4</issue><fpage>789</fpage><lpage>799</lpage><pub-id pub-id-type="doi">10.1111/j.1365-2133.2010.09868.x</pub-id><pub-id pub-id-type="medline">20854402</pub-id></nlm-citation></ref><ref id="ref5"><label>5</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Nugraha</surname><given-names>B</given-names> </name><name name-style="western"><surname>Engen</surname><given-names>G</given-names> </name><name name-style="western"><surname>Roe</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Development of a minimum reporting set of contextual factors for rehabilitation studies: a Delphi study</article-title><source>J Rehabil Med</source><year>2022</year><month>05</month><day>11</day><volume>54</volume><fpage>jrm00265</fpage><pub-id pub-id-type="doi">10.2340/jrm.v54.2033</pub-id><pub-id pub-id-type="medline">35174867</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>Whelehan</surname><given-names>DF</given-names> </name><name name-style="western"><surname>Conlon</surname><given-names>KC</given-names> </name><name name-style="western"><surname>Ridgway</surname><given-names>PF</given-names> </name></person-group><article-title>If in doubt don&#x2019;t act out! Exploring behaviours in clinical decision making by general surgeons towards surgical procedures</article-title><source>World J Surg</source><year>2021</year><month>04</month><volume>45</volume><issue>4</issue><fpage>1055</fpage><lpage>1065</lpage><pub-id pub-id-type="doi">10.1007/s00268-020-05888-2</pub-id><pub-id pub-id-type="medline">33392706</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>Williams</surname><given-names>BA</given-names> </name><name name-style="western"><surname>Phillips</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Matthias</surname><given-names>RC</given-names> </name><name name-style="western"><surname>Blakemore</surname><given-names>LC</given-names> </name></person-group><article-title>Buckling down on torus fractures&#x2014;assessing treatment preferences and perceived management barriers at a single institution</article-title><source>Iowa Orthop J</source><year>2020</year><volume>40</volume><issue>2</issue><fpage>12</fpage><lpage>20</lpage><pub-id pub-id-type="medline">33633503</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>Henshall</surname><given-names>C</given-names> </name><name name-style="western"><surname>Dawson</surname><given-names>P</given-names> </name><name name-style="western"><surname>Rahman</surname><given-names>N</given-names> </name><etal/></person-group><article-title>Understanding clinical decision-making in mesothelioma care: a mixed methods study</article-title><source>BMJ Open Respir Res</source><year>2022</year><month>07</month><volume>9</volume><issue>1</issue><fpage>e001312</fpage><pub-id pub-id-type="doi">10.1136/bmjresp-2022-001312</pub-id><pub-id pub-id-type="medline">35840292</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>Schrans</surname><given-names>D</given-names> </name><name name-style="western"><surname>Avonts</surname><given-names>D</given-names> </name><name name-style="western"><surname>Christiaens</surname><given-names>T</given-names> </name><etal/></person-group><article-title>The search for person-related information in general practice: a qualitative study</article-title><source>Fam Pract</source><year>2016</year><month>02</month><volume>33</volume><issue>1</issue><fpage>95</fpage><lpage>99</lpage><pub-id pub-id-type="doi">10.1093/fampra/cmv099</pub-id><pub-id pub-id-type="medline">26787770</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>Schuler</surname><given-names>K</given-names> </name><name name-style="western"><surname>Jung</surname><given-names>IC</given-names> </name><name name-style="western"><surname>Zerlik</surname><given-names>M</given-names> </name><name name-style="western"><surname>Hahn</surname><given-names>W</given-names> </name><name name-style="western"><surname>Sedlmayr</surname><given-names>M</given-names> </name><name name-style="western"><surname>Sedlmayr</surname><given-names>B</given-names> </name></person-group><article-title>Context factors in clinical decision-making: a scoping review</article-title><source>BMC Med Inform Decis Mak</source><year>2025</year><month>03</month><day>17</day><volume>25</volume><issue>1</issue><fpage>133</fpage><pub-id pub-id-type="doi">10.1186/s12911-025-02965-1</pub-id><pub-id pub-id-type="medline">40098142</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>Schmidt</surname><given-names>HG</given-names> </name><name name-style="western"><surname>Norman</surname><given-names>GR</given-names> </name><name name-style="western"><surname>Mamede</surname><given-names>S</given-names> </name><name name-style="western"><surname>Magzoub</surname><given-names>M</given-names> </name></person-group><article-title>The influence of context on diagnostic reasoning: a narrative synthesis of experimental findings</article-title><source>J Eval Clin Pract</source><year>2024</year><month>09</month><volume>30</volume><issue>6</issue><fpage>1091</fpage><lpage>1101</lpage><pub-id pub-id-type="doi">10.1111/jep.14023</pub-id><pub-id pub-id-type="medline">38818694</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Osheroff</surname><given-names>J</given-names> </name><name name-style="western"><surname>Teich</surname><given-names>J</given-names> </name><name name-style="western"><surname>Levick</surname><given-names>D</given-names> </name><etal/></person-group><source>Improving Outcomes with Clinical Decision Support: An Implementer&#x2019;s Guide</source><year>2005</year><publisher-name>Healthcare Information and Management Systems Society (HIMSS)</publisher-name><pub-id pub-id-type="other">9780976127727</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>Sutton</surname><given-names>RT</given-names> </name><name name-style="western"><surname>Pincock</surname><given-names>D</given-names> </name><name name-style="western"><surname>Baumgart</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Sadowski</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Fedorak</surname><given-names>RN</given-names> </name><name name-style="western"><surname>Kroeker</surname><given-names>KI</given-names> </name></person-group><article-title>An overview of clinical decision support systems: benefits, risks, and strategies for success</article-title><source>NPJ Digit Med</source><year>2020</year><volume>3</volume><fpage>17</fpage><pub-id pub-id-type="doi">10.1038/s41746-020-0221-y</pub-id><pub-id pub-id-type="medline">32047862</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>Herr</surname><given-names>TM</given-names> </name><name name-style="western"><surname>Peterson</surname><given-names>JF</given-names> </name><name name-style="western"><surname>Rasmussen</surname><given-names>LV</given-names> </name><name name-style="western"><surname>Caraballo</surname><given-names>PJ</given-names> </name><name name-style="western"><surname>Peissig</surname><given-names>PL</given-names> </name><name name-style="western"><surname>Starren</surname><given-names>JB</given-names> </name></person-group><article-title>Pharmacogenomic clinical decision support design and multi-site process outcomes analysis in the eMERGE network</article-title><source>J Am Med Inform Assoc</source><year>2019</year><month>02</month><day>1</day><volume>26</volume><issue>2</issue><fpage>143</fpage><lpage>148</lpage><pub-id pub-id-type="doi">10.1093/jamia/ocy156</pub-id><pub-id pub-id-type="medline">30590574</pub-id></nlm-citation></ref><ref id="ref15"><label>15</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Khairat</surname><given-names>S</given-names> </name><name name-style="western"><surname>Marc</surname><given-names>D</given-names> </name><name name-style="western"><surname>Crosby</surname><given-names>W</given-names> </name><name name-style="western"><surname>Al Sanousi</surname><given-names>A</given-names> </name></person-group><article-title>Reasons for physicians not adopting clinical decision support systems: critical analysis</article-title><source>JMIR Med Inform</source><year>2018</year><month>04</month><day>18</day><volume>6</volume><issue>2</issue><fpage>e24</fpage><pub-id pub-id-type="doi">10.2196/medinform.8912</pub-id><pub-id pub-id-type="medline">29669706</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Musen</surname><given-names>MA</given-names> </name><name name-style="western"><surname>Middleton</surname><given-names>B</given-names> </name><name name-style="western"><surname>Greenes</surname><given-names>RA</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Shortliffe</surname><given-names>EH</given-names> </name><name name-style="western"><surname>Cimino</surname><given-names>JJ</given-names> </name></person-group><article-title>Clinical decision-support systems</article-title><source>Biomedical Informatics: Computer Applications in Health Care and Biomedicine</source><year>2021</year><publisher-name>Springer</publisher-name><fpage>795</fpage><lpage>840</lpage><pub-id pub-id-type="doi">10.1007/978-3-030-58721-5_24</pub-id></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Abowd</surname><given-names>AD</given-names> </name><name name-style="western"><surname>Dey</surname><given-names>AK</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>PJ</given-names> </name><name name-style="western"><surname>Davies</surname><given-names>N</given-names> </name><name name-style="western"><surname>Smith</surname><given-names>M</given-names> </name><name name-style="western"><surname>Steggles</surname><given-names>P</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Gellersen</surname><given-names>HW</given-names> </name></person-group><article-title>Towards a better understanding of context and context-awareness</article-title><source>Handheld and Ubiquitous Computing First International Symposium, HUC&#x2019;99, Karlsruhe, Germany, September 27-29, 1999, Proceedings</source><year>2001</year><publisher-name>Springer</publisher-name><fpage>304</fpage><lpage>307</lpage><pub-id pub-id-type="doi">10.1007/3-540-48157-5_29</pub-id></nlm-citation></ref><ref id="ref18"><label>18</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Laka</surname><given-names>M</given-names> </name><name name-style="western"><surname>Carter</surname><given-names>D</given-names> </name><name name-style="western"><surname>Milazzo</surname><given-names>A</given-names> </name><name name-style="western"><surname>Merlin</surname><given-names>T</given-names> </name></person-group><article-title>Challenges and opportunities in implementing clinical decision support systems (CDSS) at scale: interviews with Australian policymakers</article-title><source>Health Policy Technol</source><year>2022</year><month>09</month><volume>11</volume><issue>3</issue><fpage>100652</fpage><pub-id pub-id-type="doi">10.1016/j.hlpt.2022.100652</pub-id></nlm-citation></ref><ref id="ref19"><label>19</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Wasylewicz</surname><given-names>ATM</given-names> </name><name name-style="western"><surname>Scheepers-Hoeks</surname><given-names>A</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Kubben</surname><given-names>P</given-names> </name><name name-style="western"><surname>Dumontier</surname><given-names>M</given-names> </name><name name-style="western"><surname>Dekker</surname><given-names>A</given-names> </name></person-group><article-title>Clinical decision support systems</article-title><source>Fundamentals of Clinical Data Science</source><year>2019</year><publisher-name>Springer</publisher-name><fpage>153</fpage><lpage>169</lpage><pub-id pub-id-type="doi">10.1007/978-3-319-99713-1_11</pub-id></nlm-citation></ref><ref id="ref20"><label>20</label><nlm-citation citation-type="web"><article-title>LOINC knowledge base</article-title><source>LOINC</source><access-date>2025-10-13</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://loinc.org/kb/">https://loinc.org/kb/</ext-link></comment></nlm-citation></ref><ref id="ref21"><label>21</label><nlm-citation citation-type="web"><article-title>International Classification of Diseases 11th Revision (ICD-11)</article-title><source>World Health Organization (WHO)</source><year>2019</year><access-date>2025-10-13</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://icd.who.int/en/">https://icd.who.int/en/</ext-link></comment></nlm-citation></ref><ref id="ref22"><label>22</label><nlm-citation citation-type="web"><article-title>SNOMED CT and context</article-title><source>SNOMED International</source><year>2025</year><month>09</month><day>16</day><access-date>2025-10-13</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/implementation-guides/context-representation-implementation-guide/4-snomed-ct-and-context">https://docs.snomed.org/implementation-guides/context-representation-implementation-guide/4-snomed-ct-and-context</ext-link></comment></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Schuler</surname><given-names>K</given-names> </name><name name-style="western"><surname>Sedlmayr</surname><given-names>M</given-names> </name><name name-style="western"><surname>Sedlmayr</surname><given-names>B</given-names> </name></person-group><article-title>Mapping medical context: workshop-driven clustering of influencing factors on medical decision-making</article-title><source>Stud Health Technol Inform</source><year>2024</year><month>08</month><day>22</day><volume>316</volume><fpage>1754</fpage><lpage>1758</lpage><pub-id pub-id-type="doi">10.3233/SHTI240769</pub-id><pub-id pub-id-type="medline">39176555</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Zimmermann</surname><given-names>A</given-names> </name><name name-style="western"><surname>Lorenz</surname><given-names>A</given-names> </name><name name-style="western"><surname>Oppermann</surname><given-names>R</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Kokinov</surname><given-names>B</given-names> </name><name name-style="western"><surname>Richardson</surname><given-names>DC</given-names> </name><name name-style="western"><surname>Roth-Berghofer</surname><given-names>TR</given-names> </name><name name-style="western"><surname>Vieu</surname><given-names>L</given-names> </name></person-group><article-title>An operational definition of context</article-title><source>Modeling and Using Context</source><year>2007</year><publisher-name>Springer</publisher-name><fpage>558</fpage><lpage>571</lpage><pub-id pub-id-type="doi">10.1007/978-3-540-74255-5_42</pub-id></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Spencer</surname><given-names>D</given-names> </name></person-group><source>Card Sorting: Designing Usable Categories</source><year>2009</year><publisher-name>Rosenfeld Media</publisher-name><pub-id pub-id-type="other">9781933820026</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>Ehrsam</surname><given-names>J</given-names> </name><name name-style="western"><surname>Gaudet-Blavignac</surname><given-names>C</given-names> </name><name name-style="western"><surname>Mattei</surname><given-names>M</given-names> </name><name name-style="western"><surname>Baumann</surname><given-names>M</given-names> </name><name name-style="western"><surname>Lovis</surname><given-names>C</given-names> </name></person-group><article-title>Semantics in action: a guide for representing clinical data elements with SNOMED CT</article-title><source>J Biomed Semantics</source><year>2025</year><month>03</month><day>27</day><volume>16</volume><issue>1</issue><fpage>7</fpage><pub-id pub-id-type="doi">10.1186/s13326-025-00326-5</pub-id><pub-id pub-id-type="medline">40149003</pub-id></nlm-citation></ref><ref id="ref27"><label>27</label><nlm-citation citation-type="web"><article-title>Microsoft Excel [Article in German]</article-title><source>Microsoft</source><access-date>2026-08-20</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.microsoft.com/de-de/microsoft-365/excel">https://www.microsoft.com/de-de/microsoft-365/excel</ext-link></comment></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>Matentzoglu</surname><given-names>N</given-names> </name><name name-style="western"><surname>Balhoff</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Bello</surname><given-names>SM</given-names> </name><etal/></person-group><article-title>A Simple Standard for Sharing Ontological Mappings (SSSOM)</article-title><source>Database (Oxford)</source><year>2022</year><month>05</month><day>25</day><volume>2022</volume><fpage>baac035</fpage><pub-id pub-id-type="doi">10.1093/database/baac035</pub-id><pub-id pub-id-type="medline">35616100</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="web"><source>SNOMED CT Browser</source><access-date>2026-06-03</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://snomedbrowser.org">https://snomedbrowser.org</ext-link></comment></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="web"><person-group person-group-type="author"><name name-style="western"><surname>Bogart</surname><given-names>S</given-names> </name></person-group><source>SankeyMATIC</source><access-date>2026-10-19</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://sankeymatic.com/">https://sankeymatic.com/</ext-link></comment></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="web"><article-title>Using the application functions importing source codes into Usagi</article-title><source>Usagi (OHDSI)</source><access-date>2026-06-03</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://ohdsi.github.io/Usagi/usage.html">https://ohdsi.github.io/Usagi/usage.html</ext-link></comment></nlm-citation></ref><ref id="ref32"><label>32</label><nlm-citation citation-type="web"><article-title>CodeSystem: concept map equivalence code system</article-title><source>HL7 International</source><access-date>2026-03-14</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://build.fhir.org/ig/HL7/fhir-extensions/CodeSystem-concept-map-equivalence.html">https://build.fhir.org/ig/HL7/fhir-extensions/CodeSystem-concept-map-equivalence.html</ext-link></comment></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>Lambert</surname><given-names>A</given-names> </name><name name-style="western"><surname>Castagne</surname><given-names>C</given-names> </name><name name-style="western"><surname>Pau</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Evaluating the statistical utility and information loss in the transformation of a real-world oncology database from CDISC-SDTM to OMOP-CDM</article-title><source>ESMO Real World Data Digit Oncol</source><year>2025</year><month>12</month><volume>11</volume><fpage>100655</fpage><pub-id pub-id-type="doi">10.1016/j.esmorw.2025.100655</pub-id><pub-id pub-id-type="medline">41930302</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="web"><article-title>Search</article-title><source>Athena</source><access-date>2026-02-08</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://athena.ohdsi.org/search-terms/start">https://athena.ohdsi.org/search-terms/start</ext-link></comment></nlm-citation></ref><ref id="ref35"><label>35</label><nlm-citation citation-type="web"><article-title>SNOMED CT concept model</article-title><source>SNOMED International</source><access-date>2026-03-14</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-starter-guide/6-snomed-ct-concept-model">https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-starter-guide/6-snomed-ct-concept-model</ext-link></comment></nlm-citation></ref><ref id="ref36"><label>36</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Schulz</surname><given-names>S</given-names> </name><name name-style="western"><surname>Steffel</surname><given-names>J</given-names> </name><name name-style="western"><surname>Polster</surname><given-names>P</given-names> </name><name name-style="western"><surname>Palchuk</surname><given-names>M</given-names> </name><name name-style="western"><surname>Daumke</surname><given-names>P</given-names> </name></person-group><article-title>Aligning an administrative procedure coding system with SNOMED CT</article-title><access-date>2026-10-15</access-date><conf-name>Proceedings of the Joint Ontology Workshops 2019 Episode V: The Styrian Autumn of Ontology</conf-name><conf-date>Sep 23-25, 2019</conf-date><comment><ext-link ext-link-type="uri" xlink:href="https://ceur-ws.org/Vol-2518/paper-ODLS8.pdf">https://ceur-ws.org/Vol-2518/paper-ODLS8.pdf</ext-link></comment></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>Tavakoli</surname><given-names>K</given-names> </name><name name-style="western"><surname>Kalaw</surname><given-names>FGP</given-names> </name><name name-style="western"><surname>Bhanvadia</surname><given-names>S</given-names> </name><name name-style="western"><surname>Hogarth</surname><given-names>M</given-names> </name><name name-style="western"><surname>Baxter</surname><given-names>SL</given-names> </name></person-group><article-title>Concept coverage analysis of ophthalmic infections and trauma among the standardized medical terminologies SNOMED-CT, ICD-10-CM, and ICD-11</article-title><source>Ophthalmol Sci</source><year>2023</year><month>05</month><volume>3</volume><issue>4</issue><fpage>100337</fpage><pub-id pub-id-type="doi">10.1016/j.xops.2023.100337</pub-id><pub-id pub-id-type="medline">37449050</pub-id></nlm-citation></ref><ref id="ref38"><label>38</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Thandi</surname><given-names>M</given-names> </name><name name-style="western"><surname>Brown</surname><given-names>S</given-names> </name><name name-style="western"><surname>Wong</surname><given-names>ST</given-names> </name></person-group><article-title>Mapping frailty concepts to SNOMED CT</article-title><source>Int J Med Inform</source><year>2021</year><month>05</month><volume>149</volume><fpage>104409</fpage><pub-id pub-id-type="doi">10.1016/j.ijmedinf.2021.104409</pub-id><pub-id pub-id-type="medline">33677397</pub-id></nlm-citation></ref><ref id="ref39"><label>39</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>D</given-names> </name><name name-style="western"><surname>Cornet</surname><given-names>R</given-names> </name><name name-style="western"><surname>Lau</surname><given-names>F</given-names> </name><name name-style="western"><surname>de Keizer</surname><given-names>N</given-names> </name></person-group><article-title>A survey of SNOMED CT implementations</article-title><source>J Biomed Inform</source><year>2013</year><month>02</month><volume>46</volume><issue>1</issue><fpage>87</fpage><lpage>96</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2012.09.006</pub-id><pub-id pub-id-type="medline">23041717</pub-id></nlm-citation></ref><ref id="ref40"><label>40</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Vuokko</surname><given-names>R</given-names> </name><name name-style="western"><surname>Vakkuri</surname><given-names>A</given-names> </name><name name-style="western"><surname>Palojoki</surname><given-names>S</given-names> </name></person-group><article-title>Systematized Nomenclature of Medicine&#x2014;Clinical Terminology (SNOMED CT) clinical use cases in the context of electronic health record systems: systematic literature review</article-title><source>JMIR Med Inform</source><year>2023</year><month>02</month><day>6</day><volume>11</volume><fpage>e43750</fpage><pub-id pub-id-type="doi">10.2196/43750</pub-id><pub-id pub-id-type="medline">36745498</pub-id></nlm-citation></ref><ref id="ref41"><label>41</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="ref42"><label>42</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Ash</surname><given-names>JS</given-names> </name><name name-style="western"><surname>Berg</surname><given-names>M</given-names> </name><name name-style="western"><surname>Coiera</surname><given-names>E</given-names> </name></person-group><article-title>Some unintended consequences of information technology in health care: the nature of patient care information system-related errors</article-title><source>J Am Med Inform Assoc</source><year>2004</year><volume>11</volume><issue>2</issue><fpage>104</fpage><lpage>112</lpage><pub-id pub-id-type="doi">10.1197/jamia.M1471</pub-id><pub-id pub-id-type="medline">14633936</pub-id></nlm-citation></ref><ref id="ref43"><label>43</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Greenhalgh</surname><given-names>T</given-names> </name><name name-style="western"><surname>Hinton</surname><given-names>L</given-names> </name><name name-style="western"><surname>Finlay</surname><given-names>T</given-names> </name><etal/></person-group><article-title>Frameworks for supporting patient and public involvement in research: systematic review and co-design pilot</article-title><source>Health Expect</source><year>2019</year><month>08</month><volume>22</volume><issue>4</issue><fpage>785</fpage><lpage>801</lpage><pub-id pub-id-type="doi">10.1111/hex.12888</pub-id><pub-id pub-id-type="medline">31012259</pub-id></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Schwab</surname><given-names>JD</given-names> </name><name name-style="western"><surname>Werle</surname><given-names>SD</given-names> </name><name name-style="western"><surname>H&#x00FC;hne</surname><given-names>R</given-names> </name><name name-style="western"><surname>Spohn</surname><given-names>H</given-names> </name><name name-style="western"><surname>Kaisers</surname><given-names>UX</given-names> </name><name name-style="western"><surname>Kestler</surname><given-names>HA</given-names> </name></person-group><article-title>The necessity of interoperability to uncover the full potential of digital health devices</article-title><source>JMIR Med Inform</source><year>2023</year><month>12</month><day>22</day><volume>11</volume><fpage>e49301</fpage><pub-id pub-id-type="doi">10.2196/49301</pub-id><pub-id pub-id-type="medline">38133917</pub-id></nlm-citation></ref><ref id="ref45"><label>45</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><name name-style="western"><surname>Grieve</surname><given-names>G</given-names> </name></person-group><article-title>SNOMED CT</article-title><source>Principles of Health Interoperability: FHIR, HL7 and SNOMED CT</source><year>2021</year><publisher-name>Springer</publisher-name><fpage>293</fpage><lpage>324</lpage><pub-id pub-id-type="doi">10.1007/978-3-030-56883-2_16</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>Guimar&#x00E3;es</surname><given-names>T</given-names> </name><name name-style="western"><surname>Duarte</surname><given-names>R</given-names> </name><name name-style="western"><surname>Hak</surname><given-names>F</given-names> </name><name name-style="western"><surname>Santos</surname><given-names>M</given-names> </name></person-group><article-title>Context-aware electronic health record&#x2014;Internet of Things and blockchain approach</article-title><source>Inform</source><year>2024</year><volume>11</volume><issue>4</issue><fpage>98</fpage><pub-id pub-id-type="doi">10.3390/informatics11040098</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>Rossander</surname><given-names>A</given-names> </name><name name-style="western"><surname>Lindsk&#x00F6;ld</surname><given-names>L</given-names> </name><name name-style="western"><surname>Ranerup</surname><given-names>A</given-names> </name><name name-style="western"><surname>Karlsson</surname><given-names>D</given-names> </name></person-group><article-title>A state-of-the-art review of SNOMED CT terminology binding and recommendations for practice and research</article-title><source>Methods Inf Med</source><year>2021</year><month>12</month><volume>60</volume><issue>S 02</issue><fpage>e76</fpage><lpage>e88</lpage><pub-id pub-id-type="doi">10.1055/s-0041-1735167</pub-id><pub-id pub-id-type="medline">34583415</pub-id></nlm-citation></ref><ref id="ref48"><label>48</label><nlm-citation citation-type="web"><article-title>Use of MeSH in online retrieval</article-title><source>National Library of Medicine</source><year>2025</year><access-date>2026-03-22</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://www.nlm.nih.gov/mesh/intro_retrieval.html">https://www.nlm.nih.gov/mesh/intro_retrieval.html</ext-link></comment></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>Turki</surname><given-names>H</given-names> </name><name name-style="western"><surname>Chebil</surname><given-names>K</given-names> </name><name name-style="western"><surname>Dossou</surname><given-names>BFP</given-names> </name><etal/></person-group><article-title>A framework for integrating biomedical knowledge in Wikidata with open biological and biomedical ontologies and MeSH keywords</article-title><source>Heliyon</source><year>2024</year><month>10</month><day>15</day><volume>10</volume><issue>19</issue><fpage>e38448</fpage><pub-id pub-id-type="doi">10.1016/j.heliyon.2024.e38448</pub-id><pub-id pub-id-type="medline">39403518</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>Kawamoto</surname><given-names>K</given-names> </name><name name-style="western"><surname>Houlihan</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Balas</surname><given-names>EA</given-names> </name><name name-style="western"><surname>Lobach</surname><given-names>DF</given-names> </name></person-group><article-title>Improving clinical practice using clinical decision support systems: a systematic review of trials to identify features critical to success</article-title><source>BMJ</source><year>2005</year><month>04</month><day>2</day><volume>330</volume><issue>7494</issue><fpage>765</fpage><pub-id pub-id-type="doi">10.1136/bmj.38398.500764.8F</pub-id><pub-id pub-id-type="medline">15767266</pub-id></nlm-citation></ref><ref id="ref51"><label>51</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Bousquet</surname><given-names>C</given-names> </name><name name-style="western"><surname>Souvignet</surname><given-names>J</given-names> </name><name name-style="western"><surname>Sadou</surname><given-names>&#x00C9;</given-names> </name><name name-style="western"><surname>Jaulent</surname><given-names>MC</given-names> </name><name name-style="western"><surname>Declerck</surname><given-names>G</given-names> </name></person-group><article-title>Ontological and non-ontological resources for associating Medical Dictionary for Regulatory Activities terms to SNOMED&#x2014;Clinical Terms with semantic properties</article-title><source>Front Pharmacol</source><year>2019</year><volume>10</volume><fpage>975</fpage><pub-id pub-id-type="doi">10.3389/fphar.2019.00975</pub-id><pub-id pub-id-type="medline">31551780</pub-id></nlm-citation></ref><ref id="ref52"><label>52</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>de Mello</surname><given-names>BH</given-names> </name><name name-style="western"><surname>Rigo</surname><given-names>SJ</given-names> </name><name name-style="western"><surname>da Costa</surname><given-names>CA</given-names> </name><etal/></person-group><article-title>Semantic interoperability in health records standards: a systematic literature review</article-title><source>Health Technol (Berl)</source><year>2022</year><volume>12</volume><issue>2</issue><fpage>255</fpage><lpage>272</lpage><pub-id pub-id-type="doi">10.1007/s12553-022-00639-w</pub-id><pub-id pub-id-type="medline">35103230</pub-id></nlm-citation></ref><ref id="ref53"><label>53</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Coiera</surname><given-names>E</given-names> </name></person-group><article-title>When conversation is better than computation</article-title><source>J Am Med Inform Assoc</source><year>2000</year><volume>7</volume><issue>3</issue><fpage>277</fpage><lpage>286</lpage><pub-id pub-id-type="doi">10.1136/jamia.2000.0070277</pub-id><pub-id pub-id-type="medline">10833164</pub-id></nlm-citation></ref><ref id="ref54"><label>54</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Giebel</surname><given-names>GD</given-names> </name><name name-style="western"><surname>Raszke</surname><given-names>P</given-names> </name><name name-style="western"><surname>Nowak</surname><given-names>H</given-names> </name><etal/></person-group><article-title>Problems and barriers related to the use of AI-based clinical decision support systems: interview study</article-title><source>J Med Internet Res</source><year>2025</year><month>02</month><day>3</day><volume>27</volume><fpage>e63377</fpage><pub-id pub-id-type="doi">10.2196/63377</pub-id><pub-id pub-id-type="medline">39899342</pub-id></nlm-citation></ref><ref id="ref55"><label>55</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Lee</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Jain</surname><given-names>S</given-names> </name><name name-style="western"><surname>Chen</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Clinical decision support using pseudo-notes from multiple streams of EHR data</article-title><source>NPJ Digit Med</source><year>2025</year><month>07</month><day>2</day><volume>8</volume><issue>1</issue><fpage>394</fpage><pub-id pub-id-type="doi">10.1038/s41746-025-01777-x</pub-id><pub-id pub-id-type="medline">40604255</pub-id></nlm-citation></ref><ref id="ref56"><label>56</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Guo</surname><given-names>H</given-names> </name><name name-style="western"><surname>Scriney</surname><given-names>M</given-names> </name><name name-style="western"><surname>Liu</surname><given-names>K</given-names> </name></person-group><article-title>An ostensive information architecture to enhance semantic interoperability for healthcare information systems</article-title><source>Inf Syst Front</source><year>2023</year><month>03</month><day>1</day><fpage>1</fpage><lpage>24</lpage><pub-id pub-id-type="doi">10.1007/s10796-023-10379-5</pub-id><pub-id pub-id-type="medline">37361885</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Overview of the hierarchical structure of contextual factors.</p><media xlink:href="medinform_v14i1e103470_app1.xlsx" xlink:title="XLSX File, 16 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Mapped context concepts.</p><media xlink:href="medinform_v14i1e103470_app2.xlsx" xlink:title="XLSX File, 21 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Unmatched context concepts.</p><media xlink:href="medinform_v14i1e103470_app3.xlsx" xlink:title="XLSX File, 11 KB"/></supplementary-material></app-group></back></article>