> 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-specifications/snomed-ct-release-file-specification/snomed-ct-identifiers/6.9-the-namespace-hierarchy.md).

# The Namespace Hierarchy

SNOMED CT core release files include metadata concepts that represent each of the allocated namespace-identifiers.

A namespace concept has the following characteristics:

* It is a subtype child of [370136006 |Namespace concept|](http://snomed.info/id/370136006)
* The fully specified name of the concept has the term
  * **Extension Namespace** *{nnnnnnn}***(namespace concept)**
* A synonym associated with each concept has the term
  * **Extension Namespace** *{nnnnnnn}*
* Where appropriate further synonyms may be included to identify the nature of the responsible organization.

{% hint style="info" %}
In the terms shown above *{nnnnnnn}* is the seven digit namespace identifier of the responsible organization.
{% endhint %}

{% hint style="warning" %}
[Visit our Namespace registry](https://cis.ihtsdotools.org/info)
{% endhint %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Release+File+Specification&#x26;entry.670899847=The%20Namespace%20Hierarchy" 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-ct-specifications/snomed-ct-release-file-specification/snomed-ct-identifiers/6.9-the-namespace-hierarchy.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.