This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.

Variable meanings according to context

Depending on context, concepts can be used in many different ways with various meanings.

A disorder concept can represent:

• Possible diagnosis or part of a differential diagnosis

• Diagnosis applied to a family member or some other contact person

• Diagnosis explicitly excluded

• Diagnosis, now known to be incorrect, but which was the basis for a particular course of treatment

A procedure concept can represent:

• Requested, recommended or planned procedure

• Procedure for which consent has been given or withheld

• Procedure that is contraindicated

• Procedure that has been canceled or postponed

A symptom concept can represent:

• Confirmed absence of a symptom

• Symptom deduced and reported by a third party as a witness of a clinical event

• Inability or failure to obtain information about a symptom

• Symptom which the patient is advised to respond to in a particular manner

A finding concept can represent:

• Absence of a finding

• Inability or failure to check for a finding

• Finding which, if present, is to trigger a particular change in clinical management

• Finding which is the goal or target of a treatment

A product concept can represent:

• Allergy or other contraindication to a product

• Assertion that a product caused a particular side effect

• Various therapeutic activities of a product

• Instructions given to a patient for use of a non-prescription medication

This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.

For information on precoordinated naming patterns that have been reviewed or are currently in review, see Pre-coordination Naming Patterns project. Unreviewed patterns for the Situation with explicit context hierarchy can be found here. New content should conform with the naming patterns; however, legacy content may not.

• For example,

  • Acceptable naming pattern

    • FSN: declined (situation)

    • PT: declined

    • SYN: refused (This is optional).

      • 736013005 |Body weight measurement declined (situation)|

The following naming patterns are no longer accepted for addition to the International Edition:

• Procedure offered

• Procedure not offered

• Procedure done

• Procedure not done

Note that 385658003 |Done (qualifier value)| (a descendent of 410523001 |Post-starting action status (qualifier value)|) remains in use as the target value of the 408730004 |Procedure context (attribute)| in History of <procedure> concepts.

Not every naming pattern is found in the Pre-coordination Naming Pattern project. Some naming patterns can be prescribed in . Others can come from trackers or fast track documents, such as the examples below.

716186003 |No known allergy (situation)|

• FSN: No known allergy (situation)

• PT: No known allergy

• SYN: NKA - No known allergy

428197003 |No known insect allergy (situation)|

• FSN: No known insect allergy (situation)

• PT: No known insect allergy

For concepts relating to a history of a finding, disorder, procedure, or event occurring in a past pregnancy of the subject of the record, use an FSN and PT of |Past pregnancy history of X (situation)|. These concepts are subtypes of 271903000 |History of pregnancy (situation)|.

• For example,

  • 161804005 |Past pregnancy history of antepartum hemorrhage (situation)| is a subtype of 271903000 |History of pregnancy (situation)|

For content relating to family history, this must be specified in both the FSN and preferred term to distinguish between past pregnancy of the subject of the medical record.

• For example,

  • |Past pregnancy history of neonatal death (situation)| versus |Family history of neonatal death (situation)|

This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.

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 post-coordinated expressions, its range is broader than when used in pre-coordinated 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)

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.

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)

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.

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)

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)

This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.

When authoring in this domain, these are the approved attributes and allowable ranges.

Domain Information for Situation with Explicit Context

This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.

SNOMED CT contains concepts that include context information, and concepts that are regarded as context-free. A concept includes context information if the name of the concept explicitly represents information that might otherwise be represented by another less context-rich concept in a particular place within an electronic health record or EHR.

In SNOMED CT, context describes the effects of embedding a concept in a clinical situation, i.e. when it is used in an EHR.

For example,

