Skip to content
Partner Developer Portal

Schema

The Problem Drug Record Core model links patient problems to prescriptions. Each row is uniquely identified by problem_observation_id, drug_record_id, and organisation.

Column NameData TypeDescriptionExample / Values
load_datetimetimestamp(6) with time zoneThe datetime that the record was last upserted into the EXA data lake from EMIS source system with a relevant change from source system.‘2023-09-01 09:00:00.000000 UTC’
_ingest_timevarcharThe load_datetime formatted as yyyyMMddHHmmss. This is a legacy column maintained for backward compatibility‘20230512143015’
problem_observation_idbigintThe unique internal identifier for the problem observation record linked to drug record, within an organisation.123456789
drug_record_idbigintThe unique internal identifier for the drug record linked to a problem, within an organisation.123456789
organisationvarcharAn identifier for the source of data (an organisation) relating to a given GP practice‘CDB-1234’
is_deletedbooleanIndicates whether a drug record has been deleted at source.FALSE
problem_observation_guidvarcharThe GUID for the problem within an organisation linked to this drug record‘f6a7b8c9-d0e1-9f2a-4b5c-6d7e8f9a0b1c’
problem_observation_uuidvarcharThe UUID derived from problem_observation_id and organisation, providing a stable unique identifier.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
drug_record_guidvarcharThe GUID for the drug record linked to problem, within an organisation.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
drug_record_uuidvarcharThe UUID derived from drug_record_id and organisation, providing a stable unique identifier.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
patient_idbigintThe unique internal identifier for the patient record within the organisation, for whom the drug record was prescribed.123456
patient_guidvarcharThe unique GUID for the patient record within an organisation‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
patient_uuidvarcharThe UUID derived from patient_id and organisation, providing a stable unique identifier‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
patient_organisation_idbigintThe unique internal identifier for the organisation where the patient is registered12345
patient_organisation_guidvarcharThe GUID of the organisation where the patient is registered‘c9d0e1f2-a3b4-2c5d-7e8f-9a0b1c2d3e4f’
patient_organisation_uuidvarcharThe UUID derived from patient_organisation_id and organisation, providing a stable unique identifier.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
drug_record_organisation_idbigintThe unique internal identifier of the organisation where the drug record was prescribed12345
drug_record_organisation_guidvarcharThe GUID of the organisation where the drug record was prescribed.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
drug_record_organisation_uuidvarcharThe UUID derived from drug_record_organisation_id and organisation, providing a stable unique identifier‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
availability_datetimetimestamp(6) with time zoneThe date and time the drug record was recorded in the source system‘2023-09-01 10:30:00.000000 UTC’
drug_record_code_idbigintThe unique EMIS code identifier for the drug record prescribed record1505741000033119
observation_code_idbigintThe unique EMIS code identifier for the clinical code associated with the problem2716321000006116
confidentiality_policy_idbigintIdentifier of the applied confidentiality policy-1
is_sensitivebooleanIndicates whether the drug record is flagged as sensitive. The sensitive reference set codes are 999004351000000109( gender related issues), 999004371000000100(assisted fertilisation), 999004361000000107(termination of pregnancy) and 999004381000000103 (sexually transmitted disease)FALSE
is_confidentialbooleanIndicates whether the observation record is confidential. This is based on confidentiality policy set against the patient / drug recordTRUE
transform_datetimetimestamp(6) with time zoneThe timestamp indicating when the record was last processed and updated in the data model. This field is crucial for understanding the current state of the data.‘2024-01-15 03:00:05.000000 UTC’
_execution_datevarcharThe transform_datetime formatted as yyyyMMddHHmmss. This is a legacy column provided only for backward compatibility with.‘20240115030005’

The Problem Issue Record Core model links patient problems to prescription issues. Each row is uniquely identified by problem_observation_id, issue_record_id, and organisation.

