> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/situation-with-explicit-context/situation-with-explicit-context-defining-attributes.md). # Situation with Explicit Context Defining Attributes The following defining attributes correspond to the *Situation with Explicit Context Attributes Summary* table. *Associated finding* and *Finding context* are used with Findings with Explicit Context. ## Associated finding This attribute links concepts in the Situation with explicit context hierarchy to their related Clinical finding or Event. It specifies the Clinical finding or Event concept whose context is being modified. When Associated finding is used in postcoordinated expressions, its range is broader than when used in precoordinated content. Associated finding should not reference concepts that already have precoordinated context. For example, * 443999008 | Risk of exposure to communicable disease (situation) | with Associated finding, Exposure to communicable disease (event) For example, to create the concept, History of thyroid disease in father, * Subject relationship context (attribute) with the value, father (person) * Associated finding (attribute), with the value, Disorder of thyroid gland (disorder) Incorrect example, * Using Family history with explicit context (situation), * Subject relationship context (attribute) with the value, father (person) * Associated finding with value, Family history: Thyroid disorder (situation) ## Finding context This attribute represents a situation in which a Clinical finding or Event is known or unknown. If known, whether it is present, absent, or uncertain (possible). It also represents that the finding is not actual, but anticipated or possible in the future. For example, * 161922009 | No cough (situation)| with Associated finding, Cough (finding) and Finding context, Known absent (qualifier value) *Subject relationship context* and *Temporal context* are used with Situations, Findings, and Procedures with Explicit Context. ## Subject relationship context This attribute is used to specify the subject of the Clinical finding or Procedure being recorded, in relation to the subject of the record. For example, * 161077003 | Father smokes (situation)| with Associated finding, Smoker (finding) and Subject relationship context, Father of subject (person) {% hint style="info" %} Observables about someone other than the subject of record are included in the Observable entity hierarchy, not the Situation with explicit context hierarchy, e.g,. 443722004 |Educational level of parent of subject (observable entity). {% endhint %} ## Temporal context This attribute indicates the *time* of the procedure or finding. It may be *actual,* i.e., occurred in the present, in the past, at a specified time; or in the future, i.e., it is planned or expected. The most general value is simply |Current or past (actual) (qualifier value)|, meaning that the concept was actual (not planned or expected), but not specifying anything further about the time. The word *specified* in the Temporal context means that there is a date or time stamp associated with the concept in the record. The date and/or time is a point and/or interval, that applies to the concept. For example, * 161550001 | History of hematuria (situation)| with Associated finding, Blood in urine (finding) and Temporal context, In the past (qualifier value) *Associated procedure* and *Procedure context* are used with Procedures with Explicit Context. ## Associated procedure This attribute links concepts in the Situation with explicit context hierarchy to concepts in the Procedure hierarchy for which there is additional context. For example, * 183976008 | Operative procedure planned (situation)| with Associated procedure, Surgical procedure (procedure) ## Procedure context This attribute indicates the degree of completion, or status, of a Procedure, as well as its possible future states, prior to it being initiated or completed. For example, * 183976008 | Operative procedure planned (situation)| with Procedure context, Planned (qualifier value) Provide Feedback --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snomed.org/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/situation-with-explicit-context/situation-with-explicit-context-defining-attributes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.