...

The

Concept
t 900000000000534007|Module dependency reference set|

represents dependencies between different

Gloss
t SNOMED CT

release

Gloss
t modules

. In each case, the dependency indicates which targetEffectiveTime

Specref
RefType (field) t targetEffectiveTime

of each particular

Gloss
t module

a given sourceEffectiveTime

Specref
RefType (field) t sourceEffectiveTime

of the dependent

Gloss
t module

requires.

...

The

Gloss
t Module dependency reference set

is a String

Specref
RefType (data type)

- String

t String

-

Specref
RefType (data type) t String

Gloss
t reference set

which is used to represent dependencies between

Gloss
t modules

, taking account of

Gloss
t module

versioning. Its structure is shown in the following table.

Anchor
_7da5ff8f-9913-478c-8b35-8df009e328e9 _7da5ff8f-9913-478c-8b35-8df009e328e9

Notes on usage

...

It is the responsibility of the organization owning and maintaining a dependent module to identify all modules on which it depends. They do this by adding rows to the

Concept
t 900000000000534007|Module dependency reference set|

within the dependent module. Because these added member must be in the dependent module, the moduleId

Specref
RefType (field) t moduleId

of the

Gloss
t reference set

member record is also the identifier of the dependent (source) module. The target module on which the source module depends is identified by the referencedComponentId (field)

Specref
RefType (field) t referencedComponentId

.

A module version may depend on one or more other module versions, and many module versions may have a dependency on a single module version. Cyclic module version dependencies are not allowed. If module-A depends on module-B, then module-B cannot depend on module-A.

...

Dependencies are specified between module versions, not just dependencies between modules. Therefore, it is possible to specify a dependency from a module released on one date to an earlier version of another module. The version of the dependent module is specified by the sourceEffectiveTime

Specref
RefType (field) t sourceEffectiveTime

and the version of the module on which it depends is specified by the targetEffectiveTime

Specref
RefType (field) t targetEffectiveTime

.

Note: Current practice assumes the refset.id column contains the same identifier for all versions of the dependencies between the same pair of modules. This approach means that at any given time only one version of each module has effective dependencies. Therefore, to review the dependencies of an earlier version, a snapshot for an earlier time must be checked. An alternative approach has been suggested by some people in which a new identifier is allocated to each dependency of each module. This would then mean that all past dependencies would be visible in a snapshot view. It would also mean that it would be possible release updated dependencies for an existing module version while also releasing more up-to-date versions of the same module with different dependencies. This added flexibility comes at the price of additional complexity and for the time-being the

Gloss
t International Release

continues to use the simpler approach in which each new version of a dependency supersedes the dependency between earlier versions of the same pair of modules.

...

Each component within a

Gloss
t SNOMED CT release

references a moduleId

Specref
RefType (field) t moduleId

. This is the

Gloss
t module

that the component is currently mastered in (from the effectiveTime

Specref
RefType (field) t effectiveTime

held on the component record). A module is simply a collection of

Gloss
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

Gloss
t extension

that it is responsible for into one or more modules, in a way that best fits its business needs.

...

At the point of release, if any

Gloss
t component

within a module has changed, then a new row will be added to

Concept
t 900000000000534007|Module dependency reference set|

for the module's

Gloss
t concept

, with the effectiveTime (field)

Specref
RefType (field) t effectiveTime

set to the date of the new release, irrespective of whether the other fields in the module

Gloss
t concept

record itself have changed. The updated |Module|

Gloss
t concept

record identifies that some components within the module have been updated in this release. Where no components within a module have been updated, then a new module record will not be added and the module's effectiveTime

Specref
RefType (field) t effectiveTime

field will not change from the previous release.

Each

Gloss
t component

will be in one, and only one

Gloss
t component

. The module that a component is mastered in may change over time, and when this happens, the component's moduleId

Specref
RefType (field) t moduleId

field will be updated (in the usual way by appending a row for the component).

Each module will be in one and only one

Gloss
t extension

. Modules will not straddle

Gloss
t extensions

. The

Gloss
t extension

that a module resides in is defined by the SCTID

Specref
RefType (data type) t SCTID

of the module. A module may not move from one

Gloss
t extension

to another over time. If the components within a module are to be moved to another

Gloss
t extension

, then a new module must be created within the destination

Gloss
t extension

to host the components that are to be transferred.

...

Note: The table above omits the initial four columns of data present in the release file. These follow the standards versioning pattern

Specref
RefType (field) t id

,

Specref
RefType (field)

, effectiveTime

t effectiveTime

,

Specref
RefType (field)

, active

t active

,

Specref
RefType (field)

, active (field)

t active

. Additionally, to aid understanding, the table above also shows the

Gloss
t term

from one of the

Gloss
t descriptions

associated with each of the identified

Gloss
t concept

. The release file only contains the

Gloss
t identifier

.

...

Note: The tables above omit the initial three columns of data present in the release file. These follow the standards versioning pattern id

Specref
RefType (field)

, effectiveTime

t id

,

Specref
RefType (field)

, active

t effectiveTime

,

Specref
RefType (field) t active

. Additionally, to aid understanding, the tables above also show the

Gloss
t term

from one of the

Gloss
t descriptions

associated with each of the identified

Gloss
t concept

. The release file only contains the

Gloss
t identifier

.