> 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-international-documents/snomed-ct-glossary/readme.md).

# SNOMED CT Glossary

## Introduction

The purpose of this document is to serve as a comprehensive glossary of terms and phrases commonly employed within the SNOMED CT community. As an international standard for health terminology, SNOMED CT is utilized by a diverse group of professionals, including clinicians, researchers, and developers, each of whom may encounter unique terms and concepts. This glossary aims to provide clear, precise definitions and explanations, facilitating a deeper understanding and more effective communication among users.

Whether you are new to SNOMED CT or an experienced member seeking to refine your knowledge, this resource will assist you in navigating the complex landscape of health terminology. By demystifying the terminology and concepts associated with SNOMED CT, this glossary helps ensure that users can more effectively engage with the system, fostering collaboration and innovation across the global healthcare community.

{% hint style="info" %} <img src="https://2512162860-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5ePKL1wPtOcE6DS3HJBR%2Fuploads%2F9cpTE3gMKbX6F0crel0V%2FSI_logo.jpg?alt=media&amp;token=d9e5c250-a75e-4443-b9f4-839d406f10b1" alt="" data-size="line">  © Copyright 2026 International Health Terminology Standards Development Organisation, all rights reserved.

This document is a publication of International Health Terminology Standards Development Organisation, trading as SNOMED International. SNOMED International owns and maintains SNOMED CT®.

Any modification of this document (including without limitation the removal or modification of this notice) is prohibited without the express written permission of SNOMED International. This document may be subject to updates. Always use the latest version of this document published by SNOMED International. This can be viewed online and downloaded by following the links on the front page or cover of this document.

SNOMED®, SNOMED CT® and IHTSDO® are registered trademarks of International Health Terminology Standards Development Organisation. SNOMED CT® licensing information is available at <http://snomed.org/licensing>. For more information about SNOMED International and SNOMED International Membership, please refer to [http://www.snomed.org](http://www.ihtsdo.org/) or contact us at [info@snomed.org](mailto:info@ihtsdo.org).
{% endhint %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=SNOMED%20CT%20Glossary" 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-international-documents/snomed-ct-glossary/readme.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.