Remote consent capture during virtual HCP visits
Key Takeaway
Remote consent needs Twilio. An admin selects "Remote consent" in "Twilio Settings", and reps plan the visit on the Twilio visit channel, because remote signatures aren't supported for Microsoft Teams.
Remote consent lets a field rep collect a healthcare professional's (HCP's) signed consent during a virtual visit instead of face to face. The HCP reviews the consent topics, opts in or opts out, and signs in their own browser without leaving the visit. Remote consent belongs to the remote signatures capability of Remote Engagement and builds on the org's existing Consent Management setup.
What happens in a remote consent request
A remote consent request runs in this order during the remote session:
- The rep opens the consent page and requests a signature.
- The HCP gets a notification in their browser.
- The HCP reviews the consent topics and chooses to opt in or opt out.
- The HCP provides an electronic signature without leaving the visit.