The practical uses of these views are outlined in Table C.1-1.
Table C.1-1: Practical Uses for Different Versioned Views
| View | Uses |
| This view contains all versions of all released components and reference set members.
- It can support all the uses identified in the following rows of this table.
|
| This view contains only the most recent version of all released components and reference set members. - It should be used for data entry.
- It can also be used to support for most types of retrieval and analysis.
- Detailed analysis of past use of concept that have since been made inactive may benefit
from access to previous snapshots.
- It can also be used to generate the current delta view and thus also enables the uses identified for that view.
|
| A retrospective snapshot view has the same features as a current snapshot view but excludes changes made after a certain point in time. - During and immediately after upgrading to a new release version, the previous snapshot
view map be of particular value for determining details of changes.
- Earlier snapshot views can also be valuable when comparing and evaluating results
of analyses which may have been affected by terminology changes.
|
| This view only includes the post change state of components that have changed since the previous release. - It can be used to identify components that have been added or inactivated since the
previous release and this information can be used to check whether updates are needed.
For example, updating, implementation resources such as local subsets, data entry
picklists and queries. These updates may include removing inactive concepts or descriptions
as well as adding relevant newly added concepts and descriptions.
- Note that some aspects of this review process also require access to the previous
current snapshot view.
|
| A retrospective delta has the same features as a current delta view but relates to changes between two earlier dates. - It can be used in conjunction with snapshot views
|