> 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/education/snomed-ct-education-editorial-guide/readme/authoring/general-naming-conventions/descriptions.md).

# Descriptions

<mark style="color:$danger;">**This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.**</mark>

A concept has multiple associated *descriptions*.

Each description has a *description type* and a unique numeric *description identifier.*

* Fully specified name (FSN) and synonym (SYN) are description types in SNOMED CT.
* A preferred term (PT) is a synonym that has been marked as preferred in a particular dialect.

Every concept may have only one preferred term in a specific dialect. Two preferred terms for the same language may coexist if they belong to two distinct dialects (e.g. variant US and GB of English language).

### Examples

#### 22490002 | Bleeding of mouth (disorder)|

| Description type | Description                  |
| ---------------- | ---------------------------- |
| FSN              | Bleeding of mouth (disorder) |
| PT               | Bleeding of mouth            |
| SYN              | Bleeding in mouth            |
| SYN - US English | Oral hemorrhage              |
| SYN - GB English | Oral haemorrhage             |
| SYN              | Stomatorrhagia               |

#### 241563001 | Computed tomography of upper limb (procedure)|

| Description type | Description                                   |
| ---------------- | --------------------------------------------- |
| FSN              | Computed tomography of upper limb (procedure) |
| PT               | CT of upper limb                              |
| SYN              | Computed tomography of upper limb             |

#### 32849002 | Esophageal structure (body structure)|

| Description type | Description                           |
| ---------------- | ------------------------------------- |
| FSN              | Esophageal structure (body structure) |
| PT - US English  | Esophageal structure                  |
| PT - GB English  | Oesophageal structure                 |

Disjunctives (for example, *and/or*) should be in lower case.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Descriptions" 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/education/snomed-ct-education-editorial-guide/readme/authoring/general-naming-conventions/descriptions.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.