The logic definitions are represented by the OWL axiom refset that is a replacement of the RF2 stated relationship file. As a result, the nature of the inferred relationship file in the distribution normal form (DNF) has changed, because the new DL features are not representable in the current relationships file. The inferred relationship file will maintain the same format and structure, but it is no longer equivalent to the stated form (containing all necessary and sufficient conditions). In fact, it is a collection of all the necessary conditions of precoordinated concepts and represents a subset of the full semantics.

Necessary Normal Form

The Necessary Normal Form (NNF) is a replacement for the Distribution Normal Form for inferred relationships. The NNF is a precalculated distribution form for practical purposes, for example, to support the continuity of existing implementations based on relational databases and queries by the expression constraint language.

...

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

Rule 1  - Class and Role inclusions

Given two relationships, A and B, A with r = C and B with s = D, within the same role group, A is redundant if:

...

Note, “crossover relationships”, where r is a supertype of s, and C is instead a subtype of D do not result in a redundant relationship.

Example for Class inclusion

Stated relationships

Image RemovedImage Added

Inferred relationships before the removal of redundant relationshiprelationships

Image RemovedImage Added

Inferred relationships after the reduction

Image RemovedImage Added

For

Example in OWL axiom refset and RF2 relationship file (NNF)

Example for Role inclusion

Stated relationships

Image RemovedImage Added

Inferred relationships before the removal of redundant relationship

Image RemovedImage Added

Inferred relationships after reduction

Image RemovedImage Added

For concept

Example in OWL axiom refset and RF2 relationship file (NNF)

Rule 2  - Property chains including transitive properties

Given attribute r, s and t with a property chain SubObjectPropertyOf(ObjectPropertyChain(t s) r), and two relationships A and B, A with r = C and B with u = D, within the same role group, A is redundant if:

• Attribute u is the same as or a subtype of t, and

• D has a relationship to C via attribute s

...

     SubObjectPropertyOf(ObjectPropertyChain(r r) r) and thus it is a special case of the above.

Example for property chain:

Stated relationships

Image Removed

of

Image Added

Stated relationships of

Image AddedImage Removed

Inferred relationships before the removal of the redundant relationship

Image Removed

Image RemovedImage Added

Inferred relationships after the reduction

Image RemovedImage Added

For

Image Added

Example in OWL axiom refset and RF2 relationship file (NNF)

Technical Implementation for Calculating the NNF

This fairly complex process uses the stated form and the output of the reasoner to calculate the necessary normal form which is represented in the relationship RF2 file.

The most straightforward way to produce the necessary normal form would be to use the Snomed OWL Toolkit or the Classification Service REST API which is language agnostic.

High Level Process

Classification

1. Read the Stated Form from RF2 files.

1. The following files are required: Concept, OWL Ontology Reference Set, OWL Axiom Reference Set. 

2. If the edition has any active stated relationships then the Stated Relationship and MRCM Attribute Domain Reference Set files are also required.

2. Use the OWL API to infer the class hierarchy

1. Build the Ontology object using:

1. Axioms from the OWL Axiom Reference Set, making a note of any Transitive property and Property Chain axioms.

2. Axioms created by converting Stated Relationships to OWL Axioms using the MRCM Attribute Domain Reference Set for list of attributes which should not be grouped in the given domain.

2. Use a reasoner to pre-compute the class hierarchy.

Necessary Normal Form Calculation

Calculating the necessary normal form happens in two passes of the hierarchy.org.snomed.otf.owltoolkit.normalform

1. Walk the class hierarchy in a top-down, breadth first, order.

1. For each class visited gather the stated attributes of this class and each inferred parent.

2. Compare the attributes and remove those which are found to be redundant because they are less specific in terms of depth in the hierarchy.

3. During this first pass build a hierarchy for property chains and transitive properties.

2. Walk the class hierarchy again in the same order reducing the attributes of each class further.

1. Compare the attributes and remove those which are found to be redundant because they are less specific in terms of depth in one of the alternate hierarchies.

For fine level detail the best source of information is the Java class org.snomed.otf.owltoolkit.normalform.RelationshipNormalFormGenerator which performs the Necessary Normal Form calculation.

Assignment for Role Group Number

It is important to clearly indicate if an attribute is grouped or not because 

The following rules should be followed in the inferred relationship file to provide consistent representation aligned with the concept model diagram and the OWL axiom refset.

1. All 

   Concept
   t 116680003 |Is a|

    relationships should be assigned in role group 0;

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

   Concept
   ShowParts term t 609096000 |Role group (attribute)|

    or grouped=0 in MRCM, should be assigned in role group 0;

3. Attribute that is grouped, value of 

   Concept
   ShowParts term t 609096000 |Role group (attribute)|

    or grouped=1 in MRCM, should be assigned a role group number that is not 0. Each 

   Concept
   ShowParts term t 609096000 |Role group (attribute)|

    in the OWL axiom should be presented by a unique role group number. Note, role group merging is not covered here.

An example for the current diagram representation for attribute in role group 0 in the stated relationship file and concept model diagram

Image Added  

After the complete OWL axiom refset is implemented,

Image Added

Representation of 

Image Added