I'm currently working on an iOS app which implements different types of clinical tools for doctors. On a basic level, every clinical tool includes a lot of questions, i.e. controls (buttons, segmented controls, etc.), and displays a result calculated from the inputs. The result is usually divided in ranges of values (let's say, it shows if you're not sick/somewhat sick/very sick).
I've been thinking of implementing haptic feedback while the doctors are interacting with the tools as a way of saying "the result went into a higher/lower value range". In some cases, this would inform the doctor that they don't need to continue answering the questions, as the result is now at a maximum/minimum and save them time. The intensity of the feedback would be according to the range of the value, with more powerful feedback as the result goes into higher ranges.
However, most of the usage of haptic feedback across default iOS apps, as well as some of the third-party ones, is mostly focused on direct user actions (pressing a button, toggling a switch, scrolling a spinner, etc.). I don't want to go down this route, since a lot of the clinical tools are quite extensive—getting haptic feedback at the 15th yes/no toggle consecutively would get annoying fast.
Are there any general guidelines/consensus of using haptics for direct actions vs the result of the action? What is your personal experience? Does using haptic feedback in this manner in clinical tools preclude using it in a more "traditional" manner elsewhere in the app?