Column NameData TypeDescriptionExample / Values
_ingest_timevarcharThe load_datetime formatted as yyyyMMddHHmmss. This is a legacy column maintained for backward compatibility‘20230512143015’
problem_observation_idbigintThe unique internal identifier for the problem observation record linked to issue record, within an organisation.123456789
issue_record_idbigintThe unique internal identifier for the issue record linked to a problem, within an organisation.111222333
organisationvarcharAn identifier for the source of data (an organisation) relating to a given GP practice‘CDB-1234’
load_datetimetimestamp(6) with time zoneThe datetime that the record was last upserted into the EXA data lake from EMIS source system with a relevant change from source system.‘2023-09-01 09:00:00.000000 UTC’
is_deletedbooleanIndicates whether an issue record has been deleted at source.FALSE
problem_observation_guidvarcharThe GUID for the problem within an organisation linked to this issue record‘f6a7b8c9-d0e1-9f2a-4b5c-6d7e8f9a0b1c’
problem_observation_uuidvarcharThe UUID derived from problem_observation_id and organisation, providing a stable unique identifier.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
issue_record_guidvarcharThe GUID for the issue record linked to problem, within an organisation.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
issue_record_uuidvarcharThe UUID derived from issue_record_id and organisation, providing a stable unique identifier.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
patient_idbigintThe unique internal identifier for the patient record within the organisation, for whom the issue record was issued.123456
patient_guidvarcharThe unique GUID for the patient record within an organisation‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
patient_uuidvarcharThe UUID derived from patient_id and organisation, providing a stable unique identifier‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
patient_organisation_idbigintThe unique internal identifier for the organisation where the patient is registered12345
patient_organisation_guidvarcharThe GUID of the organisation where the patient is registered‘c9d0e1f2-a3b4-2c5d-7e8f-9a0b1c2d3e4f’
patient_organisation_uuidvarcharThe UUID derived from patient_organisation_id and organisation, providing a stable unique identifier.‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
issue_record_organisation_idbigintThe unique internal identifier of the organisation where the issue record was issued112233
issue_record_organisation_guidvarcharThe GUID of the organisation where the issue record was issued.‘xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx’
issue_record_organisation_uuidvarcharThe UUID derived from issue_record_organisation_id and organisation, providing a stable unique identifier‘a1b2c3d4-e5f6-4a5b-9c8d-0e1f2a3b4c5d’
availability_datetimetimestamp(6) with time zoneThe date and time the issue record was recorded in the source system‘2023-09-01 10:30:00.000000 UTC’
issue_record_code_idbigintThe unique EMIS code identifier for the issued record578241000033111
observation_code_idbigintThe unique EMIS code identifier for the clinical code associated with the problem18423015
confidentiality_policy_idbigintIdentifier of the applied confidentiality policy-1
is_sensitivebooleanIndicates whether the issue record is flagged as sensitive. The sensitive reference set codes are 999004351000000109( gender related issues), 999004371000000100(assisted fertilisation), 999004361000000107(termination of pregnancy) and 999004381000000103 (sexually transmitted disease)FALSE
is_confidentialbooleanIndicates whether the observation record is confidential. This is based on confidentiality policy set against the patient / issue recordTRUE
transform_datetimetimestamp(6) with time zoneThe timestamp indicating when the record was last processed and updated in the data model. This field is crucial for understanding the current state of the data.‘2024-01-15 03:00:05.000000 UTC’
_execution_datevarcharThe transform_datetime formatted as yyyyMMddHHmmss. This is a legacy column provided only for backward compatibility with.‘20240115030005’

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_emis_observation_guidvarchar✓✓problem_observation_guid
problem_exa_observation_guidvarchar✓✓problem_observation_uuid
drug_record_idbigint✗✓
emis_drug_guidvarchar✓✓drug_record_guid
exa_drug_guidvarchar✓✓drug_record_uuid
emis_patient_idbigint✓✓patient_id
registration_guidvarchar✓✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
fhir_medication_intentvarchar✓✓Always NULL in V2
recorded_datetimestamp(6) with time zone✓✓availability_datetime
drug_record_code_idbigint✓✓Renamed from emis_code_id in V1
observation_code_idbigint✗✓
sensitive_flagboolean✓✓is_sensitive
confidentiality_policy_idbigint✓✓
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
_record_versionvarchar✓✗
confidential_patient_flagboolean✓✗
dummy_patient_flagboolean✓✗
non_regular_and_current_active_flagboolean✓✗
opt_out_93c1_flagboolean✓✗
opt_out_9nd19nu09nu4_flagboolean✓✗
opt_out_9nd19nu0_flagboolean✓✗
opt_out_9nu0_flagboolean✓✗
regular_and_current_active_flagboolean✓✗
regular_current_active_and_inactive_flagboolean✓✗
regular_patient_flagboolean✓✗
sensitive_patient_flagboolean✓✗
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_emis_observation_guidvarchar✓✓problem_observation_guid
problem_exa_observation_guidvarchar✓✓problem_observation_uuid
issue_record_idbigint✗✓
emis_issue_guidvarchar✓✓issue_record_guid
exa_issue_guidvarchar✓✓issue_record_uuid
emis_patient_idbigint✓✓patient_id
registration_guidvarchar✓✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
fhir_medication_intentvarchar✓✓Always NULL in V2
recorded_datetimestamp(6) with time zone✓✓availability_datetime
issue_record_code_idbigint✓✓Renamed from emis_code_id in V1
observation_code_idbigint✗✓
sensitive_flagboolean✓✓is_sensitive
confidentiality_policy_idbigint✓✓
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
_record_versionvarchar✓✗
confidential_patient_flagboolean✓✗
dummy_patient_flagboolean✓✗
non_regular_and_current_active_flagboolean✓✗
opt_out_93c1_flagboolean✓✗
opt_out_9nd19nu09nu4_flagboolean✓✗
opt_out_9nd19nu0_flagboolean✓✗
opt_out_9nu0_flagboolean✓✗
regular_and_current_active_flagboolean✓✗
regular_current_active_and_inactive_flagboolean✓✗
regular_patient_flagboolean✓✗
sensitive_patient_flagboolean✓✗

