MyVeeva for Patients Known Issues

The known issues below affect MyVeeva for Patients, Veeva eConsent, and Veeva ePRO regardless of the current Vault release. Known issues are included for MyVeeva for Patients to assist sites and sponsors with troubleshooting issues.

We also recommend that you use a desktop browser for the eConsent editor and ePRO module, and you’ll have the best experience in Google Chrome™, Microsoft Edge®, or Mozilla® Firefox®. Using Microsoft® Internet Explorer™ 11 is not recommended, and you may encounter additional cosmetic issues that aren’t listed below if you do.

See the MyVeeva for Patients Maintenance Releases page for a list of releases that fix issues affecting customers and users in production environments. Fixed issues are also documented in the Fixed Issues section of the general release notes if an issue is fixed in a general release.

Components Description Workaround Planned Fix Issue
eConsent - ClinOps Integration When site staff approve an upversioned ePRO collection containing new languages and a MyVeeva user changes their preferred language in their account settings, surveys that the user received in their tasks prior to changing their preferred language remain in their previous preferred language selection. Site staff can completely remove and add back the datetime on the participant events that triggered the surveys that are currently in the incorrect language. To be determined MYVC-8941
eConsent - Editor The spacing and margins of .PDF versions of eConsent forms recently changed. Template .PDF versions and signed .PDF versions of eConsent forms may now have different page counts than they did previously. None To be determined MYVC-9829
eConsent - Editor You cannot import .DOCX files to the Veeva eConsent editor if the file contains more than 4MB of media content. None To be determined MYVC-4483
eConsent - Editor Dragging and dropping a content block a long distance in a section or between sections can cause the content in the current section to be reordered. Select the up or down arrows to move the block up or down in the Content Blocks list. To be determined MYVC-2934
eConsent - Editor When you copy and paste a bulleted or numbered list from Microsoft Word into the Veeva eConsent editor, the indentation of the list items is not retained. Either import the Microsoft Word document or manually add the indentation in the editor. To be determined MYVC-2508
eConsent - Editor In rare instances where an eConsent form is sent to multiple signatories, the forms are sent and can be signed by MyVeeva users as expected, but their status in SiteVault remains as Processing instead of Delivered. This issue doesn't impact the eConsent signature workflow for participants and is planned to be fixed in 23R1. None To be determined MYVC-11055
eConsent - MyVeeva Users When site staff create an eConsent form template from a Microsoft Word document, approve it for use without editing it in the editor, and immediately send it to a MyVeeva user, the sent document shows an Error status. If site staff cancel the document while it's in an Error status, MyVeeva users can still sign and submit it. Users should edit the eConsent form template in the eConsent editor and check in the version they intend to approve to Vault prior to sending it to MyVeeva users. To be determined MYVC-9332
eConsent - MyVeeva Users MyVeeva users can sign and submit consent forms that may not be the latest version if site staff update the consent form while they are reviewing it. Site staff should check for users that signed a document shortly after they approved an updated version of a consent form. If any users signed the old form, recomplete the consent process with them as needed. To be determined MYVC-4784
eConsent - MyVeeva Users When site or sponsor staff create an eConsent form template from a Microsoft Word document but don't edit it in the eConsent editor prior to approving it for use, MyVeeva users who signed the form can't view the signed form in their documents list in the iOS app. Edit the eConsent form template in the eConsent editor prior to approving it for use and sending it to participants. To be determined MYVC-9327
eConsent - MyVeeva Users When site or sponsor staff create an eConsent form template from a Microsoft Word document but don't edit it or check it in to Vault from the eConsent editor prior to approving it for use, signed versions of the form contain a null value at the beginning of the document when MyVeeva users download it as a .PDF. Users should edit the eConsent form template and check in the version they intend to approve to Vault from the eConsent editor prior to approving it for use and sending it to participants. To be determined MYVC-9214
eConsent - SiteVault Integration When you update the study that an informed consent form is associated with, the incorrect document name is displayed in the title bar of the preview opened from the Veeva eConsent editor or SiteVault. The incorrect name is not displayed to patients in the MyVeeva for Patients application. To be determined MYVC-3038
eConsent - SiteVault Integration If an eConsent form is approved for use with a blank Signature Name on a signature block, the Signature Name form response value for all signatories displays as Signature_1 in SiteVault and Clinical Vault. Users can enter a custom Signature Name for the signature block. Custom Signature Name form response values display as expected. To be determined MYVC-10349
eConsent - Viewer When sponsor or site staff create an eConsent form template from a Microsoft Word document that contains images or videos in question or signature blocks and approve it for use without editing the form in the editor, MyVeeva users can't download a .PDF version of the unsigned form. Users should edit the eConsent form template in the eConsent editor and check in the version they intend to approve to Vault prior to sending it to MyVeeva users. To be determined MYVC-9258
ePRO - Module If a sponsor user upversions an ePRO collection containing more than one language and makes any change to an ePRO's configuration or patient-facing name, the collection's Translated column status will erroneously indicate that all translations are complete until the user refreshes the page. Upon refreshing the page, the collection's Translated column status will correctly indicate a new incomplete status as a result of the change. To be determined MYVC-7755
ePRO - Module In rare instances, an ePRO collection overview fails when generating a new overview and the user is unable to start generating another overview. None To be determined MYVC-11020
ePRO - Patient Surveys When a MyVeeva user submits an as-needed survey in the iOS and Android apps, the survey doesn't immediately appear to be available again in their tasks. Swipe down on the tasks page to refresh. The as-needed survey appears as available. To be determined MYVC-8454
ePRO - Patient Surveys When a MyVeeva user taking a survey with back-and-next buttons skips a question, answers the next question, and changes their response to make the skipped question required, the question after the previously skipped question has an inactive Next button and the user can't proceed. Users can temporarily select a different answer or reselect the same answer to enable the Next button. They can also refresh the page. To be determined MYVC-10530
ePRO - Patient Surveys In rare instances when site staff edit the datetime of a participant event which is the start event for an as-needed survey schedule, MyVeeva users stop receiving the survey. Completely remove the datetime from the participant event and add back the appropriate datetime. To be determined MYVC-10289
ePRO - Reporting When a study is created in Veeva CDB, any spaces in the study name are replaced with with underscores ( _ ), but this behavior isn't mirrored by ePRO, so the data fails to load to CDB. In Clinical Vault, replace spaces in the study name with underscores. To be determined MYVC-10877
ePRO - SiteVault Integration In rare instances when an ePRO collection document is shared with a site with a long (40+ character) name, the name may be cut off or missing text on the document. None To be determined MYVC-10483
ePRO - SiteVault Integration If site staff copy the study record of an ePRO-connected study to create a new study, the original study's ePRO connected status and ePRO-related actions are copied into the new study, and attempts to disconnect ePRO from the new study are unsuccessful. Create the new study using the Create Study action in SiteVault. To be determined MYVC-7983
Platform - Authentication When a MyVeeva user enters an unregistered email address on the Global Recover Account page (https://patients.myveeva.com/forgotpassword), they encounter an error and the request is unsuccessful. Users should recover their account on the Recover Account page specific to their region (https://patients-us.myveeva.com/forgot-password for United States, https://patients-eu.myveeva.com/forgot-password for Europe, and https://patients-ap.myveeva.com/forgot-password for Asia-Pacific) and confirm that they enter their email address correctly. To be determined MYVC-8360
Platform - Notifications When a MyVeeva user receives a Survey Available notification and completes the related survey in the Android app, the count indicator on their notification bell doesn't update to remove the notification. Users can open their notification bell to automatically clear the notification and update the count indicator. To be determined MYVC-10997
Menu
Knowledge Base
Training
System Information
Site Tools
Support/Community