> 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/2-introduction-to-search/2.1-the-importance-of-effective-search.md).
# The Importance of Effective Search
Search is an important part of the clinical information life-cycle. Effective search must make it quick and easy for users to accurately select the relevant content for data entry. The selected Concept or Description may need to be stored in ways that represent information consistently and allow it to be processed effectively.
An EHR system must also have a user interface that makes search easy in terms of the time and effort required to find suitable Concepts to enter into the clinical record. Improving the usability of search can help increase the utility of SNOMED CT for data entry, and hence, the overall adoption of clinical systems. Increasing the utility and the added value of clinical systems depends on improving the tradeoff between time taken to code, and the quality of the coded content produced. This is true *whichever* terminology is chosen to be implemented 'front of house'.
Leveraging SNOMED CT advanced design and implementing it properly is specifically intended to give better leverage in this tradeoff than we could ever have on other coding systems. However, if badly implemented, SNOMED CT will make an already bad situation worse. On the other hand, a multitude of different but generally poor designs is equally dangerous. There is a minimum level of functionality that should be universal, and implementers need to be more prescriptive when designing the search functionality.
Approaches to search embedded in clinical systems need to be tailored to the way different groups of clinicians work and think. While this guide identifies useful techniques to support searching, the ways in which these are applied may need to vary to match the working practices of a clinical specialty or the priorities of a particular health provider organization.
For effective data entry, the interface needs to be designed to meet the requirements for subsequent display and retrieval. Data entered and stored in the clinical record, needs to be displayed in ways that can be easily read and understood. The data should also be retrievable to enable reporting analysis, decision support and appropriate communication to other systems and other users.
Provide Feedback
---
# 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/2-introduction-to-search/2.1-the-importance-of-effective-search.md?ask=&goal=
```
`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.