This chapter delves into how context is represented within SNOMED CT, highlighting how context-free hierarchies interact with explicit contextual details present in the Situation with Explicit Context subset. Understanding these nuances holds significance for healthcare practitioners and informaticians, impacting the accuracy and utility of clinical terminologies.
The top-level hierarchies of SNOMED CT, excluding the Situations with Explicit Contexts hierarchy, are typically meant to be interpreted within the framework of an information model. These hierarchies, including Clinical Finding, Procedure, Body Structure, and Substance, among others, do not inherently carry explicit contextual information within the concepts themselves. Instead, their interpretation relies heavily on the applied information model within a specific healthcare system or setting. The information model defines how these SNOMED CT concepts are structured, related, and utilized within a particular context. It offers a structured framework for their meaningful interpretation and application in clinical scenarios. This reliance on the information model ensures that these concepts are accurately understood and used within the context of healthcare delivery, aiding in precise data representation, clinical decision-making, and interoperability across different healthcare systems.
The SNOMED CT concept model serves as the framework for SNOMED CT's quality, defining relationship types (attributes) that encapsulate the defining properties of concepts. For each top-level hierarchy or sub-hierarchies, it specifies the set of attributes applicable to concepts within that domain, and it outlines the range of concepts suitable as the value for each attribute. This set of rules supports uniformity and coherence across concept definitions.
The concept model is integral to ensuring SNOMED CT's quality standards. It fosters consistency in concept definitions, vital for the accurate functioning of the Description Logic reasoner. Adhering to this model enables the reasoner to accurately derive inferences, ensuring dependable and precise outcomes when searching, querying, or utilizing SNOMED CT data.
The attributes outlined in the SNOMED CT concept model represent inherent properties that must be true for every instance of that concept. These attributes do not change the fundamental nature or primary type of the concept within its hierarchy. Rather, they establish consistent and unchanging characteristics unique to each instance in the hierarchy, maintaining the core identity of the concept. For this reason, concepts such as 'family history of asthma' or 'diarrhea not present' are not included in the Clinical finging top-level hierarchy. These concepts don't depict actual disorders; instead, they describe particular contextualized situations associated with conditions like asthma and diarrhea. Similarly, within the Procedure hierarchy, concepts such as 'no history of mammogram' or 'Hypersensitivity skin test not done' wouldn't be present. These concepts don't signify specific clinical procedures; rather, they indicate situations or contexts surrounding procedures like mammograms or hypersensitivity skin tests.
Maintaining the integrity and scope of each hierarchy within SNOMED CT is crucial. Altering the meanings of concepts or introducing concepts with explicit context can compromise the terminology's usability for precise data retrieval, analysis, and decision support. When concepts deviate from their intended definitions within their hierarchies, it hampers the accuracy and reliability of information retrieval and analysis processes. This situation becomes particularly critical in healthcare settings, where inaccuracies or ambiguous interpretations due to altered concepts can lead to safety-critical outcomes. Therefore, upholding the intended scope and definitions within hierarchies in SNOMED CT is vital for ensuring the reliability and safety of clinical data interpretation, decision-making, and patient care.
For more information about the SNOMED CT concept model, please refer to the Editorial Guide and the .
SNOMED CT was purposefully designed with a specific hierarchy, known as the Situation with Explicit Context (SWEC), to maintain a clear separation of contextualized findings and procedures. This hierarchy intends to define clinical situations as precoordinated concepts, i.e. clinical findings or procedures associated with contextual factors. The concept model guiding SWEC precisely defines acceptable contextual factors for each concept, enabling the documentation of contextualized clinical information while maintaining a standardized structure crucial for accurate data utilization and interoperability. Importantly, unlike other clinical hierarchies in SNOMED CT that are generally context-free, SWEC concepts are distinguished by their inclusion of context-specific details within the concepts themselves. This self-contained representation of SWEC concepts reduces reliance on external models for context interpretation.
The Situation with Explicit Context (SwEC) hierarchy is designed to capture and represent clinical findings and procedures within specific contexts, ensuring that their meaning is fully understood in the appropriate circumstances.
The concept model for SwECs includes two core attributes that apply universally to any concept within the hierarchy. Additionally, two specific attributes apply to Procedures with Explicit Context, and another two attributes are specific to Clinical Findings with Explicit Context. The table below outlines the purpose and semantic interpretation of each of these attributes.
The following pages will present examples of the different types of situations with explicit context, illustrating how each attribute is applied.
Clinical findings with explicit context refer to situations where the presence, absence, or uncertainty of a clinical finding is documented with additional contextual details. These concepts provide a clear understanding of the specific circumstances under which a clinical finding is relevant.
Associated Finding : Links the situation to a relevant clinical finding or event.
For example, the concept |History of sepsis (situation)| uses this attribute to connect to the clinical finding |Sepsis|.
Finding Context : Indicates whether the clinical finding is confirmed, suspected, unknown, or absent.
Specifies the relationship of the subject to the patient.
For example, is defined with the subject relationship context “Father of subject.”
Indicates the timing of the procedure or finding, whether it occurred in the past, present, or is planned for the future.
For example, is defined with the temporal context “In the past.”
Links the situation to a related clinical finding or event. It specifies the clinical concept whose context is being modified.
For example, is defined with the associated finding “Fever”
For example, for the concept |No known food allergy (situation)|, the finding context is |Known absent|.
Temporal Context : Specifies when the finding occurred or is expected to occur (past, present, future).
For example, |History of sepsis (situation)| uses |In the past| as the temporal context.
Subject Relationship Context : Identifies who the clinical finding pertains to, such as the patient, a family member, or another individual.
For example, |Family history of diabetes mellitus (situation)| would indicate that the finding relates to a family member.
The SNOMED CT concept describes a past instance of monkeypox in a patient’s medical history. It is characterized by the Associated finding attribute, which specifies that the condition is . This indicates that monkeypox was the specific viral illness recorded in the patient’s history. The concept also includes information that the condition was confirmed as present, pertains to the patient, and occurred in the past.
The SNOMED CT concept indicates that the patient does not have known food allergies. A key attribute here is , which is . This attribute specifies that the absence of a food allergy is confirmed. Additionally, the concept includes as , showing the specific type of allergy being assessed. The is , meaning the information pertains to the patient. The is , indicating that this absence of allergy has been consistent over time.
The SNOMED CT concept represents a patient’s past occurrence of sepsis. A key attribute here is , which is . This attribute specifies that the sepsis occurred in the past. The concept also includes as , indicating the specific condition recorded, and as , confirming that the sepsis was known to be present. The is , indicating that the sepsis pertains to the patient themselves.
The SNOMED CT concept represents the smoking status of a patient’s father. Central to this concept is the Subject relationship context attribute, which is . This attribute indicates that the smoking status being recorded pertains specifically to the patient’s father. The concept also includes details such as the associated finding of , the finding context as , and the temporal context as , reflecting that the smoking status is currently known and applies to the patient’s father.
Describes whether the finding is known, absent, or uncertain, as well as anticipated future findings.
For example, is defined with the finding context “Known absent.”
Links the situation to a procedure.
For example, is defined with the associated procedure “Surgical procedure.”
Indicates the status or completion of a procedure, such as planned, ongoing, or completed.
For example, is defined with the procedure context “Planned.
<< 243796009 |Situation with explicit context (situation)|<< 243796009 |Situation with explicit context (situation)|<< 413350009 | Finding with explicit context (situation)|



