...
Note: The SNOMED International glossary 
explains some of these SNOMED CT specific terms.
4.2.1.0.2
...
Versions 
There is no single distribution that contains all defined SNOMED CT codes in all contexts of use. Instead the international release International Edition contains all concepts shared and agreed to be internationally relevant and each national release centre National Release Centre distributes this international release International Edition plus additional national content (to extend that the international set). In addition, other Other release authorities may also be designated. The SNOMED CT URI Specification describes how to unambiguously reference a particular version of a distributionSNOMED CT edition:
http://snomed.info/sct/[sctid]/version/[YYYYMMDD]
where [sctid] is the concept id of that identifies the given SNOMED CT distribution (e.g. 32506021000036107 for Australiaedition (based on the identifier of the most dependent module), and "YYYYMMDD" is the date of release. Examples of sctids that identfy a specific edition are shown in the table below:
| SNOMED CT Edition | sctid |
|---|---|
| International edition | 900000000000207008 |
| Australian extension edition | 32506021000036107 |
| Australian edition (with drug extension) | 900062011000036108 |
| UK clinical edition | 999000021000000109 |
| UK Edition (with drug extension) | 999000031000000106 |
| US edition | 731000124108 |
| US edition (with ICD-10-CM maps) | 5991000124107 |
the tail is the date of release (by custom, this is usually the last day of the month). Note that many implementations are in the habit of simple simply using the date of release in the form YYYYMMDD (e.g. "20140531"), and assuming that the distribution edition is known. However this is not always safe, so implementations that populate the version element must use the URI form.
4.2.1.0.3 Copyright
...
and Licenses
This specification includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org.
4.2.1.0.4 RDF
The IHTSDO SNOMED International URI specifications uses use the namespace http://snomed.info/sct for the code system, and the URI http://snomed.info/id for the individual concepts in the code system. This means that when a SNOMED CT concept is converted from the system::code pair, where the system is http://snomed.info/sct, to the RDF ontological form, the representation is is http://snomed.info/id/[concept-id]. Expressions are represented using the URI pattern http://snomed.info/idscg/[concept-idexpression]. Expressions are represented the same way, except that for this use, expressions Expressions represented in this way SHALL not contain whitespace, terms, or comments.
...
| inactive | boolean | Whether the code is active or not (defaults to false). This is derived from the active column in the Concept file of the RF2 Distribution (by inverting the value) |
| sufficientlyDefined | boolean | True if the description logic definition of the concept includes sufficient conditions (i.e., if the concept is not primitive - found in the value of definitionStatusId in the concept file. This is derived from the definitionStatusId value in the Concept file of the RF2 distribution (i.e. If 900000000000073002 |Sufficiently defined concept definition status| then true). |
| moduleId | code | The SNOMED CT concept id of the module that the concept belongs to. |
| normalForm | string | Generated Normal form expression for the provided code or expression, with terms |
| normalFormTerse | string | Generated Normal form expression for the provided code or expression, conceptIds only |
In addition, any SNOMED CT relationships where the relationship type is subsumed by 246061005 |Attribute (246061005) | automatically become properties. For example, laterality:
...