> 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.1-use-cases-directly-connected-to-data-entry.md).

# Use Cases Directly Connected to Data Entry

## Writing an Entry Into a Clinical Record at or Near the Point of Care

At the point of care, search is done in order to find a Concept which describes a specific event that occurred during the course of patient care (e.g. documenting the findings related to a physical examination, diagnosis or surgical procedure into a form).

## Creating Forms for Structured Data Entry

Data entry forms in clinical records are often designed for a specific documentation purpose. Designing the interface of a data entry forms and/or its content may entail associating Concepts with a template element or control. In highly structured forms, the design may involve specifying what Concepts should be available for selection. In less structured templates, the design may involve specifying the features useful for conducting an efficient and effective search. Thus, template designers may need to be able to search the whole terminology but also have the competencies to manually constrain the search by various filters and applying advanced functionalities, such as expression views and comparison between Concepts.

For more information on structured data entry, please refer to the "[Structured data entry](/snomed-ct-practical-guides/snomed-ct-search-and-data-entry-guide/6-data-entry/6.2-structured-data-entry.md)" sub-section.

<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=Use%20Cases%20Directly%20Connected%20to%20Data%20Entry" 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.1-use-cases-directly-connected-to-data-entry.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.