> 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-sql-practical-guide/introduction/2-objectives-audiences-and-uses.md).

# Objectives, Audiences and Uses

## Objectives

The key objectives of this guide are to:

1. Enhance understanding of the logical design of SNOMED CT;
2. Demonstrate the feasibility of effective terminology access;
3. Enable terminology access for practical exercises;
4. Provide a starting point for further development.

## Audiences

There are three distinct target audiences for this guide:

1. Designers and developers
   * The guide provides practical examples of the ways in which features in SNOMED CT can be accessed using a widely understood technology;
   * It demonstrates services that designers and developers should consider including in their terminology server developments;
   * It can also be used to inform terminology server requirements for system access to SNOMED CT.
2. People seeking practical ways to access SNOMED CT content and reference sets:
   * The demonstrator documented in this guide provides ways to access SNOMED CT content and reference sets using simple SQL queries.
   * This type of access can complement the use of a SNOMED CT browser or other specific tools by enabling customizable access to specific collections of terminology content.
3. Anyone interested in SNOMED CT who is seeking a practical example of accessing the terminology in ways described in other specifications and guides:
   * Although many SNOMED CT tools deliver user-friendly services for well-established use cases, some use cases require customized services that are not readily available from existing tools.
   * For example, the full version of the demonstration database allows queries to be written that report the history of changes that impact a defined set of SNOMED CT components.

{% hint style="warning" %}
Although there are three distinct target audiences, this guide has primarily been written for those with a *technical* background.
{% endhint %}

Each section of the guide includes an indication of its applicability to each of these audiences.

## Ways of Using this Guide

The guide is designed to be used in any of the following ways to suit the needs of different audiences.

1. As a set of step-by-step instructions for a practical demonstration project
2. As a source of ideas and advice to inform other development approaches
3. As a source of practical examples that illustrate and validate general guidance
4. As background reading when exploring technical options

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SQL+Guide&#x26;entry.670899847=Objectives%2C%20Audiences%20and%20Uses" 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-sql-practical-guide/introduction/2-objectives-audiences-and-uses.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.
