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 Current

changes.mady.by.user Yongsheng Gao

Saved on

Key

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

...

The NNF does not include class disjointness, transitive properties, reflexive properties and sufficient conditions represented as General Concept Inclusions (GCIs) in the OWL axiom refset.

Inferred relationships for concrete values, e.g. decimal, integer, string, or dateTime, should be included in a separate relationship file.

Rules for Determining Redundant Relationships

...

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)

...

Example for property chain:

Stated relationships

Image Removed

Inferred relationships before the removal of the redundant relationship

Image Removed
Concept

Image Removed

Inferred relationships after reduction

Image Removed

ShowPartsterm
t323739006 |Product containing precisely amoxicillin (as amoxicillin sodium) 1 gram/1 vial powder for conventional release solution for injection (clinical drug)|
 (the other model detail has been omitted):

Image Added


Stated relationships of

Concept
ShowPartsterm
t427483001 |Amoxicillin sodium (substance)|
:

Image Added



Inferred relationships before the removal of the redundant relationship

Image Added

Inferred relationships after the reduction

Image Added

For

Concept
ShowPartsterm
t422453004323739006 |Product containing ethyl morphineprecisely amoxicillin (as amoxicillin sodium) 1 gram/1 vial powder for conventional release solution for injection (clinical drug)|
, the relationship 
Concept
ShowPartsterm
t127489000|Has active ingredient|
= 
Concept
ShowPartsterm
t373529000372687004 |MorphineAmoxicillin|
 is inherited from
Concept
ShowPartsterm
t7357200927658006 |Product containing morphineamoxicillin|
. If the rule 1 for class inclusion was to applyapplied, the relationships would not be considered as redundant because 
Concept
ShowPartsterm
t74905005427483001 |Ethylmorphine Amoxicillin sodium (substance)|
 is not a subconcept of 
Concept
ShowPartsterm
t373529000372687004 |Morphine Amoxicillin (substance)|
. Because  Since  
Concept
ShowPartsterm
t74905005427483001 |Ethyl morphineAmoxicillin sodium|
 
Concept
ShowPartsterm
t738774007|Is modification of|
 
Concept
ShowPartsterm
t373529000372687004 |MorphineAmoxicillin|
and property chain of   of "
Concept
ShowPartsterm
t127489000|Has active ingredient|
 and   o  
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)372687004 |Amoxicillin|
 with 
Concept
ShowPartsterm
t127489000|Has active ingredient|
 = 
Concept
ShowPartsterm
t74905005427483001 |Ethyl morphineAmoxicillin sodium|
. 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.

Image Added Image Removed


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

...

7357200973572009 3735290007490500574905005 373529000

referencedComponentId


owlExpression

(stated relationships)

Inferred Relationships in Necessary Normal Form

sourceId

destinationId

relationshipGroup

typeId

27658006

EquivalentClasses(:

27658006 ObjectIntersectionOf(:763158003 ObjectSomeValuesFrom(:609096000 ObjectSomeValuesFrom(:127489000 :

372687004))))

7357200927658006

76488700590704004

0

116680003

73572009

360204007

0

116680003

27658006

372687004

73572009

373529000

1

127489000

422453004323739006

EquivalentClasses(:422453004 323739006 ObjectIntersectionOf(:763158003 ObjectSomeValuesFrom(:609096000 ObjectSomeValuesFrom(:127489000 762949000 :74905005427483001))))

422453004323739006

7357200927658006

0

116680003

422453004323739006

74905005427483001

1

127489000762949000

127489000

SubObjectPropertyOf(ObjectPropertyChain(:127489000 :738774007) :127489000))

N/A

N/A


N/A

427483001

SubClassOf(:

427483001 ObjectIntersectionOf(:440327007 ObjectSomeValuesFrom(:738774007 :

372687004)))

74905005427483001440327007

373298001

0

116680003

74905005427483001

373529000372687004

0

738774007

427483001

768681000

0

726542003


Technical Implementation for Calculating the 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.

...