SNOMED CT OWL Guide

Search

SNOMED CT Document Library

    Loading...

Versions Compared

Old Version 15

changes.mady.by.user David Markwell

Saved on

compared with

New Version 16

changes.mady.by.user David Markwell

Saved on

Key

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

...

For

Concept
ShowPartsterm
t12676007 |Fracture of radius|
, the relationship
Concept
ShowPartsterm
t363698007|Finding site|
 = 
Concept
ShowPartsterm
t299701004|Bone structure of radius and/or ulna|
is inherited from
Concept
ShowPartsterm
t65966004|Fracture of forearm|
, which is a redundant relationship because 
Concept
ShowPartsterm
t62413002|Bone structure of radius|
is a subtype of
Concept
ShowPartsterm
t299701004|Bone structure of radius and/or ulna|
. The relationship 
Concept
ShowPartsterm
t116676008|Associated morphology|
 = 
Concept
ShowPartsterm
t19130008|Traumatic abnormality|
is inherited from
Concept
ShowPartsterm
t429353004|Injury of radius|
, which is a redundant relationship because 
Concept
ShowPartsterm
t72704001|Fracture (morphologic abnormality)|
 is a subtype of
Concept
ShowPartsterm
t19130008|Traumatic abnormality|
.

Caption label
CapIdexampleexample1-in-owl-axiom-refset-and-rf2-relationship-file-nnf-
CapTypeTable
Example in OWL axiom refset and RF2 relationship file (NNF)

...

For concept

Concept
ShowPartsterm
t7246002|Kidney biopsy|
, the relationship 
Concept
ShowPartsterm
t363704007|Procedure site|
= 
Concept
ShowPartsterm
t64033007|Kidney structure|
is inherited from
Concept
ShowPartsterm
t118851004|Procedure on kidney|
, which is a redundant relationship to 
Concept
ShowPartsterm
t405813007|Procedure site - Direct|
= 
Concept
ShowPartsterm
t64033007|Kidney structure|
because 
Concept
ShowPartsterm
t405813007|Procedure site - Direct|
is a subtype of
Concept
ShowPartsterm
t363704007|Procedure site|
. Because 
Concept
ShowPartsterm
t64033007|Kidney structure|
is a subtype of 
Concept
ShowPartsterm
t122489005|Urinary system structure|
and
Concept
ShowPartsterm
t82849001|Retroperitoneal compartment structure|
, the inherited relationships for 
Concept
ShowPartsterm
t405813007|Procedure site - Direct|
are also redundant.

Caption label
CapIdexampleexample2-in-owl-axiom-refset-and-rf2-relationship-file-nnf-
CapTypeTable
Example in OWL axiom refset and RF2 relationship file (NNF)

...

For

Concept
ShowPartsterm
t422453004|Product containing ethyl morphine|
, the relationship 
Concept
ShowPartsterm
t127489000|Has active ingredient|
= 
Concept
ShowPartsterm
t373529000|Morphine|
 is inherited from
Concept
ShowPartsterm
t73572009|Product containing morphine|
. If the rule 1 for class inclusion was to apply, the relationships would not be considered as redundant because 
Concept
ShowPartsterm
t74905005|Ethylmorphine (substance)|
 is not a subconcept of 
Concept
ShowPartsterm
t373529000|Morphine (substance)|
. Because 
Concept
ShowPartsterm
t74905005|Ethyl morphine|
 
Concept
ShowPartsterm
t738774007|Is modification of|
 
Concept
ShowPartsterm
t373529000|Morphine|
and property chain of 
Concept
ShowPartsterm
t127489000|Has active ingredient|
 and 
Concept
ShowPartsterm
t738774007|Is modification of|
 is a sub-property of 
Concept
ShowPartsterm
t127489000|Has active ingredient|
, the rule 2 actually compares the anonymous concepts for subsumption, i.e. 
Concept
ShowPartsterm
t127489000|Has active ingredient (attribute)|
 = 
Concept
ShowPartsterm
t373529000 |Morphine (substance)|
 with 
Concept
ShowPartsterm
t127489000|Has active ingredient|
 = 
Concept
ShowPartsterm
t74905005|Ethyl morphine|
. Therefore, the inherited relationship is redundant and can be removed from the NNF.   Their relationships and property chain can be demonstrated in the following diagram.



Caption label
CapIdexampleexample3-in-owl-axiom-refset-and-rf2-relationship-file-nnf-
CapTypeTable
Example in OWL axiom refset and RF2 relationship file (NNF)

...

  1. All 

    Concept
    t116680003 |Is a|
     relationships should be assigned in role group 0;

  2. Attribute that is not grouped, not a value of 

    Concept
    ShowPartsterm
    t609096000 |Role group (attribute)|
     or grouped=0 in MRCM, should be assigned in role group 0;

  3. Attribute that is grouped, value of 
    Concept
    ShowPartsterm
    t609096000 |Role group (attribute)|
     or grouped=1 in MRCM, should be assigned a role group number that is not 0. Each 
    Concept
    ShowPartsterm
    t609096000 |Role group (attribute)|
     in the OWL axiom should be presented by a unique role group number. Note, role group merging is not covered here.

Concept
t609096000 |Role group (attribute)|
 is explicitly represented for self-grouped attributes where there is only a single attribute in a role group in an OWL axiom. However, these self-grouped attributes and values are not explicitly represented in the current relationship files. This representation has caused confusion if an attribute in role group 0 is grouped or not. The following example demonstrates the changes to assignment of role group number after the implementation of the complete OWL axiom refset.

...