# Essential Reference Information

This section discusses some of the points that should be considered when designing a relational database to provide access to SNOMED CT. It explains the rationale for decisions taken while designing the SNOMED CT example database. It also identifies some other options which, while not implemented in the example database, are worth considering.

Before designing a database to accommodate SNOMED CT, you should refer to the [**SNOMED CT Release File Specification**](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-release-file-specification/)**.** This provides the authoritative documentation about the way that SNOMED CT content is distributed to licensees. The list below picks out the key sections of this guide for those developing solutions that provide access to SNOMED CT.

The section[ Release Types, Packages and Files](/snomed-ct-specifications/snomed-ct-release-file-specification/release-types-packages-and-files/3-release-types-packages-and-files.md) contains the follow chapters that provide essentially information about SNOMED CT Release Packages

* [Common Features of All Release Files](/snomed-ct-specifications/snomed-ct-release-file-specification/release-types-packages-and-files/3.1-common-features-of-all-release-files.md)
* [Release Types](/snomed-ct-specifications/snomed-ct-release-file-specification/release-types-packages-and-files/3.2-release-types.md)
* [Naming Conventions for Release Packages and Files](/snomed-ct-specifications/snomed-ct-release-file-specification/release-types-packages-and-files/3.3-naming-conventions-for-release-packages-and-files.md)
* [Release Package Contents](/snomed-ct-specifications/snomed-ct-release-file-specification/release-types-packages-and-files/3.4-release-package-contents.md)

The section[ Component Release Files Specification](/snomed-ct-specifications/snomed-ct-release-file-specification/component-release-file-specification/4-component-release-files-specification.md) contains the authoritative documentation about the structure of release files containing data that represents SNOMED CT components (concepts, descriptions and relationships).

* [Associations Between Release Files](/snomed-ct-specifications/snomed-ct-release-file-specification/component-release-file-specification/4.1-associations-between-release-files.md)
* [File Format Specifications](/snomed-ct-specifications/snomed-ct-release-file-specification/component-release-file-specification/4.2-file-format-specifications.md)
* [Metadata Hierarchy](/snomed-ct-specifications/snomed-ct-release-file-specification/component-release-file-specification/4.3-metadata-hierarchy.md)

The section [Reference Set Release Files Specification](/snomed-ct-specifications/snomed-ct-release-file-specification/reference-set-release-file-specification/overview.md) contains the authoritative documentation about the structure of release files that represent SNOMED CT reference sets.

* [General Features of Reference Sets](/snomed-ct-specifications/snomed-ct-release-file-specification/reference-set-release-file-specification/overview.md)
* [Reference Set Types](/snomed-ct-specifications/snomed-ct-release-file-specification/reference-set-release-file-specification/5.2-reference-set-types.md)

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SQL+Guide&#x26;entry.670899847=Essential%20Reference%20Information" class="button primary">Provide Feedback</a>


---

# Agent Instructions: 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:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-sql-practical-guide/database-design/4.1-essential-reference-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.