...
An edition consists of a set of modules (usually maintained by different organizations) that can be used as a standalone terminology solution within a healthcare environment. For this reason, many extension producers choose to publish their extension as an edition (which includes the content on which the extension depends), rather than as a separate extension. As explained in 5.6.1.2 Packaging and File Naming, however, use cases exist for both packaging options.
| Caption reference |
|---|
| CapRefId | generic-edition |
|---|
| CapRefType | Figure |
|---|
|
below illustrates the composition and dependencies of a local edition that is composed of a local extension module and the two international modules.
| Caption label |
|---|
| CapId | generic-edition |
|---|
| CapType | Figure |
|---|
|
The composition of an edition is based on its module dependencies |
The local edition consists of all components and reference set members that belong to the focus module and the two modules on which the focus module depends -
| Concept |
|---|
| ShowParts | term |
|---|
| t | 900000000000207008 |SNOMED CT core module| |
|---|
|
and the
| Concept |
|---|
| ShowParts | term |
|---|
| t | 900000000000012004 |SNOMED CT model component module| |
|---|
|
. As discussed previously, the version specific dependencies must be stated in the
Module Dependency Reference Set.
...
The table below shows some examples of versioned editions of SNOMED CT, with their corresponding focus module, URI and set of included modules.
| Caption label |
|---|
| CapId | -uris-for-versioned-editions-of-snomed-ct |
|---|
| CapType | Table |
|---|
|
URIs for versioned editions of SNOMED CT |
Please note that a versioned edition is a logical composition of modules, and does not necessarily correspond to a single release package. For more information on release packages, please refer to 4.5 Release Packages and 5.6.1.2 Packaging and File Naming.
...
If a situation arises in which an extension has two equally dependent modules, then a new focus module may need to be created, with dependencies defined to all other modules in the edition. In this case, the focus module may contain only the components and reference set members used to define the module concept itself and its dependencies. below
| Caption reference |
|---|
| CapRefId | most-dependent-module |
|---|
| CapRefType | Figure |
|---|
|
below illustrates a situation in which two (equally dependent) sibling modules exist - national module A and national module B - which are both dependent on the
| Concept |
|---|
| ShowParts | term |
|---|
| t | 900000000000207008 |SNOMED CT core module| |
|---|
|
and the
| Concept |
|---|
| ShowParts | term |
|---|
| t | 900000000000012004 |SNOMED CT model component module| |
|---|
|
, and are not dependent on each other. To form a national edition, which contains both national module A and national module B, a new focus module must be created
that t hat is dependent on all other modules in the edition. The concept id of the new focus module is then used in the URI of the national edition that contains both national module A and national module B.
| Caption label |
|---|
| CapId | most-dependent-module |
|---|
| CapType | Figure |
|---|
|
Creating a new focus module to represent a national edition |