• When the concept 22298006 |Myocardial infarction (disorder)| is used in an EHR, it takes on a specific contextualized meaning. The meaning might be an assertion by the person entering the information, that on a given date, the patient was diagnosed with a myocardial infarction. Or, it may be used to document a complication of smoking, a protocol for chest pain, a medication contraindication, a part of a patient's medical history, a possible diagnosis justifying a diagnostic test, a diagnosis excluded by a diagnostic test, a patient's family history, etc.

  • The concept for breast cancer, 254837009 |Malignant neoplasm of breast (disorder)|, might be used to indicate either a current diagnosis of breast cancer, a family history of breast cancer, or a past history of breast cancer. Each of these three meanings differs in regard to the context in which breast cancer is described.

    • Current diagnosis of breast cancer indicates that the breast cancer is present now, and in this patient.

    • Family history of breast cancer refers to breast cancer occurring in a family member of a patient.

Not only are the differences significant relative to a patient's health record, but they are also important to population-based data retrieval; e.g. it is incorrect to retrieve those who have a family history of breast cancer when searching for patients with a diagnosis of breast cancer.

When a SNOMED CT concept appears in an EHR without any explicitly stated context, that concept is considered to have a default context. However, the information in the health record structure or information model can override the default context.

Default context for a Clinical finding concept implies that the finding is present (vs. being absent), that it applies to the subject of the record (the patient), and that it is current (or at a specified time in the past, linked to the concept).

Default context for a Procedure concept implies that the procedure was completed, that it was performed on the subject of the record (the patient), and that it was done at the present time (or at a specified time in the past, linked to the concept).

Concepts in the Situation hierarchy (given the appropriate record structure) have explicit context and can represent Clinical findings and Procedures that:

Have not yet occurred

For example,

• 165137000 |Endoscopy arranged (situation)|

Refer to someone other than the patient

For example,

• 160303001 |Family history: Diabetes mellitus (situation)|

• 395083002 |Discussed with next of kin (situation)|

Have occurred at some time prior to the time of the current entry in the record

For example,

• 161514008 |History of aortic aneurysm (situation)|

These attributes are used to represent Clinical finding and Procedure concepts within the Situation hierarchy:

Context typically alters the meaning of a concept, i.e., the resulting concept is no longer a subtype of the original concept.

Precoordinated expression. Clinical context is specified in the description and entered into a field in a patient's EHR.

For example,

• The precoordinated expression 266897007 |Family history: Myocardial infarction (situation)| might be put directly in a blank field in a patient's EHR. A family history of myocardial infarction is not a subtype of myocardial infarction, so family history modifies the context.

• The precoordinated expression 54355006 |Intracranial injury, without skull fracture (disorder)| might be put directly in a blank field in a patient's EHR. The disorder Intracranial injury, without skull fracture is not a subtype of skull fracture, so without modifies the context.

Postcoordinated expression. Clinical context is specified by combining concepts.

For example,

• 281666001 |Family history of disorder (situation)| , combined with 246090004 |Associated finding (attribute)| = 22298006 | Myocardial infarction (disorder). These two concepts indicate a family history of myocardial infarction.

Concept or expression in an EHR field. A concept is placed in a field with a predefined meaning in an electronic health record. The meaning is conveyed by the context in which it is recorded.

For example,

• Hip replacement planned might be represented as 397956004 |Prosthetic arthroplasty of the hip (procedure)| within a section of a patient's health record called Planned actions. A planned hip replacement is not a kind of hip replacement, so the Planned actions record section modifies the context

• 2004005 |Normal blood pressure (finding)| might be placed in a field labeled as Goal in a patient's EHR. A goal of normal blood pressure is not a kind of Normal blood pressure (finding), so the Goal field in the EHR modifies context.

Elaboration in SNOMED CT refers to any addition to or change of the meaning of a concept that may be brought about when it is embedded in a clinical situation. Embedding a concept in a clinical situation may elaborate the semantic interpretation of a concept in one of the following ways:

1. Subtype qualification

2. Axis modification

3. Affirmation or Negation

4. Combination

