MyVeeva for Patients Current Release


April 22, 2022, General Release

22R1.0

About the Release

Important Dates

Date Event Description
March 21 Pre-Release The release is deployed to the MyVeeva for Patients pre-release environment and available for customers to explore from pre-release vaults.
April 22 General Release The release is deployed and generally available. The MyVeeva for Patients validation binder will be available to customers in VeevaDocs at this time.

Release Information and Impacts

Resource Description Publication History
MyVeeva for Patients 22R1 Release Impact Assessment

The release impact assessment analyzes the regulatory, implementation, and user impacts of the MyVeeva for Patients and Veeva eConsent features in this release.

Updated March 1
What's New

The What's New information provides detailed explanations of the new features for MyVeeva for Patients and Veeva eConsent.

Published March 4
Fixed Issues

The Fixed Issues list documents issues that affected previous versions or the pre-release and are fixed in this release.

Available April 8
Known Issues

The MyVeeva for Patients Known Issues page lists issues that affect this release or previous ones and aren't fixed yet.

Available April 8
Maintenance Releases

The MyVeeva for Patients Maintenance Releases page lists releases that fix issues affecting the general release.

Available with the first maintenance release
Digital Trials Platform Release Notes

See the following release notes for more information about new features across the Digital Trials Platform:

  • Clinical Operations and SiteVault Enterprise: The About the 22R1 Release page in Vault Help provides the Vault release dates, resources, and release impact assessment.
  • SiteVault: See the SiteVault Release Notes for information about the SiteVault features in the release impact assessment and to learn what's new for sites.
  • MyVeeva for Patients: The MyVeeva for Patients Release Notes document the impact of this release on MyVeeva users.
See links

What’s New

Veeva eConsent

Form Response Data Shared With Sponsor

This feature allows sponsors to view consent and response data for studies across sites in a structured format. When a MyVeeva user submits a signature or response on a consent form connected to a sponsor, MyVeeva for Patients sends the de-identified participant response data to the Clinical Operations vault. Sponsors can then report on and aggregate the data as needed.

The eConsent form must be shared with an import code or Site Connect by the sponsor with the site. Only signatures and responses from content blocks on the sponsor form are shared with the sponsor. Blocks added by the site are not shared. If a site wants to use a sponsor form as a template for another purpose, site staff can disconnect the form from the sponsor.

See the Consent Form Settings topic in Veeva eConsent Editor Help for more information.

An example of a connected eConsent form that sends form data to sponsor
Hand-Drawn Signature

This feature allows sites and sponsors to require a hand-drawn signature for a consent form. This feature also allows registered MyVeeva users to hand-draw their signature on any consent form, which some users prefer to feel a sense of ownership over their consent.

If site or sponsor staff want to require a hand-drawn signature for a consent form, they can edit the form to toggle the Requires Hand-Drawn Signature setting to on in the Veeva eConsent editor.

See the following help topics for more information:

Live example of a hand-drawn signature
Simple Signing

This feature allows participants and other signatories to sign and submit consent forms in person without registering a user account. Being able to sign without an account enables signatories in demographics without email addresses or mobile phones to use Veeva eConsent within compliance regulations, increasing the scope of studies and participants that Veeva eConsent supports.

In SiteVault, site staff can now send eConsent forms without contact information. When a MyVeeva user is unregistered, the system requires the MyVeeva user to sign during an in-person consenting session and to draw their signature in place of dual-factor authentication. This feature is only available in the web app, which supports the in-person consent flow.

See the following help topics for more information:

Selection of View In-Person Code option and example QR code
Add Site Countersignature to MyVeeva .PDF Files

This feature allows MyVeeva users to view and download countersigned .PDF files of consent forms. When site staff countersign a consent form in SiteVault, the system updates the .PDF file in MyVeeva for Patients to include the site signature.

This feature applies only to consent forms that are countersigned after the 22R1.0 release. Consent forms countersigned before the release will continue to include only the MyVeeva user signatures.

See the following help topics for more information:

Example of PDF countersignature

MyVeeva for Patients Platform

User Language Preference

This feature allows MyVeeva users to update their preferred language in their account settings. When they change their preferred language, the user interfaces of both the web and mobile apps are displayed in the new language. Notifications such as emails and text messages are also sent in the new language.

The MyVeeva user can select any supported language. Currently, English, French, German, Italian, Polish, and Spanish are supported.

