> 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-data-analytics-guide/7-task-oriented-analytics/7.3-clinical-research.md).

# Clinical Research

Clinical research is a branch of healthcare science that determines the safety and effectiveness of medications, devices, diagnostic products, and treatment regimens intended for human use. Clinical research may be used for the prevention, treatment, diagnosis or for relieving symptoms of a disease. In contrast to clinical practice, which applies established treatment regimes, clinical research collects evidence to extend knowledge and establish the value of novel treatments and other patient management practices.

Clinical research typically involves the analysis of data from well-defined and homogenous groups of patients with a specific disease, at a specific stage, receiving similar treatments and often without significant co-morbidities. The data may be captured prospectively or retrieved retrospectively.

SNOMED CT helps clinical research activities by assisting in the identification of clinical trial candidates, enabling the powerful analysis of trial data, supporting predictive medicine, and improving the effectiveness of semantic search over clinical knowledge.

In this section, we discuss three key aspects to clinical research that can benefit from the use of SNOMED CT: identification of clinical trial candidates, predictive medicine, and semantic search.

***

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Data+Analytics+Guide&#x26;entry.670899847=7.3%20Clinical%20Research" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-data-analytics-guide/7-task-oriented-analytics/7.3-clinical-research.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
