> 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/clinical-finding-and-disorder.md).

# Clinical Finding and Disorder

<table><thead><tr><th width="132.0546875">Hierarchy</th><th width="271.7578125">Definition</th><th>Example</th></tr></thead><tbody><tr><td>Clinical finding</td><td>Normal/abnormal observations, judgments, or assessments of patients</td><td>167222005 | Abnormal urinalysis (finding) |</td></tr><tr><td>Disorder</td><td>Always and necessarily an abnormal clinical state</td><td>39579001 | Anaphylaxis (disorder) |</td></tr></tbody></table>

Clinical findings or observations are the active acquisition of subjective or objective information from a primary source. This includes information acquired from human observers, through recording of data via the use of scientific instruments, or indirectly from samples taken from the source, and evaluated separately.

#### Context

The default context for a *Clinical finding* concept is:

* Present (vs. being absent)
* Subject of the record (the patient)
* Current, if not specifically stated or specified to a time in the past by an entity linked to the concept

#### Findings and Observables

The term *observations* should not be confused with *Observable entity.* Observable entity is the name of something that can be observed and represents a question or assessment (e.g. |systolic blood pressure|, |color of iris|, |gender|) which can produce an answer or result.

Given differences in information models, a finding about the subject of the record may be captured in different ways. For example, the information may be captured using either an Observable entity concept together with a value, or a Clinical finding concept which represents what is being observed together with the result of the observation. To assist the transformation between these concepts, if when adding a requested Clinical finding concept, the modeling requires an Interprets relationship, and the Observable entity concept does not exist, then a new Observable entity concept should be created.

#### Findings and Disorders

The *Clinical finding* hierarchy contains the subhierarchy of *Disorder*. Concepts that are descendants of *Disease (disorder)* are always and necessarily abnormal clinical states. The Disease subtype allows diseases to be subtypes of other disorders, as well as subtypes of findings.

Concepts with a semantic tag of *disorder* , must have a parent of Disease (disorder) or subtype of Disease (disorder).

* For example,
  * 95617006 | Neonatal cyanosis (disorder)| has the parent, Disease (disorder). Neonatal cyanosis is also a subtype of 3415004 | Cyanosis (finding)|

The distinction between a disorder and a finding may be difficult to define. There are, however, distinct characteristics of each.

<table><thead><tr><th width="117.6953125">Hierarchy</th><th>Characteristics</th></tr></thead><tbody><tr><td>Disorder</td><td><p>-Always and necessarily abnormal</p><p>-Necessarily have an underlying pathological process</p><p>-Have temporal persistence (may be under treatment, in remission, or inactive, even though they are still present)</p><p>-May be present as a propensity for certain abnormal states to occur, even when treatment mitigates or resolves those abnormal states</p></td></tr><tr><td>Finding</td><td><p>-May be normal (but not necessarily)</p><p>-May exist only at a single point in time (e.g. a serum sodium level)</p><p>-Cannot be temporally separate from the observation (one cannot observe them and say they are absent, nor can they be present when they cannot be observed)</p><p>-Cannot be defined only in terms of an underlying pathological process that is present, when the observation itself is not present</p></td></tr></tbody></table>

In some cases the disease process is irrefutable, e.g., meningococcal meningitis. In others an underlying disease process is assumed based on the temporal and causal association of the disorder and its manifestation, e.g., nystagmus (disorder) is different from nystagmus present (finding). Nystagmus present (finding) may be a normal physiological response to head rotation. A person who spins around and has nystagmus present (finding), does not have nystagmus (disorder). Alternatively, a person may have nystagmus (disorder), but not nystagmus present (finding), i.e., they do not currently manifest nystagmus. Similarly, hearing loss (disorder) is different from perception of hearing loss (finding), which can be due to a number of temporary causes, such as excessive ear wax.

## Topics in this section

{% content-ref url="/pages/Fdf2xapWdcohNRzqUrvL" %}
[Clinical Finding and Disorder Attributes Summary](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-attributes-summary.md)
{% endcontent-ref %}

{% content-ref url="/pages/dftkxak9enZLjHq4OVSy" %}
[Clinical Finding Defining Attributes](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-defining-attributes.md)
{% endcontent-ref %}

{% content-ref url="/pages/KXIx47AhfyeiRQu2WacB" %}
[Clinical Finding and Disorder Naming Conventions](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/index.md)
{% endcontent-ref %}

{% content-ref url="/pages/KVGQxzBkUaip3x6sh5dB" %}
[Clinical finding and Disorder Modeling](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling.md)
{% endcontent-ref %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Clinical%20Finding%20and%20Disorder" class="button primary">Provide Feedback</a>


---

# 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/clinical-finding-and-disorder.md?ask=<question>&goal=<user_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.