SNOMED Documentation Search
...
The OWL representation of SNOMED CT makes use of URIs for identifying Concepts, the previously-implicit grouping role, and the ontology itself (i.e., the set of axioms).
The old pattern used for Concepts was
http://www.ihtsdo.org/SCT_{sctid}
which is now replaced by
http://snomed.info/id/{sctid}
The grouping role URI was
http://www.ihtsdo.org/RoleGroup
and is now
http://snomed.info/id/609096000
For the OWL XML representation, the URI was unspecified (the empty string), while for the OWL Functional Syntax representation the URI was (via RDF:about)
and now includes explicit version information
http://snomed.info/sct/{sctid}/version/{timestamp}
When representing SNOMED CT ontologies using OWL 2, both an ontologyURI and a versionURI should be included using the following forms respectively
Footnote Macro |
---|
See OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntaxhttp://www.w3.org/TR/owl2-syntax/#Ontology_IRI_and_Version_IRI |
http://snomed.info/sct/{sctid}
http://snomed.info/sct/{sctid}/version/{timestamp}
...
Resource | URI | Example |
---|---|---|
SNOMED CT Edition | http://snomed.info/sct/{moduleId} | http://snomed.info/sct/900000000000207008 SNOMED CT International Edition |
SNOMED CT Version | http://snomed.info/sct/{moduleId}/version/{effectiveTime} | http://snomed.info/sct/900000000000207008/version/20120131 SNOMED CT International January 2012 Version |
Module | http://snomed.info/module/{moduleId} | http://snomed.info/module/900000000000207008 SNOMED CT Core Module (only) |
A specific release of a Module | http://snomed.info/module/{moduleId}/time/{timestamp} | http://snomed.info/module/900000000000207008/time/20120131 SNOMED CT Core Module (only) with respect to the timestamp 20120131 |
SCTID | http://snomed.info/id/{sctid} | http://snomed.info/id/449650002 |
UUID | http://snomed.info/id/{uuid} | http://snomed.info/id/00000692-31c5-81a8-2e54b488c824 |
Table Field | http://snomed.info/field/{table name}.{field name} | http://snomed.info/field/Relationship.characteristicTypeId |
Map | http://snomed.info/id/{map sctid} | http://snomed.info/id/900000000000498005 A map is just a reference set in a specific format |
Map version | http://snomed.info/sct/{moduleId}/version/{effectiveTime}/id/{map sctid} | http://snomed.info/sct/900000000000207008/version/2012013/id/900000000000498005 |
Refset | http://snomed.info/id/{refset sctid} | http://snomed.info/id/900000000000498005 |
Refset version | http://snomed.info/sct/{moduleId}/version/{effectiveTime}/id/{refset sctid} | http://snomed.info/sct/900000000000207008/version/2012013/id/900000000000498005 |
Role Group | http://snomed.info/id/609096000 | http://snomed.info/id/609096000 |
...
Traditionally, HL7 has used OIDs to identify Code Systems. The OID for SNOMED CT is 2.16.840.1.113883.6.96. This is the OID that should be used for all versions of SNOMED CT and related terminologies (such as the Australian Medicines Terminology) because it identifies the system, i.e., the set of rules for interpreting SCTIDs. Under these rules, any specific SCTID is either defined with respect to a particular SNOMED CT Version, or it is undefined (i.e., not included/mentioned in that version). Furthermore, any given SCTID always identifies the same thing in all versions in which it is defined.
The HL7 specification says: the interpretation of version strings is defined by the Code System (and not by HL7). This means we can use the URI for a Version (versioned Edition) as the version code:
http://snomed.info/sct/{sctid}/version/{timestamp}
For example, here is how a CDA document with an element of CD Data Type might appear:
<xyz code="78835011000036104" codeSystem="2.16.840.1.113883.6.96" codeSystemName="Australian Medicines Terminology (AMT)" codeSystemVersion= "http://snomed.info/sct/900062011000036108/version/20121231" displayName="GANFORT 0.03% / 0.5% eye drops: solution, 3 mL"/> </xyz>
It should be noted that, because the URIs for identifying a specific Version of an Edition can be used to unambiguously determine its content, using these URIs as version numbers works regardless of whether a single OID is used to identify SNOMED CT as a "system" or individual OIDs are assigned for different Editions.
...
Fast Healthcare Interoperability Resources (FHIR™)
Footnote Macro |
---|
and the recommended string template to use for the associated version, substituting in the appropriate module sctid and effective time, is:
http://snomed.info/sct/{sctid}/version/{timestamp}
...