Feature discussion — how should CTRL collect user feedback (QA or bug) ?

[mhebrard]

Context

CTRL is being adopted by external customers (e.g. Bowman RbG cohort,
AllClear). We need a way to collect user feedback on CTRL itself — bug
reports, usability issues, feature requests.

If the collecting team isn't a clinical/service team, feedback may need
to be treated as research data under HREC governance — which would mean
collecting it through external REDCap (like other research data), not
through CTRL.

If it's QA data, we have more flexibility to build feedback collection
directly into CTRL.

Options

1. Build feedback collection into CTRL directly (e.g. in-app feedback
   widget). Simplest for the user; feasible only if feedback is treated as
   QA data.
2. Use external REDCap for all CTRL feedback — treat as research data
   by default. Requires participants to leave the CTRL flow.
3. Hybrid — allow both, configurable per customer deployment based on
   their governance context.