> 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-practical-guides/snomed-ct-search-and-data-entry-guide/5-optimize-display-of-search-results/5.3-avoid-multiple-hits-on-the-same-concept.md).

# Avoid Multiple Hits on the Same Concept

In many instances, several synonyms associated with the same Concept contain the same keyword *.* For example, <mark style="color:blue;">|</mark> herniated structure <mark style="color:blue;">|</mark>, <mark style="color:blue;">|</mark> hernia <mark style="color:blue;">|</mark>, <mark style="color:blue;">|</mark> herniated tissue <mark style="color:blue;">|</mark>, <mark style="color:blue;">|</mark> herniated structure <mark style="color:blue;">|</mark> and <mark style="color:blue;">|</mark> herniation <mark style="color:blue;">|</mark> all begin with "hernia". A search for the target Concept "hernia" would return the first phrase found during the search. Designing a filter that gives the user the option of filtering the results by description type such as the Preferred Term or the Fully Specified Name can significantly reduce the results, as illustrated in the image below.

## Avoid Multiple Hits on the Same Concept by Filtering the Search by Description Type

| Step 1                                                                                              | Step 2                                                                                              |
| --------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| <div><figure><img src="/files/vsQHxgHHWw04Gj9ltPOY" alt=""><figcaption></figcaption></figure></div> | <div><figure><img src="/files/qqJW6VvIE8p22sqhC8zO" alt=""><figcaption></figcaption></figure></div> |

<p align="center"><em><mark style="color:blue;">Filtering search results to show only the Fully Specified Name (search also constrained by supertype ancestor)</mark></em></p>

Designing a filter gives the user the option of filtering the results to show only the Description associated with the Concept that is the closest match to the search term, as illustrated in the image below.

| Step 1                                                                                              | Step 2                                                                                              |
| --------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| <div><figure><img src="/files/bNWtNoevBOPHgKDj6xZn" alt=""><figcaption></figcaption></figure></div> | <div><figure><img src="/files/9xSEFFqYm5I6VfqQGVww" alt=""><figcaption></figcaption></figure></div> |

<p align="center"><em><mark style="color:blue;">Filtering search results to show only the closest match to the search term, hernia (search also constrained by supertype ancestor)</mark></em></p>

<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=Avoid%20Multiple%20Hits%20on%20the%20Same%20Concept" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` 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.3-avoid-multiple-hits-on-the-same-concept.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.