> 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-module.md).

# snomed ct module

## SNOMED CT module

A group of SNOMED CT components and/or reference set members managed, maintained, and distributed as a unit.

#### Notes

* Components and reference set members that are part of the same *module* share the same moduleId "Reference term: moduleId (field)") value.
* All *modules* , except the [900000000000012004 | SNOMED CT model component module|](http://snomed.info/id/900000000000012004) , have dependencies on other *modules* specified by the Module Dependency Reference Set.
  * components and reference set members, that are part of the same *module,* share the same moduleId "Reference term: moduleId (field)") value.
  * components and reference set members are part of only one *module* , at any given time.
* The organization responsible for maintaining an extension must:
  * create and maintain at least one *module* identified by a *moduleId* that it has created;
  * apply a *moduleId* that it has created to all components and reference set members in its *extension* ;
  * manage and distribute information about the dependencies of its *modules* in accordance with SNOMED CT specifications.
* The organization responsible for maintaining an extension may:
  * create and maintain multiple *modules* ;
  * organize its components and reference set members within the modules it manages in a way that best meets its business needs;
  * move a component or reference set member between its *modules* by creating a revised version of that component or reference set member with a different *moduleId*(It is then part of the new *module* from the *effectiveTime* of the revised version).
* Components and reference set members may be moved between *modules* maintained by different organizations. However, such moves must only be made:
  * with the consent of the organizations responsible for both the source and target modules; and
  * in accordance with rules specified by SNOMED International.

## Alternatives

* **Module**

##

<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%20module" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/snomed-international-documents/snomed-ct-glossary/s/snomed-ct-module.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.