Viedoc and Backwards Compatibility

  • Published by Viedoc System 2021-06-11
  • Print

Viedoc is a leading eClinical software and is delivered as a multitenant, Software-as-a-Service (SaaS) solution. A multitenant solution is one where customers share a single instance of the application. SaaS solutions are also often called “cloud” or “cloud-based” solutions.

Viedoc is installed and operated in the “cloud” and all customers in the same region share the same instance. The solution is delivered through four production instances located in the US, Europe, Japan and China. Viedoc Technologies as a company are responsible for installation, operations and maintenance of Viedoc. We also continually develop and release new versions of Viedoc 7-8 times a year, usually once every 6 weeks. Unlike most other vendors, once a new version of Viedoc is ready for release it is simultaneously pushed to all instances and all customers get access to the new version at the same time. The obvious benefit of this is that all users have the possibility to make use of both new and improved functionality and the risk of falling behind on important updates is eliminated.

This way of managing new releases has also resulted in the requirement on Viedoc that all releases must be backwards compatible. The reason for this requirement is straightforward – a new release should never require a change in the study configuration of ongoing studies, affect the look and feel of the study or require the revalidation of the setup of those trials.

Viedoc Technologies have adopted a risk-based development approach to ensure backwards compatibility. An impact analysis is performed for all changes to Viedoc (new functionality, improved functionality and bug corrections) and the results are documented. Regression testing is performed during unit testing, system testing and PQ testing.

The goal is that all studies will look and work the same for all users after the release. Most customers build and manage their own studies in Viedoc, and Viedoc Technologies has no access to either the study setup or the study data. In these cases, customers are recommended to review and evaluate new and changed functionality to see whether their study would be affected by the release. This is normally only applicable if a customer wants to enable a new feature in the study. To assist our users Viedoc publishes the following information about all releases:

  • In the Viedoc eLearning there is information about the main contents of the next release, and a list of functions that are in the road map for releases after that.

  • One week before a release, the detailed release notes describing the contents of the release are posted on our website.

  • The Viedoc Inspection Readiness Packet (VIRP) is updated with detailed information about the validation of the release and is released shortly after the new version of Viedoc.

The impact and design section of user requirements and of bug reports are included as part of the release documentation in VIRP. This allows customers to compare changes in Viedoc functionality to their study configuration and confirm that their study is not affected, without the need to revalidate the study setup for every new release.

In the rare instance that a breach of backwards compatibility does occur, then all affected customers are notified in advance with details about the breach and the actions they should take.

By delivering 7-8 versions of Viedoc each year, we provide the possibility for customers to make instant use of new functionality, should they choose to do so. A successful new release of Viedoc is one that is not noticed by the users of ongoing studies!