| Table of Contents |
|---|
Summary
New versions of ClinSpark versions are released several times a year. Customers are encouraged to update regularly to each a new release. This ensures the benefit of receiving all new enhancements and fixes, and but also minimizes impact to operational and validation teams by ensuring that upgrades each upgrade are each a relatively small jump.
Here is an overview of the upgrade process:
...
To help our customers enter into a well coordinated and controlled upgrade cycle, we’ve outlined many of the common activities, expectations and responsibilities between customer and IQVIA teams and detailed article.
Example Customer Validation Process Flow
We suggest our customers review and consider these this in their own upgrade plans, and raise questions to our support team where applicable.Example Customer Validation Process Flow
| Info |
|---|
Customers should be discussing ClinSpark upgrades on a semi-frequent basis with a project manager / account manager who they are in regular contact with. Suggestions and clarifications around upgrade topics may also come from the IQVIA support team via the service desk. |
...
We anticipate our customers' need to perform training and validation activities on a new release. To support this, customers can request via a service desk ticket IQVIA provides a temporary VAL instance pair of the new release for this purpose.
This VAL instance is expected to be a short lived instance. It will be a clone of the PROD environment pair, with the upgraded version (build) applied. As such, is it expected to be a full preview of what the users will actually see once they accept the upgrade into PROD.
...
Customers request to begin the VAL process through the service desk. In the ticket, please include the following information:
...
Once validation has been completed by the customer, an upgrade to PROD Main/Test environment pair can be scheduled and coordinated. All PROD upgrades are coordinated through the service desk and with the assistance of an IQVIA PM.
...
Please ensure adequate warning is provided of the intended upgrade; minimum three weeks notice is preferred.
Upgrades typically can involve some downtime, usually a matter of minutes. The expected downtime and window size upgrade timelines will be discussed and agreed upon with the customer during the scheduling via the service desk ticket.
...