<< 413350009 | Finding with explicit context (situation)|<< 129125009 | Procedure with explicit context (situation)|<< 129125009 | Procedure with explicit context (situation)|Procedures with explicit context describe situations where a medical procedure’s status, timing, or relationship to the patient is specified. These concepts clarify whether a procedure is planned, completed, or not done, among other statuses.
Associated Procedure: Links the situation to the specific procedure being considered.
For example, |Lung transplant planned (situation)| uses this attribute to connect to |Lung transplant (procedure)|.
Procedure Context: Describes the status of the procedure, such as whether it is planned, completed, or not done.
For example, |Lung transplant planned (situation)|, the procedure context is |Planned|.
Temporal Context: Indicates when the procedure is or was to take place (past, present, future).
For example, |Lung transplant planned (situation)| uses |In the future| as the temporal context.
Subject Relationship Context: Specifies who the procedure pertains to, usually the patient but can be a different person.
For example, |Mother’s surgery planned (situation)| would indicate the procedure pertains to the patient’s mother.
The default values for the context attributes for procedures assume that the procedure has occurred, is current or at a specified time, and pertains to the subject of the record.
The SNOMED CT concept describes a patient’s status as they await a kidney transplant. A key attribute here is Associated procedure, which is . This indicates that the focus of the situation is the upcoming kidney transplantation procedure. Additionally, the concept includes the as To be done, specifying that the transplant is planned but not yet performed, and it applies to the patient at the .
The SNOMED CT concept represents a planned lung transplant for a patient. A key attribute here is . This attribute indicates that the lung transplant is scheduled for the future and has not yet been performed. Additionally, the concept includes as
, specifying the type of procedure planned. The
is , indicating that the procedure pertains to the patient themselves. The is , showing that the procedure is relevant at the present time or based on a specific schedule.
The SNOMED CT concept represents the occurrence of mastectomy within a patient’s family history. A key attribute here is Subject relationship context, which is . This attribute specifies that the mastectomy is related to a family member rather than the patient themselves. The concept also includes the associated procedure as , indicating that the mastectomy was the specific procedure performed, and the procedure context as Done, reflecting that the procedure has been completed. The temporal context is , signifying that the procedure occurred in the past or is relevant at present.
The SNOMED CT concept details a patient’s past use of estrogen hormone therapy. A key attribute here is , which is . This attribute specifies that the estrogen therapy occurred in the past. Additionally, the concept includes as , indicating the specific therapy administered, and as , showing that the therapy was completed. The subject relationship context is as , signifying that the therapy pertains to the patient themselves.



