# Rationalize Search Results by Subsumption Checking

Filtering a search by using subsumption checking is an effective technique to enhance the display of search results. It reduces the list of search results by nesting the subsumed Concepts under the general Concept. If the user wishes to select a narrower Concept, they can expand the node to select the nested subtype.

## An Example Illustrating Rationalization by Subsumption Cross-Checking

Unconstrained search for descriptions that begin with "hernia" returns a total of 49 Concepts which belong to many subtype hierarchies such as <mark style="color:blue;">|</mark> Clinical Finding <mark style="color:blue;">|</mark> and <mark style="color:blue;">|</mark> Morphologic abnormalities <mark style="color:blue;">|</mark>.

<figure><img src="https://655065570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCEAcChvWjWEu16YmwNrz%2Fuploads%2Fgit-blob-30ef4ea47553e4125e49c28c2f9092a6e8480fe3%2F52170522.png?alt=media" alt=""><figcaption><p>Rationalize search results by subsumption checking</p></figcaption></figure>

Constraining a search for "hernia" by the "clinical findings" supertype returns 35 matches which is still considered to be a long list, many of which are subsumed by the general Concept "hernia". \[see [Constrain searches by supertype ancestors](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-search-and-data-entry-guide/4-optimizing-searches/4.4-constrained-searches#constrain-searches-by-supertype-ancestors)]

<figure><img src="https://655065570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCEAcChvWjWEu16YmwNrz%2Fuploads%2Fgit-blob-c6deeafc5b290ff19163f87a4d1d1a6ee791ecaa%2F52170521.png?alt=media" alt=""><figcaption><p>Rationalize search results by subsumption checking - clinical findings only</p></figcaption></figure>

Rationalisation by subsumption cross-checking can further reduce the matches by nesting the subsumed Concepts such as <mark style="color:blue;">|</mark> perineal hernia <mark style="color:blue;">|</mark> under <mark style="color:blue;">|</mark> hernia <mark style="color:blue;">|</mark>. If the user wishes to select a narrower Concept, they can expand the node to select the nested subtype.

<figure><img src="https://655065570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCEAcChvWjWEu16YmwNrz%2Fuploads%2Fgit-blob-1967889c39b53d8acb03cf2f10d6205f21e0b9d8%2F52170520.png?alt=media" alt=""><figcaption><p>Subsumed Concepts nested under "hernia"</p></figcaption></figure>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Search+And+Data+Entry+Guide&#x26;entry.670899847=Rationalize%20Search%20Results%20by%20Subsumption%20Checking" class="button primary">Provide Feedback</a>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-search-and-data-entry-guide/5-optimize-display-of-search-results/5.4-rationalize-search-results-by-subsumption-checking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.