URI Standard

SNOMED Documentation Search

SNOMED CT Document Library

    Loading...

Versions Compared

Old Version 8

changes.mady.by.user David Markwell

Saved on

compared with

New Version 9

changes.mady.by.user David Markwell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Background

A SNOMED CT Edition edition logically consists of the complete set of members of one or more Modulesmodules.

Footnote Macro

While there may be additional files associated with a release, it is only the Module module content which affects the computable meaning of a Concept concept (i.e. , the inferable relationships and subsumption between post coordinated expressions).

Since the Module Dependency Reference Set

Footnote Macro

http://www.snomed.org/tig?t=trg2rfs_spec_module_depend

module dependency reference set (MDRS) tracks the explicit dependencies between a version of a Module module and all the versioned Modules modules it depends on, a Module Id module identifier

Footnote Macro

This is the identifier of the Module Conceptmodule concept, as would be used in the Module Dependency Reference Set. It is not acceptable to use the identifier of a Description associated with a Module module dependency reference set.

is a natural identifier for an Editionedition. When combined with a Timestamp timestamp corresponding to a sourceEffectiveTime appearing in the MDRS, this unambiguously identifies a Version the module identifier can unambiguously identify a version of an Editionedition.

Form

The URIs that identify (unversioned) Editions and Versions unversioned editions (i.e. editions) and versioned editions (i.e. , versioned Editionsversions) take the following respective forms:

...

Note, while it would be possible to extend this pattern to support multiple root Modulesmodules, each with their own sourceEffectiveTime, this introduces would introduce non-trivial complexities. For example, the Modules modules they each depend upon may themselves overlap but have different versions (targetEffectiveTime) in which case the implied content would be inconsistent. The SNOMED CT URI Guide contains additional discussion and guidance on this topic

Examples

The following table shows some examples of URIs for editions and versions.

Caption label
CapIdexamples
CapTypeTable
Examples


ResourceURI

SNOMED CT International Edition

http://snomed.info/sct/900000000000207008

SNOMED CT International Edition, 20130731

http://snomed.info/sct/900000000000207008/version/20130731

SNOMED CT-AU

http://snomed.info/sct/32506021000036107

SNOMED CT-AU, 31 May 2013

http://snomed.info/sct/32506021000036107/version/20130531

SNOMED CT-AU, 30 Nov 2012

http://snomed.info/sct/32506021000036107/version/20121130

SNOMED CT-SE

http://snomed.info/sct/45991000052106

...