Page History
| Anchor | ||||
|---|---|---|---|---|
|
The 900000000000534007 $$ Module dependency reference set $$
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set| |
| Anchor | ||||
|---|---|---|---|---|
|
The Module dependency reference set is a String (data type) - String reference set (data type) which is used to represent dependencies between modules , taking account of module versioning. Its structure is shown in the following table.
|
|
| |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Field | Data type | Purpose | |||||||||||||||||||
A 128 bit unsigned | integerInteger (data type), uniquely identifying this | reference set member . Different versions of a reference set member share the same id (field) but have different | effectiveTimeseffectiveTime (field). This allows a reference set member to be modified or made | inactive active (field) (i.e. removed from the active set) at a specified time. | |||||||||||||||||
The inclusive date or time at which this version of the identified | reference set member became the current version. The current version of this | reference set member at time T is the version with the most recent effectiveTime (field) prior to or equal to time T . | |||||||||||||||||||
The state of the identified | reference set member as at the specified effectiveTime (field) . If active (field) = 1 (true) the | reference set member is part of the current version of the set, if active (field) = 0 (false) the | reference set member is not part of the current version of the set. | ||||||||||||||||||
Identifies the | SNOMED CT module that contains this | reference set member as at the specified effectiveTime (field) . The value must be a | subtype of 900000000000443000 $$ Module (core metadata concept) $$ of
| hierarchy . In this | reference set, moduleId (field) also refers to the dependent source | module. Thus each | module contains the rows of the | 900000000000534007 $$ Module dependency reference set $$
| modules . | ||||||||||||
Identifies the | reference set to which this | reference set member belongs. In this case, set to | 900000000000534007 $$ Module dependency reference set $$
| ||||||||||||||||||
| SCTID | The identifier of a target | module on which the dependent | module (identified by moduleId (field)) depends. Thus must be a | subtype of 900000000000443000 $$ Module (core metadata concept) $$ .of
| |||||||||||||||||
| Time | The effective time of the dependent source | module (identified by moduleId (field)). This specifies a version of that | module, consisting of all | components that have the same moduleId (field) as this | refset member in their states as at the specified targetEffectiveTime (field) . | ||||||||||||||||
The effective time of the target | module required to satisfy the dependency (identified by referencedComponentId (field)). This specifies a version of that | module, consisting of all | components with the moduleId (field) specified by referencedComponentId (field) in their states as at the specified targetEffectiveTime (field) . |
| Anchor | ||||
|---|---|---|---|---|
|
Module version dependencies are represented using a single 900000000000534007 $$ Module dependency reference set $$
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set| |
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set (foundation metadata concept)| |
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 900000000000534007 $$ Module dependency reference set $$
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set| |
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 not transitive and this means that dependencies cannot be inferred from a chain of dependencies. If module-A depends on module-B and module-B depends on module-C, the dependency of module-A on module-C must still be stated explicitly.
Any release should consist of a set of module versions that are certified as being compatible. Each release should also identify other module versions that it is dependent on even when these are outside the scope of the release. For example, the dependencies of modules in an Extension on the International Release must be stated.
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 (field) and the version of the module on which it depends is specified by the targetEffectiveTime (field).
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 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.
| Anchor | ||||
|---|---|---|---|---|
|
The following metadata in the "Foundation metadata concept " hierarchy supports this reference set :
Anchor _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__6 _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__6 Anchor _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__5 _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__5
$$Scg expression ShowParts id+term 900000000000454005
$$|Foundation metadata concept
|Anchor _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__e _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__e
$$Scg expression ShowParts id+term 900000000000455006
$$|Reference set
|Anchor _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__8 _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__8
900000000000534007 $$ Module dependency $$Scg expression ShowParts id+term 900000000000534007|Module dependency|
Figure 17. Module Dependency Reference Set in the Metadata Hierarchy
Each component within a SNOMED CT release references a moduleId (field). This is the module that the component is currently mastered in (from the effectiveTime (field) held on the component record). A module is simply a collection of 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 extension that it is responsible for into one or more modules, in a way that best fits its business needs.
A module is modeled by a descendant of 900000000000443000 $$ Module $$ of
| Scg expression | ||
|---|---|---|
| ||
900000000000443000|Module| |
| Scg expression | ||
|---|---|---|
| ||
900000000000443000|Module| |
| Scg expression | ||
|---|---|---|
| ||
900000000000445007|IHTSDO maintained module| |
| Scg expression | ||
|---|---|---|
| ||
900000000000443000|Module| |
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set| |
At the point of release, if any component within a module has changed, then a new row will be added to 900000000000534007 $$ Module dependency reference set $$
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set| |
Each component will be in one, and only one component . The module that a component is mastered in may change over time, and when this happens, the component's moduleId (field) field will be updated (in the usual way by appending a row for the component).
Each module will be in one and only one extension . Modules will not straddle extensions . The extension that a module resides in is defined by the SCTID (data type) of the module. A module may not move from one extension to another over time. If the components within a module are to be moved to another extension , then a new module must be created within the destination extension to host the components that are to be transferred.
There may be more than one module in an extension .
| Anchor | ||||
|---|---|---|---|---|
|
The table below shows the descriptor that defines the structure of the 900000000000534007 $$ Module dependency reference set $$
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set| |
| 900000000000534007 $$ Module dependency $$
|
|
|
|
| |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
refsetId | referencedComponentId (Referenced component) | attributeDescription (Attribute description) | attributeType (Attribute type) | attributeOrder (Attribute order) |
| |||||||||||||||||||||||||
0 |
| |||||||||||||||||||||||||||||
1 |
| |||||||||||||||||||||||||||||
|
|
|
| 0 |
| |||||||||||||||||||||||||
|
|
|
| 1 |
| |||||||||||||||||||||||||
|
|
|
| 900000000000475002 $$ Time $$ | 2 |
|
Note: The table above omits the initial four columns of data present in the release file. These follow the standards versioning pattern id (field), effectiveTime (field), active , moduleId(field), active (field). Additionally, to aid understanding, the table above also shows the term from one of the descriptions associated with each of the identified concept . The release file only contains the identifier .
| Anchor | ||||
|---|---|---|---|---|
|
The table below holds example entries for the 900000000000534007 $$ Module dependency reference set $$ in a snapshot view
| Scg expression | ||
|---|---|---|
| ||
900000000000534007|Module dependency reference set| |
This SNOMED CT International Release contains three modules:
Anchor _6d6f9e33-8512-41ca-a84f-e1ce5e2d480b__u _6d6f9e33-8512-41ca-a84f-e1ce5e2d480b__u
900000000000012004 $$ SNOMED CT model component $$Scg expression
which has no dependencies;ShowParts id+term 900000000000012004|SNOMED CT model component|
900000000000207008 $$ SNOMED CT core $$Scg expression
which depends on the 900000000000012004 $$ SNOMED CT model component $$ ; andShowParts id+term 900000000000207008|SNOMED CT core|
; andScg expression ShowParts id+term 900000000000012004|SNOMED CT model component|
449080006 $$ SNOMED CT to ICD-10 rule-based mapping module $$ which depends on both the other modules.Scg expression ShowParts id+term 449080006|SNOMED CT to ICD-10 rule-based mapping module|
In this case all the 2014-01-31 modules depend on 2014-01-31 versions of the other modules. However, in some case a module may depend on an earlier version of another model (e.g. an extension module may be releases after the SNOMED CT International Release to which it applies).
Dependencies are not transitive. The fact that 449080006 $$ SNOMED CT to
| Scg expression | ||
|---|---|---|
| ||
449080006|SNOMED CT to ICD-10 rule-based mapping module |
| |
| Scg expression | ||
|---|---|---|
| ||
900000000000207008|SNOMED CT core| |
| Scg expression | ||
|---|---|---|
| ||
900000000000012004|SNOMED CT model component| |
| 900000000000534007 $$ Module dependency $$
|
|
|
|
| ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
moduleId | refsetId | referencedComponentId (Dependency target) | sourceEffectiveTime (Source effective time) | targetEffectiveTime (Target effective time) | |||||||||||||||||||
| |||||||||||||||||||||||
20140131 | 20140131 | ||||||||||||||||||||||
449080006 $$ SNOMED CT to ICD-10 rule-based mapping module $$ | 20140131 | 20140131 | |||||||||||||||||||||
|
|
| 20140131 | 20140131 | |||||||||||||||||||
|
|
| 20140131 | 20140131 | |||||||||||||||||||
|
|
| 449080006 $$ SNOMED CT to ICD-10 rule-based mapping module $$ | 900000000000207008 $$ SNOMED CT core $$ | 20140131 | 20140131 |
Note: The tables above omit the initial three columns of data present in the release file. These follow the standards versioning pattern id (field), effectiveTime (field), active (field). Additionally, to aid understanding, the tables above also show the term from one of the descriptions associated with each of the identified concept . The release file only contains the identifier .
Overview
Content Tools
Apps