A moduleId
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 differentiate
International content, Australian Medicines terminology and Pathology content within the Australian
.
Each component within a
| Gloss |
|---|
| Space | true |
|---|
| t | SNOMED CT release |
|---|
|
references a
moduleId . This is the module in which the component is currently maintained. A module is simply a collection of
| Gloss |
|---|
| Space | true |
|---|
| t | SNOMED CT components |
|---|
|
that are maintained as a unit by a single organization. It is the organization 's responsibility to organize the components in each
that it is responsible for into one or more modules, in a way that best fits its business needs.