> 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-terminology-services-guide/3-terminology-service-use-cases.md).
# Terminology Service Use Cases
## Overview of Use Cases
The following use cases are covered in this section:
* [**Explore and Review SNOMED CT**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/explore-and-review-snomed-ct.md) - Terminology services required for SNOMED CT browsers and exploration tools
* [**Support EHR Data Entry**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/support-ehr-data-entry.md) - Services needed for electronic health record data entry with SNOMED CT
* [**Display EHR Data**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/display-ehr-data.md) - Services for displaying SNOMED CT concepts in EHR systems
* [**EHR Reporting and Analytics**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/ehr-reporting-and-analytics.md) - Services required for reporting and analytics using SNOMED CT
* [**Reference Set Editing**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/reference-set-editing.md) - Services for creating and editing SNOMED CT reference sets
* [**Apply Mapping Reference Sets**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/apply-mapping-reference-sets.md) - Services for applying mapping reference sets between code systems
* [**Terminology Change Management**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/terminology-change-management.md) - Services for managing terminology changes and versioning
* [**Support Terminology Authoring and Review**](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/3-terminology-service-use-cases/support-terminology-authoring-and-review.md) - Services to support terminology authoring and review processes
{% hint style="info" %}
**Notes on the attributes used in the tables of this page:**
\***Status:** Applications designed to address this use case must support the practical requirements marked as *Required*. Support for the practical requirements marked as ***Optional*** is recommended as these provide enhanced functionality that may be required by some users.
**\*Required Services:** In most cases, a reference to a subsection of [Terminology Service Types](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/4-terminology-service-types.md), implies a requirement for all services marked as ***Required*** in that subsection. However, where a reference is followed by a bulleted list, that list specifies the specific terminology services required. Some of the specific services listed as required for an *Optional* practical requirement may be marked as ***Recommended*** in the referenced subsection.
**\*Dependencies:** This columns contains references to services on which a *Required Terminology Service* depends. This column does not restate dependencies on services listed as required service or additional dependencies for essential requirements listed in earlier rows.
A full list of the dependencies of each terminology service is provided in the relevant subsection of [Terminology Service Types](/snomed-ct-practical-guides/snomed-ct-terminology-services-guide/4-terminology-service-types.md).
{% endhint %}
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-terminology-services-guide/3-terminology-service-use-cases.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.