Maintenance releases fix issues that affect customers in production environments. We typically document the release at least twenty-four hours before the deployment. This list documents only fixes to general releases, and the list of fixed issues is not finalized until just before the deployment.
The issues below are now fixed. See the MyVeeva for Patients Known Issues page for additional issues that staff and MyVeeva users may encounter.
November 11, 2022 | Release Number: 222.0.2 Android
This maintenance release includes performance updates for the MyVeeva for Patients Android app that aren’t visible to users.
October 21, 2022 | Release Number: 22R2.0.5
| Component | Users | Description | Issue |
|---|---|---|---|
| ePRO - Reporting | Site Staff, Sponsor Staff | When an ePRO collection contains multiple surveys with the same start event, they are now all included in the adherence and survey response data. Previously, one or more of the survey or adherence entries may have been omitted. | MYVC-10250 |
October 13, 2022 | Release Number: 22R2.0.4
This maintenance release includes updates for internal MyVeeva for Patients tools only.
September 16, 2022 | Release Number: 22R2.0.3
Enhancements
The following enhancement is now available for Veeva eConsent:
| Component | Users | Description | Number |
|---|---|---|---|
| eConsent - Other | Site Staff, Sponsor Staff | When site staff check in a Microsoft Word-based eConsent form to Vault from the eConsent editor, the system now applies the same header and footer to the .DOCX file that's applied to .PDF files. Previously, the system didn't apply this header or footer to .DOCX files. | MYVC-9801 |
Fixed Issues
The following issues are now fixed:
| Component | Users | Description | Issue |
|---|---|---|---|
| eConsent - Editor | Site Staff, Sponsor Staff | When sponsor staff or site staff export a .DOCX version of an eConsent form that has section titles containing numbers or special characters from the eConsent editor and then re-import the file to the editor, the section titles now retain the numbers and special characters. Previously, re-importing the file removed the numbers and special characters. | MYVC-9336 |
| eConsent - MyVeeva Users | MyVeeva Users, Site Staff | When site staff update a MyVeeva user's email address in their participant record in SiteVault and send them an eConsent form, the MyVeeva user can now log in to MyVeeva for Patients from the link in their welcome email as expected. Previously, the MyVeeva user may have encountered errors while attempting to log in from the link in their welcome email if site staff previously updated the user's email address in SiteVault. | MYVC-6114 |
| eConsent - Other | MyVeeva Users, Site Staff | When a MyVeeva user who doesn't have an email address or phone number in their participant record in SiteVault signs an eConsent form in person and later registers a MyVeeva account, all study documents and consent forms they received or signed before and after registering an account now appear in their documents list in MyVeeva for Patients. Previously, study documents and consent forms they received or signed prior to registering an account may have been missing from their documents list. | MYVC-9492 |
| ePRO - Module | MyVeeva Users, Site Staff, Sponsor Staff | When sponsor staff edit a survey with an as-needed schedule to use the end event as a start event and site staff trigger the start event to occur, the MyVeeva user now receives the survey in their tasks list as expected. Previously, MyVeeva users didn't receive the survey when site staff triggered the start event to occur. | MYVC-9563 |
| ePRO - Module | Sponsor Staff | When sponsor staff approve an ePRO collection that adds a survey to their library and later add more supported languages to the survey while upversioning the ePRO collection, the new languages now show as being supported by the survey as expected. Previously, when sponsor staff added supported languages to a library survey while upversioning an ePRO collection, the new languages erroneously showed as being unsupported by the survey. | MYVC-8956 |
| ePRO - Reporting | Site Staff, Sponsor Staff | If an ePRO's question or answer text contains HTML formatting (such as bold or underline tags), the HTML tags no longer appear in Survey Data exports. | MYVC-7982 |
| ePRO - Reporting | Sponsor Staff | When an approved ePRO collection contains a custom event that's used as a start event in a survey schedule and sponsor staff later edit the event's name or sequence number values while upversioning the ePRO collection, the new event name and/or sequence number is now reflected in Survey Data, Adherence Data, and Audit Trail Data exports. Previously, the event's old values reflected in data exports after upversioning the ePRO collection. | MYVC-9754 |
August 26, 2022 | Release Number: 22R2.0.2
| Component | Users | Description | Issue |
|---|---|---|---|
| eConsent - Editor | Site Staff, Sponsor Staff | When sponsor staff or site staff create a Microsoft Word-based eConsent form containing numbered headings, the order and levels of the headings now display properly within Vault, the eConsent editor, and the eConsent editor previewer. Previously, the order and levels of the form's numbered headings didn't align across Vault, the eConsent editor, and the eConsent editor previewer. | MYVC-9299 |
| eConsent - MyVeeva Users | MyVeeva Users, Site Staff, Sponsor Staff | When sponsor staff or site staff export a .DOCX version of an eConsent form including images or videos from the eConsent editor and then import the .DOCX file to the eConsent editor to create another eConsent form, the form's images and video still frames now appear in the .PDF version of the signed form when a MyVeeva user downloads it. Previously, the images and video still frames didn't appear in the .PDF version of the signed form. | MYVC-9497 |
| eConsent - MyVeeva Users | MyVeeva Users | MyVeeva users who draw their signature by hand on an eConsent form can no longer clear their signature immediately after submission. Previously, users who cleared their signature immediately after submitting the form encountered an error. | MYVC-9337 |
| eConsent - MyVeeva Users | MyVeeva Users, Site Staff | When a MyVeeva user draws their signature on an eConsent form, the form now contains additional checks to ensure their signature is captured prior to submission, and users encounter an error message if they attempt to submit a form without a signature. Previously, certain circumstances allowed MyVeeva users to submit a blank eConsent form without encountering an error. | MYVC-9298 |
| ePRO - ClinOps Integration | Site Staff, Sponsor Staff | Sponsor and site staff in the EU region can now export ePRO audit trail data from the ePRO module or from SiteVault as expected. Previously, the export failed without displaying an error message. | MYVC-9211 |
| ePRO - ClinOps Integration | Sponsor Staff | Sponsor staff in the EU region can now export ePRO response and adherence data from the ePRO module as expected. Previously, the exports failed and displayed an internal service error. | MYVC-9210 |
| ePRO - SiteVault Integration | Site Staff | When site staff connect, disconnect, and reconnect a study to ePRO in SiteVault, they can now enable participants with ePRO as expected. Previously, attempts to enable a participant with ePRO failed after disconnecting and reconnecting the study to ePRO. | MYVC-8965 |
| ePRO - SiteVault Integration | MyVeeva Users, Site Staff | When an ePRO collection contains a survey that has Study Complete as a start event in its schedule, MyVeeva users now receive the survey when site staff change the participant's lifecycle state to Complete in SiteVault. Previously, MyVeeva users didn't receive the survey unless site staff also added an event datetime to the Study Complete event associated with the participant in SiteVault. | MYVC-9462 |
| ePRO - SiteVault Integration | MyVeeva Users, Site Staff | When site staff enable ePRO for a participant whose email is incorrect in their patient record in SiteVault, disable the participant from ePRO, update the participant's email address, and reenable the participant with ePRO, the participant now receives a MyVeeva welcome email as expected. Previously, the participant didn't receive a MyVeeva welcome email when site staff reenabled them with ePRO. | MYVC-8818 |
August 12, 2022 | Release Number: 22R2.0.1
| Component | Users | Description | Issue |
|---|---|---|---|
| eConsent - MyVeeva Users | MyVeeva Users, Site Staff | If site staff change a participant’s Patient ID and send them an eConsent form, the participant can now view and sign the form in MyVeeva for Patients as expected. Previously, the change caused the participant to encounter errors in MyVeeva for Patients. When using connected apps such as MyVeeva, users should confirm the participant's Patient ID when they initially enter it to ensure it's correct. In the event that a user enters an incorrect Patient ID, they are able to change it. | MYVC-9033 |
| eConsent - MyVeeva Users | MyVeeva Users, Site Staff | If site staff change a participant’s Patient ID, the change now applies as expected. Previously, the change caused errors with the participant’s signatory roles. When using connected apps such as MyVeeva, users should confirm the participant's Patient ID when they initially enter it to ensure it's correct. In the event that a user enters an incorrect Patient ID, they are able to change it. | MYVC-8927 |
| ePRO - Epic | Site Staff, Sponsor Staff | When sponsor staff in the AP or EU regions approve a new version of ePRO for a study, sites using ePRO for that study now receive a notification in SiteVault explaining that a new version for ePRO is available. Previously, sites using ePRO for that study didn't receive this notification. | MYVC-9212 |
SiteVault
