Best Practices for:

Migrating to a New Safety System

Download Whitepaper

By clicking ‘Submit’ button, you are agreeing to opt-in to communications from ArisGlobal and use of the above information for ArisGlobal products, news & updates.

Note: You can unsubscribe to email communication from ArisGlobal any time.

When a company decides to install a new system, consolidate multiple application instances or upgrade to a new version of their safety system, it is imperative to ensure minimum downtime and data loss.

Safety system migration is time consuming, and is fraught with data integrity and veracity issues, so it’s important to get the maximum return on investment.

This white paper details some of the best practices and techniques including the use of PL/SQL for transfer of safety data from the older safety system to LifeSphere® Safety MultiVigilance (formerly known as ARISg). Learn how to:

  • Implement effective domestic and global pharmacovigilance, clinical safety and risk management programs
  • Analyse the existing database to define the data mapping between the two systems
  • Prepare data migration routines, then test and verify
  • Prepare the validation environment
  • Execute data migration routines in the production environment
  • Adopt case-based migration for greater flexibility
  • Thoroughly test the data and application functionality to verify all data counts have been migrated as required or described