When SNOMED CT content is promoted from an extension module into a less dependent module (e.g. the international edition) to enable broader use, specific changes occur in the RF2 files of the associated SNOMED CT releases. In this section, we provide examples of how the relevant RF2 release files are changed when a concept is promoted and explain how the resulting files are used.
SNOMED CT is distributed to users using one of two main approaches:
The diagram below illustrates these two approaches. In each approach, 3 release file types are distributed - the , the and the . Please refer to 5.6.1.2 Packaging and File Naming for more information.
Please note: Delta files have been removed from the SNOMED International release package, but a Delta Generation Tool is available for those who need it. The Delta Generation Tool allows users to create their own Delta between two fixed release dates - you can find it here: https://github.com/IHTSDO/delta-generator-tool/releases.
In the following sections, we illustrate how each of the Concept files would appear both before and after the promotion of the fictitious concept from the to the .
In these examples, we will assume that the was:
We also assume the following dependencies:
In the following section, we will first illustrate the changes using the SNOMED CT edition distribution method. And in the subsequent section, we will illustrate these changes using the SNOMED CT extension distribution method. In both cases, we will consider the impact to all three release file types - the , the and the -
In this section, we illustrate the changes to the release files when promoting a concept using the edition distribute method.
Please note that the id, module and definitionStatusId fields in the RF2 release files contain only the SNOMED CT identifier of the relevant concept. In the example tables below, we have included a synonym for each concept for human readability. |
Concept File - Full (National Edition 20200331) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20180931 | 1 | |||
20200331 | 1 |
Concept File - Full (National Edition 20200931) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20180931 | 1 | |||
20200331 | 1 | |||
20200731 | 1 |
Concept File - Snapshot (National Edition 20200331) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200331 | 1 |
Concept File - Snapshot (National Edition 20200931) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200731 | 1 |
Concept File - Delta (National Edition 20200331) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200331 | 1 |
Concept File - Delta (National Edition) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200731 | 1 |
In this section, we illustrate the changes to the release files when promoting a concept using the extension distribute method.
Please note that the id, module and definitionStatusId fields in the RF2 release files contain only the SNOMED CT identifier of the relevant concept. In the example tables below, we have included a synonym for each concept for human readability. |
Concept File - Full (National Extension 20200331) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20180931 | 1 | |||
20200331 | 1 |
Concept File - Full (International Edition 20200131) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
No rows in the International Edition reference |
Concept File - Full (National Extension 20200931) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20180931 | 1 | |||
20200331 | 1 |
Concept File - Full (International Edition 20200731) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200731 | 1 |
Please note that the of the Virtual Edition (for deployment in systems) can be created by simply combining the rows from the files above (ie all three rows). |
Concept File - Snapshot (National Extension 20200331) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200331 | 1 |
Concept File - Snapshot (International Edition 20200131) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
No rows in the International Edition reference |
Concept File - Snapshot (National Extension 20200931) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200331 | 1 |
Concept File - Snapshot (International Edition 20200731) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200731 | 1 |
Please note that the of the Virtual Edition (for deployment in systems) can be created by combining the two files above and then removing any superseded version of each concept. In this example, the 20200331 version of must be removed from the combined snapshot file, as this has been superseded by the 20200731 version of this concept from the International Edition. |
Concept File - Delta (National Extension 20200331) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200331 | 1 |
Concept File - Delta (International Edition 20200131) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
No rows in the International Edition reference |
Concept File - Delta (National Extension 20200931) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
No rows in the Extension Concept File reference |
Concept File - Delta (International Edition 20200731) | ||||
id | effectiveTime | module | active | definitionStatusId |
---|---|---|---|---|
20200731 | 1 |
Please note that the of the Virtual Edition (for deployment in systems) can be created by simply combining the rows from the files above (ie one row). |