Types of Versioned Views
A versioned view is
a set of component versions and reference set member versions defined by characteristics of their effectiveTimes.
Notes
There are three types of versioned views:
A snapshot view is a view of SNOMED CT that includes the most recent version of all components and reference set members at a specified point in time.
- The current snapshot view is most important versioned view. It will be in constant use during day to day use of the terminology.
- When updating to a new version, access to the previous earlier snapshot view is required to determine the type of change made to each component and reference set member (see 4.9 Identify Changes to the Terminology).
- When reviewing, analyzing or reporting data collected while using earlier versions, access to snapshot views of the terminology at the time of data collection may assist interpretation of any unexpected variations.
A delta view is a view of SNOMED CT that contains only rows that represent changes to components and reference set members since a specified date or between two specified dates in the past.
- When updating to a new version, a delta view identifies components and reference set members that were added, updated or inactivated between to releases. to terminology content (see 4.9 Identify Changes to the Terminology).
- When updating to a new version, a delta view identifies components and reference set members that were added, updated or inactivated between to releases. to terminology content (see 4.9 Identify Changes to the Terminology).
A full view is a view of SNOMED CT that includes all versions of all components and reference set members in a full release.
- The ability to access the current full view may be useful for an organization that does not apply every update of the edition that they use. For example, if they receive data from another organization that includes content that is not in the snapshot view they are using.
- In exceptional circumstances, access to earlier versions of the full view may also be useful for detailed forensic review of data and resolution of anomalies.
Terminology Service Versioned View Options
Table 5.3.2-1 identifies options for the snapshot views that a SNOMED CT terminology server may support and Table 5.3.2-2 identifies the types of delta views that may be supported.
View | Description |
Single snapshot view of an edition | Some terminology services may only support access to a single snapshot view of a specified SNOMED CT edition at a one preset point in time.
In most cases, a terminology service that supports a single snapshot view of a specified edition only needs to import the relevant snapshot release files for that edition2. A single snapshot view of an edition:
|
Multiple snapshot views of an edition | Some terminology services may support access to snapshot views of a specified SNOMED CT edition for a limited number of specified points in time.
A terminology service that supports multiple versioned views of a specified edition can do this in one of two ways:
Access to multiple snapshot views of an edition:
|
All snapshot views of an edition | Some terminology services may support access to snapshot views of a specified SNOMED CT edition at any specified specified point in time.
A terminology service that supports all snapshot views of a specified edition can do this in one of three ways:
A terminology service that supports all snapshot views of a specified edition needs to import the full release files for that edition. Access to all snapshot views of an edition:
|
All snapshot views of a range of different editions 4 | Some terminology services may support access to snapshot views of a range of different SNOMED CT editions at any specified specified point in time.
A terminology service that supports a range of snapshot views of a specified edition needs to import the full release files for all the modules required by one or more of the supported editions. Access to all snapshot views of a range of different editions:
|
View | Description |
Single delta view of changes between current version and previous version of an edition | Some terminology services may only support a single delta view of changes between current version and previous version of an edition. This is useful for reviewing the most recent changes to the terminology. However, a complete review of the impact of those changes also requires access the snapshot view of the previous release, as this is the baseline for the changes shown in the delta. (see 4.9 Identify Changes to the Terminology). |
Multiple delta views of changes between a selected version and the preceding version of the same edition | Multiple delta views of changes between a specified version and the preceding version of the same edition. This is useful for reviewing the changes between earlier releases. It provides an opportunity to retrospectively remedy issues arising from change. However, complete review of the impact of those changes also requires access the snapshot view of the release prior to each delta view, as this is the baseline for the changes shown in the delta. (see 4.9 Identify Changes to the Terminology). |
Configurable delta views of changes to an edition | Configurable delta views of changes to an edition between any two specified points provide a flexible solution that can identify a sequence of changes occurring to one or more components. Fully configurable delta views require access to data for a full release of the edition. This also provides the authoritative source for the starting point for all the changes shown in the delta. |
Configurable delta views of a range of available editions | Configurable delta views of changes to one of a number of editions between any two specified points in time provide additional value in cases where more than one edition is in use. |
Creating and Updating Versioned Views
Creating and Updating Full Views
To enable terminology services to access a full view of a SNOMED CT edition, a server must be able to import a full release of that edition into an appropriate datastore.
To enable access to a more recent full view of a SNOMED CT edition, a server may:
- Import the latest full release as a replacement for the previous full release data; or
- Import the latest delta release and append this data to the previous full release data.
Creating and Updating Snapshot Views
To provide access to the current snapshot view of a SNOMED CT edition, a server may:
- Import the current snapshot release for that edition;
- Selectively import data from the current full release for that edition, including only the most recent versions of each component or reference set member up to and including a specified snapshot time; or
- Enable access to the full view of that edition to be filtered to include only the most recent version of each component prior to a specified snapshot time;
To provide access to more recent snapshot views of a SNOMED CT edition, a server may:
- Use any of the above methods for providing access to a snapshot view for a different date, either in addition to or as a replacement for a previously imported snapshot view; or
- Import the latest delta release and use this to update the previous snapshot view by appending new components and replacing existing components with updated versions.
Creating and Updating Delta Views
To provide access to the delta view for the current version of a SNOMED CT edition, a server may:
Import the delta release for that edition into an appropriate datastore;
- Selectively import data from the current full release for that edition, including only component versions with effectiveTime values that are after the previous release date and are also on or before the current release date;
- Enable access to the full view of that edition to be filtered to include only versions of components with effectiveTime values that are after the previous release date and on or before the current release date.
To provide access to other delta views of a SNOMED CT edition, a server may:
- Use any of the above methods to create delta views between other release dates. In all cases the effectiveTime must be after one release date and on or before the next release date;
- Import the full release and provide delta views by selectively filtering data to ensure the effectiveTime is greater than a specified start date and less than or equal to a specified end date.
- This method can be used to generate configurable delta views between specified dates that may not be directly related to adjacent release dates. In this type of delta view, there may be more than one version of a component with the specified date range. In this case, it may be useful to consider two possible delta views. One including only the most recent change to each component in the specified period and the other including all changes during that period.
Footnotes
Feedback