See the Account topic in MyVeeva for Patients Help for more information.

Example flow of MyVeeva user changing preferred language
Voice Option for Two-Factor Authentication

This feature allows MyVeeva users to receive two-factor authentication codes in voice calls as a backup for text messages. Sometimes, MyVeeva users can’t receive codes via text message, often because of delays in their wireless carrier’s SMS delivery system. When users can’t receive text messages, they can’t log in, submit signed consent forms, or confirm account setting changes. Wireless carriers prioritize voice calls over SMS messages, so voice calls are more likely to be received when text messages aren’t.

See the Account and Consent help topics in MyVeeva for Patients Help for more information.

Voice call option example

Additional Enhancements

The following enhancements are now available for MyVeeva for Patients and Veeva eConsent:

Area Users Description Number
eConsent - Editor MyVeeva Users, Site Staff, Sponsor Staff This feature allows sponsor and site staff to import Microsoft Word™ documents that include font colors and highlights into the eConsent editor. MYVC-4326
Platform - Audit Trail Veeva With this feature, the system records the previous and new values when a MyVeeva user updates their email address or phone number in their account settings. The system encrypts the values as personally identifiable information (PII). MYVC-6037
Platform - User Profile MyVeeva Users This feature includes user interface enhancements for error messages for user account settings in the MyVeeva for Patients web app. MYVC-6036

Fixed Issues

The issues below are now fixed. See the MyVeeva for Patients Known Issues page for additional issues that staff and MyVeeva users may still encounter.

Component Description Issue
eConsent - ClinOps Integration When sponsor staff copy an existing form (Form A) then share the new form (Form B) with a site with an import code without editing the form in the editor, the site form is now connected to the correct sponsor form (Form B). Previously, the site form was connected to the original sponsor form (Form A). MYVC-6617
eConsent - ClinOps Integration When a Clinical Operations user saves or checks in an eConsent form from the eConsent editor then shares the form with a site, response data is now associated with the correct form. Previously, if the Clinical Operations user imported or copied an existing Clinical Operations form (Form A) into a new form (Form B), response data was associated with Form A instead of Form B. MYVC-6540
eConsent - ClinOps Integration When sponsor staff add content blocks and check in an eConsent form multiple times, the form now remains connected to the sponsor. Previously, the form may have been disconnected from the sponsor and would not have been connected if shared with a site. MYVC-6452
eConsent - Editor When a Clinical Operations user shares an eConsent form with a site after saving but not checking in the form from the eConsent editor, the eConsent form is now connected to the sponsor. Previously, the eConsent form was not connected and response data was not received. MYVC-6606
eConsent - Editor When sponsor staff share an eConsent form with a site via Site Connect and the site approves it without editing it in the eConsent editor, the hand-drawn signature requirement is now correctly applied if the sponsor set it. Previously, the hand-drawn signature requirement was no longer applied. MYVC-6596
eConsent - MyVeeva Users Signatures are now aligned with the signature lines on the .PDF copies of signed eConsent forms if the signatory's name is long enough to require the text to wrap. MYVC-3431
eConsent - SiteVault Integration When an eConsent form is signed and submitted by all signatories, the signature response record is now associated with the signed version of the eConsent form. Previously, the signature response record remained associated with the placeholder version. MYVC-6059
General UI MyVeeva users can now click the Recover Account link in the iOS app to access the web page for resetting their password. Previously, the web page was not opened when the user clicked the link. MYVC-6165
General UI When you update your account's email address in MyVeeva for Patients, the email address saved for your login page is also updated. MYVC-5253
General UI When two guardians are logged in and viewing the same eConsent form in the iOS app and one answers a required question, the second guardian now receives a message explaining that the question has already been answered when they try to answer the same question. MYVC-6427
General UI If two MyVeeva users are viewing the same eConsent form at the same time in the iOS app and one user declines the eConsent form prior to the other, the second user will receive a message if they attempt to decline. Previously, the second user would not receive a message notifying them that another user declined. MYVC-6407
Platform - Authentication, Platform - User Profile When a SiteVault user updates a MyVeeva for Patients user's locale in SiteVault, the MyVeeva for Patients user now receives emails related to their account settings in the updated language. Previously, the MyVeeva users may have received emails in the language for the previous locale. MYVC-4202
Menu
Resources
Release Notes