> 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/s/snomed-ct-metadata.md).

# snomed ct metadata

## SNOMED CT metadata

SNOMED CT content (including concepts, descriptions, and relationships) that provides additional information about SNOMED content and derivatives (including reference sets).

#### Notes

* All SNOMED CT metadata concepts are subtypes of [900000000000441003 | SNOMED CT Model Component (metadata)|](http://snomed.info/id/900000000000441003) .
* The top level of the metadata hierarchy represents broad groups of metadata as follows:

Top level of the SNOMED CT metadata hierarchy\
[900000000000441003 | SNOMED CT Model Component (metadata)|](http://snomed.info/id/900000000000441003)

* [106237007 | Linkage concept (linkage concept)|](http://snomed.info/id/106237007)
* [370136006 | Namespace concept (namespace concept)|](http://snomed.info/id/370136006)
* [900000000000442005 | Core metadata concept (core metadata concept)|](http://snomed.info/id/900000000000442005)
* [900000000000454005 | Foundation metadata concept (foundation metadata concept)|](http://snomed.info/id/900000000000454005)

#### Examples

* Concept enumerations use *metadata concepts* to represent values that are applied to particular fields in release files.
* Reference set types and reference set names are represented by *metadata concepts* that are subtypes of [900000000000455006 | Reference set (foundation metadata concept)|](http://snomed.info/id/900000000000455006) .

## Alternatives

* **metadata**

##

<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%20metadata" 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/s/snomed-ct-metadata.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.