Not used in this schema

Not used in this schema

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_emis_observation_guidvarchar✓✓problem_observation_guid
problem_exa_observation_guidvarchar✓✓problem_observation_uuid
drug_record_idbigint✗✓
emis_drug_guidvarchar✓✓drug_record_guid
exa_drug_guidvarchar✓✓drug_record_uuid
emis_patient_idbigint✓✓patient_id
registration_guidvarchar✓✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
fhir_medication_intentvarchar✓✓Always NULL in V2
recorded_datetimestamp(6) with time zone✓✓availability_datetime
drug_record_code_idbigint✓✓Renamed from emis_code_id in V1
observation_code_idbigint✗✓
sensitive_flagboolean✓✓is_sensitive
confidentiality_policy_idbigint✓✓
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
_record_versionvarchar✓✗
confidential_patient_flagboolean✓✗
dummy_patient_flagboolean✓✗
non_regular_and_current_active_flagboolean✓✗
opt_out_93c1_flagboolean✓✗
opt_out_9nd19nu09nu4_flagboolean✓✗
opt_out_9nd19nu0_flagboolean✓✗
opt_out_9nu0_flagboolean✓✗
regular_and_current_active_flagboolean✓✗
regular_current_active_and_inactive_flagboolean✓✗
regular_patient_flagboolean✓✗
sensitive_patient_flagboolean✓✗
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_emis_observation_guidvarchar✓✓problem_observation_guid
problem_exa_observation_guidvarchar✓✓problem_observation_uuid
issue_record_idbigint✗✓
emis_issue_guidvarchar✓✓issue_record_guid
exa_issue_guidvarchar✓✓issue_record_uuid
emis_patient_idbigint✓✓patient_id
registration_guidvarchar✓✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
fhir_medication_intentvarchar✓✓Always NULL in V2
recorded_datetimestamp(6) with time zone✓✓availability_datetime
issue_record_code_idbigint✓✓Renamed from emis_code_id in V1
observation_code_idbigint✗✓
sensitive_flagboolean✓✓is_sensitive
confidentiality_policy_idbigint✓✓
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
_record_versionvarchar✓✗
confidential_patient_flagboolean✓✗
dummy_patient_flagboolean✓✗
non_regular_and_current_active_flagboolean✓✗
opt_out_93c1_flagboolean✓✗
opt_out_9nd19nu09nu4_flagboolean✓✗
opt_out_9nd19nu0_flagboolean✓✗
opt_out_9nu0_flagboolean✓✗
regular_and_current_active_flagboolean✓✗
regular_current_active_and_inactive_flagboolean✓✗
regular_patient_flagboolean✓✗
sensitive_patient_flagboolean✓✗

