URI Standard

SNOMED Documentation Search

SNOMED CT Document Library

    Loading...

Versions Compared

Old Version 2

changes.mady.by.user David Markwell

Saved on

compared with

New Version 3

changes.mady.by.user David Markwell

Saved on

Key

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

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

Footnote Macro

While there may be additional files associated with a release, it is only the Module content which affects the computable meaning of a 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

(MDRS) tracks the explicit dependencies between a version of a Module and all the versioned Modules it depends on, a Module Id
Footnote Macro

This is the identifier of the Module 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.

is a natural identifier for an Edition. When combined with a Timestamp corresponding to a sourceEffectiveTime appearing in the MDRS, this unambiguously identifies a Version of an Edition.

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

http://snomed.info/sct/{sctid}

http://snomed.info/sct/{sctid}/version/{timestamp}

Note, while it would be possible to extend this pattern to support multiple root Modules, each with their own sourceEffectiveTime, this introduces non-trivial complexities. For example, the 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.

Anchor
_Toc247737261
_Toc247737261
Examples

...