Introduce a strategy for Measurement and its subclasses

[KateSerafimova]

The Measurement class in SPHN has many subclasses, but not all data that can be described with Measurement can fit in one of the subclasses. We need a consistent strategy on how to instantiate entities of type Measurement.

Options:

1. Instantiate everything in Measurement - add all needed properties directly to it and deprecate all the subclasses
2. Instantiate everything with a subclass, and use measurement just as the Parent class - keep the subclasses with their specifics and introduce new subclasses for the needed data points - such as aidava:DiagnosticMeasurement

[KateSerafimova]

We decide on the 1st approach

[KateSerafimova]

In SPHN, the sub-classes of Measurement are used to add specific restrictions for a given Concept. So when we deprecate them, we will lose those restrictions:

• CircumferenceMeasure

  hasBodySite 1-1 owl:someValuesFrom [ a owl:Class ;
                                      owl:unionOf ( snomed:69536005 snomed:33673004 snomed:29836001 snomed:45048000 ) ]

• CardiacOutput

 hasQuantity owl:someValuesFrom [ a owl:Restriction ;
                                owl:onProperty sphn:hasUnit ;
                                owl:someValuesFrom [ a owl:Restriction ;
                                        owl:hasValue ucum:Lpermin ;
                                        owl:onProperty sphn:hasCode ] ]
...
hasMethodCode owl:someValuesFrom [ a owl:Class ;
                                owl:unionOf ( snomed:63075001 snomed:117610000 ) ]

• OxygenSaturation

 hasQuantity owl:someValuesFrom [ a owl:Restriction ;
                                owl:onProperty sphn:hasUnit ;
                                owl:someValuesFrom [ a owl:Restriction ;
                                        owl:hasValue ucum:percent ;
                                        owl:onProperty sphn:hasCode ] ]

• InhaledOxygenConcentration

  hasQuantity owl:someValuesFrom [ a owl:Restriction ;
                              owl:onProperty sphn:hasUnit ;
                              owl:someValuesFrom [ a owl:Restriction ;
                                      owl:hasValue ucum:percent ;
                                      owl:onProperty sphn:hasCode ] ]

• BloodPressure

 hasMeasurementMethod 0-1 owl:someValuesFrom [ a owl:Restriction ;
                                owl:onProperty sphn:hasCode ;
                                owl:someValuesFrom [ a owl:Class ;
                                        owl:unionOf ( snomed:716777001 snomed:46973005 ) ]
...
 hasBodySite 0-1 owl:someValuesFrom [ a owl:Restriction ;
                                owl:onProperty sphn:hasCode ;
                                owl:someValuesFrom [ a owl:Class ;
                                        owl:unionOf ( snomed:113257007 snomed:40983000 snomed:8205005 snomed:7569003 snomed:344001 ) ]

• HeartRate

 hasRegularityCode owl:someValuesFrom [ a owl:Class ;
                                owl:unionOf ( snomed:271636001 snomed:61086009 ) ]

These restrictions are maybe not always needed or they can be implemented in a different way.

[KateSerafimova]

Changes done:

Move to Measurement properties from the subclasses:

• hasBodySite (BodyTemperature, CircumferenceMeasure, OxygenSaturation, BloodPressure, HeartRate)
• hasDataDetermination (InhaledOxygenConcentration)
• hasPhysiologicState (HeartRate)

Deprecate properties (and add replacements for some):

• hasOxygenEquipment (InhaledOxygenConcentration) - deprecated and replaced by hasMedicalDevice, that has the same range and Measurement was added to its domain
• hasOxygenFlowRate (InhaledOxygenConcentration) - deprecated
• hasMeanPressure (BloodPressure)
• hasRegularityCode (HeartRate) - deprecated because it is related to pulse only, but instead hasQualitativeResultCode can be used