A subtype qualification refines the meaning of a concept. Subtype qualification is elaboration that results in a concept that is a subtype of the original unelaborated focus concept. A focus concept is the part of a SNOMED CT expression that represents a clinical finding, observation, event, or procedure. It may be given context by a surrounding context wrapper and may be made more specific by a refinement.

• For example,

  • A past history of replacement of the left hip may be represented by a SNOMED CT expression in which the focus concept, hip replacement, is refined by laterality, left and enclosed in a context wrapper representing past history.

The attributes used to define situation concepts permit explicit (rather than default) representation of various contexts. These attributes can change the meaning of a Clinical finding or Procedure concept in a way that changes the hierarchy (or axis) of the concept from Clinical finding or Procedure to Situation with explicit context. The resulting modified meaning is not a subtype of the original meaning of the concept, and therefore the axis-modifying attributes are not used to qualify the concept, but instead are used to qualify a Situation concept.

For example,

• The concept 22298006 |Myocardial infarction (disorder)| may be elaborated by including it in a clinical record specifying family history. A record of a family history of myocardial infarction does not imply that the patient has had any type of myocardial infarction. Therefore, family history changes the focus from the default context to a specified context.

• The concept 52734007 |Total replacement of hip (procedure)| may be elaborated by stating that the procedure is planned for some future date. A record of planned total hip replacement does not imply that the patient has actually had a total hip replacement, i.e. it is not the default context for a procedure.

• The concept 167272007 |Urine protein test not done (situation)| uses the context-modifying attribute Procedure context (attribute) and a value of Not done (qualifier value). This concept is not a subtype of 167271000 | Urine protein test (procedure)| , because its axis (hierarchy) is modified. Note that | not done| is no longer allowed. See the list disallowed naming patterns at

Depending on perspective, affirmation and negation may simply be viewed as the inversion of meaning of an unelaborated concept that represents a Clinical finding. A concept may be stated in the negative in a clinical situation (e.g., meningism not present). This creates the potential for a concept to represent two meanings, one of which is the inverse of the other. However, the effects of negation on interpretation are far-reaching and distinct from other elaborations.

Negation, like axis modification, results in a concept that is not a subtype of the unelaborated concept. However, negation explicitly rules out the unelaborated concept.

• For example,

  • Family history of myocardial infarction does not imply that a patient had a myocardial infarction.

  • No headache implies that patient has headache is untrue. A negative statement may expand further in the opposite direction of a positive statement. If headache is a subtype of pain then patient has headache implies patient has pain. However, patient has no headache does not imply patient has no pain. Conversely, patient has headache does not imply

A concept may be stated to be possible in a clinical situation. Statements that explicitly indicate uncertainty can be considered in two possible ways:

• Somewhere between affirmation and negation

• As a type of elaboration

Two or more concepts may be embedded in a clinical situation in a way that links them together. Linkages may include:

• Simple combination of concepts

• Combination of a concept that is present and another that is absent

Once a concept has context-shifted and become context-dependent , it should not be used in an expression that once again shifts context. In other words, when one context attribute is given an axis modifying value, the other context attributes are fixed.

• For example,

  • The model for 430679000 |Family history of diabetes mellitus type 2 (situation)| IS A Situation with explicit context (situation) with:

    • Subject relationship context of Person in family of subject (person)

Even though the Family part of the concept results in an explicit axis shift of the Subject relationship context only, SNOMED CT requires default values for Finding context and Temporal context, rather than allowing them to be unspecified.

To negate a concept with Finding context (attribute) of Known present (qualifier value), the Finding context (attribute) should instead have a value of Known absent (qualifier value).

• For example,

  • The concept 160273004 |No family history: Hypertension (situation)| negates 160357008 |Family history: Hypertension (situation)| by changing the value of Finding context (attribute) to Known absent (qualifier value) with Temporal Context (attribute) of All times past (qualifier value). The parent IS A Situation with explicit context (situation) with:

    • Temporal context of All times past (qualifier value)