[Feature Request] Automate tracking prompts for a less disruptive annotation workflow

[sen-trenser]

What feature or change would you like to see made?

Currently OHIF asks a lot of prompts for tracking in different scenarios. This would be confusing for a user to understand what is tracking, untracking etc. The current tracking workflow is documented here. This is alleviated in v3.9 with the appConfig.disableConfirmationPrompts config.

This feature request is for further simplifying the UX for the underlying tracking workflow and reducing the involvement by users for workflow decisions (assuming the user wants the tracking workflow to update automatically with what he does with annotation or SR reports).
This proposal is to remove the below scenarios from a user perspective based on the same configuration.

• "Untracked" annotations (Except non-acquisition oriented viewports in MPR views).
• Displaying locked measurements in SR preview viewport.

The existing tracking workflow could be kept under the appConfig.disableConfirmationPrompts config.

The below is the attached diagram for the proposed workflow..

Please share your suggestions or any preferred alternative suggestions to implement this requirements.

Why should we prioritize this feature?

This will provide an easier and better experience for the users.
This will also allows users to track measurement changes and allows to save their changes when necessary.

This proposal is to discuss and align the future plan from OHIF and ours to provide a better experience for users. We (Flywheel) would also plan to contribute the proposed changes to Cornerstone3D (for measurement changes tracking) and OHIF for the workflow changes once the proposal is approved.

Could you please prioritize this?

[sedghi]

I think it makes sense to have three options for tracking, the "standard" (current), the "simplified" and "none" for disable, so we get rid of the appConfig.disableConfirmationPrompts and just have appConfig.measurementTrackingMode

Is this workflow something you have iterated on based on your user interviews?

[kgoettler]

@sedghi to confirm my understanding:

• standard: current tracking workflow
• simplified: disable all prompts, except those mentioned by @sen-trenser above
• none: no tracking whatsoever (all measurements will be untracked)

Do I have that correct?

Is this workflow something you have iterated on based on your user interviews?

Yes. We've heard from users that they expect tracked measurements to be the default behavior, as they have little need for untracked measurements. The solution we've described here is the most straightforward way we've found to accomplish this without having to remove the measurement tracking functionality entirely (though if there was a way to do this while preserving the ability to save/export measurements as SR, we'd be interested in exploring that).

[sedghi]

@james-hanks