> 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/4-logical-design.md).

# Logical Design

The logical design of a SNOMED CT extension is technically consistent with that of the International Edition. Both represent and version SNOMED CT components and reference sets in release files that conform to the Release Format 2 specification. This makes it easier for consumers of the International Edition to implement extensions. The image below illustrates the logical design of a typical SNOMED CT local edition and its relationship to the associated local extension, National Edition and International Edition.

<figure><img src="https://3979592733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3RKZIWpWFT0ocCgNT16E%2Fuploads%2Fgit-blob-a1e51e05ce32219768372caf3e43bd57985bb838%2F57815012.png?alt=media" alt=""><figcaption><p>Logical design of a SNOMED CT local edition</p></figcaption></figure>

Every SNOMED CT extension includes one or more modules, and each module contains either SNOMED CT components or reference sets (or both). Modules may be dependent on other modules. A national or local extension uses a namespace identifier issued by SNOMED International to ensure that all extension components can be uniquely identified (across all extensions). A SNOMED CT edition includes the contents of a focus module together with the contents of all the modules on which it depends. This includes the modules in the International Edition and possibly other modules from a national and/or local extension.

The following subsections explain this logical design in more detail:

* [Namespaces](/snomed-ct-practical-guides/snomed-ct-extension-guide/4-logical-design/4.1-namespaces.md)
* [Modules](https://github.com/SNOMED-Documents/extension-guide/blob/main/4%20logical-design/4.2%20modules)
* [Extensions](https://github.com/SNOMED-Documents/extension-guide/blob/main/4%20logical-design/4.3%20extensions)
* [Editions](https://github.com/SNOMED-Documents/extension-guide/blob/main/4%20logical-design/4.4%20editions)
* [Release Packages](/snomed-ct-practical-guides/snomed-ct-extension-guide/4-logical-design/4.5-release-packages.md)

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Extension+Guide&#x26;entry.670899847=Logical%20Design" 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-practical-guides/snomed-ct-extension-guide/4-logical-design.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.