> 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-core-table.md).

# snomed ct core table

## SNOMED CT core table

**This is a synonym for SNOMED CT core file.**

## SNOMED CT core file

A distribution file used to represent the main SNOMED CT components (concepts, descriptions and relationships).

#### Notes

* Previously, the term *core* was also used to refer to the content of the SNOMED CT International Release, but this usage is deprecated.
* The [SNOMED CT Affiliate License](http://snomed.org/license) agreement contains a specific legal definition of the term "SNOMED CT Core", which includes all content controlled, maintained and distributed by SNOMED International.

## Alternatives

* **Core file**
* **Core table**
* **SNOMED CT core**
* **SNOMED CT core table**

## **References**

* [SNOMED CT Affiliate License](http://snomed.org/license)

<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%20core%20table" 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-core-table.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.