Search



Versions Compared

Key

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

This section outlines the rationale for distributing an OWL representation of the 

Gloss
tstated view
 of 
Gloss
tconcept definitions
 and provides an overview of the way OWL axioms are represented in 
Gloss
tSNOMED CT release files
.  More detailed information is published separately in the  DOCOWL and the  DOCLPS.

Rationale for Using OWL

The mismatch between the requirements for representing enhanced 

Gloss
tconcept definitions
 and the capabilities of the current 
Specref
RefTypefile
tstated relationship file
 might in theory be addressed by addition of columns to the file or adding additional information in reference sets. However, in practice this would create a more complex solution able to support a specific set of enhanced features.

Adopting the well-established OWL standards formats offers a more flexible solution that can represent the full range of 

Gloss
tdescription logic
 features. This approach enables 
Gloss
tSNOMED Internation
 to specify a particular logic profile to be applied to current releases of 
Gloss
tSNOMED CT
, with the option to extend that profile in the future. Future revisions of the logic profile would not require a change in the distribution file structure provided these were supported by an OWL syntax.

OWL Axioms

OWL axioms can be represented using several different syntaxes. SNOMED International has chose the

Gloss
tOWL Functional Syntax
 as its standard representation.

Glossary include
GlossOWL Functional Syntax
Suffix is
Definline
Prefix The
Linktrue

OWL Expression Axiom Set

OWL axioms are distributed in a 

Specref
treference set
 that follows the  OWL Expression Reference Set specification. The axiom itself is contained in a string field and the 
Gloss
tconcept
 whose definition it contributes to is referenced by the the 
Specref
treferencedComponentId
. Although a single row in the reference set can provide a 
Gloss
tsufficient definition
, the definition of a single concept can also include several axioms each represented by a row in the reference set.

Comparing Stated Relationships and OWL Axioms


Caption label
CapIdappendectomy-diagram
CapTypeFigure
Diagrammatic representation of the definition of appendectomy

Caption reference
CapRefIdappendectomy-diagram
CapRefTypeFigure
 shows the diagrammatic representation of the 
Gloss
tstated view
 of the definition of 
Concept
t80146002 |Appendectomy|
Caption reference
CapRefIdappendectomy-stated-rels
CapRefTypeTable
 shows the same definition as represented by three rows in the 
Specref
RefTypefile
tstated relationship file
 together with the 
Specref
tdefinitionStatusId
 in the 
Specref
RefTypefile
tconcept file
.

Caption label
CapIdappendectomy-stated-rels
CapTypeTable
Stated relationships and definition status for the concept appendectomy

id

effectiveTime

active

..

definitionStatusId

Concept
t80146002 |Appendectomy|

20020131

1

..

Concept
t900000000000073002 |Sufficiently defined concept|

id

effective Time

active

..

sourceId

destinationId

relationship Group

typeId

..

..

..

20180731

1

..

Concept
t80146002 |Appendectomy|

Concept
t71388002 |Procedure|

0

Concept
t116680003 |Is a|

..

..

..

20080731

1

..

Concept
t80146002 |Appendectomy|

Concept
t129304002 |Excision - action|

1

Concept
t260686004 |Method|

..

..

..

20080731

1

..

Concept
t80146002 |Appendectomy|

Concept
t66754008 |Appendix structure|
 

1

Concept
t405813007 |Procedure site - Direct|

..

..

Caption reference
CapRefIdappendectomy-owl-axiom
CapRefTypeTable
 shows a row in the 
Specref
tOWL axiom reference set file
 representing the same definition. As shown by this example, a single 
Gloss
tsufficient definition
is represented by a single row in the reference set. However, some 
Gloss
tconcept definitions
 may require multiple rows in the reference set. Situations in which multiple row are required include:

  • Concepts with multiple 
    Gloss
    tsufficient definitions
    , each of which requires a separate row in the reference set. 
  • Concepts with additional 
    Gloss
    tnecessary conditions
     that are not part of a
    Gloss
    tsufficient definition
    , each of which requires a separate row in the reference set.


Caption label
CapIdappendectomy-owl-axiom
CapTypeTable
Example of OWL axiom refset representation of the definition of appendectomy

id

effective Time

active

moduleId

refsetId

referenceComponentId

owlExpression

..

Footnote Macro

This example has not yet been released in this form and is subject to change.

1

..

Concept
t733073007 |OWL axiom reference set|

Concept
t80146002 |Appendectomy|

EquivalentClasses(:80146002 ObjectIntersectionOf(:71388002 ObjectSomeValuesFrom(:609096000 ObjectIntersectionOf(ObjectSomeValuesFrom(:260686004 :129304002) ObjectSomeValuesFrom(:405813007 :66754008)))))