> 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/3-use-cases-for-searches/3.2-use-cases-where-search-browsers-are-required.md).

# Use Cases Where Search Browsers are Required

## Creating Queries for Retrieving Data

Search can be required for defining Concepts and Descriptions that are used in subsequent data retrieval from patient records. The effectiveness of a search technique depends on the requirements for reporting and analysis (e.g. creating a query that searches for SNOMED CT coded data within specific subtype-hierarchies).

## Binding SNOMED CT to Knowledge Artifacts

The integration of clinical decision support tools into clinical record systems can help to improve evidence-based practice. The binding of SNOMED CT to knowledge artifacts enables the linkage between the knowledge content in clinical decision support and the SNOMED CT coded data items in the clinical record. The binding typically entails searching for the SNOMED CT Concept. Effective techniques for searching for SNOMED CT Concepts for data entry can improve the assessment of the context of a Concept within SNOMED CT prior to binding and the overall binding efficiency.

## Evaluating Terminology Content

*For example to review content coverage*

There can be various use cases for reviewing SNOMED CT content. For example, terminology content can be evaluated to decide whether the coverage of SNOMED CT is a sufficient to fit documentation purposes (e.g. a cardiovascular surgeon could assess whether SNOMED CT covers all cardiovascular terms). This assessment typically entails searching for SNOMED CT Concepts which requires effective search techniques.

## Mapping Between SNOMED CT and Another Code Scheme

In mapping, searching to identify SNOMED CT Concepts required to be mapped to or from another code scheme (e.g. ICD-10 or local codes) is required.

## Creating Reference Sets

*For example to represent subsets of terms and concepts*

Identifying subsets of Concepts or Descriptions for inclusion in a Reference Set typically requires searching SNOMED CT content.

## Learning About the Structure and Content of the Terminology

Realizing and understanding the comprehensiveness and complexity of SNOMED CT may be a steep learning curve for users. Searching and browsing through navigational results can aid the learning process. Thus, effective search techniques increase the chances of finding the required content and understanding where it fits into the overall structure of SNOMED CT.

## Editing SNOMED CT Descriptions

Terminology authorities such as National Release Centers may need to edit SNOMED CT Descriptions to adhere to national or local linguistic/editorial guidelines. This entails searching large subsets of Concepts and Descriptions. Thus, effective search techniques are required to find the correct Concept or Description within these large subsets.

<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=3.2%20Use%20Cases%20Where%20Search%20Browsers%20are%20Required" 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/3-use-cases-for-searches/3.2-use-cases-where-search-browsers-are-required.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.