In the web interface, floats are accepted even if the concept is NOT marked as precise. We need to have some additional data validation for this.
We need to enforce integer values for non-precise numerics at both the web and service layers – i.e., the obs management screen should check for this and the OpenMRS API should throw an exception if anyone attempts to store a float (non-integer) value into an observation that has a non-precise numeric concept for a question.
Consider silently rounding up or down if a float is entered for a concept not marked as precise.
For more information see...