Before You Migrate

iPCV V2 introduces changes across data models, processing logic, privacy controls and delta processing. The purpose of this guide is to help customers understand those changes, assess their impact and prepare for a successful migration.

What Should You Expect?

The changes introduced in iPCV V2 can be grouped into four broad themes that affect multiple models across the platform.

1. Reduction of Duplicated Data and Single Source of Truth

Several attributes that were previously duplicated across multiple models have been consolidated into dedicated shared models such as Patient, Organisation, User In Role and Codeable Concept.

This improves consistency and reduces the risk of conflicting representations of the same information. As a result, information that was previously available directly within a model may now be obtained through joins to dedicated shared models.

2. Traceability, Auditability and Record Linking

Additional identifiers, relationship fields and audit information have been introduced across many models. These changes improve the ability to:

• Link records across models
• Understand data lineage
• Trace how records relate to one another
• Identify record origin and ownership

This includes the introduction of additional IDs, UUIDs and relationship fields throughout the platform.

3. Record Lifecycle, Deletion and Historical Record Management

V2 introduces a more consistent approach to deletion handling and record lifecycle management. Changes include:

• Standardised deletion indicators
• Lifecycle metadata
• Historical record retention
• Improved handling of deleted records

Customers may observe differences in how deleted or historical records are represented when compared to V1.

4. Data Quality and Clinical Accuracy Improvements

V2 includes corrections and enhancements to existing processing logic. Examples include:

• Patient status logic improvements
• Registration logic improvements
• Consultation and observation linking improvements
• Timestamp standardisation
• More complete record inclusion
• Improved handling of merged records

These changes improve the accuracy, completeness and reliability of existing information rather than introducing new categories of data.

Recommended Migration Approach

1. Review Understanding Differences Between V1 and V2.
2. Review Cross-Domain Changes.
3. Review the domain-specific migration pages relevant to your use cases.
4. Validate existing reports, analytical outputs and data ingestion processes against V2 data.
5. Update any queries or pipelines affected by the documented changes.
6. Complete testing before migrating production workloads.

Do I Need To Review Every Model?

No. Many of the changes in iPCV V2 are platform-wide and affect multiple models. Review Cross-Domain Changes first, then focus on the domains and models actively used within your organisation.

If you use…	Review…
Population health reporting, patient demographics, registration status, consent and opt-out reporting	Patient Domain Changes
Appointment scheduling, utilisation and activity reporting	Appointments Domain Changes
Consultation activity and consultation-based reporting	Consultations Domain Changes
Clinical activity reporting, conditions, observations, allergies, immunisations, referrals, family history and diary activity	Clinical Records Domain Changes
Prescribing, medication management and prescribing analytics	Medications Domain Changes
Organisation, location, workforce and data-sharing reporting	Organisations & Users Domain Changes
Clinical coding, SNOMED mappings, drug reference data and terminology lookups	Clinical Coding & Reference Data Domain Changes
Data freshness monitoring and operational metadata	Platform & Operations Domain Changes

Domain-specific migration documentation is available within the relevant model documentation section.