Schema
The core schema represents the Data Freshness model schema, sourced from
IPCV data models state management tables. It tracks the data currency of each
model by recording the date range of data contained within the model
(start_datetime to end_datetime) and when that data was last refreshed
(last_updated_datetime). This enables users to assess data timeliness and
determine whether datasets meet their freshness requirements.
| Column Name | Data Type | Description | Example/Values |
|---|---|---|---|
| customer_table_name | varchar | Name of the customer table being tracked | ‘patient’ |
| organisation | varchar | Identifier for the data source organization | ‘EMIS’ |
| start_datetime | timestamp(6) with time zone | Start of the date range of data contained in the model | ‘2020-03-09 00:00:00.000000 UTC’ |
| end_datetime | timestamp(6) with time zone | End of the date range of data contained in the model | ‘2026-09-09 22:00:00.000000 UTC’ |
| last_updated_datetime | timestamp(6) with time zone | Timestamp when the model was last refreshed/updated | ‘2026-09-10 06:26:13.000000 UTC’ |
Vanilla
Section titled “Vanilla”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
Apollo
Section titled “Apollo”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
Artemis
Section titled “Artemis”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
Hermes
Section titled “Hermes”The table below presents the flavour specific schema.
| Column Name | Data Type | Core Mapping |
|---|---|---|
| table_name | varchar | customer_table_name |
| organisation | varchar | |
| start_datetime | timestamp(6) with time zone | |
| end_datetime | timestamp(6) with time zone | |
| last_updated_datetime | timestamp(6) with time zone |
Hestia
Section titled “Hestia”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
Olympus
Section titled “Olympus”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
Prometheus
Section titled “Prometheus”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
Pseudo_Anon
Section titled “Pseudo_Anon”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
Themis
Section titled “Themis”The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |
The table below presents the flavour specific schema and maps columns between core, V1, and V2. Refer to Changes in iPCV V2 for more information.
| Column Name | Data Type | Data in V1 | Data in V2 | Core Mapping | Comments |
|---|---|---|---|---|---|
| table_name | varchar | ✓ | ✓ | customer_table_name | Renamed from ipcv_table in V1 |
| organisation | varchar | ✓ | ✓ | ||
| start_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| end_datetime | timestamp(6) with time zone | ✗ | ✓ | ||
| last_updated_datetime | timestamp(6) with time zone | ✗ | ✓ | Replacement for _execution_date in V1 | |
| _execution_date | varchar | ✓ | ✗ | Replaced by last_updated_datetime in V2 | |
| mkb_version | varchar | ✓ | ✗ | Removed in V2 | |
| mkb_execution_date | varchar | ✓ | ✗ | Removed in V2 | |
| status | varchar | ✓ | ✗ | Removed in V2 |