SNOMED Documentation Search


 Other Documents
Skip to end of metadata
Go to start of metadata

Current Version - Under Revision

Importing a Full view

To provide access to the full view of the content of the SNOMED CT International Release , a terminology server must initially import content from the full release files for the International Release .

The complete content of all the main release files should be imported into the chosen internal representation.

Figure 15. Initial import to create a full view

Tip: The files that form part of a particular release can be identified by pattern matching based on the IHTSDO filenaming conventions (see Identifying release files using regular expressions ).

Updating a Full view

A full view can be updated by one of the following approaches:

  1. Append the content of the relevant

    delta release

    files to a previously created

    full view

    :
    • The delta files contain only the changes since a previous release. Appending the data from these files to the

      full view

      for the previous version creates the

      full view

      for the new version. There is no need to change or delete existing data.

CAUTION:

A delta release must be applied to the immediately previous version. Appending a delta release to earlier versions will result in omission of content and this will lead to significant errors when interpreting the data.

Figure 16. Updating a full view using a snapshot release

  1. Filter the relevant

    full release

    files to generate a

    delta release

    then apply this as in 2 above:

Note: This allows Extensions that are not distributed with delta releases to be processed by a general update process that is optimized to work with delta releases .

Figure 17. Updating a full view using a full release

  1. Use the

    full release

    files to completely replace previously imported data:

Figure 18. Updating a full view by replacement

Tip: The files that form part of a particular release can be identified by pattern matching based on the IHTSDO filenaming conventions (see Identifying release files using regular expressions ).

Importing and updating Extensions for a Full view

To provide access to the full view of one or more Extensions , a terminology server must initially import content from the full release files for each of the required Extensions . Thereafter, the full view of each Extension can be maintained by using any of the techniques described for updating a full view .

When a full view of Extension data is initially imported or subsequently updated care needs to be taken to ensure the relevant versions of the International Release and any other Extensions on which it depends have been imported. Failure to follow do this may lead to errors as a result of references from Extension components to missing or out of date components in the International Release or in another Extension .

A full view may include more recent versions of the International Release than is required to support the Extension . In this case, when the Extension is viewed the International Release can, if necessary, be viewed as it would have been in the version to which the Extension is related. Similarly, if one Extension depends on content in another Extension , the version the Extension on which it depends may be a more recent version.

The table below summarizes the compatibility between the full views of given versions of an Extension and the International Release . It also indicates the ways in which a full view may be used when the latest installed versions are not directly compatible. If one Extension depends on another Extension , the same considerations apply to compatibility between the versions of those Extensions .

Table 5. Compatibility between full views of versions of an Extension and the International Release

 

Relationship between the version of the Extension and the International Edition

Notes on compatibility and usability

Installed International Release is older than the version on which the Extension was based

Incompatible - unless recent Extension content is excluded .

The Extension may include Relationships to concepts that do not exist in this version of the International Release . This will lead to errors that cannot be reconciled while viewing the Extension content.

A system with this mix of installed versions could be safely used by excluding the content of the more recent Extension versions. This can be done by excluding any Extension component -version with an effectiveTime of one of the versions based on a newer International Release . In effect this approach rolls back the Extension to the last Extension that is valid with the installed version of the International Release .

Installed International Release is same version as the one on which the Extension was based

Fully compatible .

This is the version the Extension was created for so it should behave as intended.

Installed International Release is newer than the version on which the Extension was based.

Compatible - subject to appropriate configuration and usage .

The International Edition for this version may include:

  • Additional

    components

    . These will not cause errors because the

    International Release

    does not reference the

    Extension

    and the

    Extension

    content cannot reference

    components

    that did not exist when in the version it was based on.
  • Changes to the state of some

    components

    . These changes may affect the interpretation of some parts of the

    Extension

    .

    However, despite these issues the

    full view

    resulting from this combination can be used in several ways:
  1. Configured to roll-back the

    International Release

    to the version on which the

    Extension

    was based. This can be done with a

    full release

    by creating a virtual view of the

    International Release

    components

    which excludes

    component

    versions with an effectiveTime greater than the version on which the

    Extension

    was based. This type of view is described in more detail in

    Implementing the State-Valid view

    .
  2. Configured to exclude the

    Extension

    . In this case the most recent version of the

    International Release

    can be viewed.
  3. Configured to use those parts of the

    Extension

    that support translation of

    International Release

    content. In this case, the

    Extension

    will enable translated rendering of pre-existing translated content. This would leave new and untranslated

    concepts

    to be rendered in English (or another available language).
  4. Accepting and working within the constraints imposed by the omissions and anomalies noted above. This mode should not be used routinely but may useful for assessing the impact of changes to the

    International Release

    on the

    Extension

    .

Note: The compatibility and usability notes are specific to a full view implementation. Different considerations apply to snapshot and multi- snapshot views .


Feedback