# Module Identification

Each SNOMED CT component is managed and maintained in a module identified by its moduleId field.

A SNOMED CT module is defined as 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 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](/snomed-ct-specifications/snomed-ct-release-file-specification/reference-set-release-file-specification/5.2-reference-set-types/5.2.4-metadata-reference-sets/5.2.4.2-module-dependency-reference-set.md).
  * components and reference set members, that are part of the same *module,* share the same moduleId 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.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Release+File+Specification&#x26;entry.670899847=Module%20Identification" 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-specifications/snomed-ct-release-file-specification/release-types-packages-and-files/3.1-common-features-of-all-release-files/3.1.6-module-identification.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.