A SNOMED CT Edition logically consists of the complete set of members of one or more Modules.1 Since the Module Dependency Reference Set2 (MDRS) tracks the explicit dependencies between a version of a Module and all the versioned Modules it depends on, a Module Id3 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:
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.
Table 2.1-1: Examples
SNOMED CT International Edition
SNOMED CT International Edition, 20130731
SNOMED CT-AU,31 May 2013
SNOMED CT-AU,30 Nov 2012
|1||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).|
|3||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.|