SNOMED Documentation Search
There are a number of additional aspects features of SNOMED CT that do not have SCTIDs or UUIDs, but which still need a URI for to be identified. URIs are required to identify these additional features to support use cases such as an OWL representation of representing SNOMED CT in OWL (e.g. to identify certain annotations) and for parts of CTS2 such as characteristicTypeIdreferring to SNOMED CT properties (e.g. characteristicTypeId) from other standards (e.g. CTS2). To address these needs requirements we define a general set of URIs identifying the RF2-based properties of Componentscomponents.
The URI space for these properties follows the pattern:
http://snomed.info/field/{tableName}.{fieldName}
Valid table names are as described for Data Files with respect to the _ContentType elementinclude those described as possible values for the content type element in the File Naming Conventions
Footnote Macro |
---|
Release File Specification - section 2.1. SNOMED CT - File Naming Conventions |
in the File Naming Conventions for RF2. Note, these URIs identify the property itself, not the value or values that may be associated with the property.
The following table shows some examples of URIs for SNOMED CT RF2 properties.
Caption label | ||||
---|---|---|---|---|
| ||||
Examples |
Resource | URI |
The definitionSatusId property in the RF2 concept file | http://snomed.info/field/concept.definitionStatusId |
The characteristicTypeId property in the RF2 relationship file | http://snomed.info/field/relationship.characteristicTypeId |
The referencedComponentId property in a RF2 simple reference set file | http://snomed.info/field/refset.referencedComponentId |
The mapTarget property in a RF2 simple map reference set file | http://snomed.info/field/sRefset.mapTarget |
...
Display Footnotes Macro |
---|