Anchor |
---|
| _0aca28a6-c19b-4c5b-be07-92c3a9cd7524 |
---|
| _0aca28a6-c19b-4c5b-be07-92c3a9cd7524 |
---|
|
Purpose
The
scg-expressionShowPartsid+term | 900000000000534007|Module |
|
represents dependencies between different
release
. In each case, the dependency indicates which
targetEffectiveTime (field) of each particular
a given
sourceEffectiveTime (field) of the dependent
requires.
Anchor |
---|
| _e5f0fe86-0d58-46d8-b09c-14f66d6c8b80 |
---|
| _e5f0fe86-0d58-46d8-b09c-14f66d6c8b80 |
---|
|
Data structure
The
Gloss |
---|
t | Module dependency reference set |
---|
|
is a
String (data type) -
String (data type) which is which is used to represent dependencies between
, taking account of
versioning. Its structure is shown in the following table.
...
Module version dependencies are represented using a single
scg-expressionShowPartsid+term | 900000000000534007|Module |
|
. Thus all module dependency rows have the same refsetId (
scg-expressionShowPartsid | 900000000000534007|Module |
|
).
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
Scg expression |
---|
ShowParts | id+term Concept |
---|
t | 900000000000534007|Module |
---|
|
within the dependent module. Because these added member must be in the dependent module, the
moduleId (field) of the
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) .
...
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
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.
...
The following metadata in the "Foundation metadata " supports this
" supports this :
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-expressionShowPartsid+term | 900000000000454005|Foundation |
|
Anchor |
---|
| _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__e |
---|
| _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__e |
---|
|
Scg expression |
---|
ShowParts | id+term | 900000000000455006|Reference |
---|
|
Anchor |
---|
| _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__8 |
---|
| _2bd409bd-1d1d-43b0-a9d8-08068a1b3651__8 |
---|
|
- scg-expressionShowParts
id+term | 900000000000534007|Module |
|
Figure 17. Module Dependency Reference Set in the Metadata Hierarchy
Each Each component within a
references a
moduleId (field). This is the
that the component is currently mastered in (from the
effectiveTime (field) held on the component record). A module is simply a collection of
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.
A module is modeled by a of
scg-expressionShowPartsid+term | of Concept |
---|
t | 900000000000443000|Module| |
---|
|
in the metadata
. The
Scg expression |
---|
ShowParts | id+term Concept |
---|
t | 900000000000443000|Module| |
---|
|
sub -
is organized by a maintaining organization into a number of groups. For example, all modules maintained by
will be
of
Scg expression |
---|
ShowParts | id+term | 900000000000445007|SNOMED |
---|
|
. The
scg-expressionShowPartsid+term | 900000000000443000|Module| | ShowFormat | inline |
---|
|
models modules maintained by each organization and does NOT model module dependencies. Instead, module dependencies are modeled using the
scg-expressionShowPartsid+term | 900000000000534007|Module |
|
.
At the point of release, if any
within a module has changed, then a new row will be added to
Scg expression |
---|
ShowParts | id+term Concept |
---|
t | 900000000000534007|Module |
---|
|
for the module's
, , with the
effectiveTime (field) set to the date of the new release, irrespective of whether the other fields in the module
record itself have changed. The updated |Module|
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 (field) field will not change from the previous release.
Each
will be in one, and only one
. 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
. Modules will not straddle
. The
that a module resides in is defined by the
SCTID (data type) of the module. A module may not move from one
to another over time. If the components within a module are to be moved to another
, then a new module must be created within the destination
to host the components that are to be transferred.
There may be more than one module in an
.
Anchor |
---|
| _aaeb7fcf-bbe8-4966-a01f-16e4c41c153a |
---|
| _aaeb7fcf-bbe8-4966-a01f-16e4c41c153a |
---|
|
Descriptor
The table below shows the descriptor that defines the structure of the
Scg expression |
---|
ShowParts | id+term Concept |
---|
t | 900000000000534007|Module |
---|
|
.
...
Scg expression |
---|
|
900000000000534007|Module dependency| |
...
...
...
...
...
refsetId
...
referencedComponentId (Referenced component)
...
attributeDescription (Attribute description)
...
attributeType (Attribute type)
...
attributeOrder (Attribute order)
...
...
Scg expression |
---|
|
900000000000456007|Reference set descriptor| |
...
Scg expression |
---|
|
900000000000534007|Module dependency| |
...
Scg expression |
---|
|
900000000000535008|Dependency target| |
...
Scg expression |
---|
|
900000000000461009|Concept type component| |
...
0
...
...
Scg expression |
---|
|
900000000000456007|Reference set descriptor| |
...
Scg expression |
---|
|
900000000000534007|Module dependency| |
...
Scg expression |
---|
|
900000000000536009|Source effective time| |
...
Scg expression |
---|
|
900000000000475002|Time| |
...
1
...
...
Scg expression |
---|
|
900000000000456007|Reference set descriptor| |
...
Scg expression |
---|
|
900000000000534007|Module dependency| |
...
Scg expression |
---|
|
900000000000537000|Target effective time| |
...
Scg expression |
---|
|
900000000000475002|Time| |
...
2
...
refsetId | referencedComponentId (Referenced component) | attributeDescription (Attribute description) | attributeType (Attribute type) | attributeOrder (Attribute order) | |
---|
Concept |
---|
t | 900000000000456007|Reference set descriptor| |
---|
|
| Concept |
---|
t | 900000000000534007|Module dependency| |
---|
|
| Concept |
---|
t | 900000000000535008|Dependency target| |
---|
|
| Concept |
---|
t | 900000000000461009|Concept type component| |
---|
|
| 0 | |
Concept |
---|
t | 900000000000456007|Reference set descriptor| |
---|
|
| Concept |
---|
t | 900000000000534007|Module dependency| |
---|
|
| Concept |
---|
t | 900000000000536009|Source effective time| |
---|
|
| Concept |
---|
t | 900000000000475002|Time| |
---|
|
| 1 | |
Concept |
---|
t | 900000000000456007|Reference set descriptor| |
---|
|
| Concept |
---|
t | 900000000000534007|Module dependency| |
---|
|
| Concept |
---|
t | 900000000000537000|Target effective time| |
---|
|
| Concept |
---|
t | 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 (field), active (field). Additionally, to aid understanding, the table above also shows the
from one of the associated with each of the identified . The release file only contains the . Anchor |
---|
| _6d6f9e33-8512-41ca-a84f-e1ce5e2d480b |
---|
| _6d6f9e33-8512-41ca-a84f-e1ce5e2d480b |
---|
|
Module dependency reference set example The table below holds example entries for the
Concept |
---|
t | 900000000000534007|Module dependency reference set| |
---|
|
in a of the January 2014 Gloss |
---|
t | SNOMED CT International Release |
---|
|
. This
Gloss |
---|
t | SNOMED CT International Release |
---|
|
contains three modules: 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 (field), active (field). Additionally, to aid understanding, the table above also shows the from one of the associated with each of the identified . The release file only contains the . Anchor |
---|
| _6d6f9e33-8512-41ca-a84f-e1ce5e2d480b__u |
---|
| _6d6f9e33-8512-41ca-a84f-e1ce5e2d480b |
---|
|
...
The table below holds example entries for the
Scg expression |
---|
|
900000000000534007|Module dependency reference set| |
in a of the January 2014 . This contains three modules:
...
Scg expression |
---|
|
900000000000012004|SNOMED CT model component| |
...
Scg expression |
---|
|
900000000000207008|SNOMED CT core| |
...
Scg expression |
---|
|
900000000000012004|SNOMED CT model component| |
...
Scg expression |
---|
|
449080006|SNOMED CT to ICD-10 rule-based mapping module| |
...
Concept |
---|
t | 900000000000012004|SNOMED CT model component| |
---|
|
which has no dependencies; Concept |
---|
t | 900000000000207008|SNOMED CT core| |
---|
|
which depends on the Concept |
---|
t | 900000000000012004|SNOMED CT model component| |
---|
|
; and Concept |
---|
t | 449080006|SNOMED CT to ICD-10 rule-based mapping module| |
---|
|
which depends on both the other modules.
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
Gloss |
---|
t | SNOMED CT International Release |
---|
|
to which it applies). Dependencies are not transitive. The fact that
Concept |
---|
t | 449080006|SNOMED CT to ICD-10 rule-based mapping module| |
---|
|
is dependent on Concept |
---|
t | 900000000000207008|SNOMED CT core| |
---|
|
may seem to imply a dependency on Concept |
---|
t | 900000000000012004|SNOMED CT model component| |
---|
|
. However, in practice all dependencies must be explicitly specified, not just immediate dependencies. 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 to which it applies).
Dependencies are not transitive. The fact that
Scg expression |
---|
|
449080006|SNOMED CT to ICD-10 rule-based mapping module| |
is dependent on Scg expression |
---|
|
900000000000207008|SNOMED CT core| |
may seem to imply a dependency on Scg expression |
---|
|
900000000000012004|SNOMED CT model component| |
. However, in practice all dependencies must be explicitly specified, not just immediate dependencies. Anchor |
---|
_6d6f9e33-8512-41ca-a84f-e1ce5e2d480b__1 | _6d6f9e33-8512-41ca-a84f-e1ce5e2d480b__1 | Table 56. Sample content from Scg expression |
---|
|
900000000000534007|Module dependency| |
. | | | | moduleId | refsetId | referencedComponentId (Dependency target) | sourceEffectiveTime (Source effective time) | targetEffectiveTime (Target effective time) |
---|
Scg expression |
---|
| ShowParts | id+term | 900000000000207008|SNOMED |
---|
|
Scg expression |
---|
ShowParts | id+term Concept |
---|
t | 900000000000534007|Module |
---|
| Scg expression |
---|
| ShowParts | id+term | 900000000000012004|SNOMED |
---|
| | 20140131 | 20140131scg |
---|
-expression ShowParts | id+term | scg-expressionShowParts | id+term | 900000000000534007|Module |
|
Scg expression |
---|
ShowParts | id+term Concept |
---|
t | 900000000000012004|SNOMED |
---|
| | 20140131 | 20140131 Scg expression |
---|
| ShowParts | id+term
---|
scg-expression | ShowParts | id+term | 900000000000534007|Module |
|
scg-expression ShowParts | id+term | 900000000000207008|SNOMED |
|
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
from one of the
associated with each of the identified
. The release file only contains the
.