Overview

This section is intended for existing iPCV customers who are planning to migrate from iPCV V1 to iPCV V2. iPCV V2 introduces changes across data models, processing logic, privacy controls and delta processing. As a result, some existing reports, queries, dashboards and ingestion processes may require review before migrating to production use.

New customers being provisioned after the V2 launch date do not need to follow this migration guidance and should work directly with V2 documentation.

What is Changing in V2?

The changes introduced in iPCV V2 can be grouped into four broad themes.

1. Reduction of Duplicated Data

Several attributes previously duplicated across multiple models have been consolidated into dedicated shared models — Patient, Organisation, User In Role and Codeable Concept. Information that was previously available directly within a model may now require joins to these shared models.

2. Traceability and Record Linking

Additional identifiers, relationship fields and audit information improve the ability to link records across models, understand data lineage, and trace record origin and ownership.

3. Record Lifecycle and Deletion Handling

V2 introduces a more consistent approach to deletion handling and record lifecycle management, including standardised deletion indicators and improved handling of historical records.

4. Data Quality and Clinical Accuracy

V2 includes corrections and enhancements to processing logic covering patient status, registration, consultation and observation linking, timestamp standardisation, and handling of merged records.

In This Section

Page	Purpose
Before You Migrate	Understand what to expect and the recommended migration approach
Migration Checklist	Step-by-step checklist for planning and completing migration
Understanding Differences Between V1 and V2	What differences to expect during validation and why
Cross-Domain Changes	Technical changes that affect all models across the platform