> 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/support-terminology-authoring-and-review.md).

# Support Terminology Authoring and Review

This section identifies terminology services required to support the authoring and review of SNOMED CT content. This includes the creation and editing of concepts, descriptions, relationships, and reference sets. The terminology services described in this section are primarily used by terminology authors and reviewers working in terminology development environments. However, some of these services may also be used by applications that need to validate terminology content or provide terminology editing capabilities.

## Services Required to Support Terminology Authoring and Review

The table below shows a summary of the terminology services required to support terminology authoring and review processes.

<table data-full-width="true"><thead><tr><th width="385.26953125">Practical Requirement</th><th width="350.671875">Required Services</th><th>Dependencies</th><th data-hidden>Status</th></tr></thead><tbody><tr><td>Enable the selection of SNOMED CT edition and version to be used.<br><br>REQUIRED</td><td><a href="/pages/kpefykqjd3qpJgDShabI">Select Edition and Version</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Get concepts, descriptions, and relationships for review and editing.<br><br>REQUIRED</td><td><a href="/pages/pySRvLGt4wrX5zGq2ICH">Get a Concept, Description or Relationship</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Get terms for concepts to display in terminology editing interfaces.<br><br>REQUIRED</td><td><a href="/pages/qXxq9DcJPVBrudWhboRF">Get Terms for a Concept</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Get concept definitions for review and validation.<br><br>REQUIRED</td><td><a href="/pages/QDu79PNinoxDs3BVXZyt">Get Definition of a Concept</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Test concept subsumption relationships during authoring and review.<br><br>REQUIRED</td><td><a href="/pages/cGdAXCVg9x265cHu96h0">Get and Test Concept Subtypes and Supertypes</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Test reference set membership during authoring and review.<br><br>REQUIRED</td><td><a href="/pages/tWK3Zw3o0VDKq0xiw7Ba">Get and Test Reference Set Membership</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Validate expression constraints during authoring and review.<br><br>REQUIRED</td><td><a href="/pages/NHKUZ8RG1lMgYAYKUgC5">Validate and Apply Expression Constraints</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Find concepts for use in terminology authoring and review.<br><br>REQUIRED</td><td><a href="/pages/1Q6WhIe0nXJoVISkexL1">Find Concepts</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Get concept model rules to ensure proper authoring.<br><br>REQUIRED</td><td><a href="/pages/jxoD7d8OBuXCXQiGXicw">Get Concept Model Rules</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Validate concept definitions and expressions during authoring.<br><br>REQUIRED</td><td><a href="/pages/OycHuOnoGL4jA8YCCxy2">Validate Concept Definitions and Expressions</a></td><td>N/A</td><td>REQUIRED</td></tr><tr><td>Test expression subsumption during authoring and review.<br><br>OPTIONAL</td><td><a href="/pages/TcaXmYu9N8fqf0crhKXx">Test Expression Subsumption</a></td><td>N/A</td><td>OPTIONAL</td></tr><tr><td>Get reference set data for review and editing.<br><br>OPTIONAL</td><td><a href="/pages/YFYLYgDu4eHrmIx9sFL8">Get Data from a Reference Set</a></td><td>N/A</td><td>OPTIONAL</td></tr><tr><td>Get mapping data for review and editing.<br><br>OPTIONAL</td><td><a href="/pages/igLzXjwIqAPvVOV6JLdX">Get Mapping Data</a></td><td>N/A</td><td>OPTIONAL</td></tr></tbody></table>

{% hint style="info" %}
**Note:** The terminology services described in this section provide the foundation for terminology authoring and review. However, actual terminology editing applications typically require additional functionality beyond these services, such as:

* User interface components for editing terminology content
* Workflow management for authoring and review processes
* Version control and change tracking
* Integration with terminology classification engines
* Export and import capabilities for terminology content

These additional capabilities are outside the scope of this guide and are typically provided by specialized terminology authoring tools.
{% endhint %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Terminology+Services+Guide&#x26;entry.670899847=Support%20Terminology%20Authoring%20and%20Review" 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-terminology-services-guide/3-terminology-service-use-cases/support-terminology-authoring-and-review.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.