Schema

Core

The core schema represents the Codeable Concept schema derived from EMIS source systems.

Column Name	Data Types	Description	Example
is_deleted	boolean	Indicates if this record should be considered soft deleted	TRUE
code_id	bigint	The unique EMIS code identifier for the clinical code, which can be used to map local or legacy concepts to national standards like SNOMED CT or legacy Read Codes.	1572871000006117
term	varchar	The description of the EMIS clinical code	Splinter haemorrhage
snomed_concept_id	bigint	The unique identifier for concepts within the SNOMED CT clinical terminology.	145021000033107
snomed_description_id	bigint	The unique identifier for the preferred term that describes the concept within the SNOMED CT clinical terminology.	145021000033111
fully_specified_name	varchar	The description of the SNOMED clinical concept	Tape (substance)
readv2_code	varchar	The code that provide a standard vocabulary for clinicians to record patient findings and procedures, in health and social care IT systems across primary and secondary care. These codes have been retired since 2016.	4A12.00
other_code_system	varchar	Other system http address	https://fhir.hl7.org.uk/Id/egton-codes
other_code	varchar	The code from EMIS legacy coding system	ALLERGY4070
other_display	varchar	The description from the legacy EMIS coding system	Nature’s Bounty Vitamin E
organisation	varchar	Set to ‘EMIS’	EMIS
transform_datetime	timestamp(6) with time zone	The timestamp indicating when the record was last processed and updated in the data model.	‘2023-09-01 09:00:00.000000 UTC’
_execution_date	varchar	The transform_datetime formatted as yyyyMMddHHmmss. This column is provided only for backward compatibility.	20241015070047

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

Hermes

The table below presents the flavour specific schema.

Column Name	Data Type
is_deleted	boolean
code_id	bigint
term	varchar
snomed_concept_id	bigint
snomed_description_id	bigint
fully_specified_name	varchar
readv2_code	varchar
other_code_system	varchar
other_code	varchar
other_display	varchar
organisation	varchar
transform_datetime	timestamp(6) with time zone

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
fully_specified_name	varchar	✓	✓
other_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_display	varchar	✓	✓
readv2_code	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
term	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓

Zeus

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 Types	Data in V1	Data in V2	Core Mapping
_record_version	varchar	✓	✗
_mkb_version	varchar	✓	✗
_ingest_time	varchar	✓	✗
is_deleted	boolean	✗	✓
emis_code_id	bigint	✓	✓	code_id
term	varchar	✓	✓
snomed_concept_id	bigint	✓	✓
snomed_description_id	bigint	✓	✓
fully_specified_name	varchar	✓	✓
readv2_code	varchar	✓	✓
other_code_system	varchar	✓	✓
other_code	varchar	✓	✓
other_display	varchar	✓	✓
organisation	varchar	✓	✓
transform_datetime	timestamp(6) with time zone	✗	✓
_execution_date	varchar	✓	✓
data_filter	integer	✓	✗