Context
External CTRL customers need to collect research data alongside consent
management. Research data should NOT be collected through CTRL for data
governance reasons.
Driving use case: the Bowman RbG cohort. The team plans to use REDCap for research data
and has raised the question of how best to integrate with CTRL.
Options raised by collaborators
- Embed an external REDCap survey within CTRL — participant stays in
the CTRL UI while completing the REDCap survey (iframe or similar).
- Link out to an external REDCap survey from a CTRL page — participant
is directed to REDCap in a new tab; returns to CTRL afterward.
Trade-offs to weigh
- User experience continuity — embed is smoother; link-out is more transparent
- Data governance & audit trail — which system holds what data at each step
- Security — embedding external content, cross-domain concerns
- Session management — is CTRL identity linked to REDCap identity, or separate?
- Implementation complexity
- Recovery semantics if the participant abandons the REDCap portion partway
Context
External CTRL customers need to collect research data alongside consent
management. Research data should NOT be collected through CTRL for data
governance reasons.
Driving use case: the Bowman RbG cohort. The team plans to use REDCap for research data
and has raised the question of how best to integrate with CTRL.
Options raised by collaborators
the CTRL UI while completing the REDCap survey (iframe or similar).
is directed to REDCap in a new tab; returns to CTRL afterward.
Trade-offs to weigh