Each
| Gloss |
|---|
| Space | true |
|---|
| t | SNOMED CT component |
|---|
|
is managed and maintained in a identified by its field.| Glossary include |
|---|
| Gloss | SNOMED CT module |
|---|
| Suffix | is defined as |
|---|
| Def | inline |
|---|
| Example | true |
|---|
| Note | true |
|---|
| Prefix | A |
|---|
|
A moduleId (field) field, assigned to each component, helps identify the origin of content and dependencies in a release. This enables release centers to compose a unified release from a number of different modules, yet still identify the origin of content within the release. For example, module ids may be used to differentiateInternational content, Australian Medicines terminology and Pathology content within the Australian.
Each component within areferences a moduleId (field). This is the module in which the component is currently maintained. A module is simply a collection ofthat are maintained as a unit by a single organization. It is the organization 's responsibility to organize the components in eachthat it is responsible for into one or more modules, in a way that best fits its business needs.