> 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-extension-guide/5-key-steps/5.3-assessing-requests/5.3.2-constraints-on-concept-requests/5.3.2.1-top-level-concepts-and-clinical-concepts.md).
# Top Level Concepts and Clinical Concepts
## Top Level Concepts
| **Hierarchy** | [138875005 \| SNOMED CT Concept (SNOMED RT+CTV3)\|](http://snomed.info/id/138875005) |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Purpose** | The immediate subtype children of the root concept represent the most general types of SNOMED CT concepts. |
| **Concept Addition Rules** | It is strongly recommended that new top level concepts (i.e. direct subtype children of the root concept) are *not added* in an extension. |
| **Additional Notes** | |
## Top Level Clinical Hierarchies
| **Hierarchies** | All direct subtype children of [138875005 \| SNOMED CT Concept (SNOMED RT+CTV3)\|](http://snomed.info/id/138875005) except [900000000000441003 \| SNOMED CT Model Component (metadata)\|](http://snomed.info/id/900000000000441003) . |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Purpose** | These concepts represent a distinct type of clinical concept |
| **Concept Addition Rules** | Subtype descendants of the top level clinical concepts may be added in an extension. |
| **Additional Notes** | Concepts added in these hierarchies should conform with:
- Concept model rules applicable to the relevant concept domain
- Quality standards applicable to all SNOMED CT clinical content.
These concepts should be classified to generate a set of inferred relationships in necessary normal form, for inclusion in the extension distribution files.
|
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-extension-guide/5-key-steps/5.3-assessing-requests/5.3.2-constraints-on-concept-requests/5.3.2.1-top-level-concepts-and-clinical-concepts.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.