The table below presents the flavour specific schema.

Column NameData TypeCore Mapping
is_deletedboolean
pseudo_problem_observation_uuidvarcharproblem_observation_uuid
pseudo_drug_record_uuidvarchardrug_record_uuid
pseudo_patient_uuidvarcharpatient_uuid
pseudo_patient_organisation_uuidvarcharpatient_organisation_uuid
pseudo_drug_record_organisation_uuidvarchardrug_record_organisation_uuid
availability_datetimetimestamp(6) with time zone
drug_record_code_idbigint
observation_code_idbigint
confidentiality_policy_idbigint
is_sensitiveboolean
is_confidentialboolean
organisationvarchar
transform_datetimetimestamp(6) with time zone
Column NameData TypeCore Mapping
is_deletedboolean
pseudo_problem_observation_uuidvarcharproblem_observation_uuid
pseudo_issue_record_uuidvarcharissue_record_uuid
pseudo_patient_uuidvarcharpatient_uuid
pseudo_patient_organisation_uuidvarcharpatient_organisation_uuid
pseudo_issue_record_organisation_uuidvarcharissue_record_organisation_uuid
availability_datetimetimestamp(6) with time zone
issue_record_code_idbigint
observation_code_idbigint
confidentiality_policy_idbigint
is_sensitiveboolean
is_confidentialboolean
organisationvarchar
transform_datetimetimestamp(6) with time zone

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_idvarchar✓✓problem_observation_guid
problem_id_type5varchar✓✓problem_observation_uuid
drug_record_idbigint✗✓
drug_record_guidvarchar✓✓Renamed from medication_id in V1
drug_record_uuidvarchar✓✓Renamed from exa_medication_guid in V1
patientidbigint✓✓patient_id
registration_idvarchar✓✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
recorded_datetimestamp(6) with time zone✓✓availability_datetime
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
hestia_event_typevarchar✓✗
regular_patient_flagboolean✓✗
regular_current_active_and_inactivevarchar✓✗
regular_and_current_activevarchar✓✗
non_regular_and_current_activevarchar✓✗
sensitive_patient_flagboolean✓✗
confidential_patient_flagboolean✓✗
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_idvarchar✓✓problem_observation_guid
problem_id_type5varchar✓✓problem_observation_uuid
issue_record_idbigint✗✓
issue_record_guidvarchar✓✓Renamed from medication_id in V1
issue_record_uuidvarchar✓✓Renamed from exa_medication_guid in V1
patientidbigint✓✓patient_id
registration_idvarchar✓✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
recorded_datetimestamp(6) with time zone✓✓availability_datetime
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
hestia_event_typevarchar✓✗
regular_patient_flagboolean✓✗
regular_current_active_and_inactivevarchar✓✗
regular_and_current_activevarchar✓✗
non_regular_and_current_activevarchar✓✗
sensitive_patient_flagboolean✓✗
confidential_patient_flagboolean✓✗

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
emis_observation_guidvarchar✓✓problem_observation_guid
exa_observation_guidvarchar✓✓problem_observation_uuid
drug_record_idbigint✗✓
emis_drug_guidvarchar✓✓drug_record_guid
exa_drug_guidvarchar✓✓drug_record_uuid
pseudo_registration_guidvarchar✓✓patient_guidhashed
pseudo_patient_uuidvarchar✗✓patient_uuidhashed
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
entered_datedate✓✓availability_datetime
entered_timetimestamp(6) with time zone✓✓availability_datetime
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
intentvarchar✓✗
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
emis_observation_guidvarchar✓✓problem_observation_guid
exa_observation_guidvarchar✓✓problem_observation_uuid
issue_record_idbigint✗✓
emis_issue_guidvarchar✓✓issue_record_guid
exa_issue_guidvarchar✓✓issue_record_uuid
pseudo_registration_guidvarchar✓✓patient_guidhashed
pseudo_patient_uuidvarchar✗✓patient_uuidhashed
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
entered_datedate✓✓availability_datetime
entered_timetimestamp(6) with time zone✓✓availability_datetime
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓
intentvarchar✓✗

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
emis_observation_guidvarchar✓✓problem_observation_guid
exa_observation_guidvarchar✓✓problem_observation_uuid
drug_record_idbigint✗✓
emis_drug_guidvarchar✓✓drug_record_guid
exa_drug_guidvarchar✓✓drug_record_uuid
pseudo_registration_guidvarchar✓✓patient_guidhashed
pseudo_patient_uuidvarchar✗✓patient_uuidhashed
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
entered_datedate✓✓availability_datetime
entered_timetimestamp(6) with time zone✓✓availability_datetime
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓Renamed from execution_date in V1
intentvarchar✓✗
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
emis_observation_guidvarchar✓✓problem_observation_guid
exa_observation_guidvarchar✓✓problem_observation_uuid
issue_record_idbigint✗✓
emis_issue_guidvarchar✓✓issue_record_guid
exa_issue_guidvarchar✓✓issue_record_uuid
pseudo_registration_guidvarchar✓✓patient_guidhashed
pseudo_patient_uuidvarchar✗✓patient_uuidhashed
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
entered_datedate✓✓availability_datetime
entered_timetimestamp(6) with time zone✓✓availability_datetime
confidential_flagboolean✓✓is_confidential
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓Renamed from execution_date in V1
intentvarchar✓✗

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_observation_guidvarchar✓✓
problem_observation_uuidvarchar✗✓
drug_record_idbigint✗✓
drug_record_guidvarchar✓✓
drug_record_uuidvarchar✗✓
patient_guidvarchar✓✓
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
entered_datedate✓✓availability_datetime
entered_timetimestamp(6) with time zone✓✓availability_datetime
is_confidentialboolean✓✓
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓Renamed from execution_date in V1
intentvarchar✓✗
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_observation_guidvarchar✓✓
problem_observation_uuidvarchar✗✓
issue_record_idbigint✗✓
issue_record_guidvarchar✓✓
issue_record_uuidvarchar✗✓
patient_guidvarchar✓✓
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✓✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
entered_datedate✓✓availability_datetime
entered_timetimestamp(6) with time zone✓✓availability_datetime
is_confidentialboolean✓✓
organisationvarchar✓✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✓✓Renamed from execution_date in V1
intentvarchar✓✗

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✗✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_emis_observation_guidvarchar✗✓problem_observation_guid
problem_exa_observation_guidvarchar✗✓problem_observation_uuid
drug_record_idbigint✗✓
emis_drug_guidvarchar✗✓drug_record_guid
exa_drug_guidvarchar✗✓drug_record_uuid
emis_patient_idbigint✗✓patient_id
registration_guidvarchar✗✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✗✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
recorded_datetimestamp(6) with time zone✗✓availability_datetime
drug_record_code_idbigint✗✓Renamed from emis_code_id in V1
observation_code_idbigint✗✓
sensitive_flagboolean✗✓is_sensitive
confidentiality_policy_idbigint✗✓
confidential_flagboolean✗✓is_confidential
organisationvarchar✗✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✗✓
customer_accountvarchar✓✗
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✗✓
is_deletedboolean✗✓
load_datetimetimestamp(6) with time zone✗✓
problem_observation_idbigint✗✓
problem_emis_observation_guidvarchar✗✓problem_observation_guid
problem_exa_observation_guidvarchar✗✓problem_observation_uuid
issue_record_idbigint✗✓
emis_issue_guidvarchar✗✓issue_record_guid
exa_issue_guidvarchar✗✓issue_record_uuid
emis_patient_idbigint✗✓patient_id
registration_guidvarchar✗✓patient_guid
patient_uuidvarchar✗✓
patient_organisation_idbigint✗✓
emis_registration_organisation_guidvarchar✗✓patient_organisation_guid
patient_organisation_uuidvarchar✗✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
recorded_datetimestamp(6) with time zone✗✓availability_datetime
issue_record_code_idbigint✓✓Renamed from emis_code_id in V1
observation_code_idbigint✗✓
sensitive_flagboolean✗✓is_sensitive
confidentiality_policy_idbigint✗✓
confidential_flagboolean✗✓is_confidential
organisationvarchar✗✓
transform_datetimetimestamp(6) with time zone✗✓
_execution_datevarchar✗✓
customer_accountvarchar✓✗

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 NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓
is_deletedboolean✓
load_datetimetimestamp(6) with time zone✓
problem_observation_idbigint✓
problem_emis_observation_guidvarchar✓problem_observation_guid
problem_exa_observation_guidvarchar✓problem_observation_uuid
drug_record_idbigint✓
emis_drug_guidvarchar✓drug_record_guid
exa_drug_guidvarchar✓drug_record_uuid
pseudo_registration_guid_oureavarchar✓patient_guidhashed
pseudo_patient_uuidvarchar✓patient_uuidhashed
patient_organisation_idbigint✓
emis_registration_organisation_guidvarchar✓patient_organisation_guid
patient_organisation_uuidvarchar✓
drug_record_organisation_idbigint✗✓
drug_record_organisation_guidvarchar✗✓
drug_record_organisation_uuidvarchar✗✓
recorded_datetimestamp(6) with time zone✓availability_datetime
drug_record_code_idbigint✓Renamed from emis_code_id in V1
observation_code_idbigint✓
sensitive_flagboolean✓is_sensitive
confidentiality_policy_idbigint✓
confidential_flagboolean✓is_confidential
organisationvarchar✓
transform_datetimetimestamp(6) with time zone✓
_execution_datevarchar✓
Column NameData TypeData in V1Data in V2Core MappingComments
_ingest_timevarchar✓
is_deletedboolean✓
load_datetimetimestamp(6) with time zone✓
problem_observation_idbigint✓
problem_emis_observation_guidvarchar✓problem_observation_guid
problem_exa_observation_guidvarchar✓problem_observation_uuid
issue_record_idbigint✓
emis_issue_guidvarchar✓issue_record_guid
exa_issue_guidvarchar✓issue_record_uuid
pseudo_registration_guid_oureavarchar✓patient_guidhashed
pseudo_patient_uuidvarchar✓patient_uuidhashed
patient_organisation_idbigint✓
emis_registration_organisation_guidvarchar✓patient_organisation_guid
patient_organisation_uuidvarchar✓
issue_record_organisation_idbigint✗✓
issue_record_organisation_guidvarchar✗✓
issue_record_organisation_uuidvarchar✗✓
recorded_datetimestamp(6) with time zone✓availability_datetime
issue_record_code_idbigint✓Renamed from emis_code_id in V1
observation_code_idbigint✓
sensitive_flagboolean✓is_sensitive
confidentiality_policy_idbigint✓
confidential_flagboolean✓is_confidential
organisationvarchar✓
transform_datetimetimestamp(6) with time zone✓
_execution_datevarchar✓