Capturing Remote Signatures for Sampling

  • iPad
  • iPhone
  • Browser (Classic)
  • Browser (Lightning)

Remotely captured signatures enable end users to remotely capture signatures for BRC sampling outside of an Engage Meeting. This is useful if the user is meeting with an account remotely, for example, over Zoom or Microsoft Teams, but still wants to disburse BRCs.

For example, Sarah Jones meets with Dr. Clinton Ackerman using his preferred method of virtual communication. Dr. Ackerman requests a BRC sample of Cholecap. Sarah uses the Share Link signature method to send a link to Dr. Ackerman via iMessage. When Dr. Ackerman selects the link on his device, he is guided through a process on his device’s web browser and signs for the BRC.

Considerations

  • Share Links are a signature method selected from the Signature Setup Page
  • Only BRC-type products can be signed for
  • Remote signature capture is supported for person account calls, both with and without the --paa section signal, as well as unique activity child calls. It is not supported for standard group calls.
  • A user can only request one remote signature at a time. Requesting signatures from multiple browser tabs, devices, or platforms at the same time is not supported.
  • Links are single-use. A Request Expired error message displays to accounts if they attempt to open the same link twice.
  • The Request Expired error message also displays if the user cancels the request before the account opens the link
  • The following features are not supported for Browser (Classic) users capturing remote signatures:
  • Approved Email Receipts for Signature Transactions
  • Creating Sample and Product Limits
  • Supporting State Distributor License Validation
  • Sampling with Mid-level Practitioners
  • The following browsers are not supported when signing:
  • Internet Explorer
  • UC Browser
  • Desktop WeChat on Windows

Prerequisites

Configuring Remote Signature Capture for Sampling

To configure this feature:

  1. Grant admins the following permissions:

    Object OLS Record Types Fields FLS
    Call2_vod n/a n/a
    • Remote_Signature_Attendee_Name_vod
    • Signature_Captured_Share_Link_vod
    Edit
    Sample_Order_Transaction_vod n/a n/a
    • Signature_Captured_Share_Link_vod
    Edit
    Sample_Order_Transaction_Audit_vod n/a n/a
    • Signature_Captured_Share_Link_vod
    Edit
  2. Grant end users FLS edit permission to the following Call2_vod fields:

    • Remote_Signature_Attendee_Name_vod
    • Signature_Captured_Share_Link_vod

Using Remote Signature Capture for Sampling

Users can request signatures via iPad, iPhone, Browser (Classic), and Browser (Lightning) platforms.

Generating Signature Requests from an iPad

To generate and share a link for an attendee to use to sign for BRCs using an iPad

  1. Use the Signature Setup page to select Share Link for the Signature Method.
  2. Select Next.
  3. Select the appropriate application to share the generated link with the attendee.

    Links display as text in iMessage if the user is not added to the attendee’s contact list.

    The Mail method is not recommended. This is because anti-virus software the recipient may have might open the link in advance and render it expired.

Select Copy Link to copy the link to the device’s clipboard if an acceptable application is not available.

After selecting the appropriate option, the end user must remain in Veeva CRM until the attendee provides their signature.

Generating Signature Requests on the Browser Platforms

To generate and share a link for an attendee to use to sign for BRCs from the Browser (Classic) or Browser (Lightning) platforms:

  1. Select the Request Signature button from the More Actions menu on the Call Report to display the Signature Setup page.

  2. Use the Signature Setup page to select Share Link for the Signature Method.

    Online users cannot request receipts when remotely capturing signatures.

  3. Select the Copy Link button to copy the link to the device’s clipboard.

  4. Paste the link into the appropriate application or messaging system to share with the HCP.

Canceling Signature Requests

For online users, select the Cancel Request button from the link sharing screen to cancel signature requests.

When users cancel a signature request, a screen displays to the HCP indicating that the signature request is canceled. The HCP cannot submit a signature until the user creates a new signature request from the Signature Setup screen.

Providing a Remote Signature

When an attendee is requested to sign for a BRC remotely, they receive the link via the application selected by the end user.

Selecting the link displays the internet browser, where the signer can review requested BRCs, sign, and submit their signature via their browser.

Reviewing Remote Signatures

After the signer signed for the BRC, the end user can review the signature and either accept the signature or request the signer to sign again. If Displaying HCP Information on the Signature Page is enabled, the HCP’s display name is shown on the signature page. When users capture an HCP signature, the value in the Signature_Page_Display_Name_vod field for that account is stamped on the Call2_vod, Sample_Order_Transaction_vod, and Sample_Order_Transaction_Audit_vod records.

After accepting the signature, the call displays. For auditing purposes, calls where a BRC was signed for remotely automatically have the Signature_Captured_Share_Link_vod check box selected. Any resulting Sample_Order_Transaction_vod and Signature_Order_Transaction_Audit_vod records made from the call also have this check box selected.

A message displays to accounts when they submit their signature informing them that their signature was accepted, regardless of if the user rejects the signature or not. If the user rejects the account's signature, they must generate a new link to recapture the signature.

Admins can run reports on the Call2_vod, Sample_Order_Transaction_vod, and Sample_Order_Transaction_Audit_vod objects to review a list of all calls and sample order transaction/audit records where a signature was captured remotely. The appropriate Sample Order Transaction and Audit fields are automatically stamped by triggers when users create call records, to preserve data integrity and provide an audit trail.