...
A key decision when designing any solution intended to provide to SNOMED CT is whether it should support import files from the
, the current
or both. The determining factor when considering these options is the range of SNOMED CT versions that to which the solution needs to provide access.
| Caption reference |
|---|
| CapRefId | release-types-andtype-import-options-to-support-version-access-requirements |
|---|
| CapRefType | Table |
|---|
|
identifies the release type import options that can be used to meet particular requirements to for access to different sets of SNOMED CT versions. The release type options are summarized in the sections following this table.
| Caption label |
|---|
| CapId | release-types-andtype-import-options-to-support-version-access-requirements |
|---|
| CapType | Table |
|---|
|
Release Type Import Options to Support Version Access Requirements |
| Potential Use Cases | Requirements for access to SNOMED CT versions | Release Type Import Options | Notes |
- Clinical application (for search and data entry)
- SNOMED CT browser (to access current version)
| Access to the current version of SNOMED CT only | - Recommended:
| Link to heading |
|---|
| Heading | Import Snapshot Release Only |
|---|
|
|
|
| Access to the current version of SNOMED CT and full details of changes since the previous version | - Recommended:
| Link to heading |
|---|
| Heading | Import Full and Current Snapshot Release |
|---|
|
- Minimal:
| Link to heading |
|---|
| Heading | Import Current and Previous Snapshot Release |
|---|
|
- Alternative:
| Link to heading |
|---|
| Heading | Import Full Release Only |
|---|
|
| Full details of changes since the previous version requires access to the previous versions of all components that were changed in the current release. As a result the same release type import options apply to both these sets of requirements | Footnote Macro |
|---|
In theory, the first requirement for full details of changes could be met by a trimmed version of the previous snapshot from which rows that are unchanged in the current snapshot have been removed. However, this would complicate both the import process and the process or querying the data. |
. |
| Access to the current version of SNOMED CT and one previous version |
| Access to the current version of SNOMED CT and more than one previous version | - Recommended:
| Link to heading |
|---|
| Heading | Import Full and Current Snapshot Release |
|---|
|
- Alternative:
| Link to heading |
|---|
| Heading | Import Full Release Only |
|---|
|
| If access to more than two versions is required, it is easier to support access to all versions. As a result the same release type import options apply to both these sets of requirements | Footnote Macro |
|---|
In theory, requirements for a limited set of previous version views could also be met by importing multiple snapshot releases. However, importing a snapshot uses roughly 80% of the disk space. Performance advantages may in some cases make this approach worthwhile for two versions but it is not a scalable approach. |
. |
- Analytics / Reporting application (to access historical records)
- SNOMED CT browser (to access previous versions)
| Access to the current version of SNOMED CT and all previous versions |
Import Current Snapshot Release Only
...