Migration Checklist
This checklist is designed to help existing iPCV customers prepare for migration from iPCV V1 to iPCV V2. Not every item will apply to every customer — focus on the reports, analytical workloads and data pipelines currently used within your organisation.
Understand the Changes
Section titled “Understand the Changes”- Read Before You Migrate
- Review Understanding Differences Between V1 and V2
- Review Cross-Domain Changes
Review Relevant Domain Changes
Section titled “Review Relevant Domain Changes”Only review the domains actively used within your organisation.
- Organisations & Users Domain Changes
- Patient Domain Changes
- Appointments Domain Changes
- Consultations Domain Changes
- Clinical Records Domain Changes
- Medications Domain Changes
- Clinical Coding & Reference Data Domain Changes
- Platform & Operations Domain Changes
Assess Impact on Existing Solutions
Section titled “Assess Impact on Existing Solutions”- Identify reports that consume iPCV V1 data.
- Identify dashboards that consume iPCV V1 data.
- Identify automated data extraction or ingestion processes.
- Identify any custom SQL queries that rely on iPCV V1 models or fields.
Set Up and Test V2
Section titled “Set Up and Test V2”- Follow the relevant setup and connection documentation for iPCV V2.
- Confirm V2 data is being received successfully.
- Recreate key queries against V2.
- Recreate key reports and dashboards against V2.
- Update automated data extraction or ingestion processes for V2.
Validate V1 and V2 Outputs
Section titled “Validate V1 and V2 Outputs”- Identify the reports, dashboards and processes that will be validated during the migration period.
- Compare key reports between V1 and V2.
- Compare key analytical outputs between V1 and V2.
- Review any unexpected differences against the migration documentation.
- Confirm that expected changes are understood before raising issues.
Update Queries & Pipelines
Section titled “Update Queries & Pipelines”- Update any queries affected by model changes.
- Update any joins affected by new identifiers or reference models.
- Update any delta ingestion processes affected by V2 changes.
- Validate downstream integrations and local data stores.
Migration Complete
Section titled “Migration Complete”Before switching reporting, analytics and data ingestion processes from iPCV V1 to iPCV V2, confirm:
- Relevant migration documentation has been reviewed.
- Required query changes have been implemented.
- Required pipeline changes have been implemented.
- Validation activities have been completed.
- Differences identified between V1 and V2 have been reviewed and understood.
- Any remaining differences have been assessed and are accepted by your organisation.
- Stakeholders understand any expected changes in reporting outputs following migration to V2.