Details

Type: Change Request

Status: Closed

Priority: Minor

Resolution: Fixed

Affects versions: None

Fix versions: Release 1.0.2

Components: openehr.rm.data_types

Labels:None

Change Description:

Impact Analysis:Some small impact on software and XML schemas expected.

Approved By:ARB
Description
Gerke Geurts:
The DV_AMOUNT and DV_ABSOLUTE_QUANTITY classes contain (optional) accuracy attributes. However the specifications for the outcome of mathematical operations (especially the add/subtract operators) seem to be silent on the accuracy of the results of these operations.
A further question that then arises, is what to do with values for which the accuracy is +/0. The OpenEhr spec reserves this values as indicating that the accuracy has not been specified. I take it that the outcome of any mathematical operation on a value with unrecorded/unknown accuracy must have an unrecorded/unknown accuracy itself. However, if that is the case, the calculation of formulas that have constants (which have a true accuracy 0) becomes an issue, because the OpenEhr spec currently does not seem to allow for the representation of values with a +/0 accuracy.
Rong:
While we are on this, maybe we should consider how two precisions (optional attribute of DV_QUANTITY) can be combined as well.
The DV_AMOUNT and DV_ABSOLUTE_QUANTITY classes contain (optional) accuracy attributes. However the specifications for the outcome of mathematical operations (especially the add/subtract operators) seem to be silent on the accuracy of the results of these operations.
A further question that then arises, is what to do with values for which the accuracy is +/0. The OpenEhr spec reserves this values as indicating that the accuracy has not been specified. I take it that the outcome of any mathematical operation on a value with unrecorded/unknown accuracy must have an unrecorded/unknown accuracy itself. However, if that is the case, the calculation of formulas that have constants (which have a true accuracy 0) becomes an issue, because the OpenEhr spec currently does not seem to allow for the representation of values with a +/0 accuracy.
Rong:
While we are on this, maybe we should consider how two precisions (optional attribute of DV_QUANTITY) can be combined as well.